ONAP CNF orchestration - Jakarta Enhancements

Note: This issue is a continuation of work done under https://jira.onap.org/browse/REQ-627 for the Istanbul release.

Description of Use Case / Requirement:
REQ-890_CNFO_16.02.pptx

ONAP supports CNF orchestration

Owners (one of these should be the Assignee - use @ notation):
rajewluk seshukm

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

Project Impact (Test Only (TO), Code (C)):
As defined in the sheet
https://wiki.onap.org/display/DW/Jakarta+Impact+View+per+Component

• Multicloud (C)
• SO (C)
• SDC (TO)
• SDNC (TO)
• CCSDK/CDS (C)
• AAI (TO)
• Modeling(C)

Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

Company Engagement:

• Multicloud (S): Orange, Samsung
• Integration (S): Orange
• CCSDK/CDS (S): Orange
• SO (S): TechMahindra, Samsung, Orange, Huawei

Integration Leads (use @ notation):
rajewluk

 API Changes:
No changes in the architecture - only existing interfaces enhanced

• Multicloud
  • New API for the subscription of the status notification (consumed by SO CNF Adapter)
  • New API for upgrading of the CNF instance (consumed by SO CNF Adapter)
  • Modified Config API to create Config Template from full CNF Definition (Consumed by CCSDK/CDS)
• SO
  • API Handler: New "cnfUpgrade" endpoint in the serviceInstance API - consumed by end user
  • CNF Adapter: New upgrade endpoint for instance API - used to upgrade CNF instance (will call similar API in the k8splugin) (consumed by SO BPMN infra)