Hi Anandh  I was in this same situation a few days ago in my lab environment. I’m afraid to say it did not work out to well.  You will need to completely remove all resources associated with that venter, then remove the venter itself and re-add it when it has the new name.  I’m open to correction, but during my testing there was no other way to do this.  Also on a side note, once you have resources added to vCenter to ViPR, same applies if you rename anything.  So if you rename a Datastore , DC , Hosts, ViPR does not pick up these changes and will cause all future resource deployments to fail, until you revert back to the older naming convention.  I couldn’t find a way to get ViPR to force a update of the vCenter resources / names / database entry’s.  Let’s hope this will be addressed in future releases of ViPR  Dave
I am setting up a new ViPR environment and will discover the storages and the ESXi clusters using vCenter. There are multiple ESXi cluster which is discovered using a single vCenter in the current environment. In future, the customer is going to move the vCenter to a newer vCenter environment and the ESXi clusters will be managed by different vCenter in the new environment.   The ESXi cluster and ESXi hosts remains the same, but the vCenter will change. How does this affects ViPR, is it just delete the old vCenter and add the new vCenter and all the ESX hosts are already visible under the respective new vCenters?
Change vCenter after it is discoverd in ViPR