Ask Your Question
1

Neutron Agents Missing?

asked 2015-02-04 08:55:27 -0500

jdiaz9 gravatar image

I am in the process of deploying OpenStack IceHouse through a virtualbox setup and I am confused as to why I am only seeing the "Open vSwitch Agent" on the compute node when I do a neutron agent-list. All of the other agents are missing (l3, dhcp, metadata, and Open vSwitch Agent on Network Node).

Any ideas as to what might be happening? How do I add these agents after the fact. It seems the issue appears to be specific to the network node.

Any idea would be appreciated.

edit retag flag offensive close merge delete

Comments

How did you install? I install via packstack with answer-file. If you did similar, can you post the NEUTRON elements from your file?

mickt gravatar imagemickt ( 2015-02-04 10:02:34 -0500 )edit

Figured it out, I was missing the rabbit_mq and rpc_backend on the network neutron.conf file.

jdiaz9 gravatar imagejdiaz9 ( 2015-02-05 00:34:07 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2015-02-05 02:33:00 -0500

mickt gravatar image

updated 2015-02-05 02:36:08 -0500

My juno deployment on CentOS7 (via packstack) of 1 controller/neutron and 3 compute has Open vSwitch, Metadata & DHCP Agents on each compute host. L3 Agent is only on neutron host.

edit flag offensive delete link more
0

answered 2015-02-04 23:21:30 -0500

larsks gravatar image

updated 2015-02-04 23:22:25 -0500

You would not typically expect to find any agents other than the "Open vSwitch Agent" running on the compute node. For example, consider this output from neutron agent-list from an environment with three controller hosts and two compute nodes:

+--------------------------------------+--------------------+-----------------------+-------+----------------+---------------------------+
| id                                   | agent_type         | host                  | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+-----------------------+-------+----------------+---------------------------+
| 32edf08c-79b7-4a8f-9b3c-44ad9104f176 | L3 agent           | neutron-n-0           | :-)   | True           | neutron-l3-agent          |
| 3ac64bb3-6df9-427e-a0e1-df2c387bb22a | DHCP agent         | neutron-n-0           | :-)   | True           | neutron-dhcp-agent        |
| 5af89858-3379-4da6-b235-11476750e458 | Metadata agent     | neutron-n-0           | :-)   | True           | neutron-metadata-agent    |
| 7a0c10b6-467d-4f1c-9349-793a491b0cab | Open vSwitch agent | neutron-n-0           | :-)   | True           | neutron-openvswitch-agent |
| 9b78ff12-8e9a-4853-af2d-74d84324120a | Open vSwitch agent | mac525400b10d7b.local | :-)   | True           | neutron-openvswitch-agent |
| d745e408-7ea4-4221-b009-a462de326fed | Open vSwitch agent | mac525400059061.local | :-)   | True           | neutron-openvswitch-agent |
+--------------------------------------+--------------------+-----------------------+-------+----------------+---------------------------+

The other agents provide network control services and often there is only a single active instance of each agent in a given deployment.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-02-04 08:55:27 -0500

Seen: 822 times

Last updated: Feb 05 '15