[OVN]- openstack network agent list command doesn't display anything
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Medium
|
Terry Wilson |
Bug Description
The command line: 'openstack network agent list' doesn't display the status of OVN services of each node.
In OVN there are no agents (like in ODL) but I expected to get any indication of the connection status between OVN services of each node (Controller & compute nodes)
Version-Release: Pike
How reproducible: 100%
Steps to Reproduce:
1. Deploy Director HA Pike with OVN
2. type the command: 'openstack network agent list'
Actual results: no output!
Expected results:
Took example from ODL
# openstack network agent list
+------
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |
+------
| 2f6fae0d-
| 4024d452-
| 69d9b928-
| b0a28f38-
| eecb8ce1-
Expect- status of each OVN on each node-
# openstack network agent list
+------
| ID | Agent Type | Host | Availability Zone | Alive | State | Binary |
+------
| 2f6fae0d-
| 4024d452-
Changed in networking-ovn: | |
assignee: | nobody → venkata anil (anil-venkata) |
Changed in networking-ovn: | |
importance: | Undecided → Medium |
Changed in networking-ovn: | |
assignee: | venkata anil (anil-venkata) → Terry Wilson (otherwiseguy) |
Changed in networking-ovn: | |
status: | New → In Progress |
I thought we can use "Connection" TABLE from ovn-sbdb. But unfortunately it is not creating a separate row for each ovn-controller client. So when a ovn-controller is down, we are not sure which ovn-controller is down. May be we need to enhance ovsdb-server to update the particulars of the inactive ovn-controller in external_ ids/other_ config columns of "Connection" Table.
Another approach can be, ovn-controller has to periodically update their status in ovn-sbdb, like the way neutron agents periodically report their status to neutron server?
Once we have the mechanism to identify the status of ovn-controller, we should work on how we display this information to users.
1) neutron agent-list ------- ------- ------- ------- ----+-- ------- ------- ----+-- ------- ------- ---+--- ------- ------- --+---- ---+--- ------- ------+ ------- ------- ------- ------+ ------- ------- ------- ------- ----+-- ------- ------- ----+-- ------- ------- ---+--- ------- ------- --+---- ---+--- ------- ------+ ------- ------- ------- ------+ 4771-48be- 9e72-63f2b99f34 90 | L3 agent | devstack.rdocloud | nova | xxx | True | neutron-l3-agent | 1167-4a44- a260-00dd4edc6f d1 | Metadata agent | devstack.rdocloud | | xxx | True | neutron- metadata- agent | c967-4d20- b1bf-f2380ba054 ea | DHCP agent | devstack.rdocloud | nova | xxx | True | neutron-dhcp-agent | 65dc-43e2- b374-de8e1560b5 45 | Open vSwitch agent | devstack.rdocloud | | xxx | True | neutron- openvswitch- agent |
+------
| id | agent_type | host | availability_zone | alive | admin_state_up | binary |
+------
| 4cd5fcdd-
| 5e0fb37c-
| 6aae495b-
| fc6fd801-
We have to decide which agent types OVN support. It doesn't support DHCP agent. It has Metadata agent(how to report its status?). We can use "L3 agent" type for ovn-controller which has "enable- chassis- as-gw" flag. Do we need to have a separate agent type for computes or shall we go ahead with "Open vSwitch agent"?
Alternatively we can define separate agent types for OVN, example
OVN-Gateway
OVN-compute
I think we can also support below commands in OVN. list-hosting- router router1 ------- ------- ------- ------- ----+-- ------- ------- ---+--- ------- ------+ ------- +------ ----+ ------- ------- ------- ------- ----+-- ------- ------- ---+--- ------- ------+ ------- +------ ----+ 4771-48be- 9e72-63f2b99f34 90 | devstack.rdocloud | True | xxx | | ------- ------- ------- ------- ----+-- ------- ------- ---+--- ------- ------+ ------- +------ ----+ list-on- l3-agent 4cd5fcdd- 4771-48be- 9e72-63f2b99f34 90 ------- ------- ------- ------- ----+-- ------- +------ ------- ------- ------- ------- +------ ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------. ..
(neutron) l3-agent-
+------
| id | host | admin_state_up | alive | ha_state |
+------
| 4cd5fcdd-
+------
(neutron) router-
+------