About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Hi, I apologize, I had problems accessing the website since it moved from Support ERs.
Actually, this is not possible right now, I can show examples where we are setting the instance which supports all types of storage to tpo better reversibility, but it is generating an action to migrate from 92Gb SSD to 8Tb HDD when io usage is extremely low.
Goal: Metlife wants to ability to park the Storage to a lower tier when the VDI VMS are not in use for 7 consecutive days.
They have over 1000+ VMs attached to Premium SSD and want to use our automation to have an automativ policy which will move them from Premium SSD to HDD but keep same size. When the VDI VM goes back to active mode, (could be 3 months later) the VM will automatically be removed from the IDLE VMS Group and we will have a polify to scale the storage back to SSD.
At this time, when we select the automation policy to support only HDD, it creates the action but also forces it to go to 8Tb which is breaking the desired automation for Metlife of having the ability to scale back up to SSD of original size.
Business impact: Critical for Metlife: They are lookiong at using in-house scripts, this is critical for us to keep automation alive with the VDI team.
Anson's approach seems to meet this requirement. Richard let me know if you feel differently.
Hmm, what you are describing should already be possible in Turbo's policy engine today. Screenshot attached.
The setting to configure would be the "Better Reversibility" option. This way, you tell Turbo's analysis to not recommend making Disk size changes, and instead only focus on changing tiers.
Have you tried that?