Roadmap

All current feature requests are tracked here but this page contains strategic project efforts.

High level goals

Rundeck is meant to be an operations console to define and manage automation in a cloud(y) environment.

Features

• Monitoring and statistics

  • Generate job execution data to a stats collection agent
  • Consume operational state about nodes from monitoring collection stations
  • Alarm response trigger Rundeck action (execute job or ad hoc command)

• Snippets

  • Bundles of boiler plate command strings searchable by description, too
  • Command completion in Run and Job composition pages
  • Snippets can come from ad hoc command history

• Workflow

  • Pluggable workflow steps
  • Data share between steps
  • Configurable queue and semaphore
  • Retry (w/ threshold), pre-, post-condition workflows
  • Job iteration and step concurrency

• Node execution

  • Part of project setup, configures to the compute service remote command execution service
  • Highlight filtered console output
  • Execution search include all output

• Node provider

  • Part of project setup
  • Plugin system to resource model source
  • Merging and mapping multiple sources
  • Columnar, filterable resource listings
  • Job-history generated tags
  • Tag predicates

• Standalone

  • “headless” mode – “dispatch” and “run” tools – requires support for exec’ing workflows outside of a running server context. Eases integration inside closed virtual environments like Vagrant

• Security

  • Simplified access control policy

• Help

  • Contextual help system in GUI

• Packaging

  • Debian, Solaris, Windows packaging and service management
  • Chef, Puppet support for installation

• Build

  • Simplified (and unified) build process and tooling