csuttles (⌐■_■)

Memento Mori

What is this? This is a fun little project I did to try to take some a simple Azure Quickstart post and enhance it to do something a little more (?:interesting|useful|realistic). Challenge yourself Can you accomplish the end goal of this lab without looking at the solution? If you looked at the solution and ran it, can you change it to make it do something else, like transcode videos or one of the other common uses of batch?

This post is the last in a series on deploying the Hashicorp recommended architecture for a single DC deployment of Vault on Oracle Cloud Infrastructure (OCI). Here are some related links: https://github.com/csuttles/oci-vault/ (the code for all of this) http://blog.csuttles.io/getting-started-with-terraform-on-oracle-cloud-infrastructure-oci/ (intro) http://blog.csuttles.io/building-hashicorp-vault-in-oci-part-i/ (part i) http://blog.csuttles.io/building-hashicorp-vault-in-oci-part-ii/ (part ii) http://blog.csuttles.io/building-hashicorp-vault-in-oci-part-iii/ (this article) Create Vault Nodes In the previous articles in the series, we built out prerequisite resources, including compartments, a VCN, subnets, seclists, and finally consul servers.

This post is a continuation of a series. The first two posts are here and here[.] The source for this series is available on GitHub. Building Consul in OCI Now that we have defined the IAM and network resources that Vault depends on, it's time to start building Consul nodes, which we will use as the backend for Vault. In order to build Consul, and completely automate the bootstrap, we will take advantage of some OCI and Terraform features.

This post will continue a previous post on using Hashicorp's Terraform with OCI (Oracle Cloud Infrastructure). Building the Network Resources Let's walk through a single region where we will build out the network resources where our Vault installation will reside. Here's the variables where we define the storage backend and Terraform provider. It's the same basic setup as defined in my previous post. csuttles@cs-mbp15:[~/src/oci-vault/iad/network]:(master) [Exit: 0] 11:19: cat variables.tf variable "tenancy" {} variable "tenancy_ocid" {} variable "user_ocid" {} variable "fingerprint" {} variable "private_key_path" {} variable "region" { default = "us-ashburn-1" } variable "compartment_ocid" {} provider "oci" { tenancy_ocid = "${var.

Recently, I started doing the 100 days of code challenge. I'm off to a slow start, since I am juggling more than usual in my personal life. If you're curious about my progress, you can see my 100 days of code repository on GitHub. First steps I'm revisiting Java and C fundamentals at the same time. I hope to improve my skills in both, as well as gaining some insight at a meta level on just "programming".

This post takes a look at using Hashicorp's Vault to manage dynamic database credentials, using Chef. For this post (and the my previous post on Vault), I started working with Vault pretty quickly via this docker-compose setup I found via GitHub. It's a very quick way to get a Vault instance with a Consul backend. You'd never do this for production, since they are single instances, but for functional testing, it's enough.

I've exceeded the AWS free tier, and happened upon a post from a friend that leads to an easy $50 AWS credit. Introducing the AWS Codestar Challenge. Codestar follows the pricing model of CloudForms and Elastic Beanstalk. It's free, but the resources created by CodeStar follow their respective pricing models. CodeStar brings together a bunch of AWS services to form an incredibly easy to use CI/CD pipeline. I was able to deploy a CI/CD pipeline for a Lambda based Python app in minutes, including setting up my access.

Automate Everything It's important to automate all the things you can to make your workflow efficient and error free. It's easy to miss a step in a runbook or let a typo ruin your testing. Enter Rally I think best way to test changes is via CI/CD, and Rally is the tool that's used for gating changes to OpenStack in OpenStack's Zuul. Even if you are not commiting code to OpenStack, Rally can help you validate changes to your environment.

Upstream Institute Sunday, I attended this session, and met some great people. I sat with two Swift core contributors, two Cinder contributors, and a Manilla contributor who also previously contributed to Horizon and Trove. The class was an intro to contributing to OpenStack, so I was lucky to end up at a table full of seasoned folks. I made connections with almost everyone at the table, and I really enjoyed speaking with them and learning from them.