Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DUBLIN ITEMDESCRIPTION
A&AI1: A&AI pnf-id as INDEX for PNF

[A&AI] Using the pnf-id (instead of pnf-name) as the index for PNF into A&AI. (discussion started in R3, socialized, Contact: Chesla Wechsler ).  The URI will change, as a query parameter.
Get naming indexing consistency with PNFs and VNFs. Schema A&AI model update.

ACTIONS: Inform Clients of break in change & migration.
Details: Proposal to Change AAI PNF Entity to use PNF-ID as key

ASSOCIATED DEVELOPMENT:

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2096
(Epic)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2148
(Story)

A&AI4: SO support of A&AI creation

[SO] A&AI UI can create an inactive PNF (inactive) A&AI entry.
A Service provider might use an inventory system and A&AI UI to create a PNF A&AI entry.

In Step #19A instead of EXITING, SO would go into WAIT STATE pending rehydration of RLF w/ pnfReady

DEVELOPMENT STATUS:

(Completed in ONAP/Casablanca -

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-797
)

A&AI5: SO support for already existing PNF A&AI entry

[SO] Support of SO for an already existing PNF (active) A&AI Entry

(use case with a deleted & recreated service or instantiating 2nd service using the same PNF)

In Step #19B SO would exit and service creation would continue

MOVED TO R5 EL ALTO
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

...