Introduction to Nomad and Otto

In this talk I introduce both Nomad and Otto, tools recently announced at HashiConf 2015. Nomad is a distributed cluster scheduler, that makes it easy to declaratively run applications across a cluster of machines. Otto is the spiritual successor to Vagrant, making creating development environments easier, adding deployment to the workflow, and helping micro service oriented workflows.

This talk was presented at the InfraCoders meetup in Santa Clara.

Transcript

2. Armon Dadgar @armon
5.  
14. ATLAS
15. Management Collaboration Security Web Interface CLI Core Functionality Open Source The relationship between Otto and Atlas is like Git and GitHub Git Otto GitHub Atlas
17. Nomad Distributed Scheduler Easily Deploy Applications Job Specification
18. example.nomad # Define our simple redis job job "redis" { # Run only in us-east-1 datacenters = ["us-east-1"] # Define the single redis task using Docker task "redis" { driver = "docker" config { image = "redis:latest" } resources { cpu = 500 # Mhz memory = 256 # MB network { mbits = 10 dynamic_ports = ["redis"] } } } }
19. Job Specification Declares what to run
20. Job Specification Nomad determines where and manages how to run
21. Job Specification Powerful yet simple
22. example.nomad # Define our simple redis job job "redis" { # Run only in us-east-1 datacenters = ["us-east-1"] # Define the single redis task using Docker task "redis" { driver = "docker" config { image = "redis:latest" } resources { cpu = 500 # Mhz memory = 256 # MB network { mbits = 10 dynamic_ports = ["redis"] } } } }
23. Containerized Virtualized Standalone Docker Qemu / KVM Java Jar Static Binaries
24. Containerized Virtualized Standalone Docker Jetpack Windows Server Containers Qemu / KVM Hyper-V Xen Java Jar Static Binaries C#
25. Nomad Application Deployment Docker Multi-Datacenter and Multi-Region Flexible Workloads Bin Packing HCL Job Specifications
26. Nomad Easy for developers Operationally simple Built for scale
27. Easy for developers
28. Terminal $ nomad agent -dev ==> Starting Nomad agent... ==> Nomad agent configuration: Atlas: <disabled> Client: true Log Level: DEBUG Region: global (DC: dc1) Server: true ==> Nomad agent started! Log data will stream in below: [INFO] serf: EventMemberJoin: nomad.global 127.0.0.1 [INFO] nomad: starting 4 scheduling worker(s) for [service batch _core] [INFO] raft: Node at 127.0.0.1:4647 [Follower] entering Follower state [INFO] nomad: adding server nomad.global (Addr: 127.0.0.1:4647) (DC: dc1) [DEBUG] client: applied fingerprints [storage arch cpu host memory] [DEBUG] client: available drivers [docker exec]
29. Operationally simple
30. Client Server
31. Built for scale
32. Built on experience gossip consensus
33. Built on research gossip consensus
34. Single Region Architecture SERVER SERVER SERVER CLIENT CLIENT CLIENT DC1 DC2 DC3 FOLLOWER LEADER FOLLOWER REPLICATION FORWARDING REPLICATION FORWARDING RPC RPC RPC
35. Multi-region Architecture SERVER SERVER SERVER FOLLOWER LEADER FOLLOWER REPLICATION FORWARDING REPLICATION REGION  B  GOSSIP REPLICATION REPLICATION FORWARDING REGION  FORWARDING  REGION  A SERVER FOLLOWER SERVER SERVER LEADER FOLLOWER
36. Thousands of regions Tens of thousands of clients per region Thousands of jobs per region
37. Optimistically Concurrent
38. Data Model
39. HASHICORP Evaluations ~= State Change Event
40. HASHICORP Create / Update / Delete Job Node Up / Node Down Allocation Failed
41. HASHICORP “Scheduler” = func(Eval) => []AllocUpdates
42. HASHICORP Scheduler func’s can specialize (Service, Batch, System, etc)
43. HASHICORP Evaluation Enqueue
44. HASHICORP Evaluation Dequeue
45. HASHICORP Plan Generation
46. HASHICORP Plan Execution
47. HASHICORP External  Event Evalua?on  Crea?on Evalua?on  Queuing Evalua?on  Processing Op?mis?c  Coordina?on State  Updates
48. Case study
49. Case study 3 servers in NYC3 100 clients in NYC3, SFO1, AMS2/3 1000 Containers
50. Case study <1s to schedule 1s to first start 6s to 95% 8s to 99%
51. Nomad Easy for developers Operationally simple Built for scale
52. HASHICORP Nomad 0.1 Released in October Service and Batch Scheduler Docker, Qemu, Exec, Java Drivers
53. HASHICORP Nomad 0.2 - Service Workloads Service Discovery System Scheduler Restart Policies Enhanced Constraints
54. HASHICORP Nomad 0.3 - Batch Workloads Cron Job Queuing Latency-Aware Scheduling
55. nomadproject.io
56. Nomad
58. Otto The Successor 
 to Vagrant
60. Vagrant Our biggest OSS project Built in 2010 Re-imagined for 2015
61. Vagrant What have we learned?
62. Vagrant Development environment deviation is minimal
63. Vagrant Developers want to deploy
64. Vagrant Microservices are the future
65. Otto The Successor 
 to Vagrant
