cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1168
Views
0
Helpful
0
Comments
Orf Gelbrich
Cisco Employee
Cisco Employee
Task NameAdd VM file to vCenter inventory
DescriptionAdd VM file to vCenter inventory
Prerequisites
  1. Tested on 5.3
CategoryWorkflow tasks
ComponentsAdd VM file to vCenter inventory
  1. Log in to UCS Director as a user that has "system-admin" privileges.
  2. Navigate to "Policies-->Orchestration" and click on "Import".
  3. Click "Browse" and navigate to the location on your computer where the .wfdx file resides. Choose the .wfdx file and click "Open".
  4. Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
  5. Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
  6. Click "Submit".
  7. A new folder should appear in "Policies-->Orchestration" that contains the imported workflow.

Thank you goes out to Abhilash Pujari.

Testing on a VM:

Screen Shot 2015-04-24 at 12.28.30 PM.png

Grabbing the "almost" VM datastore path:

Screen Shot 2015-04-24 at 12.28.44 PM.png

Screen Shot 2015-04-24 at 12.28.59 PM.png

The path is:

        [UCSD_DS_SR_3724_San5] PRD-Rain1-01/PRD-Rain1-01.vmdk

        but the input for the task is this:

        [UCSD_DS_SR_3724_San5] PRD-Rain1-01/PRD-Rain1-01.vmx

Removing the VM from vCenter inventory:

Screen Shot 2015-04-24 at 12.29.26 PM.png

The workflow:

Screen Shot 2015-04-24 at 12.31.07 PM.png

The input with mouse over (description field):

Screen Shot 2015-04-24 at 12.31.30 PM.png

The resource selection:

Screen Shot 2015-04-24 at 12.31.45 PM.png

The input end product:

Screen Shot 2015-04-24 at 12.31.52 PM.png

The workflow execution:

Screen Shot 2015-04-24 at 12.33.06 PM.png

The machine is coming back:

Screen Shot 2015-04-24 at 12.32.30 PM.png

Funny little question popping up in vCenter (Need help on how to get ridd of this question, or it is because my vCenter is very old):

Screen Shot 2015-04-24 at 12.32.39 PM.png

Suggested possible solution to above VMware question:

It is caused by the Host it is running on having a different UUID that the last ESX host

I fixed it by making sure the service Profile for the ESX hosts have the same UUID

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links