Bug 1871039

Summary:	Include MTU parameter is an input for gluster logical network creation using ansible
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gluster-ansible	Assignee:	Prajith <pkesavap>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	dwalveka, godas, pkesavap, pprakash, puebele, rhs-bugs, sabose, sasundar
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Async Update
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-roles-1.0.5-18	Doc Type:	Enhancement
Doc Text:	Previously, customers could not set a custom MTU value restricting them to use the default value of 1500. In this release, a new field mtu_value is introduced for the customers to set a different value than the default value of 1500.	Story Points:	---
Clone Of:	1871038	Environment:
Last Closed:	2020-11-24 12:37:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1871038, 1898431

Description SATHEESARAN 2020-08-21 08:16:55 UTC

Description of problem:
------------------------
Gluster logical network is created and attached to the hyperconverged hosts in an automated way using ansible. This procedure however lacks the ability to make use of JUMBO frames of MTU 9000. Ansible ovirt_network module[1] allows creating logical network with MTU. Now update the inventory to provide the flexibility to provide custom MTU, on demand. Default is 1500

[1] - https://docs.ansible.com/ansible/latest/modules/ovirt_network_module.html


Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHHI-V 1.8
gluster-ansible-roles-1.0.5-17.el8rhgs

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

Actual results:
----------------
No option available in inventory to create gluster logical network with custom MTU

Expected results:
-----------------
Update the playbook and inventory to include custom MTU

Comment 2 SATHEESARAN 2020-08-21 08:20:29 UTC

Proposing this bug gluster-ansible bug for RHGS 3.5.3.
This change provide the ability to automated deployment of gluster logical network,
which provides the ease of use for the customers that deploys RHHI-V 1.8

Comment 3 Prajith 2020-08-26 07:10:07 UTC

PR:-https://github.com/gluster/gluster-ansible/pull/119

Comment 5 Prajith 2020-08-27 14:44:09 UTC

you can find the build details here:-

Task Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=30986914
Build Info: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1299277

Comment 11 SATHEESARAN 2020-11-08 15:25:37 UTC

Tested with gluster-ansible-roles-1.0.5-22.el8rhgs

1. Edited the inventory file (/etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/gluster_network_inventory.yml) with param 'mtu_value' set to 9000
2. Executed the playbook and it created the gluster logical network with MTU set to 9000
3. Also repeated the test with no param 'mtu_value', in this case, the MTU for gluster logical network is set to 1500

Comment 17 errata-xmlrpc 2020-11-24 12:37:41 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 (gluster-ansible bug fix and enhancement update), 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/RHBA-2020:5220