Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

m> >> To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org> >> Date: 08/05/2016 04:51 AM >> >> Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of >> nodes >> -

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

om> > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: 08/05/2016 04:51 AM > > Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of > nodes > -- > &

Re: [openstack-dev] [Magnum] Adding opensuse as new driver to Magnum

penstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Magnum] Adding opensuse as new driver to > Magnum > > Michal, > > The right place for drivers is the /drivers folder. > > Take a look at the existing drivers as an examples. You'll also need to > update this fil

Re: [openstack-dev] [magnum] devstack magnum.conf

ig...@gmail.com> > *Kime: *"OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > *Gönderilenler: *5 Ağustos Cuma 2016 19:32:11 > *Konu: *Re: [openstack-dev] [magnum] devstack magnum.conf > > > Hi,

Re: [openstack-dev] [magnum] devstack magnum.conf

elopment Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Gönderilenler: 5 Ağustos Cuma 2016 19:32:11 Konu: Re: [openstack-dev] [magnum] devstack magnum.conf Hi, better follow the quickstart guide [1]. Cheers, Spyros [1] http://docs.openstack.org/developer/m

Re: [openstack-dev] [magnum] devstack magnum.conf

Hi, better follow the quickstart guide [1]. Cheers, Spyros [1] http://docs.openstack.org/developer/magnum/dev/quickstart.html On 5 August 2016 at 06:22, Yasemin DEMİRAL (BİLGEM BTE) < yasemin.demi...@tubitak.gov.tr> wrote: > > Hi > > I try to magnum on devstack, in the manual Configure

Re: [openstack-dev] [magnum][heat] 2 million requests / sec, 100s of nodes

Add [heat] to the title to get more feedback. Best regards, Hongbin From: Ricardo Rocha [mailto:rocha.po...@gmail.com] Sent: August-05-16 5:48 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes Hi

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

ack.org> Date: 08/05/2016 04:51 AM Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes Hi. Quick update is 1000 nodes and 7 million reqs/sec :) - and the number of requests should be higher but we had some internal issues. We have a submission fo

Re: [openstack-dev] [magnum]

Hi, You can run `tox -egenconfig` under magnum directory, to generate sample conf. #Chinmay On 5 August 2016 at 16:51, Yasemin DEMİRAL (BİLGEM BTE) < yasemin.demi...@tubitak.gov.tr> wrote: > Hi > > I try to magnum on devstack, in the manual Configure magnum: section > has sudo cp

[openstack-dev] [magnum] devstack magnum.conf

Hi I try to magnum on devstack, in the manual Configure magnum: section has sudo cp etc/magnum/magnum.conf.sample /etc/magnum/magnum.conf command, but there is no magnum.conf. What should i do ? Thanks Yasemin __

[openstack-dev] [magnum]

Hi I try to magnum on devstack, in the manual Configure magnum: section has sudo cp etc/magnum/magnum.conf.sample /etc/magnum/magnum.conf command, but there is no magnum.conf. What should i do ? Thanks Yasemin __

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

t \(not for usage questions\)" < > openstack-dev@lists.openstack.org> > Date: 06/17/2016 12:10 PM > Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of > nodes > > -- > > > > Thanks Ricardo for sharing the data,

Re: [openstack-dev] [Magnum] Adding opensuse as new driver to Magnum

ck-dev@lists.openstack.org Subject: [openstack-dev] [Magnum] Adding opensuse as new driver to Magnum Hi, I would like to put for discussion adding new driver to Magnum. We would like to propose opensuse with kubernetes as driver. I did some initial work in bug https://launchpad.net/bugs/1600197 and changes

[openstack-dev] [Magnum] Adding opensuse as new driver to Magnum

Hi, I would like to put for discussion adding new driver to Magnum. We would like to propose opensuse with kubernetes as driver. I did some initial work in bug https://launchpad.net/bugs/1600197 and changes https://review.openstack.org/339480 https://review.openstack.org/349994 I've got

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

10:58 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for > Magnum core reviewer team > > +1 great addition to the team > > From: Hongbin Lu <hongbin...@huawei.com> > Reply-

Re: [openstack-dev] [Magnum] Microversioning implementation

: [openstack-dev] [Magnum] Microversioning implementation Hongbin & team Please forget Semantic Versioning API, that should not be done in short term especially API WG had defined lots of Microversion API docs, sorry to make confusions. Of cause that Microversion API is important to OpenS

Re: [openstack-dev] [Magnum] Microversioning implementation

: Re: [openstack-dev] [Magnum] Microversioning implementation I was completely unaware of any discussion of Semantic Versioning. That was brought up by Eli Qiao in the code review, so he might be the one to point us in the right direction for that. Jaycen -Original Message- From: Hongbi

Re: [openstack-dev] [Magnum] Microversioning implementation

OK. My replies are inline. > -Original Message- > From: Grant, Jaycen V [mailto:jaycen.v.gr...@intel.com] > Sent: July-28-16 2:31 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Magnum] Microversioning implem

Re: [openstack-dev] [Magnum] Microversioning implementation

, 2016 11:10 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Magnum] Microversioning implementation Added this to the agenda of next team meeting [1]. I would like to ask clarification for " th

Re: [openstack-dev] [Magnum] Microversioning implementation

ginal Message- > From: Grant, Jaycen V [mailto:jaycen.v.gr...@intel.com] > Sent: July-28-16 10:52 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [Magnum] Microversioning implementation > > > There has been a discussion around micro

[openstack-dev] [Magnum] Microversioning implementation

There has been a discussion around micro versioning implementation going on in the following patch: https://review.openstack.org/#/c/343060/8 and I was asked to bring it to the mailing list for further discussion. Magnum added header support for microversioning according to the Openstack

Re: [openstack-dev] [Magnum] Select our project mascot/logo

gt; Subject: Re: [openstack-dev] [Magnum] Select our project mascot/logo > > > Does anyone know that Magnum is a brand of ice cream[1]? > > I love it! can we use it, maybe it may bring some copyright issue, but > I don't know.. > > [1] http://www.magnumicecream.com/us/en/h

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility Hi Wenzhi, Looks like you are adding the new --rollback option to bay-update. If the user does not specify this new option,

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility Hi Wenzhi, Looks like you are adding the new --rollback option to bay-update. If the user does not specify this new option,

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

ngbin From: Ton Ngo [mailto:t...@us.ibm.com] Sent: July-27-16 9:36 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility Hi Wenzhi, Looks like you are adding the new -

Re: [openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

? If so, this does change the API, but does not seem to break backward compatibility. Ton Ngo, From: "Wenzhi Yu (yuywz)" <wenzhi...@163.com> To: "openstack-dev" <openstack-dev@lists.openstack.org> Date: 07/27/2016 04:13 AM Subject:[openstack-dev] [magn

[openstack-dev] [magnum] Support for bay rollback may break magnum API backward compatibility

Hi folks, I am working on a patch [1] to add bay rollback machanism on update failure. But it seems to break magnum API backward compatibility. I'm not sure how to deal with this, can you please give me your suggestion? Thanks! [1]https://review.openstack.org/#/c/343478/ 2016-07-27 Best

Re: [openstack-dev] [Magnum] Select our project mascot/logo

: Wednesday, July 27, 2016 9:26 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Magnum] Select our project mascot/logo Dims, You are fast :). I believe OpenStack Foundation will coordinate in this case.

Re: [openstack-dev] [Magnum] Select our project mascot/logo

: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Wednesday, July 27, 2016 9:26 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Magnum] Select our project mascot/logo Dims, You are fast :). I believe Ope

Re: [openstack-dev] [Magnum] Select our project mascot/logo

gt; Subject: Re: [openstack-dev] [Magnum] Select our project mascot/logo > > Hongbin, > > Moose is already taken by Oslo team (2 summits ago :) > > -- Dims > > On Tue, Jul 26, 2016 at 9:48 PM, Hongbin Lu <hongbin...@huawei.com> > wrote: > > Hi all, > >

Re: [openstack-dev] [Magnum] Select our project mascot/logo

; * Majestic moose - > https://images.indiegogo.com/file_attachments/1328366/files/20150326083908-Mooselaughing.jpg?1427384348 > > > > Best regards, > > Hongbin > > > > From: Watson, Stephen [mailto:stephen.wat...@intel.com] > Sent: July-26-16 12:09 PM > To: OpenStack

Re: [openstack-dev] [Magnum] Select our project mascot/logo

To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum] Select our project mascot/logo +1 for kangaroo and stallion And my own suggestion even though it doesn’t fit the container or name themes directly would be a St. Bernard because dogs and myths

Re: [openstack-dev] [Magnum] Select our project mascot/logo

ck-dev@lists.openstack.org> Subject: [openstack-dev] [Magnum] Select our project mascot/logo Hi team, OpenStack want to promote individual projects by choosing a mascot to represent the project. The idea is to create a family of logos for OpenStack projects that are unique, yet immediately identi

Re: [openstack-dev] [Magnum] Select our project mascot/logo

nstack.org> Date: 07/25/2016 03:56 PM Subject:[openstack-dev] [Magnum] Select our project mascot/logo Hi team, OpenStack want to promote individual projects by choosing a mascot to represent the project. The idea is to create a family of logos for OpenStack projects that are un

Re: [openstack-dev] [Magnum] Select our project mascot/logo

How about a shark? Something along these lines: http://www.logoground.com/logo.php?id=10554 On Jul 25, 2016, at 3:54 PM, Hongbin Lu wrote: Hi team, OpenStack want to promote individual projects by choosing a mascot to represent the project. The idea is to create a

Re: [openstack-dev] [Magnum] Select our project mascot/logo

List (not for usage questions) Subject: [openstack-dev] [Magnum] Select our project mascot/logo Hi team, OpenStack want to promote individual projects by choosing a mascot to represent the project. The idea is to create a family of logos for OpenStack projects that are unique, yet immediately

Re: [openstack-dev] [Magnum] Select our project mascot/logo

: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Monday, July 25, 2016 3:55 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [Magnum] Select our project mascot/logo Hi team, OpenStack want to promote individual pr

[openstack-dev] [Magnum] Select our project mascot/logo

Hi team, OpenStack want to promote individual projects by choosing a mascot to represent the project. The idea is to create a family of logos for OpenStack projects that are unique, yet immediately identifiable as part of OpenStack. OpenStack will be using these logos to promote each project

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

age questions)" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team Hi all, Spyros has consistently contributed to Magnum for a while. In my opinion, what differentiate him from others is the significance of

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

teFrom:Hongbin Lu <hongbin...@huawei.com>To:"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>Date:07/22/2016 01:30 PMSubject: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum corerev

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

