March 2016 - Devel - oVirt List Archives

Progress report on Vdsm Debian packaging
by Milan Zamazal 21 May '16

21 May '16

I made progress with Debian packaging of Vdsm. We have all the supporting packages (cpopen, ioprocess, mom, pthreading, safelease, sanlock) in Debian now. I took over maintenance of sanlock Debian package, updated it and made a lot of fixes, including preparing the previously unavailable python-sanlock package. As for Vdsm itself, the package can be installed now and Vdsm can be started. It doesn't work with Engine, which is no big surprise. We can't simply reinstall a Debian host from Engine, so we need to find some way how to initialize the host properly. And it's likely there are distribution specific pieces inside Vdsm and elsewhere. All the package sources, including not yet uploaded Vdsm package, are available on http://git.debian.org . How you can help: - Obviously, we need to make Vdsm hosts working, so any help in this area is welcome. - Reviewing and testing Vdsm Debian package (without actually using it) is also very helpful, I'm sure there are things to fix or improve. - There are some Lintian warnings in the packages, fixing them would be nice. - We should also review Debian patches in the packages, decide what should be changed upstream and report it. - You can help with anything else you consider useful.

4 6

Vdsm api package
by Nir Soffer 29 Apr '16

29 Apr '16

Hi all, In the Vdsm call, we discussed a way to expose vdsm errors to its clients (e.g, engine, hosted engine agent/setup). The idea is to have a vdsmapi package, holding: - errors.py - all public errors - events.py - all events sent by vdsm - client.py - library for communicating with vdsm - schema.py - the client will use this to autogenerate online help and validate messages - schema.yaml - we probably need several files (gluster, events, etc.) This will allow other projects talking with vdsm to do: from vdsmapi import client, errors ... try: client.list(vmId="xxxyyy") except errors.NoSuchVM: ... (this is a fake example, the real api may be different) Engine can build-require vdsmapi, and generate java module with the public errors from vdsmapi/errors.py module, instead of keeping this hardcoded in engine, and updating it every time vdsm adds new public error. Vdsm will use this package when building response to clients. Edi was concerned about sharing the errors module, so maybe we need a package: vdsmapi/ errors/ network.py virt.py storage.py gluster.py We can still expose all the errors via errors/__init__.py, so clients do not have to care about the area of the application the error come from. Thoughts? Nir

5 7

Maintenance Notification: *.ovirt.org Services Today at 18:00 IST (17:00 CET)
by Anton Marchukov 31 Mar '16

31 Mar '16

Hello All. Today at 18:00 IST (17:00 CET) we plan to do hardware upgrades at the datacenter where most of ovirt.org services are hosted. Although we plan to minimize the services downtime, it might still be needed. This does not affect gerrit.ovirt.org but may impact jenkins and other services. The maintenance window is scheduled to last for 2 hours. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

1 0

are there any ways to disable the log file?
by zhukaijie 31 Mar '16

31 Mar '16

"Since oVirt 3.5.0 (VDSM 4.16.0), VDSM does not enable the overly verbose libvirt debug logs automatically." from http://www.ovirt.org/develop/developer-guide/vdsm/log-files/. So my problem is. Each running VM has it's command line logged in /var/log/libvirt/qemu/${vmname}. And now I'd like to disable this log function, that is to say, not to record the QEMU command line of VM. So could oVirt or VDSM disable this qemu command line log file just like libvirt debug logs? Thank you.

2 1

[ANN] oVirt 3.6.5 First Release Candidate is now available for testing
by Sandro Bonazzola 31 Mar '16

31 Mar '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.5 for testing, as of March 31st, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release is also available with experimental support for: * Debian 8.3 Jessie This release candidate includes the following updated packages: - ovirt-engine - ovirt-engine-reports - ovirt-engine-sdk-python - ovirt-engine-sdk-java - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon [2]. * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.5/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.5/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [ovirt-devel] virt-v2v become zombie via python cpopen on error
by Michal Skrivanek 31 Mar '16

31 Mar '16

> On 30 Mar 2016, at 11:49, Richard W.M. Jones <rjones(a)redhat.com> wrote: > > On Wed, Mar 30, 2016 at 12:19:35PM +0300, Shahar Havivi wrote: >> Hi, >> >> We encounter a problem in VDSM project that virt-v2v become zombie task while >> importing vm from vmware. >> When virt-v2v is in 'copy disk' mode and we someone deletes the vm at vmware >> the process hang in read() method, >> I am pretty sure that its not virt-v2v problem because when I run it from the >> shell virt-v2v exit with an error, still maybe someone have an idea.... >> >> I wrote a small python script that encounter the problem: >> >> ---------------------------------------------------------------------------- >> from cpopen import CPopen >> >> env = {'LIBGUESTFS_BACKEND': 'direct'} >> cmd = ['/usr/bin/virt-v2v', '-ic', >> 'vpx://....', '-o', >> 'local', '-os', '/tmp', '-of', 'raw', '-oa', 'sparse', >> '--password-file', '/tmp/passwd', '--machine-readable', 'bbb'] >> p = CPopen(cmd, env=env) >> while p.returncode is None: >> c = p.stdout.read(1) >> print c >> ---------------------------------------------------------------------------- > > An actual zombie task? That would indicate that the parent process > (your Python program) wasn't doing a wait system call. > > I downloaded the cpopen-1.4 program, and it doesn't appear to call any > of the wait*(2) system calls anywhere, so that could be the problem. I suppose the cpopen parameters are not alright…I’m sure vdsm developers can help with that. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-p2v converts physical machines to virtual machines. Boot with a > live CD or over the network (PXE) and turn machines into KVM guests. > http://libguestfs.org/virt-v2v

4 4

oVirt Node Next builds are currently broken
by Fabian Deutsch 31 Mar '16

31 Mar '16

Hey, just a quick heads up that our oVirt Node Next jenkins builds are currently broken. Some of the symptoms are that the installation is failing and that no new updates are available. We are working on a solution. - fabian

1 0

Get Involved with oVirt project! Spring edition
by Sandro Bonazzola 30 Mar '16

30 Mar '16

Hi, Have you got some free time and do you want to get involved in oVirt project? Do you like the idea of having fresh disk images of recent distribution in oVirt Glance repository? You can help us by testing existing online images ensuring they works with cloud-init or creating one yourself and report your success to devel(a)ovirt.org. We'll be happy to upload the images once these are ready. Do you like Debian and do you have some programming or packaging skills? Help us getting Vdsm running on it! We work on inclusion of Vdsm into Debian. We need to test and fix Vdsm Debian packages to make them working before the next Debian freeze. You can find all current Debian work (Vdsm and related packages) in Debian git repositories [10]. You can follow the progress and participate on oVirt development mailing list [11]. Here are some bugs you can try to help with: 1159784 ovirt-engine Documentation NEW [RFE] Document when and where new features are available ... 1074301 ovirt-engine-cli RFEs NEW [RFE] ovirt-shell has no man page 772931 ovirt-engine-reports RFEs NEW [RFE] Reports should include the name of the oVirt engine 1120585 ovirt-image-uploader Documentation NEW update image uploader documentation 1120586 ovirt-iso-uploader Documentation NEW update iso uploader documentation 1120588 ovirt-log-collector Documentation NEW update log collector documentation 1237132 ovirt-engine Setup.Engine NEW [TEXT] New package listing of engine-setup when upgrading... 1115059 ovirt-engine General ASSIGNED Incomplete error message when adding VNIC profile to runn... Are you great at packaging software? Do you prefer a distribution which is currently unsupported by oVirt? Do you want to have packages included in your preferred distribution? Help getting oVirt ported there! Fedora: http://lists.ovirt.org/pipermail/devel/2015-September/011426.html CentOS: https://wiki.centos.org/SpecialInterestGroup/Virtualization Gentoo: https://wiki.gentoo.org/wiki/OVirt (GSoC: https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas ) Debian: http://www.ovirt.org/develop/release-management/features/debian-support-for… Archlinux: http://www.ovirt.org/develop/developer-guide/arch-linux/ OpenSUSE: https://build.opensuse.org/project/show/Virtualization:oVirt Do you love "DevOps?", you count stable builds in jenkins ci while trying to fall a sleep? Then oVirt infra team is looking for you!, join the infra team and dive in to do the newest and coolest devops tools today! Here are some of our open tasks you can help with: https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?rapidView=6 You can also help us by sharing how you use oVirt in your DevOps environment (please use [DevOps] in the subject). You can check out more docs on the DevOps side of oVirt in [12][13] You don't have programming skills, not enough time for DevOps but you want still to contribute? Here are some bugs you can take care of, also without writing a line of code: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… Do you prefer to test things? We have some test cases[5] you can try using nightly snapshots[6]. Do you want to contribute test cases? Most of the features[7] included in oVirt are missing a test case, you're welcome to contribute one! Do you want to contribute artworks? oVirt Live backgrounds and covers, release banners, stickers, .... Take a look at Fedora Artworks[9] as an example of what you can do Is this the first time you try to contribute to oVirt project? You can start from here [1][2]! You don't know gerrit very well? You can find some more docs here [3]. Any other question about development? Feel free to ask on devel(a)ovirt.org or on irc channel[4]. You don't really have time / skills for any development / documentation / testing related task? Spread the word[8]! Let us know you're getting involved, present yourself and tell us what you're going to do, you'll be welcome! [1] http://www.ovirt.org/develop/ [2] http://www.ovirt.org/develop/dev-process/working-with-gerrit/ [3] https://gerrit-review.googlesource.com/Documentation [4] http://www.ovirt.org/community/ [5] http://www.ovirt.org/develop/infra/testing/ [6] http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/ [7] http://www.ovirt.org/develop/release-management/features/ [8] http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-cove… [9] https://fedoraproject.org/wiki/Artwork#Resources [10] http://git.debian.org [11] http://lists.ovirt.org/mailman/listinfo/devel [12] http://ovirt-infra-docs.readthedocs.org/en/latest/ [13] http://www.ovirt.org/develop/infra/infrastructure-documentation/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

ovirt 3.5 to 3.6 upgrade
by Paul Dyer 30 Mar '16

30 Mar '16

Hi, after upgrade to ovirt 3.6, the ovirt-release35 repo remains on the manager machine (non-hosted engine). There is also a list of rpms from the 3.5 repo. Should the 3.5 repo be removed? What about the rpms from the 3.5 repo? Should they stay or go? Here is a list of 3.5 repo rpms still installed: # yum list installed |grep ovirt-3.5 ovirt-engine-jboss-as.x86_64 7.1.1-1.el6 @ovirt-3.5 patternfly1.noarch 1.3.0-1.el6 @ovirt-3.5-patternfly1-noarch-epel python-daemon.noarch 1.5.2-1.el6 @ovirt-3.5-epel python-kitchen.noarch 1.1.1-1.el6 @ovirt-3.5-epel python-lockfile.noarch 0.8-3.el6 @ovirt-3.5-epel python-ply.noarch 3.4-4.el6 @ovirt-3.5-epel python-websockify.noarch 0.6.0-3.el6 @ovirt-3.5-epel xalan-j2.noarch 2.7.1-8.jbossorg_1.jpp6 @ovirt-3.5-jpackage-6.0-generic Thanks, Paul -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

2 1

[vdsm] new internal stable modules + proposal
by Francesco Romani 30 Mar '16

30 Mar '16

Hi, in the last Vdsm developer call we agreed to promote a few modules in the common repository. The common repository provides the additional guarantees over regular modules in lib/vdsm/ - stable API - (thus) safe to use across verticals the planned moves are: lib/vdsm/schedule.py -> lib/vdsm/common/schedule.py lib/vdsm/periodic.py -> lib/vdsm/common/periodic.py lib/vdsm/virt/api.py -> lib/vdsm/common/api.py Question is if those modules should go under common/ or under another subdirectory, maybe infra? Lastly, i have a proposal about better handling of those modules. First, the mere fact a module is placed under lib/vdsm/common provides the extra guarantees I mentioned. But should we added more annotations? for example something like __API__ = {} near the top of the module if this attribute exist, then the module is safe to use across verticals, has stable API and so forth (this is _in addition_ to the common/ package, not as replacement). Like: __API__ = { "introduced-in": "4.14.0", "deprecated-from": "4.18.0", "removed-at": "4.20.0", "contact": "fromani(a)redhat.com" } We could refine further this concept if we like it. The idea is to be lightweight as possible while carrying all the information we need. Comments welcome as usual bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

3 7

[ATN] [ACTION REQUIRED] Tweaking engine CI flow
by Roy Golan 30 Mar '16

30 Mar '16

Hi all, Eyal and I sat together to analyse and tweak the engine CI and this is what we came up with: - dao test excludes updated - exclude dal/src/main/bundles from invoking dao tests A trivial update of validation messages without any db change would trigger dao test without any need. This is one less job run for lots of patches. This change is effective now. - Spare CI re-run on trivial rebases Gerrit trigger supports suppressing itself if the change to the tree was trivial. Most of the waste of resources(time and IO :) ) is around rebasing a change and waiting for CI to rerun. if Change1 is ci+1 and Change2 is ci+1 the chances that they will break CI together is very small and taking that risk is most probably worth it due to the huge resources waste This change isn't effective yet - *Please reply here* if you agree or not to make this change available. All of this is 'master' - 3.6 will follow if we will agree on activating that change. Thanks, Roy

4 6

[VDSM] Vdsm build requires now python 3 on EL7
by Nir Soffer 30 Mar '16

30 Mar '16

Hi all, Since commit f247a0cff310 (el7: require newly available python34-nose), building vdsm requires Python 3 on EL7. Unfortunately, it seems that ovirt-release-master that should add all the dependencies needed for vdsm does is not configured properly, so building vdsm will fail. I heard that installing epel7 repo fixes this issue. Cheers, Nir [1] https://github.com/oVirt/vdsm/commit/f247a0cff310dbbf62b07e779adbe9973734a9…

6 6

Failing to run ovirt-system-tests using lago due to missing rpms
by Eyal Edri 29 Mar '16

29 Mar '16

Hi, Anyone encountered these errors when running 3.6 basic suite on RHEL 7.2? * STDERR Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-iso-uploader >= 3.6.0 Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: slf4j >= 1.7.0 Available: slf4j-1.5.8-8.el6.noarch (base) slf4j = 1.5.8-8.el6 Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-host-deploy-java >= 1.4.0 Error: Package: ovirt-engine-vmconsole-proxy-helper-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-vmconsole-proxy Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-image-uploader >= 3.6.0 Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: ebay-cors-filter Error: Package: ovirt-engine-setup-base-3.6.4.1-1.el6.noarch (localsync) Requires: otopi >= 1.4.0 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-engine-extension-aaa-jdbc Error: Package: ovirt-engine-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-engine-wildfly >= 8.2.1 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-common-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-setup-lib Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: vdsm-jsonrpc-java >= 1.1.8 Error: Package: ovirt-engine-backend-3.6.4.1-1.el6.noarch (localsync) Requires: ovirt-engine-extension-aaa-jdbc # [Thread-3] Deploy VM lago_basic_suite_3_6_engine: ERROR (in 0:01:59) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 46, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 472, in _deploy_host host.name(), RuntimeError: /home/eedri/lago/ovirt-system-tests/basic_suite_3.6/deploy-scripts/setup_engine.sh failed with status 1 on lago_basic_suite_3_6_engine @ Deploy oVirt environment: ERROR (in 0:01:59) Error occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 248, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 180, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 501, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 512, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 174, in do_deploy prefix.deploy() File "/usr/lib/python2.7/site-packages/lago/log_utils.py", line 598, in wrapper func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 52, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 480, in deploy self._deploy_host, self.virt_env.get_vms().values() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 88, in invoke_in_parallel vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 46, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/ovirtlago/__init__.py", line 472, in _deploy_host host.name(), RuntimeError: /home/eedri/lago/ovirt-system-tests/basic_suite_3.6/deploy-scripts/setup_engine.sh failed with status 1 on lago_basic_suite_3_6_engine -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Engine 3.6.5 has been branched out
by Tal Nisan 29 Mar '16

29 Mar '16

A new branch ovirt-engine-3.6.5 has been branched out from the ovirt-engine-3.6 branch please note that: - 3.6.5 patches will now have to be backported to the new branch as well as the 3.6 branch - 3.6.6 patches should only be merged to the 3.6 branch only All 3.6.6 patches that were backported to the 3.6 and were pending the branching out can now be merged, please rebase and verify again.

2 1

Hello and a question about QEMU log
by zhukaijie 29 Mar '16

29 Mar '16

Hello, Each running VM has it's command line logged in /var/log/libvirt/qemu/${vmname}. And now I'd like to disable this log function, that is to say, not to record the QEMU command line of VM. Could you please tell me will can I configure it? Best wishes.

2 1

[ANN] oVirt 3.6.4 Final Release is now available
by Sandro Bonazzola 29 Mar '16

