Feature | Description |
---|---|
Mapping between SOL001 VNFD and SDC AID DM | SDC and SOL003 Adapter need to handle mapping between SOL001 VNFD and SDC AID DM
|
Mapping between SOL001 NSD and SDC AID DM | SDC and SOL005 Adapter need to handle mapping between SOL001 NSD and SDC AID DM |
Mapping between SOL001 PNF and SDC AID DM | for PNP, SDC and SO need to handle mapping between SOL001 PNFD and SDC AID DM
|
Epic | User Story | Description | Frankfurt? | JIRA |
---|---|---|---|---|
SDC SOL004 and SOL007 Onboarding and distribution | SDC support SOL004 and SOL007 onboarding and distribution | Yes | see the package management epic | |
Mapping between SOL001 VNFD and SDC AID DM | Mapping between SOL001 VNFD and SDC AID DM
| YES | ||
Mapping between SOL001 NSD and SDC AID DM | Mapping between SOL001 NSD and SDC AID DM
| YES |
The following is a summary of initial input from Gil Bullard (AT&T).
ONAP wants to distinguish between the mode/data required to drive ONAP functionality from a Service Provider perspective from any ancillary mode/data required to drive Cloud Provider automation.
SOL001 VNFD | SDC AID DM | Comments |
---|---|---|