Re: [openstack-dev] [Neutron] Question about service subnets spec

Resurrecting this thread from last week. On 5/31/16, 10:11 PM, "Brian Haley" wrote: >> At this point the enumeration values map simply to device owners. For >>example: >> >>router_ports -> "network:router_gateway" >>dvr_fip_ports ->

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

Yes, as Brian says this will be covered by the follow-up patch to [2] which I¹m currently working on. Thanks for the question. John On 8/1/16, 3:17 PM, "Brian Haley" wrote: >On 07/31/2016 06:27 AM, huangdenghui wrote: >> Hi >>Now we have spec named subnet service

Re: [openstack-dev] [neutron] OVO Status Dashboard

Thanks Victor, This is a nice way to track the work. If this is going to replace the etherpad[1] then can I suggest including links to reviews in place of the In Progress/Done text for each entry? The color coding will preserve the completion status. John [1]

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

+1 On 2/20/17, 4:48 AM, "Carlos Gonçalves" wrote: >+1 > >On Mon, Feb 20, 2017 at 9:17 AM, Kevin Benton > wrote: > >No problem. Keep sending in RSPVs if you haven't already. > >On Mon, Feb 20, 2017 at 2:59 AM, Furukawa, Yushiro >

[openstack-dev] [neutron] [docs] PTG Neutron Documentation Session

Hi Everyone, The OpenStack Manuals team will be holding a PTG session to discuss the current state and future of the Networking Guide[1] on: Tuesday at 3:00pm - 3:40pm in the documentation room. Anyone interested in helping with continued improvements and bug fixes is encouraged to attend.

Re: [openstack-dev] [api][doc][neutron] what releases should API reference support?

On 9/6/16, 2:02 PM, "Ihar Hrachyshka" wrote: >Akihiro Motoki wrote: > >> What releases should we support in API references? >> There are several options. >> >> 1. The latest stable release + master >> 2. All supported stable releases + master >> 3. more

[openstack-dev] [OSC] Tenant Resource Cleanup

Hello, During the Mitaka cycle we merged a new feature into the python-neutronclient called 'neutron purge'. This enables a simple CLI command that deletes all of the neutron resources owned by a given tenant. It's documented in the networking guide[1]. We did this in response to feedback

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

Thierry Carrez wrote: >[...] >In the last years there were a lot of "questions" asked by random >contributors, especially around the "One OpenStack" principle (which >seems to fuel most of the reaction here). Remarks like "we should really >decide once and for all if OpenStack is a collection of

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

Jay Pipes wrote: >[…] >The TC doesn't comply with anything at all. It's the body that is >elected to make overarching governance decisions for the OpenStack >community. Sure, that's an important distinction. My point is that when governance decisions are made that seem to contradict each

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Thierry Carrez wrote: >Edward Leafe wrote: >> [...] >> The current candidacy essay would now be posted in the campaign period, >>rather than at the time of nomination, and should exclude the sort of >>biographical information that is currently the most important piece for >>many people. [...] >

Re: [openstack-dev] [all][elections] Results of the TC Election

On 10/10/16, 5:36 AM, Monty Taylor wrote: >It's really nice to see that we had an increase in turnout percentage >even in the face of having our largest electorate yet. > >Thanks for all your great work!!! > >Monty +100 Thank you as well to all the candidates and standing TC members who took

Re: [openstack-dev] [neutron] Skip-only tests

John Schwarz wrote: >Hi all, > >The Neutron community has recently started contributing Tempest >scenario tests in the Neutron tree and I'd like to discuss a general >issue we're hitting. Mainly, we're talking about required hardware for >some features and/or VM images that support more features,

Re: [openstack-dev] [all][elections][TC] TC Candidacy

Thanks for the questions Jay, answers inline. On 9/26/16, 8:39 PM, Jay Pipes wrote: >Who decides what is integral to OpenStack and what merely "enhances" it, >though? The TC? The DefCore group? The Board of Directors? One might say >all three groups have a say in defining what "is OpenStack", no?

Re: [openstack-dev] [all][elections][TC] TC Candidacy

