UPDATE 4/4/2013: Adding an example built under WFA 2.0. I haven't tested it fully because I wanted to make it available ASAP. If you run into any issues, please let me know. Thanks!
Hi all,
I created a ton of commands and a workflow that shows them off for configuring a new controller. Unfortunately, I couldn't go all the way to bare metal. This workflow requires the controller to already have an IP address and SSH enabled. Other than that, it can do the rest of the config for you. This met the needs of several customers looking for this level of consistent startup functionality. It's not perfect and you may need more or different actions for your builds, but it gives you a good idea of what's possible.
As it is, it's so large that it busted the 1.1.1 GUI for editing a workflow, and it's not like typical labs have a lot of unboxed systems that need deploying, but it does Preview nicely to give you a good feel for what you could do.
If you were to actually use this, you would need a Linux host to act as a "Jump Host" / software repository to store approved versions of OnTap software, firmware, disk firmware, SSH keys, etc.
Here's a flowchart of what the workflow does:

This sample workflow also contains a sample of using a function for mapping between small sets of data. There's a function called "DatacenterToDFMServer" that takes a datacenter name and returns the DFM server IP address for that datacenter.
Further, there's an example of creating your own object definition in this workflow as well. There's a custom "Ontap Security Admin Options" object definition that is used in a FindChart for defining the SSL parameters and for generating a custom SSL Certificate / Certificate Signing Request.
Finally, there are about 35 additional commands in the workflow specific for Day-0 automation. The commands use PowerShell cmdlets where possible, SSH as a second alternative. SSH is required on the DFM server for this example.
Have fun and looking forward to comments and questions.
Thanks,
Dave
*NOTE* Feb-11-2013 - PowerShell hashtables are no longer supported as WFA command parameters in WFA 2.0, so if you're trying to use these commands on a WFA 2.0 system, please use the other command attached for setting OnTap options. And, understand that each field in WFA 2.0 is limited to 256 characters. So, you may have to break up your list of options to set onto multiple workflow rows, as in the example. Once I have completed it, I will update the entire workflow example for WFA 2.0. Thanks and sorry for the inconvenience. Dave.