- Devel - oVirt List Archives

[Engine-devel] Network labeling requirements follow up questions
by Malini Rao 13 Jan '14

13 Jan '14

Livnat, I had asked a couple of questions about network labeling reqs offline but wanted to continue the discussion on the list. Thank you for the answers and I have copied my questions and your answers for context - 1. Can a network be part of several labels? Currently not, we are not sure if there is a use case for that ATM, but I hope users would surprise us with an interesting use case. 2. Can a network exist as a available network in the Setup Host networks dialog on its own even if it is part of a label? i.e, can a network be assigned to a NIC on its own and to another NIC as part of a label? Network can not be provisioned twice on the same host (regardless of labels). With regard to your answer to my question 2, I understand that the network cannot be provisioned twice on the same host but it can be provisioned to multiple hosts... right? So, Let's say the Green network is part of a label called label 1 which also includes yellow and red networks, and let's say Host 1 is provisioned using label 1 and so it can use green, yellow and red networks. For Host 2, can I provision with just Green rather than with Label 1? Or can a network be used only once in a label and across hosts? Thanks Malini

3 4

[Engine-devel] ovirt-engine 3.3.3 branching
by Sandro Bonazzola 13 Jan '14

13 Jan '14

Hi, this is just a reminder we're going to build ovirt-engine 3.3.3 beta today. We're going to branch ovirt-engine around 10am EST to allow you to get your patches in. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Engine-devel] [ATN][devenv] action required when rebasing on latest master
by Alon Bar-Lev 12 Jan '14

12 Jan '14

Hello, After rebasing to latest master (at least 08be92), if you want to reuse your prefix, please: $ rm -fr "${HOME}/ovirt-engine/share/ovirt-engine/setup" $ make install-dev PREFIX="${HOME}/ovirt-engine" DEV_REBUILD=0 This will remove some leftovers and allow you to reuse your current prefix. I submitted a patch[1] to automate this process, I hope it will be merged soon, but its effect is only for the N+1 deployment. Sorry for the inconvenience. Regards, Alon Bar-Lev. [1] http://gerrit.ovirt.org/#/c/22895/

1 0

[Engine-devel] oVirt 3.4.0 alpha repository closure failure
by Sandro Bonazzola 10 Jan '14

10 Jan '14

Hi, oVirt 3.4.0 alpha repository has been composed but alpha has not been announced due to repository closure failures: on CentOS 6.5: # repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 8 base epel glusterfs-epel glusterfs-noarch-epel ovirt-3.3.2 ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 16581 package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha unresolved deps: procps-ng package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.el6.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.el6 package: ovirt-engine-sdk-java-3.4.0.1-1.el6.noarch from ovirt-3.4.0-alpha unresolved deps: httpcomponents-client >= 0:4.2 apache-commons-logging apache-commons-beanutils package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha unresolved deps: vhostmd On Fedora 19: # repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates -l ovirt-stable Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 4 fedora ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 38832 package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19 package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: openstack-java-resteasy-connector >= 0:3.0.2 openstack-java-quantum-model >= 0:3.0.2 openstack-java-quantum-client >= 0:3.0.2 openstack-java-keystone-model >= 0:3.0.2 openstack-java-keystone-client >= 0:3.0.2 openstack-java-glance-model >= 0:3.0.2 openstack-java-glance-client >= 0:3.0.2 openstack-java-client >= 0:3.0.2 package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: ovirt-engine-dwh >= 0:3.4.0 On Fedora 20 (ovirt-stable doesn't support Fedora 20): # repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 3 fedora ovirt-3.4.0-alpha updates Num Packages in Repos: 38822 package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19 package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: openstack-java-resteasy-connector >= 0:3.0.2 openstack-java-quantum-model >= 0:3.0.2 openstack-java-quantum-client >= 0:3.0.2 openstack-java-keystone-model >= 0:3.0.2 openstack-java-keystone-client >= 0:3.0.2 openstack-java-glance-model >= 0:3.0.2 openstack-java-glance-client >= 0:3.0.2 openstack-java-client >= 0:3.0.2 package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: ovirt-engine-dwh >= 0:3.4.0 Please fix dependencies / provide missing packages / provide additional repositories as soon as possible. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 5

Re: [Engine-devel] [Users] [QE] 3.4.0 Release tracker
by Itamar Heim 10 Jan '14

10 Jan '14

On 01/08/2014 10:51 AM, Markus Stockhausen wrote: >> integration 1037663 F20 - ovirt-log-collector: conflicts with file from package sos-3.0-3.fc20.noarch > > Given the fact that F20 is already relased and Ovirt 3.4.0 is intended to support it ... shouldn't that be a blocker? well, it could also be released async if it has too many issues, but worth tracking, and having it for the test day. I haven't seen the log collector used much (at all) when ovirt folks ask for help, so we could release without it for testing.

1 0

[Engine-devel] ovirt-specs project needed
by Sandro Bonazzola 10 Jan '14

10 Jan '14

Hi, can you please create a new gerrit project named ovirt-specs? it will contain .spec files for needed packages not provided by downstream distributions. It will contain: - httpcomponents-core (needed by java sdk, missing on CentOS) - httpcomponents-client (needed by java sdk, missing on CentOS) It should contain also jasper server, actually in its own repository and jboss actually packaged by us but without a git repo for the spec file. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 4

[Engine-devel] oVirt 3.4.0 alpha delayed
by Sandro Bonazzola 10 Jan '14

10 Jan '14

