Re: [Lxc-users] Control panel

[Ulli Horlacher]

On Mon 2011-04-18 (19:40), Daniel Lezcano wrote:
> On 04/17/2011 09:47 AM, Ulli Horlacher wrote:
> 
> >
> > I will integrate the other lxc basic commands as soon the phys nic
> > renaming bug is solved.
> 
> The bug is coming from the kernel and the network namespace life cycle.
> 
> As we changed the name 'eth1' in the host to 'eth0' in the container, 
> when the container exits, the kernel detect the conflict name with the 
> 'eth0' from the host and rename container's 'eth0' to 'dev%d'.
> As a workaround, I think setting lxc.network.name = eth1 in the 
> container should fix the problem 

Great! This works! 
And is an acceptable workaround until a final (kernel) fix!



-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Daniel Lezcano]

On 04/17/2011 09:47 AM, Ulli Horlacher wrote:
>
> I will integrate the other lxc basic commands as soon the phys nic
> renaming bug is solved.

The bug is coming from the kernel and the network namespace life cycle.

When the network namespace dies, the physical nic is moved back to the 
host. Unfortunately, the last process of the container can exit making 
lxc to rename 'devX' to the original name but that may fail because the 
network namespace could be still alive. That happens, for example, when 
there are TCP orphan sockets waiting for a timer to expire before being 
destroyed (FIN_WAIT1, FIN_WAIT2, ...). So the physical network device 
may be moved back after lxc exits, leading to the network device name 
inconsistency.

I think the problem should be solved from the kernel, because it renames 
the netdev to devX when there is a name collision.
As we changed the name 'eth1' in the host to 'eth0' in the container, 
when the container exits, the kernel detect the conflict name with the 
'eth0' from the host and rename container's 'eth0' to 'dev%d'.
As a workaround, I think setting lxc.network.name = eth1 in the 
container should fix the problem (assuming /etc/network/interfaces file 
is modified for this name). So no name conflict will appear when the 
container exits.

I will dig to push in the mainstream kernel a fix but I am not sure that 
will be accepted.

Thanks
   -- Daniel

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Ulli Horlacher]

On Tue 2011-03-08 (07:35), Serge E. Hallyn wrote:

> Nice - that should be pretty simple to whip up, too.  A python app
> wrapping the command line tools...  Could probably even design it
> such that the same core can be used by both a curses interface and
> a gui interface.

I do not like both, I prefer pure CLI. It's easier for scripting.
I have written a perl based lxc-command wrapper script. So far it can:

root@zoo:/lxc# lxc 
usage: lxc options container
options: -n  new container (from template)
 -b  boot container
 -c  console container
 -s  shutdown container
 -l  list

root@zoo:/lxc# lxc -l
container  size (MB)   start-PID
flupp   11801283
ubuntu   600   0


I will integrate the other lxc basic commands as soon the phys nic
renaming bug is solved.

-- 
Ullrich Horlacher  Server- und Arbeitsplatzsysteme
Rechenzentrum  E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart Tel:++49-711-685-65868
Allmandring 30 Fax:++49-711-682357
70550 Stuttgart (Germany)  WWW:http://www.rus.uni-stuttgart.de/

--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Walter Stanish]

> With somewhat more work I could add:
>
> * a wizard to create new containers (very simple at first, where it only
> creates one kind of container system)

This is a real minefield.

All in all, I would leave guest creation out of any such script as
it feels like it's going to get code rot, generate bug reports and
generally achieve little.

If you don't believe me, try it :)

All other ideas on this thread are excellent.  Thumbs up.

- Walter

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

> This is a great start.
>
> Although it's true what has been said that a real curses (or other
> compiled) app will ultimately be able to do a lot more by using liblxc,
> I really want to build on this in the mean time. I already have several
> things I want to do to it to use in conjunction with my inid.d script
> for openSUSE.

Sounds good to me.

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Brian K. White]

On 3/16/2011 5:11 AM, Geordy Korte wrote:
> On Tue, Mar 8, 2011 at 12:42 PM, Stuart Johnson  > wrote:
>
>
>  > maybe just define what you want. Gathering ideas could/would inspire
>  > someone to implement it.
>
> Ideally I want a simple ncurses application that shows you what
> containers are active, and allows simple functionality, such as create,
> start, stop and configure settings.  Super easy to install, and runs
> from the ssh console. No need for web servers, or opening up special
> ports.
>
> Hello,
>
> Had some time to spare and decided that I would pitch in. Attached a
> simple dialog system that will allow you to start/stop an lxc container
> and open the console.  It's really really really early (lol took me 5
> minutes) but let me know if this is what you are looking for and if so
> what you would like to have added to it.
>
> You need the dialog package for this to work:
> apt-get install dialog
> --
> Geordy Korte

