Re: [Users] [vdsm] [QE] oVirt 3.3.2 beta status

Am 28.11.2013 11:10, schrieb Michal Skrivanek: > [resent, accidentally took out the list] > > On Nov 28, 2013, at 08:30 , Itamar Heim <iheim(a)redhat.com&gt; wrote: > >> On 11/27/2013 05:42 PM, Michal Skrivanek wrote: >>>> virt 1029885 cloud-init testcase does not work in engine 3.3.1 >>> this is about current CentOS containing a quite dated version of cloud-init. There's little we can do except encourage people to build/use 0.7.2+ >>> Awaiting reporter's feedback >> >> as rhel 6.5 GA'd and has these properly, shouldn't be an issue, and should be in CentOS 6.5 as well. > > Yes, but this still leaves older guests without a solution. Maybe we should really push for virt-sysprep as it is much more mature in sense of legacy compatibility, nothing extra needed inside the guest. At least a simple passthrough of some basic stuff (we have only a basic stuff in cloud-init anyway). > It's slightly different approcha than cloud-init, but may be really worth it even long term... Well, I reported the cloud-init bug. atm I write a helper script to parse the cloud-init data myself. virt-sysprep cannot set IP-Information beside the MAC out of the box, so this is also no solution. I feel like there must be made some huge efforts to be able to automate vm deployment. I can't believe I'm the only one who needs this features. how do you deploy vms? set everything up by hand? do you always install $latest_OS_version with selfcompiled software?

that's not always possible, especially for production environments. See also my other mail regarding IPv6 Support in Cloud-Init and no proper static networking support.