MEF Common Information Model Overview

Slides:



Advertisements
Similar presentations
Business process engineering: an overview The goal of business process engineering (BPE) is to define architectures that will enable a business to use.
Advertisements

1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 MEF Reference Presentation December 2012 Carrier Ethernet Delivery of Cloud Services.
Multi-level SLA Management for Service-Oriented Infrastructures Wolfgang Theilmann, Ramin Yahyapour, Joe Butler, Patrik Spiess consortium / SAP.
Proposal: Model-Driven SAL for the OpenDaylight Controller
MEF Reference Presentation November 2011
Infrastructure for Electronic Government, An Overview
Enabling Broadband On-Demand Services Ethernet Services.
Programming Interface for IP-based Networks Steve Weinstein & Masa Suzuki {sbw, C&C Research Labs., NEC USA, Inc. Feb. 13, 1998.
FI-CORE Data Context Media Management Chapter Release 4.1 & Sprint Review.
SWIM-SUIT Information Models & Services
DOCUMENT #:GSC15-PLEN-51 FOR:Presentation SOURCE:ITU AGENDA ITEM:Plenary 6.10 Conformance and Interoperability Testing.
CyberInfrastructure workshop CSG May Ann Arbor, Michigan.
TOSCA Monitoring Reference Architecture Straw-man Roger Dev CA Technologies March 18, 2015 PRELIMINARY.
1 Light Reading Ethernet Europe – Frankfurt – April 2013 Ralph Santitoro MEF Director and Co-chair of CE4Cloud/SDN Project Director of Strategic Market.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
GEN15 LSO Hackathon. Session Topics LSO Hackathon vision (GEN15 and beyond) GEN15 LSO/CE 2.0 oriented scope (review of the diagram) and defined outputs.
1 SDN Framework draft-nadeau-sdn-framework-statement-01 Thomas D. Nadeau Ping Pan IETF-82.
WELCOME TO THE Presenter Name Presenter Name Jack Pugaczewski
D. Stiliadis F. Balus W. Henderickx N. Bitar M. Pisica Software Driven Networks: Use Cases and Framework draft-stiliadis-sdnp-framework-use-cases-01.txt.
VIRTUAL IT BUNDLE VIRTUAL NETWORK SASS + IAAS CLUSTER FIBRE ACCESS (LAYER 2) VIRTUAL FIREWALL TMF Active Catalogue PSA SOAP TMF Open Digital API REST RUN.
ONAP and MEF LSO External API Framework Functional Reference Architecture 12 July 2017 Andy Mayer, Ph.D. © 2016 AT&T Intellectual Property. All rights.
LSO Innovation Platform
ONAP layering/MEF alignment
Defining ONAP APIs With BSS/OSS
MEF Modeling Activities
LSO Hackathon Kickoff Charles Eckel.
Lifecycle Service Orchestration (LSO) Models in context
Service Orchestration Functionality- Service Decomposition
Bartosz Michalik, Amartus Donald Hunter, Cisco
AT&T Marketplace for Enterprise MEF Hackathon
OPEN-O Modeling Directions (DRAFT 0.6)
ONF presentations to ETSI NFV Info Modelling Industry Status ONF Modeling Update 29 March 2016 Note that some points are related to the Multi-SDO Issues.
ONF presentations to ETSI NFV m-SDO IM/DM Workshop ONF Common Information Model – Core Information Model January 2016.
OPEN-O Modeling Directions (DRAFT 0)
MEF Modeling Activities
LSO Hackathon Kickoff Charles Eckel.
MEF Q2, April Frankfurt, Germany
Systems Analysis and Design With UML 2
Orange Contribution to ONAP project Northbound API October update
ONAP Integration Through Information and Data Modeling
MEF LSO Legato SDK 24 October 2017 Andy Mayer, Ph.D. Tara Cummings.
ONAP Integration to External Domain Management Systems (DMS)
LSO Hackathon Summary Charles Eckel, Cisco DevNet.
Using the MEF Core Model in ONAP John Strassner, Ph. D. Andy Mayer, Ph
Intent Based Orchestration for Applications
OpenCS SD-WAN Project Update
ONAP APIs Andrew Mayer, AT&T
MEF Technical Vision & the Transformation Journey to MEF 3.0
Papyrus ( Focussing on use in ONF ( Nigel Davis (Ciena
MEF 3.0.
TMF Information Framework
Consideration of Modeling Evolution in ONAP Michela Bevilacqua Peter Wörndle and Tara Cummings 13 December , 2017.
ONAP External APIs Possible Enhancements / Roadmap R3+
TMF Information Framework
MEF API Development Approach
The Extensible Tool-chain for Evaluation of Architectural Models
Phaethon: a lightpath provisioning adapter for LightSoft
Unit 3c: Relations and Functions
Amdocs project overview
János Farkas, Balázs Varga, Rodney Cummings, Jiang Yuanlong
Karthik Sethuraman, NEC
MEF LSO LEGATO MIRP -> In relation to TM Forum APIs Adrian O’Sullivan / Emmanuel Sarris / Davide.
TAPI Topology & Connectivity Concepts
Karthik Sethuraman, NEC Andrea Mazzini, Nokia
Presentation transcript:

MEF Common Information Model Overview Jessie Jewitt

Modeling in the MEF 4 Types of Modeling driven from LSO Engineering Methodology Business Process Modeling Defines the overall process flows relevant to LSO, i.e. MEF 50 Common Protocol Neutral Modeling Defines the MEF Core static model and extensions in the product / service / resource domains Interface Specific Modeling Defines “interface profiles” that characterize the dynamic behavior of specific interface functionality based on static model classes API Specific Modeling Defines functional interface specific “data models” (schema)

LSO Engineering Methodology - Modeling LSO Reference Architecture & Framework API Implementations Certifications Common Information Models MEF Service Definitions (including virtualization) Reference Implementations Business Process Flows API Specifications & Data Models Interface Profiles

MEF Modeling Process Based on ONF Modeling Process Core Modeling Defines an “umbrella” model based on the TMF SID Product / Service / Resource domains Working Group Specific Projects define MEF specific extensions to the core model, i.e. MEF 7.x Interface Profiles The protocol neutral information model extensions are “pruned & refactored” to show class realizations and behavior of specific functional interfaces Data Schema Interface profiles are mapped to API specific data schema used in the delivery of an API specifications

MEF Modeling Process

MEF Common Info Model Structure Core Model Interface Profiles Work Group Specific

Mapping of Core Model to LSO RA Customer Domain SP Domain Partner Domain PRODUCT Cantata (CUS:BUS) Business Applications Business Applications Sonata (BUS:BUS) Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) SERVICE Service Orchestration Functionality Interlude (SOF:SOF) Service Orchestration Functionality Allegro (CUS:SOF) Presto (SOF:ICM) Presto (SOF:ICM) RESOURCE Infrastructure Control and Management Infrastructure Control and Management ADAGIO (ICM:ECM) ADAGIO (ICM:ECM) Element Control and Management Element Control and Management Network Infrastructure

Core Product, Service, Resource Overview

MEF 7.3 Extensions to Service Model

Service to Resource* Mapping managed object classes at Service level (Legato, Interlude) EVC (the end-to-end CarrierEthernetService) ForwardingConstruct ForwardingConstruct NE NE NE NE UNI UNI LTP I-NNI I-NNI ForwardingDomain LTP managed object classes at Resource level (Presto) * Based on ONF Model