Showing posts with label MEF. Show all posts
Showing posts with label MEF. Show all posts

Sunday, June 24, 2018

MEF offers SDN/NFV Professional Certification

MEF announced the production release of its MEF SDN/NFV professional certification, which validates professionals’ knowledge, skills, and abilities in the domains of software-defined networking (SDN) and network functions virtualization (NFV). The MEF-SDN/NFV certification exam is built around the key themes of “Design, Deploy, Manage", and details and references are contained in the newly released examination blueprint. Professionals seeking to validate their competencies must be able to demonstrate their abilities in various design, installation, and security scenarios involving SDN, NFV, and instances when virtualized objects such as VNFs (virtualized network functions) are deployed into SDN architectures.

“We are delighted that MEF has created yet another skills certification in software-centric networking technologies, adding to its world-renowned Carrier Ethernet Certified Professional (MEF-CECP) credential,” said Nan Chen, president of MEF. “Given the rising deployment of SDN and NFV solutions globally, and the tremendous potential for telecom and enterprise IT organizations to leverage SDN and NFV, we are confident that this certification will open new doors, new jobs, and new horizons for the networking workforce. Organizations that encourage their IT professionals to train for and earn this credential will signal their commitment to excellence in their workforce. Already we have received inquiries from companies wanting to get their engineers, operators and technical architects certified.”

“This is the first certification of its kind in the exploding field of virtualized networking,” said Rick Bauer, certification director at MEF. “We’re grateful to have so many companies and organizations collaborating and providing their expertise, and we look forward to broad industry acceptance of this credential.”


MEF also announced that five training companies are qualified to deliver approved training for this certification.  The five Accredited Training Providers (MEF-ATPs) are Carrier Ethernet Academy, Criterion Networks , Perpetual Solutions , SDN Essentials, and Tech2000.

Incentives for IT/telecom professionals to earn this credential were also announced today by MEF.

MEF now offers three certifications as part of its comprehensive Professional Certification Framework: MEF-SDN/NFV Certified Professional, MEF Carrier Ethernet Certified Professional (MEF-CECP), and MEF Network Foundations (MEF-NF) certifications.

https://www.mef.net


Thursday, May 31, 2018

MEF advances MEF 3.0 Ethernet, IP, SD-WAN, and Layer 1 Services

Work continues to advance on MEF 3.0, which is the global services framework unveiled last November for “defining, delivering, and certifying agile, assured, and orchestrated communication services across a global ecosystem of automated networks.”

MEF reported progress on the standardization of orchestration-ready Ethernet, IP, SD-WAN, and Layer 1 services that form a core element of the MEF 3.0.

Specifically, MEF has published two new MEF 3.0 Ethernet and IP specifications, progressed two major MEF 3.0 SD-WAN projects, and moved closer to finalizing a MEF 3.0 Layer 1 service definition specification as soon as 3Q18.

“Expansion of MEF 3.0 standardization work beyond Ethernet to include IP, SD-WAN, and Layer 1 services is critical for enabling the streamlined interconnection and orchestration of a mix of connectivity services across multiple providers,” said Pascal Menezes, CTO, MEF. “Combining this work with the ongoing development of our emerging suite of LSO (Lifecycle Service Orchestration) APIs will pave the way for orchestrated delivery of on-demand, cloud-centric services with unprecedented user- and application-directed control over network resources and service capabilities.”

Here are some highlights:

MEF has just published the Managed Access E-Line Service Implementation Agreement (MEF 62), which defines a new service with a specific set of management and Class of Service (CoS) capabilities designed to accelerate service provisioning and to simplify management of services that traverse multiple operators. The MEF 3.0 Managed Access E-Line (MAEL) service is derived from the MEF 3.0 Access E-Line service specified in MEF 51.

MEF 62 reduces ordering and provisioning complexities when a service provider requires an Operator Virtual Connection (OVC) service from an operator by defining a MAEL service with a simplified set of CoS requirements – e.g., a single CoS name per OVC – coupled with a simplified set of management requirements for SOAM fault management, SOAM performance management, and latching loopback. By leveraging the management capabilities in the MAEL operator’s network, MEF 62 also intends to eliminate the need for a service provider to deploy hardware – e.g., a NID – at the subscriber’s location to monitor services.

AT&T, Bell Canada, Canoga Perkins, Ciena, Cisco, HFR, and Zayo joined Verizon in contributing to MEF 62.

MEF has published the Subscriber IP Service Attributes Technical Specification (MEF 61) as the first in a planned series of MEF 3.0 IP specifications aiming to address these challenges. MEF 61 specifies a standard set of service attributes for describing IP VPNs and Internet access services offered to end-users and will be used as a starting point for defining attributes for operator IP services. It introduces IP UNIs and IP UNI Access Links for describing how a subscriber is connected to a service provider as well as IP Virtual Connections and IP Virtual Connection End Points for describing an IP-VPN or Internet access service between those UNIs. Specific service attributes and corresponding behavioral requirements are defined for each of these entities. These include support for assured services – e.g. multiple classes of service, with performance objectives for each class agreed using a standardized set of performance metrics in a Service Level Specification. Bandwidth Profiles that can be applied to IP services are also described, allowing the bandwidth assigned to each class of service to be agreed in a standard way.

“The immediate value of MEF 61 is that it establishes common terminology and provides the ability to standardize service level agreements for IP services with customers,” said David Ball, editor of MEF 61 and Senior Software Architect, Cisco. “In the longer term, MEF 61 provides the basis for specifying operator IP service attributes, and it will enable standardization of LSO APIs for orchestration of IP services across subscribers, service providers, and wholesale operators.”

Albis-Elcon, Ceragon, Ciena, Coriant, Cox, Ericsson, HFR, RAD, TELUS, TIM, Verizon, Zayo, and ZTE joined Cisco in contributing to MEF 61.

MEF 3.0 SD-WAN -- there are two major SD-WAN initiatives underway: the Multi-Vendor SD-WAN Implementation project and the SD-WAN Service Definition project.  The first project is focused on addressing the rapidly growing problem of orchestrating services over multiple SD-WAN deployments that are based on different technology vendor products. MEF member companies – including SD-WAN vendors Riverbed, VeloCloud (now part of VMware), and Nuage Networks from Nokia and software development services provider Amartus –  are collaborating to use MEF’s new, standardized LSO Presto Network Resource Provisioning (NRP) API to meet these interoperability challenges.

In the second project, MEF members are collaborating to develop an SD-WAN service specification that defines the service components, their attributes, and application-centric QoS, security, and business priority policy requirements to create SD-WAN services. This initiative is led by Riverbed and VeloCloud, now part of VMware, with major contributions from Fujitsu.

MEF 3.0 Layer 1 -- MEF is in the final phase of the review and approval process for a new specification that defines the attributes of a subscriber Layer 1 service for Ethernet and Fibre Channel client protocols – used in LAN and SAN extension for data center interconnect – as well as SONET and SDH client protocols for legacy WAN services. Nokia, Bell Canada, Cisco, and HFR have contributed to this project.

Work already is underway on a companion specification defining Operator Layer 1 services between a UNI and an OTN ENNI (access) and between two OTN ENNIs (transit). This will provide the basis for streamlining the interconnection of multi-domain Layer 1 services.

What is included in MEF 3.0

There are four spokes to the MEF 3.0 wheel
       

  • Standardized, Orchestrated Services - including Carrier Ethernet, wavelength, IP, SD-WAN, Security-as-a-Service, and other virtualized services that will be orchestrated over programmable networks using LSO APIs. MEF 3.0 CE R1 is the first release within the MEF 3.0 framework, while work on standardizing orchestration-ready wavelength, IP, SD-WAN, and security services currently is progressing within MEF.
  •         Open LSO APIs - MEF’s LSO Reference Architecture guides the agile development of standardized LSO APIs that enable orchestration of MEF 3.0 services across multiple providers and over multiple network technology domains (e.g., Packet WAN, Optical Transport, SD-WAN, 5G, etc.). MEF recently announced the first releases of two LSO SDKs (software development kits) that feature inter-provider APIs for address validation, serviceability, and ordering and an intra-provider API for network resource provisioning. The LSO APIs included in these SDKs are available for experimental use by MEF members and associated MEF programs.
  •         Service and Technology Certifications. MEF is increasing the agility of its popular certification programs to accelerate availability and adoption of MEF 3.0 certified services and technologies. Iometrix continues as MEF’s testing partner, but the certification process is now being virtualized and taken into the cloud. A subscription model will be used for that vendors and carriers will be able to certify that their services and technologies comply with the latest MEF 3.0 standards. This should speed up the certification process considerably from days to minutes.
  •         Expanded Community Collaboration. MEF is working with service and technology providers, open source projects, standards associations, and enterprises to realize a shared vision of dynamic services orchestrated across automated networks. MEF has created a new compute, storage, and networking platform – MEFnet – that enables development, testing, integration, and showcasing of prototype MEF 3.0 implementations using open source and commercial products. MEFnet projects will help accelerate the understanding and adoption of MEF 3.0, as well as provide immediate feedback for standards development within MEF.

