July 2014 - Devel - oVirt List Archives

python-pthreading 0.1.3-3
by ybronhei 13 Jul '14

13 Jul '14

Hello everybody, Few days ago we published python-pthreading 0.1.3-2 which included a patch ([1]) that fixes urgent bug in ovirt ([2]) Today we found out that this build also includes a patch (called monkey_patch: Fail if it is too late to monkey-patch) that introduces regression with older versions of ovirt. Therefore we publish new build (0.1.3-3) that includes only the required fix. Please test and give it a karma for your environment, if you can [3] [4] [5] [6] [7] Thanks, [1] Add the missing locked() interface [2] https://bugzilla.redhat.com/show_bug.cgi?id=1117795 [3] http://koji.fedoraproject.org/koji/buildinfo?buildID=543650 (el6) [4] http://koji.fedoraproject.org/koji/buildinfo?buildID=543651 (f19) [5] http://koji.fedoraproject.org/koji/buildinfo?buildID=543653 (f20) [6] http://koji.fedoraproject.org/koji/buildinfo?buildID=543649 (f21) [7] http://koji.fedoraproject.org/koji/buildinfo?buildID=543655 (el7) -- Yaniv Bronhaim.

1 0

Re: [ovirt-devel] [vdsm] compile vdsm and attach it to a engine.
by ybronhei 13 Jul '14

13 Jul '14

