Open Information Model & Tooling
Space shortcuts
Expand all   Collapse all
Child pages
  • 2017-12-21 OIMT Meeting Notes
Skip to end of metadata
Go to start of metadata

Date

21 December 2017

Attendees


Apologies

Goals

  • Admin
  • v1.3.1
  • v1.4

Discussion Items

TimeItemWhoNotes
IM-DAdminKam/Nigel
  • TR-512 v1.3 publication: Kam reported on the decision from the discussion with Timon on the publication of TR-512:
    • Location of publication:
    • Descriptive status sentence:
      • “Note: this Technical Recommendations has been approved by the Project TST, but has not been approved by the ONF board.  This Technical Recommendation is an update to a previously released TR specification, but it has been approved under the ONF publishing guidelines for ‘Informational’ publications that allow Project technical steering teams (TSTs) to authorize publication of Informational documents.  The designation of ‘-info’ at the end of the document ID also reflects that the project team (not the ONF board) approved this TR.”
      • To be used in all TRs that are published by Projects without ONF board oversight.  It is envisioned that only existing TRs requiring update would use this publishing method, would include this sentence in the preamble, and would use a special indicator in the Document ID
    • Status Indicator in Document ID
      • To indicate status as project approved (not ONF board approved)
      • TR-512-v1.3.1-info
    • Cleanup ONF site older documents
      • Nigel and Kam will provide instructions for cleaning up the Models-Apis page on the ONF site, then ONF will implement with web team
        • Collapse older documents into a zip for each older version 
      • Have clear indication which are current and which are the older versions
    • v1.3 and v1.3.1
      • Will wait for v1.3.1 for publishing (i.e., skipping v1.3)
      • v1.3.1 will be published once released by the Project TST
  • 2018 meeting plan
  • Status of Group review of UML-OpenAPI and UML-ProtoBuf Mapping Guidelines
    • UML-OpenAPI Mapping
      • See #20 below
    • UML-ProtoBuf
      • See #27 below
 v1.3.1Xiang
  • #7: Multi-layer examples
    • Latest draft TR-512.A.5
    • Figure 4-4, should 1/10 instead of 1/40
    • AI- Malcolm will do a final check on the numbers
    • Ready to go
 v1.4 TopicsRick/Kam
  • Discussion on the comment regarding disclaimer:
    • Agreed that all generated files (including OpenAPI file, YANG file and whatever interface protocol files) should have a disclaimer text upfront. The mapping guideline documents should thus have a guideline similar to the one in section 5.9 of oimt2017.CH.001.00_Uml-to-ProtoBuf-Mapping, i.e.

 

The generator shall generate at the top of each ProtoBuf file :

    • Copyright and license text
    • generator and model version information
    • A syntax statement for version 3
    • A package statement
    • Any required import statements

 

For example

// (c) 2017 Open Networking Foundation. All rights reserved.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
// 
//     http://www.apache.org/licenses/LICENSE-2.0
// 
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
// TapiModule-Interfaces-CoreModelAPI generated from UML
// generator version 0.0.1
// TapiModule-Interfaces-CoreModelAPI
// model version1.0.0
//
 
syntax = "proto3";
package onf.tapi.CoreModelAPI;
 
import "google/protobuf/timestamp.proto";
import "onf/protobuf/onf-descriptor.proto";
import "onf/protobuf/onf-types.proto";
    • Will set discussion time after new year to have closure on comment resolution.
      • Tentatively set for Jan. 11 IM-D slot (ensure Rick and Chris both can attend)
  Chris
  Andrea
  • #5: OAM
    • Andrea presented the mapping among the G.800, G.8021, and TAPI constructs. Agreed some enhancements for clarification, updated slides:MEF NRM OAM and TAPI v2.0- 20171220.pptx
    • Slide 8
    • Slide 7
    • Multiple MEPs (with different MELs) in a VLAN
    • Slide 10
    • Slide 11
    • Slide 12
  Malcolm
  • #12: Entity Lifecycle
  Nigel
  • #1: Controller: Not discussed.
IM-ETAPI Termination Point Model  
 Wireless transport discussion 
  • Model backward compatibility
 v1.4 topics  
IM-Fv1.4 topics Call cancelled.

Action Items

1 Comment

  1. Rick Jing

    Sorry for not be able to attend yesterday's meeting!  January 11 Thursday IM-D is OK for me. I will update the mapping guidelines as v05 before the meeting.