Tuesday, April 10, 2018

MEF advances its LSO architecture with 2 new specifications

MEF published two new specifications advancing the orchestration of MEF 3.0 connectivity services over multiple network layers, including the optical domain. Both standards were developed within MEF’s LSO (Lifecycle Service Orchestration) Reference Architecture.

Network Resource Management (NRM) – Information Model (MEF 59) -- defines the information model to facilitate the orchestration of Carrier Ethernet connectivity services through WAN SDN controllers, OTN subnetwork managers, and legacy network management systems. The MEF NRM model is specified in Papyrus UML and is based on current and developing best network management solutions by ITU-T, ONF, and TM Forum to allow for wider interoperability across multi-vendor and multi-technology platforms. This approach also facilitates upcoming work on OAM and OTN.

Along with the LSO RA, the MEF NRM serves as a basis for the new MEF 60 specification and thus supports the LSO Presto interface.

“MEF is playing a leading role to deliver the seamless management of services and resources in a multi-carrier, multi-vendor, multi-technology environment,” said Andrea Mazzini, editor of MEF 59 and Senior Systems Engineer, Nokia. “Interoperable network management models are a fundamental part of the picture and play a key role in the standardization of agile, assured, and orchestrated end-to-end connectivity.”

CenturyLink, Ciena, Cisco, Coriant, Ericsson, Huawei, Infinera, NEC, and RAD joined Nokia in contributing to MEF 59.

Network Resource Provisioning – Interface Profile Specification (MEF 60) -- provides an abstracted, intent-based solution for activation of – as well as topology retrieval of – network resources in support of MEF-defined services. The specification is complemented by an enhanced LSO Presto SDK (software development kit) that has been made available to the MEF Developer Community on the MEF GitHub.

"The CenturyLink-led MEF 60 provides an essential solution in the overall development of the MEF LSO portfolio of APIs,” said Jack Pugaczewski, editor of MEF 60 and Distinguished Architect, CenturyLink. “This development effort is a great example of a traditional standards development and open source hybrid, which resulted in a quality, expedited specification alongside the release of a corresponding API and SDK."

“MEF 60 is an excellent illustration of standards collaboration between industry organizations,” said Pascal Menezes, CTO, MEF. “Specifically, MEF 60 leverages ONF’s TAPI model for network resource activation and topology. The LSO Presto NRP API already is integrated into an OpenDaylight SDN controller plug-in, created by the MEF Developer Community working alongside the ODL UNI Manager project. And LSO Presto NRP service provisioning scenarios will be tested as part of the OIF 2018 SDN Transport API Interop Demo.”

CenturyLink, Amartus, Ciena, Cisco, Coriant, Ericsson, Huawei, Infinera, Iometrix, NEC, Nokia, and RAD contributed to MEF 60.

“MEF members have been working diligently to develop and demonstrate model-driven ‘North-South’ intra-provider LSO APIs and ‘East-West’ inter-provider LSO APIs that are required to orchestrate MEF 3.0 services,” said Nan Chen, President, MEF. “The new specifications enable us to define the critical LSO Presto NRP (Network Resource Provisioning) API for orchestrating services over a mix of underlying network technologies. We thank the LSO project teams for their diligent work and look forward to also sharing more good news related to inter-provider orchestration in the coming months.”

Thursday, March 15, 2018

Verizon and Colt demo inter carrier SDN orchestration

Colt and Verizon have demonstrated two-way, inter-carrier Software Defined Network (SDN) network orchestration.

The demonstration, which was held at an event in London, enabled each of the companies to make near-real-time bandwidth changes in each other’s production networks.

The companies described the inter-carrier SDN orchestration as a world first and an important step in enabling real-time cross-carrier automation.

Both companies are working with MEF to advance the development of inter-carrier business and operational LSO (Lifecycle Service Orchestration) APIs, which will accelerate the availability of this flexibility from many more partner networks.

Peter Konings, EMEA head of product development at Verizon, commented: “Enterprise networking is in the midst of a revolution. Organizations today want intelligent, dynamic networks that respond automatically to their changing business needs. Before today, no-one has been able to demonstrate elastic flexibility across carriers. Today’s demonstration is the first time anyone in the world has been able to flex network capacity in both directions across network boundaries. This will be a game changer for enterprise networking.”

Mirko Voltolini, Head of Network On Demand at Colt, said: “This showcase positively demonstrates the power of software-defined networking and how increased adoption is putting operators and customers in control of their networks and services. Previously, closed systems have made interoperability between service providers extremely difficult. Further, it validates Colt’s strategy of providing on-demand flexibility to truly enable customers’ digital transformation journeys. Through the use of SDN, providers are now able to better collaborate and innovate, ultimately benefitting customers.”

Daniel Bar-Lev, Director Office of the CTO, MEF, added:  “Proof of concept demonstrations and trials of inter-provider service orchestration are critical steps for making agile, assured and orchestrated connectivity services that span multiple operators a reality. We’re delighted to see today's demonstration moving the service provider industry towards this objective.”

Sunday, December 3, 2017

MEF 3.0 Certification - new subscription model



Want to learn more about the new subscription model for MEF 3.0 certification?

In this video, Bob Mandeville, President & Founder of Iometrix, talks about all of the changes for certification of MEF 3.0 products and services.

Iometrix has developed a radically different certification test platform for MEF 3.0. The certification model undergoes profound changes and the way that companies can access certification also undergoes profound changes.

See video: https://youtu.be/Ac5nsoFXWs0


Tuesday, November 21, 2017

Moving Software-based Networking Forward



Verizon is working with MEF to set standards and ensuring interoperability with customers and other carriers.

Think scale and more virtualization, says Eric Cevis, President, Verizon Partner Solutions.

See video:  https://youtu.be/ZKFfSvTY5SI


Thursday, October 19, 2017

Video: MEF and ONAP collaboration



It's all about carrier automation. MEF and ONAP recently announced a partnership to accelerate the rollout of agile, assured, and orchestrated services across automated, virtualized, and interconnected networks. Service providers, cloud providers, and enterprises are challenged to provide on-demand services profitably and competitively. This video features Pascal Menezes, CTO of MEF, and Dan Pitt, Senior VP of MEF, commenting on these developments.

See video: https://youtu.be/fSaF6syhZSU


Monday, September 11, 2017

Video: MEF – Reinventing Network Transformation

Michael Strople, Chairman, MEF and Zayo, President Enterprise Networks highlights MEF’s role in driving industry transformation as a key motivation for being part of the MEF community.

See video: https://youtu.be/jXAF_WPoCmw






Wednesday, September 6, 2017

ATIS and MEF publish specification for ordering Carrier Ethernet services

ATIS and MEF released a jointly developed specification that defines the process for ordering Carrier Ethernet services on a global basis.

The Ethernet Ordering Technical Specification focuses on business interactions associated with inter-carrier ordering of Access E-Line and Standalone UNI products, including use cases and specific MEF-defined attributes needed to support product ordering for each use case. Implementation details will be published separately in MEF’s LSO Sonata Interface Profile Specification for Ethernet Ordering that is on track to be released later this year.

ATIS and MEF described the new Ethernet Ordering Technical Specification as an important step toward creating a worldwide ecosystem of automated and interconnected networks that deliver agile, assured, and orchestrated services. This specification supports requirements defined in the LSO (Lifecycle Service Orchestration) Reference Architecture and Framework (MEF 55) for ordering services over the LSO Sonata interface that relates to inter-provider service orchestration. Information contained in the new specification will be used by both buyer and seller ordering systems for developing automated LSO API systems.

