All Posts By

opnfv

How Orange is Leveraging OPNFV for Full-Scale NFV Rollout

By | Blog

This post intially published to The New Stack

By: Jehanne Savi, executive, All IT Strategic Programs, Orange

Mandatory for the next generation of networks (such as 5G) and services, NFV transformation brings a variety of challenges.  Learn how Orange leverages open source software via OPNFV to solve several important issues along the way. 

Over the past few years, the entire networking industry has begun to transform as network demands rapidly increase. This is true for both the technology itself and the way in which carriers — like my employer Orange, as well as vendors and other service providers — adapt and evolve their approach to meeting these demands. As a result, we’re becoming more and more agile and adept in how we virtualize our evolving network and a shifting ecosystem.” keep up with growing demands and the need to virtualize.

At Orange, we are laser-focused on investments into future technologies and plan to spend over $16 billion between 2015 and 2018 towards new networks (including 4G, 4G+, fixed fiber). A key component of these investments — along with access network investments — are advancements in software-defined networking (SDN) and network functions virtualization (NFV) technologies as a way to create new revenue streams, improve agility, and reduce costs via a program we call On-Demand Networks. With 5G and network slicing around the corner, both SDN and NFV are major areas of investment. In fact, 5G will be natively virtualized through our investments in these areas. As such, our On-Demand Network program is a top priority.

NFV, in its ability to impart massive transformation, is similar to the industrial revolution in that it will profoundly impact our ‘factory’ (i.e. network) and business models along with changing consumer usage and creating a huge societal impact. That in mind, we’ve prioritized NFV use cases, including the Orange Easy GoNetwork, a Network as a Service (NaaS) offering for branch or remote-site connectivity provided by Orange Business Services in 75 countries. Easy Go Network is a network solution to connect easily remote sites with a zero-touch provisioning: the order is done online and a plug and play router is automatically sent on site. This will save time for IT managers with a lot of remote sites to manage like retail stores, agencies etc.

To experience the full benefits of NFV, the full-scale rollout is necessary. This includes model-driven architectures, policy-driven automation, DevOps, closed-loop feedback with big data analytics (ultimately utilizing AI and machine learning) and of course hardware disaggregation and virtualization. It is not enough to simply virtualize hardware resources, as other capabilities are critical to automate operations such as self-healing, scale-out, scale-in and lifecycle management. However, this work is not easy and requires a great deal of testing and analysis — not to mention skilled talent and a whole new level of KPIs.

To help us dive deeper into open source NFV, Orange became involved with the OPNFV project, hosted by The Linux Foundation, since its inception in 2014. Open source, and OPNFV in particular offers a way to collaboratively work on a set of reference architecture scenarios and testing tools for NFV Infrastructure and virtual network functions (NFV)  compliance and verification as well as Management and Orchestration (MANO) components.

Some of the top benefits of OPNFV realized by Orange include access to open source, testing and interoperability of open source NFV architecture, VNF/ service onboarding and operational simplification, among others.  The unique role that OPNFV plays in fostering collaboration among key stakeholders across the entire ecosystem is a huge benefit for all involved, and the relationship between Orange and the OPNFV community is symbiotic — in fact, Orange is the top telecom operator contributor in OPNFV, and in the top 5 across all contributors.

At Orange, we’re using open source as a way to speed up the industrialization (hardening) of technology and ensure open APIs to minimize vendor lock-in. OPNFV helps to solve some of the challenges that come with NFV by building an integrated and tested reference platform and methodology for NFV. This reduces the time and effort required for network transformation, ranging from NFV Infrastructure testing, reference architecture scenarios, VNF on-boarding and verification, network service onboarding, simplified operations, and interoperability.

Click here to learn more details on Orange’s involvement with OPNFV.

Invest in the future of NFV and your career at OPNFV Euphrates Plugfest, Dec 4-8

By | Blog

By Sandra Rivera, Senior Vice President and General Manager, Network Platforms Group, Intel Corporation

From December 4th through the 8th, Intel will host the OPNFV Euphrates Plugfest at its Jones Farm campus in Hillsboro, Oregon. We are excited to support the OPNFV developer community in this fourth Plugfest, see familiar faces and welcome new members to the community. Intel has been involved with the OPNFV since its inception, and we continue to support its mission to create a standard NFV reference architecture, developed through system level integration, deployment and testing across open source ecosystems.

During the Euphrates Plugfest, community members including project technical leads (PTLs), and software developers will tackle the technical challenges of putting Euphrates release into operation. Attendees will improve the OPNFV platform through rigorous compatibility testing across multiple hardware and software configurations, including the latest platforms based on Intel architecture built on the Intel® Xeon® Scalable family of processors. Developers and vendors can try new scenarios, test cases, installers, tools and combinations of components.

Advantech, Nokia and Intel will provide onsite hardware resources, and CENGN, Lenovo and NEC will provide remote equipment, including OCP-based servers.

OPNFV Projects Meetings, Concurrent Hacking Session

New areas of focus for this Plugfest include collaboration with ETSI on its upcoming PlugTest test cases; ONAP integration, Kubernetes and container integration, and multi-access Edge. You can learn more about the previous Plugfest by reading the Danube Plugfest report.

We also have plans for key project teams to meet face-to-face. Doctor, Clover (Cloud Native NFV), Yardstick, Bottlenecks, Daisy, SNAPS-OO and other teams will meet for in-depth discussions, problem-solving, and planning for the upcoming Fraser release.

Due to overwhelming demand from previous Plugfests, we will also host several hacking sessions.

While the agenda is still under development, you can stay up to date on the latest schedule by visiting the Plugfest collaboration wiki page.

Intel Network Builders Ecosystem and Network Services Benchmarking project

The Intel Network Builders ecosystem is comprised of independent software vendors (ISVs), operating system vendors (OSVs), original equipment manufacturers (OEMs), telecom equipment manufacturers (TEMs), system integrators, communication service providers and other industry leaders focused on creating reference architectures and new use cases to accelerate the adoption and deployment of NFV and SDN.

The Intel Network Builders community has tested new concepts and contributed many innovations to open source communities, including OPNFV. One recent example is the Network Services Benchmarking (NSB) project launched over a year ago to develop a common testing framework for Network Function Virtualization Infrastructure (NFVI) and Virtualized Network Functions (VNFs) characterization. The goal of NSB is to accelerate the VNF onboarding process, a key requirement as we prepare the infrastructure for 5G.

This benchmarking program has led to significant contributions to the Yardstick, Barometer and SampleVNF sub-projects in support of the latest Euphrates release. You can read more about NSB in a recent blog by John Healy, vice president and general manager of Intel’s Datacenter Network Solutions Group.

OPNFV Members, Non-Members and Intel Network Builders: Register for Plugfest Today

I encourage you to join us in Hillsboro December 4-8. Test the Euphrates release, expand your industry network, and build on your NFV skills. Space is limited and spots are filling up – so register today. We look forward to seeing you there!

OPNFV Euphrates release addresses open-source NFV testing, interoperability

By | Community News

OPNFV has released OPNFV Euphrates, the project’s fifth platform release, focused on enabling service providers to accelerate network functions virtualization (NFV) transformation via open-source NFV.

A key element of the new release is that OPNFV Euphrates delivers Kubernetes integration as well as enhanced cross-community continuous integration (XCI) and new carrier-grade features such as increased virtualized networks visibility.

Read more at FierceTelecom

OPNFV Supports Containerized OpenStack and Kubernetes

By | Community News

The OPNFV Project today announced availability of its fifth platform release — Euphrates. It’s the first release that delivers container integration and Kubernetes support. It gives the ability to deploy containerized OpenStack via Kolla, which provides production-ready containers and deployment tools for operating OpenStack clouds.

Read more at SDxCentral.

OPNFV Book Preview #4: “DevOps for NFV: OPNFV Infrastructure and Continuous Integration

By | Blog

This post first appeared on Linux.com

By Amar Kapadia

In this article series, we have been discussing the Understanding OPNFV book. Previously, we talked about chapters 1-5 via an introduction to network functions virtualization (NFV), the role of OPNFV in network transformation, and how OPNFV integrates and enhances upstream projects. We continue our series with a look at chapters 6 and 7, that provide in-depth insight into the OPNFV DevOps toolchain, hardware labs, continuous integration (CI) pipeline and deployment tools (installers).

