June 2015 - Devel - oVirt List Archives

[oVirt 3.6 Localization Question #18] "Snapshots scheduled on volume"
by Yuko Katabami 23 Jun '15

23 Jun '15

This is a multi-part message in MIME format. --------------040608070501080904070304 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello all, I have another question I would like to ask: *File:***LocalizedEnums *Resource ID:***AuditLogType___GLUSTER_VOLUME_SNAPSHOT_SCHEDULED *String:***Snapshots scheduled on volume *Question: *This string can be interpreted in a few different ways. Could anyone tell me which one of the following is the correct interpretation? 1) Snapshots that are scheduled on the volume 2) Snapshots are scheduled on the volume 3) Snapshots have just been scheduled on the volume Kind regards, Yuko Katabami --------------040608070501080904070304 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello all, I have another question I would like to ask: File: LocalizedEnums <div class="moz-signature"> Resource ID: AuditLogType___GLUSTER_VOLUME_SNAPSHOT_SCHEDULED String: Snapshots scheduled on volume Question: This string can be interpreted in a few different ways. Could anyone tell me which one of the following is the correct interpretation? 1) Snapshots that are scheduled on the volume 2) Snapshots are scheduled on the volume 3) Snapshots have just been scheduled on the volume Kind regards, Yuko Katabami </div> <div class="moz-signature"> </div> </body> </html> --------------040608070501080904070304--

2 2

Move to Jboss Wildfly - planned for Monday, June 22nd
by Oved Ourfali 23 Jun '15

23 Jun '15

Hi all! On Monday, June 22nd, 11:00 CET, we plan to drop JBoss 7.1 support in oVirt 3.6 and move to Jboss WildFly 8.2 (we're still doing final verifications, but it looks promising). This will allow us to support Fedora 22 properly, and in future versions to leverage some new and cool features. In addition, Jboss WildFly 8.2 works with OpenJDK 1.8 so you can easily use it for development on newer distributions where OpenJDK 1.7 is not available (Fedora 21 and 22, for example). When the patch [1] is merged, you will need WildFly 8.2 to be able to develop oVirt engine 3.6. Please use following guideline and update your development environment: I. Using WildFly 8.2 for oVirt 3.6 development 1. Enable ovirt-master-snapshot-static repository on your development machine [ovirt-master-snapshot-static] name=Latest oVirt master additional nightly snapshot baseurl=http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/@DI… enabled=1 skip_if_unavailable=1 gpgcheck=0 Please replace "@DIST@" with "fc" for Fedora or "el" for Centos/RHEL 2. Install WildFly packages: yum install ovirt-engine-wildfly ovirt-engine-wildfly-overlay 3. Rebase your patches and build oVirt engine (assuming "~/ovirt-engine" as destination) make install-dev 5. Setup WildFly overlay (assuming "~/ovirt-engine" as destination) echo "ENGINE_JAVA_MODULEPATH=\"/usr/share/ovirt-engine-wildfly-overlay/modules:\${ENGINE_JAVA_MODULEPATH}\"" \ > ~/ovirt-engine/etc/ovirt-engine/engine.conf.d/20-setup-jboss-overlay.conf 6. Execute setup cd ~/ovirt-engine ./bin/engine-setup 7. Start engine service cd ~/ovirt-engine ./share/ovirt-engine/services/ovirt-engine/ovirt-engine.py start II. Using JBoss 7.1.1 for 3.5 environment Using JBoss 7.1.1 on 3.5 is still possible, by doing the following: 1. Install JBoss 7.1.1 RPM from ovirt-master-snapshot-static repo using yum install ovirt-engine-jboss-as 2. Build oVirt engine 3.5 with your backported feature (assuming "~/ovirt-engine" as destination) make install-dev 3. Execute setup cd ~/ovirt-engine ./bin/engine-setup--jboss-home=/usr/share/ovirt-engine-jboss-as 4. Start engine service cd ~/ovirt-engine ./share/ovirt-engine/services/ovirt-engine/ovirt-engine.py start Once merged, we will send an E-mail to make sure you're all aware, and that you can do the steps described above. We're here for any issue you might have (specifically Martin who is responsible for this effort, and myself). Don't hesitate to contact us for any issue, either by mail or irc (mperina or oved). Regards, Oved [1] https://gerrit.ovirt.org/40152

3 6

ssh gerrit.ovirt.org Connection timed out
by yangfeng 23 Jun '15

23 Jun '15

Hi gerrit maintainter Now I cannot ssh gerrit.ovirt.org. It is always timeout. I have create SSH keys following page http://www.ovirt.org/Working_with_oVirt_Gerrit. But I remember ssh used to work. Following is the command output: # ssh -v gerrit.ovirt.org OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /root/.ssh/config debug1: Applying options for gerrit.ovirt.org debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to gerrit.ovirt.org [107.22.212.69] port 29418. debug1: connect to address 107.22.212.69 port 29418: Connection timed out ssh: connect to host gerrit.ovirt.org port 29418: Connection timed out Did anyone meet same issue with me? I am in Beijing, China. Thanks Feng Yang

3 2

spm changes hourly due to unexpected error of getAllTasksStatuses
by like.ma＠cs2c.com.cn 23 Jun '15

23 Jun '15

Hello all, In our ovirt environment(oVirt 3.4.4), we have 2 hosts, and the spm changes hourly between the 2 hosts. In the events of DataCenters there is following message each hour: 'Data Center is being initialized, please wait for initialization to complete' In the vdsm.log i found following error message: Thread-13::ERROR::2015-06-23 13:38:36,667::task::866::TaskManager.Task::(_setError) Task=`e450d7d6-771d-4c51-90b7-c6b10da37897`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 873, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 45, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2125, in getAllTasksStatuses allTasksStatus = sp.getAllTasksStatuses() File "/usr/share/vdsm/storage/securable.py", line 73, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state The attachment is vdsm.log and engine.log. The error occured at 2015-06-23 13:38 and 2015-06-23 15:38 in vdsm.log. (by the way, in the other host the error occured at 2015-06-23 12:38 and 2015-06-23 14:38) And in the engine.log i found following error message: 2015-06-23 13:38:37,933 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (DefaultQuartzScheduler_Worker-34) [781beaea] IrsBroker::Failed::UpdateVMVDS due to: XmlRpcException: <type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0xeb in position 749: invalid continuation byte 2015-06-23 13:38:37,971 ERROR [org.ovirt.engine.core.bll.OvfDataUpdater] (DefaultQuartzScheduler_Worker-34) [781beaea] Exception while trying to update or remove VMs/Templates ovf in Data Center Default.: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: java.lang.reflect.UndeclaredThrowableException (Failed with error VDS_NETWORK_ERROR and code 5022) at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:116) [bll.jar:] at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33) [bll.jar:] at org.ovirt.engine.core.bll.OvfDataUpdater.executeUpdateVmInSpmCommand(OvfDataUpdater.java:383) [bll.jar:] at org.ovirt.engine.core.bll.OvfDataUpdater.performOvfUpdate(OvfDataUpdater.java:163) [bll.jar:] at org.ovirt.engine.core.bll.OvfDataUpdater.updateOvfForVmsOfStoragePool(OvfDataUpdater.java:135) [bll.jar:] at org.ovirt.engine.core.bll.OvfDataUpdater.ovfUpdate_timer(OvfDataUpdater.java:93) [bll.jar:] at sun.reflect.GeneratedMethodAccessor250.invoke(Unknown Source) [:1.7.0_65] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_65] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_65] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:60) [scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz.jar:] Can anyone help? Thanks like.ma(a)cs2c.com.cn

2 2

