Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/SkeltonThatcher/aws-terraform-rancher-single-node-ha

Terraform scripts to deploy Rancher server single node HA and multi-AZ Rancher hosts in AWS
https://github.com/SkeltonThatcher/aws-terraform-rancher-single-node-ha

Last synced: 3 months ago
JSON representation

Terraform scripts to deploy Rancher server single node HA and multi-AZ Rancher hosts in AWS

Awesome Lists containing this project

README 

        
# Single Node HA for Rancher Server in AWS



This repo contains Terraform code and supporting scripts to deploy single node HA Rancher server and Rancher hosts in AWS.



The Terraform plan is designed to be applied in two stages. It will build out and deploy the following resources.



* x1 VPC + IGW

* x2 Public subnets

* x2 Private subnets

* RDS DB subnet group

* Single-AZ or Multi-AZ RDS MySQL DB instance

* Application load balancer + listener + target group

* Launch configuration + fixed Multi-AZ auto-scaling group of x1 instance for the Rancher server

* Launch configuration + fixed Multi-AZ auto-scaling group of a specified instance amount for the Rancher hosts

* RancherOS instance with active Docker running a password protected deployment of the latest version of Rancher server

* RancherOS instances with active Docker running the latest version of the Rancher host agent

* Route 53 DNS alias record for the ALB



The estimated deployment time from start to finish is 20-30 minutes.



### Prerequisites



* AWS account

* AWS IAM user account with AWS access/secret keys and permission to create specified resources

* Cygwin (or similar) installed to enable running of .sh scripts if using Windows

* Git installed and configured

* Terraform installed and configured



### How to use the Terraform plan to deploy Rancher server and Rancher hosts



#### Version advisories



* RancherOS v0.9.1

* Rancher server v1.5.3

* Rancher agent v1.2.1



#### Stage One



* Clone the repo

* Create an EC2 keypair in AWS

* Create an S3 bucket to hold remote state

* Update `init.sh` with the S3 bucket name

* Run `init.sh` to initialise remote state

* Create `terraform.tfvars` in the root of the cloned folder (see `terraform.tfvars.example`)

* Set `hst_max`, `hst_min` and `hst_des` in `terraform.tfvars` to zero (0)

* Make up a temporary reg_token in `terraform.tfvars`

* Run `terraform plan` from the root of the folder

* Run `terraform apply` from the root of the folder

* Wait until the installation has completed

* Access Rancher server at the displayed output URL

* Log in with the name and password specified in the `terraform.tfvars` file



#### Stage Two

* Enable hosts registration from within Rancher and copy the token from the registration string. The token will be in the format similar to `6C8B0D1B2E95DD1AA07A:1483142400000:PKQGzShMCv3wtD02DvlU4MkBY0`

* Update `reg_token` in `terraform.tfvars` with the registration token

* Update `hst_max`, `hst_min` and `hst_des` in `terraform.tfvars` with the max, min and desired amount of host instances

* Re-run `terraform plan`

* Re-run `terraform apply`

* The launch configuration will be replaced with a new version and applied to the auto scaling group

* The specified amount of host instances will launch and register with the Rancher server



#### How to remove

* To remove all deployed resources run `terraform destroy`



### Supplemental

*  [Container Clustering with Rancher Server (Part 5) – Automating the deployment of AWS infrastructure and Rancher with Terraform](https://skeltonthatcher.com/blog/container-clustering-rancher-server-part-5-automating-deployment-aws-infrastructure-rancher-terraform/)



### Licence



Copyright (c) 2017 Skelton Thatcher Consulting Ltd.



Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at



http://www.apache.org/licenses/LICENSE-2.0



Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.



### Acknowledgments



* Based on works produced by [George Cairns](https://www.linkedin.com/in/george-cairns-9624b621/) from [Automation Logic](http://www.automationlogic.com/)