This is a great start.

Although it's true what has been said that a real curses (or other 
compiled) app will ultimately be able to do a lot more by using liblxc, 
I really want to build on this in the mean time. I already have several 
things I want to do to it to use in conjunction with my inid.d script 
for openSUSE.

With almost trivial additions I could have it integrate with my 
particular config scheme so that this could also:

* start/stop all containers
* mark a container as enabled/disabled for automatic start at (host) boot
* display per/container status like process list
* poor-mans-top that adds a column to show what container a process 
belongs to
* display other misc info that's handy for the host admin, like the 
ip's/bridges/vlans associated with each container, rootfs and other 
mounts, etc.
* display/edit container config

With somewhat more work I could add:

* a wizard to create new containers (very simple at first, where it only 
creates one kind of container system)
* iotop-alike that shows container
* iftop-alike that shows container
* wall one or all containers

Can we put this up in a google code project, or do you mind if I do it?

A few of the things I want will be specific to openSUSE, or rather, 
specific to how I chose to do my init.d, since there is no standard yet, 
I just made up my own. But I still think it shouldn't be too hard to 
make this distribution agnostic. The wizard to create a container will 
just use template scripts and I'll just supply an openSUSE template 
script. The init.d integration is the only thing that will be really 
distribution specific but that is very simple.

I'd love to get a few more things into it and include it into my rclxc 
package for openSUSE or make it it's own package.

-- 
bkw

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[matthew byers]

yes that would be by far the best server solution i have ever come across if
somehow the openvz kernel could be used in conjuction with lxc.

On Wed, Mar 16, 2011 at 10:14 AM, Stuart Johnson  wrote:

> On 16/03/11 16:01, matthew byers wrote:
> > Oh i wasnt suggesting switching to proxmox, i was speaking mostly on
> > the control panel it uses and some of the stuff that can be
> > incorporated into this lxc panel. i used proxmox before too and i
> > highly enjoy it but i am unable to use my extra drives in my server
> > unless i setup lvm which i dont want.
>
> No I know, you weren't.  Just agreeing that proxmox is a superb product,
> and if it supported LXC, then I would be using it.
>
>
>
>
> --
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> ___
> Lxc-users mailing list
> Lxc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>



-- 
God Bless
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

On 16/03/11 16:01, matthew byers wrote:
> Oh i wasnt suggesting switching to proxmox, i was speaking mostly on 
> the control panel it uses and some of the stuff that can be 
> incorporated into this lxc panel. i used proxmox before too and i 
> highly enjoy it but i am unable to use my extra drives in my server 
> unless i setup lvm which i dont want.

No I know, you weren't.  Just agreeing that proxmox is a superb product, 
and if it supported LXC, then I would be using it.



--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[matthew byers]

Oh i wasnt suggesting switching to proxmox, i was speaking mostly on the
control panel it uses and some of the stuff that can be incorporated into
this lxc panel. i used proxmox before too and i highly enjoy it but i am
unable to use my extra drives in my server unless i setup lvm which i dont
want.

On Wed, Mar 16, 2011 at 9:50 AM, Stuart Johnson  wrote:

> On 16/03/11 15:18, matthew byers wrote:
> > This is a great start as i have heard many folks inquire about this
> > for lxc. I dont know if you all are familiar with something called
> > Proxmox (debian with openvz kernel for openvz and kvm containers) but
> > it has a great web browser based control panel that is accessed via
> > the server ip address. The panel has some functions such as:
> > 1. Start/stop/restart containers (as discussed already)
> > 2. VNC into a container
> > 3. Creation/destruction of containers
> > 4.manage container resources (RAM, hdd size, container ip, dns, etc)
> >
> > Im not sure with the resource management as we use cgroups but i just
> > wanted to throw out some ideas on it.
>
> I have recently been evaluating Proxmox, and it's near perfect for what
> I need. But it has a major drawback, in that it does not have LXC
> support yet, and requires a customised kernel for OpenVZ.  In fact it's
> a customised distro, which is fine if your installing it on your own
> hardware, but a bit of a problem installing it at a datacentre on
> someone else's machine.
>
> When I thought about it, all I needed was a recent distro (debian or
> whatever), and a simple GUI.  SSH into the box, install LXC, and the
> network bridge. Start an ncurses app, and start creating & managing
> containers.  Job done.
>
> Stuart.
>
>
> --
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> ___
> Lxc-users mailing list
> Lxc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>



