i'm currently rolling vCloud Director and run into some strange issues. As you might know, in vCloud Director Provider vCDs use vSphere ressource pools. The problem is that if you temporarily disable DRS in vSphere all your ressource pools get lost, what happend to me. They seem not to be rebuild after re-enableing DRS. Now i'm stranded with some old provider vCDs without active ressource pools. However, i can't "change" those old vCDs and add new ressource pools since vCloud Director tells me something like "unable to change vCD settings because something is wrong with the vCD" - yeh, tell me something i don't know.
However: I then created new Provider vCDs and moved all ressources from the old provider to the new one. then I wanted to delete the old providers, which is impossible since they still have 1. a edge gateway and i can't delete the edge gateways since they have 2. a organisation network, which I can't delete because - well: it dosn't tell me why exacly (but no vm's, snapshots or vApps use that network!)
So, I deleted the edge and the network using vShield Manager and made sure nothing is left in vSphere as well. However: the stranded provieder vCDs still show up the network and the edge (which are not existent which is why I can't delete them )
Please note that those objects do not show up in the "stranded items" section, where a force delete would be possible. I just call them "stranded" because vmware is using this term for broken object links.
So, my question is qute simple: how do I forcefully remove a vCD Provider / Edge-Gateway / Org. network vom vCloud director if it's not showing up in the stranded section and normal deletion fails?
I was lurking around the VCloud SQL database but was unable to find the needed table entries. However, manually editing the SQL should be the LAST RESORT. I can't belive there is no way to force a object deletion.
Any ideas?
Chris Colotti has a blog about doing this very same thing. Hopefully you have support for this infrastructure as you're probably going to need calling in VMware reinforcements.
http://www.chriscolotti.us/vmware/gotcha-disabling-vmware-drs-with-vcloud-director/