Second ONAP Release Enables Deployment-Ready Platform for Network Automation and Orchestration
Drudge Bot last edited by
ONAP, as part of LF Networking, now accounts for more than 65% of global subscriber participation through carriers creating a harmonized, de-facto open source platform
San Francisco, June 12, 2018– The Open Network Automation Platform (ONAP) Project, which delivers a unified platform for end-to-end, closed-loop network automation, today announced the availability of ONAP Beijing, its second software release. The Beijing release accelerates ease of ONAP deployment for modern network operators and comes as more leading global service providers commit to enhancing open source networking. LF Networking– a Linux Foundation entity that brings together six top networking projects (including ONAP) to increase harmonization across platforms, communities and ecosystems– now enables more than 65 percent of the world’s mobile subscribers, as well as major global enterprises and cloud providers serving hundreds of millions of customers.
“We are delighted to announce the availability of ONAP’s second release, Beijing, which advances the architecture, seven dimensions of deployability, and new automation functionality,” said Arpit Joshipura, General Manager of Networking, The Linux Foundation. “As a community, we celebrate the progress the Beijing release brings to the ecosystem and look forward to additional deployments of the platform.”
With ONAP’s Beijing release, the developer community has focused closely on new platform and process enhancements to ensure scalability, security, stability and performance in support of real-world deployments. The release also evolves the platform toward container-based implementations, and provides robust documentation and training for Virtual Network Functions (VNF) developers, service designers, and operations managers. Leading developers from solution providers, vendors and system integrators globally have laid the foundations of a robust commercial ecosystem.
“The Beijing release ushers in the next phase of ONAP,” said Mazin Gilbert, ONAP Technical Steering Committee (TSC) Chair, and Vice President, Advanced Technology, AT&T Labs. “The technical enhancements in this release focus on enhancing the stability and deployability of the platform. In addition, the community has focused on supporting users in their adoption journey with the delivery of several new Getting Started guides as well as online and in-person introductory training options. Together with the community, we are further establishing ONAP as the defacto standard for automation.”
Specific platform and feature enhancements of the Beijing release include:
- ONAP Operations Manager supports the migration to microservices-based deployments on Kubernetes
- ONAP has collaborated with MEF and TMForum on external APIs, ensuring those frameworks and APIs can communicate seamlessly with the ONAP platform.
- Starting with the Beijing release, the ONAP development process measures improvements in seven key operational parameters (Usability, Security, Manageability, Stability, Scalability, Performance and Resiliency) for each platform module.
- The Beijing release brings advanced platform stability and resiliency based on deployment of of the ONAP Operations Manager (OOM) and the Multi-Site State Coordination Service (MUSIC) projects.
- ONAP OOM enables ONAP modules to be run on Kubernetes, contributing to availability, resilience, scalability and more for ONAP deployments and sets the stage for full implementation of a microservices architecture, expected with the third release, Casablanca.
- MUSIC is an optional new solution for state management of ONAP components across geographically distributed sites, ensuring federated active-active operation without degrading performance, reliability and availability.
- As security is a key element of the CI framework, the Project has adopted CII (Core Infrastructure Initiative) badging as part of its release requirements. CII is a project managed by The Linux Foundation that collaboratively works to improve the security and resilience of critical open source projects.
Functional Enhancements – Blueprint Enrichment
The residential vCPE blueprint has been enriched with change management and policy-driven workload placement features that include hardware platform awareness (HPA).
- Network service scaling to meet traffic needs is a fundamental NFV value proposition. VNF Manual Scaleout is also supported on vLB via APPC and Policy with LCM based Manual Scale Out.
The open source community is rapidly organizing to ensure the technology, tools and services are in place to support rapid adoption.
VNF integration: With the Beijing release, the ONAP community worked closely with the OPNFV Verified Program (OVP), which simplifies adoption in commercial NFV products and establishes an industry threshold based on OPNFV capabilities and test cases, to coordinate integrations via the ONAP VNFSDK and ONAP VNF Validation Program (VVP) components.
Documentation and training:
- New startup and operations guides for users
- Design guides and API and SDK documentation for service designers and VNF developers
- Online training: Free introductory courses on Open Source Networking Technologies and ONAP as well as more in-depth, paid ONAP Fundamentals training
- Community-led best-practices webinars
- Organizations spanning every aspect of the ecosystem (vendors, telecommunication providers, cable and cloud operators, NFV vendors and solution providers) continue to leverage ONAP for commercial products and services. The Beijing release code is being integrated into new and existing proofs of concept and production deployment plans for large global carriers like AT&T, Bell Canada, China Mobile, China Telecom, Orange, Reliance Jio, Verizon, Vodafone, Turk Telecom, among others. And major leading vendors are building products and solutions on the ONAP platform.
For more details on the ONAP Beijing release, please visit https://onap.readthedocs.io/en/latest/release/index.html.
ONAP Developer Forum
The ONAP project is hosting a developer forum in preparation of the third release, Casablanca (coming this summer), which will take place in Beijing, China, June 19-22, 2018. Additional details and registration details can be found here.
About the Linux Foundation
The Linux Foundation is the organization of choice for the world’s top developers and companies to build ecosystems that accelerate open technology development and commercial adoption. Together with the worldwide open source community, it is solving the hardest technology problems by creating the largest shared technology investment in history. Founded in 2000, The Linux Foundation today provides tools, training and events to scale any open source project, which together deliver an economic impact not achievable by any one company. More information can be found at www.linuxfoundation.org.
The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our trademark usage page: https://www.linuxfoundation.org/trademark-usage. Linux is a registered trademark of Linus Torvalds.
The Linux Foundation
The post Second ONAP Release Enables Deployment-Ready Platform for Network Automation and Orchestration appeared first on The Linux Foundation.
Make ISO from DVD
In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM
Find out which device the DVD is:lsblk
Output:NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5
Therefore /dev/sr0 is the location , or disk to be made into an ISO
I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.dd if=/dev/sr0 of=win10.iso
Where if=Input file and of=output file
I chill out and do something else while the image is being copied/created, and the final output:8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s
Recreate postrgresql database template encode to ASCIIUPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';
Now we can drop it:DROP DATABASE template1;
Create database from template0, with a new default encoding:CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;