Direct SDC-ETSI Catalog Manager Interactions
The following diagram depicts the direct SDC-ETSI Catalog Manager Interactions.
| Gliffy | ||||
|---|---|---|---|---|
|
Table of Contents
Requirements
ETSI Catalog Manager supports Container Images Management, working with CIR
- CIR is realized by Docker Registry
- ETSI Catalog Manager leverages Docker Registry APIs for CRUDQ operations
Epic and User Story
Epic | User Story | Description | In Honolulu Plan? | JIRA | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Support SDC-ETSI Catalog Manager Interface | ETSI Catalog Manager needs to support the SDC-ETSI Catalog Manager interfaces
| Yes (need to test) |
| |||||||||
| ETSI Catalog Manager subscribes for SDC package notification through DMaaP | ETSI Catalog Manager subscribes for SDC package notification through DMaaP | Yes (need to test) |
| |||||||||
| ETSI Catalog Manager queries SDC for ETSI packages (SOL004 and SOL007) and stores the packages | ETSI Catalog Managers queries SDC for ETSI packages (SOL004 and SOL007) from the ETSI_PACKAGE directory and stores the packages | Yes (need to test) |
| |||||||||
Support Container Images Management to CIR | ETSI Catalog Manager needs to support push Container Images to the selected CIR | Yes |
| |||||||||
| ETSI Catalog Manager pushes Container Images to the selected CIR | ETSI Catalog Manager needs to push Container Images to the selected CIR if the SOL004 VNF package embeds Container Images
| Yes |
|
Direct SDC-ETSI Catalog Manager Interactions
The following diagram depicts the direct SDC-ETSI Catalog Manager Interactions.
- ETSI Catalog interfaces with CIR through Docker Registry APIs
- CIR would be external and be realized by the Docker Registry
| Gliffy | ||||
|---|---|---|---|---|
|