[oVirt 3.6 Localization Question #20] "Add new Label to"
by Yuko Katabami 23 Jun '15

23 Jun '15

This is a multi-part message in MIME format. --------------060802070401070402040008 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, I would like to ask you another question. * File:***UIConstants *Resource ID:***newLabel *String:***Add new Label to *Question: *Could anyone tell me how / where this string appears in the GUI? In Japanese translation, order of the words is different from English, and I would like to make sure it works when it is shown on the screen. Kind regards, Yuko* * --------------060802070401070402040008 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi, I would like to ask you another question. File: <a class="GOKOG0LCMM active_link">UIConstants</a> <div class="moz-signature">Resource ID: newLabel String: Add new Label to Question: Could anyone tell me how / where this string appears in the GUI? In Japanese translation, order of the words is different from English, and I would like to make sure it works when it is shown on the screen. Kind regards, Yuko </div> </body> </html> --------------060802070401070402040008--

2 3

[oVirt 3.6 Localization Question #19] "The selected proxy Host must be in the destination Storage Pool"
by Yuko Katabami 23 Jun '15

23 Jun '15

This is a multi-part message in MIME format. --------------080709010200010402090907 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello again, Here is another question, * File:***AppErrors *Resource ID:***ACTION_TYPE_FAILED_VDS_NOT_IN_DEST_STORAGE_POOL *String:***Cannot ${action} ${type}. The selected proxy Host must be in the destination Storage Pool. *Question: *In my language, translation for the word "destination may have to be changed depending on the action (i.e. migrate, move, import/export, copy, clone etc). What action is applicable in this case? Thank you, Yuko --------------080709010200010402090907 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello again, Here is another question, File: AppErrors <div class="moz-signature">Resource ID: ACTION_TYPE_FAILED_VDS_NOT_IN_DEST_STORAGE_POOL String: Cannot ${action} ${type}. The selected proxy Host must be in the destination Storage Pool. Question: In my language, translation for the word "destination may have to be changed depending on the action (i.e. migrate, move, import/export, copy, clone etc). What action is applicable in this case? Thank you, Yuko </div> </body> </html> --------------080709010200010402090907--

2 2

[oVirt 3.6 Localization Question #17] "unified affinity group"
by Yuko Katabami 22 Jun '15

22 Jun '15

This is a multi-part message in MIME format. --------------090005010203070603030901 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hello all, I am currently updating the oVirt 3.6 UI translations with other translators and would like to ask you the following question: * File:*** ApplicationConstants *Resource ID:***ACTION_TYPE_FAILED_AFFINITY_RULES_COLLISION *String:*** Affinity Group collision detected in unified affinity group: ${UnifiedAffinityGroups} and negative affinity group: ${negativeAR} *Question: *Is "unified affinity group" referring to "positive affinity group"? (the term is used in http://www.ovirt.org/Features/VM-Affinity and a check box in the New/Edit Affinity Group window) Is this error message is shown when there is a conflict between unified (positive?) affinity group and negative affinity group is found? Thanks in advance, Yuko Katabami --------------090005010203070603030901 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello all, I am currently updating the oVirt 3.6 UI translations with other translators and would like to ask you the following question: File: ApplicationConstants <div class="moz-signature"> Resource ID: ACTION_TYPE_FAILED_AFFINITY_RULES_COLLISION String: Affinity Group collision detected in unified affinity group: ${UnifiedAffinityGroups} and negative affinity group: ${negativeAR} Question: Is "unified affinity group" referring to "positive affinity group"? (the term is used in <a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/VM-Affinity">http://www.ovirt.org/Features/VM-Affinity</a> and a check box in the New/Edit Affinity Group window) Is this error message is shown when there is a conflict between unified (positive?) affinity group and negative affinity group is found? Thanks in advance, Yuko Katabami </div> </body> </html> --------------090005010203070603030901--

2 2

Get involved in oVirt project! Summer edition
by Sandro Bonazzola 22 Jun '15

22 Jun '15

Hi, Summer is here and vacations are near! 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 Gluster repository? You can help us by testing existing online images (like https://getfedora.org/en/cloud/download/) 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 skill? Help us getting VDSM running on it! Debian Jessie has been released a couple of weeks ago and it's a good time for giving it a try. You can follow the progress here: http://www.ovirt.org/VDSM_on_Debian Here are some bugs you can hopefully fix in less that one day or you can just try to reproduce providing info: Bug ID Status Whiteboard Summary 1065350 POST integration hosted-engine should prompt a question at the user when the host was already a host in the engine 1059952 NEW integration hosted-engine --deploy (additional host) will fail if the engine is not using the default self-signed CA 1083104 ASSIGNED integration engine-setup --offline does not update versionlock 1221176 NEW integration hosted-engine accepts FQDNs with underscore while the engine correctly fails on that 1200948 NEW integration hosted-engine-setup should validate the network interface name Do you want something easier? Bug ID Whiteboard Status Summary 1174285 i18n NEW [de-DE] "Live Snapshot Support" reads "Live Snapsnot Support" 772931 infra NEW [RFE] Reports should include the name of the oVirt engine 1143817 integration NEW [TEXT ONLY] - Hosted Engine - Instructions for FQDN are not clear enough 1156060 integration NEW [text] engine admin password prompt consistency 1115059 network NEW Incomplete error message when adding VNIC profile to running VM 734120 storage NEW [RFE] VDSM: use virt-sparsify/zerofree to reduce image size 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=1&project… 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=product%3Aovirt%20white… Do you prefer to test things? We have some test cases[5] you can try using nightly snapshots[6]. You may also help testing: Bug 1234257 - Test upgrade path from EL6 with oVirt 3.5.z to EL7 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! 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/Working_with_oVirt_Gerrit [3] https://gerrit-review.googlesource.com/Documentation [4] http://www.ovirt.org/Community [5] http://www.ovirt.org/Category:TestCase [6] http://www.ovirt.org/Install_nightly_snapshot [7] http://www.ovirt.org/Category:Feature [8] http://www.zdnet.com/article/how-much-longer-can-red-hats-ovirt-remain-cove… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Reminder: Fedora 20 end of life on 2015-06-23
by Sandro Bonazzola 22 Jun '15

22 Jun '15

Hi, just a reminder that Fedora 20 end of life tomorrow[1]. We're still building rpms targeted to Fedora 20 and we still have servers running on Fedora 20 which won't receive security updates anymore. Infra please consider to upgrade / re-provision servers / slaves this week. Since oVirt 3.5 supports Fedora only up to Fedora 20 I think we'll have to continue building packages for it until 3.6 will be out. For 3.6 I suggest to keep Fedora 20 builds until Wildfly support will be in. [1] https://lists.fedoraproject.org/pipermail/announce/2015-May/003267.html -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Live export/import
by Christopher Pereira 21 Jun '15

21 Jun '15

Hi, I would like to migrate a VM between two different ovirt installations with minimum down time. Using a export domain is slow (requires copying twice) and requires to stop the VM. It seems like the best option is to 1) create a snapshot, 2) transfer the backing chain images and OVF files to the destination storage domain 3) stop the VM, 4) transfer the active snapshot and 5) import the VM from the destination storage domain. Can you please comment and suggest other alternatives? Thanks.

