The main use case that Alex and Kim discuss is using Rundeck and Salt to drive Salesforce.com's infrastructure provisioning procedures. Kim explained how operators used to deal with complicated run lists where there could be 12 or more steps, each with lots of sub-steps. They needed a way to remove the manual process and allow operators to push a button and get a fully provisioned host that is consistent and correct every time.
To handle the scale and complexity of their environment Salesforce decided to use Salt for remote execution and the dispatch of commands to servers. Above Salt, they use Rundeck to define the sequence of actions that need to take place in a particular workflow. To tie Salt and Rundeck together, Kim wrote the first Salt plugin for Rundeck. To make things even simpler for their operators, they created a custom web interface that is specific to Salesforce. An internal application called Kingpin provides security and configuration information. All together, they call this solution Gigantor. It's a great example of a flexible and scalable "loosely-coupled" toolchain design.
Watch the video for a more hands-on view…
Note: This demo video is with the older Rudeck 1.6 and not the new and improved UI of Rundeck 2.0.
comments powered by Disqus