Finding the Future on a Toy Cloud

The Use Case

End to end examples of DevOps code are hard to find.

DevOps engineers will write the same code again and again.

Technology decisions could be simpler if we knew some basic integrations up front.

DevOps code is often surpressed out of security concerns.

Third party security providers have a niche because they allow customers to offload liability.

It's still smart to have open source security options; the learning is the ROI.

Attention to the primary encoding of infrastructure can make it easier to iterate.

Frameworks, standards, design patterns, IDEs have made application development easier.

But DevOps engineers still keep everything in their heads.

Think of a cloud as a meta filesystem. All of the services and applications are part of your project. Ouch!

Human centered design means something different if you spend all day on the command line, but it still applies to cloud.

A usable cloud is has errors that tell you where to find the code in the metasystem.

A usable cloud has easy dependency checking. It has tests and you can run them.

I want them to make my dashboards, too.

Let's say application dependencies are packages and source.

Service dependencies are external to the application: an application needs a database.

Bootscripts and custom resources are also service dependencies.

We may take it then that an army without its baggage train is lost; without provisions it is lost; without bases of supply it is lost. - Sun Tzu

Understand your dependency chain for sane project management.

Share daily builds and git automation at the beginning of the project.

Automate credentials at the outset: the first thing to the cloud is the DevOps team.

If you build a toy cloud, you'll use it for testing, development, and unscheduled capacity.

You can prototype infrastructure and iterate on complex structures. Understand your dependencies, and have a sane upgrade strategy.

ellenm@prime8consulting.com

Ele Munjeli on LinkedIn

munjeli on Github