Kickoff Materials/Background
- First presentation at ARCHCOM, 03/19
- Follow up presentation at ARCHCOM, 04/09
Meeting Information
Meetings when needed
Next meetings in week 18 to be called .
Agenda:
Discussion on ARCH Subcommittee jira Stories:
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
==============================
Objectives
- Enable use of CDS for self-service LCM operations currently supported by APPC and SDNC
Identify target architecture for LCM API consolidation across different Controller controllers: APPC, SDNC including CDS
Identify migration path need
Identify ONAP reccomendations recommendations in case of
-- Supporting PNFs for applicable LCM operations
- How and where to describe standard actions/operations including input parameters in payload
Adding a new LCM operation
-a A new UC/sw contribution with current LCM operations
El Alto/Frankfurt way forward
To Do's
-
Identify Target Architecturetarget architecture and recommended evolution for the Frankfurt (R6) release
-
El Alto improvements identificationsEstablish LCM API principles and recommendations
-
Frankfurt overall impacts
MIgration Path Conclude migration path need for APPC/SDNC
-
LCM API evolution rules
-
Identify component candidates for CCSDK
Target Architecture
SO/Policy communicate to GnfC using grpc via Self Service API.
El Alto improvements
External SOL003 Adapter as an Independent deployable component
Frankfurt step
Description
Frankfurt impacts
Contributions...
View file | ||||
---|---|---|---|---|
|