-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFE] Ability to configure various libvirt VM parameters #92
Comments
Patches definitely welcome. As for RAM/CPU's, @goern started this patch in: #84 but then gave up. Please feel free to write it from scratch or fix his. It should be straightforward. As for additional HDD's, I actually wrote this feature in vagrant-libvirt, so I'm happy to get it in OMV :) You can look at this: https://github.com/purpleidea/puppet-gluster/blob/master/vagrant/Vagrantfile#L483 for how to add disks, assuming the interface hasn't changed. HTH, |
PS: technically OMV works with virtualbox now too. So bonus points if your patch adds the virtualbox hooks, although I won't nack the patch if you don't have them. |
TBH I did not use VirtualBox for like 7 years now and have no idea how stuff works there this days. Though this does not look like a bad idea to make RAM/CPU/HDD adjustments unified, I will poke around in that direction. Patch in #84 looks reasonable (well, goern@f2186d5 at least), so I'll use it as a basis for my work, thanks James for pointing that out. |
On Fri, May 29, 2015 at 12:27 PM, br0ziliy notifications@github.com wrote:
I don't use virtualbox either. Libvirt works so much better! Feel free to |
@br0ziliy ping, still planning on doing this? Cheers! |
Hey James, Yes, sure - was just a bit busy during RH Summit times. I'm definitively on On Thu, Jul 2, 2015 at 12:54 PM, James notifications@github.com wrote:
Vasiliy Kaygorodov |
Just added: 92dd418 This should meet everything but the disk configuration aspect. I'll close this ticket for now, until someone actually wants to submit a patch for the disk part. Please test and confirm this works! I've also tagged this release as 0.0.16 and a COPR build exists too: Cheers! |
cc @aweiteka @scollier @flavio-fernandes Thanks! |
@purpleidea Thanks for implementing this - works like a charm (tested with vagrant-libvirt) |
@br0ziliy YW! enjoy |
I miss the below functionality in OMV:
I saw some code blocks related to the HDDs, and also don't see any issues about adding RAM/CPU parameters to the omv.yaml and have Vagrantfile modified accordingly.
Does it worth looking at, or there're some strong reasons why it's still not implemented?
If the only reason is lack of time - I can try to come up with a patch.
The text was updated successfully, but these errors were encountered: