Workflow Example: (C-mode) Remove a vServer and its volumes

by Frequent Contributor on ‎2012-07-17 12:20 PM

I created this workflow as a 'complement' to Workflow Example: (C-mode) Create new vServer and volumes. Where that workflow will create vServers and volumes, this workflow will pretty much tear that all down.  This workflow will find the vServer on the cluster you select and will Unmount, Offline, and Destroy all of the vServer volumes, then go and destroy the vServer itself.  Did I mention this is pretty destructive?  Please use CAREFULLY.  This workflow is very straightforward and it has a couple of other capabilities in it that can be useful as examples for other workflows (staggered user inputs & looping based on finder values).  More specifics:

User Inputs:

  • Select from the available Clusters in your environment (pulled from an OC UM 5.0 or 5.1 datasource and LOCKED)
  • Select the vServer to remove on the selected cluster (only vServers of type 'cluster' are listed)
  • Screenshot:

WFA: 1.1.1.22.5 B7752

Hope you find this useful!

Comments
Frequent Contributor

Hi Kevin,

thank you very much. That helped.

Best regards

New Contributor

This looks like exactly what I need for an automation project I am working on, but I am unable to import this workflow into WFA 2.0.0.391.2.  I believe the problem is related to this workflow being exported from WFA v1.1 and differences in the format or content of the exports between WFA versions.  Can you provide advice on how I can make use of this workflow in WFA v2.x?  Do I need to install WFA 1.x, import and then update to WFA 2.x?

Thanks!

Frequent Contributor

Calvin,

I would not recommend importing that workflow as is for 2 reasons:

1) It is using the old form rather than the simplified form (Which is far more efficient from various perspectives).

2) Some of its components were already made certified in 2.0/2.0.1 (Which was just released).

Looking at the error happening on import, it seems related to item #2 (We already have "Remove CM Volume" certified in 2.0.1 - It was not supposed to collide but somehow it does).

I took the liberty of doing the process and making a small adjustment (Renaming said command) and now it imports successfully.

With that said, I highly recommend to recreate this workflow (Once you'd be able to import it you'd see it is very simple) using the new simplified form and all the latest certified content.

Let us know if you need further assistance. Kindly try this new one (_mod) attached above.

Cheers,

Yaron

New Contributor

Thanks Yaron! I appreciate your advice and the time you took to convert this so it could be imported into 2.x.  This is a much simpler workflow than I had imagined.

Frequent Contributor

You are welcome :-)

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.