On 07/03/2014 05:11 AM, aaron Beein wrote: > Hi, > > Thank you for your great job on ovirt and vdsm. Now I devote myself to > compile vdsm on centos 6.3 host and attach it to a ovirt engine. But when I > attach the host which contains a compiled vdsm to a ovirt engine , the > status of the host is always ‘Non Responsive’(step 11 below). I reference > the links below: > > http://www.ovirt.org/Vdsm_Developers > > http://www.ovirt.org/Installing_VDSM_from_rpm > > > > The steps( 1-9 ) are executed on centos6.3 host, and the steps(10--11) are > executed on ovirt engine. So I would be very grateful if you can give me > some clues that if I've missed anything or I done something wrong. > > The attachment is the same as the bellow which makes it easier for you to > read. > 1 Deployment platform > > Centos6.3 > > Linux bogon 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 21:14:45 UTC 2014 > x86_64 x86_64 x86_64 GNU/Linux > > Ip ： 10.1.8.252 > > CPU supports hardware virtualization extensions: > > # cat /proc/cpuinfo | egrep 'svm|vmx'| grep nx > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc > aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr > pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb > xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc > aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr > pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb > xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid > 2 Apply all updates # yum -y update 3 Installing required packages > > RHEL 6 users must add EPEL yum repository for installing python-ordereddict > and pyton-pthreading. The rpm bellow will install the epel yum repo and > required gpg keys. > > # yum install http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.r… > > RHEL 6 users must install a newer pep8 version than the one shipped in > EPEL6. Older pep8 versions have a bug that's tickled by vdsm. You can use > `pip`, or > > yum install http://danken.fedorapeople.org/python-pep8-1.4.5-2.el6.noarch.rpm > > oVirt repo: > > yum install http://resources.ovirt.org/releases/ovirt-release.noarch.rpm > > RHEL 6 users must add the glusterfs repository, providing newer glusterfs > not available on RHEL 6. Optionally install 'wget' if not present > > rpm -q wget 2> /dev/null || yum install wget > > wget -O /etc/yum.repos.d/glusterfs-epel.repo > *http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/glusterfs-epel.repo* > <http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/glusterf…> > > Fedora and RHEL 6 users must verify the following packages are installed > before attempting to build: > > yum install make autoconf automake pyflakes logrotate gcc python-pep8 > libvirt-python python-devel \ > > python-nose rpm-build sanlock-python genisoimage python-ordereddict > python-pthreading libselinux-python\ > > python-ethtool m2crypto python-dmidecode python-netaddr > python-inotify python-argparse git \ > > python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl > libtool gettext-devel python-ioprocess libvirt libvirt-client > libvirt-lock-sanlock > > 4 Getting the source > > cd /root > > git clone *http://gerrit.ovirt.org/p/vdsm.git* > <http://gerrit.ovirt.org/p/vdsm.git> > > cd vdsm > > 5 Building a Vdsm RPM > > ./autogen.sh –system > > > > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=/usr/lib --enable-hooks > > make rpm NOSE_EXCLUDE=.* > 6 Basic installation and start > > When building from source, you should enable the ovirt-beta repository, to > satisfy dependencies that are not available yet in the release repository. > > # cd ~/rpmbuild/RPMS > > # yum install --skip-broken > --enablerepo=ovirt-master-snapshot-static x86_64/* noarch/vdsm-xml* > noarch/vdsm-cli* noarch/vdsm-python-zombiereaper* > noarch/vdsm-*jsonrpc* > > > > Before starting vdsmd service for the first time vdsm requires some > configuration procedures for external services that being used by vdsmd. To > ease this process vdsm provides a utility (vdsm-tool). To perform full > reconfiguration of external services perform: > > # vdsm-tool configure --force > > (for more information read "vdsm-tool --help") > > > > > 7 Finally start the vdsmd service > > # service vdsmd start > > > 8 Yum install -y bridge-utils > > Configuring the bridge Interface as below > > Disable the network manager service by executing as root: > > systemctl stop NetworkManager.service > > systemctl disable NetworkManager.service > > > > service network start > > chkconfig network on > > Add the following content into a new file named: > */etc/sysconfig/network-scripts/ifcfg-ovirtmgmt*: > > DEVICE=ovirtmgmt > > TYPE=Bridge > > ONBOOT=yes > > DELAY=0 > > BOOTPROTO=static > > IPADDR=10.1.8.252 > > NETMASK=255.255.255.0 > > GATEWAY=10.1.8.254 > > Add the following line into the configuration file of your out going > interface (usually em1/eth0) the file is located at: > */etc/sysconfig/network-scripts/ifcfg-em1* (assuming the device is em1) > > BRIDGE=ovirtmgmt > > and remove the IPADDR, NETMASK and BOOTPROTO keys, since the interface > should not have an IP address of its own. Full Example > > DEVICE=em1 > > ONBOOT=yes > > BRIDGE=ovirtmgmt > > Restart the network service by executing: > > service network restart > > *Note that if any other bridge (from ovirtmgmt) is present at the time of > host installation, the bridge creation operation is skipped and you have to > change the bridge settings to correspond to above shown configuration > manually.* > > > > *9 Configuring VDSM* > > Add the following content into the file: */etc/vdsm/vdsm.conf* (you may > need to create that file): > > [vars] > > ssl = false > > Restart the vdsmd service by executing: > > service vdsmd restart > > If Vdsm was started earlier with ssl=true, it would refuse to start and you > may need to use the undocumented verb > > service vdsmd reconfigure you should perform - "vdsm-tool configure --force" without touching other conf files. you already did it, so nothing else required although, we you set InstallVds to true (few lines underneath), it means that when you add the host to engine it will perform all those deploying vdsm steps for you. So you don't have to do all those vdsm configuration and installation steps at all. > > service vdsmd start > > which edits */etc/libvirt/qemu.conf* and changes *spice_tls=1* to > *spice_tls=0*. > > > 10 Connect to overt-engine > > *ref: OVirt_-_connecting_development_vdsm_to_ovirt_engine > <http://www.ovirt.org/OVirt_-_connecting_development_vdsm_to_ovirt_engine>.* > > > > *su - postgres -c "psql engine -c \"UPDATE vdc_options set option_value = > 'true' where option_name = 'InstallVds'\""* > > > > *service overt-engine restart* > 11 Attach the host to the engine > > I login the engine Administration Portal , and attach the centos host to a > cluster. But it failed. > can you please attach logs (host deploy logs under /var/log/ovirt-engine/host-deploy , vdsm log under /var/log/vdsm (on host side) and engine log /var/log/ovirt-engine/engine.log) I forward the mail to devel(a)ovirt.org, vdsm-devel was merged to this one few months ago. > > > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > Regards. -- Yaniv Bronhaim.

1 0

[IMPORTANT] DB script numbering reminder
by Oved Ourfali 13 Jul '14

13 Jul '14

Hi Now that a branch was created for ovirt-engine-3.5, master is practically of version 3.6. So, when adding a DB script in a patch that is pushed to master, the numbering should start with 03_06_ABCD, where ABCD starts with 0010, second should be 0020, and so on... When this patch needs to be ported to 3.5 as well, the numbering there should be 03_05_EFGH, where EFGH is the next number in the stable branch. So, for example, if the last upgrade script in the stable branch starts with 03_05_0750, then the next should start with 03_05_0760, even if it starts with 03_06_0040 on master. Confused? we're here to help! Got it? go ahead and push some stuff! Have a great day, Oved

