Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

2016-06-06 Thread Kevin Benton 
The L3 agent will plug ports into things, but it doesn't know anything
about wiring them up for the appropriate VXLAN/VLAN/whatever. That's all
very l2 specific logic and dependent on if using linuxbridge/ovs/etc.

Think of the l3 agent just like it is Nova wiring up VMs. It plugs them in
and then the l2 agent does the appropriate l2 stuff for each port.
On Jun 6, 2016 11:46 AM, "Sean M. Collins"  wrote:

> Armando M. wrote:
> > The short answer to your question in the question is yes. For OVS,
> wherever
> > you run network services (l3 or dhcp), you need an l2 agent that in
> charge
> > of port wiring.
>
> OK - I'm going senile then. For some reason I thought the L3 agent
> called the same code paths for doing wiring of router ports and didn't
> need the L2 agent running.
> --
> Sean M. Collins
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

2016-06-06 Thread Sean M. Collins 
Armando M. wrote:
> The short answer to your question in the question is yes. For OVS, wherever
> you run network services (l3 or dhcp), you need an l2 agent that in charge
> of port wiring.

OK - I'm going senile then. For some reason I thought the L3 agent
called the same code paths for doing wiring of router ports and didn't
need the L2 agent running.
-- 
Sean M. Collins

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

2016-06-06 Thread Armando M. 
On 6 June 2016 at 19:59, Sean M. Collins  wrote:

> While reviewing https://review.openstack.org/#/c/292778/5 I think I
> might have found a bit of coupling between the neutron l2 agent and the
> l3 agent when it comes to DevStack.
>
> In the DevStack neutron guide - the "control node" currently
> does double duty as both an API server and also as a compute host.
>
>
> https://github.com/openstack-dev/devstack/blob/master/doc/source/guides/neutron.rst#devstack-configuration
>
> Extra compute nodes have a pretty short configuration
>
>
> https://github.com/openstack-dev/devstack/blob/master/doc/source/guides/neutron.rst#devstack-compute-configuration
>
> So, recently I poked at having a pure control node on the "devstack-1"
> host, by removing the q-agt and n-cpu entries from ENABLED_SERVICES,
> while leaving q-l3.
>
> It appears that the code in DevStack, relies on the presence of q-agt in
> order to create the integration bridge (br-int), so when the L3 agent
> comes up it complains because br-int hasn't been created.
>
>
> https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/ovs_base#L20
>
> Anyway, here's the fix.
>
> https://review.openstack.org/#/c/326063/


The short answer to your question in the question is yes. For OVS, wherever
you run network services (l3 or dhcp), you need an l2 agent that in charge
of port wiring.


>
> --
> Sean M. Collins
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

2016-06-06 Thread Assaf Muller 
On Mon, Jun 6, 2016 at 1:59 PM, Sean M. Collins  wrote:
> While reviewing https://review.openstack.org/#/c/292778/5 I think I
> might have found a bit of coupling between the neutron l2 agent and the
> l3 agent when it comes to DevStack.
>
> In the DevStack neutron guide - the "control node" currently
> does double duty as both an API server and also as a compute host.
>
> https://github.com/openstack-dev/devstack/blob/master/doc/source/guides/neutron.rst#devstack-configuration
>
> Extra compute nodes have a pretty short configuration
>
> https://github.com/openstack-dev/devstack/blob/master/doc/source/guides/neutron.rst#devstack-compute-configuration
>
> So, recently I poked at having a pure control node on the "devstack-1"
> host, by removing the q-agt and n-cpu entries from ENABLED_SERVICES,
> while leaving q-l3.
>
> It appears that the code in DevStack, relies on the presence of q-agt in
> order to create the integration bridge (br-int), so when the L3 agent
> comes up it complains because br-int hasn't been created.
>
> https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/ovs_base#L20
>
> Anyway, here's the fix.
>
> https://review.openstack.org/#/c/326063/

The L3 agent requires an L2 agent on the same host. It's not just
about creating the bridge, it's also about plugging the router/dhcp
ports correctly.

>
> --
> Sean M. Collins
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron][devstack] Does the openvswitch-agent need to be run along side the neutron-l3-agent?

2016-06-06 Thread Sean M. Collins 
While reviewing https://review.openstack.org/#/c/292778/5 I think I
might have found a bit of coupling between the neutron l2 agent and the
l3 agent when it comes to DevStack.

In the DevStack neutron guide - the "control node" currently 
does double duty as both an API server and also as a compute host.

https://github.com/openstack-dev/devstack/blob/master/doc/source/guides/neutron.rst#devstack-configuration

Extra compute nodes have a pretty short configuration

https://github.com/openstack-dev/devstack/blob/master/doc/source/guides/neutron.rst#devstack-compute-configuration

So, recently I poked at having a pure control node on the "devstack-1"
host, by removing the q-agt and n-cpu entries from ENABLED_SERVICES,
while leaving q-l3.

It appears that the code in DevStack, relies on the presence of q-agt in
order to create the integration bridge (br-int), so when the L3 agent
comes up it complains because br-int hasn't been created.

https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/ovs_base#L20

Anyway, here's the fix.

https://review.openstack.org/#/c/326063/

-- 
Sean M. Collins

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev