Open-source News

Red Hat Summit 2020 virtual experience  Network World

Linux Gaming, Qt Drama, New Hardware Kept Open-Source Enthusiasts Entertained This Month  Phoronix

During the course of April while much of the world was in lockdown, there were plenty of interesting happenings in the Linux/open-source and hardware space to keep enthusiasts interested while social distancing from the release of Linux 5.6 to the releases of Fedora 32 and Ubuntu 20.04 LTS, among other milestones...

System76 released today Pop!_OS 20.04 as their in-house Linux distribution built off Ubuntu 20.04 LTS but with many customizations on top...

Forget about Ubuntu Linux, because the superior Pop!_OS 20.04 LTS is here  BetaNews

A new Linux Foundation whitepaper provides guidance in negotiating software contracts that have open source components. Introduction

The first and most important step in negotiating any agreement is always to get the facts.  For example, when negotiating a software development agreement, the developers for both parties probably assume that the software will include many pre-existing components written by third parties.  If the procurement and legal personnel negotiating the agreement assume that there should be no code that is not written by the vendor, the process will be inefficient and waste a lot of everyone’s valuable time.   

If developers are confronted with ridiculous assumptions about writing software from scratch, the credibility of the procurement process is undermined, and, in the future, they will find ways to avoid or delay involving procurement and their legal counsel.

The Linux Foundation recently published a whitepaper written by Karen Copenhaver and Steve Winslow that aims to help procurement professionals and their legal counsel avoid making erroneous factual assumptions that will undermine their credibility and delay negotiations through a better understanding of software development and the use of open source software assets. This is a summary of its findings.

Software is not static

The software that will be developed will evolve as it is developed. The reality is that if we required a detailed, final specification for development before the parties can begin work, the only assurance we would have is that the results would be too late to market to be valuable. 

Agreements today have to be focused on establishing the process for working together to develop something which neither party can fully define or envision. Requiring that a fixed list of the specific software components that will be used in development be included in the agreement may not make sense to the people who will perform the work. 

They may know that the list will change often, and they do not want to amend the agreement every time they consider, include, or replace a component. A process acceptable to both parties that allows for the rapid evolution of the work to be performed will be welcomed.

Software will change over its normal life

Software is never “finished” until it is uninstalled. Constant updating is required to accommodate changes in the operating environment, including the hardware, opportunities for enhancement, and to apply patches that become available to eliminate potential security vulnerabilities. If the software is not updated, then necessary software maintenance is not occurring. Agreements should not be written based on the assumption that all development will conclude at any point before the end of the life of the software.

Software providers will not author or “own” the copyright in all of the software that is being delivered

The software will include components owned and developed by third parties and will rely on dependencies that may not be part of the distributed package of software. 

Because the software does not operate in a vacuum, components and interfaces written by third parties are necessary for the software to function. For example, applications installed on laptops use interfaces in the operating system. Without using the libraries and/or interfaces that provide access to this infrastructure, the software cannot be developed, tested, or deployed.

In addition to what is developed and delivered as part of the agreement, all software operates within one or more ecosystems of third-party dependencies that are necessary for its optimal use and performance.

The use of these dependencies will directly influence the price at which the software provider offers their software for sale. 

Tools are important to the delivery of software and solutions

Just as lawyers rely on a word processing program to write an agreement, software developers use software tools to make development more efficient. These tools are often the most complex software involved in the development project, and the amount of code in this development environment will almost always far exceed the amount of code in the developed deliverable. And these tools will change and evolve just as the software that is being developed will change and evolve. Knowing the specific facts related to the collection of tools used to develop this software is essential to avoid unworkable approaches.

Sometimes the development environment will be a third-party product that can be acquired directly from the third party. If a version of the third-party product that is being used is specified, the customer will be able to replicate and maintain that development environment should it ever be needed. 

Other times, the reason to hire a specific company to do the work is that they have a well-established, unique development environment, and, just as important, a set of highly skilled developers trained to use it.  

However, to “deliver” the entire development environment is often impractical for a number of reasons. The company asking for it to be delivered may not have sufficient equipment or technical employees even to install the software, much less maintain it. 

To deliver any code at a single point in time, without a plan for someone to maintain the code going forward, is not useful.  

The continuous delivery of code in a development environment is an enormous amount of work that must be performed by highly skilled individuals – often the same individuals who are required to complete the work you have engaged the vendor to perform.  

