Bug 1835574 - Automate creation of gluster logical network
Summary: Automate creation of gluster logical network
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 2
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1832966
TreeView+ depends on / blocked
 
Reported: 2020-05-14 05:17 UTC by SATHEESARAN
Modified: 2020-06-16 05:57 UTC (History)
7 users (show)

Fixed In Version: gluster-ansible-roles-1.0.5-12.el8rhgs
Doc Type: Enhancement
Doc Text:
Previously, after RHHI deployment, Gluster network was created manually through RHV-M User Interface.With this release, Ansible playbook creates a Gluster logical network so you don't need to create it manually
Clone Of: 1832966
Environment:
Last Closed: 2020-06-16 05:57:32 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2575 0 None None None 2020-06-16 05:57:50 UTC

Description SATHEESARAN 2020-05-14 05:17:52 UTC
Description of problem:
-----------------------
Creation of RHV logical network for gluster traffic is not automated and it stops with adding the additional hosts to the cluster.

In addition to adding the additional hosts to the cluster, there should also be a automated task that creates the gluster logical network and attach that network to all the hosts, to the network interface connected to gluster network

Only when there are dedicated networks for Storage and ovrtmgmt ( Remember cockpit plugin has a option to use the same network for both storage and public network), the following task should get kicked in.

1. Create a logical network with following properties:
           - Non VM network
           - VM Migration roles
           - Gluster role
           - Not required
           - Attached to 'Default' data center and 'Default' cluster

2. On all the hosts, attach this logical network to interface that's used for gluster network

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHHI-V 1.8

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Complete RHHI-V deployment from web console ( cockpit )

Actual results:
---------------
Logical network for gluster traffic is not created, and users had to create it manually

Expected results:
-----------------
Logical network for gluster traffic should be created automatically and attached to the corresponding network interface used for gluster traffic on all the hosts

--- Additional comment from RHEL Program Management on 2020-05-07 14:29:32 UTC ---

This bug is automatically being proposed for RHHI-V 1.8 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.8' to '?'.

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 3 Gobinda Das 2020-05-26 11:33:55 UTC
PR: https://github.com/gluster/gluster-ansible/pull/109

Comment 6 SATHEESARAN 2020-06-06 11:30:16 UTC
Verified with gluster-ansible-roles-1.0.5-12.el8rhgs

1. The playbook and inventory to create the gluster network is available
[root@ ~]# ls /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/gluster_network_inventory.yml
/etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/gluster_network_inventory.yml

[root@ ~]# ls /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_network_setup.yml 
/etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_network_setup.yml

2. Run the playbook post RHHI-V deployment
3. New logical network is created and attached to all the hosts

Comment 8 Gobinda Das 2020-06-11 12:30:18 UTC
RDT looks good to me.

Comment 10 errata-xmlrpc 2020-06-16 05:57:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:2575


Note You need to log in before you can comment on or make changes to this bug.