Rundeck's History and Future
-
Upload
dev2ops -
Category
Technology
-
view
2.171 -
download
3
description
Transcript of Rundeck's History and Future
![Page 1: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/1.jpg)
SF#1
San Francisco User Group
http://rundeck.org
![Page 2: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/2.jpg)
Why Rundeck? A bit of history
Big in 2010
![Page 3: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/3.jpg)
Why Rundeck? A bit of history
Apr 2010
![Page 4: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/4.jpg)
Why Rundeck? A bit of history
Broke process into reusable workflows
![Page 5: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/5.jpg)
Why Rundeck? A bit of history
“the future rundeck”
Node info via Rightscale API
SSH
![Page 6: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/6.jpg)
Why Rundeck?
Development Testing Ops
Relative time given to each project phase (YMMV)
Ops requests are interrupt driven and usually at the last moment in the project life cycle
![Page 7: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/7.jpg)
Why Rundeck?
“Do this, then that” handoff methods don’t scale
README-------------
• “Do step 1”• “Do step 2”
• Goto README#2
and/or Tasks.xls
“Do this, then that”
and/or
![Page 8: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/8.jpg)
Why Rundeck?
Scripts
Build tools
Package
IaaS
Cfg MgtRemote execDBsRepos
LoggingNotification
“Islands” of disconnected tools
![Page 9: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/9.jpg)
Why Rundeck?
Scripts
Build tools
Package
IaaS
Cfg MgtRemote execDBsRepos
LoggingNotification
“Islands” across business units
Scripts
Build tools
Package
IaaS
Cfg MgtRemote execDBsRepos
LoggingNotification
Scripts
Build tools
Package
IaaS
Cfg MgtRemote execDBsRepos
LoggingNotification
Scripts
Build tools
Package
IaaS
Cfg MgtRemote execDBsRepos
LoggingNotification
![Page 10: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/10.jpg)
Why Rundeck?
Project vision● Central service for visibility of operations tasks● “Jobs” for easy hand offs between teams and users● Create interfaces between disparate tools and
resources● Give managers auditing, access control, logging● APIs to create and share reusable “Ops services”
New idea: “Operations as a Service”
![Page 11: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/11.jpg)
What is Rundeck?
● A Server for people that want to create reusable task automation○ Enable operations teams to be service providers○ Increase visibility and trust between teams○ Lower “mean-time to button” and a friendly end
user experience
● An open source software project at GitHub (Apache 2.0 license)
![Page 12: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/12.jpg)
Use: Standard operating procedures
Safely share code, not error prone “this, then that” information
“NOC” user
App devs
PagerDuty incident
![Page 13: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/13.jpg)
Use: 0-click deploy in testEnable continuous delivery for QA
Jenkins, Bamboo, Go
Nexus,Artifactory,Yum, apt
Email, Webhook,Hipchat, PagerDuty
Puppet, Chef, CFEngine,Saltstack
![Page 14: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/14.jpg)
Use: Data processing on AWSAutomate server provisioning and data processing work
![Page 15: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/15.jpg)
Use: VMWare test environments
Self serve provisioning of version and/or branch specific environments for testers
QA tester
![Page 16: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/16.jpg)
Use: “Powered-by” Rundeck
● Past “tool developers” now create automation SaaS for internal users.
● API only. Users never see Rundeck GUI.○ Examples:
■ Fidelity: “click-to-compute”■ Adobe: “CDOT”■ Major bank: firmwide depl.■ Salesforce■ UShareSoft: Transcend■ Axemblr: Provisionr
![Page 17: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/17.jpg)
Demo
![Page 18: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/18.jpg)
Demo - Takeaways
● Job data context: Nodes and Options● Role specific access● Error-handling workflows● Plugins: logstash, hipchat, pagerduty, aws,
puppet, salt, chef, winrm, jenkins, nexus
![Page 19: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/19.jpg)
How do you use Rundeck?
● Make jobs from multi-step workflows.● Execute tasks on nodes using your favorite
command, tool, transport and agent.● Define reusable environment independent
procedures.● Limit user access using ACL policies.
![Page 20: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/20.jpg)
Who does what?
● Admins stand up Rundeck service● Anybody can write and run jobs● Devs create plugins ● Ops runs standard operating procedures
This is a gross generalization
![Page 21: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/21.jpg)
System view
● Deploy standalone or as webapp● Packages: launcher, RPM/DEB, WAR● Authentication: LDAP/AD, PAM, file● Database: H2, Mysql, Oracle● Plugins: Java or shell script
![Page 22: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/22.jpg)
Roadmap: Vote on the trello board
● Work in progress for v2.0 ○ Software stack: New grails, Java, Jetty, Bootstrap,...○ Codahale metrics library (/metrics)○ Job libraries and project SCM support○ GUI: More user friendly job follow page○ API: Endpoints for rundeck administration, ++○ Github org change: /dtolabs > /rundeck○ New logos!
< Caution: may break stuff!
< Sponsored Dev!
![Page 23: Rundeck's History and Future](https://reader034.fdocuments.us/reader034/viewer/2022051411/548099e0b4795979578b473e/html5/thumbnails/23.jpg)
How to get involved
● Participate on the mail list● IRC: #rundeck on freenode● Twitter: @rundeck● Talk about your uses and successes● Write a plugin!● Submit a pull request
Sponsor a feature [email protected]