2 2

Re: [ovirt-devel] Live export/import
by Christopher Pereira 21 Jun '15

21 Jun '15

I attached a copy of a gluster data storage domain (containing VM images and OVF files) to another 3.6 alpha ovirt installation, but the "Virtual Machines" and "Templates" tabs are empty. Any hint for debugging or known issues? Christopher Pereira <kripper(a)imatronix.cl> wrote: >Hi, > >I would like to migrate a VM between two different ovirt installations with minimum down time. > >Using a export domain is slow (requires copying twice) and requires to stop the VM. > >It seems like the best option is to 1) create a snapshot, 2) transfer the backing chain images and OVF files to the destination storage domain 3) stop the VM, 4) transfer the active snapshot and 5) import the VM from the destination storage domain. > >Can you please comment and suggest other alternatives? > >Thanks. >

1 0

Re: [ovirt-devel] [VDSM] Live snapshot with ceph disks
by Christopher Pereira 20 Jun '15

20 Jun '15

Hi Nir, Regarding "3. Engine creates snapshot *via cinder*"... What are the benefits of creating snapshots via cinder vs via libvirt? Libvirt and qemu are offering core VM-aware storage and memory snapshot features. Besides, snapshot-create-as has no VM downtime. It would be a mistake to implement snapshoting on the ceph layer. At some point, you would need VM-aware code (eg: the VM memory state) and organically go back to the libvirt + qemu way. There seems to be qemu + libvirt support for ceph snapshots (via rbd commands) which probably offers some (?) VM-awareness, but what are the benefits of not using the good old core libvirt + qemu snapshot features? I must be missing something... 2) Not related: It seems like oVirt shifted focus towards Ceph recently... I would like to drop Gluster for Ceph if the latter supports SEEK HOLE reading and optimal sparse files operations. Can someone please confirm if Ceph is supporting SEEK_HOLE? I saw some related code, but would like to ask for comments before setting up and benchmarking Ceph sparse image file operations.

2 1

vdsm master is failing unit tests
by Sandro Bonazzola 18 Jun '15

18 Jun '15

Hi, just an heads up that vdsm on master is failing unit testing: 14:00:25 Ran 1090 tests in 92.403s 14:00:25 14:00:25 FAILED (SKIP=40, errors=7, failures=2) http://jenkins.ovirt.org/job/vdsm_master_unit-tests_merged/297/consoleFull Please fix it. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 1

Re: [ovirt-devel] Libvirt secrets management - take 2
by Oved Ourfali 18 Jun '15

18 Jun '15