“This new joint specification transforms the Ethernet ordering process globally, thus enabling faster delivery of interconnected networks,” said ATIS President and CEO Susan Miller. “It makes the ordering process easier for customers while also advancing service provider business imperatives in this area. ATIS is proud to deliver another of our contributions from our collaboration with MEF.”

“MEF is pleased to work with ATIS to deliver a new ordering specification that will improve inter-provider operational efficiencies, enable service providers to be more responsive to customer demands, and help drive market growth on a worldwide basis,” said Kevin Vachon, COO, MEF.

“Today’s process is very provider-specific, and inter-carrier ordering is done either through spreadsheets or one-off solutions,” said Dawn Kaplan, MEF Operations Area Co-Director and Solutions Architect – CoE OSS, Ericsson.

“Defining a standardized process for ordering Carrier Ethernet products across service provider partner domains is critical to significantly streamlining the buying/selling process and thus enabling improved delivery time of interconnected networks. This specification is the first step in documenting an international consensus-based process that supports the entire order lifecycle. The joint team will also be publishing additional specifications that provide implementable APIs that align with this specification.”

Letty Walker, Senior Lead Analyst, OSS & Technical Support, CenturyLink, ATIS OBF OS Co-Chair and Joint ATIS-MEF Co-Lead added, “It is a wonderful opportunity to be part of a team that is able to collaborate in the development of the Ethernet Ordering Technical Specification. Given that ATIS has such broad ordering experience throughout North America, I feel that partnering with our MEF counterparts has led to a collaboration that will provide the framework for a unified platform defining requirements for Ethernet ordering throughout the entire international telecommunications community.”
ATIS and MEF are continuing in their joint efforts to enhance the international Ethernet Ordering process and plan further releases to incorporate additional MEF-defined services.

The Ethernet Ordering Technical Specification can be downloaded here on the MEF Technical Specifications page or here in the ATIS Document Center.

http://www.mef.net
http://www.atis.org

See video: https://youtu.be/O46RPr3Sg18

Thursday, August 17, 2017

SD-WAN Managed Services update with FNC's Ralph Santitoro



Fujitsu Network Communications delivers SD-WAN-as-a-Service, a subscription-based SD-WAN managed service, that enables service providers to quickly get to market with an SD-WAN service offering.

“Fujitsu’s SD-WAN-as-a-Service uses the MEF’s work defining SD-WAN terminology, fundamental SD-WAN service capabilities and LSO reference architecture.  The MEF’s new SD-WAN service work has been quite beneficial in discussions with service & technology providers and end users, says. Ralph Santitoro, Head of SDN/NFV/SD-WAN Services at Fujitsu Network Communications.

See video: https://youtu.be/iTWO-2NakVY





Wednesday, August 9, 2017

Top Reasons to Attend MEF17 - November 13-16, Orlando



Kevin Vachon, COO, MEF shares top reasons why industry professionals will want to attend the MEF17 (MEF17.com) global networking event to be held on 13-16 November 2017 in Orlando, Florida.

Highlights include:

More than 1,000 attendees from 275+ companies and 35 countries
Leading service and technology executive speakers
15+ live Proof of Concept demonstrations
5th LSO Hackathon
Onsite professional training courses & certification exams for MEF Carrier Ethernet Certified Professionals & MEF Third Network Foundations
Global Media Hub with 50+ press & analysts

See video: https://youtu.be/SnmbIJgQ3JQ



Monday, August 7, 2017

Video: Extending MEF's LSO Architecture


Stéphan Pelletier, MEF Orchestration Area Co-Director and Director of Product Management, Oracle, discusses how LSO (Lifecycle Service Orchestration) APIs will enable end-to-end service orchestration across multiple service provider networks and multiple technology domains. LSO will help overcome the biggest OSS-related obstacles that have impeded delivery of on-demand services across providers. Stéphan explains why Oracle has embraced LSO and is playing a lead role in contributing to LSO development within MEF.

See video: https://youtu.be/yHxa7Y2_GEk


Thursday, August 3, 2017

Dan Pitt, MEF: Perspective on Open Source



