Chapter 12. Configure the logical network for gluster traffic For creating a separate gluster logical network, in Red Hat Hyperconverged Infrastructure for Virtualization (RHHI for Virtualization) 1.7 users had to perform the steps manually via the Red Hat Virtualization Administration portal. From RHHI for Virtualization 1.8 this process can be automated using the ansible playbook as follows: 12.1. Defining the logical network details for gluster traffic Prerequisites Red Hat Hyperconverged Infrastructure for Virtualization deployment is complete with hosts in up state. Procedure Log in to the first hyperconverged host. Change into the hc-ansible-deployment directory: Make a copy of the gluster_network_inventory.yml file for future reference. Define your configuration in the gluster_network_inventory.yml file. Use the example gluster_network_inventory.yml file to define the details on each host. A complete outline of this file is available in Understanding the gluster_network_inventory.yml file . Encrypt the gluster_network_inventory.yml file and specify a password using ansible-vault . The required variables in gluster_network_inventory.yml include password values, so it is important to encrypt the file to protect the password values. Enter and confirm a new vault password when prompted. 12.2. Executing the gluster network playbook Prerequisites Define configuration in the gluster_network_inventory.yml playbook: Section 12.1, "Defining the logical network details for gluster traffic" . Procedure Log in to the first hyperconverged host. Change into the hc-ansible-deployment directory. Run the following command as the root user to start the configuration process. Enter the vault password for this file when prompted to start network configuration. 12.3. Verifying the logical network for gluster traffic Check the following to verify if the logical network for gluster traffic is successfully created and attached to the host. Validate the availability of gluster logical network. Log in to the Administration Portal. Click Network Networks . This should list the newly created gluster_net network. Click on gluster_net click on Clusters tab, hovering the mouse over Network Role column should display Migration Gluster . Validate gluster_net is attached to the storage network interface of all the hosts. Click on Compute Hosts click on any host. Select Network Interfaces tab click on the drop down button near the label Logical Networks corresponding to storage or backend network, you should see the gluster_net as the network name. 12.4. (Optional) Editing the logical network for Jumbo frames If you have Jumbo frames (MTU 9000) enabled, you need to edit the default network configuration to ensure jumbo frames are used for storage traffic. The network components (switch) must support Jumbo frames. The following is the procedure to edit the logical network for Jumbo frames on the storage network, gluster_net here: Prerequisites Logical network for gluster traffic is successfully created and is attached to the host. Procedure Login in to the Administration Portal. Click Networks Network . Click on gluster_net Edit . Select custom MTU and make it as 9000. Click OK . Note Make sure all the network components are enabled with the same MTU.

Commands:
cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment
cp gluster_network_inventory.yml gluster_network_inventory.yml.backup
ansible-vault encrypt gluster_network_inventory.yml
cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment
ansible-playbook -i gluster_network_inventory.yml tasks/gluster_network_setup.yml --ask-vault-pass