Tracking of designs of functionality and API

1, F-GPS:

               Please refer to the patch https://gerrit.onap.org/r/#/c/78634/ which elaborate how to enhance current API to support F-GPS.

               The AZ names should be discovered by multicloud discovery/registry process, the AAI schema can be reused without change:

https://nexus.onap.org/service/local/repositories/releases/archive/org/onap/aai/aai-common/aai-schema/1.3.3/aai-schema-1.3.3.jar/!/onap/aai_swagger_html/aai_swagger_v14.html#operation--cloud-infrastructure-cloud-regions-cloud-region--cloud-owner---cloud-region-id--availability-zones-availability-zone--availability-zone-name--get

2, SO/MC integration

              Create Workload: https://wiki.onap.org/display/DW/SO+to+Multicloud+API+enhancements

               AAI updating: https://wiki.onap.org/pages/viewpage.action?pageId=58228881

               SDC design: https://gerrit.onap.org/r/#/c/75851/

3, FCAPS enhancement

               https://wiki.onap.org/download/attachments/53249985/FCAPS%20enhancement%20plan.pptx?version=1&modificationDate=1548905759000&api=v2

4, Multi-Tenant Support

               TBD

5, Secured-communication enablement

               The multicloud services which are based on uwsgi could utilize the https feature of uwsgi: https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html

               The question would be: who/how to generate key and cert, and distribute them to MultiCloud consumers?