Saltstack - Orchestration & Application Deployment
0 likes527 views
The document presents a comprehensive overview of SaltStack orchestration, detailing its essential features and functionalities for system automation and application deployment. It covers the role of orchestration in managing resource dependencies, executing commands across diverse servers, and achieving fully automated workflows. Additionally, the document includes a hands-on demo and links to further resources and job opportunities in related fields.
![〉 Lazy Admins: „Don‘t repeat yourself“ (DRY)
〉 Busy Admins: „I have a lot of other problems and [...]“
〉 Small Teams: „Ask X, but she/he is out of office until next week“
Who needs Orchestration?
7](https://image.slidesharecdn.com/saltstack-orchestration-and-application-deployment-arnold-bechtoldt-openrheinruhr-7-11-2015-151109111848-lva1-app6892/85/Saltstack-Orchestration-Application-Deployment-7-320.jpg)
![〉 ... uses remote execution to distribute system commands
〉 ... should be more than just executing commands (most of the tools end here)
〉 ... should be able to respect internal & external dependencies/relations
〉 ... should happen deterministic, imperative and fast
〉 ... must [RFC2119] be easy to understand/learn (YMMV)
Orchestration...
8](https://image.slidesharecdn.com/saltstack-orchestration-and-application-deployment-arnold-bechtoldt-openrheinruhr-7-11-2015-151109111848-lva1-app6892/85/Saltstack-Orchestration-Application-Deployment-8-320.jpg)
![http://www.ansible.com/blog/orchestration-you-keep-using-that-word
For instance, if you use a single-purpose deployment
tool [...] to trigger some legacy configuration
management, that might be called “orchestrating X
with Y”. In reality, it’s usually just replacing a non-
scaling [...] server solution X with a stand-alone
implementation of Y.
10](https://image.slidesharecdn.com/saltstack-orchestration-and-application-deployment-arnold-bechtoldt-openrheinruhr-7-11-2015-151109111848-lva1-app6892/85/Saltstack-Orchestration-Application-Deployment-10-320.jpg)
![salt/job/20151104191820394966/new {
"_stamp": "2015-11-04T18:18:20.512126",
"arg": [
”orchestration.bootstrap",
{
"__kwarg__": true,
"test": false
}
],
"fun": "state.sls",
"jid": "20151104191820394966",
"minions": [
”mw42"
],
"tgt": ”mw42",
"tgt_type": "glob",
"user": ”root”
}
Event Structure
17
custom/minion/haste_server_started {
"_stamp": "2015-11-04T18:33:54.650568",
"cmd": "_minion_event",
"data": {
”custom": {
"onchanges": [],
"foo": "bar",
"num": 42,
},
"sfun": "wait"
},
"id": "mw2",
"pretag": null,
"tag": "custom/minion/haste_server_started"
}](https://image.slidesharecdn.com/saltstack-orchestration-and-application-deployment-arnold-bechtoldt-openrheinruhr-7-11-2015-151109111848-lva1-app6892/85/Saltstack-Orchestration-Application-Deployment-17-320.jpg)
Saltstack - Orchestration & Application Deployment
- 1. SaltStack Orchestration & Application Deployment Arnold Bechtoldt Oberhausen, 07.11.2015
- 2. Arnold Bechtoldt Systems Engineer @ inovex GmbH 〉 Platform Engineering 〉 System Automation & Development 〉 DevOps Support & Consulting 〉 Open Source Software Contributions 2
- 3. 1. Orchestration in General 2. SaltStack Orchestration Basics 3. Hands on: Demo 4. Q&A Agenda 3
- 4. Assets & Links 4 inovex.de arnoldbechtoldt.comgithub.com/bechtoldt/talk-salt-orchestration
- 6. Highway To Heaven 6 Asset- Management, Accounting Bare-Metal Deployment Configuration Management/ Containerization Orchestration Auto-Scaling + Elasticity Cloud
- 7. 〉 Lazy Admins: „Don‘t repeat yourself“ (DRY) 〉 Busy Admins: „I have a lot of other problems and [...]“ 〉 Small Teams: „Ask X, but she/he is out of office until next week“ Who needs Orchestration? 7
- 8. 〉 ... uses remote execution to distribute system commands 〉 ... should be more than just executing commands (most of the tools end here) 〉 ... should be able to respect internal & external dependencies/relations 〉 ... should happen deterministic, imperative and fast 〉 ... must [RFC2119] be easy to understand/learn (YMMV) Orchestration... 8
- 9. 9 MCollective + Shell Script A not-so-cool Example
- 10. http://www.ansible.com/blog/orchestration-you-keep-using-that-word For instance, if you use a single-purpose deployment tool [...] to trigger some legacy configuration management, that might be called “orchestrating X with Y”. In reality, it’s usually just replacing a non- scaling [...] server solution X with a stand-alone implementation of Y. 10
- 12. SaltStack implements the same techiniques that other tools do: 〉 send commands to servers 〉 send commands to servers that have different operating systems 〉 send commands only to a subset of servers 〉 run command A, then B, then C Some people call this orchestration and wrap this shell-oneliner with thousands LoC. SaltStack Orchestration 12
- 13. What we really want to have: 〉 scale accross thousands of servers 〉 easy configuration (less software programming) 〉 an interface to implement internal/external relationships (pre/post tasks) 〉 fully automated workflows/procedures (no manual interaction) SaltStack Orchestration 13
- 14. What we really want to have: 〉 scale accross thousands of servers SOA – Message Bus Architecture 〉 easy configuration (less software programming) YAML – JSON – Python DSL 〉 an interface to implement internal/external relationships (pre/post tasks) State – Execution – Pillar – Returner – Beacon – Cloud (~ 600 modules) 〉 fully automated workflows/procedures (no manual interaction) Event System – Reactor – Runner – APIs SaltStack Orchestration 14
- 15. State A resource should look like {…} Pillar Database/CMDB (Files, RDBMS, NoSQL) Execution Execute command X on a server. Used by other Salt components. Returner Log store of job results (DB, Elasticsearch, Syslog, Monitoring) Beacon Special event triggers (inotify, load, procs, network/user activity) Reactor Reacts to events by triggering subsequent procedures (execution modules) Cloud IaaS provisioning (EC2, OpenStack, Digital Ocean, Linode, GCE, VMware) … SaltStack Terminology 15
- 16. Event-Driven System Automation 16 minion minion minion minionminion minion minion minion minion minionminion reactor (master) salt/key salt/job/new node/stonith/new update/application salt/auth salt/job/return scale/out loadbalancer/config/update salt/minion/start salt/presence/present monitoring/hosts/new firewall/config/update salt/minion/stop salt/presence/change monitoring/hosts/remove coffee/new
- 17. salt/job/20151104191820394966/new { "_stamp": "2015-11-04T18:18:20.512126", "arg": [ ”orchestration.bootstrap", { "__kwarg__": true, "test": false } ], "fun": "state.sls", "jid": "20151104191820394966", "minions": [ ”mw42" ], "tgt": ”mw42", "tgt_type": "glob", "user": ”root” } Event Structure 17 custom/minion/haste_server_started { "_stamp": "2015-11-04T18:33:54.650568", "cmd": "_minion_event", "data": { ”custom": { "onchanges": [], "foo": "bar", "num": 42, }, "sfun": "wait" }, "id": "mw2", "pretag": null, "tag": "custom/minion/haste_server_started" }
- 18. Event-Driven System Automation 18 minion minion minion minion minion minionmaster MySQL Foreman etcd MySQL ElasticsearchSMTP Syslog Icinga Appliances HTTP Docker Slack PostgreSQLminion AWS
- 19. Hands on: Demo
- 20. Demo Concept 20 1. Tells MW hosts to install MW 4. Tells FE hosts to install FE 6. Tells MW hosts to deploy App 10. Tells FE to reconfigure FE 2. Install Node.JS (MW) 3. Report back to Master 7. Deploy App 8. Send Notification Mail 9. Report back to Master 5. Install Haproxy (FE) 6. Report back to Master 11. Add/Remove HAProxy backends 12. Report back to Master Salt Master/Reactor MW hosts FE hosts
- 21. Demo Concept 21 1. Tells MW hosts to install MW 4. Tells FE hosts to install FE 6. Tells MW hosts to deploy App 10. Tells FE to reconfigure FE 2. Install Node.JS (MW) 3. Report back to Master 7. Deploy App 8. Send Notification Mail 9. Report back to Master 5. Install Haproxy (FE) 6. Report back to Master 11. Add/Remove HAProxy backends 12. Report back to Master Salt Master/Reactor MW hosts FE hosts
- 22. Assets & Links 22 sh.arbe.io/cloud-provision youtu.be/9MzeK4u4pkM (demo)github.com/bechtoldt/talk-salt-orchestration
- 23. Q&A
- 27. Kolleginnen und Kollegen gesucht! • Application Development • Business Development • Consulting • Data Management & Analytics • IT Engineering & Operations • Hamburg • Karlsruhe • Köln • München • Pforzheim inovex.de/jobs
- 28. Thank You! Arnold Bechtoldt IT Engineering & Operations inovex GmbH Ludwig-Erhard-Allee 6 76131 Karlsruhe - Germany arnold.bechtoldt@inovex.de CC BY-NC-ND inovex.de +ArnoldBechtoldtGER github.com/bechtoldt arbe.io youtube.com/ inovexGmbH