= OpenShift Ansible AWS Provisioner This repository contains various Ansible playbooks, templates, and other support files used to provision OpenShift environments onto AWS.
== Prerequisites
There are several prerequisites for using this repository, scripted and detailed instructions for usage are available in the following the link:./Preparing_your_workstation.adoc[Preparing Your Workstation] document. [estimated effort 5-10 minutes]
== Standard Configurations
NOTE: Until we implement using Ansible Vault, each "Config" has two vars files
_vars
and _secret_vars
. The example_secret_vars
file shows the format for
what to put in your CONFIGNAME_secret_vars
file.
== Running the Ansible Playbooks
Once you have installed your prerequisites and have configured all settings and files, simply run Ansible like so:
ansible-playbook -i 127.0.0.1 ansible/main.yml -e "config_name=config-name" -e "aws_region=ap-southeast-2" -e "guid=youruniqueidentifier"
NOTE: Be sure to exchange guid
for a sensible prefix of your choosing.
For "opentlc-shared" standard config, check out the link:./configs/standard_configs/opentlc-shared/README.adoc[README] file
== Cleanup
S3 Bucket
An S3 bucket is used to back the Docker registry. AWS will not let you delete a
non-empty S3 bucket, so you must do this manually. The aws
CLI makes this
easy:
Your bucket name is named {{ config_name }}-{{ guid }}
. So, in the case of a
bu-workshop
environment where you provided the guid
of "Atlanta", your S3
bucket is called bu-workshop-atlanta
.
CloudFormation Template
Just go into your AWS account to the CloudFormation section in the region where you provisioned, find the deployed stack, and delete it.
SSH config
This Ansible script places entries into your ~/.ssh/config
. It is recommended
that you remove them once you are done with your environment.
== Troubleshooting
Information will be added here as problems are solved. So far it's pretty vanilla, but quite slow. Expect at least an hour for deployment, if not two or more if you are far from the system(s).
=== EC2 instability It has been seen that, on occasion, EC2 is generally unstable. This manifests in various ways:
The autoscaling group for the nodes takes an extremely long time to deploy, or will never complete deploying
Individual EC2 instances may have terrible performance, which can result in nodes that seem to be "hung" despite being reachable via SSH.
There is not much that can be done in this circumstance besides starting over (in a different region).
=== Re-Running While Ansible is idempotent and supports being re-run, there are some known issues with doing so. Specifically:
You should skip the tag nfs_tasks
with the --skip-tags
option if you
re-run the playbook after the NFS server has been provisioned and
configured. The playbook is not safe for re-run and will fail.
You may also wish to skip the tag bastion_proxy_config
when re-running, as
the tasks associated with this play will re-write the same entries to your SSH
config file, which could result in hosts becoming unexpectedly unreachable.