-- 
God Bless
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

On 16/03/11 15:18, matthew byers wrote:
> This is a great start as i have heard many folks inquire about this 
> for lxc. I dont know if you all are familiar with something called 
> Proxmox (debian with openvz kernel for openvz and kvm containers) but 
> it has a great web browser based control panel that is accessed via 
> the server ip address. The panel has some functions such as:
> 1. Start/stop/restart containers (as discussed already)
> 2. VNC into a container
> 3. Creation/destruction of containers
> 4.manage container resources (RAM, hdd size, container ip, dns, etc)
>
> Im not sure with the resource management as we use cgroups but i just 
> wanted to throw out some ideas on it.

I have recently been evaluating Proxmox, and it's near perfect for what 
I need. But it has a major drawback, in that it does not have LXC 
support yet, and requires a customised kernel for OpenVZ.  In fact it's 
a customised distro, which is fine if your installing it on your own 
hardware, but a bit of a problem installing it at a datacentre on 
someone else's machine.

When I thought about it, all I needed was a recent distro (debian or 
whatever), and a simple GUI.  SSH into the box, install LXC, and the 
network bridge. Start an ncurses app, and start creating & managing 
containers.  Job done.

Stuart.

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[matthew byers]

This is a great start as i have heard many folks inquire about this for lxc.
I dont know if you all are familiar with something called Proxmox (debian
with openvz kernel for openvz and kvm containers) but it has a great web
browser based control panel that is accessed via the server ip address. The
panel has some functions such as:
1. Start/stop/restart containers (as discussed already)
2. VNC into a container
3. Creation/destruction of containers
4.manage container resources (RAM, hdd size, container ip, dns, etc)

Im not sure with the resource management as we use cgroups but i just wanted
to throw out some ideas on it.

On Wed, Mar 16, 2011 at 6:05 PM, Serge E. Hallyn wrote:

> Quoting Geordy Korte (gko...@gmail.com):
> > On Wed, Mar 16, 2011 at 3:00 PM, Daniel Lezcano  >wrote:
> >
> > > On 03/16/2011 02:16 PM, Serge E. Hallyn wrote:
> > >
> > >> Had some time to spare and decided that I would pitch in. Attached a
> > >>> simple
> > >>> dialog system that will allow you to start/stop an lxc container and
> open
> > >>> the console.  It's really really really early (lol took me 5 minutes)
> but
> > >>> let me know if this is what you are looking for and if so what you
> would
> > >>> like to have added to it.
> > >>>
> > >>
> > >> Exactly - this is exactly what I was thinking and how I've done some
> > >> things like this in the past.  It's not that the things it does need
> > >> to be fancy - it's just that it should reduce typing quite a bit.
> > >>
> > >> I like it.
> > >>
> > >
> > > I share Serge's opinion.
> > >
> > > Thanks !
> > >
> > > OK...
> >
> > So what could we put in it? We can edit the cfg files for a container but
> > that seems a little over the top since VI or any good text editor will do
> > the same.
> >
> > I can't think of anything I would like in there but then again I only
> have 8
> > containers.
>
> Some simple things:
>
> 1. editing configs actually is useful just bc you don't have to type
> in the whole config pathname
>
> 2. tag containers in the list view and perform group actions
>
> 3. open consoles - heck, perhaps tag containers in the list view,
> create a new screen session, and open a console for each container
> in a new window in the screen session.  Limited by # of screens in
> a session though.
>
> -serge
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQEcBAEBAgAGBQJNgNG6AAoJEHmllQITXQdFHfsH/25stTltRlEzqiyJX6Fx8y+u
> Mwt/kA3PJHnhcl/m6SHxzdUBJJ9rGUL8ZOngucUfG9Mt78fApXFEGTWpBX9UkQQY
> U39NllZwFW7myQUIqmAvkr7Ta8D1n2zPAHC35b05a34XJdR9JftoPwD/wXA/RWAD
> lJwWz9vqYODng94r0zgea0v7EdMUt9WGaBOALoXSbYLJT+IsR6Gn49gFjRA076u4
> rcwDb0aL/usEE2Ce/FF8psZDPN+kPP3rGRFzgHrZA5wCeLqE/DEJBdHgYtO7Antv
> XSKeroUqyYnhMSUaEBFDvP2iTgqkG2xrd0TPHqXNo5pm3J0+2LO7t5JnPGNlwhg=
> =gR8x
> -END PGP SIGNATURE-
>
>
> --
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> ___
> Lxc-users mailing list
> Lxc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>
>


