Rundeck is an open source tool for executing jobs and automating operations across multiple servers. It allows users to define jobs that run commands or scripts on nodes, and organize those jobs into workflows. Key features include importing nodes from configuration management databases, running jobs in parallel, monitoring job executions, and integrating with tools like JIRA, PagerDuty, and Jenkins through plugins. Benefits of Rundeck include formalizing IT operations procedures, enabling self-service access for users, and providing visibility and logging of activities.
Artur Martins introduces himself and the presentation topic on Rundeck, highlighting his experience with the tool.
Discusses what Rundeck is, its features such as dashboards, access controls, and job scheduling, emphasizing formal IT Ops procedures and self-service dashboards.
Covers requirements for installing Rundeck, installation advice, remote node setup, and post-install configuration details.
Explains node definitions, configurations in YML format, and highlights caveats for managing nodes and authentication issues.
Provides links for further reading on Rundeck documentation, GitHub, and community resources, and invites questions.
WHO AM I?
•Name:Artur Martins (@arturmartins on twitter)
• Senior Systems Engineer at
• Using rundeck since April 2014
• I
3.
WHAT IS RUNDECK
•Operations Web Dashboard (and a REST API as well)
• fine-grain access controls
• builtin-job scheduler
• jobs can have multiple sequence steps and corresponde
error handling
• ability to define workflows (coordinated sequences
commands and scripts or jobs)
4.
FEATURES
• Import Nodeinfo from chef, puppet, amazon ec2, salt or make
your own CMDB/node list.
• Run multiple jobs or workflows in parallel
• Follow job executions running (distributed tail -f)
• Trigger 3rd parties using email or webhook
• Plugins available:
JIRA, PagerDuty, Slack, HipChat, Redmine, Puppet, salt, nexus, jenkins, chef, Nexus,AWS EC2 Nodes, Kerberos, IRC,
Jabber,AWS S3
CAVEATS
• Some charactersin password field might cause authentication to fail (/
etc/rundeck/realm.proprieties)
• Assure no spaces a the end of a value in any /etc/rundeck/* config
files
• Node filter is tricky if you want to select different nodes by multiple
parameters.Workaround: regex all the way.
• Be aware of rundeck rules for quotes escaping for commands:
http://rundeck.org/docs/manual/jobs.html#quoting-arguments-to-steps