29 Mar '16

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.4. This latest community release includes numerous bug fixes for - ovirt-engine - vdsm - ovirt-hosted-engine-setup - ovirt-hosted-engine-ha oVirt is an open-source, openly-governed enterprise virtualization management application, developed by a global community. You can use the oVirt management interface (oVirt Engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. If you are familiar with VMware products, oVirt is conceptually similar to vSphere. oVirt serves as the bedrock for Red Hat's Enterprise Virtualization product, and it is the "upstream" project where new features are developed prior to their inclusion in Red Hat's supported product offering. Additional Resources: * Read more about the oVirt 3.6.4 release highlights: http://www.ovirt.org/release/3.6.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

HEADS UP: otopi - enforce priority and other changes
by Yedidyah Bar David 29 Mar '16

29 Mar '16

Hi all, In two days or so, we are going to merge [1]. Without it, if you have events (functions with a '@plugin.event' decoration) that due to before=/after= requirements, otopi could not comply with their priority=, it will continue, ignoring this and only writing a message to the console if you set OTOPI_DEBUG=1. With this change, it will fail. Under normal circumstances, you'll see nothing in the console or the log, just an exit code of 1. If you set an environment variable OTOPI_DEBUG=1, it will emit a "RuntimeError: Priorities were reversed during buildSequence" error, see examples below. You can restore the existing behavior by setting another env var OTOPI_ALLOW_PRIORITY_OVERRIDE=1 . Soon thereafter, we are going to merge [2]. This will replace the algorithm that is used to decide what to run when. In principle, after [1] is merged, they should be compatible. However, the new algorithm does not allow overriding priorities. To revert to the old algorithm, you can set env var OTOPI_ALLOW_LEGACY_BUILDSEQ=1 . The old algorithm (and this option) is intended to be removed eventually, probably after oVirt 4.0 is released. Patches to make engine-setup (engine+dwh+reports) and host-deploy compatible with the new behavior were already merged to master branches. Still we most likely forgot some other tools/flows/etc., so if you encounter such failures please open a bug against the relevant tool. On a more positive (?) side, we also recently added a new package to master, called otopi-debug-plugins. It currently includes two plugins, which are not enabled by default. One of them allows you to get a prompt 'Press Enter to continue' on [ERROR], so it's easier to have a look at the system before the tool might try to rollback or something, the other allows you to enforce a failure at a certain stage, which might be useful to debug/verify failures and especially rollbacks. More details about these are in a new README file [3]. [1] https://gerrit.ovirt.org/55329 [2] https://gerrit.ovirt.org/28775 [3] https://gerrit.ovirt.org/gitweb?p=otopi.git;a=blob;f=README.debug-plugins Examples: 1. # ovirt-host-deploy # echo $? 1 2. # OTOPI_DEBUG=1 ovirt-host-deploy 2>&1 | tail Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7f9827c9fe10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x1032990>> with priority 5000 Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 151, in execute self.context.buildSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 400, in buildSequence raise RuntimeError(msg) RuntimeError: Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7f9827c9fe10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x1032990>> with priority 5000 ('FATAL Internal error (main): Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7f9827c9fe10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x1032990>> with priority 5000',) 3. # OTOPI_DEBUG=1 OTOPI_ALLOW_PRIORITY_OVERRIDE=1 ovirt-host-deploy ... Priorities were reversed during buildSequence: method <bound method ?._init of <otopi.plugins.otopi.core.log.Plugin object at 0x7fbe17f51e10>> with priority 2000 appears after method <bound method ?._preinit of <otopi.plugins.ovirt_host_deploy.core.misc.Plugin object at 0x107f8d0>> with priority 5000 [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor. Are you sure you want to continue? (yes/no) And with [2]: 4. # OTOPI_DEBUG=1 ovirt-host-deploy ... _toposortBuildSequence failed: Cyclic dependencies found ('FATAL Internal error (main): Cyclic dependencies found',) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 151, in execute self.context.buildSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 665, in buildSequence self._sequence = self._toposortBuildSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 624, in _toposortBuildSequence raise RuntimeError(_('Cyclic dependencies found')) RuntimeError: Cyclic dependencies found 5. # OTOPI_DEBUG=1 OTOPI_ALLOW_PRIORITY_OVERRIDE=1 ovirt-host-deploy (fails the same way as (4.)) 6. # OTOPI_ALLOW_LEGACY_BUILDSEQ=1 OTOPI_DEBUG=1 ovirt-host-deploy (fails similarly to (2.) - you'll see more-or-less outputs of (4.) then (2.) combined) 7. # OTOPI_ALLOW_LEGACY_BUILDSEQ=1 OTOPI_DEBUG=1 OTOPI_ALLOW_PRIORITY_OVERRIDE=1 ovirt-host-deploy (succeeds like (3.), but with part of the output of (4.) before that) Best regards, -- Didi

1 0

Workaround for Gerrit 'Internal Server Error' after deleting draft
by Tomer Saban 28 Mar '16

28 Mar '16

Hi, I came across a bug in Gerrit when trying to delete a draft. It seems that it ruins the patchset(Gerrit doens't set the new last revision properly). So, in order to fix this issue we need to reset the last revision. In order, to do that you need to find the last revision after deleting the draft(Let's assume it's 23). Once, you have that you need to number of the patch in gerrit. For example, the number in: https://gerrit.ovirt.org/#/c/51636/ is 51636. Last, You need to run the following line from the shell: ssh gerrit.ovirt.org gerrit review --rebase 51636,23 FYI, Tomer

2 1

VDSM Network Tests
by Paul Maidment 27 Mar '16

27 Mar '16

I notice that on my build of VDSM, the network test. functional/networkTests.py:testDhcpReplaceNicWithBridge Fails on the assertion that the address will not change (the dnsmasq dhcp server returns a new address for the same mac) Can anyone reproduce this?

2 1

ovirtm Hosts reinstall button
by Paul Dyer 27 Mar '16

27 Mar '16

Hi, can anyone explain what this button does? I have looked in the documentation but have found no reference to it. Will reinstall only install packages and setting for the host, and leave cluster/storage/networks alone? I have a cluster version 3.6.2 that will not Activate the host because the message "Host .. is compatible with versions (3.0,3.1,3.2,3.3,3.4,3.5) and cannot join Cluster...". The host was part of a 3.5 cluster until the upgrade to 3.6.2. Thanks a million, Paul -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

5 10

Heads up: Engine 3.6.5 branching out next week
by Tal Nisan 24 Mar '16

24 Mar '16

Hey everyone, Around mid next week Engine 3.6.5 will be branched out from the ovirt-engine-3.6 branch. This gives the teams a few days of grace to be able to close 3.6.5 issues with a single backport so now will be a good time to go over the patches in the branch and review/verify so they can get merged. Right after the branching out all 3.6.5 patches will have to be backported both to the 3.6 branch and the 3.6.5 branch whereas 3.6.6 patches will be backported to the 3.6 branch only. Another heads up on a related issue: there are currently 38 open patches in the 3.6 branch some of which date as far as January. As this clutters my everyday work on the branch, right after branching out I'm going to clear out stale patches and I'm going to keep abandoning patches in the stable branch that are stale for too long. Bear in mind that in 99.9% of the cases there is no reason for a patch to be open on the stable branch for more that 2 weeks after it's merged on master.

1 0

Reviews needed for ovirt-system-tests
by Eyal Edri 24 Mar '16

24 Mar '16

Hi, There has been progress with fixing a few issues on ovirt-system-tests and patches were submitted [1]. We would like to merge them ASAP so the ovirt tests for 3.6 and 4.0 can get one more step closer to working and being stable both for developers and for CI. Can you please review the pending patches so we can merge them TODAY? [1] https://gerrit.ovirt.org/#/c/53534 - needs a review https://gerrit.ovirt.org/#/c/53518/ - +1, probably can be merged. https://gerrit.ovirt.org/#/c/54738/ - +1, can get merged. https://gerrit.ovirt.org/#/c/54721/ - +1, can get merged https://gerrit.ovirt.org/#/c/51566/4 - +1, can get merged https://gerrit.ovirt.org/#/c/52681/ - not sure about this one -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[vdsm][virt] what's new in virt (20151215)
by Francesco Romani 23 Mar '16

23 Mar '16

Hi all, I'm happy to start a weekly summary of what's going on on virt's world (VDSM edition). General topics * I've got some mixed feedback about my Vm-on-a-diet effort. I still believe that fat trimming is a worthwhile goal per se, but I'm willing to adapt the strategy responding to the comments, so we will focus on virt-specific topics. * As consequence of the above, I'm focusing on the last bits of device fixing, which involves - fixing all device to update themselves from libvirt XML after domain boot, instead using all the getUnderyling* methods - switch the devices related code to use Etree instead of minidom. This will involve changes to the domain_descriptor. I estimate this task will still trim ~600 lines out of vm.py, so it still somehow gets some size trimming done, albeit not intensive as planned. This is a complex topic, will post plan and ideas on a separate mail * Finally, some series are still worth pushing forward, see below. Patches in need of attention * topic branches - mpolednik started a much needed cleanup and fixing of fake_qemu and fake_kvm code, with the ultimate goal to move all the remaining bits into the faqemu hook, and to make it useful on ppc64. Lots of refactoring is needed to support this change, and that produced https://gerrit.ovirt.org/#/q/topic:cpuinfo - we want to improve the reporting in case of migratio aborted. The ultimate goal is to let Engine (thus the User) know why a migration failed. To export this information, however, we need some cleanup before. Hence: https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:m… - last and less urgent: here's some cleanup about existing getUnderlying* methods of Vm class, preparing the last step of the big vmdevices split. I believe this is useful anyway https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:v… * single patches - https://gerrit.ovirt.org/#/c/46846 this is the first of a series aiming to improve migration support in 4.0. Probably worth merging all together, even though this one seems ready for broader review to me. - https://gerrit.ovirt.org/#/c/49173/ Notified just to raise awareness, still working on ensuring backward compatibility and smooth upgrade - https://gerrit.ovirt.org/#/c/48672 v2v xen support - https://gerrit.ovirt.org/#/c/49951/ OVA support improvements. Worth a look, but note that we are working toward a split of this big patch - https://gerrit.ovirt.org/#/c/49636 V2V refactoring, also almost ready - https://gerrit.ovirt.org/#/c/49570/ still in the context of migration enhancements. We want to throttle incoming migrations, to do so we want to use a sempahore which needs to be held by the creation thread until VM is created. This helper makes this possible, using an uniform interface for both this case and the common, simpler case. That's all for now, as usual, reviews welcome! :) -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

4 14

removing old ovirt-engine unit tests jobs
by Eyal Edri 23 Mar '16

23 Mar '16

Hi, I'd like to remove the following jobs from CI [1], since they are not adding any benefit over existing logic provided by the standard ci jobs (i.e checkstyle & unit tests already run there). Pros from removing: --------------------------- - reduce time needed to wait on patch verification - reduce load on jenkins - reduce possibility of false positive errors (since they are not running on mock) - reduce load on jenkins in general & maintainability Possible cons: ------------------ - output on unit tests failure might be not nice as existing jobs, but will still provide the relevant error. there is an open ticket on adding support for UI on STD ci, so it will there in the future. If I won't get any rejections or justified concerns on this thread, I will start with disabling them and if all goes well removing them after 1 week. [1] ovirt-engine_3.6_style_gerrit ovirt-engine_master_style_gerrit ovirt-engine_3.6_unit-tests_gerrit ovirt-engine_3.6_unit-tests_merged ovirt-engine_master_unit-tests_gerrit ovirt-engine_master_unit-tests_merged -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Maintenance Notification: gerrit.ovirt.org Upgrade Today at 15:00 IST (14:00 CET) - Tentative Time
by Anton Marchukov 23 Mar '16

23 Mar '16

Hello All. We plan to upgrade gerrit to a new version today starting tentatively at 15:00 IST (14:00 CET). However it might be postponed to a later time if we did not manage to get snapshot by that time. During the upgrade the gerrit will not be available. This should not take longer than few hours and I will keep you updated on the progress. Please note that we plan to upgrade to the latest major version 2.12.2. First of all we hope that stability issues that we face are solved there. Besides that consecutive upgrade was required to be able to use online re-indexing limiting downtime. The version has the following core features: - Significant online edit UI improvements - New change submission workflows: Submit Whole Topic and Submitted Together. - Support for GPG Keys and signed pushes. Please let us know if there is anything critical that is preventing us from this upgrade. You can follow up release notes at [1], [2] and [3]. [1] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [2] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [3] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… Anton -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

3 8

[ANN] oVirt 3.6.4 Second Release Candidate is now available for testing
by Sandro Bonazzola 22 Mar '16

22 Mar '16

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6.4 for testing, as of March 22nd, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release is also available with experimental support for: * Debian 8.3 Jessie This release candidate includes the following updated packages: - ovirt-engine - ovirt-hosted-engine-ha See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon [2]. * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.4/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

ovirt-site: Failing build on pull request
by Edward Haas 22 Mar '16

22 Mar '16

Hello, Could anyone give me a hint on why this build fails and how to resolve it? https://travis-ci.org/oVirt/ovirt-site/builds/117649678 Pull request: https://github.com/oVirt/ovirt-site/pull/102 Thanks, Edy.

1 0

oVirt Integration Development Team weekly status - 2016-03-21
by Sandro Bonazzola 21 Mar '16

21 Mar '16

- *oVirt Integration Development Team weekly status - 2016-03-21* - - oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 4.0 - master is now stable enough to be tested - working with Node team to streamline NGN build in jenkins - working with Node team supporting NGN cockpit plugins - working with Infra team on packaging new dashboard nodejs based packages - working with Storage team packaging ovirt image uploader daemon - working on migration path from el6 3.6 to el7 4.0 - ovirt-log-collector works again with Fedora on master - 3.6: - Closed 3.6.4 pending bugs - Released oVirt 3.6.4 RC1 - Announce: http://lists.ovirt.org/pipermail/announce/2016-March/000238.html - Release notes: http://www.ovirt.org/release/3.6.4/ - Fixing 3.6.5 bugs - Preparing to release 3.6.4 RC2 - Infra: - Fixed guest agent jenkins jobs - Fixed repoclosure issues on 3.6 snapshot - CentOS Virt SIG: - Next meeting scheduled on Tue 22nd 16:00 CET - LINK: Roadmap and packages list: http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap - LINK: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ *Team updates* - Didi - Worked on several bugs/changes, mainly in otopi - Ido: - getting familiar with Hosted engine installation - getting familiar with Lago installation - Lev: - working on few bugs, mostly on ovirt-live - Rafael: - Working to split engine-backup from ovirt-engine-tools package - Working on configuration query tool for otopi - Worked on 3.6.4 RC1 release - Sandro: - Working with Rafael and Simone on 3.6.4 RC1 release - Working with Fabian on ovirt-release for Next Generation Node - Finishing presentation for Incotro DevOps @ Bologna - Simone: - Worked on hosted-engine compatibility issues with python SDK on master - Adding an additional CLI option to let the user pass a custom vm.conf on hosted-engine - Let user add a 3.6 hosted-engine host on a system that was started with 3.4 by scanning all the volume uuids on disk (at 3.4 time they wasn't in the answerfile) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [ovirt-devel] ovirt-engine_master_upgrade-db-from-3.6_el7_created test fails with fatal error
by Maor Lipchuk 21 Mar '16

21 Mar '16

Hi all, I'm getting the following error (see [1]) every time when I send a DB patch. any idea what seems to be wrong? [1] fatal: ambiguous argument 'origin/ovirt-engine-3.6': unknown revision or path not in the working tree. see http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-db-from-3.6_el7_cr… Regards, Maor

2 1

Access to memory snapshots?
by Matt Mossholder 17 Mar '16

17 Mar '16

Hi everyone! I am working on developing a plugin for the cuckoo sandbox ( http://cuckoosandbox.org) that will allow users to select oVirt as a virtualiztion solution. I have it working, for the most part, but one area where I need some guidance is in retrieving memory images. I know that when you take a snapshot, you can request that the memory be stored as well. My issue is that I don't see a way to retrieve the memory, so that it can be feed into analysis tools like Volatility ( http://www.volatilityfoundation.org/) Does anyone have any pointers for me? Thanks! --Matt

4 3

Coming (Very) Soon - New ovirt.org Website & Deprecated Wiki
by Mikey Ariel 16 Mar '16

16 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 In the past months we've been working on upgrading the oVirt project infrastructure, to better support the community contributions. One of the main platforms for our user documentation, release management content, and community content has been the MediaWiki site that you all know as ovirt.org. Most of us are familiar with the wiki site format, with all its advantages and disadvantages. After several years of serving the community, I'm happy to announce that we are very near to completing a full upgrade of the website infrastructure from a wiki site to a static site, source-controlled on GitHub and authored in Markdown. This email is the pre-launch announcement, as we are reaching the final stages of the migration, and there are a few actions that might affect your work on website content in the meantime. Why migrate the website ======================= As mentioned, wiki sites provide an open and flexible content editing platform. Unfortunately, as the site grows the content becomes quite difficult to manage and curate, resulting in lots of obsolete, outdated, and incorrect information. By moving to a source-controlled repository and implementing GitHub's contribution workflow, we strive to ease the work of maintaining an up-to-date content site, employ a peer-review process for changes, and standardize the authoring markup language to lower the contribution barrier. The Middleman framework (Ruby-based static site generator) was chosen based on observing successful implementation of other open-source community websites, such as OpenStack RDO, Project Atomic, and Gluster. What we did so far ================== When we started the migration, our Web design team exported all of the wiki content from the old website and converted it to MD files. They also set up the website config flow, auto-deploy, and upgraded the look-and-feel of the website. We then initiated a content review effort as well as a UX review for the new website in a smaller forum, which caught most of the critical issues with the new website and helped us get the new format to a place where we can release the website in a near-GA/public-beta format. Yesterday (Wednesday Feb 17) we exported the website one more time and currently we're running a diff on all the files that changed since the initial export was done, to make sure we grab all the updates and the latest content before we launch the new website. What is about to happen ======================= Today we are initiating a **wiki freeze**, which means the old MediaWiki site will become read-only. This is to ensure that all of our diff scripts reflect the most current state of the content on the website, and that we don't lose any content in the transition. Barring any unexpected blockers, we will port the ovirt.org domain to point to the new website and open the new website for contributions on **Monday February 22** or earlier. What do you need to do right now ================================ If you have any wiki pages that you're actively editing, please don't save them to the old MediaWiki site, and hold onto your pending changes until we send the happy launch email. We will also include instructions on how to contribute/edit/add content to the new website, but in general the workflow will be aligned with the standard GitHub best practices (clone-edit-commit-pullrequest), so you can utilize all of the git commands that you already know or work directly within the GitHub web editor. I'd like to thank all of the people who were involved with this migration so far, ovirt.org is a big website with lots of content and it was no small task to upgrade it. Please feel free to ping me on- or off-list if you have any questions about the next steps, and expect a happy launch email soon! Cheers, Mikey - -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWxa5AAAoJEHYPPTOszxHow10H/jeuhzMrUrPsCBedLg7OKnNh jdKDujT/aCyA4LgnRHnVBEASunShmVaOJrMdU4r0PZbdkX1Mf5/SvCEFGKY14qAg m/5CnDhlwbp5rqo09VOGLMg20CaMtpUoE1LpKE/epGYEKSBr2JIAA+HAsYa1OEyS 9oHDDx+ZIbfHNlygW1KpW6dsuZRscTbfy4kk8rY83YdJGyQiQN+ulsjT/c2N8ArR WylohBE2OcC7+nzf7AejKJ94loWxnVhO4qWbNWAH00LArG89yFWBBSlMK6ocJUED P4k2IzgG+75eTiCZAAw5/Vaqx0YVU7hScSmBqOPQu/wo4e2t11AR7A8D7Cn+vpU= =XWEH -----END PGP SIGNATURE-----

6 6

[ANN] oVirt 3.6.4 First Release Candidate is now available for testing
by Sandro Bonazzola 16 Mar '16

16 Mar '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.4 for testing, as of March 16th, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release is also available with experimental support for: * Debian 8.3 Jessie This release candidate includes the following updated packages: - ovirt-engine - vdsm - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available [2]. * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.4/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Welcome: New ovirt.org website!
by Mikey Ariel 15 Mar '16

15 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Following yesterday's pre-launch email[1], I'm happy to announce that the new ovirt.org[2] website is now live in **public beta** and available for community review. All the information in this email is also available in the first blog post of our shiny new oVirt blog[3]. Read on for information about new features, known issues, and a call for reviews. The old MediaWiki site is still available in read-only[4], and will be taken offline on **March 1, 2016**. This is to ensure that you can compare pages and review migrated content. What's New ========== The new Website is full of improvements and enhancements, check out these highlights: * Source content is now formatted in Markdown instead of MediaWiki. This means that you can create and edit documentation, blog posts, and feature pages with the same Markdown syntax you know. * The Website is deployed with Middleman and stored on GitHub. This means that you can make changes to content with the same GitHub contribution workflow that you know (fork, clone, edit, commit, submit pull request). We even have an "Edit this page on GitHub" link at the bottom of every page! * New layout and design, from breadcrumbs to sidebards and an upgraded landing page. (This is still WIP, please see known issues.) * Automatic redirects from the old MediaWiki site. This means that if the wiki page exists in the new website, previously-released URLs will redirect to that page. If the page was removed, the Search page will open with the page title auto-filled in the search box. * Hierarchical content structure. This means that instead of flat Wiki-style files, the deployed Website reflects an organized source repo with content sorted into directories and sub-directories. * Official oVirt blog! Our new blog welcomes contributions. This means that if you solved a problem with oVirt, want to share your oVirt story, or describe a cool integration, you can submit a pull request with a blog post and we will provide editorial reviews and help publish your posts. * Standardized contribution process. The GitHub repo now includes a README.md[5] file that you can use to learn about how to add and edit content on the website. We welcome pull requests! Known Issues ============ Despite our best efforts, there are still a few kinks with the new website that you should be aware of: * Attempting to navigate to ovirt.org (without www.) leads to a redirect loop. We have a ticket open with OpenShift, our hosting service to fix this. * Only http is available. We also have a ticket with OpenShift to add SSL and enable https. * Home page and Download page are still being upgraded by our UX experts, expect some cool new changes soon! * Feature pages look-and-feel is still under construction. You can still edit and push feature pages as usual. What's Next =========== Even though the Website is live, the work is hardly over. We'd like to ask for your help in: * Reviewing content for anything obsolete or outdated (each page in the new website includes a header toolbar with metadata from the original wiki page for your convenience) * Submitting blog posts or any other content that you wish to share with the oVirt community * Reporting bugs and proposing enhancements, for example broken links or missing pages We hope you will enjoy the new oVirt Website, looking forward to your feedback and contributions! [1] http://lists.ovirt.org/pipermail/devel/2016-February/012372.html [2] http://www.ovirt.org/ [3] http://www.ovirt.org/blog/2016/02/welcome-to-new-ovirt-site/ [4] http://old.ovirt.org/Home [5] https://github.com/oVirt/ovirt-site/blob/master/README.md - -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWxztZAAoJEHYPPTOszxHoOF4H/2UeK9JTspw4dYU+pUu8fKqf pSrE9ha3k9KpPnGIAx6VTnbXolNr9tHFiT8gcds1C9CVoMEPrKUxns9CTz3kPYBH /mGYCwQ+ncUNBCn+54uiKmXssaAtpVLnuxh8f1z9BDUoFjoY7ASLTzwXu9XTuH9V C9gaR0iGcRgSmBPjfPuAVWuHgimM068x5Ig2BoMSzAeCM7pO6LwiRzt3xX15xlR4 TMkUWLHdnJ1uL1GH267tMofrMnk25veDPIzuzIaPFjwIuTFgtwnUQI82ULbxcet2 NJ+y/UgwQ9JUQheoQL/oOsnSs244kFl0Vl+GuKMDGZ1FwCfoZerejnhEK+1cK0U= =KQLK -----END PGP SIGNATURE-----

3 4

oVirt 3.6.4 RC1 build starting
by Rafael Martins 15 Mar '16

15 Mar '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. Thanks, Rafael

1 0

oVirt 3.6.4 RC1 merge / tag / bugzilla reminder
by Rafael Martins 14 Mar '16

14 Mar '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Tuesday morning 11:00 AM TLV time. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.4, tr: 3.6.4) Thanks, Rafael Martins

1 0

oVirt 3.6.4 RC1 build planned
by Rafael Martins 14 Mar '16

14 Mar '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CET). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by monday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging tuesday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Thanks Rafael Martins

1 0

oVirt Integration Development Team weekly status - 2016-03-14
by Sandro Bonazzola 14 Mar '16

14 Mar '16

- *oVirt Integration Development Team weekly status - 2016-03-14* - - oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 4.0 - Adapting projects using ovirt-engine-sdk to v3 comaptibility layer - Migrating ovirt-log-collector to SDK 4 being python3 unavailable on v3 compatibility layer. - Rebasing oVirt Live master on new VDSM API - Rebasing Hosted Engine on new VDSM API - Dropped ovirt-host-deploy-offline package, not used anymore by node and ovirt live - oVirt Host Deploy now has pt_BR localization (thanks to *Wesley Morais de Oliveira*) - Infra: - Fixed several jenkins jobs - Disabled / removed all 3.5 jenkins jobs - CentOS Virt SIG: - 3.6.3 rpms have been released within Virt SIG repos - Wki has been updated with references to the new web site. - LINK: Roadmap and packages list: http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap - LINK: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ - *Team updates* - Didi - Worked on ovirt-host-deploy for NGN support - Worked on several bugs - Working on OTOPI for 4.0 / NGN - Ido: - getting familiar with Hosted engine installation - getting familiar with Lago installation - Lev: - Working on 3.6.5 this week - Rafael: - Added Fedora 23 support to ovirt-log-collector - Added SDK4 support to packages maintained by integration - Working to split engine-backup from ovirt-engine-tools package - Sandro: - Worked on oVirt Jenkins - Worked on ovirt-release - Worked on ovirt-host-deploy (dropped offline package) - Stabilized oVirt master (SDK and API rebase) - Simone: - Worked hosted-engine bugs for 3.6.4 - Fixing an issue adding an hosted-engine host on a system started on 3.4 - Looking at network stuff for hosted-engine on master -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Cockpit-oVirt plugin
by Marek Libra 14 Mar '16

14 Mar '16

I'm pleased to announce initial version of new oVirt plugin for Cockpit, which is recently a proposed feature for oVirt 4.0. The oVirt Wiki Feature can be found at [3]. Sources and README file can be found on the github [1]. Up-to-date issue list is at [2] (includes planed enhancements) Please refer the README file for install instructions, so far tested on Centos 7 (minimal). The plugin will be distributed as an rpm in the future and is meant as an optional add-on to oVirt. Main focus is on - troubleshooting when accessibility/functionality of webadmin is limited - easy-to-use tool for VM-centric host monitoring/administration - potential integration point with oVirt on UI level - easy to use, so for small setups the preferred choice with an option to "upgrade" to full oVirt later The plugin or its parts can be used as standalone same as embedded into other UIs, like drill-down from webadmin or ManageIQ for more details or fine-tuning. The plugin has dependency on VDSM. Please note, since there was a VDSM patch needed, recent master is required (see README in the source). Dependency on oVirt's engine is optional - when accessible then additional plugin functionality is available. Please note, the plugin is in early development phase showing basic concept. Marek ------------ Links: [1] Sources: https://github.com/mareklibra/cockpit-ovirt/ [2] Issue tracker: https://github.com/mareklibra/cockpit-ovirt/issues [3] Wiki Proposed Feature page is in review, recent unmerged version: https://github.com/mareklibra/ovirt-site/blob/cockpit-ovirt-plugin/source/d… Once merged, screenshots will be available.

9 14

feature request: shared templates and iso images
by Dobó László 13 Mar '16

13 Mar '16

Hi, It would be great if the template and iso domains can be attached to multiple datacenter at the same time. enax

2 2

Ovirt API Import OVA
by Bryan Hughes 11 Mar '16

11 Mar '16

--_000_2076DF62233643979B7AE1E4D5D9AD2Cexetergovcom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVsbG8sDQoNCkkgd2FzIGp1c3Qgd29uZGVyaW5nIGlmIHRoZXJlIHdhcyBhbiBhdXRvbWF0ZWQg d2F5IHRvIGltcG9ydCBhbiBPVkEgaW50byBvdmlydC4gIFdlIGFyZSBhdHRlbXB0aW5nIGFuIHVu YXR0ZW5kZWQgaW5zdGFsbCBhbmQgd2FudGVkIHRvIGltcG9ydCBhbiBPVkEgaW50byBvdmlydCB0 aHJvdWdoIHRoZSBBUEkgcHJlZmVyYWJseS4NCg0KSSBjb3VsZCBub3QgZmluZCBhbnl0aGluZyBp biB0aGUgQVBJIGRvY3MgaXRzZWxmIGJ1dCBtYXkgaGF2ZSBtaXNzZWQgc29tZXRoaW5nLg0KDQpU aGFua3MsDQpCcnlhbg0K --_000_2076DF62233643979B7AE1E4D5D9AD2Cexetergovcom_ Content-Type: text/html; charset="utf-8" Content-ID: <459885D3306B8340816AF42AE766EAD2(a)namprd06.prod.outlook.com> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8 ZGl2PkhlbGxvLDwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+SSB3YXMganVzdCB3b25k ZXJpbmcgaWYgdGhlcmUgd2FzIGFuIGF1dG9tYXRlZCB3YXkgdG8gaW1wb3J0IGFuIE9WQSBpbnRv IG92aXJ0LiAmbmJzcDtXZSBhcmUgYXR0ZW1wdGluZyBhbiB1bmF0dGVuZGVkIGluc3RhbGwgYW5k IHdhbnRlZCB0byBpbXBvcnQgYW4gT1ZBIGludG8gb3ZpcnQgdGhyb3VnaCB0aGUgQVBJIHByZWZl cmFibHkuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5JIGNvdWxkIG5vdCBmaW5kIGFu eXRoaW5nIGluIHRoZSBBUEkgZG9jcyBpdHNlbGYgYnV0IG1heSBoYXZlIG1pc3NlZCBzb21ldGhp bmcuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGFua3MsPC9kaXY+DQo8ZGl2PkJy eWFuPC9kaXY+DQo8ZGl2Pg0KPGRpdiBpZD0iTUFDX09VVExPT0tfU0lHTkFUVVJFIj48L2Rpdj4N CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_2076DF62233643979B7AE1E4D5D9AD2Cexetergovcom_--

5 7

Maintenance Notification: gerrit.ovirt.org Upgrade Today at 17:00 IST (16:00 CET)
by Anton Marchukov 10 Mar '16

10 Mar '16

Hello All. We plan to upgrade gerrit to a new version today starting at 17:00 IST (16:00 CET). During the upgrade the gerrit will not be available. This should not take longer than few hours and I will keep you updated on the progress. Please note that we plan to upgrade to the next major version 2.11.8 that will include UI and non UI changes. Please see summary of release notes and the link to release notes [1 - 9] below: - Inline editing (creating of new changes directly from the web browser) - Change screen (ability edit parent revision, edit now will use inline editing ui so expect lot of change in the new change screen) - Bugfixes (in fact the main motivation for upgrade were costant NullPointerExceptions) Please let us know if there is anything critical that is preventing us from this upgrade. Anton [1] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [2] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [3] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [4] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [5] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [6] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [7] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [8] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… [9] https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

1 2

ovirt 3.6.2
by Paul Dyer 10 Mar '16

10 Mar '16

since upgrading from 3.5 to 3.6.2, I cannot open a console on a VM. I made that the serial console was unchecked. I have tried using all the different console options. I have attached the last 12 lines of the engine log. It shows some errors at the time of the open VM console. Does anyone have time to give feedback and suggestions? Thanks -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

2 2

[VDSM] Moving to py.test
by Nir Soffer 10 Mar '16

10 Mar '16

Hi all, In the last vdsm call we discussed moving to py.test. Here is how to run the current tests with py.test: cd tests PYTHONPATH=../lib:../vdsm py.test -v *_test.py *_tests.py *Tests.py network Currently we have some failures and errors: 8 failed, 1662 passed, 101 skipped, 14 pytest-warnings, 10 error in 86.05 seconds Some py.test nice tricks: Finding the 10 slowest tests: PYTHONPATH=../lib:../vdsm py.test -v --durations=10 vmTests.py *_test.py *_tests.py *Tests.py network Checking code coverage: PYTHONPATH=../lib:../vdsm py.test -v --cov=../vdsm --cov=vdsm *_test.py *_tests.py *Tests.py network Once we finish moving vdsm code to lib/vdsm, renaming the tests to *_test.py, and add pytest.ini, running the test will be simply: py.test Once all the tests pass, we can: - Drop all the special asserts (assertXXX), py.test uses plain asserts https://pytest.org/latest/assert.html#asserting-with-the-assert-statement - Get better error reports https://pytest.org/latest/example/reportingdemo.html - Remove unneeded classes, or inherit from any class https://pytest.org/latest/getting-started.html - Replace @permutations with more powerfull @pytest.mark.parametrize https://pytest.org/latest/parametrize.html#parametrize-basics - Replace slowtest and stresstest with @pytest.mark https://pytest.org/latest/mark.html - Replace monkeypatch.py with simpler and more powerfull pytest monkeypatch funcarg https://pytest.org/latest/monkeypatch.html#monkeypatching-mocking-modules-a… - Replace NamedTemporaryDir with pytest tmpdir funcarg https://pytest.org/latest/getting-started.html#going-functional-requesting-… - Simplify complex context managers with pytest fixtures https://pytest.org/latest/example/simple.html - Drop testrunner.py, most of testlib.py, some of testValidation.py, run_tests*.sh - And more Nir

2 1

ovirt-aaa-jdbc-tool user password-reset admin
by Eldad Marciano 09 Mar '16

09 Mar '16

--Apple-Mail-1223A861-53D3-4012-AD3C-F398FE28C0E3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 DQoNClJlZ2FyZHMsDQotRWxkYWQNCg0KPiBPbiA5INeR157XqNelIDIwMTYsIGF0IDE5OjQ2LCBl bWFyY2lhbiA8ZW1hcmNpYW5AcmVkaGF0LmNvbT4gd3JvdGU6DQo+IA0KPiBIaSwNCj4gb3ZpcnQt YWFhLWpkYmMtdG9vbCB1c2VyIHBhc3N3b3JkLXJlc2V0IGFkbWluIA0KPiANCj4gDQo+IGltIHRy eWluZyB0byBydW4gdGhpcyB2aWEgdGhlIGFjdHVhbCBlbmdpbmUgY29kZSBlLmc6DQo+IH4vb3Zp cnQtZW5naW5lL2Jpbi9vdmlydC1lbmdpbmUtZXh0ZW5zaW9ucy10b29sDQo+IA0KPiBjYW4geW91 IGd1aWRlIG1lDQo+IC1FbGRhZA0K --Apple-Mail-1223A861-53D3-4012-AD3C-F398FE28C0E3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+PGJyPjxi cj48ZGl2PlJlZ2FyZHMsPC9kaXY+LUVsZGFkPC9kaXY+PGRpdj48YnI+T24gOSDXkdee16jXpSAy MDE2LCBhdCAxOTo0NiwgZW1hcmNpYW4gJmx0OzxhIGhyZWY9Im1haWx0bzplbWFyY2lhbkByZWRo YXQuY29tIj5lbWFyY2lhbkByZWRoYXQuY29tPC9hPiZndDsgd3JvdGU6PGJyPjxicj48L2Rpdj48 YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2Pg0KICANCg0KICAgIDxtZXRhIGh0dHAtZXF1aXY9 ImNvbnRlbnQtdHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCiAgDQog IA0KICAgIEhpLDxicj4NCiAgICA8bWV0YSBodHRwLWVxdWl2PSJjb250ZW50LXR5cGUiIGNvbnRl bnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQogICAgPHByZSBjbGFzcz0iaGlnaGxpZ2h0 IHBsYWludGV4dCIgc3R5bGU9ImJveC1zaXppbmc6IGJvcmRlci1ib3g7IG92ZXJmbG93OiBhdXRv OyBmb250LWZhbWlseTogTWVubG8sIE1vbmFjbywgQ29uc29sYXMsICdDb3VyaWVyIE5ldycsIG1v bm9zcGFjZTsgZm9udC1zaXplOiAxMXB0OyBkaXNwbGF5OiBibG9jazsgcGFkZGluZzogOHB0OyBt YXJnaW46IDBweCAwcHggOC41cHQ7IGxpbmUtaGVpZ2h0OiAxLjQyODU3OyB3b3JkLWJyZWFrOiBi cmVhay1hbGw7IHdvcmQtd3JhcDogYnJlYWstd29yZDsgY29sb3I6IHJnYig1MSwgNTEsIDUxKTsg Ym9yZGVyOiAxcHggc29saWQgcmdiKDIwNCwgMjA0LCAyMDQpOyBib3JkZXItcmFkaXVzOiA0cHg7 IGZvbnQtc3R5bGU6IG5vcm1hbDsgZm9udC12YXJpYW50OiBub3JtYWw7IGZvbnQtd2VpZ2h0OiBu b3JtYWw7IGxldHRlci1zcGFjaW5nOiBub3JtYWw7IG9ycGhhbnM6IGF1dG87IHRleHQtYWxpZ246 IHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgd2lkb3dzOiAx OyB3b3JkLXNwYWNpbmc6IDBweDsgLXdlYmtpdC10ZXh0LXN0cm9rZS13aWR0aDogMHB4OyBiYWNr Z3JvdW5kLWNvbG9yOiByZ2IoMjQ1LCAyNDUsIDI0NSk7Ij48Y29kZSBzdHlsZT0iYm94LXNpemlu ZzogYm9yZGVyLWJveDsgZm9udC1mYW1pbHk6IE1lbmxvLCBNb25hY28sIENvbnNvbGFzLCAnQ291 cmllciBOZXcnLCBtb25vc3BhY2U7IGZvbnQtc2l6ZTogaW5oZXJpdDsgcGFkZGluZzogMHB4OyBj b2xvcjogaW5oZXJpdDsgYm9yZGVyLXJhZGl1czogMHB4OyB3aGl0ZS1zcGFjZTogcHJlLXdyYXA7 IGJhY2tncm91bmQtY29sb3I6IHRyYW5zcGFyZW50OyI+b3ZpcnQtYWFhLWpkYmMtdG9vbCZuYnNw O3VzZXImbmJzcDtwYXNzd29yZC1yZXNldCZuYnNwO2FkbWluIA0KPC9jb2RlPjwvcHJlPg0KICAg IDxicj4NCiAgICA8YnI+DQogICAgaW0gdHJ5aW5nIHRvIHJ1biB0aGlzIHZpYSB0aGUgYWN0dWFs IGVuZ2luZSBjb2RlIGUuZzo8YnI+DQogICAgfi9vdmlydC1lbmdpbmUvYmluL292aXJ0LWVuZ2lu ZS1leHRlbnNpb25zLXRvb2w8YnI+DQogICAgPGJyPg0KICAgIGNhbiB5b3UgZ3VpZGUgbWU8YnI+ DQogICAgLUVsZGFkPGJyPg0KICANCg0KPC9kaXY+PC9ibG9ja3F1b3RlPjwvYm9keT48L2h0bWw+ --Apple-Mail-1223A861-53D3-4012-AD3C-F398FE28C0E3--

2 1

Where's ovirt-release-master RPM on resources.ovirt.org ?
by Yaniv Kaul 09 Mar '16

09 Mar '16

I can find it @ http://rsync.nl.gentoo.org/pub/software/ovirt/ovirt-master-snapshot/rpm/el7… I can't find it @ http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/el7Workstat…

5 6

Failing to attach iso domain to master engine
by Sandro Bonazzola 09 Mar '16

09 Mar '16

Hi, trying to attach an iso domain to engine master: 2016-03-08 15:04:28,386 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (default task-50) [477da39f] Lock Acquired to object 'EngineLock:{exclusiveLocks='[bd9860d2-756b-42bd-9cf 6-08c0e96d70dc=<STORAGE, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}' 2016-03-08 15:04:28,433 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] Running command: AttachStorageDomainToPoolCommand interna l: false. Entities affected : ID: bd9860d2-756b-42bd-9cf6-08c0e96d70dc Type: StorageAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN, ID: 07b2decc-9d40-4df6-bfa1-0da26f95df53 Type: StoragePoolAction group MANIPULATE_STORAGE_DOMAIN with role type ADMIN 2016-03-08 15:04:28,445 INFO [org.ovirt.engine.core.bll.storage.connection.ConnectStorageToVdsCommand] (org.ovirt.thread.pool-10-thread-43) [72ff69e2] Running command: ConnectStorageToVdsCommand internal: true. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_STORAGE_DOMAIN with role type ADMIN 2016-03-08 15:04:28,447 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (org.ovirt.thread.pool-10-thread-43) [72ff69e2] START, ConnectStorageServerVDSCommand(HostName = local_hos t, StorageServerConnectionManagementVDSParameters:{runAsync='true', hostId='384c1ab4-e03b-46ff-8e32-8a8b3650235b', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='NFS', connectionList='[Storag eServerConnections:{id='51ffb87c-c595-4792-b915-50af506dbf67', connection='mididell.home:/var/lib/exports/iso-20160308130525', iqn='null', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null ', nfsTimeo='null', iface='null', netIfaceName='null'}]'}), log id: 2e547cc1 2016-03-08 15:04:29,454 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (org.ovirt.thread.pool-10-thread-43) [72ff69e2] FINISH, ConnectStorageServerVDSCommand, return: {51ffb87c- c595-4792-b915-50af506dbf67=0}, log id: 2e547cc1 2016-03-08 15:04:29,455 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] START, AttachStorageDomainVDSCommand( AttachStorageDomainVD SCommandParameters:{runAsync='true', storagePoolId='07b2decc-9d40-4df6-bfa1-0da26f95df53', ignoreFailoverLimit='false', storageDomainId='bd9860d2-756b-42bd-9cf6-08c0e96d70dc'}), log id: 5bc96473 2016-03-08 15:04:30,549 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] Failed in 'AttachStorageDomainVDS' method 2016-03-08 15:04:30,558 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-10-thread-42) [477da39f] Correlation ID: null, Call Stack: null, Custom Event ID: -1, M essage: VDSM command failed: Error in storage domain action: (u'sdUUID=bd9860d2-756b-42bd-9cf6-08c0e96d70dc, spUUID=07b2decc-9d40-4df6-bfa1-0da26f95df53',) 2016-03-08 15:04:30,558 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] Command 'AttachStorageDomainVDSCommand( AttachStorageDomain VDSCommandParameters:{runAsync='true', storagePoolId='07b2decc-9d40-4df6-bfa1-0da26f95df53', ignoreFailoverLimit='false', storageDomainId='bd9860d2-756b-42bd-9cf6-08c0e96d70dc'})' execution failed: IRSGenericExc eption: IRSErrorException: Failed to AttachStorageDomainVDS, error = Error in storage domain action: (u'sdUUID=bd9860d2-756b-42bd-9cf6-08c0e96d70dc, spUUID=07b2decc-9d40-4df6-bfa1-0da26f95df53',), code = 350 2016-03-08 15:04:30,558 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] FINISH, AttachStorageDomainVDSCommand, log id: 5bc96473 2016-03-08 15:04:30,558 ERROR [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] Command 'org.ovirt.engine.core.bll.storage.domain.AttachS torageDomainToPoolCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.irsbroker.IrsOperationFailedNoFailoverException: IRSGenericException: IRSErrorException: Failed to AttachStorageDomainVDS, erro r = Error in storage domain action: (u'sdUUID=bd9860d2-756b-42bd-9cf6-08c0e96d70dc, spUUID=07b2decc-9d40-4df6-bfa1-0da26f95df53',), code = 350 (Failed with error StorageDomainActionError and code 350) 2016-03-08 15:04:30,559 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] Command [id=6426d8ba-223f-401d-8fed-c537620bd4c3]: Compensating NEW_ENTITY_ID of org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot: StoragePoolIsoMapId:{storagePoolId='07b2decc-9d40-4df6-bfa1-0da26f95df53', storageId='bd9860d2-756b-42bd-9cf6-08c0e96d70dc'}. 2016-03-08 15:04:30,575 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-10-thread-42) [477da39f] Correlation ID: 477da39f, Job ID: 13fbe031-0c58-4fff-bc38-324cce2e4c3f, Call Stack: null, Custom Event ID: -1, Message: Failed to attach Storage Domain ISO_DOMAIN to Data Center local_datacenter. (User: admin@internal) 2016-03-08 15:04:30,584 INFO [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand] (org.ovirt.thread.pool-10-thread-42) [477da39f] Lock freed to object 'EngineLock:{exclusiveLocks='[bd9860d2-756b-42bd-9cf6-08c0e96d70dc=<STORAGE, ACTION_TYPE_FAILED_OBJECT_LOCKED>]', sharedLocks='null'}' Any hint on what can be the reason? # rpm -qv ovirt-engine ovirt-engine-4.0.0-0.0.master.20160307171512.git398703d.el7.centos.noarch -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 3

