In this blog post, we will be discussing how to utilize the Cisco PowerShell Agent and the provide Cisco UCS Director task, Execute PowerShell Command. We will also go over what it’s going to take to parse the response of this task and retrieve information to be used as Cisco UCS Director variables for other tasks in our workflow.
Execute PowerShell Command
First things first, we need to create a new workflow to begin using this task. You can easily navigate to the workflow designer, by using the menu bars while logged in as an administrator. Navigate to the following location: Policies > Orchestration. Make sure you are on the Workflows tab. Create a new workflow from the menu options in these screens.
Once you’ve created the workflow, enter the Workflow Designer. Along the left side of the window, you should be able to see what sort of tasks are available to be placed in the designer. In the text entry field near the top, go ahead and enter the word “PowerShell”. You will find the Cisco created task under the Cloupia Tasks > General Tasks folder. Click on the task and drag it to the designer layout portion of the screen. Once you’ve done that, double click on the task to begin editing the task.
You can proceed right through the section for User Input Mapping, as we don’t have any sort of inputs we are assigning to required values of the task. Proceed to the “Task Inputs” section of the task edit process. You should see something like this:
As you can see, I have already entered in some of the values for this task. This looks very like what we had entered in the last blog post (Cisco UCS Director and the PowerShell Agent – Part 1). The only major difference is that there is a PowerShell Agent selection box. Populating this box is the different PowerShell agents we’ve registered with UCS Director.
One of the other major differences is that the screen has a rather lengthy scrollbar. Using the scrollbar, we can see that there are some other entries that can be made. For instance, you can perform a rollback of this task, in the form of calling upon another script. This comes in handy for cleaning up whatever was added or changed in your environment. As a good example, if you use PowerShell to perform operations in Cisco UCS Manager, when you rollback the workflow and remove those services, you would need to remove the changes you just made. If you create a service profile and associated it with a blade server, you’d want to disassociate the service profile and delete it when that service is no longer necessary.
Other key parts of the task inputs include these last options:
The task has the ability for you to specify how you want to handle the task output. Up until recently, the only output format that was available was XML. Since UCS Director 6.0 was released, the option to return the output in JSON format was introduced. The Depth option comes in handy for JSON format. The last component is the Maximum Wait Time. This is very important in determining how long you want UCS Director to keep an eye on this task before it automatically ends checking on the task. Before setting up this task, it’s highly recommended to see exactly how long you expect this task to take and account for some extra time.
Lastly, pay attention to this final output variable:
When it comes to parsing the output of the script, this is the value we need to pass to a parsing task to retrieve information for other UCS Director tasks in our workflow. Note that this comes back as UCS Director’s implementation of a generic text input object.
Parsing the Response
As recently as UCS Director 6.0, a new Cisco-created task was included in UCS Director called Parse PowerShell Output. This task is relatively decent at retrieving simple values from the returned text and creating a single UCS Director variable. To work with the task, drag the task into the Workflow Designer. Upon getting to the User Input Mapping section of the task, we need to map this value to the output of our Execute PowerShell Command task. You should be able to find it in the drop down menu when you select that you want to map this object to user input. It should look something like this:
In the output section, you’ll see the following values that should be available after processing the text we are giving to this task:
These variables will store parsed information from our PowerShell script and allow for us to use these values as inputs into other UCS Director tasks.
To be continued…
In the next blog post, we continue the discussion of how to send arguments to your PowerShell scripts…