The document discusses the evolution of infrastructure tools at Seven Bridges from a manual process to tools like Context, Minion, and Vayu. Originally configurations were kept manually in Git and environments were difficult to configure. Context was created to version and clone configurations. Minion provided a uniform way to manage services and Vayu kept data on development environments and provided a web interface. These tools emerged to address needs rather than being pre-planned, and helped move infrastructure processes into production.

1. The DevOps MeetUp
Seven Bridges Infrastructure
Tools
Ivan Vandot
SevenBridges.com

2. The way back
We had one production environment with multiple servers
One beta server with all components with versions matching
current production as a hot x environment
One beta server clone for next release, we can call it “staging”
One integrations server that never worked

3. The way back
Ten production components
Con gurations for all services were kept in Git repo in separate
directories for di erent environments and components
Con gurations were changed manually and merged from one
release to another

4. The way back
Bunraku was on worker instances and Skynet system utilized
Bunraku on static server infrastructure
Nobody knew how to manually con gure and bring up new
environment, whether it is a production, development or beta
We knew all build dependencies for all components, but not the
runtime

5. Vayu -> Context -> Minion

6. Context
Written in Django
It has almost complete API
Created with security in mind

7. Context
Can clone and merge con gurations from one environment to
another
Con gurations are versioned
Globals feature

8. Context

9. Minion
First it was written in Python
Minion was created on the principles of Skynet
Later rewritten in Go

10. Minion
Go minion has CLI client called mnn also written in Go
It has JSON based con guration les with possibility of
con guration inheritance

11. Minion JSON configuration
{
"=": [
"_component",
"_config",
"_host"
],
"check-url": "https://{{fqdn}}:{{port}}/status",
"port": "8889",
"start": [
{
"#": "start the service",
"=": "cmd",
"args": [
"start"
],
"dir": "/data/app/{{name}}",
"env": [
"JAVA_HOME=/usr/lib/jvm/java-8-oracle/jre",
"LANG=en_US.UTF-8"
],
"exec": "bin/{{name}}-server.sh"

12. Minion
Minion provided us uniformity in managing our services
Ruler and goruler

13. Vayu
Written in Django
Vayu service is keeping the data of all development environments
and provides web-interface for creating and updating them
Minion and Context emerged as a need for Vayu, not as services
that were planned

14. Vayu
Many things were left to be part of Amazon AMI
Vayu web interface has not changed much, neither the
functionality

15. Vayu

16. Vayu State
Vayu state was added to Vayu

17. Current State
Multiple production environments, each
with its own staging environment, more
than 100 vayus

18. How can something of
infrastructure move into
production and contribute to
the product

19. Bunraku muerto

20. Emerging from infrastructure -
Minion

21. Minit - Minion Initialization

22. Clockwork
Houston we have a problem!

23. Clockwork

24. Houston

25. Q&A