More updates:
https://review.openstack.org/#/q/status:open+project:openstack-dev/devstack+branch:master+topic:neutron-refactor
Has the fixes for things I screwed up. Basically it looks like just the
_configure_neutron_l3_agent got clobbered which could have broken people
using neutron-legacy.
I'm seeing some mistakes I made when moving over the contents of
neutron-legacy that were l3 related into the new file. It didn't trigger
any failures in the gate, but it might impact some developer machines or
third party systems. I'm putting together patches, but also considering
reverting
On 05/11/2016 02:48 PM, Sean M. Collins wrote:
> A quick update, https://review.openstack.org/168438 has landed.
>
> There is a lot of work that needs to be done, Armando and I spoke
> yesterday about some of the hooks that are present in neutron-legacy
> that both in-tree and out-of-tree
A quick update, https://review.openstack.org/168438 has landed.
There is a lot of work that needs to be done, Armando and I spoke
yesterday about some of the hooks that are present in neutron-legacy
that both in-tree and out-of-tree consumers rely on being called.
Doing a quick git grep - we
On 5 May 2016 at 11:31, Sean M. Collins wrote:
> Sean M. Collins wrote:
> > Here is the patch I'm using to test the refactor against the Neutron
> > CI jobs.
> >
> > https://review.openstack.org/#/c/278417/
> >
>
> Here's the test patch to make sure anything that is using the
Where do I propose my new option
NEUTRON_MAYBE_L3_MTU_VXLAN_AGENTMODE_FLOATINGIPS ?
On Thu, May 5, 2016 at 11:31 AM, Sean M. Collins wrote:
> Sean M. Collins wrote:
> > Here is the patch I'm using to test the refactor against the Neutron
> > CI jobs.
> >
> >
On 2016-05-05 15:57:22 + (+), Sean M. Collins wrote:
[...]
> So we did.
>
> https://review.openstack.org/168438
[...]
Remind me to buy you and Dean beer the next time I see you. It's
like you flipped the Etch A Sketch upside down and shook vigorously.
<>
--
Jeremy Stanley
Sean M. Collins wrote:
> Here is the patch I'm using to test the refactor against the Neutron
> CI jobs.
>
> https://review.openstack.org/#/c/278417/
>
Here's the test patch to make sure anything that is using the
neutron-legacy file isn't disrupted:
https://review.openstack.org/#/c/313049/
Terrific decision! Thank a lot for all this great work.
Edgar
On 5/5/16, 9:12 AM, "Monty Taylor" wrote:
>On 05/05/2016 10:57 AM, Sean M. Collins wrote:
>> During the Austin summit, there was a discussion in the QA meetings
>> about the future of Neutron's support in
On Thu, May 5, 2016 at 11:12 AM, Monty Taylor wrote:
> On 05/05/2016 10:57 AM, Sean M. Collins wrote:
>>
>> During the Austin summit, there was a discussion in the QA meetings
>> about the future of Neutron's support in DevStack. It's been an ongoing
>> effort, and I'd like
> On May 5, 2016, at 8:57 AM, Sean M. Collins wrote:
>
> During the Austin summit, there was a discussion in the QA meetings
> about the future of Neutron's support in DevStack. It's been an ongoing
> effort, and I'd like to step back and give everyone a view of the Big
>
Yeah, seriously, thanks a million for this.
You are making developers lives wa better!
2016-05-05 18:12 GMT+02:00 Monty Taylor :
> On 05/05/2016 10:57 AM, Sean M. Collins wrote:
>
>> During the Austin summit, there was a discussion in the QA meetings
>> about the future
On 05/05/2016 10:57 AM, Sean M. Collins wrote:
During the Austin summit, there was a discussion in the QA meetings
about the future of Neutron's support in DevStack. It's been an ongoing
effort, and I'd like to step back and give everyone a view of the Big
Picture.
Here is the patch I'm using to test the refactor against the Neutron
CI jobs.
https://review.openstack.org/#/c/278417/
There is still some work to be done, and it shows.
--
Sean M. Collins
__
OpenStack Development Mailing
14 matches
Mail list logo