Mar 11

Software-Defined Storage with NetApp and VMware – Part 2: Setup vCO to Call WFA Workflows

In this part of my series we’ll be discussing setting up vCO to call WFA workflows. I will not be discussing installing vCO, as I am using vCAC 6 and it has a built-in vCO 5.5 environment already. You’ll need to have WFA 2.1 setup as well as vCAC 6 setup and configured. Let’s dive into the process. In order to use the new OnCommand Workflow Automation package, the vCO server must be configured to support the WFA environment. Follow the steps to install the HTTP Rest Plug-in, configure the SSL connect to WFA and import the package. The first thing you’ll need to do is to start the vCO configuration service on the vCAC 6 appliance. Follow the below instructions to perform this step.

  1. SSH into your vCAC 6 appliance and enter the appropriate username and password for the appliance.
  2. Next, run the following command at the prompt: service vco-configurator start. (Note: This command turns on the vCO configuration service, which is not started by default on the vCAC 6 appliance) clip_image004.jpg clip_image002.jpg
  3. Once you’ve entered this command you will now be able to access the vCenter Orchestrator Configuration page.
  4. Next, go to the FQDN of your vCAC 6 appliance. Then click the vCenter Orchestrator (vCO) Configurator at the bottom. clip_image006.jpg
  5. When in the vCO Configurator click Network and then go the SSL Trust Manager Tab.clip_image009.jpg
  6. Enter the FQDN or IP address of the WFA 2.1 server and click Import to import the WFA SSL Certificate.clip_image012.jpg
  7. While at this page, also import the vCenter server SSL using the step above.

Once this is done you will now need to download and install the NetApp WFA Package for vCO. Follow the steps below to complete this step.

  1. Download the NetApp WFA Pakcage for VMware vCenter Orchestrator from here.
  2. Open the vCO client. At the below screen click on Import package.clip_image015.jpg
  3. Select the package to import.
  4. Click Import at the Package Import Information screen. clip_image019.jpg
  5. Click on Select/Deselect all at the bottom to be sure all elements are selected and then click Import selected elements.clip_image021.jpg

Lets take a quick look around the NetApp WFA Package for vCO.  The package imports several specific items that you will be using in the future to access and call WFA workflows.

  1. Under Design at the workflows screen a series of NetApp workflows will have been added under Library > NetApp > OnCommand WFA. Pay special attention to the workflow “Get WFA Workflow Inputs” as this will be used in the future for creating retrieving the WFA inputs needed to create vCO workflows to call WFA.clip_image023.jpg
  2. In the Design section under the Packages heading you will also see that com.netapp.oncommand.wfa has been added.
  3. In the Design section under the Actions heading you will also see that com.netapp.oncommand.wfa has been added and has multiple actions added. These are used when creating workflows to access WFA (which will be discussed in another part in the future). clip_image027.jpg

Now its time to set the values in the NetApp WFA User Configuration entry. In the Design section under the Configuration heading you will see a NetApp folder.  This is where we begin that process.

  1. Go to NetApp > OnCommand WFA and select NetApp WFA User Configuration. Click on the Edit button.clip_image029.jpg
  2. Under the Attributes tab input the information for the WFA username, password, and IP address (or hostname). Then click Save and Close. clip_image031.jpg

Now we have everything setup and ready to go. However, if you are like me you will now want to test the connection. Start this process by going to WFA and selecting a workflow you would like to test against.  Then begin the test process below.

  1. Under Design at the Workflows tab go to Library > NetApp > OnCommand WFA. Right click on “Get WFA Workflow Inputs” and click Start workflow. clip_image033.jpg
  2. At the Start Workflow: Get WFA Workflow Inputs screen enter the WFA Workflow name you would like to test against. In this case, I chose “Add QoS Policy to NAS Datastore” workflow. clip_image035.jpg
  3. Let the workflow run. When it is finished a workflow completed message will be displayed. clip_image037.jpg
  4. To view the workflow Inputs needed for to create a vCO workflow to access this WFA workflow, look in the Logs section.
  5. Here you will see a series of User Inputs that are numbered starting at #1. These are the inputs you will need for creating a vCO Workflow to match the WFA workflow.

I’ve mentioned creating vCO workflows several times. Don’t worry, I’ll be walking you through how to do this in my next blog entry. As always, thanks for reading and feedback is always welcomed.

Here are the links for the Software-Defined Storage with NetApp and VMware series:

As always I’d love to get your feedback and hear what you’d like to see.  Workflow ideas, blog post ideas, and general comments are all welcome.

Thanks for reading!


Share Button

4 pings

  1. Software-Defined Storage with NetApp and VMware – Part 1: Setup WFA » McCloud on Cloud

    […] Software-Defined Storage with NetApp and VMware – Part 2: Setup vCO to Call WFA Workflows » […]

  2. Software-Defined Storage with NetApp and VMware – Overview: vCAC 6, vCO, and NetApp WFA » McCloud on Cloud

    […] Software-Defined Storage with NetApp and VMware – Part 2: Setup vCO to Call WFA Workflows […]

  3. #38 McCloudOnCloud & the SDDC – Datacenter Dude

    […] PART 2 […]

  4. Using the NetApp OnCommand WFA package for vCO | The Practical Administrator

    […] of configuration (adding the WFA host name and credentials), but that’s it. Jack has a couple of posts that do an excellent job of describing the setup process on his […]

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>