Re: [openstack-dev] [neutron] PTL candidacy for Rocky

ng List <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [neutron] PTL candidacy for Rocky Hello OpenStack Community, I write this to submit my candidacy for the Neutron PTL position during the Rocky cycle. I had the privilege of being the project's PTL for most of the Queens release ser

[openstack-dev] [neutron] PTL candidacy for Rocky

Hello OpenStack Community, I write this to submit my candidacy for the Neutron PTL position during the Rocky cycle. I had the privilege of being the project's PTL for most of the Queens release series and want to have another opportunity helping the team and the community to deliver more and

Re: [openstack-dev] [neutron] PTL candidacy

>There is no such thing as arbitrary API. It is like one person's treasure is other person's trash no body loves to create arbitrary APIs - there are genuine needs. Arbitrary in the sense that new APIs can be developed on-demand to solve one specific use case that leads to fragmentation and

Re: [openstack-dev] [Neutron] PTL Candidacy

I think we may also want to bring this up in a cross-project session at the PTG. We are definitely to blame for some of the instability, but towards the end of this cycle I have noticed lots of issues with HTTPS connection errors, etc that don't seem to be related to Neutron at all. The squad team

Re: [openstack-dev] [neutron] PTL candidacy

On 25 January 2017 at 14:17, Monty Taylor wrote: > > Adding an additional networking project to try to solve this will only > > make things work. We need one API. If it needs to grow features, it > > needs to grow features - but they should be features that all of > >

Re: [openstack-dev] [neutron] PTL candidacy

On 01/25/2017 08:16 AM, Monty Taylor wrote: > On 01/24/2017 06:42 PM, Sukhdev Kapur wrote: >> >> Ihar and Kevin, >> >> As our potential future PTLs, I would like to draw your attention to one >> of the critical issue regarding Neutron as "the" networking service in >> OpenStack. >> >> I keep

Re: [openstack-dev] [neutron] PTL candidacy

On Tue, Jan 24, 2017 at 5:04 PM, Kevin Benton wrote: > >I would really like us to discuss this issue head-on and see what is > missing in Neutron APIs and what would take to make them extensible so that > vendors do not run around trying to figure out alternative solutions

Re: [openstack-dev] [Neutron] PTL Candidacy

On Tue, Jan 24, 2017 at 12:26 PM, Morales, Victor wrote: > Given the latest issues related with the memory consumption[1] in CI jobs, > I’m just wondering if you have a plan to deal and/or improve it in Neutron. AFAIU the root cause is still not clear, and we don't

Re: [openstack-dev] [neutron] PTL candidacy

Folks, This thread has gotten too long and hard to follow. It is clear that we should discuss/address this. My suggestion is that we organize a session in Atlanta PTG meeting and discuss this. I am going to add this on the Neutron etherpad - should this be included in any other session as well?

Re: [openstack-dev] [neutron] PTL candidacy

On Wed, Jan 25, 2017 at 7:45 AM, Kevin Benton wrote: > LBaaS is a little special since Octavia will have it's own API endpoint > completely that they will evolve on their own. The other spun-out projects > (e.g. VPNaaS) will have the API defined in neutron-lib[1]. In a way,

Re: [openstack-dev] [neutron] PTL candidacy

Folks, this is a great discussion. I hope this leads us to some good consensus and direction :-) I would suggest that we discuss this in upcoming PTG meeting as well. On Wed, Jan 25, 2017 at 5:20 AM, Kevin Benton wrote: > >So I'm not sure that Kevin and Thierry's answers

Re: [openstack-dev] [neutron] PTL candidacy

Catching up on the thread, lots of good thoughts. I don't think there is disagreement here around how Networking API should evolve in terms of vendor extensions. As Kevin suggested, we don't want to advertise API extensibility without Neutron team supervision. One of the reasons behind current

Re: [openstack-dev] [neutron] PTL candidacy

LBaaS is a little special since Octavia will have it's own API endpoint completely that they will evolve on their own. The other spun-out projects (e.g. VPNaaS) will have the API defined in neutron-lib[1]. The specific DVR issue you are referring to with roaming IPs being the target of floating

Re: [openstack-dev] [neutron] PTL candidacy

On 25/01/2017 01:08, Kevin Benton wrote: >>I would really like us to discuss this issue head-on and see what is > missing in Neutron APIs and what would take to make them extensible so > that vendors do not run around trying to figure out alternative > solutions > > The Neutron API is already

Re: [openstack-dev] [neutron] PTL candidacy

On 01/24/2017 06:42 PM, Sukhdev Kapur wrote: > > Ihar and Kevin, > > As our potential future PTLs, I would like to draw your attention to one > of the critical issue regarding Neutron as "the" networking service in > OpenStack. > > I keep hearing off and on that Neutron is not flexible to

Re: [openstack-dev] [neutron] PTL candidacy

On 01/24/2017 08:04 PM, Kevin Benton wrote: >>I would really like us to discuss this issue head-on and see what is > missing in Neutron APIs and what would take to make them extensible so > that vendors do not run around trying to figure out alternative > solutions > > The Neutron API is

Re: [openstack-dev] [neutron] PTL candidacy

>So I'm not sure that Kevin and Thierry's answers address Sukhdev's point. I stated that I am happy to develop new APIs in Neutron. "So I'm all for developing new APIs *as a community*"... The important distinction I am making is that we can make new APIs (and we do with routed networks as you

Re: [openstack-dev] [neutron] PTL candidacy

On Wed, Jan 25, 2017 at 10:20 AM Thierry Carrez wrote: > Kevin Benton wrote: > > [...] > > The Neutron API is already very extensible and that's problematic. Right > > now a vendor can write an out-of-tree service plugin or driver that adds > > arbitrary fields and

Re: [openstack-dev] [neutron] PTL candidacy

Kevin Benton wrote: > [...] > The Neutron API is already very extensible and that's problematic. Right > now a vendor can write an out-of-tree service plugin or driver that adds > arbitrary fields and endpoints to the API that results in whatever > behavior they want. This is great for vendors

Re: [openstack-dev] [neutron] PTL candidacy

>I would really like us to discuss this issue head-on and see what is missing in Neutron APIs and what would take to make them extensible so that vendors do not run around trying to figure out alternative solutions The Neutron API is already very extensible and that's problematic. Right now a

Re: [openstack-dev] [neutron] PTL candidacy

On 01/24/2017 06:42 PM, Sukhdev Kapur wrote: Ihar and Kevin, As our potential future PTLs, I would like to draw your attention to one of the critical issue regarding Neutron as "the" networking service in OpenStack. I keep hearing off and on that Neutron is not flexible to address many

Re: [openstack-dev] [Neutron] PTL Candidacy

<sukhdevka...@gmail.com> > *Reply-To: *"OpenStack Development Mailing List (not for usage > questions)" <openstack-dev@lists.openstack.org> > *Date: *Tuesday, January 24, 2017 at 3:14 PM > *To: *"OpenStack Development Mailing List (not for usage questions)" <

Re: [openstack-dev] [Neutron] PTL Candidacy

I remember good old days when CI was introduced in Neutron (during Icehouse time frame). There was excellent momentum behind it. We did not know some of the enforcement details, which created lots of confusion/havoc. Now that we have a better understanding of the past issues, and lots of good

Re: [openstack-dev] [neutron] PTL candidacy

Ihar and Kevin, As our potential future PTLs, I would like to draw your attention to one of the critical issue regarding Neutron as "the" networking service in OpenStack. I keep hearing off and on that Neutron is not flexible to address many networking use cases and hence a new (or additional)

Re: [openstack-dev] [Neutron] PTL Candidacy

3:14 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Neutron] PTL Candidacy I remember good old days when CI was introduced in Neutron (during Icehouse time frame). There was excellent mo

Re: [openstack-dev] [neutron] PTL Candidacy

In deed, excellent and well qualified candidates. Best of Luck to both -Sukhdev On Tue, Jan 24, 2017 at 7:16 AM, Armando M. wrote: > Hi neutrinos, > > No, it's not what you might be thinking...I am just delighted to see two > excellent candidates willing to take the

Re: [openstack-dev] [Neutron] PTL Candidacy

On 2017-01-24 13:10:26 -0800 (-0800), Ihar Hrachyshka wrote: > On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley wrote: [...] > > I guess the question I have is who, then, can tell our > > operators/users what Neutron drivers are reasonably supported? It > > sounds like you're

Re: [openstack-dev] [Neutron] PTL Candidacy

On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley wrote: > On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: >> On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: >> > I'm on board with getting visibility into the drivers with improvements to >>

Re: [openstack-dev] [Neutron] PTL Candidacy

On 24 January 2017 at 12:46, Jeremy Stanley wrote: > On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: > > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > > > I'm on board with getting visibility into the drivers with > improvements to > >

Re: [openstack-dev] [Neutron] PTL Candidacy

On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > > I'm on board with getting visibility into the drivers with improvements to > > driverlog, etc. What I'm uncertain of is providing much in the lines of > >

Re: [openstack-dev] [Neutron] PTL Candidacy

Definitely, both are great candidates and my best wishes to both during this process. Given the latest issues related with the memory consumption[1] in CI jobs, I’m just wondering if you have a plan to deal and/or improve it in Neutron. Regards, Victor Morales irc: electrocucaracha [1]

Re: [openstack-dev] [Neutron] PTL Candidacy

On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > I'm on board with getting visibility into the drivers with improvements to > driverlog, etc. What I'm uncertain of is providing much in the lines of > 'validation'. Core reviewers don't frequently have access to the

[openstack-dev] [neutron] PTL Candidacy

Hi neutrinos, No, it's not what you might be thinking...I am just delighted to see two excellent candidates willing to take the reins of the project going forward [1,2]. I couldn't hope for more enthusiasm; best of luck to both candidates and anyone else who is going to step up! This is

Re: [openstack-dev] [Neutron] PTL Candidacy

I'm on board with getting visibility into the drivers with improvements to driverlog, etc. What I'm uncertain of is providing much in the lines of 'validation'. Core reviewers don't frequently have access to the hardware or software required to validate these drivers so we can't be sure if the

[openstack-dev] [neutron] PTL candidacy

Hi team, I would like to propose my PTL candidacy for Pike. Some of you already know me. If not, here is my brief OpenStack bio. I joined the community back in Havana, and managed to stick around till now. During the time, I fit several project roles like serving as a Neutron liaison of

Re: [openstack-dev] [Neutron] PTL Candidacy

On 18:35 Jan 22, Kevin Benton wrote: > I would like to propose my candidacy for the Neutron PTL. > > I have been contributing to Neutron since the Havana development > cycle working for a network vendor and then a distribution vendor. > I have been a core reviewer since the Kilo development cycle

Re: [openstack-dev] [Neutron] PTL Candidacy

On 01/22/2017 09:35 PM, Kevin Benton wrote: I would like to propose my candidacy for the Neutron PTL. I have been contributing to Neutron since the Havana development cycle working for a network vendor and then a distribution vendor. I have been a core reviewer since the Kilo development cycle

[openstack-dev] [Neutron] PTL Candidacy

I would like to propose my candidacy for the Neutron PTL. I have been contributing to Neutron since the Havana development cycle working for a network vendor and then a distribution vendor. I have been a core reviewer since the Kilo development cycle and I am on the Neutron stable maintenance

[openstack-dev] [neutron] PTL Candidacy

Hi, I saw that Armando has put himself up for reelection. I would like to endorse him and vote a big +1 for him doing the job in the next cycle. One of the hard things about working in this environment is that it is very hard to get any feedback. I think that over the last cycle you have grown

