+1, even if my vote doesn’t count.
From: Miguel Lavalle
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, February 5, 2018 at 11:21 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [neutron] PTL candidacy for Rocky
Hello
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 bette
>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 in
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
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
> > OpenStack users get.
>
> WOR
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 hear
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
>
> The Neutron API
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 know if it's
Neutron or job se
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?
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, VPNaaS is also special
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 address Sukhdev's point
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 ap
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 IP
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 v
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 addr
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 alrea
>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 me
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 endpoints to the API that resul
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 beca
>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
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
networki
lopment Mailing List (not for usage
> questions)"
> *Date: *Tuesday, January 24, 2017 at 3:14 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [Neutron] PTL Candi
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 idea
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) ne
ons)"
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 momentum behind it. We did not know some of
the enforcement details, which created lots of confusion/havoc.
Now t
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 reins of the project g
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 saying Neutron develo
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
>> > driverlog, etc. What I'm uncertain o
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
> > > driverlog, etc. What I'm uncertain
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
> > 'validation'. Core rev
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] htt
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 hardware or
> software req
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 exciting!
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
feat
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 different
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
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 a
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 team
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 a
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 the
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 wil
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 h
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
> an
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
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
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. O
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" wrote:
> Hi everyone,
>
> I have decided to run for the OpenStack Networking
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 hav
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 skills necessary to do it. I've worked in Open
Source for many ye
37839 wrote:
_+1 for Mark McClain.
Regards,
Balaji.P
*From:*Justin Hammond [mailto:justin.hamm...@rackspace.com]
*Sent:* Saturday, September 21, 2013 9:13 AM
*To:* OpenStack Development Mailing List
*Subject:* Re: [openstack-dev] [Neutron] PTL Candidacy
I agree. +1. Mark has been nothing but helpf
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 and
Big Plus 1 for Mark!
Great PTL and Excellent Job in Neutron!
Edgar
On Fri, Sep 20, 2013 at 1:44 PM, Mark McClain wrote:
>
> 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
+1 for Mark McClain.
Regards,
Balaji.P
From: Justin Hammond [mailto:justin.hamm...@rackspace.com]
Sent: Saturday, September 21, 2013 9:13 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] PTL Candidacy
I agree. +1. Mark has been nothing but helpful to me and I have
ate: Fri, 20 Sep 2013 18:03:44 -0700
To: OpenStack Development Mailing List
mailto: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 20, 2013 at 1:44 PM, Mark McClain
mailto:mark.mcc
+1
Mark has done a phenomenal job as Neutron PTL
On Fri, Sep 20, 2013 at 1:44 PM, Mark McClain wrote:
>
> 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 exi
I think many people like me want to know the plan, when can remove Nova
network?
On Sat, Sep 21, 2013 at 4:44 AM, Mark McClain wrote:
>
> 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
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
57 matches
Mail list logo