As mentioned previously, OPNFV integrates a number of upstream projects along with code contributions from the OPNFV community. To integrate and test these projects and contributions in an automated manner, the OPNFV project uses a variety of DevOps tools, hardware labs and a sophisticated CI pipeline. In fact, there is no better way for a telecom operator to absorb the principles of DevOps than by joining OPNFV.

Chapter 6 of the book starts by discussing each of the various software and cloud-based tools used by OPNFV for DevOps:

  • Collaboration: JIRA/Confluence
  • Source code management and code review: Git, Gerrit, and GitHub
  • CI/software automation: Jenkins
  • Artifact repository: Google cloud storage and Docker hub

Here is an excerpt from the book discussing Gerrit:

Code Reviews – Gerrit

Committing to master requires an approval process, and this process is managed through a tool called Gerrit. Gerrit is an open source web-based code review tool developed by Google. All changes pushed by contributors using a git push or git review command are reviewed in Gerrit by a set of reviewers, who view and inspect the patch. Reviewers also get to see the results of a continuous integration (CI) build and automated verify test run. Reviewers provide scores of +2, +1, -1 or -2. A +2 is a definite accept, while a -2 is a definite reject. A +1 or -1 may result in the change being accepted, rejected or sent back for changes.

OPNFV Gerrit

The chapter then describes the hardware labs used for automated integration and testing jobs. OPNFV has defined a standardized set of hardware, called a Pharos lab, consisting of 6 nodes and associated switches to automatically deploy OPNFV software by using the CI pipeline. The Pharos lab concept has been very successful with 16 labs distributed all around the world working seamlessly.

Chapter 6 continues by describing the CI pipeline in detail, where changes in upstream projects or community code contributions trigger integration jobs and specific time-durations (such as daily, weekly) trigger testing jobs. The CI pipeline diagram from the book is shown below:

Chapter 7 start by exploring the concept of OPNFV scenarios. Since OPNFV allows for multiple choices for different software layers, numerous permutations are possible. In addition to the different upstream projects described in the previous blog, OPNFV also allows for diversity in installers. The list of scenarios represents a subset of all possible permutations; effectively each scenario is a tested reference architecture. Examples of scenarios are:

  • OpenStack + ODL + L3 FD.io + High Availability (HA) using the Apex installer, or
  • OpenStack + OpenContrail + HA using the JOID installer

The OPNFV Danube release had 55 scenarios. However, if we ignore non-HA scenarios and the specific installer used, we are down to 21 distinct usable scenarios.

The chapter continues by providing an overview of the 4 major installers used in the Danube release: Apex, Compass, Fuel and JOID, and ends with a discussion of additional deployment related projects such as Daisy (a new installer), IPv6, Parser, ARMBand (to run OPNFV on ARM) and FastDataStacks (FD.io with OPNFV).

Want to learn more? You can check out the previous blog post that discussed the broader NFV transformation complexities  and how OPNFV solves an important piece of the puzzle, download the Understanding OPNFV ebook in PDF (in English or Chinese), or order a printed version on Amazon.

OPNFV Community Delivers Euphrates

By | Blog

By Tapio Tallgren

Three years after its founding, OPNFV has carved out a solid niche in the industry as an NFV center of gravity, as an integrator of upstream projects, and as the standard software testing platform. OPNFV Euphrates, the project’s fifth platform release, demonstrates the hard work and industry collaboration of the vibrant OPNFV community that continues to advance open source NFV through containers, improved testing, new features, and deep community collaboration.

The journey towards container integration is one of the biggest changes coming to NFV, and Euphrates begins to take these steps for OPNFV. The way I tell NFV history is that it started by moving network elements to virtual machines (VMs). Then integration of the cloud infrastructure removed the need to know exactly where the VM was running, and enabled more automation. However, the network elements (Virtualized Network Functions or VNFs) have evolved to remove the dependencies on emulating hardware. Thus, the software can now run in containers, which are much lighter than VMs. This in turn enables new innovations that will change the actual software architecture since the overhead of a container is so small, each process can be broken out into its own container. The innovation opportunity that containers create for open source networking is profound.

