On Jan 17, 2008 12:55 PM, Vivek Kashyap <kashyapv@us.ibm.com> wrote:
On Thu, 17 Jan 2008, Shuveb Hussain wrote:
On Jan 17, 2008 2:30 AM, Dan Smith <danms@us.ibm.com> wrote:
DL> <network> DL> <ipaddress>192.168.1.110</ipaddress> DL> <hostname>browndog</hostname> DL> <gateway>192.168.1.1</gateway> DL> <nameserver>192.168.1.1</nameserver> DL> <netmask>255.255.255.0</netmask> DL> </network>
This is me showing my complete ignorance here, but can you enforce the hostname inside a container like that? I would expect that to be done by the init scripts inside a container, much like a real machine.
It is most flexible to manage virtual machines from the base machine on which they run. The idea is to run an agent on the base machine alone that is able to configure all virtual machines without the need to have agents inside of each of the virtual machines. When an OpenVZ VPS is being created, the tools actually set /etc/resolv.conf and also
Containers would similarly be managed from the init namespace.
[On 2.6.24 kernel ensure you have cgroup and controllers support included - CGROUP_* set of config options. Then mount as follows -
mount -t cgroup -o ns none /containers]
If a Container is clone()ed now it will automatically show up in /containers as node_<pid> of the child. One can then rename this to the desired name as well as pass the desired hostname as part of the configuration for the Container wherein its init task/script can set the hostname.
Am I understanding and correlating the above correctly to what you mention wrt OpenVZ?
You are correct. Also, like mentioned before the container(its init script) is responsible for picking up its networking parameters and setting it up. Thanks, -- Shuveb Hussain B I N A R Y K A R M A Chennai, India. Phone : +91 44-64621656 Mobile: +91 98403-80386 http://www.binarykarma.com