Feature Overview (aka. Goal Summary)

Currently, ThinPoolConfig.OverprovisionRatio can only be configure at LVMCluster creation time and not edited later. This makes it impossible to disable Overprovisioning during cluster livetime.

Goals (aka. expected user outcomes)

Allow editing the OverProvisionRation after creation

Requirements (aka. Acceptance Criteria):

1. Allow changing to a smaller value down to 1, effectively disabling over-provisioning. Note: this can lead to creation of new PVCs to fail, if not enough space is available.
2. Allow changing to a bigger value (esp from 1 to e.g. 10), effectively enabling over-provisioning
3. No impact on existing clusters / installations.

Questions to Answer (Optional):

Analyse the potential impact of disabling or enabling on existing PVCs

Out of Scope

This by no means allows changing from thin to thick pool provisioning. Even when disabled during cluster live, thin pool is still used. 

Background

n/a

Customer Considerations

See linked RFE for customer cases requesting this

Documentation Considerations

We currently do not document that the field can not be changed. Hence I think we can keep it that way, meaning no docs needed.

Interoperability Considerations

none