Comments on: CloudCleaner

By: Jeff Jones

Jeff Jones — Mon, 01 Apr 2013 17:25:21 +0000

Thanks for this cleaner. It worked very well. The only minor addition that may help is staggering maintenance mode for the hosts as they have the vCD agent removed.

By: Ted Laurent

Ted Laurent — Thu, 31 Jan 2013 20:24:10 +0000

It would be great if this were updated to work with vCloud Director 5.1. A utility that directly allows someone to edit the cell would be cool too.

By: Mike

Mike — Tue, 08 Jan 2013 18:23:18 +0000

SSH needs to be running on the host

By: Rajesh

Rajesh — Fri, 04 Jan 2013 09:42:49 +0000

Hi, I want to migrate aroud 700 vm’s from one vcloud to another. The number is huge so vcloud connector won’t suffice. It would have been great if this cleaner tool could just remove the vcloud entires like agents etc instead of deleting the VM’s themselves. That way I could have just added the VC/hosts/datastore to the new vcloud and imported the existing VM’s without enabling customization.

By: Larry

Larry — Fri, 12 Oct 2012 02:06:59 +0000

I ran the cleaner, got prompted for the credentials of my host, entered them, and got a connection failed. I then logged in with the VI client to the host with the same ROOT credentials to test access and was able to log in fine. vcCleaner just keeps prompting for host credentials when I know they are correct. Any suggestions?

By: Jim Owens

Jim Owens — Wed, 03 Oct 2012 03:46:05 +0000

I downloaded and ran the tool because I have a network pool that shows in my vcd inventory, but does not exist. I wanted to delete this network pool or maybe just the label that shows up in vcd. The only thing the cleaner shows is my 3 hosts assigned to vcd. Am I using this tool wrong?

By: Larry

Larry — Fri, 14 Sep 2012 18:37:47 +0000

I want to remove VM’s from vCD and then remove vCD keeping the VM’s intact. Is this possible?

By: Piet Kiekebos

Piet Kiekebos — Tue, 19 Jun 2012 10:02:28 +0000

Doublecheck filelist!!! Even in vCD created mode. View replica disks and View user disks need to be removed from list. Remove all ESX hosts ecept one and run cleaner. Run for each host seperate.

By: Luke

Luke — Tue, 28 Jun 2011 17:35:07 +0000

Heh! The log messages are perhaps a little confusing at first, sorry about that. The scanning engine is separate from the work engine in CC, which is why there is the second scan. You can think of the first scan as “SCAN:FIND” and the second as “SCAN:REMOVE”. This makes it easy to add / modify worker engines in the future. You’re absolutely right, though, the scanner could be made smarter. I will add that to the TODO list.

By: Luke

Luke — Tue, 28 Jun 2011 17:26:30 +0000

Future versions of the vCD agent are requiring that the host be put into maintenance mode before uninstalling, so that’s why CC does that. I’m working on fine-tuning that feature.