Skip to content
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

Closed
br0ziliy opened this issue May 29, 2015 · 10 comments
Closed

[RFE] Ability to configure various libvirt VM parameters #92

br0ziliy opened this issue May 29, 2015 · 10 comments

Comments

@br0ziliy
Copy link
Collaborator

I miss the below functionality in OMV:

  • ability to adjust number of CPUs/set RAM size for a VM
  • ability to assign additional HDD(s) to a VM

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.

@purpleidea
Copy link
Owner

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,
James

@purpleidea
Copy link
Owner

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.

@br0ziliy
Copy link
Collaborator Author

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.

@purpleidea
Copy link
Owner

On Fri, May 29, 2015 at 12:27 PM, br0ziliy notifications@github.com wrote:

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.

I don't use virtualbox either. Libvirt works so much better! Feel free to
ignore those additions. We'll open an issue for that feature and have a
virtualbox user add that in later.

@purpleidea
Copy link
Owner

@br0ziliy ping, still planning on doing this?

Cheers!

@br0ziliy
Copy link
Collaborator Author

br0ziliy commented Jul 2, 2015

Hey James,

Yes, sure - was just a bit busy during RH Summit times. I'm definitively on
it though - it's just the time that is the matter.

On Thu, Jul 2, 2015 at 12:54 PM, James notifications@github.com wrote:

@br0ziliy https://github.com/br0ziliy ping, still planning on doing
this?

Cheers!


Reply to this email directly or view it on GitHub
#92 (comment)
.

Vasiliy Kaygorodov
System Administrator

@purpleidea
Copy link
Owner

@br0ziliy @goern

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:
https://copr.fedoraproject.org/coprs/purpleidea/oh-my-vagrant/

Cheers!

@purpleidea
Copy link
Owner

cc @aweiteka @scollier
Please test... ^^^^

@flavio-fernandes
Can you confirm this works on virtualbox.

Thanks!

@br0ziliy
Copy link
Collaborator Author

@purpleidea Thanks for implementing this - works like a charm (tested with vagrant-libvirt)

@purpleidea
Copy link
Owner

@br0ziliy YW! enjoy

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants