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

Hi, Spyros I updated ironic heat template, and succeeded booting k8s bay with Ironic. Could you test it? Unfortunately there are some problem and requirement to test. I describe below. * subnet which belongs to private network should be set up with dns_nameservers like following. $ neutron

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

[mailto:strig...@gmail.com] Sent: June-13-16 3:59 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit Hi Gary. On 13 June 2016 at 09:06, Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) <li-gong.d...@hpe.com<mai

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

+1 On Fri, Jun 10, 2016 at 5:32 PM, Shuu Mutou wrote: > Hi team, > > I propose the following changes to the magnum-ui core group. > > + Thai Tran > http://stackalytics.com/report/contribution/magnum-ui/90 > I'm so happy to propose Thai as a core reviewer. > His

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

> > Regards, > Gary Duan > > > -Original Message- > From: Cammann, Tom > Sent: Tuesday, May 03, 2016 1:12 AM > To: OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [

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

-- From: Cammann, Tom Sent: Tuesday, May 03, 2016 1:12 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit Thanks for the write up Hongbin and thanks to all those who contrib

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

nstack-dev@lists.openstack.org >> Cc: Haruhiko Katou >> Subject: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, >> and removal notice >> >> Hi team, >> >> I propose the following changes to the magnum-ui core group. >> >> +

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

+1 > -Original Message- > From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] > Sent: June-10-16 5:33 AM > To: openstack-dev@lists.openstack.org > Cc: Haruhiko Katou > Subject: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, > and removal notice > &

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

Hi team, I propose the following changes to the magnum-ui core group. + Thai Tran http://stackalytics.com/report/contribution/magnum-ui/90 I'm so happy to propose Thai as a core reviewer. His reviews have been extremely valuable for us. And he is active Horizon core member. I believe

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

Rackspace is willing to host in Austin, TX or San Antonio, TX, or San Francisco, CA. -- Adrian On Jun 7, 2016, at 1:35 PM, Hongbin Lu > wrote: Hi all, Please find the Doodle pool below for selecting the Magnum midcycle date. Presumably, it

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

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 remote conferencing using Vidyo at CERN. While it is not the same as an F2F experience, it would

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 Hi Hongbin. CERN's location: https://goo.gl/maps/DWbDVjn

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

---Original Message- > > From: Ricardo Rocha [mailto:rocha.po...@gmail.com] > > Sent: June-08-16 5:43 AM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle > > > > Hi Hongbin. &

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

gt; Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle > > Hi Hongbin. > > Not sure how this fits everyone, but we would be happy to host it at > CERN. How do people feel about it? We can add a nice tour of the place > as a bonus :) > > Let us know. > > Ricardo >

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

rote: > 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)

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

Hi Hongbin. Not sure how this fits everyone, but we would be happy to host it at CERN. How do people feel about it? We can add a nice tour of the place as a bonus :) Let us know. Ricardo On Tue, Jun 7, 2016 at 10:32 PM, Hongbin Lu wrote: > Hi all, > > > > Please find

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

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][heat] spawn a

[openstack-dev] [Magnum] The Magnum Midcycle

Hi all, Please find the Doodle pool below for selecting the Magnum midcycle date. Presumably, it will be a 2 days event. The location is undecided for now. The previous midcycles were hosted in bay area so I guess we will stay there at this time. http://doodle.com/poll/5tbcyc37yb7ckiec In

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

_ > From: Adrian Otto [adrian.o...@rackspace.com] > Sent: Thursday, June 02, 2016 4:24 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually managing > the bay nod

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

On Tue, May 24, 2016 at 1:23 PM, Gal Sagie wrote: > Hi Hongbin, > > Thank you for starting this thread. > The person that is going to work on this integration is Fawad (CC'ed) and > hopefully others will help > him (We have another person from Huawei that showed intrest in

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

From: Adrian Otto [adrian.o...@rackspace.com] > Sent: Thursday, June 02, 2016 4:24 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually > managing the bay nodes > > I am really struggling to a

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

> -Original Message- > From: Adrian Otto [mailto:adrian.o...@rackspace.com] > Sent: June-02-16 7:24 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually > managing the bay nodes > > I am rea

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

Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes I am really struggling to accept the idea of heterogeneous clusters. My experience causes me to question whether a heterogeneus cluster makes sense for Magnum. I

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

in > >> -Original Message- >> From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com] >> Sent: June-02-16 12:24 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually >>

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

