...
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | |||
AAF | |||
APPC | |||
CLAMP | |||
CC-SDK | Epic#1: Controller to PNF exchange (Epic) | Epic #1:
| |
DCAE | |||
DMaaP | |||
External API | |||
MODELING | Epic #2: Geolocation parameters | Epic #2:
| |
Multi-VIM / Cloud | |||
OOF | Shankaranarayanan Puzhavakath Narayanan | ||
POLICY | |||
PORTAL | |||
SDN-C | |||
SDC | |||
SO | |||
VID | |||
VNFRQTS | |||
VNF-SDK | |||
CDS |
...
DUBLIN ITEM | DESCRIPTION |
A&AI2: External Manager (EMS/NMS) [ESR] | [A&AI] IP address or association with the External Manager. Is the ESR concept sufficient? https://onap.readthedocs.io/en/beijing/submodules/aai/esr-server.git/docs/ During PnP, the IP address of the External Manager would saved/stored or set by user or by the PNF. Where would that be stored? would it be in A&AI. Information about the External Manager is discovered & stored. Note: The External Manager info is optional LOW PRIORITY |
A&AI3: Cloud Home Server (A&AI) | [A&AI] Tracking the Cloud Home Server (CLLI, Cloud ID); is the association with the COMPLEX Object sufficient? How-To: Register a VIM/Cloud Instance to ONAP LOW PRIORITY |
A&AI / Model | [A&AI] GeoLocation information for the PNF reported via pnfRegistration VES Event LOW PRIORITY (Nice to have) |
A&AI4: A&AI pnf-id as INDEX for PNF | [A&AI] New A&AI schema adaptations: discrepancy between PNFs and VNFs; VNFs are identified via VNF-ID (UUID), and PNFs - via PNF-name. PNF-id should be used for Identities. This differentiates the way that PRH is searching for PNFs in A&AI, when PRH does the PNF registration in A&AI (may also require SO change). July 31th 2019 → AAI team has cancelled this request (redacted). CANCELED |
MODEL IMPACTS
DUBLIN ITEM | DESCRIPTION |
Model | [Modeling] GeoLocation alignment in Modeling with RFC6225 and the PNFD, A&AI schema, and SDC AID Data model. LOW PRIORITY (Nice to have) |