Microservices Demo

Demo of Automated Microservices Infrastructure Setup using Ansible, Docker, Consul and the friends. Demo is tested and uses AWS cloud, but can be adapted for other clouds.

License

MIT

Installation

1. Install Ansible

   1. On OS-X you can just run: sudo -H pip install --ignore-installed ansible
   2. For other platforms consult with Ansible installation notes

2. Install docker-py:

   sudo -H pip install docker-py
   

3. Install jq (sed for JSON):

   1. On OS-X you can just run: brew install jq
   2. For other platforms consult with jq installation notes

4. Install and configure AWS CLI Tools

5. Install and configure Boto:

   1. Installation: http://boto.readthedocs.org/en/latest/getting_started.html

      On OS-X El Capitan, you will have to ignore six that is pre-installed and causes issues:

      sudo -H pip install --ignore-installed boto

   2. Configuration of Boto/AWS credentials: http://boto.readthedocs.org/en/latest/getting_started.html#configuring-boto-credentials

   3. Please note that there's currently a major bug in Ansible/epc_vpc which ignores profile parameter and uses default credentials, so you need to make sure that your default AWS credentials point to the environment where you need things created.

6. Clone this repo with:

   git clone https://github.com/apiacademy/microservices-deployment.git

7. Go into the cloned repo and run the included ec2 script, to make sure you properly installed and configured Boto:

   cd inventory && ./ec2.py --list --boto-profile irakli-aws && cd --

   Make sure to replace irakli-aws with your AWS profile name from ~/.aws/credentials. You can omit the option if you are using default profile from that file.

   Please also note that in the version of ec2.ini file we ship, for the sake of speed, we restrict the AWS regions the script works with to North America ones. If you need access to any other zone, or all zones: please edit the ec2.ini file accordingly.

8. Save a private SSH key that you use/will use the root user on your AWS servers under: ssh/private-key.pem. For security reasons, ssh folder is .gitignore-d in the demo repo, and you should ignore it, as well, if you build on top of the demo. NEVER check-in SSH keys into repos!

   ATTENTION: corresponding public key must be placed under roles/aws-server-creation/ssh/public-key.pem!!!

9. Make sure your private key permissions are valid:

   chmod 700 ssh
   chmod 600 ssh/*    
   

10. If you have some EC2 servers tagged with [key=Name, value=cademo_consuls], and the AWS credentials profile you are using is still `irakli-aws, then you can ping the tagged servers from Ansible with a command like:

    AWS_PROFILE=irakli-aws ansible -i ec2.py tag_Name_cademo_consuls -m ping    
    

    You can find more information about ec2 script and using dynamic EC2 inventories at: https://aws.amazon.com/blogs/apn/getting-started-with-ansible-and-dynamic-amazon-ec2-inventory-management/

11. Please make sure you set up proper AWS Profile in group_vars/all.yml under aws_profile variabe and then you can create required servers as easily as running:

Quickstart

To create all the servers:

AWS_PROFILE=irakli-aws ansible-playbook play-010-create-servers.yml

To run the entire thing:

AWS_PROFILE=irakli-aws ansible-playbook play-all.yml

Debugging

Consul logs are under: /var/log/upstart/consul.log

To see current members of Consul cluster:

consul members

To make sure that consul leadership election succeeded (bootstrapping), you can run the following on a consul server:

consul info

and analyze the raft: section of the response.

Troubleshooting

If you are on a network that doesn't allow access to custom port you can create an SSH proxy:

ssh -D 12345 myuser@remote_ssh_server

and then in your browser proxu settings indicate SOCKS5 proxy with hostname: localhost, port: 12345.