Create a job by defining a single step or a workflow that can execute any set of commands, scripts, or tools on any number of local or remote nodes.
Safely hand off the job to others to execute or follow the output -- depending on the permissions you give them. Collaborate with others and build your organization's library of repeatable and auditable actions.
Enjoy being the Hero. You've safely given Dev and QA teams access to self-service operations tasks (deployments, restarts, data management, etc). You've made collaboration with your Operations colleagues easier. You've improved everyone's visibility into Operations activity. Now you can spend less of your time fielding repetitive requests and more of your time doing new and interesting things that will further the business.
Build up a common set of reusable procedures. Share those procedures with others as executable code rather than error prone "do this, then that" text files or checklists.
Move towards Continuous Delivery by having your build or CI server trigger Rundeck to execute the post-build deployment process and deployment verification testing. Reuse those same jobs to deploy across all environments automatically (zero-click) or with a manual trigger (one-click).
Provide Dev and QA with self-service provisioning of test environments. Use Rundeck's option providers to allow users to select specific versions of artifacts to deploy. Pair with virtualization or cloud infrastructure to allow techniques like short-lived, branch-specific test environments.
Coordinate the lifecycle of a data processing job, including the provisioning and de-provisioning of the supporting cloud infrastructure. Rundeck's Web-UI and ACL policies enable you to safely delegate to non-technical users the ability to kick-off and view data processing jobs.
Build a custom Operations Platform that leverages Rundeck's full featured API. Integrate with other tools, build your own plugins, and build your own business-specific UI.
Prakash uses Rundeck to: 1. provide visibility into deployments in secure production environments 2. safely enable self-service capabilities that protect the capacity of the TechOps Team 3. improve the ease of patching and routine maintenance by leveraging a library of repeatable procedures.(read more...)