Fix exception if listing raw vSphere volumes (thinProvisioned method missing)
[aws|dns] omit ttl for alias records
[vsphere] fix broken detection of existing network interface type
[Brightbox] Extract to provider module
Add fence_mode to network model

fence_mode can be 'isolated' (disconnected from EdgeGateway) or
'natRouted' (connected to NatService on EdgeGateway).

The network types differ significantly enough to have a separate
set of tests, to be expanded later.
Ensure get_network_complete mock returns like API

Booleans were being passed through unaltered. The API
returns them as strings, and in Real mode we do not post-process
them into boolean types.

Update so that booleans are returned as strings, as per
Real mode.
Add is_shared attribute to network Model

is_shared reports whether a network is shared across all
vDCs within an organization, or just within the vDC it is defined in.
Update getting_started.md

Added missing Ruby versions.
Update to attempt to alleviate confusion between Directory.new and get.

May want to have Directory metadata load only on #each instead of #get
Removing superfluous markup
Incorporated feedback from @mikhailov
[aws/security_group] update mock search and revoke

* update #normalized_permissions to work with GroupId
* fix #describe_security_groups ip-permission.group* filters
Merge pull request #2715 from fog/rackspace_storage_docs

Update to attempt to alleviate confusion between Directory.new and get.
[GH-2630] Bring in Minitest

This adds Minitest as a dependency and replaces the old `rake test`
by a Rake test runner.

Travis now includes the Minitest run before the Shindo run
[aws/compute] delete_security_group mock fixes

* mock delete failures when instances are present
* fix mock describe_instances by group-id
Merge pull request #2717 from fog/add_minitest

[GH-2630] Bring in Minitest
[core] Deprecate Fog::Connection

This reapplies the deprecation warnings that were originally part of
7ee3535 when using Fog::Connection request.

Unfortunately the Mock world does not exercise any of the code affected
by this change so I missed that I had adjusted the signature of the
method.

If you pass a parser argument into Fog::Connection you should switch to
using Fog::XML::SAXParserConnection and pass the parser as the first
argument to `#request`

If you don't it is better to use Fog::Core::Connection to get rid of the
backwards compatibility code and XML dependency.

This will make fog VERY NOISY since you'll get output for every request
on out of date services.
[GH-2711] Add Fog::XML::Connection

Attempting to move to using Fog::XML::SAXParserConnection directly
failed because the arguments changed.

This adds another compatibility level with two key differences:

1) It's namespaced within XML so stands out as not being part of core
2) It is NOT creating deprecation warnings so can be used as the final
   step if rewriting to use SAXParserConnection is undesired

So when merged Fog::Connection usage will create noise.

Fog::XML::Connection works the same way and will be extracted to
"fog/xml" when we get to it.

Fog::Core::Connection just wraps Excon.request and leaves the response
body parsing to the provider.
[GH-2711] Replace Fog::Connection with XML shim

Unlike last attempt this replaces Fog::Connection with
Fog::XML::Connection which should be directly compatible.

Fog::Connection is there for old PRs but should be removed real soon.

Providers using JSON should be able to replace "XML" with "Core" within
their code to cut down on the dependency.

If I get the time I may attempt to clean up some but testing with Mock
will mean that is mostly educated guesswork.
Merge pull request #2716 from engineyard/firewall-in-use

[aws/security_group] update mock search and revoke