+1, it has been a pleasure to work with Spyros. Ton Ngo, From: Hongbin Lu <hongbin...@huawei.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 07/22/2016 01:30 PM Subject: [

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

+1 for Sypros. Regards, Madhuri From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Saturday, July 23, 2016 1:57 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnu

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

+1 -- Adrian On Jul 22, 2016, at 10:28 AM, Hongbin Lu > wrote: Hi all, Spyros has consistently contributed to Magnum for a while. In my opinion, what differentiate him from others is the significance of his contribution, which adds

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

+1, Spyros will be a great addition to the team. Yuanying 2016年7月25日(月) 9:39 taget : > I am +1 > > Eli. > > > On 2016年07月23日 04:27, Hongbin Lu wrote: > > Hi all, > > > > Spyros has consistently contributed to Magnum for a while. In my opinion, > what differentiate him from

Re: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

I am +1 Eli. On 2016年07月23日 04:27, Hongbin Lu wrote: Hi all, Spyros has consistently contributed to Magnum for a while. In my opinion, what differentiate him from others is the significance of his contribution, which adds concrete value to the project. For example, the operator-oriented

Re: [openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Your a class act Dims. It was good working with you on Magnum :) Regards -steve On 7/22/16, 2:15 PM, "Davanum Srinivas" wrote: >Thanks Hongbin! > >On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote: >> Hi all, >> >> >> >> Based on Dims¹s request, I

Re: [openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Thanks Hongbin! On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote: > Hi all, > > > > Based on Dims’s request, I removed him from the Magnum core reviewer team. > Dims’s contribution started from the first commit of the Magnum tree, and he > was served as a Magnum core

[openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Hi all, Based on Dims's request, I removed him from the Magnum core reviewer team. Dims's contribution started from the first commit of the Magnum tree, and he was served as a Magnum core reviewer for a long time. I am sorry to hear that Dims want to leave the team, but thanks for his

[openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core reviewer team

Hi all, Spyros has consistently contributed to Magnum for a while. In my opinion, what differentiate him from others is the significance of his contribution, which adds concrete value to the project. For example, the operator-oriented install guide he delivered attracts a significant number of

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

nt Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes Sounds ok, but there needs to be a careful upgrade/migration path, where both are supported until after all pods are migra

Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ?

<openstack-dev@lists.openstack.org> Date: 07/20/2016 04:51 AM Subject: Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ? Thanks Ton, When is the Docker libnetwork functionality forecasted to be available ? Greg. From:

Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ?

ack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ? Hi Greg, This is a capability that we are working on at this time: enabling Docker libnetwork using the Kuryr driver. T

Re: [openstack-dev] [Magnum] What is Magnum's behaviour wrt Images in Glance and which ones are downloaded to COE ?

On 2016年07月20日 00:35, Waines, Greg wrote: Does MAGNUM automatically download all Glance Images of a particular Container Format to the COE ? No, Magnum will not do this. Only the swarm docker image is download by Magnum. In the above setup, which Glance Image does the ‘docker image’

Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ?

, From: "Waines, Greg" <greg.wai...@windriver.com> To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Date: 07/19/2016 11:12 AM Subject:[openstack-dev] [Magnum] Does Docker-Swarm not support inter-no

[openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ?

I have successfully setup devstack with Magnum, following this link https://github.com/openstack/magnum/blob/master/doc/source/dev/quickstart.rst#building-and-using-a-swarm-bay I created a Docker-Swarm bay and successfully launched some simple containers. I noticed that Docker-Swarm’s Container

[openstack-dev] [Magnum] What is Magnum's behaviour wrt Images in Glance and which ones are downloaded to COE ?

I have successfully setup devstack with Magnum, following this link https://github.com/openstack/magnum/blob/master/doc/source/dev/quickstart.rst#building-and-using-a-swarm-bay I created a Docker-Swarm bay and successfully launched a simple container. What is the behavior of MAGNUM wrt

Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

s, > > Madhuri > > > > *From:* Waines, Greg [mailto:greg.wai...@windriver.com] > *Sent:* Monday, July 18, 2016 5:11 PM > *To:* openstack-dev@lists.openstack.org > *Subject:* [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ? > > > > I’m relatively new

Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

onday, July 18, 2016 at 10:07 AM To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ? Hi Greg, Now it is not mandatory to have lbaas in Magnum. Here is blueprint in Magnum

Re: [openstack-dev] [Magnum] Following Magnum QuickStart page, how do i use Docker CLI directly to manage containers

[mailto:greg.wai...@windriver.com] Sent: Monday, July 18, 2016 6:53 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Magnum] Following Magnum QuickStart page, how do i use Docker CLI directly to manage containers Was trying out Magnum in Devstack, following the instructions

Re: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

allows you to disable lbaas when master count is 1. Regards, Madhuri From: Waines, Greg [mailto:greg.wai...@windriver.com] Sent: Monday, July 18, 2016 5:11 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ? I’m relatively new to looking

[openstack-dev] [Magnum] Following Magnum QuickStart page, how do i use Docker CLI directly to manage containers

Was trying out Magnum in Devstack, following the instructions at http://docs.openstack.org/developer/magnum/dev/dev-quickstart.html I successfully created a swarmbay. test -f ~/.ssh/id_rsa.pub || ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa nova keypair-add --pub-key ~/.ssh/id_rsa.pub testkey magnum

[openstack-dev] [Magnum] Is LBAAS mandatory for MAGNUM ?

I’m relatively new to looking at Magnum. Just recently played with Magnum in devstack on Newton. I noticed that the HEAT Stack used by Magnum created Load Balancer Pool and Load Balancer HealthMonitor. QUESTION … Is LBAAS support mandatory for MAGNUM ? or can it be used (configured) without it

[openstack-dev] [Magnum] Discussing approaches to build `Discovery options for bay types`

Hey All, Wanted to discuss integration of locally hosted discovery mechanisms, as proposed in the following blueprint https://blueprints.launchpad.net/magnum/+spec/bay-type-discovery-options. As suggested by Hongbin, taking inspiration from the etcd approach is good

Re: [openstack-dev] [magnum] Use Keystone trusts in Magnum?

make it a lot easier. I'll give it a try... Cheers, Johannes Best regards, Hongbin -Original Message- From: Johannes Grassler [mailto:jgrass...@suse.de] Sent: July-06-16 9:40 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [magnum] Use Keystone trusts in Magnum

[openstack-dev] [magnum] Use Keystone trusts in Magnum?

Hello, I submitted https://review.openstack.org/#/c/326428 a while ago to get around having to configure Heat's policy.json in a very permissive manner[0]. I naively only tested it as one user, but gating caught that omission and dutifully failed (a user cannot stack-get another user's Heat

Re: [openstack-dev] [magnum][heat] Global stack-list for Magnum service user

+1. Id like to see a similar thing for keystone validate user tokens. Thanks, Kevin From: Johannes Grassler Sent: Monday, July 04, 2016 2:43:47 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [magnum][heat] Global stack-list for Magnum service

Re: [openstack-dev] [magnum][heat] Global stack-list for Magnum service user

Hello, Thanks for the exhaustive comment on the issue. Won't help much in the short term, but it's good to see there will eventually be a way to sort this out properly! On 07/04/2016 12:50 PM, Steven Hardy wrote: On Mon, Jul 04, 2016 at 11:43:47AM +0200, Johannes Grassler wrote: [Magnum's

Re: [openstack-dev] [magnum][heat] Global stack-list for Magnum service user

On Mon, Jul 04, 2016 at 11:43:47AM +0200, Johannes Grassler wrote: > Hello, > > Magnum has a periodic task that checks the state of the Heat stacks it creates > for its bays. It does this across all users/tenants that have Magnum bays. > Currently it uses a global stack-list operation to query

Re: [openstack-dev] [magnum][heat] Global stack-list for Magnum service user

Hi Johannes, this is still not too optimal, as AFAIK admin role is still global, so admin in tenant also means admin of whole OpenStack, thus it still can assign himself/whomever the 'service' role and get access to global stack list. Best solution would probably be to create a separate domain

[openstack-dev] [magnum][heat] Global stack-list for Magnum service user

Hello, Magnum has a periodic task that checks the state of the Heat stacks it creates for its bays. It does this across all users/tenants that have Magnum bays. Currently it uses a global stack-list operation to query these Heat stacks:

[openstack-dev] [Magnum] Want to know our users

Hi all, FYI. The Magnum team is collecting a list of Magnum users. If you are using Magnum, we would like to have your name and organization recorded in our wiki [1]. Please note that this is totally optional, but we hope you will let us know if you are our users. [1]

[openstack-dev] [Magnum]Midcycle

Hi all, The Magnum midcycle will be held in Aug 4 - 5 at Austin. Below is the link to register. Hope to see you all there. https://www.eventbrite.com/e/magnum-midcycle-tickets-26245489967 Best regards, Hongbin __ OpenStack

Re: [openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi Yuanying. On 21 June 2016 at 08:02, Yuanying OTSUKA wrote: > Hi, Spyros > > Thanks for testing it. > Maybe you see that there are some problems to support baremetal. > We should add functional test to our jenkins job > because this template will be broken easily if

Re: [openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi, Spyros Thanks for testing it. Maybe you see that there are some problems to support baremetal. We should add functional test to our jenkins job because this template will be broken easily if anyone adds some logic to our templates/codes. But following problems will block us. 1. How to get

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

/2016-June/097522.html [2] https://review.openstack.org/#/c/328822/ Best regards, Hongbin > -Original Message- > From: Ricardo Rocha [mailto:rocha.po...@gmail.com] > Sent: June-07-16 3:02 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-de

[openstack-dev] [Magnum] Midcycle location and date

Hi all, This is a reminder that there are doodle pools for midcycle participants to select the location and time: Location: http://doodle.com/poll/2x9utspir7vk8ter Date: http://doodle.com/poll/5tbcyc37yb7ckiec If you are able to attend the midcycle, I encourage you to vote for your preferred

Re: [openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi Yuanying, I tested your patch [2] with the image that Ton created [1] and it worked. For me devicemapper as docker-storage-driver didn't work but this is unrelated to this patch, I'll update devicemapper. I used overlay and it was ok. I'll sum up what I did here, for others to test. On a

Re: [openstack-dev] [magnum] Stable/liberty functional tests

On Tue, Jun 14, 2016 at 01:25:14PM +, Bunting, Niall wrote: > Hi, > > > There was work on a patch [1] to fix the liberty stable branch. However, we > are running into problems with the functional tests, because the functional > tests were set up differently in liberty eg. The current [2]

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

List \(not for usage questions \)" <openstack-dev@lists.openstack.org> Date: 06/17/2016 12:10 PM Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes Thanks Ricardo for sharing the data, this is really encouraging! Ton, Inactive hide det

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

(not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes Thanks Ricardo for sharing the data, this is really encouraging! Ton, [Inactive hide detail

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

ge questions) > Subject: [openstack-dev] [magnum] 2 million requests / sec, 100s of > nodes > > Hi. > > Just thought the Magnum team would be happy to hear :) > > We had access to some hardware the last couple days, and tried some > tests with Magnum and Kubernetes

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes Hi. Just thought the Magnum team would be happy to hear :) We had access to some hardware the last couple days, and tried some tests with Magnum and Kubernetes - fol

Re: [openstack-dev] [Magnum] The Magnum Midcycle

On Jun 14, 2016, at 3:37 PM, Anita Kuno wrote: > > What other projects would make sense for you to host mid-cycles for > should the opportunity arise? I can keep my ears open. Nova! Nova! Nova! -- Ed Leafe (really wants to see the LHC!)

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Thanks Ricardo for sharing the data, this is really encouraging! Ton, From: Ricardo Rocha <rocha.po...@gmail.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 06/17/2016 08:16 AM Subject:

[openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Hi. Just thought the Magnum team would be happy to hear :) We had access to some hardware the last couple days, and tried some tests with Magnum and Kubernetes - following an original blog post from the kubernetes team. Got a 200 node kubernetes bay (800 cores) reaching 2 million requests /

Re: [openstack-dev] [magnum][heat] spawn a group of nodes on different availability zones

On 07/06/16 23:53, Hongbin Lu wrote: Hi Heat team, A question inline. Best regards, Hongbin -Original Message- From: Steven Hardy [mailto:sha...@redhat.com] Sent: March-03-16 3:57 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum

Re: [openstack-dev] [Magnum] The Magnum Midcycle

im Bell [mailto:tim.b...@cern.ch] > Sent: June-09-16 2:27 PM > > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle > > > > If we can confirm the dates and location, there is a reasonable chance we > could a

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

2016 3:04 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Cc: Katou Haruhiko(加藤 治彦) <har-ka...@ts.jp.nec.com> > Subject: Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, > and removal notice &

Re: [openstack-dev] [magnum][lbaas][docs] Operator-facing installation guide

(not for usage questions) Subject: Re: [openstack-dev] [magnum][lbaas][docs] Operator-facing installation guide Let us know if this is what you're looking for: http://docs.openstack.org/mitaka/networking-guide/adv-config-lbaas.html Thanks Major Hayden for writing it up. Anne On Tue, Jun 14, 2016

Re: [openstack-dev] [magnum][lbaas][docs] Operator-facing installation guide

est regards, > Hongbin > > > -Original Message- > > From: Adrian Otto [mailto:adrian.o...@rackspace.com] > > Sent: June-02-16 6:50 PM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [magnum][lbaas] Operato

Re: [openstack-dev] [magnum][lbaas][docs] Operator-facing installation guide

regards, Hongbin > -Original Message- > From: Adrian Otto [mailto:adrian.o...@rackspace.com] > Sent: June-02-16 6:50 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][lbaas] Operator-facing > installation

Re: [openstack-dev] [Magnum] The Magnum Midcycle

" > <openstack-dev@lists.openstack.org> > Date: Wednesday 8 June 2016 at 16:43 > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle >

Re: [openstack-dev] [Magnum] The Magnum Midcycle

regards, Hongbin From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: June-09-16 3:56 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle Rackspace is willing to host in Austin, TX or San Antonio, TX, or San Francisco

Re: [openstack-dev] [Magnum] The Magnum Midcycle

regards, Hongbin From: Tim Bell [mailto:tim.b...@cern.ch] Sent: June-09-16 2:27 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle If we can confirm the dates and location, there is a reasonable chance we could also offer

[openstack-dev] [magnum] Stable/liberty functional tests

Hi, There was work on a patch [1] to fix the liberty stable branch. However, we are running into problems with the functional tests, because the functional tests were set up differently in liberty eg. The current [2] magnum.yaml compared to the old one [3]. This leads us with two options to

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

+1 Ton Ngo, From: Shuu Mutou <shu-mu...@rf.jp.nec.com> To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Cc: Haruhiko Katou <har-ka...@ts.jp.nec.com> Date: 06/10/2016 02:41 AM Subject: [openstack-dev] [magn

Re: [openstack-dev] [magnum] Notes for Magnum design summit

(not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit Gary, It is hard to tell if your change fits into Magnum upstream or not, unless there are further details. I encourage you to upload your changes to gerr

Re: [openstack-dev] [magnum] Notes for Magnum design summit

[mailto:strig...@gmail.com] Sent: Monday, June 13, 2016 3:59 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit Hi Gary. On 13 June 2016 at 09:06, Duan, Li-Gong (Gary, HPServers-C

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

2 PM, Shuu Mutou < > shu-mu...@rf.jp.nec.com> wrote: > > From: 王华 <wanghua.hum...@gmail.com> > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: 13/06/2016 05:30 pm > Subject: Re: [openstack-dev]

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

ailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 13/06/2016 05:30 pm Subject: Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice +1 On Fri, Jun 10, 2016 at 5:32 PM, Shuu Mutou <shu-m

<    1   2   3   4   5   6   7   8   9   10   >