Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-15 Thread 王华
se cases. Maybe magnum could support multiple modes? > > > > Best regards, > > Hongbin > > > > *From:* Corey O'Brien [mailto:coreypobr...@gmail.com] > *Sent:* February-15-16 8:43 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subjec

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-15 Thread Hongbin Lu
) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Hi all, A few thoughts to add: I like the idea of isolating the masters so that they are not tenant-controllable, but I don't think the Magnum control plane is the right place for them. They still need to be running on tenant-owned

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-15 Thread Corey O'Brien
-- > Hyper - Make VM run like Container > > > > On Mon, Feb 15, 2016 at 9:53 AM, Hongbin Lu <hongbin...@huawei.com> wrote: > >> My replies are inline. >> >> >> >> *From:* Kai Qiang Wu [mailto:wk...@cn.ibm.com] >

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-14 Thread Peng Zhao
inline. From: Kai Qiang Wu [mailto: wk...@cn.ibm.com ] Sent: February-14-16 7:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? HongBin, See my replies and questions in line. >> Thanks

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-14 Thread Hongbin Lu
My replies are inline. From: Kai Qiang Wu [mailto:wk...@cn.ibm.com] Sent: February-14-16 7:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? HongBin, See my replies and questions in line. >> Thanks Best

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-14 Thread Kai Qiang Wu
uawei.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 15/02/2016 01:26 am Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Kai Qiang, A major benefit is to have Magnum manage the COEs for

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-14 Thread Hongbin Lu
(not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Hi HongBin and Egor, I went through what you talked about, and thinking what's the great benefits for utilisation here. For user cases, looks like following: user A want to have a COE provision. user B want

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-13 Thread Kai Qiang Wu
lists.openstack.org> Date: 13/02/2016 11:02 am Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Egor, Thanks for sharing your insights. I gave it more thoughts. Maybe the goal can be achieved without implementing a shared COE. We could move all the master nodes out of use

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-12 Thread Guz Egor
bin...@huawei.com> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Sent: Thursday, February 11, 2016 8:50 PM Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Hi team,   Sorry for bringing up this old thread, but a recent

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2016-02-12 Thread Hongbin Lu
Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: February-12-16 2:34 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Hongbin Lu Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Hongbin, I am not sure that it's good idea, it looks you

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-10-03 Thread Egor Guz
Date: Wednesday, September 30, 2015 at 16:26 To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? We are looki

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-10-01 Thread Hongbin Lu
...@godaddy.com] Sent: September-30-15 7:26 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both you and josh. I agree

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-10-01 Thread Fox, Kevin M
[mailto:klindg...@godaddy.com] Sent: September-30-15 7:26 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both you and josh. I

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-10-01 Thread Hongbin Lu
mentioned. Best regards, Hongbin From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: October-01-15 11:58 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? I believe keystone already supports hierarchical projects Thanks

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Joshua Harlow
k.org > > > > <mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org > > <mailto:openstack-dev@lists.openstack.org>>> > > Date: Tuesday, September 29, 2015 at 08:44 > > To: "OpenStack Development Mailing List

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Peng Zhao
k .org >” < openstack-dev@lists.openstack .org >> Date: Tuesday, September 29, 2015 at 2:22 AM To: “ openstack-dev@lists.openstack .org >” < openstack-dev@lists.openstack .org >> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? This has been my thinking in the las

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Joshua Harlow
September 30, 2015 9:44 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? +1 from me as well. I think what makes Magnum appealing is the promise to provide container-as-a-service. I see coe deployment as a helper to

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Joshua Harlow
dnesday, September 30, 2015 9:44 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? +1 from me as well. I think what makes Magnum appealing is the promise to provide container-as-a-service. I see coe deployment as a

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Adrian Otto
. Regards, Devdatta From: Hongbin Lu<hongbin...@huawei.com<mailto:hongbin...@huawei.com>> Sent: Wednesday, September 30, 2015 9:44 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? +1 from me as well. I

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Steven Dake (stdake)
;>> Kulkarni<devdatta.kulka...@rackspace.com >>>>> <mailto:devdatta.kulka...@rackspace.com>> wrote: >>>>> >>>>> +1 Hongbin. >>>>> >>>>> From perspective of Solum, which hopes to use Magnum for its >>

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Joshua Harlow
All those tenancy information is in keystone, not replicated/synced >>>> into the COE (or in some other COE specific disjoint system). >>>> >>>> Thoughts? >>>> >>>> This one becomes especially hard if said COE(s) don't even have a >>

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Kris G. Lindgren
We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both you and josh. I agree that managing one large system is going to be a pain and pas experience tells me this wont be practical/scale, however from experience I also

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Adrian Otto
Kris, On Sep 30, 2015, at 4:26 PM, Kris G. Lindgren > wrote: We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both you and josh. I agree that managing one large

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Ryan Rossiter
opment Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Hongbin Lu
To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? +1 to Egor, I think that the final goal of Magnum is container as a service but not coe deployment as a service. ;-) Especially we are also working on Magnum UI, the Magnum UI

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Adrian Otto
naged from within > Horizon. > > Regards, > Devdatta > > > From: Hongbin Lu <hongbin...@huawei.com> > Sent: Wednesday, September 30, 2015 9:44 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum]swar

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Devdatta Kulkarni
: Hongbin Lu <hongbin...@huawei.com> Sent: Wednesday, September 30, 2015 9:44 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?   +1 from me as well.   I think what makes Magnum appealing is the promise to p

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread 王华
rtlabs.com> > To: "openstack-dev@lists.openstack.org" > <openstack-dev@lists.openstack.org> <openstack-dev@lists.openstack.org> > <openstack-dev@lists.openstack.org> > Date: 09/28/2015 10:20 PM > Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? &g

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread Tom Cammann
s)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Monday, September 28, 2015 at 22:03 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.ope

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread 王华
@Egor, docker compose is just a command line tool now, but I think it will change its architecture to Client and Server in the future, otherwise it can not do some complicate jobs. __ OpenStack Development Mailing List (not

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread Daneyon Hansen (danehans)
: Tuesday, September 29, 2015 at 2:22 AM To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? This has been my th

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread Adrian Otto
g>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? This has been my thinking in the last couple of months to completely deprecate the COE specific APIs such as pod/service/rc and conta

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread Monty Taylor
-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? This is definitely a topic we should cover in Tokyo.

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread Jay Lau
ate: Tuesday, September 29, 2015 at 08:44 > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org > >> > Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? >

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-29 Thread Egor Guz
sts.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? This has been my thinking in the last couple of months to completel

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-28 Thread Mike Spreitzer
> From: 王华 <wanghua.hum...@gmail.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 09/28/2015 11:34 PM > Subject: [openstack-dev] [magnum]swarm + compose = k8s? > > Hi folks, > &

[openstack-dev] [magnum]swarm + compose = k8s?

2015-09-28 Thread 王华
Hi folks, Magnum now exposes service, pod, etc to users in kubernetes coe, but exposes container in swarm coe. As I know, swarm is only a scheduler of container, which is like nova in openstack. Docker compose is a orchestration program which is like heat in openstack. k8s is the combination of

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-28 Thread Adrian Otto
Wanghua, I do follow your logic, but docker-compose only needs the docker API to operate. We are intentionally avoiding re-inventing the wheel. Our goal is not to replace docker swarm (or other existing systems), but to compliment it/them. We want to offer users of Docker the richness of

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-28 Thread Ton Ngo
: Egor Guz <e...@walmartlabs.com> To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Date: 09/28/2015 10:20 PM Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Also I belive docker compose is just command line t

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-28 Thread Egor Guz
r 28, 2015 at 22:03 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Wanghua, I do follow your logic, but docker-compose onl