Hi Hongbin Lu, Thanks for your reply. I have responded inline.
BRs, Hieu LE. > On Sun, Jun 19, 2016 at 10:58 PM, Hongbin Lu <[email protected]> wrote: > > > >> 1. What is the pros/cons of deployment containers on VMs comparing with > >> containers on bare metal? I have seen RackSpace providing their > >> container service on bare metal and some other providers, but Amazon > >> use container on VM instead. > >> The only problem I saw with container on VM is only about management of > >> quota and resources. Deploying containers on VM will lead us to think > >> about whether we need to provide more containers on x VM for user or we > >> need to provide x+1 VMs for user to scale based on their needs. There > >> are 2 layers for operators to manage: 1st is VMs quota/resources and > >> 2nd is containers. > > [Hongbin Lu] Agree with you that containers on VMs are more complex to > > manage. There are other cons as well. For example, networking and storage > > are harder to setup. It is slower to scale up (because the speed to spin up > > VMs is not as fast as spinning up containers). In comparison, there are > > several pros. First, running containers on VMs provide strong isolation > > between containers of different tenants. Second, it can reuse the same > > resource pool to run VMs and containers (instead of creating a dedicated > > resource pool for running containers). Yeah, multi-tenancy is the good point of containers on VM but the second pros can lead to complex managements. > > > >> 2. Currently Magnum is on her way to implement the integration with > >> Ironic but I can not see the clearer way to keep track about this > >> feature (I have read the etherpad of Magnum team after summit). My team > >> really want to contribute in this feature but we need something clearer > >> to make a decision. Can you provide us some specs or related bp? > > [Hongbin Lu] Here is the BP: > > https://blueprints.launchpad.net/magnum/+spec/magnum-baremetal-full-support > > . Currently, we have the Heat templates to provision k8s on top of Ironic > > instances. The next step is to introduce an ironic bay to deliver the full > > support. Spyros (the BP owner) will report the latest status every weeks in > > the Magnum team meeting, so you can keep track of the status there. I > > encourage you to contact Spyros if you want to contribute in this feature. > > I believe Spyros will coordinate the efforts. Thank you, we will start investigating at this BP. > >> >> Thanks, >> Hieu LE. >> >> -- >> -----BEGIN GEEK CODE BLOCK----- >> Version: 3.1 >> GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C++++(++++)$ ULC++++(++)$ P >> L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+ >> b+(++)>+++ DI- D+ G e++(+++) h-- r(++)>+++ y- >> ------END GEEK CODE BLOCK------ -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/CM/IT/M/MU d-@? s+(++):+(++) !a C++++(++++)$ ULC++++(++)$ P L++(+++)$ E !W N* o+ K w O- M V- PS+ PE++ Y+ PGP+ t 5 X R tv+ b+(++)>+++ DI- D+ G e++(+++) h-- r(++)>+++ y- ------END GEEK CODE BLOCK------ _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
