Glenn Sarti df783f0ed0 (POOLER-52) Use a Connection Pooler for vSphere connections ... Previously the vSphere Provider would share a single vSphere connection for all pools under management. This would cause issues in large environments as this would cause errors to be thrown or operations to slow down. This commit modifies the vSphere Provider to use a connection pool when communicating with the vSphere API - Uses the GenericConnectionPool object to manage the connection pool - Uses a default connection pool size of: Whatever is biggest from: - How many pools this provider services - Maximum number of cloning tasks allowed - Need at least 2 connections so that a pool can have inventory functions performed while cloning etc. - A large connection_pool_timeout is used as a connection object is consumed during a VM clone, which can take up to 2 minutes - Removes the `get_connection` method as that is now obsolete due to the connection pool - Removes the `close` method as it is now obsolete - Modified the spec tests slightly, to stop mocking get_connection as it no longer exists, and set a super low pool timeout so that if a test fails, it will fail quickly instead of taking the default time of 60+ seconds		2017-05-17 13:52:28 -07:00
..
base_spec.rb	(POOLER-70) Update base VM provider	2017-05-17 13:52:27 -07:00
dummy_spec.rb	(POOLER-52) Modify dummy provider to use a connection pool	2017-05-17 13:52:28 -07:00
vsphere_spec.rb	(POOLER-52) Use a Connection Pooler for vSphere connections	2017-05-17 13:52:28 -07:00