Re: [openstack-dev] [magnum] Mesos Conductor

sing/cli/marathonsyntax/ > > > > From: bharath thiruveedula [mailto:bharath_...@hotmail.com] > > Sent: November-18-15 1:20 PM > > To: openstack-dev@lists.openstack.org > > Subject: [openstack-dev] [magnum] Mesos Conductor > > > > Hi all, > > > > I am working on

Re: [openstack-dev] [magnum] Autoscaling both clusters andcontainers

e questions)" <openstack-dev@lists.openstack.org> Date: 11/17/2015 10:05 PM Subject: Re: [openstack-dev] [magnum] Autoscaling both clusters and containers It's great that we discuss this in mail list, I filed a bp here https://blueprints.launchpad.net/magnum/+spec/

[openstack-dev] [magnum] Issue on history of renamed file/folder

Hi team, I would like to start this ML to discuss the git rename issue. Here is the problem. In Git, it is handy to retrieve commit history of a file/folder. There are several ways to do that. In CLI, you can run "git log ..." to show the history. In Github, you can click "History" bottom on

Re: [openstack-dev] [magnum] Autoscaling both clusters and containers

will write a spec on autoscaling containers and cluster. A patch should be coming soon, so it would be great to have your input on the spec. Ton, From: Ryan Rossiter <rlros...@linux.vnet.ibm.com> To: openstack-dev@lists.openstack.org Date: 11/17/2015 02:05 PM Subject: [opensta

Re: [openstack-dev] [magnum] Autoscaling both clusters and containers

ck-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum] Autoscaling both clusters and containers Hi Ryan, There was a talk in the last Summit on this topics to explore the options with Magnum, Senlin, Heat, Kubernetes: https://www.openstack.or

Re: [openstack-dev] [magnum] Autoscaling both clusters and containers

ate: Tuesday, November 17, 2015 at 16:58 > 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] Autoscaling both clusters and

[openstack-dev] [magnum] Autoscaling both clusters and containers

Hi all, I was having a discussion with a teammate with respect to container scaling. He likes the aspect of nova-docker that allows you to scale (essentially) infinitely almost instantly, assuming you are using a large pool of compute hosts. In the case of Magnum, if I'm a container user, I

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.

/244847/ Best regards, Hongbin From: Kai Qiang Wu [mailto:wk...@cn.ibm.com] Sent: November-13-15 12:33 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate. Right now, we seems can not reduce devstack

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.

Excerpts from Hongbin Lu's message of 2015-11-13 16:05:24 +: > I am going to share something that might be off the topic a bit. > > Yesterday, I was pulled to the #openstack-infra channel to participant a > discussion, which is related to the atomic image download in Magnum. It looks > the

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testingongate.

3/2015 10:03 AM Subject: Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate. Excerpts from Hongbin Lu's message of 2015-11-13 16:05:24 +: > I am going to share something that might be off the topic a bit. > > Yesterday, I was pulled to the #op

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 11, 2015 at 23:02 To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [op

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

creation time for the cluster. If we can look at the Heat event stream, we might get an idea. Ton, From: Egor Guz <e...@walmartlabs.com> To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Date: 11/12/2015 05:25 PM Subject:

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.

t for usage questions \)" <openstack-dev@lists.openstack.org> Date: 13/11/2015 01:13 pm Subject: Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate. Thanks Eli for the analysis. I notice that the time to download the image is only around 1:15 mins out of

[openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

hello all: I will update some Magnum functional testing status, functional/integration testing is important to us, since we change/modify the Heat template rapidly, we need to verify the modification is correct, so we need to cover all templates Magnum has. and currently we only has k8s

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.

Eli, I like this proposed approach. We did have a discussion with a few Stackers from openstack-infra in Tokyo to express our interest in using bare metal for gate testing. That’s still a way out, but that may be another way to speed this up further. A third idea would be to adjust the nova

[openstack-dev] [magnum] Networking Subteam Meetings

All, I apologize for issues with today's meeting. My calendar was updated to reflect daylight savings and displayed an incorrect meeting start time. This issue is now resolved. We will meet on 11/12 at 18:30 UTC. The meeting has been pushed back 30 minutes from our usual start time. This is

Re: [openstack-dev] [magnum] Networking Subteam Meetings

It seems integration of the SocketPlane acquisition has come to fruition in 1.9… Lee > On Nov 5, 2015, at 1:18 PM, Daneyon Hansen (danehans) > wrote: > > All, > > I apologize for issues with today's meeting. My calendar was updated to > reflect daylight savings and

[openstack-dev] [Magnum] [RFC] split pip line of functional testing

hi Magnum hackers: Currently there is a pip line on project-config to do magnum functional testing [1] on summit, we've discussed that we need to split it per COE[2], we can do this by adding new pip line to testing./ / /- '{pipeline}-functional-dsvm-magnum{coe}{job-suffix}':/ coe could be

Re: [openstack-dev] [Magnum] [RFC] split pip line of functional testing

: "Qiao,Liyong" <liyong.q...@intel.com> To: openstack-dev@lists.openstack.org, "Qiao, Liyong" <liyong.q...@intel.com> Date: 03/11/2015 06:13 pm Subject:[openstack-dev] [Magnum] [RFC] split pip line of functional testing

Re: [openstack-dev] [magnum]generate config files by magnum

t for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [magnum]generate config files by magnum Hi forks, Magnum needs to prepare config files for k8s and docker and add these services to systemd. Now

Re: [openstack-dev] [magnum]generate config files by magnum

2, 2015 at 06:37 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]generate config files by magnum The reason we don’t rely on cloudint more th

[openstack-dev] magnum on OpenStack Kilo

Hi, Does anyone have any guidance for configuring magnum on OpenStack kilo? this is outside of devstack. I thought I had it configured and when I log into horizon, I see the magnum service is started, but when I execute cli commands such as: magnum service-list or magnum container-list I get

Re: [openstack-dev] magnum on OpenStack Kilo

Bruce, That sounds like this bug to me: https://bugs.launchpad.net/magnum/+bug/1411333 Resolved by: https://review.openstack.org/148059 I think you need this: keystone service-create --name=magnum \ --type=container \ --description="magnum

Re: [openstack-dev] magnum on OpenStack Kilo

Bruce, Another suggestion for your consideration: The region the client is using needs to match the region the endpoint is set to use in the service catalog. Check that OS_REGION_NAME in the environment running the client is set to ‘RegionOne’ rather than ‘regionOne’. That has snagged others

[openstack-dev] [magnum]generate config files by magnum

Hi forks, Magnum needs to prepare config files for k8s and docker and add these services to systemd. Now we use "sed" to replace some parameters in config files. The method has a disadvantage. Magnum code depends on a specific image. Users may want to create images by themselves. The config

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

Hi Steve, It is really a big loss to Magnum and thanks very much for your help in my Magnum journey. Wish you good luck in Kolla! On Tue, Oct 27, 2015 at 2:29 PM, 大塚元央 wrote: > Hi Steve, > > I'm very sad about your stepping down from Magnum core. Without your help, > I

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

Hi Steve, I'm very sad about your stepping down from Magnum core. Without your help, I couldn't contribute to magnum project. But kolla is also fantastic project. I wish you the best of luck in kolla. Best regards. - Yuanying Otsuka On Tue, Oct 27, 2015 at 00:39 Baohua Yang

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

stack-dev@lists.openstack.org> Date: 26/10/2015 09:22 am Subject:[openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer Hey folks, It is with sadness that I find myself under the situation to have to write this message. I have the privilege of b

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum corereviewer

for ideas. Ton, From: "Steven Dake (stdake)" <std...@cisco.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 10/25/2015 05:22 PM Subject:[openstack-dev] [magnum][kolla

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

Really a pity! We need more resources on the container part in OpenStack indeed, as so many new projects are just initiated. Community is not only about putting technologies together, but also putting technical guys together. Happy to see so many guys in the Tokyo Summit this afternoon. Let's

[openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

Hey folks, It is with sadness that I find myself under the situation to have to write this message. I have the privilege of being involved in two of the most successful and growing projects (Magnum, Kolla) in OpenStack. I chose getting involved in two major initiatives on purpose, to see if

Re: [openstack-dev] [magnum] k8s api tls_enabled mode testing

Hi, Eli Qiao If ca or client certs is wrong, I think client will get error before `client hello`. I tested broken ca cert and client cert in my local environment. See below logs. yuanying@devstack:~/temp$ curl https://192.168.19.92:6443 --tlsv1.0 -v --key ./client.key --cert ./client.crt

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

Steve, Thanks so much for your contributions to Magnum. You have played a critically important role for us, and we are saddened to hear the news of your departure. You are welcome to return at any time. Cheers, Adrian On Oct 26, 2015, at 9:17 AM, Steven Dake (stdake)

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

: October-25-15 8:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer Hey folks, It is with sadness that I find myself under the situation to have to write this message. I have the privilege

Re: [openstack-dev] [Magnum] Coe components status

r usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, October 20, 2015 at 20:56 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.opensta

[openstack-dev] [magnum] k8s api tls_enabled mode testing

Hello, I need your help on k8s api tls_enabled mode. Here’s my patch https://review.openstack.org/232421 It is always failed on gate, but it works in my setup. Debug more I found that the ca cert return api return length with difference: On my setup： 10.238.157.49 - - [21/Oct/2015 19:16:17]

[openstack-dev] [Magnum] Mitaka Design Summit Sessions in Tokyo

Magnum Team, For those of you attending the Mitaka Design Summit in Tokyo next week, here are the sessions that I respectfully request you attend: 2015-10-28, 11:15-11:55 http://sched.co/4Qck Heat Template Refactoring 2015-10-28, 12:05-12:45 http://sched.co/4Qdc Magnum Scalability (Work

[openstack-dev] [Magnum] Coe components status

Hi Team, I would appreciate any opinion/concern regarding "coe-component-status" feature implementation [1]. For example in k8s, using API api/v1/namespaces/{namespace}/componentstatuses, status of each k8s component can be queried. My approach would be to provide a command in magnum like

Re: [openstack-dev] [Magnum] Coe components status

hi Vikas, thanks for propose this changes, I wonder if you can show some examples for other coes we currently supported: swarm, mesos ? if we propose a public api like you proposed, we'd better to support all coes instead of coe specific. thanks Eli. On 2015年10月20日 18:14, Vikas Choudhary

Re: [openstack-dev] [Magnum] Coe components status

@ Eli , I will look into how to support this feature for other COEs also(mesos and swarm). But anyways Magnum's goal is to provide users *atleast* what other coes are providing (if not something extra). All coes dont have common features, so we cant be very strict on providing common interface

Re: [openstack-dev] [Magnum] Coe components status

+ 1 to vikas. As we have monitor framework only to docker swarm COE at present and we are pushing other COE drivers in future. So it is better to have component status for one COE at first and will push other COEs support later. Correct me if I am wrong. Regards Bharath T On Wed, Oct 21, 2015

Re: [openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2

Hi Ton, "docker --help" command works ok, but [fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ sudo /usr/bin/docker -d -H fd:// -H tcp://0.0.0.0:2375 --tlsverify --tlscacert="/etc/docker/ca.crt" --tlskey="/etc/docker/server.key" --tlscert="/etc/docker/server.crt"

Re: [openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2

Hi Hongbin, I can ssh into the swarm node, and curl cmd works ok: [fedora@sw-d7cum4a5z5a-0-dx4eksy72u4q-swarm-node-3d7bwzm7fso7 ~]$ curl openstack.org 301 Moved Permanently 301 Moved Permanently nginx On Fri, Oct 16, 2015 at 2:36 PM, Mars Ma wrote: > Hi, > > I used image

Re: [openstack-dev] [magnum] Failed to create swarm baywithfedora-21-atomic-5-d181.qcow2

t;openstack-dev@lists.openstack.org> Date: 10/16/2015 01:05 PM Subject: Re: [openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2 Hi Mars, I cannot reproduce the error. My best

Re: [openstack-dev] [magnum] Failed to create swarm baywithfedora-21-atomic-5-d181.qcow2

ent Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 10/16/2015 01:05 PM Subject:Re: [openstack-dev] [magnum] Failed to create swarm bay withfedora-21-atomic-5-d181.qcow2 Hi Mars, I cannot reproduce the error. My best guess

Re: [openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2

From: Mars Ma [mailto:wenc...@gmail.com] Sent: October-16-15 2:37 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2 Hi, I used image fedora-21-atomic-5-d181.qcow2 to create swarm bay , but the bay went to failed

[openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2

Hi, I used image fedora-21-atomic-5-d181.qcow2 to create swarm bay , but the bay went to failed status with status reason: Resource CREATE failed: WaitConditionFailure: resources.swarm_nodes.resources[0].resources.node_agent_wait_condition: swarm-agent service failed to start. debug inside swarm

Re: [openstack-dev] [magnum] Creating pods results in "EOF occurred in violation of protocol" exception

: October-14-15 8:51 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Creating pods results in "EOF occurred in violation of protocol" exception Hi, I try Magnum, following instructions on the quickstart page [1]. I successful

[openstack-dev] [magnum] Creating pods results in "EOF occurred in violation of protocol" exception

Hi, I try Magnum, following instructions on the quickstart page [1]. I successfully create the baymodel and the bay. When I run the command to create redis pods (_magnum pod-create --manifest ./redis-master.yaml --bay k8sbay_), client side, it timeouts. And server side (m-cond.log), I get the

[openstack-dev] [magnum] Networking Subteam Meeting Cancelations

All, I have a conflict this week and will be unable to chair the weekly irc meeting [1]. Therefore, we will not meet this week. 10/22 and 10/29 meetings will also be canceled due to the Mitaka Design Summit. We will resume are regularly scheduled meetings on 11/5. [1]

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

you might want to be inspired by that. Regards, Neil From: Adrian Otto Sent: Thursday, 8 October 2015 21:07 To: OpenStack Development Mailing List (not for usage questions) Reply To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Document

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

te: Thursday, October 8, 2015 at 1:04 PM 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] Document adding --memory option to create containers

[openstack-dev] [Magnum] Testing result of new atomic-6 image

Testing result of new atomic-6 image [1] built by Tango atomic-5 image has issue to start a container instance(docker version is 1.7.1), Tango built a new atomic-6 image with docker 1.8.1 version. eghobo and I (eliqiao) did some testing works (eghobo_ did most of them) Here is the summary: *

Re: [openstack-dev] [magnum] New Core Reviewers

gt; +1 for both. Welcome! >>> >>> >>> >>> *From:* Davanum Srinivas [mailto:dava...@gmail.com] >>> *Sent:* September-30-15 7:00 PM >>> *To:* OpenStack Development Mailing List (not for usage questions) >>> *Subject:* Re: [openstack-dev] [m

[openstack-dev] [magnum] How to verify a service is correctly setup in heat template

hi Magnum hackers: Recently, we upgrade to fedora atomic-5 image, but the docker (1.7.1) in that image doesn't works well. see [1]. When I using that image to create a swarm bay, magnum told me that bay is usable, actually swarm-master swarm-agent service are not running correctly, so that

[openstack-dev] [magnum] Document adding --memory option to create containers

Hi team, I want to move the discussion in the review below to here, so that we can get more feedback https://review.openstack.org/#/c/232175/ In summary, magnum currently added support for specifying the memory size of containers. The specification of the memory size is optional, and the COE

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

Thanks Hongbin, for raising this for discussion. There is a middle ground that we can reach. We can collect a set of “best practices”, and place them together in a document. Some of them will be operational best practices for cloud operators, and some of them will be for end users. We can make

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

enstack-dev@lists.openstack.org > >> > Date: Thursday, October 8, 2015 at 13:04 > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org > >> > Subject: Re: [op

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

gt; Date: Thursday, October 8, 2015 at 9:00 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [magnum] Document adding --memory option to create con

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

t for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum] Document adding --memory option to create containers Steve, I agree with the concept of a simple quickstart doc, but there also needs to

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

<liyong.q...@intel.com> To: openstack-dev@lists.openstack.org Date: 10/08/2015 06:32 PM Subject: Re: [openstack-dev] [magnum] Document adding --memory option to create containers +1, we can add more detail explanation information of --memory in magnum CLI instead of q

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

<mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>>> Subject: Re: [openstack-dev] [magnum] Document adding --memory option to create containers Steve, I agree with the concept of a simple

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [magnum] Document adding --memory option to create containers Hi team, I want to move the discussion in the review below to here, so that we can get more feedback https://review.openstack.org/#/c/232175/ In summary, magnu

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

st (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [magnum] Document adding --memory option to create containers Hi team, I want to move the discussion in the review below to here, so that we c

Re: [openstack-dev] [magnum] New Core Reviewers

gt; >> *From:* Davanum Srinivas [mailto:dava...@gmail.com] >> *Sent:* September-30-15 7:00 PM >> *To:* OpenStack Development Mailing List (not for usage questions) >> *Subject:* Re: [openstack-dev] [magnum] New Core Reviewers >> >> >> >> +1 from m

Re: [openstack-dev] [magnum] New Core Reviewers

From: Davanum Srinivas [mailto:dava...@gmail.com<mailto:dava...@gmail.com>] Sent: September-30-15 7:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] New Core Reviewers +1 from me for both Vilobh and Hua. Thanks, Dims On Wed, Sep 30

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

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?

...@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?

I believe keystone already supports hierarchical projects Thanks, Kevin From: Hongbin Lu [hongbin...@huawei.com] Sent: Thursday, October 01, 2015 7:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum

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

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

[openstack-dev] [Magnum]: PTL Voting is now open

If you are a Foundation individual member and had a commit in one of Magnum's projects[0] over the Kilo-Liberty timeframe (September 18, 2014 06:00 UTC to September 18, 2015 05:59 UTC) then you are eligible to vote. You should find your email with a link to the Condorcet page to cast your vote in

Re: [openstack-dev] [Magnum]: PTL Voting is now open

I want to thank personally and publicly our election officials for their willingness to take care of this election. Nice work, Tony and Tristan. Much appreciated. Anne On Thu, Oct 1, 2015 at 5:58 PM, Tony Breeds wrote: > If you are a Foundation individual member and

Re: [openstack-dev] [magnum] New Core Reviewers

usage questions) > *Subject:* Re: [openstack-dev] [magnum] New Core Reviewers > > > > +1 from me for both Vilobh and Hua. > > > > Thanks, > > Dims > > > > On Wed, Sep 30, 2015 at 6:47 PM, Adrian Otto <adrian.o...@rackspace.com> > wrote: > > Co

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

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?

ackspace.com >> Reply-To: “OpenStack Development Mailing List (not for usage questions)“ < openstack-dev@lists.openstack .org >> Date: Tuesday, September 29, 2015 at 08:44 To: “OpenStack Development Mailing List (not for usage questions)“ < openstack-dev@lists.openstack .org >> Subject

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

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?

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?

. 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] New Core Reviewers

+1 for both. Welcome! From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: September-30-15 7:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] New Core Reviewers +1 from me for both Vilobh and Hua. Thanks, Dims On Wed, Sep 30, 2015

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

;>> 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] New Core Reviewers

+1 from me for both Vilobh and Hua. Thanks, Dims On Wed, Sep 30, 2015 at 6:47 PM, Adrian Otto wrote: > Core Reviewers, > > I propose the following additions to magnum-core: > > +Vilobh Meshram (vilobhmm) > +Hua Wang (humble00) > > Please respond with +1 to agree or

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

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 >>

[openstack-dev] [magnum] New Core Reviewers

Core Reviewers, I propose the following additions to magnum-core: +Vilobh Meshram (vilobhmm) +Hua Wang (humble00) Please respond with +1 to agree or -1 to veto. This will be decided by either a simple majority of existing core reviewers, or by lazy consensus concluding on 2015-10-06 at 00:00

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 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?

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?

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?

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?

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?

: 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?

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?

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?

@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?

: 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?

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?

-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?

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?

" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: 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.openstac

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

> 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?

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?

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

<    5   6   7   8   9   10   11   12   13   14   >