Game plan is to deploy gluster cluster with heketi prior to deploying ONAP, then point ONAP to created heketi+gluster storage. (Challenge is that there are manual steps during and after gluster deployment, e.g. provisining storageClass with random gluster ClusterID - and deployment of topology file after launching gluster "pods").

So we want to create a helm chart to deploy 3 glusterFS nodes + heketi front end, with externally available heketi interface (e.g. nodeport service) so that ONAP deployment can access. 

Current plan is to deploy gluster in separate deployment and namespace from ONAP - then re-evaluate.