On Jun 12, 2015 14:21, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > Recently support for Ceph network disk landed in master. It its possible > now to start a vm using Ceph network disk or hot-plug/unplug such disk > using Cephx authentication. > > However, to make it work, you must add the relevant Ceph secret to > libvirt manually, in the same way it is done in OpenStack deployment. > Our goal is to manage secrets automatically and use ephemeral (safer) > secrets. > > The next patches in the Ceph topic [1], implement secret management in > the same way we manage storage domains or server connections: > > The concept is - all hosts can use all secrets, so you can migrate a vm > using Ceph disk to any host in the cluster. > > 1. When host becomes up, we register the secrets associated with all the > current active domains with libvirt > > 2. When activating a domain, we register the secrets associated with the > new domain with libvirt > > 3. When deactivating a domain, we unregister the secrets associated with > the domain from libvirt > > 4. When moving host to maintenance, we clear all secrets > > 5. When vdsm shutdown or starts, clear all secrets to ensure that we don't keep > stale or unneeded secrets on a host > > This system seems to work, but Federico pointed few issues and suggested > a new (simpler?) approach. > > In future libvirt version, libvirt will support the concept of transient > secrets so you can start a transient vm using secret without registering > the secret with libvirt before starting the vm. The secret will be > specified in the vm XML (for starting a vm) or disk XML (for hot-plug). > This will make our secret management system and APIs useless. When is this planned to be added to libvirt? iiuc, once added, you will no longer need to register the secrets with libvirt, right? > > Managing state on multiple hosts is hard; we will probably have to deal > with nasty edge cases (e.g. lost messages, network errors), which may > lead to host with missing secret, which cannot run some vms. We probably > do this right for storage domains (after 8 years?), and we should not > assume that we are smarter and secret management will work in the first > try. > > The new approach is to *not* manage state or multiple hosts. Instead, > send the required secrets only to the host that starting a vm or > hot-plugging a disk that need a libvirt secret: > > 1. When starting a vm, add the required secrets to the vm description. > On the host, vdsm will register these secrets with libvirt before > starting the vm. > > 2. When migrating a vm, add the required secrets to the vm description. > On the host, vdsm will send these secrets to the destination host, > and on the destination host, vdsm will register the secrets with libvirt > before starting the vm. > Will these secrets be part of the domain xml? If so, no need for special treatment in case of VM migration. > 3. When hot-plugging a disk, send the secret if needed in the disk > description. On the host, vdsm will register the secrets with libvirt. > > 4. When vdsm shutdown or starts, clear all secrets to ensure that we don't keep > stale or unneeded secrets on a host > > 5. We never unregister secrets, since they are ephemeral anyway. > > 6. Alternatively, we can implement secrets reference counting so when a vm > stops or disk is hot-unplugged we decrease the reference count on the > secrets associated with this vm/disk, and if no other vms need the > secret, we can unregister the secret from libvirt. Doesn't seem necessary to me. > > The new approach is simpler, if we avoid the fancy secret reference > counting. I believe we can get it merged in couple of weeks with help > from the virt team. > > Please share your thoughts on these alternative solutions. > Keep in mind also hosted engine. Sounds to me like the new approach will be a better fit for it, as he won't need to deal with storage domain secrets, but just pass it in the VM description... Although I'm not a hosted engine expert, so not sure it makes a difference, but it sounds simpler in that aspect as well. > Thanks, > Nir > > [1] https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:c… > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > >

3 2

help with karma for mom
by Eyal Edri 17 Jun '15

17 Jun '15

Hi, can you please help with karma for new mom pkgs? https://admin.fedoraproject.org/updates/FEDORA-2015-9899/mom-0.4.5-2.fc22 https://admin.fedoraproject.org/updates/FEDORA-2015-9898/mom-0.4.5-2.fc21 https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-6686/mom-0.4.5-2.e… this will reduce custom hacks so that ci jobs will work with nightly builds (rather than take it from epel/fedora) -- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 2

oVirt UI log records persisted in browser's local storage
by Vojtech Szocs 17 Jun '15

17 Jun '15

Hi, with patches [1,2] merged recently into master branch, oVirt UI (WebAdmin and UserPortal) now persists client-side log records in browser's local storage [3] in addition to logging them via console.log API [4]. This means that client-side logs are kept in browser's storage between browser restarts, unless the user manually clears the storage. To inspect "localStorage" object in Firefox: * Menu / Developer / Toggle Tools * on Console tab, type "inspect(localStorage)" Client-side logs now use application-specific key prefix, e.g. "ENGINE_WebAdmin_MyKey" or "ENGINE_UserPortal_MyKey" to avoid clashes. For backwards compatibility (any existing items with un-prefixed keys), UI has a fallback to read the un-prefixed key when the prefixed one is missing. (Newly persisted items always use the key prefix.) In addition to changes above, any uncaught errors that originate from UI code are now properly caught and logged. This means that you shouldn't see uncaught JavaScript errors in browser's error console anymore. Regards, Vojtech [1] https://gerrit.ovirt.org/#/c/25444/ [2] https://gerrit.ovirt.org/#/c/41404/ [3] http://www.w3.org/TR/webstorage/#the-localstorage-attribute [4] https://developer.mozilla.org/en-US/docs/Web/API/Console/log

1 0

CI flag enabled to all projects
by David Caro 17 Jun '15

17 Jun '15

--47eKBCiAZYFK5l32 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi everyone, to ease our current issues, the CI flag has been enabled to all the projects. It will be the only flag that jenkins will set/unset and it c= an also be set by a maintainer. A +1 is required to enable the submit but a -1 will not block (so if jenkins -1 it and a maintainer +1 the +1 prevails). The permissions to the maintainers is added manually, that means that I mig= ht have messed some of them, if you have any issues ping me and I'll check. Any project that does not have any jenkins jobs, will have to get it set manually by a maintainer (or create a jenkins job, that would be best...). Thanks!! --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --47eKBCiAZYFK5l32 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVgRszAAoJEEBxx+HSYmnDiQEIAIB+mB1/JWgaSpEyOnqwumQ/ oKKNUgtGK43dt29dxMSoXT5Z1nUxrvnwDNbx9fDqTY4/x/E2vNvIkR7CrxdI+B/R OGA01EB8x2ZxDxUNiZtRMvTwfwh2IFCgFd1tOujPGgcOxJRUgywWQVaiIuH5SfHv no7WyuEZjzF5JhBHEOUfGGbF/kS4YoDB93rDrwABLQMbk1sKnSe6M2DTpl3hTyBO or+Vbw1n2PmOk+YNQcsJVZr7msz1H4Cmwi1+4M9XdElR3Vj7tTuML7/PMlymiT7F FpetYzm1sHeKBNjtn3iqmfVbgV2DaK+LOH6XbL9B2DBK6g3vq0mqkh9Nt9SiSAI= =Onxt -----END PGP SIGNATURE----- --47eKBCiAZYFK5l32--

1 0

Postponing 3.6.0 second alpha to next week
by Sandro Bonazzola 17 Jun '15

17 Jun '15

Hi, due to instability of the current code, we need to postpone second alpha to next week. Maintainers: - please ensure that all packages you maintain builds in jenkins - please ensure that all the dependencies required by your packages are available either in ovirt repository or in an external repository included in ovirt-release repo files. - please ensure that engine is at least able to add a couple of hosts, create a vm on one host and migrate it to the other one. Infra: - please help keeping jenkins monitored and stabilizing it. Community: - please help testing nightly build while stabilizing it for the second alpha release. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Libvirt secrets management - take 2
by Nir Soffer 16 Jun '15

16 Jun '15

Hi all, Recently support for Ceph network disk landed in master. It its possible now to start a vm using Ceph network disk or hot-plug/unplug such disk using Cephx authentication. However, to make it work, you must add the relevant Ceph secret to libvirt manually, in the same way it is done in OpenStack deployment. Our goal is to manage secrets automatically and use ephemeral (safer) secrets. The next patches in the Ceph topic [1], implement secret management in the same way we manage storage domains or server connections: The concept is - all hosts can use all secrets, so you can migrate a vm using Ceph disk to any host in the cluster. 1. When host becomes up, we register the secrets associated with all the current active domains with libvirt 2. When activating a domain, we register the secrets associated with the new domain with libvirt 3. When deactivating a domain, we unregister the secrets associated with the domain from libvirt 4. When moving host to maintenance, we clear all secrets 5. When vdsm shutdown or starts, clear all secrets to ensure that we don't keep stale or unneeded secrets on a host This system seems to work, but Federico pointed few issues and suggested a new (simpler?) approach. In future libvirt version, libvirt will support the concept of transient secrets so you can start a transient vm using secret without registering the secret with libvirt before starting the vm. The secret will be specified in the vm XML (for starting a vm) or disk XML (for hot-plug). This will make our secret management system and APIs useless. Managing state on multiple hosts is hard; we will probably have to deal with nasty edge cases (e.g. lost messages, network errors), which may lead to host with missing secret, which cannot run some vms. We probably do this right for storage domains (after 8 years?), and we should not assume that we are smarter and secret management will work in the first try. The new approach is to *not* manage state or multiple hosts. Instead, send the required secrets only to the host that starting a vm or hot-plugging a disk that need a libvirt secret: 1. When starting a vm, add the required secrets to the vm description. On the host, vdsm will register these secrets with libvirt before starting the vm. 2. When migrating a vm, add the required secrets to the vm description. On the host, vdsm will send these secrets to the destination host, and on the destination host, vdsm will register the secrets with libvirt before starting the vm. 3. When hot-plugging a disk, send the secret if needed in the disk description. On the host, vdsm will register the secrets with libvirt. 4. When vdsm shutdown or starts, clear all secrets to ensure that we don't keep stale or unneeded secrets on a host 5. We never unregister secrets, since they are ephemeral anyway. 6. Alternatively, we can implement secrets reference counting so when a vm stops or disk is hot-unplugged we decrease the reference count on the secrets associated with this vm/disk, and if no other vms need the secret, we can unregister the secret from libvirt. The new approach is simpler, if we avoid the fancy secret reference counting. I believe we can get it merged in couple of weeks with help from the virt team. Please share your thoughts on these alternative solutions. Thanks, Nir [1] https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:c…

