On Sat, Sep 16, 2017 at 3:47 AM, Julián Tete <danteconrad14@gmail.com> wrote:
You are absolutely right Ondra. Thank You
Also to me seems ok, is similar to the configuration we're using to deploy.
I have three questions for you:
1) How does this work ? Ansible creates the configuration disk?
You mean cloud-init configuration-disk? no, the work is directly done by oVirt. oVirt knows what you want to put into the configuration drive and creates a new cdrom device with the configuration drive to be attached directly to the vm during "Run Once". Once restarted with standard "Run" the device disappears.
2) How can I do to disable cloud-init after execution, maybe a script that runs systemd disable cloud-init.service and systemd mask cloud-init.service. There is little documentation about it
I simply run a task after first successful boot with cloud-init that runs yum erase -y cloud-init
3) If you would like to turn off or on a huge set of virtual machines how you can group them to do so. Without having to do a Task for each one
What do you mean grouping? via engine interface you can apply a tag to them and then lookup by tag, select all and shutdown. -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet è la più grande biblioteca del mondo. Ma il problema è che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , <lorenzetto.luca@gmail.com>