-- 
God Bless
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Serge E. Hallyn]

Quoting Geordy Korte (gko...@gmail.com):
> On Wed, Mar 16, 2011 at 3:00 PM, Daniel Lezcano wrote:
> 
> > On 03/16/2011 02:16 PM, Serge E. Hallyn wrote:
> >
> >> Had some time to spare and decided that I would pitch in. Attached a
> >>> simple
> >>> dialog system that will allow you to start/stop an lxc container and open
> >>> the console.  It's really really really early (lol took me 5 minutes) but
> >>> let me know if this is what you are looking for and if so what you would
> >>> like to have added to it.
> >>>
> >>
> >> Exactly - this is exactly what I was thinking and how I've done some
> >> things like this in the past.  It's not that the things it does need
> >> to be fancy - it's just that it should reduce typing quite a bit.
> >>
> >> I like it.
> >>
> >
> > I share Serge's opinion.
> >
> > Thanks !
> >
> > OK...
> 
> So what could we put in it? We can edit the cfg files for a container but
> that seems a little over the top since VI or any good text editor will do
> the same.
> 
> I can't think of anything I would like in there but then again I only have 8
> containers.

Some simple things:

1. editing configs actually is useful just bc you don't have to type
in the whole config pathname

2. tag containers in the list view and perform group actions

3. open consoles - heck, perhaps tag containers in the list view,
create a new screen session, and open a console for each container
in a new window in the screen session.  Limited by # of screens in
a session though.

-serge


signature.asc
Description: Digital signature
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Daniel Lezcano]

On 03/16/2011 03:23 PM, Geordy Korte wrote:
> On Wed, Mar 16, 2011 at 3:00 PM, Daniel Lezcanowrote:
>
>> On 03/16/2011 02:16 PM, Serge E. Hallyn wrote:
>>
>>> Had some time to spare and decided that I would pitch in. Attached a
 simple
 dialog system that will allow you to start/stop an lxc container and open
 the console.  It's really really really early (lol took me 5 minutes) but
 let me know if this is what you are looking for and if so what you would
 like to have added to it.

>>>
>>> Exactly - this is exactly what I was thinking and how I've done some
>>> things like this in the past.  It's not that the things it does need
>>> to be fancy - it's just that it should reduce typing quite a bit.
>>>
>>> I like it.
>>>
>>
>> I share Serge's opinion.
>>
>> Thanks !
>>
>> OK...
>
> So what could we put in it? We can edit the cfg files for a container but
> that seems a little over the top since VI or any good text editor will do
> the same.
>
> I can't think of anything I would like in there but then again I only have 8
> containers.


You should use the monitoring of the container to reflect the changes. 
Not sure that would be easy with a shell script.
IMHO, the dialog based is a good way to prototype but I think a ncurse 
based program would more adequate as it can directly use the C api of 
the liblxc and provide much more functionalities.

Also, it could be interesting to add a container configuration/creation 
wizard ala 'anaconda'.

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

>
> Had some time to spare and decided that I would pitch in. Attached a 
> simple dialog system that will allow you to start/stop an lxc 
> container and open the console.  It's really really really early (lol 
> took me 5 minutes) but let me know if this is what you are looking for 
> and if so what you would like to have added to it.
>
> You need the dialog package for this to work:
> apt-get install dialog
> -- Worked
> Geordy Korte
>

Thats great, thank you. Just what I had in mind. I guess the skys the 
limit as to it's functionality. It would be nice to be able to view and 
even change the containers settings on the fly, like cpu limits.

Stuart.

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Geordy Korte]

On Wed, Mar 16, 2011 at 3:00 PM, Daniel Lezcano wrote:

> On 03/16/2011 02:16 PM, Serge E. Hallyn wrote:
>
>> Had some time to spare and decided that I would pitch in. Attached a
>>> simple
>>> dialog system that will allow you to start/stop an lxc container and open
>>> the console.  It's really really really early (lol took me 5 minutes) but
>>> let me know if this is what you are looking for and if so what you would
>>> like to have added to it.
>>>
>>
>> Exactly - this is exactly what I was thinking and how I've done some
>> things like this in the past.  It's not that the things it does need
>> to be fancy - it's just that it should reduce typing quite a bit.
>>
>> I like it.
>>
>
> I share Serge's opinion.
>
> Thanks !
>
> OK...

So what could we put in it? We can edit the cfg files for a container but
that seems a little over the top since VI or any good text editor will do
the same.

I can't think of anything I would like in there but then again I only have 8
containers.


