Skip to main content

Announcing Amsterdam, ONAP’s First Code Release

By November 20, 2017November 22nd, 2017Blog

We are pleased to announce the launch of Amsterdam, ONAP’s first united platform. We are incredibly proud of the community for all of the hard work that has gone into this release, which launched just eight months ago. A Herculean effort from a diverse and growing community, Amsterdam not only merges two separate, existing projects (OpenECOMP and Open-O), but re-architects and optimizes the code base into a single, flexible and modular platform. Amsterdam delivers a unified architecture for end-to-end, closed-loop network automation — which is becoming a mandatory requirement before 5G and IOT deployments — and by doing so, celebrates a new milestone for open source networking.

None of this could have been possible without vast support and contributions of time, resources, and passion from across the growing, global ONAP community. Since coming together, ONAP is now comprised of:

  • 58 members (Turk Telekom just joined as the newest Platinum), including major global carriers, collectively representing more than 55 % of the world’s mobile subscribers
  • All top 10 networking vendors, plus leading global services firms
  • 538 contributors from 46 different organizations (including 7 carriers)

With Amsterdam, ONAP is already delivering on its promise to accelerate the development of a vibrant ecosystem around a globally shared architecture and implementation for network automation. Additionally, ONAP is the first open source project to unite the majority of operators (end users) with the majority of vendors (integrators) in building a real service automation and orchestration platform.

Key Features of Amsterdam

So let’s get to the heart of the release–the key features.  At a high level, Amsterdam is the first vendor-agnostic, policy driven network orchestration and automation platform with closed loop automation.  

For ONAP’s first platform release, it was crucial to lay out a framework that would benefit not only the technology but also the ecosystem. As a result, the Technical Steering Committee (TSC) developed a high-level framework of initial requirements for the release, which have come to fruition with Amsterdam. The requirements include things like modularity; enhancement of model-driven design; the addition of new features/functionalities; open code; upstream collaboration; harmonization with standards bodies; and CI/CD, to name a few.

Architectural principles and and how they funnel into the stack are also critical element of the release. These include:

  • Policy- and Model-Driven: The ability to automate according to intent, without hard-coding
  • Cloud-Native: Built for the cloud and has ability to manage the cloud through native VNF
  • DevOps CI/CD: Built using CI/CD Manage VNFs using CI/CD Break/Fix → Plan/Build

Amsterdam Architecture Diagram:

Another key capability of Amsterdam is VNF automation. In current deployments, every VNF works in a different way and can start/stop at various points. Configuring a variety of VNFs is therefore a very time-consuming, manual process. Amsterdam has standardized VNF automation by creating a streamlined deployment process that  happens through the abstraction layer (through the virtual controller) and has a SDK plug-in. More details on automation and CLAMP can be found on the ONAP Developer Wiki, here.

Additionally, ONAP’s focus on automation helps move the industry forward in accelerating the development and deployment of next-gen use cases. Automation is mandatory for 5G deployments due to the scale, access, bandwidth, and latency it demands. Amsterdam provides the platform to deploy new services to enable 5G in an automated manner.


Real-World Support for Amsterdam

Despite ONAP’s infancy, we are proud to see early deployments, testing, and POCs using various modules of pre-release code from member carriers and vendors including Amdocs, AT&T, Bell Canada, China Mobile, China Telecom, Fujitsu, Huawei, Orange, Vodafone and many others. Members have also been testing blueprints of early use cases like VoLTE and residential vCPE. Stay tuned for more information on user stories in the near future!  (To see what members are saying in support of the Amsterdam release, please visit our Member Quotes page here. Additional videos with commentary from members can be found here.)

Interested in learning more about ONAP or getting involved with the community? Join us for the ONAP Developer Design Forum, Dec. 11-13 in Santa Clara, California! More details on the event -including how to register – are available here.  

Please join me in congratulating the ONAP community on its first release!