...
- Meeting every Wednesday 09:00 EDT, 06:00 PDT, 15:00 CET, 10:00PM Beijing Time (UTC+8)
- Meeting bridge?https://zoom.us/j/9117271979
- Concluded doodle poll at https://doodle.com/poll/enf3tcuaq5bhshrb
Upcoming call
Time
- Nov 1421, Wednesday TBD
Proposed Agenda
- 1. open issues clarification in last week. Cloud Service Architecture ( Mehmet Toy ) 15mins
- 2. Latest ETSI SOL001 Updates (shitao li, Arturo Martin de Nicolas) 15mins2. ask modeling subcommittee to vote for NS belongs to service or resource
- 3. Discussion on three NS modeling ways :
1) NS as attachments
2) support a separate NSD internally:
concerns: how to map with the service instance(as we are now trying to combine NS instance into service instance)
3) service expansion to include NS attributes
concerns: how to model nested service (when having multiple Network services) and map it with service instance
Past calls
20181107
Agenda
- 1. open issues clarification in last week.
- 2. ask modeling subcommittee to vote for NS belongs to service or resource
- 3. agenda for next week
Participants
Lin Meng, Chesla Wechsler, Andy Mayer, Deng hui, Gil Bullard, Kevin Scaggs, Margaret Chiosi, Mehmet, Yang xu, John
Minutes
- Clarified open issues from last week.
1) "status" in VFC and "orchestration status" used by SO: add a VFC-Status field to AAI to capture VFC's status. Chesla will propose to the architecture subcommittee that we need an orchestration "meeting of the minds" on state transitions, terminal states and transition states and what gets written to AAI.
2) "sdncontrollerId" is a legacy attribute. Delete
3)"nsdmodel", "scaleparams", "inputparameters" . Just internal fields in VF-C. Do not add to A&AI.
4) The use of "selflink" is to contain the URL to the service topology in SDN-C, for example.
5) "nslevel" and "flavorId": Chesla Wechsler has sent an email to use case mailing lists, according to the discussion threads, No need to worry about flavour_id or nslevel in Dublin. So it won't be added to current service instance. At info model level, you can always add instantiation level and deployment flavor to the service instance as Future stereotype, and data modelers know that they don't need to be added. - Lin suggests to have a vote for NS belongs to service or resource. Andy Mayer suggests to propose that to next week's modeling subcommittee.
- Next week, Mehmet Toy will talk about cloud service architecture. Also, a discussion about service IM modeling with NS will be started.
Recording
Audio only
Video and audio
chat
20181107
Agenda
- Combination of NS and service in A&AI (Service Instance thoughts)
Participants
Lin Meng, Chesla Wechsler, Andy Mayer, Deng hui, Gil Bullard, Kevin Scaggs, Margaret Chiosi, Mehmet, Sal R, Yang xu
Minutes
Compare implementations of service instance in A&AI and NS instance in VFC, and decide how to model NS instance into service instance in A&AI:
...
chat
20181024
Agenda
- Architecture F2F Meeting Planning From ServiceIM perspective
View file name Architecture F2F Planning - Service IM.pptx height 250
...
Video and audio
chat
20181017
Agenda
- Time change options for service IM call
- Presentation from 3GPP team
Participants
Lin Meng, Andy Mayer, Anatoly(Nokia), John, Kevin Scaggs, Lishitao, Michela Bevilacqua, Thinh Nguyenphu, Xu Yang
Minutes
- Time change options of service IM call on Wednesday:
...
chat
20181010
Agenda
- Papyrus Service Model Updates (Service order)
- RST documentation for master branch
- The role of 3GPP 28.541 in the ONAP service model
Participants
Lin Meng, Andy Mayer, Dave Miham, Gill Bullard, Kevin Scaggs, Thinh Nguyenphy, Xu Yang
Minutes
- Kevin talked about his updates on service order, especially for the state of service order. Will update it in Papyrus working branch after Lin hand over the editor to Kevin.
- Lin will submit the rst documentation work next week.
- Gil proposed the role of 3GPP 28.541 in ONAP service model, discussion mainly centered on the character of network service. Gil and Thinh will have more discussion with 3GPP team about this question.
...