Page History

NOTE: Originally, the 5G Edge Use Case was planned for Dublin.  But that was deferred because an ONAP-wide multi-site (routing) solution was not implemented.  So, this page represents notes for the Work In Progress...as DMaaP team experiments with various approaches.

The The Dublin 5G Use Case has dependencies on DMaaP services.  The 5G components  (Data File Collector and 3GPP PM Mapper) will be deployed at the Edge, so DMaaP services should be made available to them to avoid a data flow path through the Central Kubernetes cluster.    This 5G Use Case relies on both Data Router and Message Router.

...

Solution Options for Dublin

NOTE: planning for Dublin assumed that the AAI component would provide an API that served as a registry of each ONAP site.  This did not happen.

This section is based on a discussion with Jack Lucas about possible approaches that we might consider within the Dublin feature set.

...

1. Central K8S Deployment
2. Central DMaaP Deployment
   1. Use k8s cluster name as the Release.  e.g. "central"
   2. Deploy aaf
   3. Deploy aai
   4. Deploy dmaap
   5. Deploy dcae
   6. Deploy VES perf3gpp via dcae
3. Edge K8S Deployment
   1. Register Edge K8S deployment in AAI (how?)
   2. Add dcaeLocation (for new Edge K8S) to DMaaP Bus Controller
4. Edge DMaaP Deployment
   1. Update dmaap-edge.yaml configuration override file with values from central
   2. Use k8s cluster name as the Release.  e.g. "edge1"
   3. deploy dmaap
   4. deploy PM Mapper via dcae

...