Note: Reduced scope moved to https://jira.onap.org/browse/REQ-458

Description of Use Case / Requirement:

ONAP supports CNF orchestration [Guilin] 

• Make Helm a first-class citizen and be understood by the Design and Runtime components of ONAP on need basis
• Leverage the K8s API adaptation in SO
• Currently K8s Integration done in MultiCloud is more a hacky way of passing the helm info embedded in a heat package.
• In G release we intend to correct this by integrating this functionality in SO.

Attached presentation, slides 7 and 9 present the overview of the technical scope of the proposed requirement

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

Link to HLD/LLD (if any):
attached

Dependency Relationships with Other Projects:

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

• Multicloud (C)
• SO (C)
• SDC (C)
• SDNC (TO)
• CCSDK/CDS (C)
• ESR (C) (Stretch)
• AAI (TO) - No AAI Schema change

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, Huawei
• Integration (S): Samsung, Orange, Huawei
• SO (S): Huawei, Lumina, Orange
• SDC (S): Lumina, Huawei
• CCSDK/CDS (S): T-Mobile, Orange
• ESR (S): Aarna Networks

Integration Leads (use @ notation):
rajewluk

NFR Contributions:

• REQ-364 - Orange
• REQ-361 (SO, CDS)
• REQ-362 (SO)
• REQ-340