-- 
==
Geordy Korte
MSN geo...@geordy.nl
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Daniel Lezcano]

On 03/16/2011 02:16 PM, Serge E. Hallyn wrote:
>> Had some time to spare and decided that I would pitch in. Attached a simple
>> dialog system that will allow you to start/stop an lxc container and open
>> the console.  It's really really really early (lol took me 5 minutes) but
>> let me know if this is what you are looking for and if so what you would
>> like to have added to it.
>
> Exactly - this is exactly what I was thinking and how I've done some
> things like this in the past.  It's not that the things it does need
> to be fancy - it's just that it should reduce typing quite a bit.
>
> I like it.

I share Serge's opinion.

Thanks !

   -- Daniel

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Serge E. Hallyn]

> Had some time to spare and decided that I would pitch in. Attached a simple
> dialog system that will allow you to start/stop an lxc container and open
> the console.  It's really really really early (lol took me 5 minutes) but
> let me know if this is what you are looking for and if so what you would
> like to have added to it.

Exactly - this is exactly what I was thinking and how I've done some
things like this in the past.  It's not that the things it does need
to be fancy - it's just that it should reduce typing quite a bit.

I like it.

thanks,
-serge


signature.asc
Description: Digital signature
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Geordy Korte]

On Tue, Mar 8, 2011 at 12:42 PM, Stuart Johnson  wrote:

>
> > maybe just define what you want. Gathering ideas could/would inspire
> > someone to implement it.
>
> Ideally I want a simple ncurses application that shows you what
> containers are active, and allows simple functionality, such as create,
> start, stop and configure settings.  Super easy to install, and runs
> from the ssh console. No need for web servers, or opening up special ports.
>
> Hello,

Had some time to spare and decided that I would pitch in. Attached a simple
dialog system that will allow you to start/stop an lxc container and open
the console.  It's really really really early (lol took me 5 minutes) but
let me know if this is what you are looking for and if so what you would
like to have added to it.

You need the dialog package for this to work:
apt-get install dialog
-- 
Geordy Korte


lxc-dialog
Description: Binary data
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Brian K. White]

On 3/10/2011 9:04 PM, Stuart Johnson wrote:
>
>>> Meaning you think python would be too heavyweight?
>> Certainly as one approaches the embedded end of the spectrum, there's
>> something to be said for avoiding dependencies on large (compared to
>> busybox ash) interpreters.  It'd be neat if I could deploy per-service
>> containers on, say, a router with an 8MB MTD and 32MB RAM, and using
>> python/perl/ruby/whatever would make that harder.  Mybe lua would be
>> a better fit; I tend to stick to busybox ash, since it's already there.
>
> Perhaps we should be asking first, should an ncurses control panel be
> part of LXC or a separate project?  If it's the latter, then its rather
> immaterial, although personally I would love it to be part of LXC.  I
> want to able to install LXC on any Linux box, and start managing
> containers with the least amount of effort.

The embedded example just shows how everyones needs are very different.
I can see that wanting the lightest of non-interactive shell scripts run 
as cgi from a web server and all ui done via browser, or possibly run 
directly by the web server from a built-in mod_php or such with no use 
for ncurses at all.

I say let the main lxc package just continue to make better 
non-interactive command line tools, and let all higher level front-ends 
be separate packages written in whatever language(s) the authors like, 
serving whatever diverse special purposes they may.

Ideally of course would be to improve libvirt and/or other virt managers 
add lxc support to them and modify lxc relatively little just to 
facilitate that where indicated.

-- 
bkw

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Matto Fransen]

Hi all,

This thread is becoming more interesting all the time :)

On Fri, Mar 11, 2011 at 11:06:53AM +, Stuart Johnson wrote:
> > If you're in a production environment, you will tend to start or stop 
> > your containers as seldom as you will start and stop your servers.
> 
> 
> I see this as a good reason to have a simple control panel. When you 
> seldom use something, you tend to forget how to do things, or in the 
> case of manageing multiple servers, you forget how each one is 
> configured. A simple visual interface helps to get the job done with the 
> confidence your not going to break anything.
> 
> As a developer, I may be required to install something on a clients 
> machine, and I want to set up a container to protect their system and 
> myself from any mishap.  A simple ncurses app, would allow me to add a 
> container without worrying about what distro i am using, or interfering 
> with existing containers should there be any.
 
Here you touch another interesting aspect. And that is what you tend
to run inside containers. The LXC Linux Containers provide us with
a beautifull light and elegant solution. 

So suppose you have a nice text-mode application to create and manage
containers, what will you install into them, and how would you 
like to do that?

