Re: Startup delay for VMs in a cluster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dirk H. Schulz schrieb:
Hi folks,

the VMs in my cluster are defined via <vm> containers which are not inside <service> containers because the latter prevents live migration (as far as I could find out).

Now when I start up the cluster, all VMs are started at once, which I would like to prevent. Is there any way to define a startup sequence or startup delay (like you can for the xendomains service) without misusing dependencies?

Dirk

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
Just for the archive: I have an idea now.

I will try defining soft dependencies between the VMs (as I understand soft is only regarded at startup), so I can have a startup sequence which is even more than just a startup delay.

Any reasons why this should not work?

Dirk

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux