Rock Solid WordPress

Erik OstermanCloud ArchitectureLeave a Comment

1 min read

Learn how Cloud Posse recently architected and implemented WordPress for massive scale on Amazon EC2. We'll show you exactly the tools that we used and our recipe to both secure and power WordPress setups on AWS using Elastic Beanstalk, EFS, CodePipeline, Memcached, Aurora and Varnish.

The “Holy Grail” of DevOps

Erik OstermanDevOps2 Comments

1 min read

Learn about some of the “best practices” for running a modern engineering organization that we practice at Cloud Posse. “Best Practices” are opinionated & proven strategies/tactics used to achieve some desired outcome.
These slides are a small part of what we think it takes to embrace a DevOps culture. It starts with the “Organization” embracing change and laying a foundation that will support the cross-disciplinary practice of DevOps.

Managing Secrets in Production

Erik OstermanCloud ArchitectureLeave a Comment

1 min read

Secrets are any sensitive piece of information (like a password, API token, TLS private key) that must be kept safe. This presentation is a practical guide covering what we've done at Cloud Posse to lock down secrets in production. It includes our answer to avoid the same pitfalls that Shape Shift encountered when they were hacked. The techniques presented are compatible with automated cloud environments and even legacy systems.

The Paradigm Shift

Erik OstermanOpEdLeave a Comment

4 min read

Over the last year we're seeing yet another massive transformation in how software is being delivered take hold. I’m going to call this a “Paradigm Shift” – it’s that containers are replacing virtual machines as the fundamental unit of software delivery at an unprecedented rate.
Apparently Moore’s Law applies to the rate of adoption of new technologies as much as it does the density of transistors. The rate of adoption of public cloud is twice that of of what we saw with Virtual Machines and now we're seeing the same thing with container adoption. You see, Enterprises are interesting species to study because they are the slowest to move and therefore a consistent barometer of change. Enterprises are learning to be more tolerant of change—this an awesome trend.
What are the ingredients for a paradigm shift? Let’s begin by looking at few examples.
The concept of “Virtual Machines” had been around since the 60s, but it took until the late 90s for the technology to catch up. It wasn’t until VMware came out with their “VMware Workstation” product 1998 that the concept got popularized and we saw mass adoption. What did they do? They made it easy—first and foremost for developers to run multiple environments on their desktops. Then they conquered the enterprise with tools.

The other prime example is “Cloud Computing.” It was not a new concept, it’s just that no one had really cracked the nut to show us how to do it properly. That was until Amazon came along. With EC2 they made it accessible and showed us the possibilities; they let us write infrastructure as code. Our minds were blown with the possibilities! So everyone tried to copy what Amazon did, but unfortunately it was a little too late.

That's because now we have the container movement. The concept of “Containers” is also nothing new. In Linux, the core functionality has existed ever since 2008 when Google contributed their work on LXC – the technology behind containers – to the Linux Kernel. However, it wasn’t until Docker came along circa 2013 (5 years later!) and made it braindead easy for developers to run them that we started seeing an uptick in their adoption. Now Docker is taking a page out of VMware's playbook by following up with Enterprise tools for production with release of Universal Container Platform (“UCP”) & and the Docker Datacenter (“DDC”).

The the secret?
  1. Make it easy.
  2. Target developers.
  3. Let percolate through out the enterprise until resistance is futile.
In the wake of all these transitions is some collateral damage. These are shims or training wheels that we used to get from bare metal to containers. It's the result of the natural process of innovation.
  • A dozen or more hypervisor technologies like VMware, Zen, KVM will lose massive market share.
  • Elaborate Configuration Management tools like Puppet and Chef that were created to address the broken ways we used to configure software (basically emulated what humans would do by hand) will no longer be needed because we don’t write software as broken anymore.
  • EC2 private-cloud knock offs like OpenStack, vCloud, Eucalyptus, CloudStack, etc that were designed to run your own private cloud on-prem like Amazon, are now overkill or at the very least passé (R.I.P.)
So why is the move to containers happening so quickly?

Hint: It’s not strictly technological.

First of all, we can agree that anytime we iterate, the second iteration is easier, better and faster than the first. Simply put, everything is less scary the second time around. Moving from the classic “bare metal” paradigm to a “virtualized” one was a massive endeavor. It was the “first” major paradigm shift of it’s kind. It took convincing of both C-Level execs and wrangling of Operations teams. Since it was a foreign concept, there was severe skepticism and push back at all stages. Flash forward 15 years later and there’s now fresh blood at the top. There’s a new guard who has moved up through the ranks that’s more accepting of new technology. Enterprises have gotten better at accepting change. More over, the tools of the trade have improved. We’re better at writing software — software that is more cloud friendly (aka “cloud native”).

Here are my predictions for what we're going to see over the next few years.
  1. Containers will become first-class citizens, replacing VMs as the defacto unit of cloud.
  2. If you still need a VM, that’s cool; you’ll have a couple options:
    • Leverage a VM running inside a container. There's a project by Rancher called “VM Containers” which does exactly this. Sound absurd? Not to Google. They run their entire Public Cloud – VMs & all – on top of Borg.
    • Use Clear Containers by Intel which have minimal overhead, full machine-level isolation and can leverage the VT technology of modern CPU chipsets. Not to mention, it's fully Open Source!
    • The brave will attempt using some sort of Unikernel, but it’s still too early to know for sure if that will be the way to go.
  3. Interest behind OpenStack (et al) will wane and innovation cease – they were ahead of their time. We learned A LOT from the experience – both what worked well and didn't. As a result, we'll see a significant brain-drain, with key contributors moving over to the Kubernetes camp.
  4. Kubernetes will replace OpenStack du jour and as a result we'll see a resurgence of bare-metal in the Enterprise
  5. Amazon’s ECS will be EOL’d and replaced with offerings of Kubernetes & Swarm.
  6. Kubernetes and Swarm will be battling it out for #1 because competition is good.
  7. The best features of Mesos will be cherry picked by both Kubernetes & Swarm, but Mesos fail to gain bigger foothold in the market.

Tips on Writing Go Microservices for Kubernetes

Erik OstermanCI/CD, Cloud ArchitectureLeave a Comment

1 min read

Kelsey Hightower, a Google Developer Advocate and Google Cloud Platform evangelist, recently gave a very helpful screencast demonstrating some of the tips & tricks he uses when developing Go microservices for Kubernetes & docker. Among other things, he recommends being very verbose during the initialization of your app by outputting environment variables and port bindings. He also raises the important distinction between readiness probes and liveness probes and when to use them. Lastly, in the Q&A he explains why it's advantageous to use resource files instead of editing live configurations because the former fits better in to a pull-request workflow that many companies already use as part of the CI/CD pipeline.