Appendix B. Deploying a vSphere VM Environment (Optional)

Note

The follow deployment steps are not supported by Red Hat and are provided as additional assistance.

# yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
# yum install -y python2-pyvmomi
$ git clone -b vmw-3.11 https://github.com/openshift/openshift-ansible-contrib
$ cd openshift-ansible-contrib/reference-architecture/vmware-ansible/

Verify that the inventory file has the appropriate variables including IPv4 addresses for the virtual machines in question and logins for the Red Hat Subscription Network. All of the appropriate nodes should be listed in the proper groups: masters, infras, apps.

Note

The VMware template should be specified in the ansible inventory file. This template should be a RHEL7 based template with 3 hard disks: 60GB, 40GB and 40GB. The ansible playbooks will customize the VM according to the requirements.

$ cat /etc/ansible/hosts | egrep 'rhsub|ip'
rhsub_user=rhn_username
rhsub_pass=rhn_password
rhsub_pool=8a85f9815e9b371b015e9b501d081d4b
infra-0 vm_name=infra-0 ipv4addr=10.x.y.8
infra-1 vm_name=infra-1 ipv4addr=10.x.y.9
...omitted...
$ ansible-playbook playbooks/provision.yaml

If an HAproxy instance is required it can also be deployed.

$ ansible-playbook playbooks/haproxy.yaml

This will provide the necessary nodes to fulfill Section 2.10, “vSphere VM Instance Requirements for RHOCP”