TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

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

2 点作者 yannovitch大约 12 年前
Hello,<p>Who am I ? I'm a french "studentrepeneur", doing distance studies in Computer Science &#38; Business, and working on my companies during the day.<p>What is my problem ? (/!\ Test conditions, not in production /!\) I have implemented an hybrid private/public cloud (using OpenStack &#38; OpenNebula) with AMI provisioning. As such, I can use by default my own dedicated servers, then scale up with Amazon EC2 instances if I get too much charge on my private instances. As such, I have one pool of VM by function : load balancer, one pool for webserver , one pool for proxy, one for DBB, and so forth ... I use a mix of different technologies, PHP, Python, and I'm even thinking of trying Go. I use Nginx as reverse proxy and as webserver.<p>Now, all the domains are grouped ( clusterized) together, so they are VM agnostic : I can add as much instance as I want, it will always be presented to the domain as just one big resourceful physical server, not many VM.<p>What I would like to do now is to add more security by putting each domain in a LXC container. But I wonder, if I include container, won't it break my scalability model ? If yes, should I use a totally different model ? Like, not using a clusterized model but rather a lot of different instances with one per domain ? As it's in test and not in production, I can still break everything ;).<p>Yann

2 条评论

dilithiumhe3大约 12 年前
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.<p>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: <a href="https://github.com/dotcloud/docker‎" rel="nofollow">https://github.com/dotcloud/docker‎</a>
评论 #5708225 未加载
评论 #5708000 未加载
yannovitch大约 12 年前
OK, after having read the whole night, I think I will go with OpenShift to have Paas on top of the OpenStack Iaas.<p>This kind of thing looks like what I want to have : <a href="https://www.openshift.com/wiki/architecture-overview" rel="nofollow">https://www.openshift.com/wiki/architecture-overview</a><p>Moreover, when I will have other Saas needs, looks like it will be more easy to deploy.<p>Y