Type verification for vdsm
by Piotr Kliczewski 09 Mar '16

09 Mar '16

All, I am working on converting our vdsm schema to yaml. As part of this work [1] I added type verification for request and response data. There was a suggestion to raise an exception when there is type inconsistency but after a bit of testing I can see that there are inconsistencies for many verbs. I introduced strict mode config value which switches between raising exception and logging a warning. At the moment we log inconsistencies but there is a plan to be strict for master and log for stable branches. I would like to ask each vertical representative/maintainer to review the code and fix any inconsistencies in the schema. Thanks, Piotr [1] https://gerrit.ovirt.org/#/c/53919

2 5

[VDSM] check_merged failures
by Nir Soffer 08 Mar '16

08 Mar '16

Hi all, The new check_merged job is failing randomly. I have see this error today: 14:20:16 @ Start specified VMs: 14:20:16 # Start nets: 14:20:16 * Create network vdsm_functional_tests_lago: 14:20:16 libvirt: error : internal error: Network is already in use by interface 7f0c-bc616ef 14:20:16 * Create network vdsm_functional_tests_lago: ERROR (in 0:00:00) 14:20:16 # Start nets: ERROR (in 0:00:00) 14:20:16 @ Start specified VMs: ERROR (in 0:00:00) 14:20:16 Error occured, aborting 14:20:16 Traceback (most recent call last): 14:20:16 File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 539, in main 14:20:16 cli_plugins[args.verb].do_run(args) 14:20:16 File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 180, in do_run 14:20:16 self._do_run(**vars(args)) 14:20:16 File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 132, in wrapper 14:20:16 return func(*args, prefix=lago_prefix.Prefix(prefix_path), **kwargs) 14:20:16 File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 141, in wrapper 14:20:16 return func(*args, prefix=prefix, **kwargs) 14:20:16 File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 191, in do_start 14:20:16 prefix.start(vm_names=vm_names) 14:20:16 File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 819, in start 14:20:16 self.virt_env.start(vm_names=vm_names) 14:20:16 File "/usr/lib/python2.7/site-packages/lago/virt.py", line 187, in start 14:20:16 net.start() 14:20:16 File "/usr/lib/python2.7/site-packages/lago/virt.py", line 354, in start 14:20:16 self._env.libvirt_con.networkCreateXML(self._libvirt_xml()) 14:20:16 File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4093, in networkCreateXML 14:20:16 if ret is None:raise libvirtError('virNetworkCreateXML() failed', conn=self) 14:20:16 libvirtError: internal error: Network is already in use by interface 7f0c-bc616ef Hopefully someone is owning the infrastructure and can look into this. Nir

