Chapter 5. Creating new bricks and configuration

1. Verify host state in the Administrator Portal.

   1. Log in to the Red Hat Virtualization Administrator Portal.

      The host is listed as NonResponsive in the Administrator Portal. Virtual machines that previously ran on this host are in the Unknown state.

   2. Click Compute Hosts and click the Action menu (⋮).
   3. Click Confirm host has been rebooted and confirm the operation.
   4. Verify that the virtual machines are now listed with a state of Down.

2. Update the SSH fingerprint for the failed node.

   1. Log in to the Ansible controller node as the root user.

   2. Remove the existing SSH fingerprint for the failed node.

      # sed -i `/failed-host-frontend.example.com/d` /root/.ssh/known_hosts
      # sed -i `/failed-host-backend.example.com/d` /root/.ssh/known_hosts

      Copy to Clipboard Toggle word wrap

   3. Copy the public key from the Ansible controller node to the freshly installed node.

      # ssh-copy-id root@new-host-backend.example.com
      # ssh-copy-id root@new-host-frontend.example.com

      Copy to Clipboard Toggle word wrap

   4. Verify that you can log in to all hosts in the cluster, including the Ansible controller node, using key-based SSH authentication without a password. Test access using all network addresses. The following example assumes that the Ansible controller node is host1.

      # ssh root@host1-backend.example.com
      # ssh root@host1-frontend.example.com
      # ssh root@host2-backend.example.com
      # ssh root@host2-frontend.example.com
      # ssh root@new-host-backend.example.com
      # ssh root@new-host-frontend.example.com

      Copy to Clipboard Toggle word wrap

      Use ssh-copy-id to copy the public key to any host you cannot log into without a password using this method.

      # ssh-copy-id root@host-frontend.example.com
      # ssh-copy-id root@host-backend.example.com

      Copy to Clipboard Toggle word wrap

Procedure

1. Familiarize yourself with your Gluster configuration.

   The configuration that you define in your inventory file must match the existing Gluster volume configuration. Use gluster volume info to check where your bricks should be mounted for each Gluster volume, for example:

   # gluster volume info engine | grep -i brick
   Number of Bricks: 1 x 3 = 3
   Bricks:
   Brick1: host1.example.com:/gluster_bricks/engine/engine
   Brick2: host2.example.com:/gluster_bricks/engine/engine
   Brick3: host3.example.com:/gluster_bricks/engine/engine

   Copy to Clipboard Toggle word wrap

2. Back up the node_prep_inventory.yml file.

   # cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment
   # cp node_prep_inventory.yml node_prep_inventory.yml.bk

   Copy to Clipboard Toggle word wrap

3. Edit the node_prep_inventory.yml file to define your node preparation.

   See Appendix B, Understanding the node_prep_inventory.yml file for more information about this inventory file and its parameters.

Procedure

1. Back up the node_replace_inventory.yml file.

   # cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment
   # cp node_replace_inventory.yml node_replace_inventory.yml.bk

   Copy to Clipboard Toggle word wrap

2. Edit the node_replace_inventory.yml file to define your cluster.

   See Appendix C, Understanding the node_replace_inventory.yml file for more information about this inventory file and its parameters.

Procedure

1. Execute the playbook.

   # cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/
   # ansible-playbook -i node_prep_inventory.yml -i node_replace_inventory.yml tasks/replace_node.yml

   Copy to Clipboard Toggle word wrap

Procedure

1. Activate the host.

   1. Log in to the Red Hat Virtualization Administrator Portal.
   2. Click Compute Hosts and observe that the replacement host is listed with a state of Maintenance.
   3. Select the host and click Management Activate.
   4. Wait for the host to reach the Up state.

2. Attach the gluster network to the host.

   1. Click Compute Hosts and select the host.
   2. Click Network Interfaces Setup Host Networks.
   3. Drag and drop the newly created network to the correct interface.
   4. Ensure that the Verify connectivity between Host and Engine checkbox is checked.
   5. Ensure that the Save network configuration checkbox is checked.
   6. Click OK to save.

   7. Verify the health of the network.

      Click the Network Interfaces tab and check the state of the host’s network.

      If the network interface enters an "Out of sync" state or does not have an IP Address, click Management Refresh Capabilities.