This repository shows how to create a CP-Ansible Job Template within Ansible Tower. Ansible Tower acts as an automation server for deploying Confluent Platform on AWS Infrastructure.
- Docker
- Docker Compose
- Terraform
- An AWS VPC with
Enabled DNS hostnamesset to true, preferably inus-west-2 - An AWS Subnet in the above VPC
Fork this repo. Your fork will serve as a repo containing your Infrastructure-as-Code.
Set the REPO_URL environment variable and clone your fork. Use HTTPS (not SSH) because Tower uses this URL.
export REPO_URL=https://github.com/<fork>/demo-scene
git clone $REPO_URL
Set environment variables:
export AWS_ACCESS_KEY_ID="key"
export AWS_SECRET_ACCESS_KEY="secret"
export TF_VAR_vpc_id=vpc-xxxx
export TF_VAR_subnet=subnet-xxxx
If your AWS Subnet is outside of us-west-2, set the below AMI variable to a CentOS image within your region:
export TF_VAR_ami=ami-xxxx
If running this demo in the same subnet as someone else in your organization, to avoid naming collisions set
export TF_VAR_unique_identifier=<your-name>
export TF_VAR_ssh_key_pair=<your-name>-key
Provision AWS infrastructure:
make create-infra
Commit the updated inventory file, and push to your fork:
git add terraform/hosts.yml
git commit -m 'Provisioned infrastructure and updated inventory file.'
git push origin master
Stand up Ansible Tower:
make start-tower
Create CP-Ansible Job
make create-tower-job
Go to http://localhost:8052 in your browser and login with credentials admin / password:
Under Templates you can launch Deploy on AWS
When the Job completes, Confluent Platform is deployed! Find the ansible_host of the Control Center host in terraform/hosts.yml and go to https://<ansible_host>:9021 in your browser.
Tear down Ansible Tower:
make stop-tower
Note: This step stops the containers, but does not delete any tower objects. To delete everything delete the awx/pgdocker/12 directory.
Tear down AWS infrastructure:
make destroy-infra
You now have a successful Confluent Platform deployment automated with Ansible Tower.
In CP-Anisble 6.1.0 we have added Reconfiguration. This means you fully automate your deployments on any changes within Git. First, add Git Webhooks. Next, under the Deploy on AWS Job Template, add the tag "package" under the skip tags field. Now, any updates to your inventory in Git will trigger Ansible Tower to reconfigure your deployment in true GitOps fashion!
The terraform code that enables this blog is great for demos, but is not a production set up. The code should be refactored into Terraform Modules. Autoscaling groups should be added to each ec2 instance. Potentially user data scripts could configure each host on start up.