3 2

node-iso for 3.6
by Dobó László 08 Mar '16

08 Mar '16

Hi, I didn't find any node iso for ovirt 3.6, which one is recommended for installation ? Thanks! Enax

2 1

[VDSM] STOMP tests failures
by Nir Soffer 08 Mar '16

08 Mar '16

Hi all, We are seeing the following error randomly - there must be a timing issue in the test, or maybe in the code? Pitor, can you check this? (From http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/3568/conso…) 13:33:28 ====================================================================== 13:33:28 ERROR: test_echo(1024, False) (stompTests.StompTests) 13:33:28 ---------------------------------------------------------------------- 13:33:28 Traceback (most recent call last): 13:33:28 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testlib.py", line 73, in wrapper 13:33:28 return f(self, *args) 13:33:28 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/stompTests.py", line 83, in test_echo 13:33:28 str(uuid4())), 13:33:28 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/__init__.py", line 339, in callMethod 13:33:28 raise JsonRpcNoResponseError(methodName) 13:33:28 JsonRpcNoResponseError: [-32605] No response for JSON-RPC echo request. 13:33:28 -------------------- >> begin captured logging << -------------------- 13:33:28 vds.MultiProtocolAcceptor: INFO: Listening at ::1:38659 13:33:28 Scheduler: DEBUG: Starting scheduler test.Scheduler 13:33:28 Scheduler: DEBUG: started 13:33:28 Executor: DEBUG: Starting executor 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/0 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/1 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/2 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/3 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/4 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/5 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/6 13:33:28 Executor: DEBUG: Worker started 13:33:28 Executor: DEBUG: Starting worker jsonrpc.Executor/7 13:33:28 Executor: DEBUG: Worker started 13:33:28 vds.MultiProtocolAcceptor: DEBUG: Adding detector <vdsm.rpc.bindingxmlrpc.XmlDetector instance at 0x7f9e4b3e9a70> 13:33:28 vds.MultiProtocolAcceptor: DEBUG: Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x7f9e4b3e9ab8> 13:33:28 FakeClientIf: INFO: XMLRPC server running 13:33:28 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from ::1:39788 13:33:28 ProtocolDetector.Detector: DEBUG: Using required_size=11 13:33:28 ProtocolDetector.Detector: INFO: Detected protocol stomp from ::1:39788 13:33:28 Broker.StompAdapter: INFO: Processing CONNECT request 13:33:28 jsonrpc.AsyncoreClient: DEBUG: Sending response 13:33:28 yajsonrpc.protocols.stomp.AsyncClient: DEBUG: Stomp connection established 13:33:28 Broker.StompAdapter: INFO: Subscribe command received 13:33:28 jsonrpc.JsonRpcServer: DEBUG: Calling 'echo' in bridge with [u'Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut en'] 13:33:29 jsonrpc.JsonRpcServer: DEBUG: Return 'echo' in bridge with Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut en 13:33:29 protocoldetector.StompDetector: DEBUG: Stomp detected from ('::1', 39788) 13:33:29 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 13:33:29 jsonrpc.JsonRpcServer: INFO: Stopping JsonRPC Server 13:33:29 Executor: DEBUG: Stopping executor 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/7 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Worker stopped 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/2 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/3 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/0 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/1 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/6 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/5 13:33:29 Executor: DEBUG: Waiting for worker jsonrpc.Executor/4 13:33:29 FakeClientIf: INFO: Stopping XMLRPC server 13:33:29 FakeClientIf: INFO: XMLRPC server stopped 13:33:29 Scheduler: DEBUG: Stopping scheduler test.Scheduler 13:33:29 Scheduler: DEBUG: stopped 13:33:29 --------------------- >> end captured logging << ---------------------