Requiring delivery of the development environment as a contract solution where the technical employees of both companies know that the delivered code will never be used is considered by developers as a frustrating waste of valuable resources that will delay the work everyone wants the vendor to perform.

Many of the most valuable third-party components and tools are made available under open source licenses

Most estimates suggest 70-90% of all the code in a system will be built from open source software. And even proprietary, purchased solutions that any IT organization currently uses are very likely built in large part with open source components.

Unless your technical people agree that there should be no open source code of any kind used in its development, do not ask for a representation or warranty that there will be no open source from a contractor or supplier. 

If software made available under an open source license will be used, the relevant questions you should ask should be related to the selection of the code, maintenance of the code, and compliance with the applicable license terms in your specific use case. And all of these are questions that should be asked about both open source and non-open source software. 

If your competitors are using these valuable open source assets and you do not, it will be hard to be competitive on cost, quality, maintenance, and security. One of the most important reasons to use open source is to benefit from the advantages of shared support across an ecosystem. 

Software licenses can be categorized in unlimited ways

There are many software licenses. Some are licenses that the Open Source Initiative (https://opensource.org/) has approved as consistent with the Open Source Definition (https://opensource.org/osd-annotated). There are also licenses that are similar to those licenses but that have never been approved, and some of those variations are not considered by people familiar with this terminology to be “open” or may even be of a proprietary or commercial nature. 

The SPDX License List (https://spdx.org/licenses/) has been curated by lawyers working in the open source ecosystem and identifies many of the licenses that frequently come up in reviews and negotiations.

The question is: does any practical difference arise in any specific contractual context based on exactly where a license falls on that spectrum? In our estimation, spending time and energy trying to define a separate category of Open Source Software is not helpful in reaching an agreement. Aside from how the open source ecosystem may categorize licenses, all software licensed from third parties should be evaluated under the same criteria for your project.

Some of the most essential and widely used software are provided under the GPL and other copyleft licenses

GPL-licensed software such as the GCC Compiler and the Linux operating system is used by the vast majority of companies and industries around the world. The distribution of this software usually triggers copyleft obligations to provide source code. Many businesses are built on top of the GPL-licensed Linux operating system and other copyleft software that is used in the business to provide services but are not distributed. 

A common perception of the GPL and its variants as being unworkable open source licenses is inaccurate. Keep in mind that the GPL, like all free and open source licenses, does not restrict your usage. As a recipient of GPL software, you have far more expansive license rights to use the software than you have under a proprietary software license agreement. Compliance with the GPL upon a redistribution of the code may be a factor to consider but should be compared with the fact that you would likely not have the right to redistribute proprietary software at all. 

A company can have a “no GPL policy,” yet it cannot operate in most industries without dependence upon the Linux operating system, which is GPL-licensed software.  

Unless your technical people agree that there should be no GPL or copyleft licensed code of any kind used in its development or provided in the work product, do not ask for a representation or warranty that there will be no copyleft software. Once again, the relevant questions related to the selection of the code, maintenance of the code, and compliance with the applicable license terms in the relevant use case.  

Conclusion

Lawyers and procurement professionals should not even attempt to dictate how software development will be accomplished. If negotiations hit a rough patch, take the time to confirm that the real issue is risk allocation. Make sure that the dispute is not due to insistence on facts that your technical team does not believe to be true. This is particularly difficult when longstanding corporate policies are out of step with current realities.   

To download “Fact gathering: The first and most important task in software negotiations”, click on the button below. Download whitepaper

The post A guide to open source software for procurement professionals appeared first on The Linux Foundation.

With about a month and a half since GNOME 3.36 debuted, GNOME 3.37.1 is out today as the first development release towards GNOME 3.38 due out this September...

How to check for weak passwords on your Linux systems with John the Ripper  TechRepublic

New Red Hat CEO Thrives on Channel Partner Relationships  Channel Futures

3.5-inch Whiskey Lake SBC ships with Ubuntu image  LinuxGizmos.com

Chef Infra 16 adds YAML recipe support  InfoWorld

Coronavirus (COVID-19) Business Impact – Linux-based Set Top Box Market Size, Growth Trends, Top Players, Application Potential and Forecast to 2027 – 3w Market News Reports  3rd Watch News

The GNU Compiler Collection 10 stable release (GCC 10.1) is on track for releasing in early May...

I fudged VirtualBox by mistake on Kubuntu 18.04 - Linux & Unix  BleepingComputer

Watch this 90-year-old tech turned Linux terminal create ASCII art  PC Gamer

Watch this 90-year-old tech turned Linux terminal create ASCII art  PC Gamer UK

 

• China Mobile brings XGVela to the Linux Foundation, focusing on open telco PaaS platform for 5G network functions and related applications

• Accelerating LFN collaboration across open source projects within CNCF, LF Edge, LF AI, Hyperledger, ORAN-SC to enhance 5G, Cloud Native, and Edge as ecosystem moves to deployment

• Growing developer participation in critical projects through virtual technical conferences, new Training courses, and expanded Mentorship programs 

 

SAN FRANCISCO– April 30, 2020 – LF Networking (LFN), which facilitates collaboration and operational excellence across open source networking projects, today announced continued successes with cross-industry, global collaboration. Progress includes the Linux Foundation induction of new project, XGVela, an open source telco Platform as a Service (PaaS) for 5G network functions and related applications; new LFN silver member everis; expanded mentorship and training opportunities; and a new verified product by the OPNFV Verification Program (OVP). Together, these efforts bring additional support for future automation and deployment of 5G, edge, and cloud native networking technologies. 

“In a new normal, networking serves as the critical foundation for everything we do. That said, we are pleased to see strong growth in developer participation of our projects, including training with close to 30,000 enrollees to date, and a recent virtual developer event with over two-times the registration of past physical events,” said Arpit Joshipura, general manager, Networking, Edge and IOT, the Linux Foundation. “We’re expanding our global footprint that enables open source networking and related technologies to grow and thrive. Other examples include the addition of XGVela as a Linux Foundation project aimed to accelerate telco cloud adoption, new silver member everis, and new training and mentorship opportunities.” 

Donated by LFN member China Mobile, XGVela provides a PaaS platform to accelerate the design, development and innovation of telco-related services. The project refines common capabilities of upper layer services as PaaS functions on platform layer. The platform brings General PaaS functions from existing open source PaaS component projects (e.g.  Grafana, Envoy, Zookeeper, etc.) to be enhanced with telco requirements, and Telco PaaS which has strong telecommunication characteristics and is under exploration. 

Currently, XGVela has gathered partners including China Mobile, China Unicom, China Telecom, ZTE, Ericsson, Nokia, H3C, CICT and Beijing University of Post and Telecommunications, and received high attention from Intel, and Red Hat. XGVela hopes to expand the telco cloud native ecosystem and enable more cloud deployments among telcos.

“Exploring the future direction of network transformation has always been one of China Mobile’s core missions,” said Xiaodong Duan, director of network and IT department, China Mobile Research Institute. “ With the deployment of 5G, applications of containers and microservice technologies, we believe operator networks will eventually evolve into a cloud native network. Hence China Mobile is pleased to launch a new project within the  Linux Foundation – XGVela, a 5G cloud native PaaS. We hope XGVela will gather the most intelligent technicians from operators, vendors and IT companies to help accelerate operators’ cloud native transformation and promote vertical industrial prosperity.”

Welcome everis

LFN welcomes its newest Silver member, everis, an NTT DATA company dedicated to  consulting and outsourcing in all sectors. Everis joins recently-announced Silver members A10 Networks, AMD, Codilime, Mirantis, Robin.io, Solutions by STC, ULAK, and Xilinx. These organizations work alongside the plethora of existing member organizations to drive development, testing and implementation of LFN’s existing networking projects, including FD.io, ONAP, OPNFV, OpenDaylight, OpenSwitch, PNDA, SNAS, and Tungsten Fabric.

“We are really excited to join LFN. everis, as a networking system integrator, finds in LFN a key lever to unleash industry Data Openness, Network Process Automation and 5G future networks,” said Hugo Alberto Nava, Telecom Director at everis. “This area is so important for us that we have designed a new area, #everisOpenNetworks, in charge of uniquely integrated networks and systems, helping CSPs achieve more efficient and low-cost operations. Our vision in relation to the future of OSS is directly connected with a disaggregated, open, cloud-based and data-driven architecture with the main purpose of enabling value through close loop automation inside the most important network processes. We believe the Linux Foundation Networking is essential to go deep into this approach, helping us to make a difference by sharing knowledge and taking our proposal into a superior level.” 

About everis

everis is a consulting and outsourcing company that covers all sectors of the economy, with a turnover of nearly 1.437 million euros in the last fiscal year, made up of 27,000 professionals distributed throughout Europe, the USA and Latin America. everis is firmly committed to talent and innovation and its main objective is to attract the best professionals and help them develop their careers in the company https://www.everis.com/

Mentorship & Training

LFN is kicking off an expanded mentorship program with 9 active projects; opportunities for students (mentees) include building a portal for ONAP Automation Testing; Hardware Delivery Verification Tool; ONAP Security Requirements; Conformance Testing for ETSI NFV APIs; and more. More details on the LFN Mentorship program are available here. 

Additionally, the Linux Foundation offers a robust package of networking training courses. Given the current global situation, the Linux Foundation is making it easier to use this time to brush up on open source skills, or gain new ones. All certification exams, and nearly all  training courses, are available remotely, making them a good option for those home during this time. 

Included is the entire catalog of open networking training courses, covering everything from DevOps for Network Engineers to courses on ONAP, OPNFV and more. An ONAP certification exam will be launching in the coming months, so this is a great chance to get prepared. The LF also offers dozens of completely free training courses. Edge training courses will be available in May. 

OVP Badging

The OPFV Verification Program (OVP), which has verified 12 products with the NFVI “Infrastructure” badge, is pleased to announce its first product to be verified with the “VNF” Badge – Çınar, a 5G Core VNF from LFN member Ulak Communications. The team from Ulak participated in the LFN Developer & Testing Forum in Prague and the VNF Hacking Track designed to help VNF vendors jumpstart their VNF testing efforts. 

New LFN Assets

A new whitepaper, prepared by a Working Group of the LFN Technical Advisory Council (TAC), has been published that illustrates the state-of-the-art in networking technology and provides an overview for how the LF Networking (LFN) projects may be used as building blocks for modern networks. An introductory guide for the edge is also now available that gives an overview of the edge compute market opportunity, where open source fits in, the role of Linux Foundation projects in your edge strategy, and how to get involved. 

Looking Ahead

2020 will continue to be a productive year for LFN. The community will host a virtual developer event June 1-4 (details to come) for developers to collaborate and engage across LFN communities, including ONAP, OPNFV, CNTT, and more. 

The Open Networking & Edge Summit (ONES),  the industry’s premier open networking event now expanded to comprehensively cover Edge Computing, Edge Cloud & IoT will take place in Los Angeles September 28-29. ONES enables collaborative development and innovation across enterprises, service providers/telcos and cloud providers to shape the future of networking and edge computing. Register today for Early Bird pricing: https://events.linuxfoundation.org/open-networking-edge-summit-north-america/register/

ONAP will soon issue its sixth platform release, ONAP Frankfurt, which enhances support for cloud native with deeper Kubernetes integration and for 5G through network slicing and an initial O-RAN integration. Frankfurt will also include security improvements and begin the shift to Python 3 and Java 11.  

More LFN content is on the way with an LFN End User Advisory Group (EUAG) whitepaper on ONAP consumption, a CNTT whitepaper, and introductory guides for cloud native and 5G.

Support for XGVela

“Cloud Native has reached broad consensus as the target architecture of telecom networks,” said Xiongyan Tang, chief scientist of China Unicom Network Technology Research Institute and the Chief Architect of China Unicom Intelligent Network Center, China Unicom. “China Unicom believes that the telecom cloud native architecture is a key path towards agile operations, and would provide a great foundation for the digital transformation of operators. XGVela is committed to work together towards a telecom PaaS functions platform for 5G and Cloud-oriented services，which will play an important role in the cloud native evolution of  thetelecom industry. China Unicom is pleased to join XGVela project, and will work together with community partners to nurture a vibrant technical community.”

“In the 5G era, services innovation needs a fast-paced, continuous change of technology to promote network transformation,” said Yongbing Fan, vice director of Network Evolution Department, China Telecom Research Institute. “The integration of CT and IT technology, network and cloud-native are currently recognized to be telco-industry trends. China Telecom attaches great importance to the combination of network and services, and is committed to accelerating its cloudification. The cloud-native telecom PaaS platform, XGVela, perfectly meets the needs of the 5G era. China Telecom is pleased to join this project and work with community partners to cultivate a dynamic technical community.”

“Cloud native paradigm and design principles are key to Ericsson, being the first 5G provider to include cloud native container-based technologies as part of its 5G Core offering,” said Anders Rpsengren, head of Architecture & Technology, Business Area Digital Services, Ericsson. “Ericsson is one of the leading promoters and supporters of the open source ecosystem, accelerating the adoption and industry alignment in a number of key technology areas. As a leading vendor of cloud native telco applications we see significant value in both standardization and open source projects in the cloud native area including CNCF, CNTT and now XGVela, that help push the boundaries of tomorrow’s networks in terms of agility, efficiency and reliability.”

“Network transition has become a consensus among global operators. NFV, SDN and 5G have accelerated the progress of telecommunication network and cloud computing combination,” said Chen Fang, technical director, H3C Carrier Departemnet. “XGVela will further promote the introduction of cloud-native concepts into telecommunications networks. By constructing a carrier-grade PaaS platform and restructuring the organization of 5G network elements, it will promote the full opening of 5G network capabilities and support the network transition and success of 5G networks. H3C is committed to promoting the digital transition of society and is willing to work with China Mobile to promote the maturity and industrialization of XGVela.”

“The telecommunications industry is in the middle of two key transitions that will shape the world to come – the deployment of 5G and the transition to cloud native,” said Jonne Soininen, head of Open Source Initiatives, Nokia  “The industry needs to work closely together in order to succeed in this transition. Nokia is strongly committed to contribute to achieve this goal. We welcome the leadership from CMCC in proposing the XGVela project. Nokia is looking forward to working closely with CMCC and the rest of the industry to make sure the transition to cloud native in telecommunications is successful.”

“ZTE is honored to participate in the XGVela project as a major telecommunications equipment manufacturer. We believe that XGVela attempts to use containerization technology and reasonably divide the telecommunications capabilities and general capabilities in PaaS, which will help the flexible deployment of network elements and the rapid scheduling of resources in 5G networks,” said Wang Weibin, CTO of ZTE Telecom Cloud & CN Product Operation. “ZTE hopes to contribute our experience accumulated in the long-term research and development of telecommunications core networks in this project. We sincerely hope that industry peers will work closely together in this new open source project to enrich the ecosystem, create extraordinary value, and achieve complete success!”

About the Linux Foundation

The Linux Foundation is the organization of choice for the world’s top developers and companies 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 post LF Networking Accelerates 5G, Cloud Native, and Edge Readiness with Expanded Projects and Growing Community Ecosystem appeared first on The Linux Foundation.

 

• Initiatives across the Common NFVI Telco Taskforce (CNTT), LF Networking’s Compliance and Verification program (OVP), ONAP Cloud Native, and OPNFV holistically address cloud native architecture, deployment challenges, and Cloud Native Network Function (CNF) requirements 

• Open source groups preemptively address interoperability and performance to accelerate networking industry cloud native transformation

 

 

SAN FRANCISCO– April 30, 2020 – LF Networking (LFN), which facilitates collaboration and operational excellence across open source networking projects, today announced a turning point for the industry, with integrated initiatives focused on cloud native interoperability and deployment for telcos. Consolidated efforts among the Common NFVI Telco Taskforce (CNTT), LF Networking’s Compliance and Verification Committee (or OPNFV Verification Program, “OVP”), and the OPNFV project through CNTT’s cloud native “R2” workstreams, OVP’s cloud native “OVP 2.0,” and OPNFV’s renewed commitment to testing and integration alignment with end users indicate a deep commitment to  address challenges faced in cloud native adoption. 

“NFV continues to evolve as telcos increasingly adopt cloud native technologies,” said Heather Kirksey, vice president, Community & Ecosystem Development, the Linux Foundation. “Change, however, brings challenges, especially to areas like compliance, testing, automation, and integration. With input from telcos directly, collaborative efforts across CNTT, OVP, and OPNFV enable our ecosystem to benefit from cloud native adoption.”  

Celebrating its first year, CNTT – developed to create a  reference model, implementations and conformance requirements to reduce cost, time-to-market and complexity of telco operations in development and adoption of VNFs and CNFs – has augmented its VM-based specifications with several cloud native focused workstreams focused on container technologies. These workstreams will enable service providers to specify infrastructure and CNF requirements to empower operators to drive forward with their cloud native implementations with an early emphasis on streamlining operations, ease of CNF deployment, and implementation consistency. These requirements will enable strong integration and conformance to streamline operational efficiency and new service agility. The group is also on track for its third release, Baldy, in early June. 

“China Mobile started the world’s largest NFV cloud deployment in 2019. Taking into consideration cross-vendor and scalability challenges, China Mobile put in a huge effort on interoperability and integration automation, and established a mature integration process and automation toolsets, which help improve the overall efficiency and quality of NFV cloud,” said Xiaodong Duan, director of Network and IT department of China Mobile Research Institute. “We believe these practices and experiences could also provide help and reference to other operators. Open source communities provide de-facto standards, open interfaces and automation tools, which are crucial for NFV adoption. We are expecting CNTT and OPNFV 2.0 to take the leading role for promoting NFV to the next phase of integrated innovation.”

In tandem with CNTT, OPNFV – which reduces time to integrate and deploy NFV infrastructure and onboard VNF/CNFs for those who supply components and those who operationalize these platforms – has adapted its mission based on the evolving needs of telcos. The next stage of OPNFV takes the initial foundations laid by the project to the next level by providing support for CNTT architectures and introducing reference implementation and test automation ahead of 5G deployments while continuing and refining the testing and integration work OPNFV is known for.  Providing the code implementation of CNTT platform references and testing requirements, OPNFV further accelerates the telecom ecosystem’s commitment to improving adoption and easing operational headaches.

Pivot points include improved developer resources, such as more refined testing and deployment tools for conformance and performance of NFV infrastructure, aligned with industry reference architectures.

“Having successfully completed the roll-out of our network virtual infrastructure, Vodafone is accelerating it’s journey to Cloud Native,” said Rabi Abdel, principal cloud architect and senior manager at Vodafone Group. “Industry initiatives such as CNTT, empowered by a compliance program, can help us simplify the management of our sophisticated, feature-rich, complex Cloud Networks, and enable an open, inter-operable & fully integrated architecture eco-system.This is a key factor to enable the delivery of high quality new Services to our Customers, faster than ever, in the 5G era.” 

 Also taking on a concerted effort to address cloud native for telcos, the OPNFV Verification Program (OVP) –  which combines open source-based automated compliance and verification testing for cloud stack specifications established by ONAP, multiple SDOs such as ETSI and GSMA, and the LF Networking End User Advisory Group (EUAG) – has launched a Cloud Native OVP sub-committee focused on conformance, validation, and performance testing for cloud native infrastructure and CNFs. Working closely with the CNTT requirements workstreams, the automated integration and testing work with OPNFV, and ONAP cloud native orchestration initiatives, the cloud native OVP initiative further enhances operator and vendor abilities to more easily transition to cloud native in a cost effective and interoperable fashion.These requirements feed tool-sets and testing scripts developed within OPNFV, ONAP, and the CNCF Telecom User Group (TUG) communities.

To date, OVP’s VM-based program has verified 12 products with the NFVI “Infrastructure” badge and one product with the VNF badge. OVP 2.0 will enhance this effort with badges for cloud native telecom platforms and CNFs.

Looking Ahead

Taken as a whole, these initiatives spanning architecture specifications, implementation integration and deployment, automated testing, and compliance badging provide a solid foundation to advance the telecom industry’s cloud native journey. Moving forward, the groups will continue alignment and collective integration with other related groups including the CNCF Telecom User Group (TUG), ETSI, the GSMA, and other open source and SDO groups. As 5G becomes more pervasive, telcos need to find new paths to adopt technologies in ways that did not exist five plus years ago when NFV came onto the scene. 

The community expects to issue two CNTT releases this year, with an updated Reference Architecture, Reference Model and Reference Conformance to start. Reference Implementations and more OVP Badging updates are also in the works. 

Additional Resources

• OVP Wiki
• OVP Bootstrap page 
• OPNV Mission page
• CNTT 

About the Linux Foundation

The Linux Foundation is the organization of choice for the world’s top developers and companies 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 post Telcos Increase Focus on Cloud Native as LF Networking and Ecosystem Groups Solve Interoperability Challenges appeared first on The Linux Foundation.

Telcos Increase Focus on Cloud Native as LF Networking and Ecosystem Groups Solve Interoperability Challenges  Yahoo Finance

LF Networking Accelerates 5G, Cloud Native, and Edge Readiness with Expanded Projects and Growing Community Ecosystem  Baker City Herald