Re: Keeping the VEs upon hardware machine reinstall? [message #29858 is a reply to message #29857] |
Sun, 27 April 2008 14:09 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
ArsDangor
Messages: 6 Registered: March 2008
|
Junior Member |
|
|
"matatrus" | b) VE.conf file is responsible for the last two items.
So, for example what value of PRIVVMPAGES do you expect from the following command?
Quote:
vzctl create 10000 --noostemplate --private /vz/private/10000
| I don't care. I'd expect the same PRIVVMEMPAGES as if I run vzctl create 1000 --private /vz/private/1000 --ostemplate cern-4-x86_64-default To make this easier to understand, (sorry for spamming), I'm integrating OpenVZ VE management within Quattor. My code performs something like this:
if ! vzlist 1000
then
vzctl create 10000 --private /vz/private --ostemplate cern-4-x86_64-default
fi
vzctl set 1000 --privvmempages <privvmempages> --diskspace <diskspace> --hostname <hostname>...
vzctl start 1000
So, my "--noostemplate" requirement would be just another "if" inside the first if statement. Simple to me, and transparent for my users, if it was at all supported.
"curx" | move /etc/vz/conf to your /vz/conf(ig) and create a symlink from
/etc/vz/conf -> /vz/conf
|
Yes, this workaround will work with our framework. Thanks! Although it would be simpler for users to avoid this...
Cheers.
If all the world is a stage, I want better ligthting.
|
|
|