The industry is looking very closely at open source software and open source hardware for a number of reasons, says Dan Pitt, MEF, Senior Vice President. Open source shares the development costs in a way that provides everyone with access to the same code base. MEF builds a larger framework that incorporates components that could be built with open source or closed source software elements, shows how you can create end-to-end services with them, and defines LSO APIs that MEF members can instantiate with open source software. MEF currently is developing Software Development Kits (SDKs) for the LSO APIs.

See video: https://youtu.be/lBA9RjzvNdU



Monday, July 31, 2017

MEF Update and Scope with Nan Chen



Nan Chen, President of MEF, provides an update from MEF’s recent Annual Meeting in Toronto.  MEF is enabling service providers to create a global ecosystem of automated networks that deliver agile, assured, and orchestrated services.

There are 4 major areas of strategic work:
(1) Third Network services (wavelength, Carrier Ethernet, IP, SD-WAN, Layer 4-7 cloud services),
(2) LSO Reference Architecture and Open APIs,
(3) reference implementations and MEFnet, and
(4) certification programs for services, technology, and professionals.

These topics and more will be explored at MEF17 (www.MEF17.com) , 13-14 November in Orlando, Florida.

See video: https://youtu.be/5NexRVi2VkI


MEF - Advancing the Industry



Over the last few years, MEF has done three very important things: (1)  shifting beyond Ethernet to support other connectivity types and network-based apps; (2)  developing Lifecycle Service Orchestration (LSO);  shifting from just implementing technology specs to implementing LSO APIs, reference processes, and other operations enablers. The combination of these three will be very powerful, says Allan Langfield, Executive Director of Product Management at Comcast Business.

Recorded at the MEF Annual Member's Meeting in Toronto.

See video: https://youtu.be/5eb0pwSpj-M


Wednesday, July 26, 2017

MEF aims to define the future of Lifecycle Service Orchestration – Part 2

link to part 1 of this article

by Bartosz Michalik of Amartus

OpenCS Packet WAN project advances development of LSO

Together with Donald Hunter from Cisco, I have the privilege of co-leading the OpenCS Packet WAN project, which is one of the seven initiatives started in OpenCS ecosystem. The aim of the project is to deliver a reference implementation of an SDN controller that manages multi-vendor networks. The northbound API was released as a part of Presto SDK, which, in its current version, focuses on Presto network resources provisioning (NRP) models. Packet WAN is an open source module of the OpenDaylight controller called Unimgr. But, before I delve into the project details, let me take you on a journey through how we got to this stage of the development.

LSO hackathons throwback

The LSO development effort started in Dallas, in November 2015, during the first LSO Hackathon that was co-located with MEF’s GEN15 conference. At the time, I joined one of the Hackathon teams as a regular participant, and together with 40+ other colleagues from various vendor and provider companies, we were experimenting with the first ideas around Presto API. This experience had a great influence upon me, and it turned out to be extremely productive in terms of the LSO development. As I already mentioned at the beginning of this article, soon after the Hackathon I summarized the work of our team and presented it in this guest blog post at SDxCentral.

Since that first Hackathon, MEF organised three successful meetings in Rome, Baltimore and Frankfurt that saw developers, engineers and networking experts from MEF member and non-member companies invest their exceptional skills in LSO evolution. For a recap of the last Frankfurt Euro17 Hackathon, please go to this blog post by Charles Eckel, an Open Source Developer Evangelist at Cisco. At the consecutive Hackathons, we were crowded in a confined space and turning coffee, sweets and brainpower into Presto, Legato and Sonata LSO building blocks code. In parallel, on the official level, OpenCS and OpenLSO were launched, and the Hackathon teams could start remote collaboration on a daily basis.

To facilitate continuous development, MEF has built MEFnet, a compute-storage-networking platform, which delivers technical facilities for the Third Network reference implementations, OpenLSO and OpenCS projects, and gives interested parties an ability to evaluate APIs using reference implementations deployed to the MEFnet cloud.

