Deprecation of default Storage Policy Components for SIOC Storage Policy

Products

• VMware vCenter Server

Issue/Introduction

In VCF 9.0GA, the support for shares and reservations is stopped from SIOC SPBM policy. It will only support limits. The SIOCV2 backend code will ignore shares and reservations starting VCF9.0.

The shares and reservations are removed from default storage policy components as shown in the screenshots below.

	Description	Before	After
1	High IO shares allocation
2	Low IO shares allocation
3	Normal IO shares allocation

Environment

VCF 9.0

Resolution

As seen in the screenshots above, after the removal of shares and reservations, these storage policy components will have only limits with some default values. However, their names still refer to them as "High/Low/Normal IO shares allocation". Since they contain only the limit values, the current names do not correctly reflect what is supported and it may be confusing to the users. To address this, the default storage policy components are deprecated in this release and could be removed in future VCF release.

To avoid the breaking any automation that may be already using the default storage policy components : 

• In VCF 9.0, the description of the default storage policy components for SIOC Storage Policy is updated to refer to the KB 385396 as shown below.
  
  
  
  
• In future VCF releases,
  • The default storage policy components related to SIOC Storage Policy may not be available on
    
    • Fresh installations.
    • Existing installations if they are not being used by any storage policies.
  • The customer have to create their own custom Storage Policy component and set the Limit values in order to use it. To create a custom storage policy component
    
    • Navigate to Policies and Profiles -> Storage Policy Components.
    • Click on Create.
    • Enter the name of the component. For ex. High.
    • Choose Category - "Storage I/O Control".
    • Provider will be default "VMware Storage IO Control".
    • Enter the IOPS limit
      • Set the limits values from earlier supported defaults values(i.e 1000/10,000/100,000) depending on the workload.
      • Or set any custom value as per the workload needs.
    • Once completed, this storage policy component can be used to create a SPBM Storage policy.