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”
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)
Use: Standard operating procedures Safely share code, not error prone “this, then that” information “NOC” user PagerDuty incident App devs
Use: 0-click deploy in test Enable continuous delivery for QA Jenkins, Nexus, Bamboo, Artifactory, Go Yum, apt Email, Webhook, Hipchat, PagerDuty Puppet, Chef, CFEngine, Saltstack
Use: Data processing on AWS Automate server provisioning and data processing work
Use: VMWare test environments Self serve provisioning of version and/or branch specific environments for testers QA tester
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
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
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.
Who does what? This is a gross generalization ● Admins stand up Rundeck service ● Anybody can write and run jobs ● Devs create plugins ● Ops runs standard operating procedures
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
Roadmap: Vote on the trello board ● Work in progress for v2.0 < Caution: may break stuff! ○ 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, ++ < Sponsored Dev! ○ Github org change: /dtolabs > /rundeck ○ New logos!
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 enhancement firstname.lastname@example.org