Sealing the VM is not something specific to oVirt, and is also valid for KVM.
Actually sealing the VM is to run virt-sysprep against the VM/disk.
You can check
http://libguestfs.org/virt-sysprep.1.html and especially the
--list-operations which can help you understand what ia being cleaned up.
So you can:
1. Update the VM
2. Install and enable cloudinit service
3. Maybe try to create your ansible user and allow ssh keys (Using ansible over root is
not good and is a bad practice)
4. Power off and seal the machine as a template (details at
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtuali...
)
5. Create VM from the template and power it up manually.
6. Verify that the new VM matches your needs and remove.
About cloud init - you should know that is used extensively in OpenStack and VmWare has
it's own solution similar to CloudInit.
Some examples can be found at:
https://cloudinit.readthedocs.io/en/latest/topics/examples.html
So you can change passwords, configure network, create your ansible user with necessary
permissions and way more.
Best Regards,
Strahil NikolovOn Dec 23, 2019 18:46, jeremy_tourville(a)hotmail.com wrote:
Thank you for your reply Luca,
In general your work flow is helpful and makes sense to me.
I meant to say above- "As part of the template creation process ***the Ovirt docs***
say to seal the VM".
So I think I understand that you need to use both processes (seal template + cloudinit)
to get everything to work as desired. I'd still appreciate any more specifics about
what sealing a VM does.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BRLNWOQB6FM...