Let's use Terraform to easily get a CoreOS cluster up on Digital Ocean. In this example we will get a 5 node CoreOS cluster up and running on the Digital Ocean 8GB size.
Grab a copy of Terraform for your platform from http://www.terraform.io/downloads.html. Follow the instructions at http://www.terraform.io/intro/getting-started/install.html by getting Terraform in your PATH and testing that it works.
| # The Roots theme by default does not check production assets into Git, so | |
| # they are not deployed by Capistrano when using the Bedrock stack. The | |
| # following will compile and deploy those assets. Copy this to the bottom of | |
| # your config/deploy.rb file. | |
| # Based on information from this thread: | |
| # http://discourse.roots.io/t/capistrano-run-grunt-locally-and-upload-files/2062/7 | |
| # and specifically this gist from christhesoul: | |
| # https://gist.github.com/christhesoul/3c38053971a7b786eff2 |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |
This gist is an implementation of http://sirile.github.io/2015/05/18/using-haproxy-and-consul-for-dynamic-service-discovery-on-docker.html on top of Docker Machine and Docker Swarm.
| { | |
| "check": { | |
| "id": "check-disk", | |
| "name": "check-disk", | |
| "script": "/usr/lib/nagios/plugins/check_disk -w 30% -c 5%", | |
| "interval": "1m" | |
| } | |
| } |
This script will pull down an S3 remote configuration before running any terraform actions. Assumes the following structure:
main.tf
terraform.cfg
env/dev/vars
env/staging/vars
env/whatever/vars
env/whatever/somefile.tf
| #cloud-config | |
| coreos: | |
| etcd2: | |
| # generate a token from https://discovery.etcd.io/new?size=3 | |
| discovery: https://discovery.etcd.io/<token> | |
| advertise-client-urls: http://$private_ipv4:2379 | |
| initial-advertise-peer-urls: http://$private_ipv4:2380 | |
| listen-client-urls: http://0.0.0.0:2379 | |
| listen-peer-urls: http://$private_ipv4:2380 |
| Set-StrictMode -Version Latest | |
| $payload = @{ | |
| "channel" = "#my-channel" | |
| "icon_emoji" = ":bomb:" | |
| "text" = "This is my message. Hello there!" | |
| "username" = "Mr. Robot" | |
| } | |
| Invoke-WebRequest ` |
This is quick howto for installing vault on AWS Linux, mostly to remind myself. At the end of this tutorial, you'll have a working vault server, using s3 for the backend, self signed certificates for tls, and supervisord to ensure that the vault server is always running, and starts on reboot.
First things first, let's set up an s3 bucket to use as the storage backend for our s3 instance.
From the AWS Mangement Console, go to the S3 console.
Click on the Create Bucket button
| #! /usr/bin/env bash | |
| # Install any build dependencies needed for curl | |
| sudo apt-get build-dep curl | |
| # Get latest (as of Feb 25, 2016) libcurl | |
| mkdir ~/curl | |
| cd ~/curl | |
| wget http://curl.haxx.se/download/curl-7.50.2.tar.bz2 | |
| tar -xvjf curl-7.50.2.tar.bz2 |