On 06/01/2010 11:26 PM, Christian Haintz wrote:
> Hi,
>
> At first, thanks for all the great feedback and the quickly ongoing
> development to lxc.
>
> On May 13, 2010, at 11:22 PM, Daniel Lezcano wrote:
>
>> On 05/13/2010 06:17 PM, Christian Haintz wrote:
>>> 6) is LXC production ready?
>>
>> yes
Hi,
At first, thanks for all the great feedback and the quickly ongoing
development to lxc.
On May 13, 2010, at 11:22 PM, Daniel Lezcano wrote:
On 05/13/2010 06:17 PM, Christian Haintz wrote:
6) is LXC production ready?
yes and no :)
If you plan to run several webserver (not a full syst
> > 3) Is there support for tun/tap device
>
> The drivers are ready to be used in the container but not
> sysfs and that
> unfortunately prevent to create a tun/tap in a container.
>
> sysfs per namespace is on the way to be merged upstream.
The workaround here is to create a TUN/TAP on the h
On 05/13/2010 06:17 PM, Christian Haintz wrote:
> Hi,
>
> At first LXC seams to be a great work from what we have read already.
>
> There are still a few open questions for us (we are currently running
> dozens of OpenVZ Hardwarenodes).
>
> 1) OpenVZ in the long-term seams to be a dead end. Will LX
On Thu, 13 May 2010, Christian Haintz wrote:
> Hi,
>
> At first LXC seams to be a great work from what we have read already.
>
> There are still a few open questions for us (we are currently running
> dozens of OpenVZ Hardwarenodes).
I can't answer for the developers, but here's my answers/observ
Hi,
At first LXC seams to be a great work from what we have read already.
There are still a few open questions for us (we are currently running
dozens of OpenVZ Hardwarenodes).
1) OpenVZ in the long-term seams to be a dead end. Will LXC be a
feature complete replacement for OpenVZ in the 1.0
