| 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950 |
- # This is an example of a bring your own (byo) host inventory for a cluster
- # with natively hosted, containerized GlusterFS storage for applications. It
- # will also autmatically create a StorageClass for this purpose.
- #
- # This inventory may be used with the byo/config.yml playbook to deploy a new
- # cluster with GlusterFS storage.
- #
- # This inventory may also be used with byo/openshift-glusterfs/config.yml to
- # deploy GlusterFS storage on an existing cluster.
- #
- # There are additional configuration parameters that can be specified to
- # control the deployment and state of a GlusterFS cluster. Please see the
- # documentation in playbooks/byo/openshift-glusterfs/README.md and
- # roles/openshift_storage_glusterfs/README.md for additional details.
- [OSEv3:children]
- masters
- nodes
- etcd
- # Specify there will be GlusterFS nodes
- glusterfs
- [OSEv3:vars]
- ansible_ssh_user=root
- openshift_deployment_type=origin
- [masters]
- master
- [nodes]
- master openshift_schedulable=False
- # A hosted registry, by default, will only be deployed on nodes labeled
- # "region=infra".
- node0 openshift_schedulable=True
- node1 openshift_schedulable=True
- node2 openshift_schedulable=True
- [etcd]
- master
- # Specify the glusterfs group, which contains the nodes that will host
- # GlusterFS storage pods. At a minimum, each node must have a
- # "glusterfs_devices" variable defined. This variable is a list of block
- # devices the node will have access to that is intended solely for use as
- # GlusterFS storage. These block devices must be bare (e.g. have no data, not
- # be marked as LVM PVs), and will be formatted.
- [glusterfs]
- node0 glusterfs_devices='[ "/dev/vdb", "/dev/vdc", "/dev/vdd" ]'
- node1 glusterfs_devices='[ "/dev/vdb", "/dev/vdc", "/dev/vdd" ]'
- node2 glusterfs_devices='[ "/dev/vdb", "/dev/vdc", "/dev/vdd" ]'
|
