Closed myoung34 closed 10 years ago
I'll reopen this later to keep from flooding your email. The changes are becoming quite thick.
Also, you can't use the vagrant gem like this anymore.
$ bundle exec vagrant up --provider=ovirt
Vagrant appears to be running in a Bundler environment. Your
existing Gemfile will be used. Vagrant will not auto-load any plugins.
You must load any plugins you want manually in a Vagrantfile. You can
force Vagrant to take over with VAGRANT_FORCE_BUNDLER.
Vagrant.require_plugin is deprecated and has no effect any longer.
Use `vagrant plugin` commands to manage plugins. This warning will
be removed in the next version of Vagrant.
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.
The provider 'ovirt' could not be found, but was requested to
back the machine 'ovirtbox'. Please use a provider that exists.
@pradels Any plans on accepting this pull request and preparing a new release? I've tested these changes for some time now as they're needed when using oVirt 3.4 and they seem to work just fine
Sorry for no action for long time. We are not working on ovirt with vagrant in our company anymore. If anyone have time to continue developing this plugin, it would be great.
Can you delete your repository then so mine becomes the main fork?
Quite a few fixes. This allows it to work for sure with oVirt 3.1.0. Aside from that it also allows ssh options to be used in the Vagrantfile and a new option for Console to switch to 'vnc'