Github user kmccormick commented on the pull request:
https://github.com/apache/cloudstack/pull/766#issuecomment-137155599
Regarding the upgrade scenario, I believe that this would not affect any
running VMs. Can anyone confirm? Besides just running VMs, it is still a
potential problem for an installation that is already near capacity, as the
upgrade would remove a little bit of capacity. For both issues, I think a
mention in the release notes would be sufficient. To keep the old behavior,
admins just need to add host.reserved.ram.mb=0 to their agent.properties file.
CPU I don't think is an issue, as memory is typically the limiting factor
in virtualization. If the CPU gets overly taxed, things slow down, where if all
the memory gets used up, VMs or other processes get killed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
