On Tue, Dec 1, 2015 at 9:42 AM, Shahar Havivi <shaharh@redhat.com> wrote:
Hello, is it correct that even if I use cloud-init I have to seal my candidate VM before making it a template? Well it depend, If you have a common initialization you can run cloud-init before sealing
On 01.12.15 09:03, Gianluca Cecchi wrote: the template, its more reasonable to create a template and run cloud-init on each VM that created from this template.
In that case what is the correct approach to pre-seal a CentOS 7 VM? Also, for operating system like Fedora >=20 and/or RHEL/CentOS 7 should I unconfigure NetworkManager before sealing them, using classic network service, or what? Yes the NetworkManager can override cloud-init network settings.
OK, I'm trying using classic network instead of NetworkManager. But right before running the "make template" action, do I have to run any of "sys-unconfig" and/or "virt-sysprep" tools? - sys-unconfig I see in its man page: "This utility should not be used for creating cloud or virtual machine images. For that use please see virt-sysprep" Does this note apply also in my scenario where I want to seal a VM in oVirt before making a template from it? - virt-sysprep It should be run "out of band" against a disk of a powered off VM if I understood correctly. Is it applicable in my case with oVirt and a disk that actually is on a storage domain? It seems more applicable in a plain Qemu?KVM environment... It remains open the question about how to properly seal a RHEL 7 / CentOS 7 VM/OS. Thanks, Gianluca