Open Stack

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 at 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                                   | agent_type         | host     |
> availability_zone | alive | admin_state_up | 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 at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160629/91a63d59/attachment.html>