Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Meeting time: 13:00 UTC

Zoom Meeting Link:  https://zoom.us/j/137904496 International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a

2020 Modeling Subcommittee Recordings



Duration 60 minutes


DurationAgenda ItemRequested byNotes / Links

START RECORDING:





 15

Co-chair

ONAPMODEL-3 - Getting issue details... STATUS

1) Email Polls


2)  Modeling current activity status.

Provide the dash board of current status and how to involve:

See: Modeling Current Activity Status

Please keep updated


3)  Joint SDC & Modeling subcommittee DM review:

   Left issue: how to document DM spec, what about update AID model? approve AID officially?

  •  Potential topics: (Fred is defining IM and DM, Ericsson will make enhancement in SDC, reviewed in the future)
    • ETSI  Package Management , (SOL007 NS package,  after NSD/VLD), to support SDC to design firstly , other than onboarding.
    • Mapping between SOL001 VNFD/NSD DM and AID model, initial information model to meet REQ271 (difficulty: how to do nesting, composed /atomic model in ONAP)
    • Action:  SDC PTL.  invite ChrisC
    • REQ-334 - Getting issue details... STATUS
    • step 1:info model: link:  ETSI IFA011 v2.7.1 Changes (review and collect feedback in resource model call and subcommittee poll later)
    • step 2:  approve changes, 
    • ETSI Package Management (SDC Enhancements)- Guilin#SOL001MappingtoSDCAIDDM
    • collect feedback in SDC and modeling subcommittee together and send an poll later.
    • 2.1: have a call to review the proposal (Friday, Internal Ericsson review(mapping and 2.7.1), next Monday review in SDC)
    • 2.2: email collect feedback (1 week) , will consult with A&AI PTL.
    • 2.3: poll on this. (2 weeks)
    • step 3: coding and documentation 


4)  ONAP R7 Modeling High Level Requirements

Category 1 : R1/R2:

  Fred: Whether ETSI NFV 2.7.1 review next week will be decided by next Monday.

Category 1 : R3 will contact about how to proceed.

Category 1:  R4 Chuyi will detail the requirement

Category 2: Ben will handle them firstly , will contact with chairs once he need the help

Category 5: Container model documented, encourage the contribution.

ACTION:  Do we need requirements for: O-RAN A1 Adapter; CMPS; and License Management

Decision: we will start our own ONAP policy model firstly. Chuyi and MIchela will discuss offline, will join resource model call later.


Please add JIRAs for Experimental items: Fernando Oliveira Byung-Woo Jun Seshu Kumar Mudiganti Benjamin Cheung Andy Mayer


5) Request initiation of co-chair election process 

Modeling Subcommittee Members




Data models shared with Modeling subcommittee

Guilin Release Data Model

Guilin Impact View per Component

ONAP R7 Modeling High Level Requirements

Action: review all

 5

ONAPMODEL-1 - Getting issue details... STATUS

Resource IM


 5

ONAPMODEL-2 - Getting issue details... STATUS

 0

ONAPMODEL-12 - Getting issue details... STATUS

AAI Reverse Engineering status


10Modeling and Use Cases

Please review and provide comments by next week to help finalize next week: Proposed ONAP Release Process Updates for Information and Data Modeling

Please attend Aug 10 Resource IM call if there are additional comments or questions.

See: ONAP Use Case / Requirements Teams Process Way of Working (WoW)

Modeling process will be shared on the next Arch SC Call.

UC Information Element Templates are being filled in. 

See: Guilin (R7) - Use Cases (and Requirements in Use Cases)

Model review will be on Aug 12th: Use Case Realization Call: Aug 12 2020





ACTION ITEMS:






Zoom Chat Log




  • No labels