2 1

[URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed
by Sandro Bonazzola 08 Mar '16

08 Mar '16

Hi, I think I already raised the issue several times, but let me raise this again. VDSM building / automated versioning is badly broken. Currently, 3.6 snapshot is building: vdsm-4.17.19-32.git171584b.el7.centos.src.rpm <http://jenkins.ovirt.org/job/vdsm_3.6_build-artifacts-el7-x86_64/178/artifa…> because the last tag on the 3.6 branch was 4.17.19 and new tags have been created in different branches. This make impossible to upgrade from stable (4.17.23) to latest snapshot. This also break dependencies on other projects requiring the latest released version like hosted engine. Please fix the automated versioning system vdsm is currently using or get rid of it. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

6 23

[oVirt jenkins] Weekly report on open tasks for ovirt-engine
by jenkins＠ovirt.org 08 Mar '16

08 Mar '16

------=_Part_84_1710939013.1457436534280 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Files scanned: '**/*.java, **/*.py'. Strings searched: FIXME | TODO | @deprecated Report: http://jenkins.ovirt.org/job/ovirt-engine_master_scan-open-tasks_merged//45… ------=_Part_84_1710939013.1457436534280--

1 0

How can users use oVirtCli to complete "run once"?
by zhukaijie 08 Mar '16

08 Mar '16

As you know. In web, users can use "RUN ONCE" button to run a VM with some params (such as certain custom properties). But can oVirtCli be used to complete "RUN ONCE"? Thank you.

3 2

oVirt Integration Development Team weekly status - 2016-03-07
by Sandro Bonazzola 07 Mar '16

07 Mar '16

- oVirt integration open bugs: https://bugzilla.redhat.com/buglist.cgi?quicksearch=classification%3Aovirt%… - 3.6.3 - Built and released oVirt 3.6.3 GA distribution - Built and released oVirt Live 3.6.3 GA media - Release notes: http://www.ovirt.org/release/3.6.3/ - Announce: http://lists.ovirt.org/pipermail/announce/2016-March/000237.html - Fixing latest blockers for 3.6.3 - Adding Fedora 23 support to ovirt-log-collector - Published documentation about HE upgrade from el6 3.5 to el7 3.6 - 4.0.0 - Re-factored ovirt-release package for easy Jenkins and NGN consumption - started 4.0 pre integration and migration from 3.6 testing - SpagoBi: progress packaging spagobi and spagobi-dependencies - Infra: - Fixed several jobs issues - CentOS Virt SIG: - Rafael joined CentOS Virt SIG - CentOS Virt SIG - oVirt How To: http://wiki.centos.org/HowTos/oVirt - Meeting minutes will be available on https://www.centos.org/minutes/2016/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

master ovirt-engine requires ovirt-engine-sdk-python >= 4.0.0.0
by Yedidyah Bar David 07 Mar '16

07 Mar '16

Hi all, I am trying, on a rhel7 vm: yum install -y http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm yum install ovirt-engine Fails with: --> Finished Dependency Resolution Error: Package: ovirt-iso-uploader-4.0.0-0.0.master.20160208072812.gita433ce3.el7.centos.noarch (ovirt-master-snapshot) Requires: ovirt-engine-sdk-python >= 4.0.0.0 Available: ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.0.3-1.el7.centos Available: ovirt-engine-sdk-python-3.6.2.1-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.2.1-1.el7 Installing: ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.3.0-1.el7 Error: Package: ovirt-image-uploader-4.0.0-0.0.master.20160211135948.git43cc942.el7.centos.noarch (ovirt-master-snapshot) Requires: ovirt-engine-sdk-python >= 4.0.0.0 Available: ovirt-engine-sdk-python-3.6.0.3-1.el7.centos.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.0.3-1.el7.centos Available: ovirt-engine-sdk-python-3.6.2.1-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.2.1-1.el7 Installing: ovirt-engine-sdk-python-3.6.3.0-1.el7.noarch (centos-ovirt36) ovirt-engine-sdk-python = 3.6.3.0-1.el7 Tried also: yum install http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-artifacts-el7-x8… which works, but does not satisfy the above dep. Should it? Any other place to find 4.0 python sdk? Thanks, -- Didi

4 6

nested hosts \ vdsm hooks on rhel 7.2
by emarcian 07 Mar '16

07 Mar '16

Hi, Has anyone ever used vdsm hooks in RHEL 7.2 on to of 3.6 ? I faced some issues with that, related to emulated machines [root@localhost ~]# tail -f /var/log/vdsm/vdsm.log |grep ':ERROR:' Thread-18::ERROR::2016-03-06 07:43:57,019::caps::195::root::(_get_emulated_machines_from_domain) Error while looking for kvm domain (x86_64) libvirt capabilities -Eldad

2 2

logging VDSM-generated libvirt XML properly
by Martin Polednik 07 Mar '16

07 Mar '16

Hello developers! I've been chasing a bug that lead me to an idea of improving our XML logging. Now, to see a VMs generated libvirt XML, we have to rely on vdsm.log. The issue is that the log is rotating and therefore, it is easy to miss the correct XML when dealing with busy hypervisor. Since we're built on libvirt, I was thinking of doing similar thinks that libvirt does with qemu commandline. Each running domain(VM) has it's command line logged in /var/log/libvirt/qemu/${vmname}. This is great for debugging as you can mostly just take the cmdline and restart the VM. There is an issue with using the cmdline directly - networking. Libvirt uses additional script to create and up a bridge. Therefore, it is easier to use the XML and shape it to one's needs. I propose that we properly log the generated XML in a similar fashion as libvirt generates the cmdline. This means we would have path like /var/log/vdsm/libvirt/${vmname}, where generated XML would be stored. To minimize the logging requirements, only last definition of VM with that name may be stored. Additionally, exception level errors related to that VM could also be stored there. What do you think, can we afford the space and additional writes per VM to help the debugging process? Regards, mpolednik

2 2

In AIO environment, why engine and vdsm communicate timeout
by 李坚 07 Mar '16

07 Mar '16

4 3

Engine High Availability
by Sunny Shin 06 Mar '16

06 Mar '16

Hi All, In the new architecture page ( http://www.ovirt.org/documentation/architecture/architecture/) overall architecture picture shows that engine supports active-active high availability. However, as per engine HA page ( http://www.ovirt.org/develop/release-management/features/engine/engine-high…) active-active HA is not supported yet and there are several implementation issues. So, could anyone give me a brief explanation about discrepancy between these two pages, and about the plan to implement this feature if not implemented yet? Sunny

2 9

Allow access to Cockpit by default after adding a host? Or make it configurable in Engine?
by Fabian Deutsch 04 Mar '16

04 Mar '16

Hey, Node Next will ship Cockpit by default. When the host is getting installed, Cockpit can be reached by default over it's port 9090/tcp. But after the host was added to Engine, Engine/vdsm is setting up it's own iptables rules which then prevent further access to Cockpit. How do we want users to control the access to Cockpit? So where shall users be able to open or close the Cockpit firewall port. Initially I thought that we can open up the cockpit port by default, but this might be a security issue. (Brute force attacks to crack user passwords through the web interface). - fabian

3 5

oVirt Engine 3.6.4 branch was created + backport guide for 3.6.z
by Tal Nisan 03 Mar '16

03 Mar '16

Hi everyone, The ovirt-engine-3.6.4 branch has been created following the last (hopefully) respin of 3.6.3 Note the the branch was created from the 3.6.3 branch today and contains all the content of 3.6.3 obviously. As I am asked a lot of questions questions concerning the backport flow for 3.6.z bugs, here it is: 3.6.5 bugs should be included in: - master - ovirt-engine-3.6 3.6.4 bugs should be included in: - master - ovirt-engine-3.6 - ovirt-engine-3.6.4. As for 3.6.6 only bugs i.e. those that are solved in the timeline before branching out of 3.6.5 but you do not want them to be included in 3.6.5, those should NOT be merged on ovirt-engine-3.6 until 3.6.5 will be branched out (date TBD, probably a couple of weeks before the release date). For further questions feel free to contact me.

1 0

[ANN] oVirt 3.6.3 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 03 Mar '16

03 Mar '16

The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 3.6.3 for testing, as of February 24th, 2016 This release is available now for Fedora 22, Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar). This release supports Hypervisor Hosts running Red Hat Enterprise Linux >= 7.2, CentOS Linux >= 7.2 (or similar) and Fedora 22. Highly experimental support for Debian 8.3 Jessie has been added too. This release candidate includes updated packages for: - ovirt-engine - vdsm - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup This release of oVirt 3.6.3 includes numerous bug fixes. See the release notes [1] for an initial list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO will be available soon [2]. Please note that mirrors[3] may need usually one day before being synchronized. * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.3/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/Upcoming_events [1] http://www.ovirt.org/release/3.6.3/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 4

python3-ovirt-engine-sdk4-4.0.0-0.0.20160302git42dbb0c.x86_64 missing deps on el7
by Sandro Bonazzola 03 Mar '16

03 Mar '16

Hi, python3 is not available on el7, causing: *00:17:51.028* Num Packages in Repos: 20203*00:17:51.028* package: python3-ovirt-engine-sdk4-4.0.0-0.0.20160302git42dbb0c.x86_64 from check-custom-el7*00:17:51.028* unresolved deps: *00:17:51.028* python3-pycurl*00:17:51.028* python3 Please fix the spec file avoiding to build python3 modules on el7, thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[ACTION REQUIRED] Legacy code removal
by Sandro Bonazzola 03 Mar '16

03 Mar '16

Hi, for oVirt 4.0 we're going to drop backward compatibility with oVirt < 3.6, you're kindly invited to cleanup the code dropping legacy support for older version. More in detail, for 4.0 we'll assume: * Support for EL6 hosts will be dropped * oVirt Engine support for EL6 will be dropped * Upgrade / Migration (if oVirt Engine was running on EL6) will be supported only from oVirt 3.6 * Network API support for oVirt < 3.6 will be dropped, the remaining API should be backward compatible * oVirt Engine will support cluster compatibility >= 3.6 * We won't support in place upgrade for oVirt Engine from 3.6 EL6 to 4.0 EL7: we'll support only migration. * oVirt DWH will only have 3.6 \ 4.0 compatibility views in 4.0. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Cockpit port open by default after adding host
by Fabian Deutsch 02 Mar '16

02 Mar '16

Hey, we use cockpit on Node Next, and we configure firewalld to open the port by default. However, after adding the host to Engine, the port is getting closed again because iptables is the used. How do you recommend to get the cockpit port opened by default? - fabian

2 4

Move host-deploy package installations into package?
by Fabian Deutsch 02 Mar '16

02 Mar '16

Hey, IIUIC host-deploy is currently installing some packages manually: https://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=src/plugin… Can't these dependencies moved to vdsm - or if not - can't they be moved to a ovirt-host package? Then we'd have all package related informations in one place. I find it odd that host-deploy is taking care of package installation, imo it should be sufficient to install a single package and have a host ready. host-deploy can then focus on just configuring the existing packages. Thoughts? - fabian

3 3

Iscsi and other BAD buggy
by Вячеслав Бадалян 02 Mar '16

02 Mar '16

Hello. ZERO) https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt Sorry, entering a bug into the product *oVirt* has been disabled And lets go. A) If host with ovirt have iscsi target we will have bug troubles. Its looks like 1. Create targetcli from LVM 2. All ok 3. Reboot 4/ LVM found oVIrt partitions and connect it. 5. targetcli can't get device. It's allready busy. If you add some filter to don's search iscsi devices then ovirt does not work correctly. B) Some throuble with glusterD. VSDM do mount of hosted engine volume and this host is aslo GluserD Server. Bug troubles. C) If i reboot 1 of 3 gluster servers then hosted engine will very slowly. Have many errors in dmes, Agent-ha reboot VM. Vm can't conect to don't full cluster and stuck in Paused mode. Realy... Its all look so bad... i mirgrate to NFS :( D) Network conffugurate realy bad. If i need to change network i can't do it. oVirt save posted from web settings. Bug vsdm-networking MUST fallback to previos setup if i mistake or SERVIS does not start. E). Ovirt reports does not install. [java] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actionModelService' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.ExceptionInInitializerError 2016-02-28 09:20:59 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_reports.jasper.deploy plugin.execute:941 execute-output: ('./js-ant', '-DmasterPropsSource=/tmp/tmp3paFhC/config', 'import-minimal-ce') stderr: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 BUILD FAILED /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:263: The following error occurred while executing this line: /usr/share/jasperreports-server/buildomatic/bin/import-export.xml:142: Java returned: 255 Total time: 24 seconds 2016-02-28 09:20:59 DEBUG otopi.context context._executeMethod:156 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 146, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py", line 656, in _deploy self._buildJs(config=config, cmd=cmd) File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-reports/jasper/deploy.py", line 215, in _buildJs 'buildomatic', File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 946, in execute command=args[0], RuntimeError: Command './js-ant' failed to execute 2016-02-28 09:20:59 ERROR otopi.context context._executeMethod:165 Failed to execute stage 'Misc configuration': Command './js-ant' failed to execute 2016-02-28 09:20:59 DEBUG otopi.transaction transaction.abort:134 aborting 'Yum Transaction' 2016-02-28 09:20:59 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:95 Yum Performing yum transaction rollback Загружены модули: fastestmirror, versionlock -- -- С уважением, Бадалян Вячеслав Борисович ООО "Открытые бизнес-решения" Технический директор +7 (495) 666-0-111 http://www.open-bs.ru