Improved testing seems to be a recurring highlight of each OPNFV release and the integration and testing effort has made significant progress in providing an extensive set of tools to test the NFV cloud, VNFs, and complete network services. New projects—including Sample VNF, which provides testing of the VIM/NFVI layer with applications approximating real-life application workloads; and NFVBench, which provides an end-to-end dataplane benchmarking framework—have been introduced. Additionally, existing test projects have continued to evolve with new features, capabilities, and test cases.

OPNFV also continues to develop carrier grade features for the industry as shown by the new Calipso project which provides operational visibility into complex virtual networks. Euphrates also includes performance improvements, better security, and additional choice in the stack.

One of the most important attributes of OPNFV is integration and collaboration. To demonstrate how OPNFV collaborates with upstream projects, OPNFV has introduced the cross-community continuous integration initiative, or “XCI.” This takes the latest and greatest software releases from different upstream communities, tests them in the OPNFV setup, and provides feedback to the community—quickly. Thus, an OpenStack developer can find out if a patch she is about to create will make something break when integrated with the latest OpenDaylight release, running on a platform with the VPP virtual switch from the FD.io project, for example. (Learn more about the XCI initiative in this recent blog post from key members of the OPNFV community.)

Looking ahead, planning is already underway for the next release—OPNFV Fraser (named for the Fraser river in British Columbia, Canada) and the projects that will be part of it are already signing up! And we’re holding our fourth OPNFV Plugfest in the early December to test and try to break the Euphrates release with different hardware setups, and to give the OPNFV project members a chance to plan the work ahead. I invite you to join us in Portland, Oregon.

As a further sign of OPNFV’s maturity, the OPNFV Compliance and Verification (CVP) is now under beta testing. CVP will help enhance interoperability, build the market for OPNFV-based infrastructure and applications designed to run on that infrastructure, while reducing adoption risks and testing costs for end users.

All of these improvements to the OPNFV platform have (and do require) required tremendous effort from across the community. Please see the section below to hear what Euphrates means to some of our core upstream communities. I would like to take this opportunity to thank everyone involved in OPNFV for contributing to the Euphrates release, and beyond!

Comments From Upstream Communities

FD.io
“In addition to participation in XCI efforts, OPNFV Euphrates leverages the latest enhancements from FD.io 17.04, and performs continuous integration against the upcoming 17.10 master branch. VPP supports IP multicasting, Enhanced NAT, security groups, IOAM, LISP, and scalable packet filtering, in addition to numerous other features,” said Ed Warnicke, FD.io Technical Steering Committee chair and distinguished consulting engineer in the Chief Technology and Architecture Office (CTAO) at Cisco Systems. “OPNFV Euphrates also takes advantage of FD.io’s strong performance gains in Layer 3 performance.”

Kubernetes
“It’s exciting to see Kubernetes and cloud native technology being adopted into the NFV space,” said Chris Aniszczyk, chief operating officer, Cloud Native Computing Foundation. “For example, OPNFV Euphrates introduces the notion of containerized VNFs which will enhance performance, while also supporting OPNFV’s evolving DevOps processes.”

OpenBaton
“With Euphrates, OPNFV makes an additional important step towards a more comprehensive reference platform for accelerating the adoption of NFV and SDN technologies,” said Giuseppe Carella, project manager, Open Baton and OPNFV Orchestra project project technical lead. “We are proud of having introduced the first OPNFV scenario integrating a full MANO stack provided by the Open Baton project, leveraging the JOID installer. Moreover, functest has been extended for validating such integration using vIMS VNF packages available on the Open Baton marketplace.”

OpenStack
“The strong collaboration between the OpenStack and OPNFV communities delivers greater agility, performance and value for carriers and service providers building next-generation open networking stacks,” said Jonathan Bryce, executive director of the OpenStack Foundation. “OPNFV’s Euphrates release supports containerized OpenStack via the Kolla project, and it gives users the improved performance and functionality found in OpenStack’s 15th release, Ocata. Euphrates is proof that when open source communities work together, users win.”

OpenDaylight
“OpenDaylight continues to integrate closely with OPNFV,” said Phil Robb, vice president of Operations, Networking & Orchestration, The Linux Foundation, and executive director, OpenDaylight. “As an upstream contributor to OPNFV Euphrates, ODL Carbon and Nitrogen bring enhanced stability, performance, security and network programmability features to the open source networking stack.”

