WISH: allow to specify VEs boot order for /etc/init.d/vz

[Cédric Dufour]

Binary package hint: vzctl

Hello,

When (re-)starting the host, the OpenVZ startup script (/etc/init.d/vz) starts VEs tagged "ONBOOT" in the order corresponding to their VE number.

In some cases, it may desirable to alter the boot order, for dependencies reasons. An optional "BOOT" file in the VEs configuration directory (/etc/vz/conf) could fit this requirement.

Applies to:
- vzctl 3.0.22-5ubuntu1.1 (Hardy Heron 8.04 LTS)
- vzctl 3.0.22-14ubuntu2 (Jaunty Jackalope 9.04)

Hope this could be of help to others.

Cheers

[Daniel Hahler (blueyed)]

Thank you attacking this, I think it's a really useful wish.

However, the implementation should make sure, that any "ONBOOT" containers get started.
I propose to use the "BOOT" file, but append any containers not listed in there to the generated list.

What do you think?

Anyway, this is a nice feature and should get implemented upstream, not in Ubuntu, Debian or other distributions only.
Please forward it to http://bugzilla.openvz.org/ and then link it here (via "Also affects project"). They might have something in mind to implement this already, or can help with getting it done.

Thanks!

[Cédric Dufour (cdufour-keyword-ubuntu-086000)]

Hello Daniel,

I think you're right... follows a revised patch which does not brake the expected behavior of the "ONBOOT" parameter. Human-friendly put:
 - first use the (valid/ONBOOT) VEIDs in the BOOT_ORDER file
 - then add the ONBOOT VEIDs that do not appear in the BOOT_ORDER file

I will also propose the patch upstream and see what gives.

Cheers

[Daniel Hahler (blueyed)]

Should be fixed in 3.0.24, which hopefully makes it into Ubuntu Maverick still (bug 628965).

[Simon Déziel (sdeziel)]

http://bugzilla.openvz.org/show_bug.cgi?id=1300 says that this is implemented in vzctl >= 3.0.24 so marking this "Fix Released"