4 14

master broken
by Piotr Kliczewski 16 Jun '15

16 Jun '15

Guys, I attempted to add a host using latest master code and got following exception: 2015-06-16 10:01:28,854 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (http--0_0_0_0_0_0_0_0-8080-3) [14cc5839] CanDoAction of action 'AddVds' failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server 192.168.1.7,VDS_SECURITY_CONNECTION_ERROR,$ErrorMessage Couldn't store fingerprint to db for host 192.168.1.7: javax.persistence.PersistenceException: org.hibernate.id.IdentifierGenerationException: ids for this class must be manually assigned before calling save(): org.ovirt.engine.core.common.businessentities.VdsStatic,VDS_CANNOT_AUTHENTICATE_TO_SERVER 2015-06-16 10:01:41,724 ERROR [org.ovirt.engine.core.utils.transaction.TransactionalInterceptor] (http--0_0_0_0_0_0_0_0-8080-3) [740e96b9] Failed to run operation in a new transaction: javax.persistence.PersistenceException: org.hibernate.id.IdentifierGenerationException: ids for this class must be manually assigned before calling save(): org.ovirt.engine.core.common.businessentities.VdsStatic at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1361) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1289) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1295) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:876) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.jboss.as.jpa.container.AbstractEntityManager.merge(AbstractEntityManager.java:548) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] at org.ovirt.engine.core.dao.jpa.AbstractJpaDao.update(AbstractJpaDao.java:60) [dal.jar:] at org.ovirt.engine.core.dao.VdsStaticDAODbFacadeImpl$Proxy$_$$_WeldSubclass.update(VdsStaticDAODbFacadeImpl$Proxy$_$$_WeldSubclass.java) Thanks, Piotr

3 5

vdsm_master_unit-tests_created and vdsm_master_unit-tests_merged have been disabled
by Sandro Bonazzola 16 Jun '15

16 Jun '15

Hi, I disabled vdsm_master_unit-tests_created and vdsm_master_unit-tests_merged since they get stuck testing jsonrpc and cause jenkins job to grow over 500 jobs taking busy for days the slaves. Please either fix vdsm or the unit tests before enabling these jobs again. Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 5

Repository closure is currently failing for 3.5
by Sandro Bonazzola 16 Jun '15

16 Jun '15

Hi, repository closure is currently failing for 3.5 on: 01:18:15 package: ovirt-optimizer-jboss-0.9-1.el6.noarch from check-custom-el6 01:18:15 unresolved deps: 01:18:15 ovirt-engine-wildfly >= 0:8.2 Since Wildfly support is targeted to 3.6 please provide a 3.5 branch for ovirt-optimizer or give ack for removing ovirt-optimizer from published rpms. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

VDSM from 3.5 branch is currently failing on Fedora 20
by Sandro Bonazzola 16 Jun '15

16 Jun '15

VDSM from 3.5 branch is currently failing on Fedora 20: make[1]: Entering directory `/builddir/build/BUILD/vdsm-4.16.20' make check-local make[2]: Entering directory `/builddir/build/BUILD/vdsm-4.16.20' python -c 'import pyflakes; print("pyflakes-%s" % pyflakes.__version__)' pyflakes-0.7.3 find . -path './.git' -prune -type f -o \ -name '*.py' -o -name '*.py.in' | xargs /usr/bin/pyflakes | \ grep -w -v "\./vdsm/storage/lvm\.py.*: list comprehension redefines 'lv' from line .*" | \ while read LINE; do echo "$LINE"; false; done ./tests/functional/networkTests.py:80: redefinition of unused 'vdsm' from line 43 ./tests/functional/networkTests.py:88: redefinition of unused 'vdsm' from line 43 make[2]: Leaving directory `/builddir/build/BUILD/vdsm-4.16.20' make[2]: *** [check-local] Error 1 make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/builddir/build/BUILD/vdsm-4.16.20' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.fmuLh5 (%check) Please fix it. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

Automated builds and releases
by David Caro 16 Jun '15

16 Jun '15

--kkRamCq5m5VQq0L6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi everyone! In an effort to improve the project workflow and ease the maintenance and improve the quality of the project releases I want to propose start working towards automated builds and releases, the main ideas are the following: * Stop building differently for release and non-release: - Building only once, testing what you build and release what you test - Don't use two different version strings, one for testing and one for release * Automate the build process, and the release process, directly getting the code from the repos (no manual build tarballs) * Adopt semantic versioning, it's a lot more meaningful than the current sc= heme and fits very well with the above points This will ease and lower the maintenance and the extra work required by maintainers, release engineers (sandro) and infra itself by making releases= as easy as hitting a button at any time. That will allow us to lower the time features and fixes get to the users, and deliver packages and builds that h= ave passed through all the tests we have, instead of rebuilding on another env,= at another time, by someone else, and passing only manual testing. wdyt? --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --kkRamCq5m5VQq0L6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVcZDBAAoJEEBxx+HSYmnDT08IAJcqZK4lgNV1DqOTvfXrB7Tl 7f7ceRfBezUVVnwQigvDuUz7LqT9SPO9jaNonFzHHuEiBanaug7W+YUdsFPyIEXF khJriJRocs2brZKFlL4IGfHC1yQGh6FomILAJkIUBWyzo+YJWhtobkfz1346q2dl 8B8k7ReZxTCnrB3Rb+dU0i4XY75IGKX0GFMOHQx9Ws0cFbhQBrqd7vW8svTmuFcY 6mtdzvQBmARqYM/wwkC9lLVUAZ0zlfsEoPAU2JSaSCXNEQkd0cy5XLua1oofUVuv t4epBTRu4RXTwblGwcCqrxC5XUoSerHWM2O7Yv5yaXYa6LP4OXSOy4cvEfju+Zk= =8dph -----END PGP SIGNATURE----- --kkRamCq5m5VQq0L6--

5 6

[ANN] oVirt 3.5.3 Second Release Candidate is now available for testing
by Sandro Bonazzola 16 Jun '15

16 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The oVirt team is pleased to announce that the 3.5.3 Second Release Candidate is now available for testing as of May 28th 2015. The release candidate is available now for Fedora 20, Red Hat Enterprise Linux 6.6, CentOS 6.6 (or similar) and Red Hat Enterprise Linux 7.1, CentOS 7.1 (or similar). This release of oVirt includes numerous bug fixes and one CVE fix for the VENOM Vulnerability. See the release notes [1] for a list of the new features and bugs fixed. Please refer to release notes [1] for Installation / Upgrade instructions. A new oVirt Live ISO is already available as well[2]. Please note that mirrors[3] may need usually one day before being synchronized. Please refer to the release notes for known issues in this release. [1] http://www.ovirt.org/OVirt_3.5.3_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.5-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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVZrrzAAoJEHw3u57E4QAOnX4QAMFi+d4Vq5jnZ0e+LaD1vB9R GmT+k21q6vybjIvovPh7q6StCtPS0sg15BoH5JTmTfl5IWL01qMsFvw/G32PIjZI u3mm2Z3evbxPg9qsqJPyJm/jAlRHv/L6ntLJaJBDPDSO6Y0iqiHTVUQG16easW3L ZnUC2IM5TpHuU3PcgVp8zY9gqFqQWnnsA8deJXBvif9J8RdSf7DnkFha9/Ei3v0E 1btkzt0XVS3Cate8pEaTT8zSoE/tOBBS/D65HsnnZdD13RAxYkolzuPvT+7BlmUO QMhyIE7msWex048HrcDVTEDLrkYF2SpAmYix3sA2O9+AIujenpICHJ8JyxAc+BmJ scsvv99iDLU3wkpMwKiIABj7nE8gIiUbyZBNaxsxQJ0jurLZGHGIhQGLAJ2q/rd7 MTkcDXOBOZHEadqs87mSEzHt1pQCmZ40KSJCvyWbqa7vFv6kyOgOs3PldoizsOyV Z1DlDmfMM8hs/6LOP/Mr/4p/l3JgS3gbOy34L2q9J/B+BX/XU7H2bOk6GTEMVPOn av7m2kDs8DlQJzSqZAURZNt6XTnGGw05THOBWD8NmHuvlVZsSF1mxKb0BC+LpRcs QmLGAtT12Y2Wnq1xwzcRav9+wiIeEYTVJCbyohMLyqTHqPgRstpeF3JulpqILo5I rHhGapreYDlzy06Ki7X7 =pUqF -----END PGP SIGNATURE-----

2 1