Ce contenu n'est pas disponible dans la langue sélectionnée.
Appendix B. Understanding the gluster_volume_inventory.yml file
The gluster_volume_inventory.yml inventory file is an example file that you can use to create logical volume from the existing volume group if free space is available.
You can create this file at /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/gluster_volume_inventory.yml
B.1. Configuration parameters for creating logical volumes
- hosts
Backend network FQDN of the hyperconverged hosts. Mention the same set of host names under
cluster_nodessection.hosts: <host1-backend-FQDN>: <host2-backend-FQDN>: <host3-backend-FQDN>:
- vgname
- The name of the existing volume group (VG) on the host.
- gluster_infra_disktype
Disk Aggregation Type. Values taken:
- RAID6
- RAID5
- JBOD
- gluster_infra_diskcount
- Number of data disks in the RAID set. For JBOD the value is 1.
- gluster_infra_stripe_unit_size
- RAID stripe size. Ignore this parameter for JBOD.
Example gluster_volume_inventory file
hc_nodes:
hosts:
host1-backend.example.com:
host2-backend.example.com:
host3-backend.example.com:
# Common configurations
vars:
gluster_infra_volume_groups:
- vgname: gluster_vg_sdb
pvname: /dev/sdb
gluster_infra_mount_devices:
- path: /gluster_bricks/newengine
lvname: gluster_lv_newengine
vgname: gluster_vg_sdb
gluster_infra_thick_lvs:
- vgname: gluster_vg_sdb
lvname: gluster_lv_newengine
size: 100G
gluster_infra_disktype: RAID6
gluster_infra_diskcount: 10
gluster_infra_stripe_unit_size: 256
gluster_features_force_varlogsizecheck: false
gluster_set_selinux_labels: true
cluster_nodes:
- host1-backend.example.com
- host2-backend.example.com
- host3-backend.example.com
gluster_features_hci_cluster: "{{ cluster_nodes }}"
gluster_features_hci_volumes:
- volname: newengine
brick: /gluster_bricks/newengine/newengine
arbiter: 0
