Charles Eckel

We have a rich and evolving set of standards that we use to build and deploy interoperable systems. We also have a talented and productive open source community that creates code intended for use in these systems and their ongoing operation. The challenge is shifting from defining standards and writing code to knowing which standards to use and finding code that accelerates implementation and deployment of these standards. This challenge increases as we become more efficient at defining new standards and creating new open source projects. What if we could make it easier to navigate this landscape? What if we could create clear links between standards and code? This would make our open source and standards communities more productive. It would also make the great work they do more useful and rewarding. Fortunately, a set of practices is being defined and put in practice to make make it easy to identify and find open source code related to IETF standards. Join this session to learn what new mechanisms exist, how to use them, and to how help shape what comes next.

Open source communities move quickly, value running code, and docs are best effort at best. Standards move slowly, value precise specs, and negotiate compromises for broad alignment. Given these differences, why would open source communities fraternize with standards orgs? Standards orgs such as IETF and MEF realize they need to change to remain relevant. By embracing open source, standards orgs benefit from the speed and collaborative spirit of open source and get timely feedback on the clarity and correctness of standards as they evolve in parallel with running code. Open source communities gain users, address additional use cases, and gain the stability of standards to ease integration efforts and avoid forks. This session explores this evolution in standards orgs, highlights areas of mutual interest, and shares ideas on the benefit of closer collaboration.

Please note that this talk replaces one entitled "Open Source for students, by students" that was due to have been given by Kristin Yim. Also this talk was originally scheduled to be given at 10:00.

By collaborating with standards organizations and supporting existing and evolving standards, the open source community gains users, address a larger set of use cases, and benefit from the stability of standards that can help avoid harmful forking and ease integration efforts. Standards orgs benefit from the speed and collaborative spirit characteristics of open source, and they gain timely and critical feedback on the clarity and correctness of their standards as they evolve iteratively and in parallel with the open source code. The end result is open source code that is more consumable by industry, and standards that are more consumable by the open source community.

Companies regularly use and contribute to FOSS. Most larger companies now employee internal staff who make policy decisions, recommend Tools, oversee license compliance, teach others about FOSS, and interpret community politics for the company. Different offices and departments usually differ in their approaches to managing, using, contributing to, and releasing FOSS. This second annual Open Source Program Office (OSPO) panel explores the different approaches companies have to FOSS.

Software Defined Networking (SDN) may have started as the separation of the control plane and the data plane, but the true power lies in the ability to communicate with the network through well defined interfaces using standard protocols. This session provides a brief intro to SDN in general, and more specifically to OpenDaylight, an open source platform for programmable SDN. Next we dive into network programmability, including why we need it and the role of NETCONF, YANG, and RESTCONF. Then we put the theory into practice as we install OpenDaylight as use it a platform for programming a sample network.

Heard about OpenDaylight and SDN? Ready to get your feet wet and start kicking the tires with an OpenDaylight installation? This session provides a brief intro to Software Defined Networking (SDN) in general, and more specifically to OpenDaylight, an open source platform for programmable SDN. After providing a high level overview of the architecture, the session goes on to show you how to deploy OpenDaylight and interact with it through the CLI and graphical tools. You will learn how to configure various options and enable/disable various features, and how to check the logs to verify things are working as planned and trouble shoot things when they are not. Lastly we show you how to interact with OpenDaylight through its northbound APIs for network aware applications and southbound plugins to physical and virtual network elements.