1. MEF API Development Approach
Jack Pugaczewski
Distinguished Architect
CenturyLink
March 26, 2018

2. Architecture and Framework Principles
Successful implementations of APIs, Portals and Open Source SHOULD be based on a well-defined architecture with clear and concisely defined interfaces.
Architectures provides layering and abstraction with interfaces thus enabling the separation of concerns and ability to clearly develop functions at each layer.
The communications across these well-defined interfaces are the APIs by the client-side and server-side.
The client-side and server-side is where the software logic for each functional component or set of components is developed (in-house/off-the-shelf/open source).
LSO Architecture and Framework implements the above principles.

3. MEF LSO Architecture
MEF LSO (Lifecycle Service Orchestration) is an example of layered and abstracted architecture.
Clear and concise interfaces are defined.
FCAPS+T/I[1] APIs are defined at each interface.
Interfaces are for intra-carrier/operator as well as inter-carrier/operator.
A Service Provider/Operator paradigm is necessary to abstract the customer away from the network complexities.
Customer should not be concerned with ENNI, OVC Per UNI/ENNI.
[1] Fault, Configuration, Accounting, Performance, Security, Topology and Inventory.

4. MEF LSO Development Community
Reference Implementation Projects
LSO Hackathon
MEF Dev Community
Complementary Open Source Communities
LSO Innovation Platform
SDK
System Integrators
MEF Members
EAC

5. MEF LSO API Roadmap LSO Cantata LSO Allegro LSO Sonata LSO Interlude
2017
Q1 2018
Q2 2018
Q3 2018
Q4 2018
2019 R1
(Portal-based Service Ordering)
LSO Cantata R1
(Elastic Service,
Notifications – Performance, Service Status, Testing, Fault )
LSO Allegro R2
(Ordering-II
Inventory,
Trouble Ticket)
SLA Reporting
Contracting
Catalog, Invoicing
Contact Mgmt.
Feedback from implementation
R1 , R1.1
(Ordering-I Serviceability)
LSO Sonata R3
(Quote-I) R4
(Quote-II) R1
(Elastic Service, Performance Reporting, Testing, Technical Fault Notification )
LSO Interlude
LSO Legato R1
(Service Catalog, Service Order, Service Inventory) R2
(SOAM/SAT) R3
(Optical)
LSO Presto R1
(NRP)
R1.1
(NRP)
LSO Adagio
Released
In Development
Planned

6. Collaboration with other SDOs
MEF and ONF with incorporation of TAPI.
TAPI provides reusable patterns for Connectivity Service, Topology Service, Notification Service, Path Computation Service and Virtual Network Service.
These are patterns that are used to support the FCAPS+T/I for every layer within LSO Architecture.
MEF Presto SOAM Interface Profile Specification is collaborating with ONF, ITU-T and IEEE.

7. Hybrid of Standards and Open Source
MEF has incorporated a hybrid of traditional standards development and open source.
The results are optimal and timely delivery of standards with open APIs, information and data models, reference implementations wrapped in SDK(s).
Process is a controlled loop with Hackathons providing real-world feedback to Interface Profile Specification, API, YANG data model development.
MEF has actively participated in tool chain development.
IISOMI EAGLE Tool which artifact maps UML (xmi) to YANG data model.

8. API Development
SDK (Software Development Kit) and Tool Chaining are key components of API development.
SDK and Tool Chaining enable the software lifecycle from API design to code.
Tools such as Swagger (Open API) enable client and server-side stub code generation using different languages and framework.

9. Model Centric Approach
OpenDaylight and ONOS are model-driven and can leverage model-centric approach.
SOF (Orchestrator), other Domain Controllers are API-driven and can leverage model-centric approach.
Protocols, API(s) communications, programming languages change and evolve. Model once defined stays relatively static.
Eclipse Papyrus for object model, use cases, interaction diagrams, state machine diagrams. Foundation for Interface Profile Specification.

10. Open Microservice Development – e.g., SOF layer
Definition of functional components (i.e., MEF 55) lend to microservice definitions.
Best of breed can be leveraged within a solution (i.e., SOF).

11. SOF Topology Engine
SOF-TE PoC demonstrates a working implementation of SOF sub-functional components and interface points defined by LSO in order to provide SOF with topology information.
SOF-TE demonstrates open software microservices of a number of SOF-sub components.
Topology Engine potential alignment with ONAP.

12. NaaS and Cloud – Building Vertical Markets
The combination of MEF NaaS REST API(s) and cloud REST API(s) enable customer to control network, compute and store.

13. 4 Parallel Tracks in 2018 MEF LSO API/SDK Training LSO Hackathons
Interface-specific quarterly releases
Models, API Guides, IPSs, LSO development stack
LSO Hackathons
Customer-driven use case that consumes MEF LSO APIs
MEF LSO API/SDK Training
End User 101, Developer 101, Micro Service 101
MEF 3.0 Liaisons and Marketing
Promote Industry adoption of MEF LSO APIs
Get MEF LSO APIs used by open source projects

14. LSO API and SDK: Key Goals for 2018
Grow contributors - 6 new vendors & 4 new SPs
Migrate all SDK projects to a model-driven open source tool chain
Improve tool chain robustness by identifying tasks and working on them in MEF hackathons and via MEF Dev Community
Arrange 2 semi-annual tool chain workshops
Onboard LSO development stack on MEF Innovation Platform
Arrange 2 semi-annual workshops on LSO development stack
Enable 3 MEF 3.0 implementation projects on LSO development stack running on MEF Innovation Platform
Define the process/timeline to convert Sonata API Guides to IPSs
Kickstart 3 new IPS efforts
LSO Cantata
LSO Allegro
LSO Interlude

15. Additional Slides

16. Tool chain Information model is domain specific and should be source.
Data models (i.e., YANG) can be derived.
APIs (i.e., Swagger) can be derived.
Data model (YANG) is used to generate stub code.
Swagger is used to generate both client and server side code.

17. SDK Contents MEF LSO Presto SDK includes MEF LSO Sonata SDK includes
API definitions (YANG/Swagger) for Network Resource Provisioning (NRP)
tutorial and example usage using ODL UniMgr
available for download here
MEF LSO Sonata SDK includes
LSO Sonata Address Validation API 
LSO Sonata Site Validation API
LSO Sonata Product Offering Qualification API
LSO Sonata Product Order API 
JSON representations for Product Spec description for Ordering & Serviceability
tutorial and example usage using dummy client and Sonata server

18. LSO Presto SDK v2017R1: 08/2017 v2018R1: 02/2018
Network Resource Provisioning (NRP) API
Get available topology
Create a connectivity service
Get a list of connectivity services
Delete a connectivity service
Reference Implementation
A packaged demo VM running OpenDaylight Unimgr that implements NRP API; also includes mininet and a suite of postman tests that act as a simulated client taking NRP API to the OpenDaylight SDN Controller
Support for Bandwidth profile handling in orchestrated CE services
Update github with new/modified yang models to incorporate NRP CfC comments 
Recompile ODL VM to consume the new/modified APIs
Support both ETH and ODU connectivity service requests as well as multi-layer topology
Reference Implementation
Quality improvement for ODL reference implementation
Topology service
Connectivity service
Improvement of experimental features
*In planning

19. LSO Sonata SDK v2017R1: 08/2017 v2018R1: 02/2018 Ordering APIs
LSO Sonata Product Order API 
Serviceability APIs
LSO Sonata Address Validation API 
LSO Sonata Site Validation API
LSO Sonata Product Offering Qualification API
JSON representations for Product Spec description for Ordering & Serviceability
Example
Demonstrates how a dummy client can use a portal to perform address validation for a service, check specific service availability at that address, & finally place the service order*
Quote APIs
Product Inventory APIs
Trouble Ticketing APIs
Ordering APIs (Phase II)
Example
Buyer/Seller emulators to use the latest version of Ordering and Serviceability APIs as well as Quote, Product Inventory, & Ticketing APIs
*Please note that the API definitions used in the tutorial are an older version and do not match the API definitions under the ‘api’ directory. 

20. LSO Legato SDK
*v2017R1: 05/2018
Work jointly with ONAP External API Project in defining use cases and information model for Legato
Leverage MEF Operational Threads and revise MEF 56, Interface Profile Specification: Service Configuration and Activation, to reflect consistent use cases
The Service Descriptor Model is key to Model-Driven Orchestration
Work with ONAP and TM Forum to define the Service Catalog and Service Instantiation API in a model driven and extensible fashion
Reference Implementation
A packaged demo VM to include a dummy client and ONAP orchestrator speaking LSO Legato APIs
*In planning