If you go for a small, simple and elegant solution like LXC, then put 
something small and specific to the job in them. Which means a container 
that contains just enough to get the job done.

Putting a full Ubuntu or Fedora distro inside a container is IMHO something
of a contradiction towards the container approach. If you go for 
bloat, you might as well use kvm or xen to run that distro.

> As a newbie, I may want to try LXC out without a steep learning curve.

IMHO that requires available container-images, ready to run. Something
like what http://www.turnkeylinux.org provides, but than in container-format.
That would be really cool ...

Cheers,

Matto

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

> If you're in a production environment, you will tend to start or stop 
> your containers as seldom as you will start and stop your servers.


I see this as a good reason to have a simple control panel. When you 
seldom use something, you tend to forget how to do things, or in the 
case of manageing multiple servers, you forget how each one is 
configured. A simple visual interface helps to get the job done with the 
confidence your not going to break anything.

As a developer, I may be required to install something on a clients 
machine, and I want to set up a container to protect their system and 
myself from any mishap.  A simple ncurses app, would allow me to add a 
container without worrying about what distro i am using, or interfering 
with existing containers should there be any.

As a newbie, I may want to try LXC out without a steep learning curve.




--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Jäkel , Guido]

Hi all,

i want to agree to Stuart statement:

> Perhaps we should be asking first, should an ncurses control panel be part of 
> LXC or a separate project?

To my opinion and in comparison to similar projects, there should be a clear 
separation between any higher level (GUI) tool and the basic level teer with 
it's commandline accessors.

In the scope of low level teer, it would be usefull for this to have a well 
structurized communication API like a procfs-driver (and/or an XML interface) 
to get the status and parameters of the running containers or even set some 
things. This may be the interface for some higher level toolkits. Maybe one 
will say, that this all is already available in the cgroup. Then it's fine -- i 
havn't looked closely on this, yet.

But I personally wonder what group of users will need a simple "control panel". 
If you're in a production environment, you will tend to start or stop your 
containers as seldom as you will start and stop your servers. If your're a 
developer, you may use it a few times for convenience and then you'll ask to 
script it by your development environment. But I may be wrong and when people 
ask for it other may start to work.


>From following this mailing list a couple of days now, I would say: For the 
>LXC project itself will much more helpful to lower the border for the newbies 
>and users of binary-distro if there is some kind of setup wizard tool to guide 
>the compilation of a lxc.conf. Or at least a bunch of well-kept howto's, 
>explanations and examples in a wiki space on the LXC homepage.


with greetings

Guido

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

>> Meaning you think python would be too heavyweight?
> Certainly as one approaches the embedded end of the spectrum, there's
> something to be said for avoiding dependencies on large (compared to
> busybox ash) interpreters.  It'd be neat if I could deploy per-service
> containers on, say, a router with an 8MB MTD and 32MB RAM, and using
> python/perl/ruby/whatever would make that harder.  Mybe lua would be
> a better fit; I tend to stick to busybox ash, since it's already there.

Perhaps we should be asking first, should an ncurses control panel be 
part of LXC or a separate project?  If it's the latter, then its rather 
immaterial, although personally I would love it to be part of LXC.  I 
want to able to install LXC on any Linux box, and start managing 
containers with the least amount of effort.






--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Trent W. Buck]

"Serge E. Hallyn" writes:

> Meaning you think python would be too heavyweight?

Certainly as one approaches the embedded end of the spectrum, there's
something to be said for avoiding dependencies on large (compared to
busybox ash) interpreters.  It'd be neat if I could deploy per-service
containers on, say, a router with an 8MB MTD and 32MB RAM, and using
python/perl/ruby/whatever would make that harder.  Mybe lua would be
a better fit; I tend to stick to busybox ash, since it's already there.


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Matto Fransen]

Hi,

On Thu, Mar 10, 2011 at 07:56:23AM -0600, Serge E. Hallyn wrote:
 
> > One of the nice things IMHO of LXC Linux Containers is that it hardly
> > needs any extra's on the host. The user-space app's are either
> > compiled C-programs or bash-scripts. There is one Perl application
> > but that is not-critical and one can do without.
> > 
> > I would love to see it stay that way. At the moment, it is very
> > doable to set up a host containing just a minimal system (like
> > kernel, busybox, ssh or dropbear, some libs and the LXC-app's).
> > 
> > So I would recommend to see of this could be done either in
> > shellscript or C, or otherwise stay at Perl.
> 
> (just making sure)
> 
> Meaning you think python would be too heavyweight?

Well, not perhaps heavy weight, but would still add another dependencie.

At the moment you can run LXC without the need of Python.
When we would stick to shellscript or compiled C, we could keep it that
way :)

