Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VIO Changing allocation ratios (76886)

Last Updated: 3/31/2022Categories: How toTotal Views: 3185Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

OpenStack allows you to overcommit CPU and RAM and DISK on compute nodes. This allows you to increase the number of instances running on your cloud at the cost of reducing the performance of the instances.

Note:  You must select the appropriate CPU and RAM and DISK allocation ratio for your particular use case.

Resolution

SSH to primary

Run the following command to open up vi and the virtual nova configuration file which is in YAML format. After the change is performed in the nova CR make sure to run the same steps in nova-compute:

viocli update nova

Add a new section header called DEFAULT and add the specific allocation ratio under it.

Note:  Formatting matters so here is what the file will look like with this addition

conf:
nova:
DEFAULT:

cpu_allocation_ratio: 10
ram_allocation_ratio: 1.5
disk_allocation_ratio: 1.5

neutron:
metadata_proxy_shared_secret: .Secret:managedencryptedpasswords:data.metadata_proxy_shared_secret
vmware:
passthrough: true
tenant_vdc: true

Save the file.

Note:  Saving the file will trigger LCM to update the nova services.  You can observe by tailing the tiller log (kubectl -n kube-system logs -f -lapp=helm) and running pods to watch the destruction of the old pods and creation of the updated pods.  The changes should be applied in less than a few minutes.

Run the following to check deployment is in running status.

viocli get deployment

root@oms [ ~ ]# viocli get deployment
PUBLIC VIP      PRIVATE VIP       HIGH AVAILABILITY
...
OpenStack Deployment State: RUNNING

Once the changes have been applied we can view them by exec-ing into the nova-api-osapi* pod and checking /etc/nova/nova.conf.

pods | grep -i nova-api
root@oms [ ~ ]# pods | grep -i nova-api
openstack            nova-api-metadata-684b7fb449-nz577                                1/1     Running             7          95d
openstack            nova-api-osapi-cb5bcb5b7-knbcl                                    2/2     Running             6          95d

root@oms [ ~ ]# osctl exec -it nova-api-osapi-cb5bcb5b7-knbcl /bin/bash
Defaulting container name to nova-osapi.
Use 'kubectl describe pod/nova-api-osapi-cb5bcb5b7-knbcl -n openstack' to see all of the containers in this pod.
[root@nova-api-osapi-cb5bcb5b7-knbcl /]#

[root@nova-api-osapi-cb5bcb5b7-knbcl /]# grep -i allocation_ratio /etc/nova/nova.conf
cpu_allocation_ratio = 10
ram_allocation_ratio = 1.5
[root@nova-api-osapi-cb5bcb5b7-knbcl /]#

Note:  If the changes aren’t applied, check the status of the osdeployment pod. If it is in init state for more than 15 or so seconds it may need to be destroyed manually (ie osdel po osdeployment-osdeployment1).

Related Information

The default allocation ratios are as follows.
cpu_allocation_ratio = 10
ram_allocation_ratio = 1.5
disk_allocation_ratio = 1

openstack allocation candidate list --os-placement-api-version 1.10 --resource VCPU=1 --resource MEMORY_MB=2048 --resource DISK_GB=20

+---+----------------------------------+--------------------------------------+----------------------------------------------+

| # | allocation | resource provider | inventory used/capacity |

+---+----------------------------------+--------------------------------------+----------------------------------------------+

| 1 | VCPU=1,MEMORY_MB=2048,DISK_GB=20 | a3067051-af36-4f37-b088-69a4caaf6dbf | VCPU=3/40,MEMORY_MB=1536/36862,DISK_GB=3/699 |

| 2 | MEMORY_MB=2048,VCPU=1,DISK_GB=20 | bf194dc9-aee1-4526-9ed6-2a48ebb110f7 | VCPU=0/80,MEMORY_MB=0/73725,DISK_GB=0/699 |

+---+----------------------------------+--------------------------------------+----------------------------------------------+

[root@vioadmin1-vioshim-6dbdb59f56-mq7lb /]# openstack resource provider list

+--------------------------------------+-------------------------------------------------+------------+

| uuid | name | generation |

+--------------------------------------+-------------------------------------------------+------------+

| bf194dc9-aee1-4526-9ed6-2a48ebb110f7 | domain-c20.4b5b07bd-3fb5-4f03-a7d5-a38280f3cc3b | 6 |

| a3067051-af36-4f37-b088-69a4caaf6dbf | domain-c8.5e82ed7a-604f-4f1b-91de-0997fe708fff | 14 |

+--------------------------------------+-------------------------------------------------+------------+

[root@vioadmin1-vioshim-6dbdb59f56-mq7lb /]# openstack resource provider inventory list a3067051-af36-4f37-b088-69a4caaf6dbf
Password:
+----------------+------------------+----------+----------+-----------+----------+-------+
| resource_class | allocation_ratio | max_unit | reserved | step_size | min_unit | total |
+----------------+------------------+----------+----------+-----------+----------+-------+
| VCPU           |             10.0 |        8 |        0 |         1 |        1 |    16 |
| MEMORY_MB      |              1.5 |    20479 |        0 |         1 |        1 | 40958 |
| DISK_GB        |              1.0 |      670 |        0 |         1 |        1 |  1199 |
+----------------+------------------+----------+----------+-----------+----------+-------+

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
已启用 "仅压缩" 的磁盘达到100% 的已满 (81071)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
送信メール サーバを構成すると、「テスト接続に失敗しました (Test connection failed)」というメッセージが表示される (76868)

KB
•
在 vRA 扩展设置中初始化群集时替换证书失败 (76863)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Integrated OpenStack

Related Versions:

VMware Integrated Openstack 7.x

VMware Integrated OpenStack 6.x

Take Our Survey

Support Assistant