Apigee OPDK Ansible Setup Playbook

The purpose of this project is to help configure Ansible for the use of Apigee OPDK roles. The Apigee OPDK roles follow conventions in the naming of files and where those files are located. This project sets up those locations and performs the git clone to setup your environment with the templates that should be customized for your use.

Usage: Minimum Setup

Set up your a workspace at ~/apigee-workspace/ if you already have git and pip installed:

ansible-playbook setup-base.yml 

Requirements

• Ansible 2.1 or greater
• Linux control server version 6 or greater
• Access to github.com
• Git
• Pip

Overview: Minimum Setup

This playbook will perform the following activities:

1. Scaffold required folders

2. Git clone of Ansible configuration file templates

3. Git clone of inventory file templates. [Updating your Inventory File] (inventory.md)

4. Create credentials.yml template file

System Packages

Required system packages can be installed with

ansible-playbook install-system-packages.yml -K

Default Workspace Folders

The default workspace folders can be modified by updating workspace-folders.yml.

Default Github Repository List

The github repositories that you include can be modified by updating workspace-github-repos.yml

Inventory Semantics

A full description of inventory semantics.

Scaffold required folders

This playbook will create the following folders for you:

~/.ansible/configurations

Sample configuration templates for single and multi-dc planets

~/.ansible/inventory

Sample configuration inventory template files that model the required group semantics used.

~/.apigee

Folder to contain credentials, downloaded logs, configs and maintain the edge license.txt file.

~/apigee-workspace/apigee-opdk-playbook-workspace

Starter templates for playbooks. Use these playbooks as accelerators for your own.

~/apigee-workspace/apigee-odk-role-workspace

Workspace containing the roles used by the playbooks.

Overview: EC2 Managed Setup

The minimum setup must be completed prior to configuring the EC2 managed setup. The EC2 managed setup will update perform the following activities:

• Update ~/.bashrc to export AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY values you provide.
• Update ~/.bashrc to export EC2_INI_PATH.
• Create a template .boto file and place it your home directory
• Create a template ec2.ini and place it in your ~/.ansible folders
• Provide a copy of the ec2.py script that must be included with any AWS managed inventory file.

Usage: Setup for EC2 Managed Images

Please follow the usage instructions:

ansible-playbook setup-ec2.yml \
    -e secure_aws_region={{ secure_aws_region }} \
    -e aws_access_key_id={{ aws_access_key_id }} \
    -e aws_secret_access_key={{ aws_secret_access_key }}

Variables Used

Variable Name	Description
secure_aws_region	Please provide your ec2_region.
aws_access_key_id	Please provide your AWS Access Key ID.
aws_secret_access_key	Please provide your AWS Secret Access Key.