ONF IM TAPI Development Cycle ONF Core IM

  • Slides: 2
Download presentation
ONF IM & TAPI Development Cycle ONF Core IM Mapping … "https: //registry. npmjs.

ONF IM & TAPI Development Cycle ONF Core IM Mapping … "https: //registry. npmjs. org/xmlbuilder/-/xmlbuilder-8. 2. 2. tgz" }, "maintainers": [ { "name": "oozcitak", "email": "oozcitak@gmail. com" } ], "_npm. Operational. Internal": { "host": "packages-12 -west. internal. npmjs. com", "tmp": "tmp/xmlbuilder-8. 2. 2. tgz_1460102388901_ … ONF Information Model (IM) P&R Tool KEY Manual process ITU-T IETF Tool Assisted Prune & Refactor Vendor/ operator specific specs can be developed that further narrow the definitions to support particular cases. Proprietary capabilities can also be added using the spec approach. ONF Spec Approach Pruned Core model is refactored to project familiar named items, for example: • Forwarding. Construct in the Core becomes both Connection and Connectivity. Service in TAPI. • Logical. Termination. Point in the Core becomes Node. Edge. Point, Connection. Endpoint and Service. End. Point in TAPI ONF Wireless Transport team have used the same approach to construct their interface model. Their model is different from TAPI IM Tooled Generation UML-YANG tooling generates conformant YANG from any appropriately structured model. Technology and service specific properties decorate structural classes derived from the ONF Core IM to form a fully detailed interface definition. YANG, REST, TOSCA… /**************************************************** * Name: UML to YANG Mapping Tool * Copyright 2015 CAICT (China Academy of Information and Communication Technology (former China Academy of Telecommunication Research)). All Rights Reserved. * Licensed under the Apache License, Version 2. 0 (the "License"). * * This tool is developed according to the mapping rules defined in onf 2015. 261_Mapping_Gdls_UML-YANG. 08 by Open. Network. Foundation(ONF) IMP group. * * file: modelyangpackage. js * * The above copyright information should be included in all distribution, reproduction or derivative works of this software. * **************************************************/ function Package(name, id, path, comment, file. Name) { this. name = name; this. id = id; this. path = path; this. description = comment; this. file. Name = file. Name; this. children = []; this. uses = []; } UML YANG Tool module tapi-connectivity { namespace "urn: onf: params: xml: ns: yang: tapi-connectivity" ; prefix tapi-connectivity; import tapi-common { prefix tapi-common; } import tapi-topology { prefix tapi-topology; } import tapi-path-computation { prefix tapi-path-computation; } organization "Open Networking Foundation (ONF) / Open Transport Working Group(OTWG) / Transport API (TAPI) Project" ; contact " WG Web: TAPI SDK Project http: //opensourcesdn. org/projects/project-snowmass/ WG List: TAPI Discussion list <mailto: transport-api@login. opennetworking. org >, WG Chair: Karthik Sethuraman <mailto: karthik. sethuraman@necam. com>, Editor: Ricard Vilalta <mailto: ricard. vilalta@cttc. es>" ; description "none"; revision 2017 -05 -31 { description "TAPI SDK 2. 0 -alpha"; reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020 and RFC 6087" ; } augment "/tapi-common: context" { uses connectivity-context; description "Augments the base TAPI Context with Connectivity. Service information" ; } augment "/tapi-common: context/tapi-topology: topology/tapi-topology: node/tapi-topology: owned-node-edge-point" { uses cep-list; ……………… TAPI YANG Implementation Transformation Tooling - IISOMI (Java Script, Open Source) Code snippets Comments IEEE Full Technology/Service definitions are pruned and refactored to provide the ONF Specs. Generalized Core model is pruned to remove elements not necessary for the TAPI view, for example Processing. Construct. Model and environment (inc. Papyrus (Eclipse, Open Source)UML tooling) Model and environment (NOT Papyrus) Technology IMs Network technology and service expert groups provide detailed properties (ideally in UML). Mapping Detail Mapping Tool Assisted Detail Prune & Refactor MEF Tooled process Model development process ONF Spec Approach ODU Spec

(40 x 28 inch) 39 x 27 inch 99. 06 x 68. 58

(40 x 28 inch) 39 x 27 inch 99. 06 x 68. 58