Recently, we have implemented agile methodologies with the aim to iteratively deliver APIs, their reference implementations, and other artifacts that, when they are combined, will become LSO IRP SDK. And only a few months ago MEF initiated yet another program to welcome contributions from academia – namely MEF Software Developer Community. The idea is to give researchers and students an opportunity to participate in the development of Lifecycle Service Orchestration. The next edition of the LSO Hackathon is coming this fall to Orlando, co-located with MEF17. Check out this MEF17 link for more details and information on participation. All hands on deck!

What Is OpenDaylight Unimgr plug-in?

So, to return to 'my' Hackathon project. OpenCS Packet WAN is a project that delivers orchestration of MEF CE 2.0 services with SDN OpenDaylight controllers in combination with CE 2.0 networking devices. It has been developed as an OpenDaylight Unimgr module. For the current implementation, we use the ODL controller similarly as we did at the first Hackathon when we were experimenting with some ad-hoc Presto NRP ideas: https://wiki.opendaylight.org/view/Unimgr:Main.

However, the model itself has evolved a great deal - from the prototype, via the ONF Core model-based data model to ONF Transport API (T-API). We have also been working on improving the architecture of the solution and adjusting it to the model changes.

Unimgr is a platform that focuses on the Presto NRP-compliant network resource activation API and is a good starting point to making a network LSO-compliant. The most important concept in our Presto implementation is a driver that encapsulates protocol- and vendor-specific logic to make a sub-segment activation possible. What it means is that networks built using Cisco and/or Juniper devices, can be using two different drivers to manage these types of devices. In addition, a driver is required to contribute an abstract representation of managed devices to the Unimgr topology. Why? Because an NBI client (e.g. Service Orchestration Functionality – SOF) needs to know the current state of the network to be able to trigger resource activation requests.

To support other network vendors, there are three drivers being maintain – Cisco XR driver for MPLS, OVSDB driver for SDN-like networks, and a dummy driver, which can act as a template and requires a minimal amount of code to meet a Unimgr driver contract. Once the driver is installed, then Unimgr middleware will begin handling the RPC requests, decomposing them and triggering requests to the registered drivers if needed.

The Unimgr development plan is aligned with MEF SDK effort and OpenCS planning. In fact, the second iteration of OpenCS is about to be delivered as a part of the ODL Nitrogen release. Some of the new features include:

•   The implementation of the latest Presto NRP.

•   Support for P2P connection over multiple drivers.

•   Support for dynamic bandwidth changes in the drivers that we host in the project.

In addition, a simple implementation of MEF LSO Legato will also be delivered for the scenarios in which a fully-featured SOF (e.g. for a lab/experimental network) is not needed.

The future for the LSO ecosystem

The LSO ecosystem is dynamic and fast growing which means the future of LSO is very bright. However, it is important to continually grow this ecosystems, which means encouraging engineers and coders from more companies to join the upcoming meetings and hackathons. The next big LSO hackathon is in Orlando, FL, 13-16th November during the MEF17 show.

About the Author

Bartosz Michalik is a Software Architect at Amartus, a Certified MEF Engineer, and a holder of the MEF Recognition Award for LSO Hackathon blogging and facilitation. He leads the LSO Presto Hackathon project, and co-leads the OpenCS Packet WAN project together with Donald Hunter from Cisco. He is also a contributor to the Open Daylight UniMgr project. E-mail me at a Bartosz.Michalik@amartus.com with any questions or queries.

