Ansible: Nine (9) Part Series for Familiarization

Do you want to learn about Ansible? Well, you've found the best place to start! This nine (9) part series will familiarize you with Ansible.

Article 1 creates a base environment for using Ansible in future articles in the series. It leverages AWS Cloud9, several AWS CLI for "aws ec2" for describing instances and provisioning SSH keys. The article ends with making sure your Cloud9 environment is up-to-date with Python, Pip, and Ansible.

Ansible 1 of 9: Environment Setup

Article 2 introduces you to the Ansible inventory and the Ansible ping module, pointing out how the Ansible ping module does more than just ping a host, it attempts to connect to the host also. You will also get introduced to the Ansible config file.

Ansible 2 of 9: Inventory/Ad-Hoc Configuration

Article 3 is all about Ansible modules. You will use several modules:
ping module to check if targets are up
command module to run commands against target hosts
apt module to install software on targets
shell module to run commands in a shell on targets
service module to interact with services on targets
copy module to copy files to targets
file module to manipulate files on target (e.g.: delete)

Ansible 3 of 9: Modules

Article 4 is more of a setup for the next article. It provisions the infrastructure via Terraform and validates connectivity to targets via Ansible ping. Suffice to say, playbooks are repeatable recipes that can be run against your infrastructure.

Ansible 4 of 9: Playbooks 1 of 2

Article 5 is about using an Ansible Plabyook. You will dp several things:
manually install nginx test the application uninstall nginx install nginx using the Ansible playbook At the end of this article, you will destroy the infrastructure you created in Article 4.

Ansible 5 of 9: Playbooks 2 of 2

Article 6 is about Ansible Variables. Use variables to store and reference values that can be used throughout playbooks, templates, and other Ansible configuration files. Variables can be used against a single host or a group of hosts.

Ansible 6 of 9: Variables

Article 7 is about Ansible Conditionals. You can use conditionals to control the execution of playbooks based on specific conditions or values. For example, you can do certain steps depending upon the target operating system

Ansible 7 of 9: Conditionals

Article 8 is about Ansible Loops. The looping techniques used are "with_items" and the "loop" directive.

Ansible 8 of 9: Loops

Article 9 is about Ansible Roles. Roles permit you to do a series of operations against infrastructure, simply due to classification into certain "roles". You can load variables, files, tasks, handlers, etc., all based on a known file structure.

Ansible 9 of 9: Roles

Comments

Post a Comment

Popular posts from this blog

Orphaned No More: Adopting AWS Lambda

Image
Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture is fully automated on AWS. The architecture is not ready for go-live. All actions so far are for a proof-of-concept that is presented to the Chief Technical Officer (CTO) for review. During the weekly team meeting, Ko (User Experience Lead) reports that his team has performed thousands of tests against the infrastructure, with moves, adds, and changes, and is not finding any issues in the application user interface. Woo (Infrastructure Lead) reports that there are hundreds of 'orphaned' files in the S3 bucket. (These files are considered 'orphaned' because they do not have corresponding records in the DynamoDB table.) Kim (Tech Lead) reports that there is not a trigger to delete the file from the bucket when a user is deleted from the DynamoDB database. Brady (Lawyer) reports that not deleting t
Read more

Containing the Chaos! | A Three-Part Series Demonstrating the Usefulness of Containerization to HumanGov

Background HumanGov is a Model Automated Multi-Tenant Architecture (MAMA) that is meant to be used by the 50 states for personnel tracking. Currently the architecture requires Amazon Elastic Compute Cloud (EC2) instances that are maintained by the HumanGov systems administrators. The systems administrators handle all the patching, operations, etc. Due to states wanting their data separate from each other, each state gets a separate set of EC2 instances, which means that as the application scales from one state up to 50 states, the systems administrators will have to patch 50x as many EC2 instances. The system administrators report that they have begun to schedule more and more overtime to handle the maintenance windows for updating the EC2 instances. The lead developer remarked that it was taking longer and longer for new application deployments to get rolled out as the infrastructure grew and more states came on board. By the way, the development environment does not have standa
Read more

Ansible is the Answer! | A Three-Part Series Demonstrating the Usefulness of Ansible to HumanGov

This is a three (3) part series that demonstrates how Ansible can be useful/leveraged for configuring your infrastructure. The background story here is that HumanGov is a multi-tenant cloud application that requires that each of the fifty (50) states has its own separate infrastructure. The HumanGov Infrastructure Engineers are trying to figure out how they can get it done, and they are considering using Ansible to help them deploy the application. Part 1 sets up the base infrastructure for the scenario. The HumanGov Infrastructure Engineers are accustomed to using Terraform to efficiently deploy infrastructure, but they are not very experienced with Ansible. Part 1 of 3: HumanGov: Ansible is the Answer! | Terraform | AWS Cloud9 | AWS IAM | AWS EC2 | AWS DynamoDB | AWS S3 Part 2 attempts to setup HumanGov via a MANUAL process. Part 2 goes through the steps to MANUALLY install Python, Nginx AND application files as well as MANUALLY configuring the firewall in Ubuntu. After g
Read more