Headline:
Adjust the way Morpheus applies Custom Plans so the CPU, cores per socket, and Memory stay at the current configured value for a VM instead of adjusting back to 1
Description:
Currently, when you adjust from one Custom Plan to another Custom Plan, Morpheus reverts the total CPU count and Memory back to 1, instead of keeping things default to what the current Instance has. This has proven problematic as we use custom plan options as a way to determine a DR tier level as that reconfigure kicks off workflow automation tasks we can use for various backend adjustments.
Unfortunately, we’ve experiences several times where end users adjust the Custom Plan on an instance from one selection to another (say Standard to Replicated) for a more critical role production system, and this reset the CPU and Memory to 1 unnoticed by the end user.
Example/Use case(s):
User has a system in vCenter with 8 vCPU, 32GB RAM, and 200 HD that’s currently using a Custom Plan called “Standard Plan - No replication”
User reconfigures the instance and switches to a “Replicated Plan”, values for CPU and cores per socket stay as they were currently set, same with RAM (so system still has 8 vCPU, 32GB by default going into the new plan)
User hits “okay”, the plan is adjusted and reconfigure workflow automation tasks kick off, instance remains at the 8 vCPU, 32GB RAM, 200HD and no reboot within vCenter occurs.