nk of an > alternative solution. > > Therefore, I vote to support the proposed idea. > > Best regards, > Hongbin > >> -Original Message- >> From: Hongbin Lu >> Sent: June-01-16 11:44 AM >> To: OpenStack Development Mailing List (not for usage

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

Brandon, Magnum uses neutron’s LBaaS service to allow for multi-master bays. We can balance connections between multiple kubernetes masters, for example. It’s not needed for single master bays, which are much more common. We have a blueprint that is in design stage for de-coupling magnum from

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

Call me ignorance, but I'm surprised at neutron-lbaas being a dependency of magnum. Why is this? Sorry if it has been asked before and I've just missed that answer? Thanks, Brandon On Wed, 2016-06-01 at 14:39 +, Hongbin Lu wrote: > Hi lbaas team, > > > > I wonder if there is an

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

totally fine with that). > >Best regards, >Hongbin > >> -Original Message- >> From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com] >> Sent: June-02-16 12:24 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: R

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

Message- > > From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com] > > Sent: June-02-16 12:24 AM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually > > managing the bay node

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

ng List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually > managing the bay nodes > > Hi Hongbin, > > I also liked the idea of having heterogeneous set of nodes but IMO such > features should not be implemented in Magnum, thus deviati

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

-Original Message- From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Thursday, June 2, 2016 3:33 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually managing th

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

; From: Hongbin Lu > Sent: June-01-16 11:44 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: RE: [openstack-dev] [magnum] Discuss the idea of manually > managing the bay nodes > > Hi team, > > A blueprint was created for tracking this idea: >

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

gt; Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually > managing the bay nodes > > The discussion at the summit was very positive around this requirement > but as this change will make a large impact to Magnum it will need a > spec. > > On the API of things, I

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

Hi. I have added https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun Regards, Spyros On 1 June 2016 at 16:39, Hongbin Lu wrote: > Hi lbaas team, > > > > I wonder if there is an operator-facing installation guide for > neutron-lbaas. I asked that because Magnum is

[openstack-dev] [magnum][lbaas] Operator-facing installation guide

Hi lbaas team, I wonder if there is an operator-facing installation guide for neutron-lbaas. I asked that because Magnum is working on an installation guide [1] and neutron-lbaas is a dependency of Magnum. We want to link to an official lbaas guide so that our users will have a completed

Re: [openstack-dev] [Magnum][Octavia] Need help for LBaaS v2

Hi Wanghua, I think that you have a networking issue within your setup - Octavia service is unable to connect to the running Amphora. If this is the case - you will have to debug your setup as this is a connectivity issue and not a software problem. On May 24, 2016, at 05:45, 王华

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

Hi, Spyros I fixed a conflicts and upload following patch. * https://review.openstack.org/#/c/320968/ But it isn’t tested yet, maybe it doesn’t work.. If you have a question, please feel free to ask. Thanks -yuanying 2016年5月25日(水) 17:56 Spyros Trigazis : > Hi Yuanying,

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

Hi Yuanying, please upload your workaround. I can test it and try to fix the conflicts. Even if it conflicts we can have some iterations on it. I'll upload later what worked for me on devstack. Thanks, Spyros On 25 May 2016 at 05:13, Yuanying OTSUKA wrote: > Hi,

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

