Re: [openstack-dev] [Magnum] duplicate scripts in different coes

Sure that is the things I want to cleanup long time before. I listed on https://etherpad.openstack.org/p/magnum-newton-design-summit-topics (item 12) and bug https://bugs.launchpad.net/magnum/+bug/1517218 On 2016年04月19日 10:40, 王华 wrote: Hi all, There are some duplicate scripts in different

Re: [openstack-dev] [Magnum]Cache docker images

@wanghua I think there were some discussion already , check https://blueprints.launchpad.net/magnum/+spec/support-private-registry and https://blueprints.launchpad.net/magnum/+spec/allow-user-softwareconfig On

[openstack-dev] [Magnum]Cache docker images

Hi all, We want to eliminate pulling docker images over the Internet on bay provisioning. There are two problems of this approach: 1. Pulling docker images over the Internet is slow and fragile. 2. Some clouds don't have external Internet access. It is suggested to build all the required images

[openstack-dev] [Magnum] duplicate scripts in different coes

Hi all, There are some duplicate scripts in different coes now, for example scripts for tls and etcd. I think we should put them into a common function module. If there is some minor difference between the scripts in different coes, we can pass different parameters to these scripts. Regards,

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

Puimedon <t...@midokura.com>, Irena Berezovsky <ir...@midokura.com> Date: 19/04/2016 06:50 am Subject:Re: [openstack-dev] [magnum][kuryr] Shared session in design summit Thanks Hongbin, Actually we have a new project called Fuxi that sorta like Kur

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

com] > *Sent:* March-30-16 10:36 AM > *To:* OpenStack Development Mailing List (not for usage questions); > Antoni Segura Puimedon; Fawad Khaliq; Mohammad Banikazemi; Taku Fukushima; > Irena Berezovsky; Mike Spreitzer > *Subject:* Re: [openstack-dev] [magnum][kuryr] Shared session in desig

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

To: OpenStack Development Mailing List (not for usage questions); Antoni Segura Puimedon; Fawad Khaliq; Mohammad Banikazemi; Taku Fukushima; Irena Berezovsky; Mike Spreitzer Subject: Re: [openstack-dev] [magnum][kuryr] Shared session in design summit All these slots are fine with me, added Kuryr team

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Douglas Mendizábal > [1] https://etherpad.openstack.org/p/magnum-barbican-alternative > > Best regards, Hongbin > >> -Original Message- From: Nathan Reller >> [mailto:nathan.s.rel...@gmail.com] Sent: April-14-16 9:22 AM To: >> OpenStack Development Maili

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

[1] https://etherpad.openstack.org/p/magnum-barbican-alternative Best regards, Hongbin > -Original Message- > From: Nathan Reller [mailto:nathan.s.rel...@gmail.com] > Sent: April-14-16 9:22 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstac

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

ring un-encrypted data). Would I >> confirm if Keystone team agrees (or doesn’t disagree) with this >> point of view? >> >> >> >> [1] https://etherpad.openstack.org/p/magnum-barbican-alternative >> >> >> >> Best regards, >> &g

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

point of view? > > > > [1] https://etherpad.openstack.org/p/magnum-barbican-alternative > > > > Best regards, > > Hongbin > > > > *From:*Morgan Fainberg [mailto:morgan.fainb...@gmail.com] *Sent:* > April-13-16 12:08 AM *To:* OpenStack Development Maili

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Excerpts from Clayton O'Neill's message of 2016-04-13 07:37:16 -0700: > On Wed, Apr 13, 2016 at 10:26 AM, rezroo wrote: > > Hi Kevin, > > > > I understand that this is how it is now. My question is how bad would it be > > to wrap the Barbican client library calls in another

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Excerpts from Douglas Mendizábal's message of 2016-04-13 10:01:21 -0700: > Hash: SHA512 > > Hi Reza, > > The Barbican team has already abstracted python-barbicanclient into a > general purpose key-storage library called Castellan [1] > > There are a few OpenStack projects that have planned to

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

: Wednesday, April 13, 2016 7:37 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates On Wed, Apr 13, 2016 at 10:26 AM, rezroo <openst...@roodsari.us> wrote: > Hi Kev

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

On 04/12/2016 03:43 PM, Hongbin Lu wrote: Hi all, In short, some Magnum team members proposed to store TLS certificates in Keystone credential store. As Magnum PTL, I want to get agreements (or non-disagreement) from OpenStack community in general, Keystone community in particular, before

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates > I think we need to ask who we are lowering the barrier of entry for. Are we > going down this path because we want developers to have less th

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

