Skip to content
ahonor edited this page Jul 19, 2011 · 19 revisions

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

Overarching goals

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

Functional areas

Monitoring and statistics

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

Snippets

Workflow

  • Pluggable workflow steps
  • Queue
  • Retry (w/ threshold), pre-, post-condition workflows
  • Job iteration and step concurrency

Node execution

Node provider

Non functional areas

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 (patrick dubois)

Security

  • Access control policy

Help

  • Contextual help system in GUI

Packaging

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