[Docs] Wrong output

[Denis Klepikov]

https://docs.mirantis.com/openstack/fuel/fuel-master/monitoring-guide.html#ha-cluster

state on each of the cluster nodes when HA is handled in active/active mode. You can make that verification with the crm status command as shown below:

# crm status
......

Should be:

# crm status
============
Last updated: Tue Jun 23 08:47:23 2015
Last change: Mon Jun 22 17:24:32 2015
Stack: corosync
Current DC: node-1.domain.tld (1) - partition with quorum
Version: 1.1.12-561c4cf
3 Nodes configured
43 Resources configured
============

Online: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]

Clone Set: clone_p_vrouter [p_vrouter]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
vip__management (ocf::fuel:ns_IPaddr2): Started node-1.domain.tld
vip__public_vrouter (ocf::fuel:ns_IPaddr2): Started node-1.domain.tld
vip__management_vrouter (ocf::fuel:ns_IPaddr2): Started node-1.domain.tld
vip__public (ocf::fuel:ns_IPaddr2): Started node-2.domain.tld
Master/Slave Set: master_p_conntrackd [p_conntrackd]
    Masters: [ node-1.domain.tld ]
    Slaves: [ node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_haproxy [p_haproxy]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_dns [p_dns]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_mysql [p_mysql]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Master/Slave Set: master_p_rabbitmq-server [p_rabbitmq-server]
    Masters: [ node-1.domain.tld ]
    Slaves: [ node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_heat-engine [p_heat-engine]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_neutron-plugin-openvswitch-agent [p_neutron-plugin-openvswitch-agent]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_neutron-dhcp-agent [p_neutron-dhcp-agent]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_neutron-metadata-agent [p_neutron-metadata-agent]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_neutron-l3-agent [p_neutron-l3-agent]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_p_ntp [p_ntp]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]
Clone Set: clone_ping_vip__public [ping_vip__public]
    Started: [ node-1.domain.tld node-2.domain.tld node-3.domain.tld ]

Here, the crm status command provides an easy method to inform the monitoring system that the HA cluster is comprised of three controller nodes (node-10, node-6, and node-7), and that node-10 is the actual master node. It also tells the monitoring system that the VIPs for the public and management interfaces are started on the master node and that the HAProxy is started on all the nodes of the HA cluster.

The crm_resource command can also be used to verify on which node a particular resource is active. Execution of the command below, for example, tells the monitoring system that the Neutron DHCP agent is active on node-10:

# crm_resource --locate --quiet --resource p_neutron-dhcp-agent
node-10
Use the --resource vip_public option to find out on which node the public VIP is active:

# crm_resource --locate --quiet --resource vip__public
node-10

Should be

Here, the crm status command provides an easy method to inform the monitoring system that the HA cluster is comprised of three controller nodes (node-1, node-2, and node-3), and that node-1 is the actual master node. It also tells the monitoring system that the VIPs for the public and management interfaces are started on the master node and that the HAProxy is started on all the nodes of the HA cluster.

The crm_resource command can also be used to verify on which node a particular resource is active. Execution of the command below, for example, tells the monitoring system that the Neutron DHCP agent is active on node-1:

# crm_resource --locate --quiet --resource p_neutron-dhcp-agent
node-1
Use the --resource vip_public option to find out on which node the public VIP is active:

# crm_resource --locate --quiet --resource vip__public
node-1

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/199981

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/199981
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=062c9b8020d5c8e05d59b306d89f9c22080b0d20
Submitter: Jenkins
Branch: master

commit 062c9b8020d5c8e05d59b306d89f9c22080b0d20
Author: Olena Logvinova <email address hidden>
Date: Thu Jul 9 12:35:50 2015 +0300

    Changes the output format in crm commands

    This patch:
    - separates the examples of output from the commands;
    - changes node-10, node-6, and node-7 to node-1, node-2, and node-3
      + changes the commands accordingly.

    Change-Id: I1584220caea366ffb629ff46d4b10e8b4ddba9de
    Closes-Bug: #1471274