Cheers,

Matto


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Serge E. Hallyn]

Quoting Matto Fransen (ma...@matto.nl):
> Hi,
> 
> On Tue, Mar 08, 2011 at 07:35:38AM -0600, Serge E. Hallyn wrote:
> > Nice - that should be pretty simple to whip up, too.  A python app
> > wrapping the command line tools...  Could probably even design it
> > such that the same core can be used by both a curses interface and
> > a gui interface.
> 
> One of the nice things IMHO of LXC Linux Containers is that it hardly
> needs any extra's on the host. The user-space app's are either
> compiled C-programs or bash-scripts. There is one Perl application
> but that is not-critical and one can do without.
> 
> I would love to see it stay that way. At the moment, it is very
> doable to set up a host containing just a minimal system (like
> kernel, busybox, ssh or dropbear, some libs and the LXC-app's).
> 
> So I would recommend to see of this could be done either in
> shellscript or C, or otherwise stay at Perl.

(just making sure)

Meaning you think python would be too heavyweight?

-serge

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Matto Fransen]

Hi,

On Tue, Mar 08, 2011 at 07:35:38AM -0600, Serge E. Hallyn wrote:

> > Ideally I want a simple ncurses application that shows you what 
> > containers are active, and allows simple functionality, such as create, 
> > start, stop and configure settings.  Super easy to install, and runs 
> > from the ssh console. No need for web servers, or opening up special ports.
> 
> Nice - that should be pretty simple to whip up, too.  A python app
> wrapping the command line tools...  Could probably even design it
> such that the same core can be used by both a curses interface and
> a gui interface.

One of the nice things IMHO of LXC Linux Containers is that it hardly
needs any extra's on the host. The user-space app's are either
compiled C-programs or bash-scripts. There is one Perl application
but that is not-critical and one can do without.

I would love to see it stay that way. At the moment, it is very
doable to set up a host containing just a minimal system (like
kernel, busybox, ssh or dropbear, some libs and the LXC-app's).

So I would recommend to see of this could be done either in
shellscript or C, or otherwise stay at Perl.

Just my thoughts ...

Cheers,

Matto

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Serge E. Hallyn]

Quoting C Anthony Risinger (anth...@extof.me):
> On Mar 8, 2011 5:52 PM, "Trent W. Buck"  wrote:
> >
> > Jon Nordby  writes:
> >
> > > On 7 March 2011 22:35, Stuart Johnson  wrote:
> > >> There is OpenQRM http://www.openqrm.com/?q=node/180
> > >>>
> > >>> But there are no ncurses and a simple web control panels for lxc
> > >>> neither an IHM yet, unfortunately ...
> > >>> That could be really nice ...
> > >>>
> > >>
> > >> Thanks. I have seen openQRM, but looks overkill for what I want.  A
> > >> simple menu driven interface over ssh would have been ideal.
> > > libvirt has pretty good support for LXC. Maybe virsh or the
> > > ncurses-like/based UI that recently got committed to virt-manager is
> > > something along the lines of what you're looking for?
> >
> > Is it really "pretty good"?  A few months ago, when I deployed lxc (as
> > in, lxc.sf.net) instead of libvirt, it was because the libvirt people
> > said that their LXC support was bare-bones.
> 
> Really?  I'm soon to set it up again ... I had it running 2 yrs ago under.
> 32 without much problem (but used this instead); at that time it _was_
> barebones.  I hoped it'd be decent by now because libvirt pretty much rocks
> :-)
> 
> C Anthony [mobile]

I suspect if you just want a full system container it's ok.  Especially
now that the bug is fixed where when you log into console and logout.
AFAIR the .xml config doesn't let you specify any device whitelist,
esoteric network config, bind mount sharing with the host, etc.  But
sometimes you don't need that.

-serge

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[C Anthony Risinger]

On Mar 8, 2011 5:52 PM, "Trent W. Buck"  wrote:
>
> Jon Nordby  writes:
>
> > On 7 March 2011 22:35, Stuart Johnson  wrote:
> >> There is OpenQRM http://www.openqrm.com/?q=node/180
> >>>
> >>> But there are no ncurses and a simple web control panels for lxc
> >>> neither an IHM yet, unfortunately ...
> >>> That could be really nice ...
> >>>
> >>
> >> Thanks. I have seen openQRM, but looks overkill for what I want.  A
> >> simple menu driven interface over ssh would have been ideal.
> > libvirt has pretty good support for LXC. Maybe virsh or the
> > ncurses-like/based UI that recently got committed to virt-manager is
> > something along the lines of what you're looking for?
>
> Is it really "pretty good"?  A few months ago, when I deployed lxc (as
> in, lxc.sf.net) instead of libvirt, it was because the libvirt people
> said that their LXC support was bare-bones.

