From 2bf65cdab4aa88f160d005d3b7649b22a6dceba8 Mon Sep 17 00:00:00 2001 From: Russell Teague Date: Fri, 8 Dec 2017 08:42:32 -0500 Subject: Cleanup byo references --- inventory/byo/hosts.byo.glusterfs.mixed.example | 63 ------------------------- 1 file changed, 63 deletions(-) delete mode 100644 inventory/byo/hosts.byo.glusterfs.mixed.example (limited to 'inventory/byo/hosts.byo.glusterfs.mixed.example') diff --git a/inventory/byo/hosts.byo.glusterfs.mixed.example b/inventory/byo/hosts.byo.glusterfs.mixed.example deleted file mode 100644 index a559dc377..000000000 --- a/inventory/byo/hosts.byo.glusterfs.mixed.example +++ /dev/null @@ -1,63 +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 and a native -# heketi service -openshift_storage_glusterfs_is_native=False -openshift_storage_glusterfs_heketi_is_native=True -# Specify that heketi will use SSH to communicate to the GlusterFS nodes and -# the private key file it will use for authentication -openshift_storage_glusterfs_heketi_executor=ssh -openshift_storage_glusterfs_heketi_ssh_keyfile=/root/id_rsa -[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" ]' -- cgit v1.2.3