4 6

Re: [ovirt-devel] In AIO environment, why engine and vdsm communicate timeout
by lijian 02 Mar '16

02 Mar '16

This is a multi-part message in MIME format. ------=_NextPart_56D64ED3_8055F6B0_0FD12B2F Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgTWHvvIwKCgogcHJvdmlkZSBvdmVydC1lbmdpbmUgbG9n77yMSSB3aWxsIHByb3ZpZGUg dmRkbSBsb2cuIHRoYW5rcyEKCgrigJTigJTigJTigJTigJTigJTigJTigJTigJTigJTigJTi gJTigJTigJTigJTigJTigJTigJTigJTigJTigJTigJQKb3ZpcnQgZGV2ZWxvcGVyCgoKUGxl YXNlIHNoYXJlIHZkc20gYW5kIGVuZ2luZSBsb2dzIHNvIEkgY291bGQgdW5kZXJzdGFuZCB3 aGF0IGhhcHBlbmVkLiBPbiBUdWUsIE1hciAxLCAyMDE2IGF0IDEyOjM4IFBNLCDmnY7lnZog bGlqaWFuQGNsb3VkLXRpbWVzLmNvbSB3cm90ZTogIERlYXIgb3ZpcnQgZGV2ZWxvcGVycywg ICBJbiBvdmlydCAzLjUueCB2ZXJzaW9uLCB0aGVyZSBpcyBhIHByb2JsZW0gY29tbXVuaWNh dGluZyB0aW1lb3V0IGJldHdlZW4gIG92aXJ0LWVuZ2luZSBhbmQgdmRzbSBpbiBBSU8gZW52 aXJvbm1lbnQuIFRoZSBkZWZhdWx0IHRpbWVvdXQgaXMgMTgwICBzZWNvbmRzLCBidXQgdmRz bSByZXR1cm5pbmcgYSByZXF1ZXN0IGNvc3QgNTAwIHNlY29uZHMuIFRoZSBBSU8gaG9zdCBp cyAgbGlnaHQgbG9hZCBhbmQgZG8geW91IGtub3cgd2h5IHNvIHNsb3dseS4gICAgSSByZW1l bWJlciB0aGF0IGl0IGRvbid0IGhhdmUgdGhpcyBwcm9ibGVtIGluIDIueCB2ZXJzaW9uLiBw bGVhc2UgaGVscCBtZSwgIHRoYW5rcyEgICAgIFRoYW5rcyAgQmVzdCBSZWdhcmRzICAgLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLSAgIG92aXJ0IGRlbGVsb3BlciAgICAgIF9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fICBEZXZlbCBtYWlsaW5nIGxpc3QgIERl dmVsQG92aXJ0Lm9yZyAgaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZv L2RldmVs ------=_NextPart_56D64ED3_8055F6B0_0FD12B2F Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0iZm9udDoxNHB4LzEuNSAnTHVjaWRhIEdyYW5kZScsICflvq7ova/pm4Xp u5EnO2NvbG9yOiMzMzM7Ij48cCBzdHlsZT0iZm9udDoxNHB4LzEuNSAnTHVjaWRhIEdyYW5k ZSc7bWFyZ2luOjA7Ij5IaSBNYe+8jDwvcD48cCBzdHlsZT0iZm9udDoxNHB4LzEuNSAnTHVj aWRhIEdyYW5kZSc7bWFyZ2luOjA7Ij48YnI+PC9wPjxwIHN0eWxlPSJmb250OjE0cHgvMS41 ICdMdWNpZGEgR3JhbmRlJzttYXJnaW46MDsiPiZuYnNwOyBwcm92aWRlIG92ZXJ0LWVuZ2lu ZSBsb2fvvIxJIHdpbGwgcHJvdmlkZSB2ZGRtIGxvZy4gJm5ic3A7dGhhbmtzITwvcD48YnI+ PGRpdj48ZGl2IHN0eWxlPSJmb250OiAxNHB4LzEuNSAnTHVjaWRhIEdyYW5kZSc7Ij48cCBz dHlsZT0ibWFyZ2luOiA1cHggMHB4OyBmb250LWZhbWlseTogdmVyZGFuYSwgVGFob21hLCBB cmlhbCwg5a6L5L2TLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE2cHg7IGxpbmUtaGVpZ2h0 OiBub3JtYWw7IHdpZG93czogMTsiPuKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKA lOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlOKAlDwvcD48cCBzdHlsZT0ibWFyZ2lu OiA1cHggMHB4OyBmb250LWZhbWlseTogdmVyZGFuYSwgVGFob21hLCBBcmlhbCwg5a6L5L2T LCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE2cHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IHdp ZG93czogMTsiPm92aXJ0IGRldmVsb3BlcjwvcD48L2Rpdj48L2Rpdj48ZGl2IGNsYXNzPSJm b3htYWlsX2Jsb2NrcXVvdGVfZnJvbWhlcmVfZWxlbWVudCIgc3R5bGU9ImZvbnQ6IDEycHgv MS41ICdMdWNpZGEgR3JhbmRlJztwYWRkaW5nOjJweCAwIDJweCAwOyI+PGJyPjwvZGl2Pjxk aXYgY2xhc3M9Im1haWxfcXVvdGVfOEZBRDk1MUQyNzNENDZBM0FEQTJERkI2ODA0REMzQzgi IHN0eWxlPSJmb250OiAxNHB4LzEuNSAnTHVjaWRhIEdyYW5kZSc7Y29sb3I6IzMzMzsiPjxw cmUgc3R5bGU9IndoaXRlLXNwYWNlOnByZS13cmFwOyI+UGxlYXNlIHNoYXJlIHZkc20gYW5k IGVuZ2luZSBsb2dzIHNvIEkgY291bGQgdW5kZXJzdGFuZCB3aGF0IGhhcHBlbmVkLgoKT24g VHVlLCBNYXIgMSwgMjAxNiBhdCAxMjozOCBQTSwg5p2O5Z2aICZsdDs8YSBocmVmPSJtYWls dG86bGlqaWFuQGNsb3VkLXRpbWVzLmNvbSIgdGl0bGU9Im1haWx0bzpsaWppYW5AY2xvdWQt dGltZXMuY29tIj5saWppYW5AY2xvdWQtdGltZXMuY29tPC9hPiZndDsgd3JvdGU6CiZndDsg RGVhciBvdmlydCBkZXZlbG9wZXJzLAoKJmd0OwomZ3Q7ICAgSW4gb3ZpcnQgMy41LnggdmVy c2lvbiwgdGhlcmUgaXMgYSBwcm9ibGVtICBjb21tdW5pY2F0aW5nIHRpbWVvdXQgYmV0d2Vl bgomZ3Q7IG92aXJ0LWVuZ2luZSBhbmQgdmRzbSBpbiBBSU8gZW52aXJvbm1lbnQuIFRoZSBk ZWZhdWx0IHRpbWVvdXQgaXMgMTgwCiZndDsgc2Vjb25kcywgYnV0IHZkc20gcmV0dXJuaW5n IGEgcmVxdWVzdCBjb3N0IDUwMCBzZWNvbmRzLiBUaGUgQUlPIGhvc3QgaXMKJmd0OyBsaWdo dCBsb2FkIGFuZCBkbyB5b3Uga25vdyB3aHkgc28gc2xvd2x5LgomZ3Q7CiZndDsKJmd0OyAg IEkgcmVtZW1iZXIgdGhhdCBpdCBkb24ndCBoYXZlIHRoaXMgcHJvYmxlbSBpbiAyLnggdmVy c2lvbi4gcGxlYXNlIGhlbHAgbWUsCiZndDsgdGhhbmtzIQomZ3Q7CiZndDsKJmd0OwomZ3Q7 ICAgVGhhbmtzICZhbXA7IEJlc3QgUmVnYXJkcwomZ3Q7CiZndDsgLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LQomZ3Q7CiZndDsgIG92aXJ0IGRlbGVsb3BlcgomZ3Q7CiZndDsKJmd0OwomZ3Q7CiZndDsg X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KJmd0OyBE ZXZlbCBtYWlsaW5nIGxpc3QKJmd0OyA8YSBocmVmPSJtYWlsdG86RGV2ZWxAb3ZpcnQub3Jn IiB0aXRsZT0ibWFpbHRvOkRldmVsQG92aXJ0Lm9yZyI+RGV2ZWxAb3ZpcnQub3JnPC9hPgom Z3Q7IDxhIGhyZWY9Imh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9k ZXZlbCIgdGl0bGU9Imh0dHA6Ly9saXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9k ZXZlbCI+aHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RldmVsPC9h PgoKCjwvcHJlPjwvZGl2PjwvZGl2Pg== ------=_NextPart_56D64ED3_8055F6B0_0FD12B2F--

1 0

[ANN] oVirt 3.6.3 Final Release is now available
by Sandro Bonazzola 01 Mar '16

01 Mar '16

The oVirt Project is pleased to announce today the general availability of oVirt 3.6.3. This latest community release includes numerous bug fixes and several new features, such as: - The WebSocketProxy VDC option(and a few others) can now be updated without need to restart the engine. - OVIRT-CLI now use remote-viewer instead of spicec for spice based console - unassigned host status now reflects more the real status - cloud-init service after appliance deployment is now disabled oVirt is an open-source, openly-governed enterprise virtualization management application, developed by a global community. You can use the oVirt management interface (oVirt Engine) to manage hardware nodes, storage and network resources, and to deploy and monitor virtual machines running in your data center. If you are familiar with VMware products, oVirt is conceptually similar to vSphere. oVirt serves as the bedrock for Red Hat's Enterprise Virtualization product, and it is the "upstream" project where new features are developed prior to their inclusion in Red Hat's supported product offering. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.3/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Read more about oVirt Project community events: http://www.ovirt.org/events/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0