You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "rajujith (via GitHub)" <gi...@apache.org> on 2024/08/20 12:30:07 UTC
[I] Dynamic scaling improvement for VMware [cloudstack]
rajujith opened a new issue, #9555:
URL: https://github.com/apache/cloudstack/issues/9555
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VMware
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.19
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
Instance with dynamic scaling enabled.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Currently, dynamic scaling enabled instances get created at the vCenter with CPU and Memory hot add enabled but there is no user-friendly way to manage the limits. Some values get applied on the instances on vCenter and beyond that scale-up won't work.
It would be good to manage this better either by taking the limit value from the user to allowing the value to the updated through Cloudstack per instance.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Dynamic scaling improvement for VMware [cloudstack]
Posted by "rajujith (via GitHub)" <gi...@apache.org>.
rajujith closed issue #9555: Dynamic scaling improvement for VMware
URL: https://github.com/apache/cloudstack/issues/9555
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Dynamic scaling improvement for VMware [cloudstack]
Posted by "harikrishna-patnala (via GitHub)" <gi...@apache.org>.
harikrishna-patnala commented on issue #9555:
URL: https://github.com/apache/cloudstack/issues/9555#issuecomment-2306543585
@rajujith I'm keeping the notes below based on our discussion privately. If you agree for this, we can close the issue.
The "Limit" value is not related to the dynamic scaling or hot add feature. It is a setting for memory on a VM allows you to specify the maximum amount of memory that the VM can use, regardless of the amount of memory that has been allocated to the VM. If the utilization crosses the limit, then it will be swapped with disk.
The maximum value which anyone can dynamically scale the VM is 16times of the memory when the VM is started. This is given from the VMware documentation. https://knowledge.broadcom.com/external/article/343190/cannot-hot-add-more-than-3gb-to-linux-64.html
So setting limit value will not have any effect on the hot add limit.
For CS to provide a way to configure this limit I think it will degrade the VMs performance later at some point. If multiple VMs on the same host are configured with "Unlimited" memory limits and high memory allocations, this can lead to resource contention. If the host does not have enough physical memory to satisfy the needs of all VMs, some VMs might experience performance degradation or may need to swap memory to disk.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org