Red Hat Bugzilla – Bug 1281927
[RFE][nova]: [VMware] Enable setting memory, disk and vnic limits
Last modified: 2016-08-24 08:52:24 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/vmware-limits.
Currently the VMware driver enables setting CPU limits and shares. The Blueprint extends that to enable setting the following limits: and shares:
- disk (http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.wssdk.apiref.doc/vim.vm.device.VirtualDisk.html)
- memory (http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.wssdk.apiref.doc/vim.vm.ConfigSpec.html#field_detail)
- vnic (http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.wssdk.apiref.doc/vim.vm.device.VirtualEthernetCard.html)
Specification URL (additional information):
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
Failed to verify:
1. Disk IO limit - passed.
2. Disk IO shares level - failed to boot an instance once disk IO share parameters were tested.
# openstack flavor show disksharelimit2
| properties | quota:disk_io_share_level='High', quota:disk_io_shares_share='850' |
| ram | 1024 |
Failed to boot instance Horizon reports -> Error: Failed to perform requested operation on instance "DiskShareLimit", the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available.].
3. 4. Network vif_limit & vif_share_level - can't test don't have prerequisites, see link . My vmware setup is 5.5u3 based not 6, without NSX/vdistributed switch, I don't see such NIC resource settings on VMware's side.
5. Memory limit - passed.
6. Memory shares level - failed to boot instance with these settings:
# openstack flavor show memorysharelimit
| properties | quota:memory_shares_level='high', quota:memory_shares_share='1740' |
| ram | 2048
Failed to boot instance, Horizon reports -> Error: Failed to perform requested operation on instance "memsharelimit", the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available.].
"There are not enough hosts" is a bit misleading.
On same deployment I was later able to boot up a few more instances with a duplicate flavor which didn't include memory share limits. So I had free resources yet when I try to boot an instance based on flavor which included disk or memory share limits I'd get same error.
Deployment remains up if any one wishes to retest/review this.
Packstack rhos9 (installed on Aug20)
vmware vcenter/esxi 5.5u3
Created attachment 1193305 [details]
Not sure how much this helps, check attached nova logs.
look for instance
780313c6-10d2-4d3a-8a92-42d8688d527c -> nova-compute.log
564a - - -] [instance: 780313c6-10d2-4d3a-8a92-42d8688d527c] Invalid input received: Share level 'high' cannot have share configured notify_about_instance_usage /usr/lib/python2.7/site-packages/nova/compute/utils.py:284
/var/log/nova/nova-compute.log:2016-08-23 13:49:22.325 24254 DEBUG nova.compute.manager [req-c536c99c-8b9b-40b7-a131-152ef78c02c6 09315ae5287a45d59ad6d5898f818ebf c2bc1778e6b94443a7e9732ab83d564a - - -] [instance: 780313c6-10d2-4d3a-8a92-42d8688d527c] Build of instance 780313c6-10d2-4d3a-8a92-42d8688d527c was re-scheduled: Invalid input received: Share level 'high' cannot have share configured _do_build_and_run_instance /usr/lib/python2.7/site-packages/nova/compute/manager.py:1945
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.