Three Tier App config whilst intended for the deployment of a three tier app is perhaps better described as "5 unconfigured RHEL machines all exposed to the internet".
It is worth noting, despite its name, that no application is actuall deployed.
It makes an ideal base infrastructure to build on and can easily be extended via it’s env_vars.yml
to less or more machines and also to different operating system images.
-
This file ./env_vars.yml contains all the variables you need to define to control the deployment of your environment.
You can run the playbook with the following arguments to overwrite the default variable values:
REGION=ap-southeast-2
KEYNAME=ocpkey
GUID=praktest2
ENVTYPE="three-tier-app"
CLOUDPROVIDER=ec2
HOSTZONEID='Z3IHLWJZOU9SRT'
BASESUFFIX='.example.opentlc.com'
ansible-playbook \
ansible/main.yml \
-e "guid=${GUID}" \
-e "env_type=${ENVTYPE}" \
-e "key_name=${KEYNAME}" \
-e "subdomain_base_suffix=${BASESUFFIX}" \
-e "cloud_provider=${CLOUDPROVIDER}" \
-e "aws_region=${REGION}" \
-e "HostedZoneId=${HOSTZONEID}" \
-e "[email protected]" \
-e "output_dir=/opt/workdir" \
-e@../secret.yml -vv
REGION=ap-southeast-2 KEYNAME=ocpkey GUID=praktest1 ENVTYPE="three-tier-app" CLOUDPROVIDER=ec2 ansible-playbook ./ansible/configs/${ENVTYPE}/destroy_env.yml \ -e "guid=${GUID}" -e "env_type=${ENVTYPE}" -e "cloud_provider=${CLOUDPROVIDER}" -e "aws_region=${REGION}" \ -e "key_name=${KEYNAME}" -e "subdomain_base_suffix=${BASESUFFIX}" -e@../secret.yml -vv