-
Story
-
Resolution: Done
-
High
-
None
-
None
-
Frankfurt Sprint 0
- Finalize the Design for the Generic Building block call to CDS
- Using a common BB for all activities that interact with CDS.
- Finalize on the SO selection of ACTOR for APPC or CDS or SDNC
- Stop using the SO DB tables for actor selection (Must be meta data-driven via SDC) for all action
- Single Controller for a given Resource (VNF or PNF).
- All actions go through either APPC or SDNC or CDS.
- Allow via SDC selection of multiple CDS blueprint processor namespace.
- SO to ingest the CSAR with the namespace for a given resource.
- Scope & Action naming convention should follow the camel case format for all use cases.
- Scope naming convention is as follows:
- “service”
- “vnf”
- “pnf”
- “vfModule”
- “vnfc” - shall be introduced in the G Release
- CDS Payload Generation:
- The Scope shall be used for passing correct keys and instance params per scope level. In previous design discussion $actionName was derived from concatenation of scope+action but this rule has changed as of 12/18/2019. The $actionName shall consistent of only action thus $actionName=action.value
- *a*ction-name=$actionName
- $actionName-request
- $actionName-properties
- The Scope shall be used for passing correct keys and instance params per scope level. In previous design discussion $actionName was derived from concatenation of scope+action but this rule has changed as of 12/18/2019. The $actionName shall consistent of only action thus $actionName=action.value
- State Transition
- A&AI Update for SO building for status
See the attached PPT for more information.
1.
|
SO CDS Meta Data Ingestion for SERVICE, VNF, PNF, and VF Module | Closed | eeginux | |
2.
|
SO to CDS Generic Building Block implementation | Closed | prathameshmo | |
3.
|
SO to support state transition in A&AI for the CDS generic Building Blocks | Closed | seshukm | |
4.
|
Implement logic to pass a scope and action values from SO-DB to SO-Backend | Closed | manamohan |