Nick Huanca d5e5822ba8 Added case to reboot gracefully if toolsOld ... https://www.vmware.com/support/developer/converter-sdk/conv50_apireference/vim.vm.GuestInfo.ToolsStatus.html Having a response of tools_state == toolsOld is ok in my opinion since tools functionality doesn't change drastically revision to revision. Currently vSphere will force stop your assets if your vmware tools aren't up to date (even by one small revision). This behaviour is not optimal. The `tools_running?` check is only used in one place, the stop command in server.rb.		2015-09-29 10:35:06 -06:00
..
cluster.rb	[vSphere]: Add full path to cluster	2014-12-18 10:15:46 +02:00
clusters.rb
customfield.rb
customfields.rb
customvalue.rb
customvalues.rb
datacenter.rb
datacenters.rb
datastore.rb
datastores.rb
folder.rb
folders.rb
interface.rb	Replace deprecated Hash methods	2014-05-26 16:22:08 +01:00
interfaces.rb	[vsphere] Use the server_id in interfaces.	2014-07-15 15:08:25 -07:00
interfacetype.rb
interfacetypes.rb	Remove trailing blank lines	2014-05-26 14:35:26 +01:00
network.rb
networks.rb
resource_pool.rb
resource_pools.rb
scsicontroller.rb
server.rb	Added case to reboot gracefully if toolsOld	2015-09-29 10:35:06 -06:00
servers.rb
servertype.rb
servertypes.rb	Remove trailing blank lines	2014-05-26 14:35:26 +01:00
template.rb
templates.rb
volume.rb	Standardise on collection methods	2014-05-26 16:22:07 +01:00
volumes.rb	[vsphere] Use server_id in the Volumes collection.	2014-07-15 15:08:46 -07:00