PV's can be a shared resource among charts,  Currently we are using PVs in a 1:1 fashion with claims.

We can make this better by abstracting the PV and then having apps make claims against a particular PV.

Currently the following claims are made against persistent volumes:

• appc 2Gi
• clamp 2Gi
• log 2Gi
• message-router 2Gi
• mso 2Gi
• portal 2Gi
• sdc 2Gi
• so 2Gi
• vid 2Gi

The onap charts will declare 12  PVs and the other charts will make claims against these PVs. Only a single StorageClass of "standard" will be supported during initial development.

See here: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#writing-portable-configuration for a description of the rule on writing portable charts.

Here: https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner is a description of the storage classes.