[ovirt-users] workflow suggestion for the creating and destroying the VMs?

Yaniv Kaul ykaul at redhat.com
Fri Jul 21 13:58:13 UTC 2017


On Fri, Jul 21, 2017 at 6:07 AM, Arman Khalatyan <arm2arm at gmail.com> wrote:

> Yes, thanks for mentioning puppet, we have foreman for the bare metal
> systems.
> I was looking something like preboot hook script, to mount the /dev/sda
> and copy some stuff there.
> Is it possible to do that with cloud-init/sysprep?
>

It is.

However, I'd like to remind you that we also have some scale-up features
you might want to consider - you can hot-add CPU and memory to VMs, which
in some workloads (but not all) can be helpful and easier.
(Hot-removing though is a bigger challenge.)
Y.

>
> On Thu, Jul 20, 2017 at 1:32 PM, Karli Sjöberg <karli at inparadise.se>
> wrote:
>
>>
>>
>> Den 20 juli 2017 13:29 skrev Arman Khalatyan <arm2arm at gmail.com>:
>>
>> Hi,
>> Can some one share an experience with dynamic creating and removing VMs
>> based on the load?
>> Currently I am just creating with the python SDK a clone of the apache
>> worker, are there way to copy some config files to the VM before starting
>> it ?
>>
>>
>> E.g. Puppet could easily swing that sort of job. If you deploy also
>> Foreman, it could automate the entire procedure. Just a suggestion
>>
>> /K
>>
>>
>> Thanks,
>> Arman.
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170721/1d7bd9e2/attachment.html>


More information about the Users mailing list