OPNFV ‘Euphrates’ Initiates the Cloud Native NFV Journey

By | Announcements

Fifth iteration of open source NFV project platform advances functionality, interoperability, and performance to accelerate NFV transformation

PRAGUE, Czech Republic — Open Source Summit Europe — 24 October, 2017 — The OPNFV Project, an open source project that facilitates the development and evolution of Network Functions Virtualization (NFV) components across various open source ecosystems through integration, deployment, and testing, today announced the availability of OPNFV Euphrates, the project’s fifth platform release. OPNFV Euphrates represents a step forward in functionality, interoperability and performance to help operators advance network transformation via open source NFV.

OPNFV Euphrates delivers Kubernetes integration for the first time as well as enhanced cross-community continuous integration (XCI) and new carrier-grade features such as increased visibility into complex virtualized networks. This is enabled via Euphrates’ platform of pre-tested, tuned, interoperable, open source NFV components that facilitate multiple use cases such as VNF onboarding, network service testing, data plane acceleration, NFVI/VIM validation, MANO qualification, test automation and creation of DevOps methodologies and operational best practices.

“With this initial integration of Kubernetes with the existing stack of open source network components, Euphrates enables NFV to make significant advances in the journey towards cloud native,” said Heather Kirksey, director, OPNFV. “Combined with a focus on XCI and modern DevOps practices, more efficient infrastructure, and enhanced operations capabilities, we’re witnessing the powerful culmination of three years’ worth of collaboration across a broad swath of open source communities, come to life.”

Key enhancements available in OPNFV Euphrates include:

  • Architecture: OPNFV container journey begins. Though early, there is an unmistakable trend towards the containerization of VNFs in the industry. Euphrates brings Kubernetes and container integration with multiple components of the end-to-end stack, as well as the ability to deploy containerized OpenStack via Kolla, which provides production-ready containers and deployment tools for operating OpenStack clouds that are scalable, fast, reliable, and upgradable using community best practices. These enhancements enable easier management of the infrastructure, support of cloud native network applications in NFV, and lighter weight control plane capabilities as service providers prepare for edge architectures to support 5G and IOT.
  • Integration: access to the latest upstream code. Building on the continuous integration/continuous deployment (CI/CD) pipeline integration work in Danube, Euphrates introduced the implementation of the XCI integrated CI/CD pipeline amongst OPNFV, OpenStack, OpenDaylight, and FD.io. Instead of waiting for an official stable release, the OPNFV CI pipeline integrates the latest upstream code from these upstream projects in order to more quickly resolve bugs and validate features. This reduces the time it takes for feedback on a new feature or bug-fix from months to days, greatly increasing the pace of innovation. XCI also enables multi-distribution support and fosters closer developer relationships.
  • New carrier-grade features. With the integration of the new Calipso project, operators now have operational visibility into their complex virtual networks. When combined with telemetry enhancements in existing Barometer and Doctor projects, users have access to a powerful service assurance framework. Euphrates also includes performance improvements on the Arm architecture, and in Layer 3 performance with FD.io. Moreover, Euphrates brings new security and user management capabilities with Moon, continued improvement in Service Function Chaining (SFC), FD.io, and new EVPN features. Euphrates also integrates the OVN network virtualization project along with the most recent versions of other upstream projects to provide additional choice in networking control options.
  • Enhanced testing and integration. The OPNFV integration and testing effort has made significant progress in providing an extensive set of tools to test the NFV cloud, VNFs, and complete network services. New projectsincluding Sample VNF, which provides testing of the VIM/NFVI layer with applications approximating real-life application workloads; and NFVBench, which provides an end-to-end dataplane benchmarking frameworkhave been introduced. Additionally, existing test projects have continued to evolve with new features, capabilities, and test cases.

“Euphrates brings a deeper level of maturity to the platform,” said Tapio Tallgren, chair of Technical Steering Committee (TSC), OPNFV, and lead software architect, Nokia’s Mobile Architecture Unit. “Iterative updates and improvements in areas such as MANO integration and service assurance, security, testing, and performance are part and parcel to bigger architectural changes that introduce Kubernetes as a VIM to orchestrate containerized VNFs.”

