summaryrefslogtreecommitdiffstats
path: root/inventory/byo/hosts.byo.glusterfs.registry-only.example
diff options
context:
space:
mode:
authorRussell Teague <rteague@redhat.com>2017-12-08 08:42:32 -0500
committerRussell Teague <rteague@redhat.com>2017-12-08 15:55:25 -0500
commit2bf65cdab4aa88f160d005d3b7649b22a6dceba8 (patch)
treeadae4f2b0e6bf75a63175a2371470789c22f0df0 /inventory/byo/hosts.byo.glusterfs.registry-only.example
parentc0f7152a51c6306340f9634f191e81d4322d1b52 (diff)
downloadopenshift-2bf65cdab4aa88f160d005d3b7649b22a6dceba8.tar.gz
openshift-2bf65cdab4aa88f160d005d3b7649b22a6dceba8.tar.bz2
openshift-2bf65cdab4aa88f160d005d3b7649b22a6dceba8.tar.xz
openshift-2bf65cdab4aa88f160d005d3b7649b22a6dceba8.zip
Cleanup byo references
Diffstat (limited to 'inventory/byo/hosts.byo.glusterfs.registry-only.example')
-rw-r--r--inventory/byo/hosts.byo.glusterfs.registry-only.example56
1 files changed, 0 insertions, 56 deletions
diff --git a/inventory/byo/hosts.byo.glusterfs.registry-only.example b/inventory/byo/hosts.byo.glusterfs.registry-only.example
deleted file mode 100644
index 32040f593..000000000
--- a/inventory/byo/hosts.byo.glusterfs.registry-only.example
+++ /dev/null
@@ -1,56 +0,0 @@
-# This is an example of a bring your own (byo) host inventory for a cluster
-# with natively hosted, containerized GlusterFS storage for exclusive use
-# as storage for a natively hosted Docker registry.
-#
-# 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/registry.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_registry
-
-[OSEv3:vars]
-ansible_ssh_user=root
-openshift_deployment_type=origin
-# Specify that we want to use GlusterFS storage for a hosted registry
-openshift_hosted_registry_storage_kind=glusterfs
-
-[masters]
-master
-
-[nodes]
-master openshift_schedulable=False
-# A hosted registry, by default, will only be deployed on nodes labeled
-# "region=infra".
-node0 openshift_node_labels="{'region': 'infra'}" openshift_schedulable=True
-node1 openshift_node_labels="{'region': 'infra'}" openshift_schedulable=True
-node2 openshift_node_labels="{'region': 'infra'}" 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_registry]
-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" ]'