Skip to main content


OPNFV – Ready, Set….Go!

By Blog

Thank you for your interest in the OPNFV Community! To make getting started with the community a smooth process, this post will guide you through the basics of our resources, projects, tools, and processes.

OPNFV InfographicOPNFV consists of multiple projects focusing on everything from hardware management to KVM enhancements to running applications. We work closely with underlying upstream projects  to help accelerate NFV via an integrated, open platform.  Beyond new features, our main focus is integrating of open source components into the platform with proper verification and validation. We have several projects designed to to drive upstream implementation and provide hardware infrastructure, tool sets, testing frameworks and so forth. Furthermore, we encourage every participating member to use Agile methodologies as we believe in speed, proactivity and flexibility. If you would like to learn more about OPNFV in general before jumping in, feel free to reference  the OPNFV website or take a look at the OPNFV Wiki.

If you’d like to jump right in,  the absolute first step is to create a Linux Foundation account and visit the tools page where you will find links to all of the developer tools available.  (Note, in most cases you will  only have read rights, but once you begin to contribute to a project you will get the access you need to get started.)Our community believes in coordination and well organized activities as well. This means that we plan and track our tasks within each project around the theme of releases. More detailed information about our project plans are documented in Jira, which can be a good resource to reference tasks or find issues to work on. If you’re not familiar with this tool, check out the Getting started web page for guidance.

You may have heard  that OPNFV is a “mid-stream community” which is not supposed to carry any code on its own. It actually depends on how  you define “code.” Let’s use the word  “artifacts” instead,  which includes test cases, documentation, integration scripts and so forth. The common integration point is Git, which we use for version control. You should also familiarize yourself with Gerrit; via the OPNFV Gerrit you can access repositories and provide patch reviews. You’ll need to set-up a few things to get started with Gerrit, like your email address, and you should also not forget to sign the CLA! Without that you will not be able to submit a patch. You can also access our artifacts page for some results and check out project documentation or even ISO images.

As with every other open source community,  we have several channels for communication. These include weekly meetings, mailing lists and IRC channels for daily text-based discussions. The Meetings wiki page contains an up- to-date list of meetings,  including agendas and all the information required for joining. We use GoToMeeting for voice and also the #opnfv-meeting or project IRC channels on Freenode for meeting minutes. You can join to the development activities, raise topics for discussion or ask questions on the opnfv-tech-discuss mailing list, which like all the other lists, is also archived.

And last, but not least, the most important thing among all, if you would like to meet with the eager fellow developers, keep an eye on the Events web page for the list of upcoming events, where you can find us.

“That’s all folks!”

Stay tuned for more, and thank you for joining to this short tour of OPNFV!  I hope to see you again on a project meeting, on IRC or even at the next, and very first, OPNFV Summit!

About the author of this post

OPNFV Developer Spotlight: Peter Lee

By Blog

The OPNFV community is comprised of a diverse set of active developers who are passionate about transforming the industry through open source NFV. This new blog series highlights the people who are collaborating in the trenches to build a de facto standard open source platform for NFV.

About Peter Lee

Peter LeePeter Lee leads R&D at ClearPath Networks where he is responsible for driving technology innovation and strategic vision across the company’s products and services. He is also serving as project lead for OPNFV Promise project dealing with Resource Management for the Virtualized Infrastructure. He is the primary developer for YangForge model-driven open-source framework and serving as project lead on YANG enablement for ON.LAB XOS/ONOS projects. He is an avid practitioner of pragmatic programming principles and a strong advocate of open source development and open standards-based initiatives. Peter holds B.S. degrees in Computer Science, Electrical Engineering, and Computer Engineering from Duke University.

What projects in OPNFV are you working on? Any new developments to share?

I’m currently leading the OPNFV Promise project and committer to IPv6, MOVIE, and Doctor. The Promise project was initiated just after OPNFV was introduced and addresses the ETSI NFV use case requirements around Resource Reservation for Future Usage. We’ve worked closely with the ETSI NFV IFA working group (many of our project members active in both organizations) and received strong collaboration from NTT-DOCOMO, NEC, Ericsson, and AT&T – just to name a few participating organizations.

During the upcoming OPNFV Summit, the OPNFV Promise project team will be demonstrating our first implementation, which will showcase live integration with multiple OpenStack environments for providing active capacity awareness, planning future capacity increase/decrease, reserving resources for future utilization, and allocating resources based on reservations.

During the Summit, we will also provide an in-depth overview of the underlying YANG Model-Driven framework (YangForge) which ClearPath open-sourced back in July.  The YangForge framework powers the Promise implementation and provides a rich abstraction for YANG-driven NB interface generation for CLI, REST/JSON, as well as web sockets.

Where do you see OPNFV in five years?

Within five years, I believe that OPNFV will successfully deliver a NFV platform that will be deployed by many communications service providers around the globe.  We will be actively working on a number of new use cases including service federation across clouds, along with the next generation real-time resource and service exchange systems.  With the emergence of Personal Clouds, OPNFV will be focusing on enhancing per-subscriber networking experience for the users, while addressing geo-political concerns around data privacy, lawful intercepts and other transport related challenges as the network boundaries become blurred into a series of dynamically created service paths across carriers.

What is the biggest challenge facing networking today and how do you see NFV helping to resolve it?

The networking industry today faces a significant challenge in recruiting and growing software development talent. With so much competition from the mobile, social, and other web-centric industries, our industry needs to focus on highly targeted developer outreach programs (into external development ecosystems) to spread awareness of recent developments within the networking industry while specifically highlighting the new monetization opportunities. I believe that the NFV movement captures the key ingredients for opening up the software development ecosystem as we usher in the next generation of marketplace-driven networking apps to become the new currency for delivering services to end users running directly on the carrier networks.

What is the best piece of developer advice you’ve ever received?

“There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. It demands the same skill, devotion, insight, and even inspiration as the discovery of the simple physical laws which underlie the complex phenomena of nature.”–C.A.R. Hoare

The above observation has provided foundational guidance throughout my software development career. I always strive to identify the primitive logical constructs that succinctly expresses the desired solution, give it a whirl, attack the underlying implicit assumptions, then try again until further decomposition is no longer practical.

Unfortunately, the emphasis on design over implementation is often at odds with many recent trends in software development methodologies where quantitative progress is being championed over qualitative progress (which is inherently much more difficult to measure). Open Reference Platforms such as OPNFV provide the testing grounds for newly emerging paradigms in model-driven and functional software construction that serve to shift the focus back on design along with a new trajectory for collaborative innovation.

A View from the Board: OPNFV at One Year, Part 2

By Blog

OPNFV has made great progress since we started the organization in September 2014. As a community, the OPNFV project represents the first time open software developers, architects and standards professionals from over 55+ companies are collaborating to create an open framework for NFV platforms. The first release of OPNFV Arno in June and the Arno SR1 in September are great first steps in having a common build with some basic Continuous Integration/Continuous Deployment for an NFV platform consisting of Openstack, OpenDaylight and Linux operating system on an Intel platform. This integration allows OPNFV to evaluate the NFV platforms and develop further capabilities.

Trying to shepherd an entire industry to work together and create an open NFV platform in this fast-evolving market is pretty daunting. But one thing became clear to me due to my involvement in AT&T’s software-centric network transformation – the networking industry has been very inefficient by solving the same problems again and again in different silos. These problems are operationalizing the instantiation and lifecycle to support an application/service model, which is the competitive edge for each service provider. Our operational challenges with SDN and virtualization are even more similar for the service provider and enterprise end-users. We are all using essentially the same NFVi platforms – compute, storage and networking in a “data center”/cloud environment.

There are a lot of open source projects appearing monthly and the platforms used are also evolving (e.g. containers). But each of these open source projects trying to optimize in their own space is necessary, yet not completely sufficient for NFVi platform users.

OPNFV is the only public forum with a broad community where the industry can pull together the components of the platform(s) to see if they work together. It is also an incubation environment to try out new software features and/or hardware components. We are already doing this now, except within our own corporate silos. Think about the power of open communities – can you imagine how much faster the industry will move if we come together to eliminate the interoperability differences among the various platform components?

It’s clear what the use cases should be to drive this integration: Day 0 of instantiating a virtual application with its networking and then the lifecycle of the virtual application within its networking. Automated performance testing with common traffic profiles against common benchmarks to get to the stress points in the NFVi platform are also critical to flush out.

We need more user input – enterprise and service providers – on these use cases as well as test resources to validate the platform(s) built. So, I encourage the end users and suppliers to join in the OPNFV requiremets, collaborative development and integration testing of the NFV platform.

Learn more on how to get involved with OPNFV.

About the author of this post

