Bug 1483842
| Summary: | [RFE]- OVN adding an option to see cluster status from single point | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eran Kuris <ekuris> |
| Component: | openstack-neutron | Assignee: | Assaf Muller <amuller> |
| Status: | CLOSED DUPLICATE | QA Contact: | Eran Kuris <ekuris> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 12.0 (Pike) | CC: | amuller, chrisw, ekuris, majopela, nyechiel, oblaut, srevivo |
| Target Milestone: | --- | Keywords: | FutureFeature, UserExperience |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-08 14:25:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eran Kuris
2017-08-22 06:20:47 UTC
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 *** |