Enforce Resource Configuration as Multiples of Increment Values in Container Specs Policies

I would like to submit an enhancement request for Turbonomic regarding policy settings for Container Specs.

Currently, Turbonomic policies allow us to define:

• minimum configuration,
• maximum configuration,
• and increment steps.

However, it would be very helpful to have an additional option to ensure that the resulting resource configuration is always a multiple of the defined increment value.

For example: We currently have container specifications with configurations such as 1.98 GB. If Turbonomic only applies an increment step of 128 MB, the resulting value may still end up being an uneven or non-rounded configuration. From an operational and administrative perspective, it would be much more practical if the final resource configuration were always aligned to a clean multiple of the increment.

This would provide:

• cleaner and more standardized resource values,
• easier interpretation and administration,
• improved consistency across container configurations,
• and more practical sizing recommendations.

Suggested Enhancement: Please consider adding a policy option in Container Specs that enforces resource values to always be rounded or aligned to the nearest valid multiple of the configured increment.

Example:

• Current configuration: 1.98 GB
• Increment: 128 MB
• Desired behavior: resulting recommendation/configuration should be adjusted to a clean multiple of 128 MB instead of ending with an irregular value.

Thank you for considering this enhancement.