Consistent Resizing based on Example / Template Server Group-

We'd like to request an enhancement to the "Consistent Resizing" feature that would allow an "example" or "template" server group to drive the sizing actions of several other linked groups.

We would like to be able to divide our servers into different groups based on lifecycle stage (Production, Pre-Prod, Test, Dev, etc…) and designate our Production group as the example / template group. The rest of our server groups (containing servers from our lower environments) would then be tied to the right-size actions of the example / template group. After the groups are established and linked, all consistent resizing decisions for all of the linked groups will be based entirely off of the demand placed on the example / template group (Production).

Our servers residing in the lower environments (Dev, Test, Preprod) must be the same size as their Production counterparts to facilitate valid and accurate testing, but resource utilization in these lower environment servers can swing wildly between extended idle periods and full throttle load testing. With Turbonomic / CWOM's current functionality, our only option to achieve uniform sizing between production and lower environments is to place all of the servers from different environments into a single Consistent Resize group. This could potentially lead to production servers being downsized due to sparse demand in the lower environments, or oversized based on load testing that does not represent actual demand. That would be bad.