[vdsm] ovirt 3.3 RC packages
Dear maintainers, As you probably know, we're heading towards the 3.3 release of ovirt. I'd like to get a short status about your project, and it's readiness for the upcoming release. If your project is blocker free, please let me know of the relevant build to pick up into the RC repo. Current known blockers (as in https://bugzilla.redhat.com/show_bug.cgi?id=918494 - Tracker: oVirt 3.3 release): ovirt-engine 984586 ovirt-engine-backendinfra Cannot start a VM with USB Native - Exit message: internal error Could not format channel target type. 988299 ovirt-engine-core gluster Impossible to start VM from Gluster Storage Domain 987939 ovirt-engine-installer integration engine-setup - engine-cleanup - engine-setup - fails vsdm 988004 vdsm network [vdsm] OSError: [Errno 2] No such file or directory: '/sys/class/net/ovirtmgmt/brif' 988065 vdsm virt Migration fails - AttributeError: 'ConsoleDevice' object has no attribute 'alias' 988397 vdsm network ovirt-node post-installation setup networks fails when NetworkManager is running 988990 vdsm network oVirt 3.3 - (vdsm-network): netinfo - ValueError: unknown bridge ens3 990854 vdsm network Multiple Gateways: Upgrade VDSM to 3.3 must reconfigure networking on host 990963 vdsmvdsm must require selinux-policy-3.12.1-68.fc19 ovirt-node 988986 ovirt-node libvirt network directory is not persisted other = 990509 selinux-policy Current selinux policy prevents running a VM with volumes under /var/run/vdsm/storage Thanks, Ofer Schreiber ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Engine-devel] ovirt 3.3 RC packages
On 08/07/2013 01:42 PM, Ofer Schreiber wrote: Dear maintainers, As you probably know, we're heading towards the 3.3 release of ovirt. I'd like to get a short status about your project, and it's readiness for the upcoming release. If your project is blocker free, please let me know of the relevant build to pick up into the RC repo. Current known blockers (as in https://bugzilla.redhat.com/show_bug.cgi?id=918494 - Tracker: oVirt 3.3 release): ovirt-engine 984586 ovirt-engine-backendinfra Cannot start a VM with USB Native - Exit message: internal error Could not format channel target type. 988299 ovirt-engine-core gluster Impossible to start VM from Gluster Storage Domain There's an issue with running this on CentOS 6.4 as there is no qemu 1.3 available for this distro. Deepak (deepakcs) has initiated a conversation asking for inputs on how to handle this dependency. We could take a call based on the resolution. 987939 ovirt-engine-installer integration engine-setup - engine-cleanup - engine-setup - fails vsdm 988004 vdsm network [vdsm] OSError: [Errno 2] No such file or directory: '/sys/class/net/ovirtmgmt/brif' 988065 vdsm virt Migration fails - AttributeError: 'ConsoleDevice' object has no attribute 'alias' 988397 vdsm network ovirt-node post-installation setup networks fails when NetworkManager is running 988990 vdsm network oVirt 3.3 - (vdsm-network): netinfo - ValueError: unknown bridge ens3 990854 vdsm network Multiple Gateways: Upgrade VDSM to 3.3 must reconfigure networking on host 990963 vdsmvdsm must require selinux-policy-3.12.1-68.fc19 ovirt-node 988986 ovirt-node libvirt network directory is not persisted other = 990509 selinux-policy Current selinux policy prevents running a VM with volumes under /var/run/vdsm/storage Thanks, Ofer Schreiber ___ Engine-devel mailing list engine-de...@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] How to handle qemu 1.3 dep for Gluster Storage Domain
On 08/07/2013 08:21 AM, Sahina Bose wrote: [Adding engine-devel] On 08/06/2013 10:48 AM, Deepak C Shetty wrote: Hi All, There were 2 learnings from BZ https://bugzilla.redhat.com/show_bug.cgi?id=988299 1) Gluster RPM deps were not proper in VDSM when using Gluster Storage Domain. This has been partly addressed by the gluster-devel thread @ http://lists.gnu.org/archive/html/gluster-devel/2013-08/msg8.html and will be fully addressed once Gluster folks ensure their packaging is friendly enuf for VDSM to consume just the needed bits. Once that happens, i will be sending a patch to vdsm.spec.in to update the gluster deps correctly. So this issue gets addressed in near term. 2) Gluster storage domain needs minimum libvirt 1.0.1 and qemu 1.3. libvirt 1.0.1 has the support for representing gluster as a network block device and qemu 1.3 has the native support for gluster block backend which supports gluster://... URI way of representing a gluster based file (aka volume/vmdisk in VDSM case). Many distros (incl. centos 6.4 in the BZ) won't have qemu 1.3 in their distro repos! How do we handle this dep in VDSM ? Do we disable gluster storage domain in oVirt engine if VDSM reports qemu 1.3 as part of getCapabilities ? or Do we ensure qemu 1.3 is present in ovirt.repo assuming ovirt.repo is always present on VDSM hosts in which case when VDSM gets installed, qemu 1.3 dep in vdsm.spec.in will install qemu 1.3 from the ovirt.repo instead of the distro repo. This means vdsm.spec.in will have qemu = 1.3 under Requires. Is this possible to make this a conditional install? That is, only if Storage Domain = GlusterFS in the Data center, the bootstrapping of host will install the qemu 1.3 and dependencies. (The question still remains as to where the qemu 1.3 rpms will be available) hosts are installed prior to storage domain definition usually. we need to find a solution to having a qemu 1.3 for .el6 (or another version of qemu with this feature set). What will be a good way to handle this ? Appreciate your response thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