Hi, Hongbin, Spyros. I’m also interesting this work. I have workaround patch to support ironic. (but currently conflict with master. Is it helpful to upload it for initial step of the implementation? Thanks -yuanying 2016年5月25日(水) 6:52 Hongbin Lu : > Hi all, > > > > One

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

Berezovsky; Mohammad Banikazemi Subject: Re: [openstack-dev] [magnum][kuryr] Nested containers networking Hi Hongbin, Thank you for starting this thread. The person that is going to work on this integration is Fawad (CC'ed) and hopefully others will help him (We have another person from Huawei

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

Hi all, One of the most important feature that Magnum team wants to deliver in Newton is the full baremetal support. There is a blueprint [1] created for that and the blueprint was marked as "essential" (that is the highest priority). Spyros is the owner of the blueprint and he is looking for

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

Hi Hongbin, Thank you for starting this thread. The person that is going to work on this integration is Fawad (CC'ed) and hopefully others will help him (We have another person from Huawei that showed intrest in working on this). I think Fawad, given that he is the primary person working on this

Re: [openstack-dev] [Magnum][Octavia] Need help for LBaaS v2

Hi Michael, Thank you for your help. Do you need any other logs to debug this problem? Regards, Wanghua On Tue, May 24, 2016 at 12:31 AM, Michael Johnson wrote: > Hi Wanghua, > > From the o-cw log, it looks like the amphora service VM did not boot > properly or the

Re: [openstack-dev] [Magnum][Octavia] Need help for LBaaS v2

Hi Wanghua, From the o-cw log, it looks like the amphora service VM did not boot properly or the network is not configured correctly. We can see that Nova said the VM went active, but the amphora-agent inside the image never became reachable. I would check the nova instance console log to make

[openstack-dev] [magnum][kuryr] Nested containers networking

Hi Kuryr team, I want to start this ML to sync up the latest status of the nested container networking implementation. Could I know who is implementing this feature in Kuryr side and how Magnum team could help in this efforts? In addition, I wonder if it makes sense to establish cross-project

[openstack-dev] [magnum] FW: Mentors needed in specific technical areas

FYI, If you interest to be a mentor for containers or other areas, check below... Best regards, Hongbin From: Emily K Hugenbruch [mailto:ekhugenbr...@us.ibm.com] Sent: May-23-16 10:25 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [PTLs][all][mentoring] Mentors needed in

[openstack-dev] [Magnum][Octavia] Need help for LBaaS v2

Hi all, Previously Magnum used LBaaS v1. Now LBaaS v1 is deprecated, so we want to replace it by LBaaS v2. But I met a problem in my patch https://review.openstack.org/#/c/314060/. I could not figure out why it didn't work. It seems there are some errors in

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

ons) Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes I would vote for the OSC pattern to make it easier for the users, since we already expect that migration path. Also agree with Tom that this is a significant change so we should write a spec to think thro

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

t;OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 05/16/2016 11:24 AM Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes > On May 16, 2016, at 7:59 AM,

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

: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes The discussion at the summit was very positive around this requirement but as this change will make a large impact to Magnum it will need a spec. On the API of things, I was thinking a slightly more generic approach

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

Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes Hi all, This is a continued discussion from the design summit. For recap, Magnum manages bay nodes by using ResourceGroup from Heat. This approach works

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

..@oeilvert.org> >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" >> <openstack-dev@lists.openstack.org> >> Date: Monday, 16 May 2016 at 01:07 >> To: "OpenStack Development Mailing List (not for usage questions)" >>

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

>Tom > >From: Yuanying OTSUKA <yuany...@oeilvert.org> >Reply-To: "OpenStack Development Mailing List (not for usage questions)" ><openstack-dev@lists.openstack.org> >Date: Monday, 16 May 2016 at 01:07 >To: "OpenStack Development Mailing List (

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

hi Tom I like your idea on define a generic approach of bay life cycle operations. Seems current propose is to allow user dynamically adding/deleting nodes from a created bay, what if the master/node flavor in baymodel(bay's flavor) ? if a user add a new node with flavor which is not defined

Re: [openstack-dev] [magnum] How to document 'labels'

Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [magnum] How to document 'labels' > > Shu, > > You mentioned that Swagger was promoted by the API-WG. I wonder if they > mention how to use it.

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

ailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Monday, 16 May 2016 at 01:07 To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Discuss the idea of manually

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

On Sun, May 15, 2016 at 10:49:39PM +, Hongbin Lu wrote: > Hi all, > > This is a continued discussion from the design summit. For recap, Magnum > manages bay nodes by using ResourceGroup from Heat. This approach works but > it is infeasible to manage the heterogeneity across bay nodes, which

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

Hi, I think, user also want to specify the deleting node. So we should manage “node” individually. For example: $ magnum node-create —bay … $ magnum node-list —bay $ magnum node-delete $NODE_UUID Anyway, if magnum want to manage a lifecycle of container infrastructure. This feature is

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

Hi all, This is a continued discussion from the design summit. For recap, Magnum manages bay nodes by using ResourceGroup from Heat. This approach works but it is infeasible to manage the heterogeneity across bay nodes, which is a frequently demanded feature. As an example, there is a request

Re: [openstack-dev] [magnum] How to document 'labels'

bility should discourage us from exposing information to the u > > From: Jamie Hannaford <jamie.hannaf...@rackspace.com> > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Cc: Qun XK Wang <bjw...@cn.ib

Re: [openstack-dev] [magnum] How to document 'labels'

st (not for usage questions) > > <openstack-dev@lists.openstack.org> > > Cc: Qun XK Wang <bjw...@cn.ibm.com> > > Subject: Re: [openstack-dev] [magnum] How to document 'labels' > > > > I would like to add some context for a bigger picture so we might arriv

Re: [openstack-dev] [magnum] Jinja2 for Heat template

Sounds good to me. Best regards, Hongbin From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: May-12-16 9:12 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat template Hi, My concern is that using option 1

Re: [openstack-dev] [magnum] How to document 'labels'

Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Cc: Qun XK Wang <bjw...@cn.ibm.com> > Subject: Re: [openstack-dev] [magnum] How to document 'labels' > > I would like to add some context for a bigger picture so we might arrive > at a more

Re: [openstack-dev] [magnum][higgins][all] The first Higgins team meeting

penstack.org/wiki/Higgins#Agenda_for_2016-05-13_0300_UTC >> >> >> >> Best regards, >> >> Hongbin >> >> >> >> From: Hongbin Lu >> Sent: May-03-16 11:31 AM >> To: OpenStack Development Mailing List (not for usage questions) >>

Re: [openstack-dev] [magnum][higgins][all] The first Higgins team meeting

TC > > > > Best regards, > > Hongbin > > > > *From:* Hongbin Lu > *Sent:* May-03-16 11:31 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* RE: [openstack-dev] [magnum][all] Build unified abstraction > for all COEs > >

Re: [openstack-dev] [magnum] Jinja2 for Heat template

est regards, > > Hongbin > > > > *From:* Yuanying OTSUKA [mailto:yuany...@oeilvert.org > <yuany...@oeilvert.org>] > *Sent:* May-12-16 6:02 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [magnum] Jinja2 for

Re: [openstack-dev] [magnum] How to document 'labels'

om: Jamie Hannaford <jamie.hannaf...@rackspace.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Cc: Qun XK Wang <bjw...@cn.ibm.com> Date: 05/12/2016 07:08 AM Subject:Re: [openstack-dev] [ma

Re: [openstack-dev] [magnum] Jinja2 for Heat template

) Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat template We discussed the management of Heat templates several times. It seems the consensus is to leverage the *conditionals*feature from Heat (option #1). From the past discussion, it sounds like option #2 or #3 will significantly complicate

Re: [openstack-dev] [magnum] How to document 'labels'

/v1/shell.py#L218 [2] https://github.com/openstack/python-novaclient/blob/master/novaclient/v2/shell.py#L526 Tom From: Tim Bell [mailto:tim.b...@cern.ch] Sent: 12 May 2016 17:58 To: OpenStack Development Mailing List (not for usage questions) Cc: Qun XK Wang Subject: Re: [openstack-dev] [magnum

Re: [openstack-dev] [magnum] How to document 'labels'

questions)" <openstack-dev@lists.openstack.org> Cc: Qun XK Wang <bjw...@cn.ibm.com> Subject: Re: [openstack-dev] [magnum] How to document 'labels' +1 for 1 and 3. I'm not sure maintainability should discourage us from exposing information to the user through the client - we'll face the

Re: [openstack-dev] [magnum] Jinja2 for Heat template

if they want to run newer version of Magnum with older version of OpenStack. Thoughts. Best regards, Hongbin From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: May-12-16 6:02 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat

Re: [openstack-dev] [magnum] How to document 'labels'

<hongbin...@huawei.com> Sent: 11 May 2016 21:52 To: OpenStack Development Mailing List (not for usage questions) Cc: Qun XK Wang Subject: [openstack-dev] [magnum] How to document 'labels' Hi all, This is a continued discussion from the last team meeting. For recap, 'labels' is a pr

Re: [openstack-dev] [magnum] How to document 'labels'

/2016 03:53 am Subject: [openstack-dev] [magnum] How to document 'labels' Hi all, This is a continued discussion from the last team meeting. For recap, ‘labels’ is a property in baymodel and is used by users to input additional key-pair pairs to configure the bay. In the last team meet

Re: [openstack-dev] [magnum] Jinja2 for Heat template

Hi, Thanks for your helpful comment. I didn’t know about the pattern you suggested. We often want to “if” or “for” etc… For example, * if private network is supplied as parameter, disable creating network resource. * if https parameter is enable, tcp 6443 port should be opened instead of 8080

Re: [openstack-dev] [magnum] Jinja2 for Heat template

On Thu, May 12, 2016 at 11:08:02AM +0300, Pavlo Shchelokovskyy wrote: >Hi, > >not sure why 3 will bring chaos when implemented properly. I agree - heat is designed with composition in mind, and e.g in TripleO we're making heavy use of it for optional configurations and it works pretty

Re: [openstack-dev] [magnum] Jinja2 for Heat template

Hi, not sure why 3 will bring chaos when implemented properly. Can you abstract the "thing" (sorry, not quite familiar with Magnum) that needs FP + FP itself into a custom resource/nested stack? Then you could use single master template plus two environments (one with FP, one without), and

Re: [openstack-dev] [magnum] How to document 'labels'

, 2016 7:01 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum] How to document 'labels' +1 for #2, to keep help message in magnum API server, since we have an validation list in API Server, see https://review.openstack.org/#/c/312990/5/magnum/api/attr_validator.py@23

[openstack-dev] [magnum] Jinja2 for Heat template

Hi, all. Now, I’m trying to implement following bp. * https://blueprints.launchpad.net/magnum/+spec/bay-with-no-floating-ips This bp requires to disable/enable “floating ip resource” in heat template dynamically. We have 3 options to implement this. 1. Use “conditions function” *

Re: [openstack-dev] [magnum] How to document 'labels'

+1 for #2, to keep help message in magnum API server, since we have an validation list in API Server, see https://review.openstack.org/#/c/312990/5/magnum/api/attr_validator.py@23 . But, if we chose #2 , CLI should add supporting to retrieve help message from API server. On 2016年05月12日

Re: [openstack-dev] [magnum] How to document 'labels'

Hi all, +1 for option #2. Yuanying drafted following blueprint. And I will follow up this. https://blueprints.launchpad.net/magnum/+spec/magnum-api-swagger-support I think, this will be satisfy Tom's comments. regards, Shu Muto

Re: [openstack-dev] [magnum] How to document 'labels'

: Hongbin Lu [hongbin...@huawei.com] Sent: Wednesday, May 11, 2016 12:52 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Qun XK Wang Subject: [openstack-dev] [magnum] How to document 'labels' Hi all, This is a continued discussion from the last team meeting. For recap, ‘labels

[openstack-dev] [magnum] How to document 'labels'

Hi all, This is a continued discussion from the last team meeting. For recap, 'labels' is a property in baymodel and is used by users to input additional key-pair pairs to configure the bay. In the last team meeting, we discussed what is the best way to document 'labels'. In general, I heard

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

he responsibility. > > > > [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation > > > > Best regards, > > Hongbin > > > > *From:* Spyros Trigazis [mailto:strig...@gmail.com] > *Sent:* May-11-16 11:13 AM > *To:* OpenStack Development M

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons Hi, since I work on the install docs (btw, I'll push in our repo in the next hour), I could do it. Spyros On 11 May 2016 at 00:35, Anthony Chow <vcloudernb...@gmail.

[openstack-dev] [magnum][higgins][all] The first Higgins team meeting

Sent: May-03-16 11:31 AM To: OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [magnum][all] Build unified abstraction for all COEs Hi all, According to the decision in the design summit [1], we are going to narrow the scope of the Magnum project [2

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

Hi, since I work on the install docs (btw, I'll push in our repo in the next hour), I could do it. Spyros On 11 May 2016 at 00:35, Anthony Chow wrote: > HongBin, > > What is the skill requirement or credential for this documentation liaison > role? I am interested in

Re: [openstack-dev] [magnum] Need a volunteer for documentation liaisons

HongBin, What is the skill requirement or credential for this documentation liaison role? I am interested in doing this Anthony. On Tue, May 10, 2016 at 3:24 PM, Hongbin Lu wrote: > Hi team, > > We need a volunteer as liaison for documentation team. Just let me know if

[openstack-dev] [magnum] Need a volunteer for documentation liaisons

Hi team, We need a volunteer as liaison for documentation team. Just let me know if you interest in this role. Best regards, Hongbin > -Original Message- > From: Lana Brindley [mailto:openst...@lanabrindley.com] > Sent: May-10-16 5:47 PM > To: OpenStack Development Mailing List;

Re: [openstack-dev] [magnum] Add support for using Keystone in k8s bay

...@huawei.com] Sent: Wednesday, May 04, 2016 8:33 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Add support for using Keystone in k8s bay Hi team, Based on requests, I propose to add support for Keystone authentication for k8s bay. A blueprint

[openstack-dev] [magnum] Add support for using Keystone in k8s bay

Hi team, Based on requests, I propose to add support for Keystone authentication for k8s bay. A blueprint was created for that: https://blueprints.launchpad.net/magnum/+spec/keystone-for-k8s-bay A goal is to enable other OpenStack services to access the APIs of k8s bays. So far, I received a

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

> -Original Message- > From: Ricardo Rocha [mailto:rocha.po...@gmail.com] > Sent: May-03-16 8:34 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit > > Hi. > > On

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

> -Original Message- > From: Cammann, Tom [mailto:tom.camm...@hpe.com] > Sent: May-02-16 1:12 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit > > Thanks for the write

Re: [openstack-dev] [magnum][all] Build unified abstraction for all COEs

: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: April-23-16 11:27 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs Magnum is not a COE installer. It offers multi tenancy from

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

-Original Message- From: Ricardo Rocha [mailto:rocha.po...@gmail.com] Sent: Tuesday, May 03, 2016 8:34 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit Hi. On Mon, May 2, 2016 at 7:11 PM, Cammann

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

ore investigation and isn’t a current > priority. > > Tom > > > From: Hongbin Lu <hongbin...@huawei.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: Saturday, 30 April 2016 at 0

Re: [openstack-dev] [magnum] Proposed Revision to Magnum's Mission

/p/magnum-mission-statement Your comments on the etherpad will be appreciated. Best regards, Hongbin From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: April-29-16 8:47 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [magnum] Proposed Revision to Magnum's Mission Magnum

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

st (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] Notes for Magnum design summit Hi team, For reference, below is a summary of the discussions/decisions in Austin design summit. Please feel free to point out if anything is incorrect or inco

Re: [openstack-dev] [magnum] Proposed Revision to Magnum's Mission

Cool, abandoning mine as it seems the team is working on one anyway. (I just didn't want a mission statement change to wait until some unknown project comes along, someday in the future...) -Josh Davanum Srinivas wrote: Adrian, fyi, there's one more already filed by Josh -

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

Hi team, For reference, below is a summary of the discussions/decisions in Austin design summit. Please feel free to point out if anything is incorrect or incomplete. Thanks. 1. Bay driver: https://etherpad.openstack.org/p/newton-magnum-bay-driver - Refactor existing code into bay drivers -

Re: [openstack-dev] [magnum] Proposed Revision to Magnum's Mission

Adrian, fyi, there's one more already filed by Josh - https://review.openstack.org/#/c/310941/ -- Dims On Fri, Apr 29, 2016 at 7:47 PM, Adrian Otto wrote: > Magnum Team, > > In accordance with our Fishbowl discussion yesterday at the Newton Design > Summit in Austin,

[openstack-dev] [magnum] Proposed Revision to Magnum's Mission

Magnum Team, In accordance with our Fishbowl discussion yesterday at the Newton Design Summit in Austin, I have proposed the following revision to Magnum’s mission statement: https://review.openstack.org/311476 The idea is to narrow the scope of our Magnum project to allow us to focus on

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