Update Vagrant to 2.0.3, unbork bundler.

[greut]

Hi,

The current setup complains about two little things.

• the protocol being insecure;
• and the gem being set up twice.

The git source `git://github.com/mitchellh/vagrant.git` uses the `git` protocol, which transmits data without encryption. Disable this warning with `bundle config git.allow_insecure true`, or switch to the `https` protocol to keep your data secure.
Your Gemfile lists the gem vagrant-cloudstack (>= 0) more than once.
You should probably keep only one of them.
While it's not a problem now, it could cause errors if you change the version of one of them later.

[!] There was an error parsing `Gemfile`: You cannot specify the same gem twice coming from different sources.
You specified that vagrant-cloudstack (>= 0) should come from source at `.` and source at `.`
. Bundler cannot continue.

 #  from /home/yoan/soft/vagrant-cloudstack/Gemfile:19
 #  -------------------------------------------
 #  group :plugins do
 >    gem 'vagrant-cloudstack', path: '.'
 #  end
 #  -------------------------------------------

I've also upgraded Vagrant to 2.0.x and managed to start/ssh/destroy a machine with it.

Best,

[coveralls]

Coverage remained the same at 88.293% when pulling 3312d48 on exoscale:vagrant2 into 9704968 on MissionCriticalCloud:master.