[openstack-dev] [Neutron] PTL Candidacy

I would like to propose my candidacy for the Neutron PTL. I have been the Neutron PTL for the Mitaka release, and I would like to continue the journey on which I have embarked upon a little over six months ago. Back then, I had a number of objectives which I wanted to achieve with the help of

[openstack-dev] [Neutron] PTL Candidacy

I would like to propose my candidacy for the Neutron PTL. If you are reading this and you know me, then you probably know what I have been up to up until now, what I have done for the project, and what I may continue to do. If you do not know me, and you are still interested in reading, then I

[openstack-dev] [Neutron] PTL Candidacy

Hi everyone, I decided to run for the Neutron PTL position for the Mitaka release cycle. I have been contributing to Neutron since Havana and I am a member of the control plane core review team. During these years I have touched most parts of the Neutron code and in the last cycle my main focus

Re: [openstack-dev] [neutron] PTL Candidacy

confirmed On 04/02/2015 10:16 AM, Kyle Mestery wrote: Hi everyone: I'd like to announce my candidacy for another term as the Neutron PTL. I'm the current Neutron PTL, having been the Neutron PTL for the past two cycles (Juno and Kilo). I'd like a chance to lead the Neutron team for another

[openstack-dev] [neutron] PTL Candidacy

Hi everyone: I'd like to announce my candidacy for another term as the Neutron PTL. I'm the current Neutron PTL, having been the Neutron PTL for the past two cycles (Juno and Kilo). I'd like a chance to lead the Neutron team for another cycle of development. During the Kilo cycle, we worked hard

Re: [openstack-dev] [Neutron] PTL Candidacy

confirmed On 03/31/2014 01:04 PM, Kyle Mestery wrote: Hi everyone, I have decided to run for the OpenStack Networking (Neutron) PTL position. Why I Want To Be Neutron PTL - I want to be Neutron PTL because I wish to continue pushing Neutron forward and help it evolve, and have the

Re: [openstack-dev] [Neutron] PTL Candidacy

Thanks anh. Lúc chiều e cũng bookmark bài này rồi. E phải xem kỹ phần kiến trúc trong neutron, phần network này vẫn chưa thông lắm anh ạ. P/s: Anh gửi tài liệu OVS cho e và Long nhé. On 1 Apr 2014 00:04, Kyle Mestery mest...@noironetworks.com wrote: Hi everyone, I have decided to run for the

[openstack-dev] [Neutron] PTL Candidacy

All- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL and would like to continue leading our team during the Juno cycle. As PTL, I have worked to promote a vibrant open ecosystem of deployers, integrators and vendors within Neutron.

Re: [openstack-dev] [Neutron] PTL Candidacy

confirmed On 03/31/2014 04:15 PM, Mark McClain wrote: All- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL and would like to continue leading our team during the Juno cycle. As PTL, I have worked to promote a vibrant open

Re: [openstack-dev] [Neutron] PTL Candidacy

20, 2013 11:44 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [Neutron] PTL Candidacy Hi- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL. Our team continued to grow during the Havana cycle and both existing

[openstack-dev] [Neutron] PTL Candidacy

Hi- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL. Our team continued to grow during the Havana cycle and both existing and new contributors worked to deliver double the number of blueprints than the previous release. Our vibrant

Re: [openstack-dev] [Neutron] PTL Candidacy

+1 Mark has done a phenomenal job as Neutron PTL On Fri, Sep 20, 2013 at 1:44 PM, Mark McClain mark.mccl...@dreamhost.comwrote: Hi- I writing to announce my candidacy for the OpenStack Networking (Neutron) PTL. I am the current Neutron PTL. Our team continued to grow during the Havana

Re: [openstack-dev] [Neutron] PTL Candidacy

@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Date: Fri, 20 Sep 2013 18:03:44 -0700 To: OpenStack Development Mailing List openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] PTL Candidacy +1 Mark has done a phenomenal job as Neutron PTL On Fri, Sep