Note: This issue is a continuation of work done under https://jira.onap.org/browse/REQ-341 for the Guilin release.
Note: Reduced scope moved to https://jira.onap.org/browse/REQ-627

Description of Use Case / Requirement:

ONAP supports CNF orchestration [Honolulu]

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

Link to HLD/LLD (if any):
REQ-458_CNFO_Honolulu_Extensions_13_01_21.pptx

Dependency Relationships with Other Projects:

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

• Multicloud (C)
• SO (TO)
• SDC (C)
• 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): Samsung, Intel
• Integration (S): Orange, Samsung, Huawei
• SDC (P): Nokia, Huawei
• CCSDK/CDS (S): Orange, Samsung

Integration Leads (use @ notation):
rajewluk

API Changes:

only API of Multicloud/k8splugin like described in the attached presentation:

REQ-458_-_API_Changes.pdf

It considers modifications of the existing API:

• Configuration API
• Status API

It introduces also a new API:

• Test API

Existing SO flows will be unchanged. Changes in Configuration API may impact Guilin implementations of the use cases - requires changes in the use case test files (CBA packages) to reflect modified endpoints of Configuration API or to use new Configuration capabilities of CDS that deprecates direct use of Configuration API from CBA packages.