I think we need to ask who we are lowering the barrier of entry for. Are we going down this path because we want developers to have less things to do to stand up a development environment? Or do we want to make it easy for people to realistically test? If you're going to realistically vet magnum,

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates On Tue, Apr 12, 2016 at 8:06 PM, Adrian Otto <adrian.o...@rackspace.com<mailto:adrian.o...@rackspace.com>> wrote: Pleas

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

On Wed, Apr 13, 2016 at 10:26 AM, rezroo wrote: > Hi Kevin, > > I understand that this is how it is now. My question is how bad would it be > to wrap the Barbican client library calls in another class and claim, for > all practical purposes, that Magnum has no direct

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Barbican is the abstraction layer. Its plugable like nova, neutron, cinder, etc. Thanks, Kevin From: rezroo Sent: Tuesday, April 12, 2016 11:00:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3

Re: [openstack-dev] [magnum] Microversions usage

Hi Jamie On 2016年04月13日 17:26, Jamie Hannaford wrote: ​I recently discovered that Magnum supports microversions [1] - but it doesn't seem to be incrementing the API in accordance with new functionality releases. Is this due to the v1 API not being locked yet? What is the status of freezing

[openstack-dev] [magnum] Microversions usage

?I recently discovered that Magnum supports microversions [1] - but it doesn't seem to be incrementing the API in accordance with new functionality releases. Is this due to the v1 API not being locked yet? What is the status of freezing the API, so that we can move to a microversions-based

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

, April 12, 2016 8:06:03 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates Please don't miss the point here. We are seeking a solution that allows a location to plac

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

ha setups and barbican before. Ha is way worse. Thanks, Kevin From: Adrian Otto Sent: Tuesday, April 12, 2016 8:06:03 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

On Tue, Apr 12, 2016 at 8:06 PM, Adrian Otto wrote: > Please don't miss the point here. We are seeking a solution that allows a > location to place a client side encrypted blob of data (A TLS cert) that > multiple magnum-conductor processes on different hosts can reach

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Please don't miss the point here. We are seeking a solution that allows a location to place a client side encrypted blob of data (A TLS cert) that multiple magnum-conductor processes on different hosts can reach over the network. We *already* support using Barbican for this purpose, as well as

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

On Tue, Apr 12, 2016 at 3:27 PM, Lance Bragstad wrote: > Keystone's credential API pre-dates barbican. We started talking about > having the credential API back to barbican after it was a thing. I'm not > sure if any work has been done to move the credential API in this >

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Keystone's credential API pre-dates barbican. We started talking about having the credential API back to barbican after it was a thing. I'm not sure if any work has been done to move the credential API in this direction. From a security perspective, I think it would make sense for keystone to back

[openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Hi all, In short, some Magnum team members proposed to store TLS certificates in Keystone credential store. As Magnum PTL, I want to get agreements (or non-disagreement) from OpenStack community in general, Keystone community in particular, before approving the direction. In details, Magnum

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

gt; Sent: Sunday, April 10, 2016 6:59 PM Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay #2 seems more flexible, and if it be proved it can "make the SAME mesos bay applied with mutilple frameworks." It would be great. Which means, one mesos bay should support m

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

t for usage questions)" <openstack-dev@lists.openstack.org> Date: 12/04/2016 04:36 am Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay +1 for "#1: Mesos and Marathon". Most deployments that I am aware of has this setup. Also we can provi

Re: [openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress

ailto:thie...@openstack.org] >> Sent: April-11-16 5:28 AM >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-dev] [magnum][requirements][release] The >> introduction of package py2-ipaddress >> >> Hongbin Lu wrote: >> > Hi requirements

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

  --- Egor From: Kai Qiang Wu <wk...@cn.ibm.com> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Sent: Sunday, April 10, 2016 6:59 PM Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay #2 seems more flexibl