1 0

ovirt-guest-agent
by Sandro Bonazzola 12 Jul '14

12 Jul '14

Hi, looking at http://jenkins.ovirt.org/view/All/ I see that for ovirt-guest-agent there's only the following job: http://jenkins.ovirt.org/view/All/job/ovirt-guest-agent_master_gerrit/ This means that ovirt-guest-agent is not built nightly neither for master nor for stable and it's not published neither in nightly snapshot nor in official releases. I see that ovirt-guest-agent is shipped within Fedora and EPEL: http://koji.fedoraproject.org/koji/packageinfo?packageID=15434 so I suppose official release are shipped there. Do we need nightly builds? Also I see that http://www.ovirt.org/How_to_install_the_guest_agent_in_Fedora refers to obsolete layout / releases and the package is not shipped within oVirt repo for above considerations and should be updated accordingly. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4

[vdsm] VM recovery now depends on HSM
by Adam Litke 11 Jul '14

11 Jul '14

Hi all, As part of the new live merge feature, when vdsm starts and has to recover existing VMs, it calls VM._syncVolumeChain to ensure that vdsm's view of the volume chain matches libvirt's. This involves two kinds of operations: 1) sync VM object, 2) sync underlying storage metadata via HSM. This means that HSM must be up (and the storage domain(s) that the VM is using must be accessible. When testing some rather eccentric error flows, I am finding this to not always be the case. Is there a way to have VM recovery wait on HSM to come up? How should we respond if a required storage domain cannot be accessed? Is there a mechanism in vdsm to schedule an operation to be retried at a later time? Perhaps I could just schedule the sync and it could be retried until the required resources are available. Thanks for your insights. -- Adam Litke

4 7

[vdsm] logging levels and noise in the log
by Martin Sivak 11 Jul '14

11 Jul '14

Hi, we discussed the right amount of logging with Nir and Francesco while reviewing my patches. Francesco was against one DEBUG log message that could potentially flood the logs. But the message in question was important for me and SLA, because it was logging the VDSM changes in response to MoM command. Since DEBUG really is meant to be used for debug messages, I have one proposal: 1) Change the default log level of vdsm.log to INFO 2) Log (only) DEBUG messages to a separate file vdsm-debug.log 3) Make the vdsm-debug.log rotate faster (every hour, keep only last couple of hours?) so it does not grow too much This way the customer would be able to monitor INFO logs (much smaller) without all the noise and we would be able to collect the DEBUG part in case something happens. What do you think? -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

7 11

Call for Papers Deadline In Two Days: Linux.conf.au
by Brian Proffitt 11 Jul '14

11 Jul '14

Conference: Linux.conf.au Information: Each year open source geeks from across the globe gather in Australia or New Zealand to meet their fellow technologists, share the latest ideas and innovations, and spend a week discussing and collaborating on open source projects. The conference is well known for the speakers and delegates depth of talent, and its focus on technical linux content. Possible topics: Virtualization, oVirt, KVM, libvirt, RDO, OpenStack, Foreman Date: January 12-15, 2015 Location: Auckland, New Zealand Website: http://lca2015.linux.org.au/ Call for Papers Deadline: July 13, 2014 Call for Papers URL: http://lca2015.linux.org.au/cfp Contact me for more information and assistance with presentations. -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

python-pthreading 0.1.3-2
by Douglas Schilling Landgraf 11 Jul '14

11 Jul '14

Hi, python-pthreading 0.1.3-2 is available to test. Please help giving karmas to achieve this version to stable branch as soon as possible. Changes included: - monkey_patch: Fail if it is too late to monkey-patch - Add the missing locked() interface F19: https://admin.fedoraproject.org/updates/python-pthreading-0.1.3-2.fc19 F20: https://admin.fedoraproject.org/updates/python-pthreading-0.1.3-2.fc20 EL6: https://admin.fedoraproject.org/updates/python-pthreading-0.1.3-2.el6 -- Cheers Douglas

2 1

[Documentation] Assistance Needed with User-Facing Documentation
by Brian Proffitt 10 Jul '14

10 Jul '14

