On 03/14/2013 12:49 PM, Dirk Müller wrote:
the "we" in this case was the SUSE Cloud team. if "SUSE Cloud" is continue to support Xen, then we need to solve the issue without a package overlay. either by upgrading libvirt, by fixing the old libvirt or by somehow adding a kludge to our openstack packages. Which way is the best needs to be investigated first.
I thought SUSE Cloud will live in a subproject in the ISV project and _not_ in C:O? I don't like that we have to do things, because there are requirement of the SUSE Cloud. And I don't like that we can't simply provide a newer libvirt package because a requirement of the SUSE Cloud is to not overlay existing packages in SLE. Also I don't like it to add patches to the packages in C:O only to workaround issues in the SUSE Cloud existing because of some requirements of the SUSE Cloud. If a newer libvirt package is a problem for the SUSE Cloud you can simply remove the libvirt package in the SUSE Cloud repository (in the ISV project) and add needed patches to workaround existing issues there. But using workarounds to support older versions of libvirt or creating bugreports for SLE to backport bugfixes to 0.9.6 (when SLES11 SP3 will provide a newer version of libvirt..) is not the way I want to go. It's nice that SLES11 SP3 will include a newer libvirt package, but we need the newer libvirt now and not in a few months. We should clarify how to proceed with such issues in C:O. In my understanding: C:O != SUSE Cloud. Christian. -- Christian Berendt Cloud Computing Solution Architect Tel.: +49-171-5542175 Mail: berendt@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org