Storage Policies

Unless I’ve missed something, it doesn’t appear possible to assign or modify a volume storage policy after an instance or volume has been created.

From what we can see, the storage policy needs to be defined at the point of deployment, and cannot be changed afterwards without recreating the volume.

From a provider perspective, this presents some operational challenges. For example, we may need to move workloads between different storage tiers (e.g. performance vs capacity) as requirements evolve over time, or as part of optimisation or commercial changes. Being able to update the storage policy post-deployment would allow this to be handled more flexibly and without disruption.

As administrators, we can work around this where required (for example by recreating volumes or handling this outside of OSIE), however this adds operational overhead and reduces the overall efficiency of managing customer environments at scale.

Could you confirm whether there is a supported method for modifying storage policy after deployment? If not, would this be something that could be considered as a feature request?

Thanks!