Re: [openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress

age- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: April-11-16 5:28 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [magnum][requirements][release] The > introduction of package py2-ipaddress > > Hongbin Lu wrote: > > Hi requi

Re: [openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress

Hongbin Lu wrote: Hi requirements team, In short, the recently introduced package py2-ipaddress [1] seems to break Magnum. In details, Magnum gate recently broke by an error: “'\xac\x18\x05\x07' does not appear to be an IPv4 or IPv6 address” [2] (the gate breakage has been temporarily fixed but

[openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress

Hi requirements team, In short, the recently introduced package py2-ipaddress [1] seems to break Magnum. In details, Magnum gate recently broke by an error: "'\xac\x18\x05\x07' does not appear to be an IPv4 or IPv6 address" [2] (the gate breakage has been temporarily fixed but we are looking

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

2016 12:06 am Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay My preference is #1, but I don’t feel strong to exclude #2. I would agree to go with #2 for now and switch back to #1 if there is a demand from users. For Ton’s suggestion to push Marathon into the introd

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

[mailto:t...@us.ibm.com] Sent: April-10-16 11:24 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay I would agree that #2 is the most flexible option, providing a well defined path for additional frameworks

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

PM Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay On Apr 8, 2016, at 3:15 PM, Hongbin Lu <hongbin...@huawei.com> wrote: Hi team, I would like to give an update for this thread. In the last team, we discussed several options to introd

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

o: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay Jay, just keep in mind that Chronos can be run by Marathon. --- Egor From: Jay Lau <jay.lau@gmail.com<mailto:jay

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

prefer? Or you have other suggestions? Advices are welcome. Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: March-28-16 12:19 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay Jay, just

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Thanks Ihar & neutron team for the quick fix. Best regards, Hongbin > -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: April-08-16 7:56 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-de

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

o: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' > object has no attribute 'strftime' > > Hongbin Lu <hongbin...@huawei.com> wrote: > > > Hi all, > > Magnum gate recentl

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com <mailto:ihrac...@redhat.com>] > Sent: April-07-16 12:04 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' &g

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' > > object has no attribute 'strftime' > > > > Hongbin Lu <hongbin...@huawei.com> wrote: > > > > > Hi all, >

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

> -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: April-07-16 12:04 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' > object has no a

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

hi hongbin & team. Thanks for all your supporting, Magnum core team and the community, I am very glad to have this opportunity to join this team. I will try my best to contribute Magnum team and OpenStack community. Thanks Eli. On 2016年04月08日 03:35, Hongbin Lu wrote: Hi all, Thanks for

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team +1 On Sat, Apr 2, 2016 at 7:24 AM, Kai Qiang Wu <wk...@cn.ibm.com<mailto:wk...@cn.ibm.com>> wrote: + 1 for Eli :) Thanks

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Hongbin Lu wrote: Hi all, Magnum gate recently broke with error: “AttributeError: 'str' object has no attribute 'strftime'” (here is a full log [1]). I would like to confirm if there is a recent commit in Neutron that causes the breakage. If yes, a quick fix is

[openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Hi all, Magnum gate recently broke with error: "AttributeError: 'str' object has no attribute 'strftime'" (here is a full log [1]). I would like to confirm if there is a recent commit in Neutron that causes the breakage. If yes, a quick fix is greatly appreciated. [1]

Re: [openstack-dev] [magnum] Containers lifecycle management

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: April-06-16 12:16 PM > To: Hongbin Lu > Cc: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum] Containers lifecycle management > >

Re: [openstack-dev] [magnum] Containers lifecycle management

On 06/04/16 15:54 +, Hongbin Lu wrote: -Original Message- From: Flavio Percoco [mailto:fla...@redhat.com] Sent: April-06-16 9:14 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [magnum] Containers lifecycle management Greetings, I'm fairly new to Magnum and I

Re: [openstack-dev] [magnum] Containers lifecycle management

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: April-06-16 9:14 AM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [magnum] Containers lifecycle management > > > Greetings, > > I'm fairly new to Magnu

[openstack-dev] [magnum] Containers lifecycle management

Greetings, I'm fairly new to Magnum and I hope my comments below are accurate. After reading some docs, links and other references, I seem to understand the Magnum team has a debate on whether providing abstraction for containers lifecycle is something the project should do or not. There's a

[openstack-dev] [magnum] Collaborating topics for Magnum design summit

Hi team, As mentioned in the team meeting, Magnum team is using an etherpad [1] to collaborate topics for design summit. If you interest to join us in the Newton design summit, I would request your inputs in the etherpad. In particular, you can do the followings: * Propose new topics that you

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? A few things: Public IPs and Floating IPs are not the same thing. Some clouds have public IPs. Some have floating ips. Some have both. I think it's important to be able to have

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

...@yahoo.com] Sent: March-31-16 12:42 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Hongbin Lu Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hongbin, It's correct, I was involved in two big OpenStack private cloud deployments and we

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi Egor, I know some people still want to use floating ips to connect nodes, So I will not remove floating ips feature completely. Only introduce the option which

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

> contributed to Magnum for a while. His contribution started f > > From: Hongbin Lu <hongbin...@huawei.com> > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: 01/04/2016 02:20 am > Subject: [ope

Re: [openstack-dev] [magnum] Split k8s-client in separate python package

Thanks Dims. -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: April-02-16 8:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Split k8s-client in separate python package Hongbin, Here's what i came up

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

ailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 01/04/2016 02:20 am Subject: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team Hi all, Eli Qiao has been consistently contributed to Magnum for a while. Hi

Re: [openstack-dev] [magnum] Split k8s-client in separate python package

n > > -Original Message- > From: Davanum Srinivas [mailto:dava...@gmail.com] > Sent: April-01-16 3:36 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [magnum] Split k8s-client in separate python package > > Team, > > I've

Re: [openstack-dev] [magnum] Split k8s-client in separate python package

regards, Hongbin -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: April-01-16 3:36 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Split k8s-client in separate python package Team, I've been meaning to do

[openstack-dev] [magnum] Split k8s-client in separate python package

Team, I've been meaning to do this for a while. Short version, see repo: https://github.com/dims/python-k8sclient/ Long version: - Started from the magnum repo. - pulled out just ./magnum/common/pythonk8sclient - preserved entire history in case we had to go back - reorganized directory

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

age questions)" < > openstack-dev@lists.openstack.org> > Date: Thursday, 31 March 2016 at 19:18 > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [magnum] Proposing Eli

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

t;openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important b

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

and this is very > handy feature. > > --- > Egor > > -- > *From:* 王华 <wanghua.hum...@gmail.com> > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Sent:* Wednesday,

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 from me. Thanks Eli for your contribution. Regards, Madhuri From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: Friday, April 1, 2016 8:13 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

Eli. >> >> >> >> Regards, >> >> Gary Duan >> >> >> >> *From:* Hongbin Lu [mailto:hongbin...@huawei.com] >> *Sent:* Friday, April 01, 2016 2:18 AM >> *To:* OpenStack Development Mailing List (not for usage questions) < >> op

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

gt; *Sent:* Friday, April 01, 2016 2:18 AM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core > reviewer team > > > > Hi all, > > > >

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli. Regards, Gary Duan From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Friday, April 01, 2016 2:18 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core re

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 On Mar 31, 2016, at 11:18 AM, Hongbin Lu > wrote: Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 On Mar 31, 2016, at 11:18 AM, Hongbin Lu > wrote: Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli Ton Ngo, From: Hongbin Lu <hongbin...@huawei.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 03/31/2016 11:21 AM Subject: [openstack-dev] [magnum] Proposing El

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 from me for Eli Thanks, Dims On Thu, Mar 31, 2016 at 2:18 PM, Hongbin Lu wrote: > Hi all, > > > > Eli Qiao has been consistently contributed to Magnum for a while. His > contribution started from about 10 months ago. Along the way, he implemented > several important

[openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and fixed a lot of bugs. His contribution covers various aspects (i.e. APIs, conductor, unit/functional tests,

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Lu <hongbin...@huawei.com> *To:* Guz Egor <guz_e...@yahoo.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> *Sent:* Thursday, March 31, 2016 7:29 AM *Subject:* RE: [openstack-dev] [magnum] Are Floating IPs really needed for a

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

) . --- Egor From: Hongbin Lu <hongbin...@huawei.com> To: Guz Egor <guz_e...@yahoo.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Sent: Thursday, March 31, 2016 7:29 AM Subject: RE: [openstack-dev] [magnum] Are F

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry" Hi. On Wed, Mar 30, 2016 at 4:20 PM, Kai Qiang Wu <wk...@cn.ibm.com<mailto:wk...@cn.ibm.com>> wrote: I agree to that support-private-registry should be secure. As insecure seems not much useful fo

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

don’t have enough public IP addresses. Best regards, Hongbin From: Guz Egor [mailto:guz_e...@yahoo.com] Sent: March-31-16 12:08 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? -1 who is going

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

com> To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Sent: Wednesday, March 30, 2016 8:41 PM Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Hi yuanying, I agree to reduce the usage of

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes? Importance: Low Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hi yuanying, I agree to reduce the usage of floating IP. But as far as I know, if we need to pull docker images from docker hub in nodes floating ips are needed. To reduce the usage of floating ip, we can use proxy. Only some nodes have floating ips, and other nodes can access docker hub by

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hi Yuanying, +1 I think we can add option on whether to using floating ip address since IP address are kinds of resource which not wise to waste. On 2016年03月31日 10:40, 大塚元央 wrote: Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer

[openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hi team, Previously, we had a reason why all nodes should have floating ips [1]. But now we have a LoadBalancer features for masters [2] and minions [3]. And also minions do not necessarily need to have floating ips [4]. I think it’s the time to remove floating ips from all nodes. I know we are

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

stack.org> Date: 30/03/2016 09:09 pm Subject: Re: [openstack-dev] [magnum] Discuss the blueprint "support-private-registry" Hi. On Wed, Mar 30, 2016 at 3:59 AM, Eli Qiao <liyong.q...@intel.com> wrot

Re: [openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

<openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [magnum][magnum-ui] Have magnum jobs respect > upper-constraints.txt > > Hi team, > > After a quick check, it seems python-magnumclient and magnum-ui don't use > upper constraints. Magnum (the main repo) uses upper constrain

Re: [openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

On 03/30/2016 05:31 PM, Hongbin Lu wrote: > Hi team, > > After a quick check, it seems python-magnumclient and magnum-ui don't use > upper constraints. Magnum (the main repo) uses upper constraints in > integration tests (gate-functional-*), but doesn't use it in others (e.g. > py27, py34,

[openstack-dev] [magnum][magnum-ui] Have magnum jobs respect upper-constraints.txt

Hi team, After a quick check, it seems python-magnumclient and magnum-ui don't use upper constraints. Magnum (the main repo) uses upper constraints in integration tests (gate-functional-*), but doesn't use it in others (e.g. py27, py34, pep8, docs, coverage). The missing of upper constraints

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

. Best regards, Hongbin From: Ton Ngo [mailto:t...@us.ibm.com] Sent: March-29-16 4:54 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder In multiple occasions in the past, we have had to use

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

l Sagie [mailto:gal.sa...@gmail.com] > *Sent:* March-30-16 2:00 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [magnum][kuryr] Shared session in design > summit > > > > Anything you pick is fine with me, Kuryr fishbowl sessio

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

heart. You are miracle! From: Ricardo Rocha <rocha.po...@gmail.com> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: 30/03/2016 09:09 pm Subject: Re: [openstack-dev] [magnum] Discuss the

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

...@gmail.com] Sent: March-30-16 2:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum][kuryr] Shared session in design summit Anything you pick is fine with me, Kuryr fishbowl session is on Thursday 4:10 - 4:50, i personally think the Magnum

Re: [openstack-dev] [magnum] Discuss the blueprint "support-private-registry"

Hi. On Wed, Mar 30, 2016 at 3:59 AM, Eli Qiao wrote: > > Hi Hongbin > > Thanks for starting this thread, > > > > I initial propose this bp because I am in China which is behind China great > wall and can not have access of gcr.io directly, after checking our > cloud-init

Re: [openstack-dev] [magnum][kuryr] Shared session in design summit

Anything you pick is fine with me, Kuryr fishbowl session is on Thursday 4:10 - 4:50, i personally think the Magnum integration is important enough and i dont mind using this time for the session as well. Either way i am also ok with the 11-11:40 and the 11:50-12:30 sessions or the 3:10-3:50 On

Re: [openstack-dev] [magnum] Discuss the blueprint "support-private-registry"

Hi Hongbin Thanks for starting this thread, I initial propose this bp because I am in China which is behind China great wall and can not have access of gcr.io directly, after checking our cloud-init script, I see that lots of code are *hard coded* to using gcr.io, I personally though this

[openstack-dev] [magnum] Discuss the blueprint "support-private-registry"

Hi team, This is the item we didn't have time to discuss in our team meeting, so I started the discussion in here. Here is the blueprint: https://blueprints.launchpad.net/magnum/+spec/support-private-registry . Per my understanding, the goal of the BP is to allow users to specify the url of

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

with development, and gate tests if it makes sense. Ton Ngo, From: Yolanda Robla Mota <yolanda.robla-m...@hpe.com> To: <openstack-dev@lists.openstack.org> Date: 03/29/2016 01:35 PM Subject: Re: [openstack-dev] [magnum] Generate atomic images using diski

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

So the advantages I can see with diskimage-builder are: - we reuse the same tooling that is present in other openstack projects to generate images, rather than relying on an external image - it improves the control we have on the contents of the image, instead of seeing that as a black box. At

[openstack-dev] [magnum][kuryr] Shared session in design summit

Hi all, As discussed before, our team members want to establish a shared session between Magnum and Kuryr. We expected a lot of attendees in the session so we need a large room (fishbowl). Currently, Kuryr has only 1 fishbowl session, and they possibly need it for other purposes. A solution is

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