Looking ahead, the OPNFV Fraser Release is scheduled for spring 2018. Evolutions on the horizon include continuing to evolve MANO capabilities through ONAP integration, and a focus on analytics with PNDA.io analytics framework integration.

The OPNFV community is currently planning ts its fourth OPNFV Plugfest, December 4-8, 2017  in Hillsboro, Ore. Hosted by Intel, the event will focus on interoperability of the OPNFV platform in deployment, network integration, VNF applications, and more. Developers who are both OPNFV members and non-members are welcome to attend. More information is available here: http://events.linuxfoundation.org/events/opnfv-plugfest.

More information about OPNFV Euphrates is available here: https://www.opnfv.org/software

About the Open Platform for NFV (OPNFV)
Open Platform for NFV (OPNFV) facilitates the development and evolution of NFV components across various open source ecosystems. Through system level integration, deployment and testing, OPNFV creates a reference NFV platform to accelerate the transformation of enterprise and service provider networks. For more information, please visit  http://www.opnfv.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.

 

XCI: How OPNFV Slashed Upstream Integration from Months to Days

By | Blog

By Fatih Degirmenci, Yolanda Robla Mota, Markos Chandras

The OPNFV Community will soon issue its fifth release, OPNFV Euphrates. Over the past four releases, the community has introduced different components from upstream projects, integrated them to compose different flavors of the stack, and put them through extensive testing to help establish a reference platform for Network Functions Virtualization (NFV). While doing this work, the OPNFV community strictly followed its founding principle: Upstream First. Bugs found or features identified as missing are implemented directly into upstream code; OPNFV has carried very little in its own source code repositories, reflecting the project’s true upstream nature. This was achieved by the use of stable release components from the upstream communities. In addition to the technical aspects of the work, OPNFV established good relationships with these upstream communities, such as OpenStack, OpenDaylight, FD.io, and others. 

Building on previous experience working on integrating and testing different components of the stack, Euphrates brings applied learnings in Continuous Delivery (CD) and DevOps principles and practices into the fray, via the Cross Community Continuous Integration (XCI) initiative.  Read below for a quick summary about what it is, where we are now, what we are releasing as part of Euphrates, and a sneak peek into the future.

Upstream Development Model
The current development and release model employed by OPNFV provides value to OPNFV community itself and the upstream communities it works with, but is limited and dependant on using stable versions of upstream components. This essentially limits the speed at which new development and bugfixes can be contributed to upstream projects. This results in losing the essence of CI (finding issues, providing fast and tailored feedback) and means that the developers who contribute to upstream projects might not see results for several months, after everyone has moved on to the next item in their roadmap. The notion of constantly playing “catch up” with upstream projects is not sustainable.

In order for OPNFV to achieve true CI, we need to ensure that upstream communities implement a CD approach. One way to make this happen is to enable patch-level testing and consuming of components from master branches of upstream communities–allowing for more timely feedback when it matters most. The XCI initiative establishes new feedback loops across communities and with supporting tooling makes it possible to:

  • shorten the time it takes to introduce new features
  • make it easier to identify and fix bugs
  • ease the effort to develop, integrate, and test the reference platform
  • establish additional feedback loops within OPNFV, towards the users and between the communities OPNFV works with
  • provide additional testing from a production-like environment
  • increase real-time visibility

Apart from providing feedback to upstream communities, we strive to frequently provide working software to our users, allowing them to be part of the feedback loop. This ensures that while OPNFV pushes upstream communities to CD, the platform itself also moves in the same direction.

Helping Developers Develop by Supporting Source-Based Deployments
One of the most important aspects of XCI is to ensure developers do what they do best: develop. XCI achieves this by supporting source-based deployments. This means that developers can patch the source on their workstations and get their patch deployed quickly, cutting the feedback time from months to hours (or even minutes). The approach employed by XCI to enable source-based deployments ensures that nothing comes between developers and the source code who can even override whatever is provided by XCI to ensure the deployment fits their needs. Additionally, users also benefit as they can adjust what they get from XCI to further fit their needs. This is also important for patch-level testing and feedback.