All: The Red Hat ECS team has made a great effort to convert some of the more important downstream documentation to a MediaWiki format that we can post on oVirt.org as an official set of user- and admin-facing documentation. This is being done as a bootstrapping effort to get our upstream documentation up to date and take a big step towards making the upstream documentation the canonical source for documentation in the near future. Before that can happen, we need to get this RHEV-oriented information ported over to oVirt nomenclature and screenshots taken for oVirt and added to the documents as well. I have placed the three guides * Administration Guide[1] * User's Guide[2] * Installation Guide[3] on the oVirt site as unlinked pages. General wording has been changed from RHEV to oVirt, but not always. Each of these documents must be reviewed and completely adapted to oVirt 3.4 before they can be posted as official documentation. Specifically: * Review all text to ensure proper steps and descriptions for oVirt features and procedures * Review all text to remove downstream-specific text * Review all code for changes in package names on on-screen displays * Replace all downstream RHEV screenshots with upstream oVirt 3.4 screenshots (Max width: 1024px) I will be stepping through these documents to edit them in more detail under these guidelines, but help is most assuredly needed, in order to get this done in a timely manner. oVirt.org wiki users can visit these pages, review them, and add their changes. MediaWiki has limited version control, so it would be best to edit sections instead of entire documents, to minimize stepping on others' changes. Editing by section will also help us track the sections that have been edited, using the pages' histories. Thank you in advance for all of your help on this project... when finished, this will represent a significant improvement to oVirt's documentation, and make oVirt that much easier to use. Peace, Brian [1] http://www.ovirt.org/DraftAdministrationGuide [2] http://www.ovirt.org/DraftUserGuide [3] http://www.ovirt.org/DraftInstallationGuide -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

2 1

[ANN] oVirt 3.4.3 Release Candidate is now available
by Sandro Bonazzola 10 Jul '14

10 Jul '14

The oVirt development team is pleased to announce the availability of oVirt 3.4.3 Release Candidate as of Jul 10th 2014 for testing. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The new repository ovirt-3.4-rc has been updated for delivering this release, please refer to release notes [1] for instructions on how to enable the repository and for Installation / Upgrade instructions. A new oVirt Live ISO will be available soon[2]. Feel free to join us testing it [3]! [1] http://www.ovirt.org/OVirt_3.4.3_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.4-rc/iso/ [3] http://www.ovirt.org/Testing/oVirt_3.4.3_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Exception during VM recovery causes VMs not being properly recovered
by Vinzenz Feenstra 10 Jul '14

10 Jul '14

Hi, With the current master of VDSM after restarting VDSM (e.g. after upgrading) I noticed that the VMs were not properly initialized and in PAUSED state. Once checking the logs I found that the cause was here: Thread-13::INFO::2014-07-10 12:11:56,400::vm::2244::vm.Vm::(_startUnderlyingVm) vmId=`db614831-3b4b-4010-a989-f7a5ae6fa5d0`::Skipping errors on recovery Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2228, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 3312, in _run self._domDependentInit() File "/usr/share/vdsm/virt/vm.py", line 3204, in _domDependentInit self._syncVolumeChain(drive) File "/usr/share/vdsm/virt/vm.py", line 5686, in _syncVolumeChain volumes = self._driveGetActualVolumeChain(drive) File "/usr/share/vdsm/virt/vm.py", line 5665, in _driveGetActualVolumeChain sourceAttr = ('file', 'dev')[drive.blockDev] TypeError: tuple indices must be integers, not NoneType The reason here seems to be this: Thread-13::DEBUG::2014-07-10 12:11:56,393::vm::1349::vm.Vm::(blockDev) vmId=`db614831-3b4b-4010-a989-f7a5ae6fa5d0`::Unable to determine if the path '/rhev/data-center/00000002-0002-0002-0002-000000000002/41b6de4e-23da-481d-904d-9af24fc5f3ab/images/17206f99-38ab-45bc-ae9b-d36a66b00e4c/7b05de43-9d85-435f-8ae9-6ccde21548e4' is a block device Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 1346, in blockDev self._blockDev = utils.isBlockDevice(self.path) File "/usr/lib64/python2.6/site-packages/vdsm/utils.py", line 99, in isBlockDevice return stat.S_ISBLK(os.stat(path).st_mode) OSError: [Errno 2] No such file or directory: '/rhev/data-center/00000002-0002-0002-0002-000000000002/41b6de4e-23da-481d-904d-9af24fc5f3ab/images/17206f99-38ab-45bc-ae9b-d36a66b00e4c/7b05de43-9d85-435f-8ae9-6ccde21548e4' I am running the host on RHEL6.5 Note: I just rebooted the host and started a few more VMs again and when I restart VDSM I get the same errors again. -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R & D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

