Starting in HCP 7.0, the behavior that’s governed by namespace service plans has been expanded to include the specification of the DPL setting and the primary running storage tier MPL setting for each storage tier that’s defined for a namespace by its service plan. As a result, starting in HCP 7.0, the system-level DPL setting has been deprecated and replaced with the ingest tier DPL setting for the default service plan, and the namespace DPL and MPL settings have also been deprecated.
During an upgrade from HCP 6.x to HCP 7.0 or later, to maintain the behavior of the system-level DPL setting and the namespace DPL and MPL settings that are in effect for each namespace that’s defined on an HCP system, the HCP Setup program will update existing service plans and create new service plans for each namespace, as needed.
After an upgrade completes, all existing service plans will be upgraded to use the HCP 7.x format. In addition, HCP will ensure that each namespace has a new or existing service plan that sets the correct DPL and primary running storage MPL for each storage tier that’s defined for the namespace.
During an upgrade from HCP 6.x to HCP 7.0 or later, if the system-level DPL setting was in use before the upgrade, HCP Setup modifies the default service plan to use the system-level DPL setting as the ingest tier DPL. If any namespace has a DPL setting of Dynamic and the default service plan is not assigned to that namespace, then HCP Setup either modifies the existing service plan for that namespace or creates a new service plan for that namespace to ensure that the current system-level DPL setting is used for each storage tier that’s defined for the namespace.
After modifying the ingest tier DPL setting for the default service plan (if necessary) then for each existing service plan:
•If the existing service plan is assigned to one or more namespaces, and all of those namespaces have the same DPL setting (for example, Dynamic, or 1), HCP Setup reconfigures the existing service plan to specify the existing namespace DPL setting as the ingest tier DPL.
•If the existing service plan is assigned to multiple namespaces that have different DPL settings, then for those namespaces, HCP Setup performs the following procedure:
1.HCP Setup creates a new, retired service plan for each unique combination of an existing namespace DPL setting and the existing service plan storage tier specification.
2.HCP configures each namespace to replace the existing service plan with the appropriate retired service plan that’s required to maintain the behavior of the original namespace DPL setting on each storage tier that was defined by the original service plan.
After an upgrade from HCP 6.x to HCP 7.0 or later, the new retired service plans created by HCP Setup are not configurable, and each assignment of a retired service plan to a given namespace overrides the previous service plan assignment that was configured for that namespace before the upgrade.
As a result, for each namespace to which HCP Setup has assigned an automatically generated, retired service plan:
•If the namespace is owned by a tenant that’s not configured to allow the tenant administrator to assign a new service plan to the namespace:
oBecause a retired service plan is currently in use by the namespace, HCP generates a system-level alert to inform you that you need to assign a new service plan to the namespace.
oTo respond to the alert, you need to take one of these actions:
–Change the status of the retired service plan from retired to active, and continue to use the new service plan that HCP Setup has generated for the namespace.
–Assign a new service plan to the tenant that owns the namespace (and hence, assign that new service plan to all namespaces owned by that tenant).
–Configure the tenant that owns the namespace to allow tenant administrators to assign a specific service plan to each namespace that’s owned by the tenant. In this case, the retired service plan will continue to be assigned to the namespace until a tenant administrator configures the namespace to assign a new service plan to it.
•If the namespace is owned by a tenant that is configured to allow the tenant administrator to assign a new service plan to the namespace:
oBecause a retired service plan is currently in use by the namespace, HCP generates a tenant-level alert to inform tenant administrators that a new service plan needs to be assigned to the namespace.
oIn response to this alert, a tenant administrator needs to assign a new service plan to the namespace.
© 2016 Hitachi Data Systems Corporation. All rights reserved.