...
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||||||||||||||||||||||||
SO1: SO support of A&AI creation | [SO] A&AI UI can create an inactive PNF (inactive) A&AI entry. In Step #19A instead of EXITING, SO would go into WAIT STATE pending rehydration of RLF w/ pnfReady DEVELOPMENT STATUS:
| ||||||||||||||||||||||||||||||
| SOx: Service & NF Instance Association | Associating a xNF to a Service. Seen in the VID UI, after instantiation waiting for registration see only a Service instance, and beyond that a PNF resource instance associated with it. DEVELOPMENT STATUS: | ||||||||||||||||||||||||||||||
SO2: SO support for already existing PNF A&AI entries | [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) DEVELOPMENT STATUS: In ONAP/Casablanca this was updated, and irrespective of AAI entry existence for a PNF instance, the workflow execution always waits to receive a PNF registration event.
This is not planned to be changed in ONAP/Dublin release. | ||||||||||||||||||||||||||||||
| SO3: SO to support updated A&AI PNF schema | [SO] Support of SO for updated AAI PNF instance model. ASSOCIATED DEVELOPMENT: See task A&AI1 and PRH1. JIRA: (Depends on the A&AI work:
Epic Created: SO Dublin Page: Service Orchesrator Dublin Release | ||||||||||||||||||||||||||||||
| FUTURE (El Alto) | |||||||||||||||||||||||||||||||
SO-future: Controller Association [FUTURE MOVED TO EL ALTO] | [SDC/SO] The PNF controller caused quite a stir in Casablanca, the tension between Design/Platform Model vs Run-Time/Deployment Model. As a result the SO controller design was sub-optimal and should be addressed in Dublin. | ||||||||||||||||||||||||||||||
...
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||||||||||||||
VID1: VID Enhancements (Test only) | Confirm the PNF PnP still works with ONAP Dublin UI changes. There was VID GUI changes that happened in R4 Dublin to for new presentation layer with redesign of how VID presentation layer, new layout & buttons. VID displays pages only with certain conditions e.g. only shows PNF if it finds a PNF resource in the service model. HIGH PRIORITY. TESTING STATUS: | ||||||||||||||||||||
| VID2: VID PNF Mgmt. Enhancements | VID A&AI Schema Changes PNFid vs PNFnamePNF-id vs PNF-name. VID will have to be updated to support the new A&AI Schema change PNF model (PNF-id vs PNF-name). HIGH PRIORITY. PROPOSAL: ASSOCIATED DEVELOPMENT:
| ||||||||||||||||||||
| VID3: VID Enhancements | VID A&AI INSTANCE CREATION – (optional) (slide 20/Step 4) – VID supporting Resource Declaration a PNF A&AI Instance creation. Similar flow in eCOMP. LOW PRIORITY. | ||||||||||||||||||||
| VID4: Error Cases | ACTION: Error cases (check if SDC model parameters != A&AI PNF entry). LOW PRIORITY. |
...