Choice
What we summarized until now are firsts for OPNFV and perhaps firsts for the entire open source ecosystem; bringing multiple open source components together from master. But we have a few other firsts provided by XCI as part of the Euphrates release, such as:

  • multiple deployment flavors ranging from all-in-one to full blown HA deployment
  • multi-distro support: Ubuntu, Centos, and openSUSE
  • extended CI pipelines for all projects that choose to take part in XCI

This is another focus area of XCI: giving choice. We believe that if we offer choices to developers and users, they will leverage these options to invent new things or use them in new and different ways. XCI empowers the community by removing barriers and constraints and providing freedom of choice.

XCI utilizes tools such as Bifrost and OpenStack Ansible directly from upstream and what is done by XCI is to use these tools in a way that enables CI.

Join the Party
Are we done yet? Of course not. We are working on bringing even more components together and are reaching out to additional communities, such as ONAP and Kubernetes.

If you would like to be part of this, check the documentation and try using the XCI Sandbox to bring up a mini OPNFV cluster on your laptop. You can find XCI developers on #opnfv-pharos channel on Freenode and while you are there, join us to make things even better.

Finally, we would like to thank everyone who has participated in the development of XCI, reviewed our patches, listened to our ideas, provided hardware resources, motivated us in different ways, and, most importantly, encouraged us. What we have now is just the beginning and we are on our way to change things.

Heading to Open Source Summit Europe? Don’t miss Fatih’s presentation, “Bringing Open Source Communities Together: Cross-Community CI,” Monday, October 23, 14:20 – 15:00.

Learn more about XCI by reading the Solutions Brief or watching the video, and signing up for this XCI-based webinar on November 29th.

 

OPNFV Intern Spotlight: Shrenik Jain

By | Blog

We kicked off our intern program last summer and are pleased to have  welcomed an amazing group of young talent! They work directly with the community and receive hands-on development experience in NFV. Each intern works closely with an active OPNFV developer as their mentor on a project that suited interest and community need. This blog series aims to showcase these interns and the projects they work on, the mentors who are helping with their professional development, and their experience working in an open source community to help  accelerate NFV.

About Shrenik (in his own words):
I am  currently in my final year pursuing a dual degree – Bachelor of Technology and Master of Science in Computer Science and Research from the International Institute of Information Technology, Hyderabad. Presently, I am working on Cloud Economics and Resource Allocation problems in Federated Cloud environments. Aside from my studies, I am a big foodie and I like to try out different cuisines.

How did you hear about OPNFV and what got you interested in this internship?
I heard about OPNFV from college mates who had previously worked in OPNFV as interns.
Since I had already worked on docker as part of my research work, I was comfortable with open source and have been able to familiarize myself more with OPNFV and the community.

Can you talk about your experience working on an open source project? Any previous experiences you can share or key learnings from working on OPNFV so far?
I had a wonderful learning experience while working on the StorPerf project. I learned about new technologies, specifically Arm support being one of the most significant new technologies being added to StorPerf.

What’s the best thing you’ve learned from your internship?
The best thing I have learned is more effective communication within the community towards a proposal or a solution, and how to effectively keep on contributing to surpass the barriers of location and time zones.

Who is  your mentor and what’s the experience been like?
My mentor is Mark Beierl. He is an amazing mentor who is adept at his work and also very passionate. He has been very helpful and flexible during the entire duration of my internship. even when I bugged him a lot with silly questions.

What’s your advice to other aspiring open source folks out there?
My advice to them would be if you are thinking about open source, the right time to start is now. Don’t hesitate in asking for help. People in open source are amazing and they will welcome you with open arms.

What gets you jazzed to work with open source? (e.g., listening to music, drinking coffee, chatting in IRC, etc.)?
Coffee and chatting on IRC. There are a lot of interesting things to try with IRC (an IRC bouncer being a very simple one).

Being in open source allows you to work from anywhere in the world and interact with lots of different people. What have you found most surprising about the open source developer community?
The unambiguous communication within people spread in all parts of the world with a lot of politeness and respect for each other is very inspiring. The way everyone is welcome to contribute and the fact that people are always ready to help in case of any stuck ups keeps moving you forward.

What do you want to do next? What is your dream job?
I am still trying to figure this one out. But I would go for a job where I am happy with the work I do.