This repository has been archived by the owner on Mar 18, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 46
Local Vagrant environment for portable integration testing #43
Comments
This is me ^ forgot to switch accounts when drafting up the issue. |
Closed
This would be useful for testing. Do you know if it'd work with KVM on Linux too? |
Hi @alexellis, in theory it should be fine with vagrant-libvirt plugin and the libvirt provider (I haven't tried it myself). More info here: https://github.com/vagrant-libvirt/vagrant-libvirt. I could see adding something like this in the Vagrantfile: config.vm.provider "libvirt" do |lv|
lv.cpus = 4
lv.memory = 1024
...
end then to trigger it would be: |
Liking this so far, I have left a couple of comments, I think we can probably make things a little more generic. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since this feature doesn't quite fit the issue template, I'll outline it below:
Provide a portable Vagrant environment via Vagrantfile that can:
Discussed briefly with @nicholasjackson, but wanted to track it.
The text was updated successfully, but these errors were encountered: