Bug 1871038 - Include MTU parameter is an input for gluster logical network creation using ansible
Summary: Include MTU parameter is an input for gluster logical network creation using ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHHI-V 1.8.z Batch Update 2
Assignee: Prajith
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1871039
Blocks: 1898431
TreeView+ depends on / blocked
 
Reported: 2020-08-21 08:15 UTC by SATHEESARAN
Modified: 2020-12-01 06:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: A new field to provide Customized MTU as input Reason: mtu_value field is introduced, because if customer wants a different value apart from the default one (1500) . they could parse it Result: Customers can successfully set a custom MTU value.
Clone Of:
: 1871039 1898431 (view as bug list)
Environment:
Last Closed: 2020-12-01 06:58:20 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2020-08-21 08:15:24 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 Prajith 2020-08-26 07:09:38 UTC
Pr:- https://github.com/gluster/gluster-ansible/pull/119

Comment 3 SATHEESARAN 2020-11-08 15:16:11 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


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