, John [1] https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement On 9/27/16, 5:13 PM, Zane Bitter wrote: >On 27/09/16 06:19, John Davidge wrote: >>> Having Stackforge as a separate Github organization and set of >>> >repositories was a maintenance nightmar

[openstack-dev] [all][elections][TC] TC Candidacy

Hi everyone, I'd like to submit my candidacy for the OpenStack Technical Committee. You may know me as john-davidge on IRC. I've been an active member of the OpenStack community since 2012 (Folsom). I met many of you for the first time while presenting the Curvature Network Visualization

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Hi Erin, Thank you for the details. Can you tell us anything about how discount codes for ATCs will change for Boston and onwards? Thanks, John From: Erin Disney > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Neutron] Stepping down from core

It's been a pleasure to work with you these past few years, Carl. I wish you all the best in whatever's next for you. Hopefully we'll meet again soon in the not so distant future. There will forever be a Carl-shaped hole in our codebase. John From: Carl Baldwin

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

Steve, Why just the one summit? Each cycle has a PTG and a summit, which makes 4 events per year. John From: "Steven Dake (stdake)" > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] PTG from the Ops Perspective - a few short notes

On 10/12/16, 11:18 AM, Dmitry Tantsur wrote: >On 10/12/2016 11:59 AM, Thierry Carrez wrote: >> >> PTGs happen in more cost-effective locations, airport hubs with cheaper >> hotels, which should lower the cost of attending. Yes, I'm pretty sure >> traveling to Atlanta downtown for a week will be

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

+1 Thanks Miguel! From: Miguel Lavalle > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Friday, October 14, 2016 at 7:30 PM To: OpenStack

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

Huge +1 from me. Miguel has been doing an excellent job chairing the l3-subteam meetings for a long time now. Well deserved! On 12/16/16, 11:00 AM, "Rossella Sblendido" wrote: >well deserved, +1! > >On 12/16/2016 09:32 AM, Miguel Angel Ajo Pelayo wrote: >> +1 :) >> >> On

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

On 12/6/16, 6:06 PM, "Tidwell, Ryan" wrote: > >I failed to make much mention of it in previous write-ups, but I also >encountered scale issues with listing ports after a certain threshold. I >haven’t gone back > to identify where the tipping point is, but I did notice that

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

On 1/9/17, 2:11 PM, "Armando M." wrote: >Hi neutrinos, > >The PTL nomination week is fast approaching [0], and as you might have >guessed by the subject of this email, I am not planning to run for Pike. >If I look back at [1], I would like to think that I was able to exercise

Re: [openstack-dev] [docs] Stepping down from core

On 12/21/16, 4:11 PM, "Matt Kassawara" wrote: >Howdy! > > >After several years of contributing to OpenStack documentation, a >significant change in my career path warrants resigning from my role as a >core reviewer. Working with the OpenStack community was a great

[openstack-dev] [neutron][all] So long, and thanks for all the fish

Friends and colleagues, It is with a heavy heart that I write to say my adventure in the OpenStack community is coming to an end. It began in 2012 with my first job as an intern at Cisco, and ends here as the Technical Lead for Neutron in the OpenStack Innovation Center at Rackspace. In that

[openstack-dev] [Horizon] [UX] Curvature interactive virtual network design

As discussed in the Horizon contributor meet up, here at Cisco we’re interested in upstreaming our work on the Curvature dashboard into Horizon. We think that it can solve a lot of issues around guidance for new users and generally improving the experience of interacting with Neutron. Possibly

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

in the various distros. I¹m not sure if there is a way to avoid this problem, unless we have devstack install from our updated repo while we wait. John Davidge OpenStack@Cisco On 13/02/2015 16:01, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

Copying my response on the review below: Yes that completely makes sense Sean. In our original proposal we wanted to allow the user to initiate a subnet-create without providing a CIDR, and have an 'ipv6_pd_enabled' flag which could be set in the API call to tell Neutron that this particular

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

17:40, John Davidge (jodavidg) jodav...@cisco.com wrote: Hello all, We now have a work-in-progress patch up for review: https://review.openstack.org/#/c/158697/ Feedback on our approach is much appreciated. Many thanks, John Davidge OpenStack@Cisco On 20/02/2015 18:28, Ihar Hrachyshka

Re: [openstack-dev] [neutron] Prefix delegation using dibbler client

Hello all, We now have a work-in-progress patch up for review: https://review.openstack.org/#/c/158697/ Feedback on our approach is much appreciated. Many thanks, John Davidge OpenStack@Cisco On 20/02/2015 18:28, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

Following discussion on IRC, a patch is now up to add this config option. Reviews appreciated. https://review.openstack.org/#/c/166973/ Cheers, John On 23/03/2015 18:11, Carl Baldwin c...@ecbaldwin.net wrote: On Mon, Mar 23, 2015 at 12:04 PM, John Davidge (jodavidg) jodav...@cisco.com

Re: [openstack-dev] [Neutron][IPv6] Prefix delegation and user facing API thoughts

Going forward, I think the best approach for PD would be to align with the subnet-pools being added by the subnet allocation BP work (thanks to Sean for bringing this to our attention again). http://specs.openstack.org/openstack/neutron-specs/specs/kilo/subnet-alloca tion.html#rest-api-impact

Re: [openstack-dev] [neutron] IPv4 transition/interoperation with IPv6

On the subject of Prefix Delegation - yes, the external system is responsible for the routing. Here¹s a couple of video guides on using PD in Neutron and setting up the Prefix Delegation Server (in this case a dibbler server): Using Neutron PD: https://www.youtube.com/watch?v=wI830s881HQ

[openstack-dev] [openstack-infra] [neutron] Third Party CI Voting

Hi all, Recent neutron third party CI issues have got me thinking again about a topic which we discussed in Vancouver: Should any Third Party CI have voting rights for neutron patches in gerrit? I’d like to suggest that they shouldn’t. A -1 from a third party CI tool can often be an

Re: [openstack-dev] [openstack-infra] [neutron] Third Party CI Voting

) Subject: Re: [openstack-dev] [openstack-infra] [neutron] Third Party CI Voting On 25 June 2015 at 16:08, John Davidge (jodavidg) jodav...@cisco.commailto:jodav...@cisco.com wrote: Hi all, Recent neutron third party CI issues have got me thinking again about a topic which we discussed

Re: [openstack-dev] [Neutron] Mid-cycle meetup for Mitaka

++ Sounds very sensible to me! John From: "Armando M." > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday, 4 November 2015 21:23 To:

Re: [openstack-dev] [OpenStack-docs][Neutron] Networking Guide - Call for contributors

Hi Edgar, Happy to continue contributing here. Currently in GMT timezone, but probably PST by the end of the year. Looking forward to the first meeting! Cheers, John Davidge From: Edgar Magana <edgar.mag...@workday.com<mailto:edgar.mag...@workday.com>> Reply-To: "Open

Re: [openstack-dev] [neutron] gate-neutron-dsvm-api failures

On 1/14/16, 3:04 PM, "Brian Haley" <brian.ha...@hpe.com> wrote: >On 01/14/2016 05:42 PM, John Davidge (jodavidg) wrote: >> The >>neutron.tests.api.admin.test_floating_ips_admin_actions.FloatingIPAdminTe >>stJSON >> test has been consistently failing fo

[openstack-dev] [neutron] gate-neutron-dsvm-api failures

The neutron.tests.api.admin.test_floating_ips_admin_actions.FloatingIPAdminTestJSON test has been consistently failing for patch https://review.openstack.org/#/c/258754/ and I don't see how they can be related. This patch has been trying to merge for a month. This test seems to be

Re: [openstack-dev] [Heat] HOT Software orchestration proposal for workflows

://ciscosystems.github.io/curvature/ http://ciscosystems.github.io/donabe/ It looks like some of the ground covered by these projects can be helpful to this discussion. John Davidge jodav...@cisco.com -- Forwarded message -- From: Thomas Spatzier thomas.spatz...@de.ibm.com Date: Wed, Oct