Description of problem: It is required to have a command line that gives us the cluster status from single point like we have with pcs status. It helps to get the status of per OVS DB on each controller node. Version-Release number of selected component (if applicable): OSP-12 openvswitch-ovn-common-2.7.2-4.git20170719.el7fdp.x86_64 python-networking-ovn-3.0.0-0.20170807061656.2425483.el7ost.noarch openvswitch-ovn-host-2.7.2-4.git20170719.el7fdp.x86_64 puppet-ovn-11.3.0-0.20170805080331.4425658.el7ost.noarch openvswitch-ovn-central-2.7.2-4.git20170719.el7fdp.x86_64 python-ovsdbapp-0.4.0-0.20170719205620.71ce425.el7ost.noarch python-openvswitch-2.7.2-4.git20170719.el7fdp.noarch openstack-neutron-openvswitch-11.0.0-0.20170807223712.el7ost.noarch openvswitch-2.7.2-4.git20170719.el7fdp.x86_64 openstack-neutron-11.0.0-0.20170807223712.el7ost.noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: The combination of "pcs status" and then checking status and db contents on each node is all we have right now Expected results: "single command" to check everything, DB sync. Additional info:
Can you please add example output? What information would you like to see?
Today we need to run : ovs-appctl -t ovsdb-server ovsdb-server/sync-status state: active on each openstack controller X 2 ovsdb-servers We would like to have something like +--------------------+--------------------------+-------------------+-------+----------------+------------+- | ovn-serice | host | alive | admin_state_up | binary | sync-status| +--------------------+--------------------------+-------------------+-------+----------------+------------+- | ovsdb-server | controller-1.localdomain | :-) | True | northbound-db |Active | ovsdb-server | controller-1.localdomain | :-) | True | southbound-db |Active | ovn-controller | controller-1.localdomain | xxx | True | ovn-north |N/A | ovsdb-server | controller-2.localdomain | :-) | True | northbound-db |Passive | ovsdb-server | controller-2.localdomain | xxx | True | southbound-db |Passive | ovn-controller | controller-2.localdomain | :-) | False | ovn-north |N/A | ovsdb-server | controller-3.localdomain | :-) | True | northbound-db |Passive | ovsdb-server | controller-3.localdomain | xxx | True | southbound-db |Passive | ovn-controller | controller-3.localdomain | :-) | False | ovn-north |N/A | ovn-controller | compute-3.localdomain | :-) | True | ovn-controller |N/A
Can't you just do the same thing doing a pcs status on any of the nodes of the cluster?
(In reply to Ofer Blaut from comment #2) > Today we need to run : > ovs-appctl -t ovsdb-server ovsdb-server/sync-status > state: active > > on each openstack controller X 2 ovsdb-servers > > > > We would like to have something like > > > +--------------------+--------------------------+-------------------+------- > +----------------+------------+- > | ovn-serice | host | alive | admin_state_up | > binary | sync-status| > +--------------------+--------------------------+-------------------+------- > +----------------+------------+- > | ovsdb-server | controller-1.localdomain | :-) | True | > northbound-db |Active > | ovsdb-server | controller-1.localdomain | :-) | True | > southbound-db |Active > | ovn-controller | controller-1.localdomain | xxx | True | > ovn-north |N/A > | ovsdb-server | controller-2.localdomain | :-) | True | > northbound-db |Passive > | ovsdb-server | controller-2.localdomain | xxx | True | > southbound-db |Passive > | ovn-controller | controller-2.localdomain | :-) | False | > ovn-north |N/A > | ovsdb-server | controller-3.localdomain | :-) | True | > northbound-db |Passive > | ovsdb-server | controller-3.localdomain | xxx | True | > southbound-db |Passive > | ovn-controller | controller-3.localdomain | :-) | False | > ovn-north |N/A > | ovn-controller | compute-3.localdomain | :-) | True | > ovn-controller |N/A We cannot do that, networking-ovn ml2 plugin does not know how many ovsdb servers are running, or how many ovn-northd servers, ... etc. It's transparent to it, it just talks to a VIP for the OVN NB or OVN SB databases. We introduced the agent RFE to at least show the ovn-controller items.
I'm closing it, but feel free to reopen if you believe that pcs status is not enough and that we should provide other means, but we can't list the items of the cluster in the agent list of neutron.
(In reply to Miguel Angel Ajo from comment #5) > I'm closing it, but feel free to reopen if you believe that pcs status is > not enough and that we should provide other means, but we can't list the > items of the cluster in the agent list of neutron. It should be fix as part of RFE :[RFE] [OVN] Implement the agents API "https://bugzilla.redhat.com/show_bug.cgi?id=1495692
*** This bug has been marked as a duplicate of bug 1495692 ***