settingsLogin | Registersettings

[Openstack] What neutron agent on Compute node?

0 votes

After fiddling with the bridge interfaces etc, I ended up
with a not-working-at-all system (not sure why, reboot
or something else).

But it also ended up as something weird.

----- s n i p -----
[this is the Control node]
bladeA01:~# neutron agent-list
+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+
| id | agenttype | host | availabilityzone | alive | adminstateup | binary |
+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+
| 223d58b0-df0a-4b4b-aabb-0c23cabc8b98 | L3 agent | bladeA01 | nova | :-) | True | neutron-l3-agent |
| 34542c7d-0efa-4bc3-84ca-a154176bedd0 | Open vSwitch agent | bladeA01 | | :-) | True | neutron-openvswitch-agent |
| 50a43570-cebb-4f1c-b690-05d3a73b8a00 | DHCP agent | bladeA01 | nova | :-) | True | neutron-dhcp-agent |
| 78ba5409-01a5-4875-b3af-08643280438c | Open vSwitch agent | bladeA03 | | :-) | True | neutron-openvswitch-agent |
| 7a5b3f1f-5d0e-4791-a5ce-d4e9dd253295 | L3 agent | bladeA03 | nova | :-) | True | neutron-l3-agent |
| 8a80a356-3f14-4cb5-8625-37021c89a9aa | Metering agent | bladeA01 | | :-) | True | neutron-metering-agent |
+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+

bladeA01:~# ip netns
qdhcp-d85ba6b9-3d7f-45e1-a1c3-ed239747b758
qdhcp-ef6fabfb-704d-43bc-902b-831ff6a79bd3
qdhcp-d7729d5b-069d-4781-b09f-0536806be0da

[this is the Compute node]
bladeA03:~# ip netns
qrouter-bbceece4-3e49-464d-a81b-16ec51fa6d0a
----- s n i p -----

So previously, they where all running on the Control node.
But this time, qrouter ended up on the Control node.

This actually got me thinking - should there BE a L3/Open vSwitch
agent running on the Compute node at all?? Isn't this the job of
the Control node!?
--
Det är när man känner doften av sin egen avföring
som man börjar undra vem man egentligen är.
- Arne Anka


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
asked Jun 29, 2016 in openstack by Turbo_Fredriksson (8,980 points)   7 13 19

4 Responses

0 votes

It depends on if you are using Distributed Virtual Routing (DVR). If so,
each compute node also needs to be running the l3 agent since the routing
is done locally at each node.
On Jun 29, 2016 11:57 AM, "Turbo Fredriksson" turbo@bayour.com wrote:

After fiddling with the bridge interfaces etc, I ended up
with a not-working-at-all system (not sure why, reboot
or something else).

But it also ended up as something weird.

----- s n i p -----
[this is the Control node]
bladeA01:~# neutron agent-list

+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+
| id | agenttype | host |
availability
zone | alive | adminstateup | binary |

+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+
| 223d58b0-df0a-4b4b-aabb-0c23cabc8b98 | L3 agent | bladeA01 |
nova | :-) | True | neutron-l3-agent |
| 34542c7d-0efa-4bc3-84ca-a154176bedd0 | Open vSwitch agent | bladeA01 |
| :-) | True | neutron-openvswitch-agent |
| 50a43570-cebb-4f1c-b690-05d3a73b8a00 | DHCP agent | bladeA01 |
nova | :-) | True | neutron-dhcp-agent |
| 78ba5409-01a5-4875-b3af-08643280438c | Open vSwitch agent | bladeA03 |
| :-) | True | neutron-openvswitch-agent |
| 7a5b3f1f-5d0e-4791-a5ce-d4e9dd253295 | L3 agent | bladeA03 |
nova | :-) | True | neutron-l3-agent |
| 8a80a356-3f14-4cb5-8625-37021c89a9aa | Metering agent | bladeA01 |
| :-) | True | neutron-metering-agent |

+--------------------------------------+--------------------+----------+-------------------+-------+----------------+---------------------------+

bladeA01:~# ip netns
qdhcp-d85ba6b9-3d7f-45e1-a1c3-ed239747b758
qdhcp-ef6fabfb-704d-43bc-902b-831ff6a79bd3
qdhcp-d7729d5b-069d-4781-b09f-0536806be0da

[this is the Compute node]
bladeA03:~# ip netns
qrouter-bbceece4-3e49-464d-a81b-16ec51fa6d0a
----- s n i p -----

So previously, they where all running on the Control node.
But this time, qrouter ended up on the Control node.

This actually got me thinking - should there BE a L3/Open vSwitch
agent running on the Compute node at all?? Isn't this the job of
the Control node!?
--
Det är när man känner doften av sin egen avföring
som man börjar undra vem man egentligen är.
- Arne Anka


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2016 by kevin_at_benton.pub (15,600 points)   2 3 5
0 votes

On Jun 29, 2016, at 7:15 PM, Kevin Benton wrote:

It depends on if you are using Distributed Virtual Routing (DVR). If so,
each compute node also needs to be running the l3 agent since the routing
is done locally at each node.

Ok, thanx. It doesn't say on

http://docs.openstack.org/admin-guide/networking_config-agents.html

and the first section isn't clear either:

Plug-ins typically have requirements for particular software
that must be run on each node that handles data packets. This
includes any node that runs nova-compute and nodes that run
dedicated OpenStack Networking service agents such as
neutron-dhcp-agent, neutron-l3-agent, neutron-metering-agent
or neutron-lbaas-agent.

The first sentence is quite clear. But the second indicates that
it should also run on the Compute.

But with your answer above, that makes it more clear, but it should
say that..
--
Choose a job you love, and you will never have
to work a day in your life.

responded Jun 29, 2016 by Turbo_Fredriksson (8,980 points)   7 13 19
0 votes

Even if you are NOT running DVR, the OVS agent (but not L3) needs to run on the compute to plumb the networking for instances on that node. The L3 agent only needs to run on the network node unless you are running DVR.

John

On Jun 29, 2016, at 2:19 PM, Turbo Fredriksson turbo@bayour.com wrote:

On Jun 29, 2016, at 7:15 PM, Kevin Benton wrote:

It depends on if you are using Distributed Virtual Routing (DVR). If so,
each compute node also needs to be running the l3 agent since the routing
is done locally at each node.

Ok, thanx. It doesn't say on

http://docs.openstack.org/admin-guide/networking_config-agents.html

and the first section isn't clear either:

Plug-ins typically have requirements for particular software
that must be run on each node that handles data packets. This
includes any node that runs nova-compute and nodes that run
dedicated OpenStack Networking service agents such as
neutron-dhcp-agent, neutron-l3-agent, neutron-metering-agent
or neutron-lbaas-agent.

The first sentence is quite clear. But the second indicates that
it should also run on the Compute.

But with your answer above, that makes it more clear, but it should
say that..
--
Choose a job you love, and you will never have
to work a day in your life.


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jul 1, 2016 by John_Belamaric (2,140 points)   1 2
0 votes

On Jul 1, 2016, at 9:28 PM, John Belamaric wrote:

Even if you are NOT running DVR, the OVS agent (but not L3) needs to run on the compute to plumb the networking for instances on that node. The L3 agent only needs to run on the network node unless you are running DVR.

Ah! That's might be why I get a qrouter-xxx network name space
on the Compute node(?)!

I guess that's true for the LBaaS, VPNaaS and FWaaS agents as well?
--
You know, boys, a nuclear reactor is a lot like a woman.
You just have to read the manual and press the right buttons
- Homer Simpson

responded Jul 1, 2016 by Turbo_Fredriksson (8,980 points)   7 13 19
...