Feature #2288: Quota Support for RHEV 3.1 - Foreman

Feature #2288

Quota Support for RHEV 3.1

Added by Anonymous about 10 years ago. Updated over 9 years ago.

Status:

Closed

Priority:

High

Assignee:

Category:

VM management

Target version:

1.3.0

Difficulty:

medium

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

RHEV 3.1 has quota support. Unfortunately for a an account to work as a compute resource it appears it needs to have an Admin Role.

This means it sees all quotas, even those for which it is not a consumer.

When Foreman tries to provision, there is no way to select a quota, so the vm fails to provision with an error message like:
Failed to create a compute it-tower-finance (oVirt) instance test3: Cannot add VM. Quota is not valid

There needs to be a way to either select a quota for a compute resource account to use when provisioning, or to select a compute resource on the Virtual Machine tab when creating a new vm.

fog.patch	fog.patch	4.41 KB	fog Patch	Anonymous, 03/08/2013 01:32 PM
foreman.patch	foreman.patch	3.54 KB	Foreman Patch	Anonymous, 03/08/2013 01:32 PM
rbovirt.patch	rbovirt.patch	4.51 KB	rbovirt Patch	Anonymous, 03/08/2013 01:32 PM
add-quota-support.patch	add-quota-support.patch	4.8 KB	Patch to add quota support in Foreman 1.2	Anonymous, 06/28/2013 03:53 PM

Related issues

Associated revisions

Revision 180d7f43 (diff)
Added by Jason Montleon over 9 years ago

fixes #2288 - Add oVirt/RHEV Quota Support

History

#1 Updated by Anonymous about 10 years ago

Same issue looks to affect CloudForms if quotas are enabled: https://bugzilla.redhat.com/show_bug.cgi?id=905261

#2 Updated by Anonymous about 10 years ago

File fog.patch fog.patch added
File foreman.patch foreman.patch added
File rbovirt.patch rbovirt.patch added

Neil Miao and I were able to piece something together. I think it still needs some clean up for sure, but the patches below make it possible to select a quota when provisioning for both the vm and disk (they can be different).

If we can have the disk use the same quota as the vm I think that would be better from the user perspective as it means less drop downs, but I'm not sure how to get it to do that.

I also think it might still be better to have the compute resource always use the same quota when provisioning, but I'm not sure how to go about doing that either.

#3 Updated by Anonymous about 10 years ago

I created pull requests for rbovirt and fog. While my patch above for foreman 'works' I do not believe it is necessarily the right way, so I haven't create a pull request for it at this time.

#4 Updated by Anonymous about 10 years ago

Disregard this comment (spoke too soon.)

#5 Updated by Anonymous almost 10 years ago

File add-quota-support.patch add-quota-support.patch added

Since the patches are included in the new versions of fog and rbovirt to support quotas we are able to get quotas working with only the changes in add-quota-support.patch

I'm sure that it can be done better, but it has some redeeming qualities in that it has no negative impact if quotas are not enabled and do not exist, if they are enabled and exist you get a list of quotas, and if you name a quota and compute resource the same it will automatically select the like named quota for you. Anyway, support for quotas, even done better than we have, are probably a feature that could be easily added at this point.