Over the last week, I’ve been banging my head against the wall trying to figure out how to exactly approach the usage of this task in UCS Director. On the one hand, it works rather well. On the other hand, it’s nearly impossible to roll back the changes in which this task performs. This is mostly due to the inability to pass variables back and forth between the task and UCS Director.
I knew going into this that I’d have some issues with UCS Central due to the lack of built-in tasks in Director. I made it work, but unfortunately, I still have to manually clean up what my script does in creating a boot policy in UCS Central. The boot policy is central to allowing that blade to boot up properly to the SAN LUN I allocate and zone for that host. When I’m rolling back the entire server, I want all that information gone. Unfortunately, as I stated before, it’s a manual clean up afterwards since the boot policy was created by the PowerShell script, but none of the information about what was done was passed to UCS Director for proper cleanup.
I’ve put in a word with some of my contacts related to UCS Director at Cisco. I hope there could be some sort of ability to provide a rollback script section, similar to the way the Execute Network CLI task functions. At least at a minimum, it would provide the ability to rollback the changes done by some of the PowerShell scripts.
*** EDIT – I edited this post because I was able to finally find the UCS Director task related to connecting an ESX host to a distributed virtual switch. One of these years, I’m going to remember all the tasks that are available in the UCS Director task library. However, my point about what I had to do to get UCS Central components configured through PowerShell is still valid.