OpenNebula
Extend quota subsystem
Author Name: Tino Vázquez (Tino Vázquez) Original Redmine Issue: 3210, https://dev.opennebula.org/issues/3210 Original Date: 2014-09-29
Allow an admin to control per user/group: a) ratio of CPU:VCPU b) io rate limiting per disk per datastore (with 4.8 we can set a default for all disks, on all datastores, for all users) c) nic bandwith (QoS) per nic
As well the ability to control per user/group: a) max VCPU per VM b) max MEMORY per VM c) max NICs per VM
Original Redmine Comment Author Name: Stefan Kooman (Stefan Kooman) Original Date: 2017-01-05T17:45:51Z
I would like to add the following to the list of quota's:
NETTX / per time period NETRX / per time period
Per VM and per User / Group. As soon as a VM / User / Group would hit this quota, an event (hook?) could be triggered to take appropriate measures, i.e. 1) poweroff VM, 2) Send alert to user, and prevent any other VM's being created.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. The OpenNebula Dev Team
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
- We can limit VCPU with generic quotas, not the CPU:VCPU ratio
- Disk IO rate is limited by attributes: TOTAL_BYTES_SEC, TOTAL_BYTES_SEC_MAX_LENGTH, TOTAL_BYTES_SEC_MAX, READ*, WRITE* . These can be specified as kvm defaults, per Cluster, per Host or for each VM->DISK
- default configuration doesn't allow to specify it per Datastore, you need to add these attributes to oned.conf INHERIT_DATASTORE_ATTR to define them per Datastore
- Network bandwidth can be set per NIC or inherited from VNET, attributes: INBOUND_AVG_BW, INBOUND_PEAK_BW, INBOUND_PEAK_KB, OUTBOUND_AVG_BW, OUTBOUND_PEAK_BW, OUTBOUND_PEAK_KB
- We are not able to limit max VCPU, MEMORY and NICs per VM