Hi, oVirt 3.4.0 alpha will be delayed due to packages dependencies issue. Maintainers are already working on this, alpha will be released just after all dependency issues will have been fixed. Details on dependency missing: on CentOS 6.5: [ovirt-3.4.0-alpha] name=Alpha builds of the oVirt 3.4 project baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/$releasever/ enabled=1 skip_if_unavailable=1 gpgcheck=0 # repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 8 base epel glusterfs-epel glusterfs-noarch-epel ovirt-3.3.2 ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 16581 package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha unresolved deps: procps-ng package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.el6.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.el6 package: ovirt-engine-sdk-java-3.4.0.1-1.el6.noarch from ovirt-3.4.0-alpha unresolved deps: httpcomponents-client >= 0:4.2 apache-commons-logging apache-commons-beanutils package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha unresolved deps: vhostmd On Fedora 19: [ovirt-3.4.0-alpha] name=Alpha builds of the oVirt 3.4 project baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$release… enabled=1 skip_if_unavailable=1 gpgcheck=0 # repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates -l ovirt-stable Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 4 fedora ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 38832 package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19 package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: openstack-java-resteasy-connector >= 0:3.0.2 openstack-java-quantum-model >= 0:3.0.2 openstack-java-quantum-client >= 0:3.0.2 openstack-java-keystone-model >= 0:3.0.2 openstack-java-keystone-client >= 0:3.0.2 openstack-java-glance-model >= 0:3.0.2 openstack-java-glance-client >= 0:3.0.2 openstack-java-client >= 0:3.0.2 package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: ovirt-engine-dwh >= 0:3.4.0 On Fedora 20 (ovirt-stable doesn't support Fedora 20): [ovirt-3.4.0-alpha] name=Alpha builds of the oVirt 3.4 project baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$release… enabled=1 skip_if_unavailable=1 gpgcheck=0 # repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 3 fedora ovirt-3.4.0-alpha updates Num Packages in Repos: 38822 package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19 package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: openstack-java-resteasy-connector >= 0:3.0.2 openstack-java-quantum-model >= 0:3.0.2 openstack-java-quantum-client >= 0:3.0.2 openstack-java-keystone-model >= 0:3.0.2 openstack-java-keystone-client >= 0:3.0.2 openstack-java-glance-model >= 0:3.0.2 openstack-java-glance-client >= 0:3.0.2 openstack-java-client >= 0:3.0.2 package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha unresolved deps: ovirt-engine-dwh >= 0:3.4.0 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[Engine-devel] oVirt 3.4.0 release schedule updated
by Sandro Bonazzola 09 Jan '14

09 Jan '14

oVirt team has updated the release schedule for 3.4.0 [1] These are tentative planning dates and may change General availability: 2014-02-24 oVirt 3.4 Second Test Day: 2014-02-19 RC Build: 2014-02-17 oVirt 3.4 Test Day: 2014-01-27 Beta release: 2014-01-20 Branching / Feature freeze: 2014-01-15 Alpha release: 2014-01-09 more details on test days, etc to come in the next few weeks [1] http://www.ovirt.org/OVirt_3.4_release-management#Timeline -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 4

[Engine-devel] Fwd: Re: oVirt 3.3.3 tracker
by Sandro Bonazzola 09 Jan '14

09 Jan '14

Adding VDSM and devel list. -------- Messaggio originale -------- Oggetto: Re: oVirt 3.3.3 tracker Data: Wed, 08 Jan 2014 22:03:07 +0200 Mittente: Itamar Heim <iheim(a)redhat.com> A: Sandro Bonazzola <sbonazzo(a)redhat.com>, arch <arch(a)ovirt.org>, Doron Fediuck <dfediuck(a)redhat.com>, Dave Neary <dneary(a)redhat.com>, "users(a)ovirt.org" <users(a)ovirt.org> On 01/08/2014 07:04 PM, Sandro Bonazzola wrote: > Hi, > during today oVirt sync meeting it has been decided to release oVirt 3.3.3 [1] just after 3.4.0 alpha. > 3.4.0 alpha will be composed tomorrow using next nightly build rpms. > > It has been proposed to build 3.3.3 beta next Monday, so here is the proposed schedule: > > General availability: 2014-01-28 > RC Build: 2014-01-21 > Beta release: 2014-01-13 make sense. > > A tracker bug has been created for blockers tracking: BZ 1050084 - Tracker: oVirt 3.3.3 release > > We still have ~30 bugs targeted to 3.3.3 [2], please update target releases and add blocker bugs to the tracker. I asked for 3.3.4 target release to be added, but i think folks should consider if to push bugs to 3.3.4, or to 3.4.0 by now. I've added users mailing list, in case there is a specific bug someone would like to highlight a specific bug that should go into 3.3.3 or 3.3.4. > > Waiting approval before preparing the email for other mailing lists. > > [1] http://www.ovirt.org/OVirt_3.3.z_release-management#oVirt_3.3.3 > [2] http://red.ht/1cOYkMo >

1 0

[Engine-devel] 3.4 ReleasePlan / missing branches?
by Sven Kieske 07 Jan '14

07 Jan '14

Hi, according to: http://www.ovirt.org/OVirt_3.4_release-management Feature Freeze for 3.4. was 31.12.2013 But I can not find any branches for 3.4 release in gerrit.ovirt.org. Shouldn't there be branches for this version or is anybody aware that there can't get any new features into master after 31.12. ? Or will additional features get into 3.4 or is the feature freeze date for 3.4 in the wiki not correct? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

3 3