Automate Windows Azure Pack operations with Service Management Automation
You can use Service Management Automation (SMA) runbooks to automate routine operations in your Windows Azure Pack for Window Server environment. There are two distinct types of SMA runbooks:
|PowerShell Workflow||Text runbook based on Windows PowerShell Workflow.|
|PowerShell||Text runbook based on Windows PowerShell script.|
PowerShell workflow runbooks
PowerShell Workflow runbooks are based on Windows PowerShell Workflow. You directly edit the code of the runbook using the editor in the Management Portal. You can also use any offline text editor and import the runbook into SMA.
- Implement all complex logic with PowerShell Workflow code.
- Use checkpoints to resume runbook in case of error.
- Use parallel processing to perform multiple actions in parallel.
- Can include other PowerShell Workflow runbooks as child runbooks to create high-level workflows.
- You must be familiar with PowerShell Workflow.
- Runbook must deal with the additional complexity of PowerShell Workflow such as deserialized objects.
- Runbook takes longer to start than PowerShell runbooks since it needs to be compiled before running.
- PowerShell runbooks can only be included as child runbooks by using the Start-SMARunbook cmdlet which creates a new job.
PowerShell runbooks are based on Windows PowerShell. You directly edit the code of the runbook using the editor in the Management Portal. You can also use any offline text editor and import the runbook into SMA.
- Implement all complex logic with PowerShell code without the additional complexities of PowerShell Workflow.
- Runbook starts faster than PowerShell Workflow runbooks since it doesn't need to be compiled before running.
- You must be familiar with PowerShell scripting.
- You can't use parallel processing to perform multiple actions in parallel.
- You can't use checkpoints to resume runbooks when an error occurs.
- PowerShell Workflow runbooks can only be included as child runbooks by using the Start-SMARunbook cmdlet, which creates a new job.
How SMA executes runbooks
Requests to start a runbook are performed by the SMA web service using either the Service Management Portal, or the Start-SmaRunbook Windows PowerShell cmdlet. The web service writes this request to the Automation database where it is retrieved by one of the Automation Worker servers.
If the RunbookWorker property of the runbook is populated, then that Worker server will service the job. If the Worker server is not available, then the job fails with an error. If the RunbookWorker property of the runbook is not populated, then SMA randomly selects an available Worker server to service the request.
The Worker server creates a job that runs on the Worker server that services the request and remotely accesses any computers or other resources that it will work with. This requires the cmdlets in the runbook to be able to remotely access these resources. Alternatively, the runbook can include an InlineScript command in order to use PowerShell Remoting to run commands locally on a target computer. This concept is illustrated in the following diagram.
If a job is suspended or interrupted, it may be resumed on a different Worker server. Because of this, you should be careful about using local resources that are not accessible to all Worker servers such as a file on a local computer. You should leverage Global Assets such as Variables as much as possible for sharing information between checkpoints.
In order for a runbook to perform its required actions, it must have permissions to access the resources that it works with. Runbooks in SMA always run in the context of the service account of the Automation Runbook Service. If this account does not have required permissions, then you can use either a Credentials or a Connection global resource in your runbook to run required commands using credentials with the required permissions. These credentials can either be used with a cmdlet that accepts credentials through a parameter or with InlineScript to run a block of code using alternate credentials.