[lxc-devel] Default Namespace

[Maheswara Reddy C - ERS, HCL Tech]

Hi,
Requirement is, internally we can maintain N number of namespaces(net), but we are exposing one namespace(default) which will communicate with external system and with other N namespaces (processes inside the these should not communicate but only with default namespace).


Thanks
Mahesh


-----Original Message-----
From: Rob Landley [mailto:rlandley at parallels.com]
Sent: Friday, February 25, 2011 12:57 AM
To: Maheswara Reddy C - ERS, HCL Tech
Cc: lxc-devel at lists.sourceforge.net
Subject: Re: [lxc-devel] Default Namespace

On 02/24/2011 07:52 AM, Maheswara Reddy C - ERS, HCL Tech wrote:
> Hi, How can we create common default namespace which can be
> communicated with all the other namespaces.

What does that mean?

When you say "namespace", there's the mount namespace, network
namespace, PID namespace, /dev namespace, and several others.  Each can
be individually unshared, meaning siblings processes can see the same
network but different filesystems and neither of them have the full
device list their parent has.

As for "communicate": they can communicate.  You can set up a network
routing between different network namesapces.  You can mount shared
filesystems between different filesystem namespaces.  You can
communicate to the outside world through /dev nodes in a unique device
namespace.

Please explain: what are you trying to _do_?

Rob

::DISCLAIMER::
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

-----------------------------------------------------------------------------------------------------------------------