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 -> "network:floatingip_agent_gateway"
>>
>> It was at thi
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 time
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 types, which provides a
>>
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] https://etherpad.openstack.org/p/new
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 older releases too?
>>
>> Option 2 sound
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 from
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 i
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 other,
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 Horizon
>began to reall
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 Fri, Dec 16, 2016 at 2:4
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
>experience and I hope it contin
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
>the influence on th
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.
Than
+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
> wrote:
>
>
>
>+1
>
>Sorry for late, Kevin!!
>
>
> Yushiro Furu
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,
Honestly, I had assumed Ihar was on the Drivers team already :)
A great addition to the team, and much deserved!
From: Paul Michali mailto:p...@michali.net>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, Septembe
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
Vis
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?
community.
All the best,
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
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. [...]
>
>A
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
par
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 ch
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)" mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, Oct
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 mailto:e...@openstack.org>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.ope
+1
Thanks Miguel!
From: Miguel Lavalle mailto:mig...@mlavalle.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, October 14, 2016 at 7:30 PM
To: OpenStack Development Mailing List
mailto:openstack-dev@lists.ope
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 mailto:c...@ecbaldwin.net>>
Repl
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 a
++
Sounds very sensible to me!
John
From: "Armando M." mailto:arma...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, 4 November 2015 21:23
To: "OpenStack Development Mailing List (not for usage que
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 experiencing
On 1/14/16, 3:04 PM, "Brian Haley" 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 for patch
>> https://r
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 mailto:edgar.mag...@workday.com>>
Reply-To: "OpenStack Development Mailing List (no
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 indication
;
Subject: Re: [openstack-dev] [openstack-infra] [neutron] Third Party CI Voting
On 25 June 2015 at 16:08, John Davidge (jodavidg)
mailto:jodav...@cisco.com>> wrote:
Hi all,
Recent neutron third party CI issues have got me thinking again about a topic
which we discussed in Vancouver
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" wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Thanks
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" wrote:
>-BEGIN PGP SIGNED MESSAGE
/2015 17:40, "John Davidge (jodavidg)" 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
>OpenStac
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 subne
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
Th
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" wrote:
>On Mon, Mar 23, 2015 at 12:04 PM, John Davidge (jodavidg)
> wrote:
>&g
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
Configur
http://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
>Date: Wed, Oct 9, 201
41 matches
Mail list logo
