Workshop Venue:

Huawei Technologies

Bldg C 1F-05 Training Room

2330 Central Expressway

Santa Clara,  CA 95050


Check-in Instruction:

1) All attendees must use self sign in system to check in at the main reception desk located at Bldg B lobby.

For any external guests who bring in their own laptops must sign a laptop registration form at the sign in, name tag will be issued afterwards.  


2) Follow the conference sign to the meeting room in Bldg C.


Chair (Hui Deng, Lingli Deng, Rittwik Jana)

TimeTopicPrime
09:00 - 09:05Host welcome and facilityHuawei
09:05 - 09:10 ONAP PresidentYacheng Wang
09:10 - 10:50SDO Session
09:10 - 09:30MEF

John Strassner

09:30 - 09:50TMF
09:50 - 10:10 ONF
10:10 - 10:30ETSI NFVETSI NFV

Andrei and Shitao https://wiki.onap.org/download/attachments/19202200/NFVSOL%2817%29000746r3_Draft_Presentation_for_ONAP_MOdeling_Workshop.pptx?version=1&modificationDate=1513352578217&api=v2

10:30 - 10:50OASIS TOSCA

Michael Brenner

10:50 - 11:00Break
11:00 - 12:00CIM discussionLingli Deng & Andy Mayer
ONAP Beijing CIM-1214.pdf
12:00 - 13:00Lunch
13:00 - 14:00Resource SessionAndy & David & Yangxu
13:00 - 13:30Resource IM

13:00 - 14:00Resource DT DM
14:00 - 15:00Service SessionLingli & Maopeng & David
14:00 - 14:30Service IMService IM Discussion
14:30 - 15:00Service DT DM
15:00 - 15:30RT DM A&AIJimmy & Yangxu & Maopeng
 15:30 - 16:00Close Loop Automation Model  Ron Shacham
 16:00 - 16:30MultiVIM FCAPS Model
 Xinhui Li
 16:30 - 17:00Wrapup 
  • No labels

7 Comments

  1. I'd recommend a session on Modeling Tools, Processes, Methodologies that will be used for R2+ before we dive into the Resource and Service models themselves. Andy has presented this material on some of our calls, based on the work of IISOMI

    It would also be useful to integrate Use Cases and Lifecycle Flows in the context of how the models will be used once implemented at the various interfaces. This will give us some understanding of the dynamic behavior behind the models, aside from their static information structure we've been discussing to-date.

    In addition, will there be representatives from other SDOs or open source projects present?  If so, it would be good to have an agenda item to allow them to present their modeling efforts/status at a high level and if they see value in collaborating with ONAP on our Common Information Model. For example, if and how ONAP would leverage the ETSI and/or TM Forum information models, data models and API interface definitions, and stay in synch with them through a formal collaborative agreement.

    It's important to lay the foundation first, before diving deep into the models themselves, so we attract a larger audience of participants.

    1. we got SDO session on Tuesday afternoon during forum, so I plan to move those presenation to that slot, do you think that workshop will represent it again on thursday? anyway SDO only got 45 minutes slot in the forum, but they have more large audience

  2. +1

    I thought that there was going to be an opportunity for other SDOs to present their models. I canceled a trip to Europe in order to present the MEF work, and where the MEF is similar to IISOMI and where it is different (also different from the TMF).

    In addition, I thought we were talking about a **common** information model? Where is that on the agenda? Having separate service and resource sessions doesn't work, as they could be designed using completely different approaches. In addition, the hardest thing to model is how the business interacts with the service layer - that deserves a separate session.

    1. John, we got SDO session on Tuesday afternoon during forum, so I plan to move those presenation to that slot, do you think that workshop will represent it again on thursday?

      1. I don't think 45 minutes is enough.

        There are HUGE differences in philosophy, let alone the actual modeling, in the MEF, TMF, and IISOMI. The MEF and IISOMI did just agree on a good subset of Resource model work, with changes to both (there is still much more work to do). However, the MEF and TMF are not aligned at all.

        IFF we want a model-driven system, then we need to derive APIs and other artifacts from the models. We aren't doing that in ONAP right now. I understand that people are feeling time pressure to get things out. However, without a unified and consensual model, we will end up with silos of systems that have little in common, and will require too much code to semi-integrate them. We need a higher-level meta discussion of model-driven engineering if we want to fix this.

  3. I don't think this is the right place to solve the potential misalignment between the information models (between MEF, TMF, IISOMI, ...).

    There is a specific working group created for that. See Pascal Menezes for more details.

  4. Per action item from yesterday's workshop, the link to TM Forum SID in Papyrus format is here (available for download by TM Forum members only):

    https://www.tmforum.org/resources/standard/information-framework-sid-release-17-0-papyrus-format/