66. Otto Development Deployment Microservices Appfile
67. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla quis ex nec lectus auctor semper at eu nunc. Nulla lorem mi, interdum eget libero eleifend, euismod laoreet neque. Donec nec enim rhoncus, varius nisi ut, hendrerit sem. Cras nec vestibulum nunc, blandit cursus eros. Etiam tincidunt cursus turpis, sit amet lacinia nunc consectetur at. Vestibulum nec faucibus neque, a dapibus elit. Cras aliquam, enim ut tincidunt aliquam, enim nunc hendrerit leo, ac fringilla lectus lacus quis arcu. Appfile
68. Appfile
69. THIS FILE INTENTIONALLY LEFT BLANK Appfile
70. application { name = "my-store" type = "ruby" dependency { source = "github.com/hashicorp/otto/examples/postgresql" } } customization "ruby" { ruby_version = "2.1" } Appfile
71. Codification vs. Fossilization
72. Otto is smart. Otto will get smarter.
73. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla quis ex nec lectus auctor semper at eu nunc. Nulla lorem mi, interdum eget libero eleifend, euismod laoreet neque. Donec nec enim rhoncus, varius nisi ut, hendrerit sem. Cras nec vestibulum nunc, blandit cursus eros. Etiam tincidunt cursus turpis, sit amet lacinia nunc consectetur at. Vestibulum nec faucibus neque, a dapibus elit. Cras aliquam, enim ut tincidunt aliquam, enim nunc hendrerit leo, ac fringilla lectus lacus quis arcu. Appfile Compilation 
74. $ otto compile ==> Loading Appfile... ==> Fetching all Appfile dependencies... ==> Compiling... Application: vault (go) Project: vault Infrastructure: aws (simple) Compiling infra... Compiling foundation: consul ==> Compiling main application… ==> Compilation success! This means that Otto is now ready to start a development 
 environment, deploy this application, build the 
 supporting infrastructure, and more. See the help for 
 more information.
75. $ tree .otto .otto "## appfile $ "## Appfile.compiled $ &## version "## compiled $ "## app $ $ "## dev $ $ $ &## Vagrantfile $ $ "## dev-dep $ $ $ "## Vagrantfile $ $ $ "## Vagrantfile.fragment $ $ $ "## build.sh $ $ $ &## upstart.conf $ $ &## foundation-consul $ $ "## app-build $ $ $ "## main.sh $ $ $ &## upstart.con … 27 directories, 49 files
77. Fossilization
78. Development  
79. otto dev
80. $ otto dev … ==> Caching SSH credentials from Vagrant... ==> Development environment successfully created! IP address: 172.16.1.154 A development environment has been created for writing a generic Ruby-based app. Ruby is pre-installed. To work on your project, edit files locally on your own machine. The file changes will be synced to the development environment. When you're ready to build your project, run 'otto dev ssh' to enter the development environment. You'll be placed directly into the working directory where you can run 'bundle' and 'ruby' as you normally would. You can access any running web application using the IP above.
81. $ otto dev ssh ==> Executing SSH. This may take a few seconds... Welcome to Ubuntu 12.04.1 LTS * Documentation: https://help.ubuntu.com/ Last login: Sun Sep 27 17:20:30 2015 from 172.16.1.1 vagrant@precise64:/vagrant$
82. $ otto dev address 172.16.1.154
83. $ otto dev destroy ==> Destroying the local development environment... ==> default: Stopping the VMware VM... ==> default: Deleting the VM... ==> default: Running cleanup tasks for 'shell' provisioner... ==> default: Running cleanup tasks for 'shell' provisioner... ==> Deleting development environment metadata... ==> Development environment has been destroyed!
84. A wonderfully simple development experience
85. Development  
86. Deployment  
89. Today's Best Practices WEB DB MICRO SERVICES PRIVATE  SUBNET  PUBLIC  SUBNET  INTERNAL  NETWORK LB BASTION NAT
90. WEB DB MICRO SERVICES PRIVATE  SUBNET  PUBLIC  SUBNET  INTERNAL  NETWORK LB BASTION NAT Today's Best Practices COMPLEXITY
92. $ otto infra $ otto build $ otto deploy
93. Microservices Monolithic Microservices
94. Microservices
95. Microservices
96. Otto
97. application { name = "my-store" type = "ruby" dependency { source = "github.com/hashicorp/otto/examples/postgresql" } } customization "ruby" { ruby_version = "2.1" } Appfile
98. $ otto dev … [otto] Installing dependency: postgresql [otto] Configuring Consul service: postgresql ==> Development environment successfully created! IP address: 172.16.1.154 A development environment has been created for writing a generic Ruby-based app. Ruby is pre-installed. To work on your project, edit files locally on your own machine. The file changes will be synced to the development environment. When you're ready to build your project, run 'otto dev ssh' to enter the development environment. You'll be placed directly into the working directory where you can run 'bundle' and 'ruby' as you normally would. You can access any running web application using the IP above.
99. $ otto dev ssh vagrant@precise64:/otto$ nslookup postgresql.service.consul. Server: 127.0.0.1 Address: 127.0.0.1#53 Name: postgresql.service.consul Address: 192.168.139.214
100. $ otto deploy … ==> Application deployed! Address: ec2-10-1-2-3.us-east-1.compute.amazonaws.com
101. Otto Development Deployment Microservices Appfile
102. ottoproject.io
103. Otto
104. QUESTIONS? THANK  YOU!