cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
875
Views
0
Helpful
0
Comments
Orf Gelbrich
Cisco Employee
Cisco Employee
Task Name

Advanced VM decommission with scheduling the decommission 14 days out

Description
Prerequisites

vCenter

CategoryWorkflow
ComponentsUCSD 6.6
User Inputs
Output

Instructions for Regular Workflow Use:

  1. Download the attached .ZIP file below to your computer. *Remember the location of the saved file on your computer.
  2. Unzip the file on your computer. Should end up with a .WFD file.
  3. Log in to UCS Director as a user that has "system-admin" privileges.
  4. Navigate to "Policies-->Orchestration" and click on "Import".
  5. Click "Browse" and navigate to the location on your computer where the .WFDX file resides. Choose the .WFDX file and click "Open".
  6. Click "Upload" and then "OK" once the file upload is completed. Then click "Next".
  7. Click the "Select" button next to "Import Workflows". Click the "Check All" button to check all checkboxes and then the "Select" button.
  8. Click "Submit".
  9. A new folder should appear in "Policies-->Orchestration" that contains the imported workflow. You will now need to update the included tasks with information about the specific environment.

Inspired by a large customer....

The idea is to create a new end user button to decommission a VM

Take away the power off and delete vm buttons and present a new decom. button

The 1st workflow sets up the 2nd workflow (14days later) to do the actual delete.

The trick is to keep track of certain VM information while the VM is being turned off (IP and back up IP)

The workflow will also clone the decom workflow and set up the schedule.

The decom. workflow will clean up the global variable and the schedule and the cloned workflow.

The first workflow setting everything up:

Screen Shot 2018-06-09 at 7.19.11 AM.png

Make sure the workflow is selected in the clone (mine is 809):

Screen Shot 2018-06-11 at 1.51.46 PM.png

In this task:

Screen Shot 2018-06-11 at 1.52.19 PM.png

Input select VM out of the VM context:

Screen Shot 2018-06-09 at 7.19.31 AM.png

Workflow run:

Screen Shot 2018-06-09 at 7.21.17 AM.png

The second workflow (final decom):

Screen Shot 2018-06-09 at 7.21.47 AM.png

Screen Shot 2018-06-09 at 7.22.00 AM.png

The wait task in here should be re-placed with the compound task / WF that does the

     AD cleanup

     DNS clean up

     Hand back IP to infoblox / IP mamangement

     Puppet clean up

Workflows before:

Screen Shot 2018-06-09 at 7.22.18 AM.png

Workflows after:

Screen Shot 2018-06-09 at 7.22.35 AM.png

Notice the new cloned workflow with host name attached.

Global variable created:

Screen Shot 2018-06-09 at 7.59.09 AM.png

Schedule created:

Screen Shot 2018-06-09 at 7.22.44 AM.png

Schedule with VM name input:

Screen Shot 2018-06-09 at 7.23.45 AM.png

Running the decom WF :

Screen Shot 2018-06-09 at 7.25.17 AM.png

Input is the VM name / host name:

Screen Shot 2018-06-09 at 7.25.25 AM.png

SR log entries:

Screen Shot 2018-06-09 at 7.26.08 AM.png

Decom WF run:

Screen Shot 2018-06-09 at 7.29.27 AM.png




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

Review Cisco Networking for a $25 gift card