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
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
++
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:
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 >
Reply-To: "OpenStack Development
)
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
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
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
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
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
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
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
.
Cheers, Robert
On 2/13/15, 12:16 PM, Kyle Mestery mest...@mestery.com
mailto:mest...@mestery.com wrote:
On Fri, Feb 13, 2015 at 10:57 AM, John Davidge (jodavidg)
jodav...@cisco.com mailto:jodav...@cisco.com wrote:
Hi Ihar,
To answer your questions in order:
1. Yes, you
Hi Ihar,
To answer your questions in order:
1. Yes, you are understanding the intention correctly. Dibbler doesn¹t
currently support client restart, as doing so causes all existing
delegated prefixes to be released back to the PD server. All subnets
belonging to the router would potentially
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
14 matches
Mail list logo