Ask HN: LXC container inside a VM : is it good for scalability?

Re:Ask HN: LXC container inside a VM : is it good for scalab... by dilithiumhe3 on Tuesday May 14, 2013 @04:07PM (#5707679)

This is a pretty common thing if you want to get absolute separation for applications within a single (large) vm and is used extensively in the PaaS world. Have a look at cloudfoundry (look on github). This is how it manages containers for each application. Heroku, dotCloud and others seems to follow similar approaches.

Long answer short, a lxc container would look like a self-contained vm to everything outside and from within (except for the controlling vm). You can go with the existing model but I would recommend using one container per application/service. Also have a look at: https://github.com/dotcloud/docker‎

[ Parent | on HN ]

Re:Ask HN: LXC container inside a VM : is it good for scalab... by yannovitch on Tuesday May 14, 2013 @05:14PM (#5708225)

When you say "one container per application/service", you mean I should use

- one container = one domain ? with www.example.com, have one container for www.example1.com with all the services included (webserver_example1, database_example1,...) in one container ? and so forth with www.example2.com, ...

- one container = one service ? have a VM_DB for all the database with container1 = database_example1, container2 = database_example2, ... have a VM_WebServer with container1 = webserver_example1, ... ?

which approach work the best if i keep adding more and more VM (with container inside this VM) ??

[ Parent | on HN ]

Re:Ask HN: LXC container inside a VM : is it good for scalab... by yannovitch on Tuesday May 14, 2013 @04:47PM (#5708000)

Thanks a lot for your answer. What about the long answer not short ^^?

[ Parent | on HN ]