USE CASE REALIZATION MEETING (Notes 2019-02-27)
Date
Feb 27, 2019
Attendees
@Benjamin Cheung
@Floyd Goldstein
@Former user (Deleted)
@Oskar Malm
@Peter Loane
@James Forsyth
@Zu Qiang
@Enbo Wang
@Scott Blandford
@marge.hillis
@Joanne Liu Rudel
@t
@Margaret Chiosi
@Yuriy Malakov
@Tim Carey
@N.K. Shankaranarayanan
@Ulas Kozat
Goals
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Carry over | A&AI Platform Evolution Items | @James Forsyth | Schema Change PNFid: AAI-2148: Change key on PNF object from pnf-name to pnf-idClosed |
Carry Over | BBS U/C platform evolution & A&AI Schema change | @Chaker Al-Hakim @Margaret Chiosi @Tim Carey @David Perez Caparros | Platform evolution for PNF Re-Registration & Attachment Point Id AAI-2151: Add attachmentPoint attribute to PNF to support BBS use caseClosed (Resolved with BBS U/C, it will use an Edge to Logical Link instead of a A&AI Schema change) Plug and Play Wiki needs to be updated. Update PnP-6230 @Tim Carey |
Carry Over | Controller to NF Association | @Benjamin Cheung | Platform Evolution for Controller to NF Association. Will create a new Use Case in R5 El Alto for this. |
Carry Over | PNF Software Upgrade Use Case (Scope Change) | @Ulas Kozat @Oskar Malm | Huawei is now moving the PNF Software Upgrade forward with a new scope change. Based on Ansible. For R5 El Alto will also support NetConf. Created new Jira tickets in SDN-C. PTL Ajay has committed. R4 page updated. M2: API, Req, Integration. Roll-back testing. Reuse of Casablanca Tests. |
Carry Over | Platform Evolution for Data Persistency | @N.K. Shankaranarayanan | MariaDB and platform evolution for run-time persistent configuration information. Used in the OOF/PCI U/C. DCAE Post-gress DB. Primary inventory in A&AI. Base another database off of that. ConfigDB doesn't publish updates. PCI U/C if SDN-R knows of a config change it updates. SDN-R publishes changes on DMaaP. Network Maps & Topology & History. Timestamp. Controllers keeping state of network. |
(New) | Firewall U/C carry-over to R4 | @t | SOL005 I opened epic AAI-2194: Support ETSI NFV-SOL 005 (Os-Ma-Nfvo ref point ) between SO & VF-C/NFVOClosed to start tracking the SOL 005 Fw U/C From SO PoV Implementing SOL005 new API. from R3 U/C UI. create network svc from SO and call VF-C. Not part of SOL005). In R4 introduce SOL005 API between SO & VF-C. Register VNF no way to register NFVO and store in ESR/AAI to registrer NFVO. VFC/SOL005 Adapter there in R3 but API calls not API. talks to VF-C alone. Changes. Rearranging things in VF-adaptor. Changing Client Libraries. Functionality is the same. UUI to call SOL5 NB API. |
30 min | Scaling Use Case Overview | @Scott Blandford | |
Mar 6, 2019 | FM Meta-Data GUI display | @Benjamin Cheung @marge.hillis | SDC-2094: R4 5G U/C SDC: FM Meta Data GUI Display from PNF Onboarded PackageClosed |
Mar 6, 2019 | PM Dictionary Schema GUI display | @Benjamin Cheung @marge.hillis | SDC-2095: R6 5G U/C SDC: PM Dictionary GUI Display from PNF Onboarded PackageClosed |
SUPPORTING DOCUMENTS
Document | File |
---|---|
Use Case & Cross U/C Interaction Spreadsheet | |
RECORDING
Recording | File |
---|---|
Zoom (MP4) | |
Chat (Txt) | |
Audio Only (M3U) | |