Question about Deprovisioning

[kbrowns]

We're currently using knife-vsphere and looking to move Chef Provisioning VSphere for a number of reasons with Test Kitchen support being one of the bigger ones. We use a series of knife-vsphere commands to deprovision machines in certain areas of the company where we're using a blue/green deployment model. One lesson we learned in doing this was that ip addresses handed out by via DHCP needed to be explicitly released prior to physically deleting the VM - otherwise the VLAN would leak addresses. We accomplished this by using "knife vsphere vm execute" on the guest.

Does the chef provisioning vsphere kitchen driver handle this in some way during it's destroy stage? I come from the app dev side of the house so networking details isn't my wheelhouse - is there a better way to solve this or avoid the leaking behavior?

Outside of kitchen destroy does Chef Provisioning VSphere support any form of deprovisioning of machines? Assuming no, would this be a desirable feature from a PR perspective?

[bradwilliamson]

Looks like there is a method in the driver.rb for this. I haven't tested it yet. I I may use a restricted account within vCenter & attempt it. But it looks doable.

https://github.com/CenturyLinkCloud/chef-provisioning-vsphere/blob/master/lib/chef/provisioning/vsphere_driver/driver.rb#L400

Have you attempted destroying/deleting & did it work?