Really?  I'm soon to set it up again ... I had it running 2 yrs ago under.
32 without much problem (but used this instead); at that time it _was_
barebones.  I hoped it'd be decent by now because libvirt pretty much rocks
:-)

C Anthony [mobile]
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Trent W. Buck]

Jon Nordby  writes:

> On 7 March 2011 22:35, Stuart Johnson  wrote:
>> There is OpenQRM http://www.openqrm.com/?q=node/180
>>>
>>> But there are no ncurses and a simple web control panels for lxc
>>> neither an IHM yet, unfortunately ...
>>> That could be really nice ...
>>>
>>
>> Thanks. I have seen openQRM, but looks overkill for what I want.  A
>> simple menu driven interface over ssh would have been ideal.
> libvirt has pretty good support for LXC. Maybe virsh or the
> ncurses-like/based UI that recently got committed to virt-manager is
> something along the lines of what you're looking for?

Is it really "pretty good"?  A few months ago, when I deployed lxc (as
in, lxc.sf.net) instead of libvirt, it was because the libvirt people
said that their LXC support was bare-bones.


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Serge E. Hallyn]

Quoting Stuart Johnson (stu...@stu.org.uk):
> 
> > maybe just define what you want. Gathering ideas could/would inspire
> > someone to implement it.
> >
> > Regards
> > Erkan
> >
> 
> Ideally I want a simple ncurses application that shows you what 
> containers are active, and allows simple functionality, such as create, 
> start, stop and configure settings.  Super easy to install, and runs 
> from the ssh console. No need for web servers, or opening up special ports.

Nice - that should be pretty simple to whip up, too.  A python app
wrapping the command line tools...  Could probably even design it
such that the same core can be used by both a curses interface and
a gui interface.

-serge

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

> maybe just define what you want. Gathering ideas could/would inspire
> someone to implement it.
>
> Regards
> Erkan
>

Ideally I want a simple ncurses application that shows you what 
containers are active, and allows simple functionality, such as create, 
start, stop and configure settings.  Super easy to install, and runs 
from the ssh console. No need for web servers, or opening up special ports.






--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[erkan yanar]

Hi Stuart,

On Mon, Mar 07, 2011 at 10:35:09PM +, Stuart Johnson wrote:
> 
> Thanks. I have seen openQRM, but looks overkill for what I want.  A 
> simple menu driven interface over ssh would have been ideal.
> 

maybe just define what you want. Gathering ideas could/would inspire
someone to implement it.

Regards
Erkan

-- 
über den grenzen muß die freiheit wohl wolkenlos sein 

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

libvirt has pretty good support for LXC. Maybe virsh or the
> ncurses-like/based UI that recently got committed to virt-manager is
> something along the lines of what you're looking for?
>
Interesting, thanks, I will check it out.

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Jon Nordby]

On 7 March 2011 22:35, Stuart Johnson  wrote:
> There is OpenQRM http://www.openqrm.com/?q=node/180
>>
>> But there are no ncurses and a simple web control panels for lxc
>> neither an IHM yet, unfortunately ...
>> That could be really nice ...
>>
>
> Thanks. I have seen openQRM, but looks overkill for what I want.  A
> simple menu driven interface over ssh would have been ideal.
libvirt has pretty good support for LXC. Maybe virsh or the
ncurses-like/based UI that recently got committed to virt-manager is
something along the lines of what you're looking for?

-- 
Jon Nordby - www.jonnor.com

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Stuart Johnson]

There is OpenQRM http://www.openqrm.com/?q=node/180
>
> But there are no ncurses and a simple web control panels for lxc 
> neither an IHM yet, unfortunately ...
> That could be really nice ...
>

Thanks. I have seen openQRM, but looks overkill for what I want.  A 
simple menu driven interface over ssh would have been ideal.

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Re: [Lxc-users] Control panel

[Daniel Lezcano]

On 03/07/2011 09:40 PM, Stuart Johnson wrote:
> Are there any web or ncurses control panels available for lxc?

There is OpenQRM http://www.openqrm.com/?q=node/180

But there are no ncurses and a simple web control panels for lxc neither 
an IHM yet, unfortunately ...
That could be really nice ...

Thanks
   -- Daniel

--
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
___
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users