Bug 1041175 - [RFE][nova]: Add an admin-only API that allows setting VM resource quota at runtime
Summary: [RFE][nova]: Add an admin-only API that allows setting VM resource quota at r...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:51 UTC by RHOS Integration
Modified: 2019-09-09 14:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:02:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 13:51:26 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/admin-set-resource-quota-dynamically.

Description:

This blueprint is a supplement to Instance Resource Quota (https://blueprints.launchpad.net/nova/+spec/quota-instance-resource) supported by OpenStack from Grizzly. Instance Resource Quota is a static mechanism for cloud tenants to require precisely quantitative resources, while this new blueprint helps an administrator to effectively manage and utilize the cloud hardware resouces. In detail, this blueprint enables an admin to change physical resource allocation, CPU execution time, physical memory occupation, disk I/O bandwidth and priority, after VM instances have been created and in running. The benefits could be as the following:
    - The admin can use this runtime mechanism to change physical resource allocation, if a tenant over-claims resource quota when creating instances. But the instances themselves do not need to be terminated and re-created while resources changed;
    -  The admin can also use this runtime mechanism to dynamically adjust resource quota of instances during running according to the change of instance workloads and/or priorities.

Parts of this blueprint related with VCPU performance management have been implemented in our local OpenStack Grizzly deployment and work well.

Specification URL (additional information):

https://wiki.openstack.org/wiki/Admin-set-resource-quota-dynamically


Note You need to log in before you can comment on or make changes to this bug.