Re: [ovirt-devel] [VDSM][sampling] thread pool status and handling of stuck calls
by Saggi Mizrahi 10 Jul '14

10 Jul '14

The more I think about it the more it looks like it's purely a libvirt issue. As long as we can make calls that get stuck on D state we can't scale under stress. In any case, seems like having an interface like. libvirtConnectionPool.request(args, callback) Would be a better solution than a thread pool. It would queue up the request and call the callback once it's done. pseudo example: def collectStats(): def callback(resp): doStuff(resp) threading.Timer(4, collectStats) lcp.listAllDevices(callback) We could have the timer queue in a threadpool since it normally runs in the main thread but that is orthogonal to the libvirt connection issue. As for the thread pool itself. As long as it's more than one class it's too complicated. Things like: * Task Cancelling * Re-queuing (periodic operations) Shouldn't be part of the thread pool. Task should just be functions. If we need something with a state we could use the __call__() method to make an object look like a function. I also don't mind doing if hasattr(task, "run") or callable(task) to handle it using an "interface" Re-queuing could be done with the build it threading.Timer as in threading.Timer(4.5, threadpool.queue, args=(self,)) That way each operation is responsible for handing the details of rescheduling. Should we always wait X, should we wait X - timeItTookToCalculate. You could also do: threading.Timer(2, threadpool.queue, args=(self,)) threading.Timer(4, self.handleBeingLate) Which would handle not getting queued for a certain amount of time. Task cancelling can't be done in a generic manner. The most I think we could do is have threadpool.stop() check hassattr("stop", task) and call it. ----- Original Message ----- > From: "Francesco Romani" <fromani(a)redhat.com> > To: devel(a)ovirt.org > Sent: Friday, July 4, 2014 5:48:59 PM > Subject: [ovirt-devel] [VDSM][sampling] thread pool status and handling of stuck calls > > Hi, > > Nir has begun reviewing my draft patches about the thread pool and sampling > refactoring (thanks!), > and already suggested quite some improvements which I'd like to summarize > > Quick links to the ongoing discussion: > http://gerrit.ovirt.org/#/c/29191/8/lib/threadpool/worker.py,cm > http://gerrit.ovirt.org/#/c/29190/4/lib/threadpool/README.rst,cm > > Quick summary of the discussion on gerrit so far: > 1. extract the scheduling logic from the thread pool. Either add a separate > scheduler class > or let the sampling task reschedule themselves after a succesfull > completion. > In any way the concept of 'periodic task', and the added complexity, > isn't needed. > > 2. drop all the *queue classes I've added, thus making the package simpler. > They are no longer needed since we remove the concept of periodic task. > > 3. have per-task timeout, move the stuck task detection elsewhere, like in > the worker thread, ot > maybe better in the aforementioned scheduler. > If the scheduler finds that any task started in the former pass (or even > before!) > has not yet completed, there is no point in keeping this task alive and it > should be cancelled. > > 4. the sampling task (or maybe the scheduler) can be smarter and halting the > sample in presence of > not responding calls for a given VM, granted the VM reports its > 'health'/responsiveness. > > (Hopefully I haven't forgot anything big) > > In the draft currently published, I reluctantly added the *queue classes and > I agree the periodic > task implementation is messy, so I'll be very happy to drop them. > > However, a core question still holds: what to do in presence of the stuck > task? > > I think it is worth to discuss this topic on a medium friendlier than gerrit, > as it is the single > most important decision to make in the sampling refactoring. > > It all boils down to: > Should we just keep somewhere stuck threads and wait? Should we cancel stuck > tasks? > > A. Let's cancel the stuck tasks. > If we move toward a libvirt connection pool, and we give each worker thread > in the sampling pool > a separate libvirt connection, hopefully read-only, then we should be able to > cancel stuck task by > killing the worker's libvirt connection. We'll still need a (probably much > simpler) watchman/supervisor, > but no big deal here. > Libvirt allows to close a connection from a different thread. > I haven't actually tried to unstuck a blocked thread this way, but I have no > reason to believe it > will not work. > > B. Let's keep around blocked threads > The code as it is just leaves a blocked libvirt call and the worker thread > that carried it frozen. > The stuck worker thread can be replaced up to a cap of frozen threads. > In this worst case scenario, we end up with one (blocked!) thread per VM, as > it is today, and with > no sampling data. > > I believe that #A has some drawbacks which we risk to overlook, and on the > same time #B has some merits. > > Let me explain: > The hardest case is a call blocked in the kernel in D state. Libvirt has no > more room than VDSM > to unblock it; and libvirt itself *has* a pool of resources (threads in this > case) which can be depleted > by stuck calls. Actually, retrying to do a failed task may deplete their pool > even faster[1]. > > I'm not happy to just push this problem down the stack, as it looks to me > that we gain > very little by doing so. VDSM itself surely stays cleaner, but the > VDS/hypervisor hosts on the whole > improves just a bit: libvirt scales better, and that gives us some more room. > > On the other hand, by avoiding to reissue dangerous calls, I believe we make > better use of > the host resources in general. Actually, the point of keeping blocked thread > around is a side effect > of not reattempting blocked calls. Moreover, to keep the blocked thread > around has a significant > benefit: we can discover at the earliest moment when it is safe again to do > the blocked call, > because the blocked call itself returns and we can track this event! (and of > course drop the > now stale result). Otherwise, if we drop the connection, we'll lose this > event and we have no > more option that trying again and hoping for the best[2] > > I know the #B approach is not the cleanest, but I think it has slightly more > appeal, especially > on the libvirt depletion front. > > Thoughts and comments very welcome! > > +++ > > [1] They have extensions to management API to dinamically adjust their thread > pool and/or to cancel > tasks, but it is in the RHEL7.2 timeframe. > [2] A crazy idea would be to do something like > http://en.wikipedia.org/wiki/Exponential_backoff > which I'm not sure would be beneficial > > Bests and thanks, > > -- > Francesco Romani > RedHat Engineering Virtualization R & D > Phone: 8261328 > IRC: fromani > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel >

3 4

Docker containers for ovirt-engine
by Daniel Erez 10 Jul '14

10 Jul '14

Hi, I've created a couple of Docker images with a running ovirt-engine service and uploaded to the Docker registry [1]. Quite useful for quickly having a ready-to-use environment (tests, demos, etc) or to be used as a base image for building new Docker Images. Note that currently the container is not persistent by its nature, hence for saving changes, take use of the 'commit' functionality [2]. [1] https://registry.hub.docker.com/u/danielerez/ovirt-engine/ [2] https://docs.docker.com/reference/commandline/cli/#commit

1 0

Re: [ovirt-devel] [vdsm] virt-v2v integration feature
by Sandro Bonazzola 10 Jul '14

10 Jul '14

Il 09/07/2014 20:26, Arik Hadas ha scritto: > Hi All, > > The proposed feature will introduce a new process of import virtual machines from external systems using virt-v2v in oVirt. > I've created a wiki page that contains initial thoughts and design for it: > http://www.ovirt.org/Features/virt-v2v_Integration > > You are more than welcome to share your thoughts and insights. Please use http://www.ovirt.org/Feature_template as template > > Thanks, > Arik > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

3.6 release in bugzilla
by Michal Skrivanek 10 Jul '14

10 Jul '14

can someone please add 3.6 to oVirt release in bugzilla? Thanks, michal

1 1

oVirt 3.5 Test Day 1 Results - user defined Windows Sysprep file
by Vojtech Szocs 10 Jul '14

10 Jul '14

Hi, today I played with this feature [1]: - Win7 VM without custom Sysprep override in VM dialog - Win7 VM with custom Sysprep override in VM dialog - REST API call to check custom Sysprep override for VM [1] https://bugzilla.redhat.com/show_bug.cgi?id=1080002 It worked for me without any problems. Vojtech

2 1

[QE][ACTION NEEDED] oVirt 3.4.3 RC status
by Sandro Bonazzola 10 Jul '14

10 Jul '14

Hi, We're going to start composing oVirt 3.4.3 RC tomorrow *2014-07-10 08:00 UTC* from 3.4 branch. A 3.4.3 branch will be created immediately after using the same hash of the build. The bug tracker [1] shows no blocking bugs for the release Bug 1096312 - log spam in vdsm: guest agents not heartbeating has been proposed for backport from 3.6 target on the bug tracker [1] There are still 28 bugs [2] targeted to 3.4.3. Excluding node and documentation bugs we still have 9 bugs [3] targeted to 3.4.3. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.4.3 should not be released without them fixed. - Please update the target to any next release for bugs that won't be in 3.4.3: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please build packages before today *2014-07-09 15:00 UTC*. Community: - If you're testing oVirt 3.4 nightly snapshot, please add yourself to the test page [5] [1] bugzilla.redhat.com/1107968 [2] http://red.ht/1lBAw2R [3] http://red.ht/1ly9hfA [4] http://www.ovirt.org/OVirt_3.4.3_Release_Notes [5] http://www.ovirt.org/Testing/oVirt_3.4.3_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1

Update on ovirt-appliance and ovirt-node-iso for oVirt 3.5
by Fabian Deutsch 10 Jul '14

10 Jul '14

Hello, I just wanted to give a short update on the state of the ovirt-appliance and ovirt-node-iso for 3.5. ovirt-node is actually in a quite good shape. An iso is available with the ovirt-node-plugin-vdsm and -hosted-engine. Both based on ovirt-node from master, which will be branched off. The pain point is the automation. Ryan has actually gotten the Jenkins job back into place - good job! - so that at least the rpm packages are built. And could actually be included in the nighlies, Sandro. The automatic iso generation is still not working, due to several reasons (same as the last N months). The appliance generation is in a slightly better state than the ovirt-node-iso generation, but is still failing when it comes to automation. The automation is currently blocked by several issues which I tried to tackle together with David during the last week. The build automation of the appliance is actually getting most of my attention these days, as it is more likely to get the automation working. So we are not stable yet, but we are moving into the right direction. Greetings fabian

2 1

Command/Query infrastructure changes in 3.5
by Oved Ourfali 10 Jul '14

10 Jul '14

Hi As part of 3.5 we did some changes in the command/query infrastructure that change the way they should be written. These changes and some usage examples are described in http://www.ovirt.org/Wiki/Engine_Command_changes This wiki page was written by Ravi and Yair. Please go over those, as it is relevant for everyone writing a new engine command/query. Thank you, Oved

1 0

[URGENT][ACTION REQUIRED][vdsm] vdsm_3.4_create-rpms_merged failing on F19
by Sandro Bonazzola 09 Jul '14

09 Jul '14

Hi, VDSM from 3.4 branch is failing build on F19, see http://jenkins.ovirt.org/view/Publishers/job/vdsm_3.4_create-rpms_merged/la… Since 3.4.3 RC is scheduled for tomorrow, please fix this as soon as possible. Thanks -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[QE][ACTION NEEDED] oVirt 3.5.0 Second Beta status
by Sandro Bonazzola 09 Jul '14

09 Jul '14

Hi, We're going to compose oVirt 3.5.0 Second Beta on Mon *2014-07-21 08:00 UTC*. Maintainers: - Please be sure that 3.5 snapshot allow to create VMs before *2014-07-20 15:00 UTC* The bug tracker [1] shows the following proposed blockers to be reviewed: Bug ID Whiteboard Status Summary 1114994 infra NEW Cannot edit cluster after upgrade from version 3.4 to 3.5 because cpu type (Intel Haswell) does not match 1115044 infra POST Host stuck in "Unassinged" state when using jsonrpc and disconnection from pool failed 1115152 infra POST Cannot edit or create block storage doamin when using jsonrpc 1116009 infra POST sdk always raises a DisconnectedError trying to instantiate again after a previous failure 1060198 integration NEW [RFE] add support for Fedora 20 1073944 integration ASSIGNED Add log gathering for a new ovirt module (External scheduler) 1113974 integration POST Hostname validation during all-in-one setup 1113091 network POST VDSM trying to restore saved network rollback 1114057 storage NEW uploaded iso is not visible in the engine 1110305 virt POST BSOD - CLOCK_WATCHDOG_TIMEOUT_2 - Win 7SP1 guest, need to set hv_relaxed About Add log gathering for a new ovirt module (External scheduler), patch have been merged on upstream sos master branch. For Fedora >= 19 sos-3.1 package includes the fix. For EL 6 patches need to be backported to ovirt-log-collector. Feature freeze is now effective, and branch has been created. All new patches must be backported to 3.5 branch too. Features completed are marked in green on Features Status Table [2] There are still 422 bugs [3] targeted to 3.5.0. Excluding node and documentation bugs we still have 358 bugs [4] targeted to 3.5.0. Maintainers / Assignee: - Please remember to rebuild your packages before *2014-07-20 15:00* if needed, otherwise nightly snapshot will be taken. - Please be sure that 3.5 snapshot allow to create VMs before *2014-07-20 15:00 UTC* - If you find a blocker bug please remember to add it to the tracker [1] - Please start filling release notes, the page has been created here [5] - Please review and add test cases to oVirt 3.5 Second Test Day [6] Community: - Thanks for your participation in first test day! - You're welcome to join us testing next beta release and getting involved in oVirt Quality Assurance[7]! [1] http://bugzilla.redhat.com/1073943 [2] http://bit.ly/17qBn6F [3] http://red.ht/1pVEk7H [4] http://red.ht/1rLCJwF [5] http://www.ovirt.org/OVirt_3.5_Release_Notes [6] http://www.ovirt.org/OVirt_3.5_TestDay [7] http://www.ovirt.org/OVirt_Quality_Assurance Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

oVirt 3.5.0 release schedule updated
by Sandro Bonazzola 09 Jul '14

09 Jul '14

Here is the updated schedule for oVirt 3.5.0. These are tentative planning dates and may change: 2014-08-26 (Tue): oVirt 3.5.0 GA 2014-08-12 (Tue): oVirt 3.5 Third Test Day 2014-08-04 (Mon): oVirt 3.5.0 RC 2014-07-24 (Thu): oVirt 3.5 Second Test Day 2014-07-21 (Mon): oVirt 3.5.0 second beta Release management page has been updated accordingly: http://www.ovirt.org/OVirt_3.5_release-management oVirt Google Calendar has been updated accordingly: ICAL: https://www.google.com/calendar/ical/ppqtk46u9cglj7l987ruo2l0f8%40group.cal… XML: https://www.google.com/calendar/feeds/ppqtk46u9cglj7l987ruo2l0f8%40group.ca… HTML: https://www.google.com/calendar/embed?src=ppqtk46u9cglj7l987ruo2l0f8%40grou… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ACTION NEEDED] ovirt-engine-3.5 branch update
by Sandro Bonazzola 09 Jul '14

09 Jul '14

Hi, We're going to refresh ovirt-engine-3.5 branch tomorrow 2014-07-08 at 08:00 UTC. If you have any commits that are relevant only for 3.6 and not for 3.5, please don't merge them yet until we'll update the 3.5 stable branch. An email with the exact cutoff commits sha will be sent once the branch is updated. After branch update patch targeted to 3.5 will need to be cherry-picked to 3.5 branch too. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1

VDSM sync meeting minutes July 8th, 2014
by Dan Kenigsberg 09 Jul '14

09 Jul '14

We had relatively low attendence today and we did not discuss pending 3.5 issus deeply enough. If you have urgent 3.5 issue that needs fix/review, please chime in! live-merge: - we have 2 complex patches by Adam http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:li… jsonrpc - we have 3 pending patches by Piotr http://gerrit.ovirt.org/#/q/owner:%22Piotr+Kliczewski%22+status:open+projec… The most flaky of them adds lastClientIface element to getVdsCaps over jsonrpc. That element is used by Engine to deduce which network interface is used to carry management traffic, and build ovirtmgmt network on top of this. I suggest in Bug 1117303 - add a new getRoute() verb to introduce a new verb for this purpose, but until this happens in 3.6, we'd need a hack to expose it here. pthreading's superfluous wakeups - Nir's reported bug is still in effect, and his suggested patches awaits review. qos patches - Martin has plenty of patches. Most urgent is the log spam avoidence of http://gerrit.ovirt.org/#/c/29504/9/vdsm/virt/vm.py All should be reviewed by virt folks, due to the natural dependency. copious rebases - It is sometimes tempting to use a single topic branch for multiple patches that do not really depend on each other. The down size of this is that on every rebase, reviewers are swamped with emails; it is also less apparent that a certain patch can be merged without waiting for previous patches. So if you can break your serial branch to multiple branches with the same topic, you should probably do it. Hear you in a fortnight, Dan.

2 1

oVirt Node ISO for 3.5-pre
by Fabian Deutsch 08 Jul '14

08 Jul '14

Hey, here is another draft ISO which is intended to be used for testing with oVirt 3.5. This ISO also provides for the first time the oVirt Node Hosted Engine plugin. http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/ovirt-node-iso-3.5.0.ovirt… We've learned from the past: To circumvent some SELinux issues, please append enforcing=0 to the kernel commandline on boot. And please provide us your feedback, so we can take a look and address the problem. Greetings fabian

1 0