Infrastructure provisioning on AWS with Ansible within your Shippable pipeline

A Shippable pipeline for provisioning and terminating Tomcat servers on Amazon EC/2 using Ansible.

This repo demonstrates the following features:

• Set up a CD pipeline to provision and terminate Amazon EC/2 instances
• Use of Ansible to install and configure software (Apache Tomcat) in a Shippable pipeline
• Use of runSh jobs in a Shippable pipeline
• Use of the PEM Key Account Integration in a Shippable pipeline job
• Dynamically determine EC/2 instances to take action on from within a pipeline job

Prerequisites to run this sample

• Source control account (e.g. GitHub, Bitbucket, Gitlab)
• Shippable account (sign up for free at www.shippable.com)
• Amazon Web Services account (aws.amazon.com)

Setup

• Fork this repo to your source control account
• Follow the [instructions](insert link) to store your AWS credentials needed for this sample in Shippable
• All pipeline config is in shippable.resources.yml and shippable.jobs.yml. Check these files and update config wherever the comment asks you to replace with your specific values (for example, to replace with your Integration names)
• Specifications for the instances that will be launched in AWS can be found in group_vars/tomcat-servers.yml. Update these, as appropriate.
• Add the pipeline to your SPOG view in Shippable:
  • Select your subscription from the dropdown menu in upper left (three horizontal lines)
  • Select the Pipelines tab
  • Select the "+" icon in the upper right
  • Select the source control repo where your fork is
• Since the mirror for Apache Tomcat changes frequently, verify the latest one on the Apache Download page and update the $TOMCAT_MIRROR value in the ansible-ec2-tomcat-provision.yml file.

Run the pipeline

• Right-click on the runSh job in the SPOG view named 'shipdemo-provision-aws-ansible' and run the job
  • This demo uses a custom scripting job type called 'runSh' in Shippable - learn more about 'runSh' jobs
• When your job completes, you should see new EC/2 instances running Apache Tomcat in your AWS account
• Make a change to the number of instances in the group_vars/tomcat-servers.yml file and push the change to your source control
  • The job will automatically run and update the number of instances in EC/2
• Right-click on the runSh job named 'shipdemo-terminate-aws-ansible' and run the job
• When the job completes, you should now see all of the instances terminated in EC/2

With this approach, your entire team can easily manage infrastructure provisioning as a dedicated pipeline or incorporate on-demand provisioning as a step in an end-to-end testing scenario.

Additional notes:

• This sample uses dynamic inventory. You can also use static inventory by updating the inventory/static_hosts file. To turn off dynamic inventory, comment out the config in inventory/base.

AWS integration

runSh console

CD pipeline screenshot