(More information about MEF’s Third Network Vision and Lifecycle Service Orchestration is available here: https://www.mef.net/third-network/lifecycle-service-orchestration)

SD-WAN Interaction and the Importance of Interoperability



Verizon is rapidly expanding its portfolio of virtual services, including SD-WAN. Interoperability is increasingly important as these are rolled out across the globe. The ability to link SD-WAN into other services is critical, says Shawn Hakl, VP, Product and New Business Innovation, @VZEnterprise.

See video: https://youtu.be/2EysfBTwidc

Recorded at MEF Annual Member's Meeting in Toronto.


Intent-based Networking and MEF



Intent-based networking is an important part of MEF's work on Lifecycle Service Orchestration (LSO).

Intent-based networking makes use of next generation network policy frameworks and will enable top-level business and application developers to express the goals of their organization without having to define algorithmically how those goals are accomplished, says Dr. John Strassner, MEF Orchestration Area Co-Director; CTO, Software Lab, Huawei Technologies.

Recorded at the MEF Annual Members' Meeting in Toronto.

See video:  https://youtu.be/LuwEaFPy5wc




Introducing MEFnet



Daniel Bar-Level, Director, Office of the CTO, MEF provides an overview of MEFnet – a new compute-storage-networking platform that enables development, testing, integration, and showcasing of Third Network service reference implementations based on open source and commercial closed source products.

MEF members currently are working on three 3 reference implementation projects on MEFnet:  (1) orchestration of Carrier Ethernet and IP services across 3 service providers using open LSO APIs; (2) an ONAP-to-ONAP use case involving LSO-enabled automation of inter-carrier processes like serviceability and ordering; and (3) a project focused on enabling SD-WAN managed service providers to extend their service reach in an automated way to locations served by broadband access partners.

See video: https://youtu.be/7P_alPofzUM



Tuesday, July 25, 2017

MEF aims to define the future of Lifecycle Service Orchestration – Part 1

by Bartosz Michalik of Amartus

MEF is an industry body that, besides other activities, defines the LSO capabilities and APIs to automate the entire service lifecycle in a sustainable fashion. This activity will allow service providers to attain coordinated management and control across all network domains responsible for delivering end to end connectivity services. In order to enable that coordinated management and ensure efficient communication within networks, MEF has defined the reference architecture. In short, this architecture comprises functional blocks and 'LSO Reference Points'. Reference Points are the logical points of interaction between specific functional management components, such as business applications, service orchestration functions (SOF), or infrastructure management and control applications (ICM). The Presto Management Interface Reference Point is the 'north-south' interface for network resource provisioning that sits between the SOF and ICM, and according to MEF 55 (https://wiki.mef.net/display/CESG/LSO+Presto), it is "needed to manage the network infrastructure, including network and topology view related management functions".



Currently, the LSO Presto API efforts are spearheaded by CenturyLink, with active contributions from Amartus, Ciena, Cisco, Ericsson, Infinera and NEC.

Industry-wide Collaboration Accelerates Realization of the Third Network Vision

Last year, MEF began the process of specifying the industry standard to accelerate the adoption of orchestrated network services. Enabling and assuring Third Network services across multiple provider networks calls for an industry-wide collaboration because of the involved level of complexity. In order to facilitate that cooperation and complement the work of its Technical and Operations Committee, MEF has come forward with a number of initiatives.

What emerged from that work was a plan to support and validate the work around MEF standards and LSO architecture by delivering open and close source reference implementations that realize the ideas defined in MEF 55 specification, outlining the LSO Reference Architecture and Framework. MEF has launched a series of initiatives that allow the in-network validation of Lifecycle Service Orchestration data models and interfaces. The current effort of the working groups is streamlined under the umbrella terms of Open Lifecycle Service Orchestration (OpenLSO) and Open Connectivity Services (OpenCS) ecosystems.



OpenLSO is focused on the implementation of functions and APIs specific for service orchestration functionality (SOF). It primarily targets service providers who are accelerating their adoption of LSO to enjoy all benefits of end to end service orchestration over standard MEF services. OpenCS focuses on Presto NRP, which is an LSO interface reference point (IRP) specific for infrastructure and control management (ICM). OpenCS provides reference implementations of connectivity services using combinations of open and close source software, open hardware, SDN, NFV and Carrier Ethernet (CE) 2.0-certified devices. To leverage these technologies, MEF develops this work stream in close cooperation with open source projects such as ON.Lab, OpenDaylight and OPNFV. This ecosystem should be of interest to those service providers that are adopting SDN and NFV to deliver MEF-defined connectivity services.

About the author

Bartosz Michalik is a Software Architect at Amartus, a Certified MEF Engineer, and a holder of the MEF Recognition Award for LSO Hackathon blogging and facilitation. He leads the LSO Presto Hackathon project, and co-leads the OpenCS Packet WAN project together with Donald Hunter from Cisco. He is also a contributor to the Open Daylight UniMgr project. E-mail me at a Bartosz.Michalik@amartus.com with any questions or queries.

(NB: Further information about MEF's Third Network Vision and Lifecycle Service Orchestration is available here: https://www.mef.net/third-network/lifecycle-service-orchestration)

See also