Next Article +

Run Book Orchestration

Automate any data center IT workflow with PlateSpin Orchestrate

Written by Adam Spiers, Till Franke and Bill Tobey

Many Existing Successes

The combination of a highly capable tool set and a long list of low-hanging automation opportunities with significant ROI hasn’t gone unnoticed. The list of successful PlateSpin Orchestrate-based run book automation projects is already long and growing quickly. A few examples:

SAP Business Intelligence Accelerator failover – A German company with SAP BIA installations for disaster recovery located in two cities had a failover process so complex the run book ran to 40 pages of step-by-step instructions, with dependencies on both sides. Some steps had to be run on one server, others on up to 16. Using PlateSpin Orchestrate as the workflow engine, a group of Novell and HP engineers needed just two days to produce a proof-of-concept that automates the more complex steps on the infrastructure side, including storage system failover, SAP cleanup and restart.

Administrator password reset – When a system administrator leaves an organization it is standard practice to change the passwords on all systems, including some legacy resources that may only be powered up intermittently. PlateSpin Orchestrate is able to run predefined jobs on resources as they join the grid, including password resets. For one organization, this function alone justified the capital costs of PlateSpin Orchestrate deployment.

Service desk ticket enrichment – PlateSpin Orchestrate has been used to automate initial intelligence gathering on trouble tickets. When a new incident is reported, the ticketing system triggers a PlateSpin Orchestrate job to identify all systems associated with that service, run a support script on those services and append the results to the ticket. This is an example of an application in which the job script can acquire additional intelligence over time. It’s also an application that can benefit from the availability of a configuration management database.

Check system health – PlateSpin Orchestrate has been used in various applications to check specific measures of system health, and to automatically initiate remedial responses. Examples include checks for full file systems, and checks on various application and system processes.

Public key handling – PlateSpin Orchestrate has been used to automate the management of SSL/TLS keys for servers. A regularly scheduled job checks all systems for certificate validity, generates new certificate signing requests for those that are expiring, collects the CSRs and distributes new certificates. A similar process is used with SSH keys to automatically update known host and authorized key lists.

Orchestrate isn't just a hypervisor-agnostic VM manager. It originated in high-performance computing as an advanced grid management tool.

A Simple Job Script Sample: Baseline

Let’s take a look at a very simple example of the type of JDL script used to automate a workflow in PlateSpin Orchestrate. This illustration (See Figure 2.) is a basic configuration file management task you might use to ensure that a certain configuration file remains identical across a number of machines. This job can have two modes of operation. It can either do a check, which compares the file contents on all designated resources with a baseline version and reports all discovered differences for subsequent action. It can also take a more aggressive approach and simply overwrite any versions that have diverged from the baseline.

This job does three things:
  1. Job code running on the PlateSpin Orchestrate server retrieves the authoritative baseline file and copies it to the data grid, where it can be seen by all other resources.
  2. Joblets running on the targeted resources compare their own configuration files with the authoritative file contents (jobargs.mode == "put")
  3. If necessary, the joblets remediate any unwanted differences by replacing the divergent file with the authoritative version from the master server.

Now obviously, a simple script like this one will never threaten the livelihood of any entrenched configuration management tool. But if you harness this type of automation in a management environment where additional information about resource state, health, workload and events can be leveraged along with rules, policies and constraints, the possibilities for improving operational efficiency, reducing costs and enhancing service level performance become hard to ignore.

Run book automation offers an appealing entry-level automation target with short implementation cycles, fast ROI, limited integration complexity, and the opportunity to incrementally address workload optimization and other more complex implementations.

Find Out More

For more information on PlateSpin Orchestrate and its various applications in data center automation and virtual machine management, visit PlateSpin Orchestrate or contact product manager Jo De Baer at

Next Article +

Pages: Prev | 1 2 | Next Full Page
Novell Connection Magazine
Special Editions

© 2011 Novell, Inc. All Rights Reserved.