diff options
author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2017-12-08 15:49:41 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-12-08 15:49:41 -0800 |
commit | 54fe1e38764332634181cc7bdc0d0e7692304f91 (patch) | |
tree | adae4f2b0e6bf75a63175a2371470789c22f0df0 /inventory/byo/hosts.byo.glusterfs.external.example | |
parent | c0f7152a51c6306340f9634f191e81d4322d1b52 (diff) | |
parent | 2bf65cdab4aa88f160d005d3b7649b22a6dceba8 (diff) | |
download | openshift-54fe1e38764332634181cc7bdc0d0e7692304f91.tar.gz openshift-54fe1e38764332634181cc7bdc0d0e7692304f91.tar.bz2 openshift-54fe1e38764332634181cc7bdc0d0e7692304f91.tar.xz openshift-54fe1e38764332634181cc7bdc0d0e7692304f91.zip |
Merge pull request #6399 from mtnbikenc/cleanup-byo-refs
Automatic merge from submit-queue.
Cleanup byo references
* Remove playbooks/byo/config.yml, replaced by playbooks/deploy_cluster.yml
* Update example inventories
* Update doc references to 'byo' paths
Diffstat (limited to 'inventory/byo/hosts.byo.glusterfs.external.example')
-rw-r--r-- | inventory/byo/hosts.byo.glusterfs.external.example | 60 |
1 files changed, 0 insertions, 60 deletions
diff --git a/inventory/byo/hosts.byo.glusterfs.external.example b/inventory/byo/hosts.byo.glusterfs.external.example deleted file mode 100644 index acf68266e..000000000 --- a/inventory/byo/hosts.byo.glusterfs.external.example +++ /dev/null @@ -1,60 +0,0 @@ -# This is an example of a bring your own (byo) host inventory for a cluster -# with natively hosted, containerized GlusterFS storage. -# -# This inventory may be used with the byo/config.yml playbook to deploy a new -# cluster with GlusterFS storage, which will use that storage to create a -# volume that will provide backend storage for a hosted Docker registry. -# -# This inventory may also be used with byo/openshift-glusterfs/config.yml to -# deploy GlusterFS storage on an existing cluster. With this playbook, the -# registry backend volume will be created but the administrator must then -# either deploy a hosted registry or change an existing hosted registry to use -# that volume. -# -# 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 -# Specify that we want to use an external GlusterFS cluster -openshift_storage_glusterfs_is_native=False -# Specify the IP address or hostname of the external heketi service -openshift_storage_glusterfs_heketi_url=172.0.0.1 - -[masters] -master - -[nodes] -master openshift_schedulable=False -node0 openshift_schedulable=True -node1 openshift_schedulable=True -node2 openshift_schedulable=True - -[etcd] -master - -# Specify the glusterfs group, which contains the nodes of the external -# GlusterFS cluster. At a minimum, each node must have "glusterfs_hostname" -# and "glusterfs_devices" variables defined. -# -# The first variable indicates the hostname of the external GLusterFS node, -# and must be reachable by the external heketi service. -# -# The second variable is a list of block devices the node will have access to -# that are 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.local glusterfs_ip='172.0.0.10' glusterfs_devices='[ "/dev/vdb" ]' -node1.local glusterfs_ip='172.0.0.11' glusterfs_devices='[ "/dev/vdb", "/dev/vdc" ]' -node2.local glusterfs_ip='172.0.0.11' glusterfs_devices='[ "/dev/vdd" ]' |