Re: [openstack-dev] [all] devstack changing to neutron by default RSN - current issues with OVH

2016-08-08 Thread Sean M. Collins
+1 on this plan too, if the +2's I've been slinging haven't made it obvious :) -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all] devstack changing to neutron by default RSN - current issues with OVH

2016-08-08 Thread Armando M.
On 8 August 2016 at 08:01, Sean Dague wrote: > In summary, it turns out we learned a few things: > > 1) neutron guests in our gate runs don't have the ability to route > outwards. For instance, if they tried to do a package update, it would > fail. > > 2) adding the ability for

Re: [openstack-dev] [all] devstack changing to neutron by default RSN - current issues with OVH

2016-08-08 Thread Sean Dague
In summary, it turns out we learned a few things: 1) neutron guests in our gate runs don't have the ability to route outwards. For instance, if they tried to do a package update, it would fail. 2) adding the ability for them to route outwards (as would be expected for things like package

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Sean Dague
On 08/05/2016 04:32 PM, Armando M. wrote: > > > On 5 August 2016 at 13:05, Dan Smith > wrote: > > > I haven't been able to reproduce it either, but it's unclear how packets > > would get into a VM on an island since there is no router

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 13:05, Dan Smith wrote: > > I haven't been able to reproduce it either, but it's unclear how packets > > would get into a VM on an island since there is no router interface, and > > the VM can't respond even if it did get it. > > > > I do see outbound

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Dan Smith
> I haven't been able to reproduce it either, but it's unclear how packets > would get into a VM on an island since there is no router interface, and > the VM can't respond even if it did get it. > > I do see outbound pings from the connected VM get to eth0, hit the > masquerade rule, and

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Brian Haley
On 08/05/2016 02:32 PM, Armando M. wrote: > > Looking at the health trend for DVR [1], the test hasn't failed in a > while, so I wonder if this is induced by the proposed switch, even > though I can't correlate it just yet (still waiting for caffeine to kick

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Dan Smith
> The only functional difference in the new code that happens in > the gate > is the iptables rule: > > local default_dev="" > default_dev=$(ip route | grep ^default | awk '{print $5}') > sudo iptables -t nat -A POSTROUTING

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 11:25, Armando M. wrote: > > > On 5 August 2016 at 10:21, Sean Dague wrote: > >> On 08/05/2016 11:34 AM, Armando M. wrote: >> > >> > >> > On 5 August 2016 at 05:59, Sean Dague > > > wrote: >> > >> >

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 10:21, Sean Dague wrote: > On 08/05/2016 11:34 AM, Armando M. wrote: > > > > > > On 5 August 2016 at 05:59, Sean Dague > > wrote: > > > > On 08/04/2016 09:15 PM, Armando M. wrote: > > > So glad we are finally

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Sean Dague
On 08/05/2016 11:34 AM, Armando M. wrote: > > > On 5 August 2016 at 05:59, Sean Dague > wrote: > > On 08/04/2016 09:15 PM, Armando M. wrote: > > So glad we are finally within the grasp of this! > > > > I posted [1], just to err on the

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 07:39, Brian Haley wrote: > On 08/05/2016 08:59 AM, Sean Dague wrote: > >> On 08/04/2016 09:15 PM, Armando M. wrote: >> >>> So glad we are finally within the grasp of this! >>> >>> I posted [1], just to err on the side of caution and get the opportunity

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 05:59, Sean Dague wrote: > On 08/04/2016 09:15 PM, Armando M. wrote: > > So glad we are finally within the grasp of this! > > > > I posted [1], just to err on the side of caution and get the opportunity > > to see how other gate jobs for Neutron might be

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Brian Haley
On 08/05/2016 08:59 AM, Sean Dague wrote: On 08/04/2016 09:15 PM, Armando M. wrote: So glad we are finally within the grasp of this! I posted [1], just to err on the side of caution and get the opportunity to see how other gate jobs for Neutron might be affected by this change. Are there any

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Sean Dague
On 08/04/2016 09:15 PM, Armando M. wrote: > So glad we are finally within the grasp of this! > > I posted [1], just to err on the side of caution and get the opportunity > to see how other gate jobs for Neutron might be affected by this change. > > Are there any devstack-gate changes lined up

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-04 Thread Armando M.
On 4 August 2016 at 11:35, Sean Dague wrote: > One of the cycle goals in newton was to get devstack over to neutron by > default. Neutron is used by 90+% of our users, and nova network is > deprecated, and is not long for this world. > > Because devstack is used by developers as

[openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-04 Thread Sean Dague
One of the cycle goals in newton was to get devstack over to neutron by default. Neutron is used by 90+% of our users, and nova network is deprecated, and is not long for this world. Because devstack is used by developers as well as by out test infrastructure, the major stumbling block was coming