Margaret ChiosiMargaret Chiosi, AT&T
Margaret Chiosi, Distinguished Network Architect AT&T Labs, has been involved in data networking for 30+ years. Margaret’s current focus is on implementing AT&T’s User Defined Network Cloud (UDNC) which is based on SDN and Virtualization building blocks. She has led large organizations responsible from concept through development and deployment of emerging global network services, development of data networking equipment, and strategic direction for data services and products. Margaret was one of the key members in the creation of the ETSI ISG – Network Virtualization Forum as well as the Linux Foundation Open Platform for NFV, OPNFV.

A View From the Board: OPNFV at One Year, Part 1

By Blog

This month marks the end of the third year of the engagement of the telecom industry with this thing we call Network Functions Virtualization (NFV). Three years ago when a few of us got together to write the seminal white paper that coined the term NFV, and launched a call to our industry to work with us in this space, we had no idea how long it would take us to get traction and build a community. In these three years we have witnessed an explosion of effort around these three letters,  and the establishment of a global community that has been engaged in defining frameworks and requirements, building proof-of-concept demonstrations and developing products and solutions.  The number of industry events and conversations around this topic are also quite mind boggling (e.g., ~ 6,000 people shared #NFV links on Twitter in September 2015). My own journey from a carrier (Verizon) to a solution provider (HP) during this period has allowed me to appreciate how truly global this effort is, with both users and suppliers engaged.

We have also just crossed another milestone in the NFV journey. Last month marked the completion of one year of the existence of the Open Platform for NFV (OPNFV). This open source collaborative project housed under the Linux Foundation was expressly instituted to accelerate the implementation and adoption of the NFV approach. The goal is to create a reference platform and a flexible framework for NFV based on open source software. It will integrate the efforts of various other open source projects and apply them to NFV, and fill in the gaps if necessary – the OPNFV mantra being: upstream first!

In one short year OPNFV has moved quickly beyond the initial formation phase.  With 55 member companies, 43 approved projects, ~ 100 developers, ~ 1500  commits to date, and over 430  participants on the IRC  with 45K +  IRC messages – this is clearly a vibrant and productive community. And the community is not just having an interesting set of discussions, it has produced OPNFV’s first software release – OPNFV Arno – that provides a software platform for developing the NFV reference framework. This initial effort involved the integration of various open source software platforms (OpenStack, Open Daylight, Ceph, KVM) into an integrated release with installation and continuous build environments that allow the software to be installed and run on a variety of hardware.

As we begin the second year and embark on the next release – Brahmaputra – the focus is shifting to NFV functionality and use cases, and to testing and interoperability. The Pharos project within OPNFV has created 10 globally distributed operational OPNFV testbeds with more planned. These are member- donated and operated labs that are available for testing of OPNFV software releases, the testing of OPNFV releases with third-party VNFs and other related systems. This has resulted in a global community that is engaged in the business of establishing interoperability, integration and standardization across the NFV solution space, in an open and transparent manner.

We invite all who are engaged in the current effort to transform the telecom infrastructure – users and suppliers – to join us at OPNFV and develop the tools to help accelerate this transformation. The journey continues and we are proceeding full speed ahead.

About the author of this post

OPNFV Arno SR1 is Here

By Blog

While much of the OPNFV community is engaged on the next milestone release, Brahmaputra, a team of developers has been hard at work making iterative updates and improvements to our first release, Arno. After dedicated work and collaboration, today we’re proud to announce the availability of OPNFV Arno SR1!

SR1 was designed to address known issues in the initial release for incremental stability and improved predictability. Specifically, this includes the enablement of virtual deployments complementing the bare-metal deployment, as well as component upgrades/bug fixes (e.g. full plug-in support for OpenDaylight in Fuel).

Arno SR1 also delivers deployment environment enhancements, such as:

  • Harmonized network configuration, which alleviates the need for network reconfiguration between runs of different installers on the same hardware
  • Simplified network configurations which simplifies deployments in locations with access restrictions
  • Simplified deployments on de/re-commissioned hardware (including clean-up scripts, etc.)
  • Enhanced configurations such as VM resources, floating IPs, etc.

Hear from the developers themselves on what’s new in Arno SR1:

Tim Rozet of Red Hat on Foreman/Quickstack:

“For Arno SR1 we have worked on fixing bugs and adding features that make the installation/deployment process of OPNFV more flexible and more reliable.  We gained a lot of feedback from OPNFV users for the Arno release and realized a lot of users wanted to try OPNFV, but did not have the hardware setup of 5 or 6 servers to do so.

To address this, we focused on adding a lot of support for virtualized deployments with minimal hardware requirements so that more users would be able to simply deploy and try out OPNFV on their laptops.

In addition to these features, other fixes have gone in with respect to deployments as well as migrating OpenDaylight from Helium SR3 to SR4, so users should experience a more stable OPNFV environment with Arno SR1.”

Morgan Richomme of Orange and Jose Lausuch of Ericsson on Testing:

“In SR1, we did not integrate new test cases but instead consolidated the four suites of tests already  integrated in Arno. We ensured that no regression occurred despite strong refactoring on the installer side. The automation of the tests has also been enhanced.

In preparation for Brahmaputra, we were able to automatically run the functional tests on the same POD (same hardware) with the two installers; this task required some integration work that should contribute to a better interoperability and a better user experience moving forward.

Additional preparation for Brahmaputra includes integrating the experimental mechanism of test result collection for one of the test cases, which will be generalized in Brahmaputra. It should help the community to build a testing dashboard and also reflect the influence of hardware on functional testing.”

The work done on SR1 of Arno improves the foundation upon which our future releases will be built. Kudos and deep thanks to the technical team behind this release!

More technical details about what’s included are available here:

Inaugural OPNFV Summit Schedule Announced, Sessions Span Technical and Business Tracks

By Blog

We are gearing up for our inaugural OPNFV Summit happening November 9-12 in Burlingame, CA. After reviewing an astounding 131 submissions, we are pleased to announced our final agenda that includes over 65 technical tracks including a focus on business and use cases, as well as hands-on sessions and tutorials.

We start the week with the OPNFV Design Summit, which gives our developer community the opportunity to come together and collaborate face-to-face on the upcoming Brahmaputra release, conduct project breakout sessions and organic meetups. Our friends from the OpenDataPlane project and OpenDaylight Project will also host tracks at the Design Summit, which can be added to any OPNFV Summit registration at no additional cost.

Our main conference is divided into tracks and session groups that highlight a number of key focus areas for the project. These provide a focused way to collect talks, panels, and tutorials related to a particular area and will enable the community to hear a range of perspectives from service providers, developers, and other community members on a given topic.

Schedule Overview & Highlights:

  • Introduction to OPNFV Technical Track covering the Nature of OPNFV (Technology, Status & Evolution) and Community
  • An OPNFV in Depth Technical Track reviewing Security, SFC and Hands-on Deployment
  • A Looking Outward Technical Track covering SDN and Standards and Fora
  • The Looking Ahead and Getting Real Technical Track with sessions on Futures and Testing
  • An OPNFV Qualities Technical Track investigating Telco Grade Requirements and Efficient Forwarding
  • A Business & Use Case track including user stories and use cases from Alcatel-Lucent, Huawei, Cisco, Akamai and a panel of cable operators moderated by CableLabs

Previously announced keynotes include:Voice of the Customer Keynote Panel featuring:

    • Jacob Loveless, CEO of Lucera
    • Hal Stern, Executive Director of Advanced Technology and IT Planning at Merck
    • Bikash Koley, Principal Architect & Director, Network Architecture and Engineering at Google
    • Alan Blackburn, VP Architecture & Design for AT&T
    • Philippe Lucas, SVP, Standardisation, Orange
    • Moderated by Ulf Ewaldsson, CTO of Ericsson
  • Sandra Rivera, VP, Data Center Group and General Manager of Intel’s Network Platforms Group, Intel; OPNFV Marketing Chair
  • Dr. Prodip Sen, CTO of the Network Functions Virtualization (NFV) Business Unit, HP. OPNFV Chair
  • Strategic Technology Upstream Panel featuring:
    • Jonathan Bryce, Executive Director of the OpenStack Foundation
    • Neela Jacques, Executive Director of the OpenDaylight Project
    • Pere Monclus, CTO of Plumgrid
    • Brandon Phillips, CTO of CoreOS
    • Reynold Xin, Co-Founder of Databricks
    • Moderated by Peter Jarich of Current Analysis
  • Chris Wright, Technical Director of SDN, Red Hat
  • Heather Kirksey, Director of the OPNFV Project

Given the high number and caliber of entries, it was an incredibly tough process for our committee to whittle it down to just 65. We are very excited for this inaugural event that is bringing together the end users, developers, networking industry and open source communities to advance the development and adoption of an open source NFV platform. Thank you to everyone who submitted — it’s each and every one of you who keep us going and we couldn’t be more thrilled to have such an awesome line-up planned for our very first Summit!

Access the full agenda here and go here to register now — only US$299 through October 15th!

Thank you to our Sponsors, inlcuding HP, Intel and RedHat. See here for a full list of all event sponsors:

NFV Community Comes Together to Collaborate on the Future of the Industry

By Blog

Marc Cohn, OpenDaylight board director and SVP of marketing for ClearPath Networks,  just posted a great summary of the most recent ETSI NFV ISG meeting to SDxCentral, entitled NFV Insider #11: Collaboration (and More Collaboration). Held in close collaboration with OpenDaylight Summit and MEF which were also happening in Silicon Valley that week, key discussion topics included NFV Phase 3 (2016 and beyond), which is “aimed toward establishing an open ecosystem as NFV is deployed.”

Hear more on Marc’s insider perspectives of the evolution and challenges of NFV and how the industry–operators, vendors, open source projects –can capitalize on NFV ISG’s progress. Check out  the full post on SDxCentral or on the ETSI NFV ISG Blog.

OPNFV Brahmaputra Begins to Emerge at OpenDaylight Summit

By Blog

Our community is transitioning from the Arno release—where we constrained release activities to include only five projects—to our Brahmaputra release, where we may have more than thirty projects participating! This last week, the OPNFV community gathered at the OpenDaylight Summit for the first coordinated Developer Summit following our inaugural release, Arno. The focus of our community at the event was fittingly shared between collaboration with the OpenDaylight community and establishing our release plans for the next OPNFV release, Brahmaputra.

The OPNFV project in it’s essence collaborates and works with our upstream source communities to bring new and needed technologies to the industry, and we try to facilitate that by co-locating our events with other important upstream communities. While collaboration with the OpenDaylight community was top-of-mind, we were fortunate to schedule a combined session with OPNFV, OpenDaylight and representatives from the ETSI NFV ISG. We are grateful to the OpenDaylight community, similarly to the OpenStack community, for being receptive to having the OPNFV community co-locate our activities at their respective summits.

OPNFV Hackfest

As expected, the focus of collaboration last week was highly network-centric and the OPNFV community benefited greatly from the wealth of networking expertise accessible at the OpenDaylight Summit. It was satisfying to participate in and observe discussions between the groups covering topics from scale and resilience, through protocol and overlay technologies, to policy and topology of virtual networks. As a user community of OpenDaylight, intent on exposing the values provided by the controller platform, OPNFV looks forward to seeing the seeds sown during these days together grow to fruition for future releases.

For OPNFV, the balance between working with open source communities and SDO’s is a challenge we face on a daily basis. Having the opportunity to participate in a joint session with a delegation from the ETSI NFV ISG while at the OpenDaylight Summit provided an in-person touch point across these domains. The team from ETSI NFV ISG raised a number of key use cases around deployment and lifecycle management of SDN controllers in the context of infrastructure and there was a good chance to converge on the testing activities across groups.

Brahmaputra planning, which is top of mind for our community today, provides the next major challenge for OPNFV and a clear priority for us during the summit. Debra Scott, our OPNFV release manager, led a number of sessions and one-on-one discussions with the community and project leaders to establish a foundation for our Brahmaputra release. While this may sound like business as usual, the challenge is immense.

A key takeaway from the event was that our community is really coming to terms with working through the process of taking concept to an upstream development community; then integrating, validating and leveraging the results to deliver cloud platform features. To have established such an understanding across the community in such a short time and with so few iterations speaks to the clarity of vision and intent across OPNFV.

I fully expect Brahmaputra to provide the first demonstration of our ability to work effectively with our upstream communities. And with the growing number of upstream-focused activities across OPNFV, there will be no shortage of features available in our “C” release.

About the author of this post

Chris Price
Chris leads open source industry collaboration for Ericsson in the areas of NFV, Cloud & SDN from the CTO’s office in Sweden and is an active member of the technical steering comitee’s of the OpenDaylight and OPNFV Projects.  Chris’ experiences include leading Ericssons’ IP&Broadband network architecture and standardization teams with a rich history in development of systems and technology in the areas of network management, policy control and user service management, user session control plane solutions, and DPI technologies.

Test-Bed Infrastructure Helps Community Development of OPNFV

By Blog

Last November, we started a project—codenamed ‘Pharos’—to develop a test-bed framework for creating a federated NFV test capability, hosted by OPNFV member companies from across the community. Nine months later, we’re very excited about the participation so far, with 10 existing test-bed labs spanning North America, Europe and Asia and even more in the works planned by vendors, system integrators and service providers. Companies like Orange, who just opened the first two OPNFV test-bed labs in Europe, have created community access for evaluating real-world OPNFV environments. Ericsson, Intel, Huawei, China Mobile and Dell are also hosting labs which are helping to develop a federated OPNFV test-bed capability that is geographically and technically diverse.


To make this happen, we needed to develop a baseline specification for an OPNFV “compliant” test environment along with tools, processes and documentation to support integration, testing and collaborative development projects with needed infrastructure and tooling.Pharos provides a consistent view of test-bed infrastructures and their capabilities to facilitate developer/project access. Other artifacts include libraries of workloads, test-tools, best practices, etc. And in addition to the community-hosted labs, the Linux Foundation hosts an OPNFV infrastructure that is used primarily for Continuous Integration (CI), Build and Release Deployment/testing. After using the community labs for early development, the Linux Foundation infrastructure was used for deploying and testing the Arno release.


Why invest in a community test-bed lab?

These test-bed labs have become a valuable resource to our developers, providing a platform for early testing of integrated OPNFV ingredients within realistic NFV environments via an open, consistent, repeatable test domain. And while some developing can be done in virtual or more simplistic environments, many features require substantial resources that may not be available to many developers. These community-accessible test-beds allow for a range of scenarios across varying community needs.

Another advantage the labs provide is simplification– setup and evaluation of OPNFV technologies and platforms is a complicated process with significant a integration effort and a multitude of configuration decisions. Reference implementations running on a test-bed with well-documented hardware and software configurations and integration/configuration learnings help lower barriers for adoption by the community.

Additionally, Pharos enables us the community to test across different hardware platforms, architectures and environments to ensure that OPNFV really is a multi-hardware platform.



Moving forward, these community labs will be connected to CI infrastructure for continuous deployment and testing in diverse, multi-vendor environments. We’re developing common test-bed tools and an infrastructure manager for configuring a variety of test-bed deployments tools and methods.

Now that Arno has been released, the community is looking towards the next iteration, Brahmaputra. To make these labs even more resourceful, we’ll be developing automated deployment and testing capabilities, making improvements to documentation for developers, making specifications for virtual environments so developers can start experimenting without access to expensive infrastructures and expanding the scale of test environments. We’re also in the process of developing centralized reporting and anlytics with dashboards and a reservation system.

To learn more about the Pharos test-bed community labs project—and to stay up to date on the latest developments—visit the OPNFV wiki page.

About the author of this post

Trevor Cooper
Trevor CooperTrevor Cooper has over 20 years of experience developing and deploying new technology solutions
in Networking, Telecoms and Healthcare markets. He has lived in US, Canada, UK and South Africa (where he grew up). He has worked extensively with multi-disciplinary and dispersed teams developing mission critical hardware and software. His current role at Intel is Solutions Architect working on Software Defined Networking initiatives. He also leads an Open Source group in OPNFV and represents Intel in the ETSI NFV Test and Open Source Working Group.

How OPNFV and ETSI NFV are Advancing NFV Adoption

By Blog

ETSI was the birthplace of the NFV concept in 2012, and OPNFV was launched just two years later with many of the same members to help bring NFV from specs to reality using open source methodologies. Marc Cohn, who is an active participant in many open communities including OPNFV, OpenDaylight and the Open Networking Foundation, recently published an article for SDxCentral about how OPNFV and ETSI continue to work in tandem to accelerate NFV adoption.

He says, “OPNFV and ETSI NFV ISG share many common members, providing continuity and collaboration across the NFV specification and implementation activities. Both the ETSI NFV ISG and OPNFV senior leadership teams are aligned on their common mission—to stimulate a vibrant open ecosystem to ultimately drive adoption for NFV. And what we’ve seen is that instead of specifications solely driving implementation, the OPNFV reference platform will help drive the requirements, which in term will drive evolution of the reference platform.”

He goes on to discuss where the two initiatives complement each other and what we can expect to see in the long-term. Read the full article here: ‘WE’ is ‘Us’: How OPNFV and ETSI NFV are collaborating to accelerate NFV adoption.