Two alternatives:

  1. Using OOM (K8-based strategy), which was approved in the past face-to-face meeting and will be the standard/preferred way in the long run;
  2. Using Heat template, which is what we did for OpenECOMP.

OOM User Guide

OOM Deployment Status

(D: Done | C: Committed, when? | NC: Not Committed)

Project NameNeeded by UC

Heat Template

OOM

Project Tech. LeadNotes
A & AI YesD

D

Complete
Application Authorization FrameworkNo
CNot Release A
APPCYesDD
CLAMPYesDD


Common Controller SDKYesN/AN/AAs a library, CCSDK is not installed separately but rather is installed as part of the client project(s) that uses it (e.g. APPC, SDNC)
DCAEYes

Gen 1 - D

Gen 2 - D

D

D

DCAE GEN 2 is in Heat, but the DCAE team is still solving authentication issues that prevent the controller container to come up

DMaaPYesDD
DocumentationYesN/AN/A
External API FrameworkNo


HolmesYesN/AN/AManaged by DCAE
IntegrationYesN/AN/A
Logging Enhancements Project No

NC

R2?

C(OOM ) - 3 containers committed (some filebeat config pending)
Microservices BusYesDD
ModelingNoC

Multi VIM/CloudYesD

D

Patch

https://gerrit.onap.org/r/#/c/11901/ merged

ONAP CLINoDD
ONAP Operations ManagerYes?N/AN/A
ONAP Optimization FrameworkNoN/AN/ANot in Release A
ONAP UniversityNoN/AN/A
ONAP Usecase UI Project ProposalYesD
Mike to work on this one
Policy Framework Project ProposalYesD

Complete for 1.1

Portal Platform Project ProposalYesDD
SDN-CYesDD
Service Design & CreationYesDDSDC will use the heat based deployment For R1
Service OrchestratorYesDD
VF-C: Virtual Function ControllerYesD

D



VID projectYesDD
VNF SDKYesDD
VNF RequirementsNoN/AN/ADocumentation
VNF ValidationNoN/AN/ANot in Release A
  • No labels