oes in the server and storage virtualization space. ODL project has currently settled into a stable and growing federation. ODL is designed to care for existing environments and new environments. This is one of its key strengths. It allows ODL to be used for a broad set of use-cases, from configuring existing switches and routers, to controlling the configuration of OpenROADM- based devices, to the control over routing and flows. In a similar way, for the hypervisor data plane realm, FD.IO has emerged to fill the "federated" gap, when the incumbents like Open Virtual Switch (OVS) and OpenContrail did not have the scope or the governance model to do SO [10]. When the European Telecommunications Standards Institute (ETSI) industry specification group for NFV was finished with its first set of NFV white papers, a group of participants in that effort came up with the idea to create an open-source reference implementation of NFV standards. Based on the lessons learned in creating OpenStack and ODL, an Open-Source Foundation called OPNFV was started within the Linux Foundation Collaborative Projects effort. OPNFV is intended to regularly release a reference platform and reference methodology for implementing NFV and Building the Network of the Future its associated infrastructure. The goal of the OPNFV project is to reduce redundant effort around documenting NFV use cases, creating functional and performance testing standards and tools for NFV, integrating existing software such as OpenStack and ODL, filling in gaps where key func- tionality is missing, and working to ensure NFV requirements are represented and code accepted in upstream projects. By doing this, consistency and interoperability can be maintained across a diverse set of integrated software. In the "shift to software," Open Source Foundations, specifically those with federated frame- works, and their collaborative ecosystems, play an integral role in the adoption and evolution of NFV and SDN. 17.6 SCRIPTING AND CONCURRENT LANGUAGES Long compilation times 