 So I'm live, very good. Well, thanks, folks. My name's Phil Robb, and we're going to be talking about Open Daylight. For those of you that aren't familiar with the project, Open Daylight launched in April. Our first code release is in December. And because of that, pretty much all of the developers are heads down. So I don't actually have a demo for you today. But I do want to kind of talk about the project and take any questions. So first off, just to kind of level set with everybody exactly what is SDN. And it really depends on who you are and how you're looking at SDN. Fundamentally, it's about software-defined networking. But it's many different things to many different people. That includes network virtualization in the cloud, dynamic service chains for service providers, dynamic traffic engineering, dynamic network configuration, network function virtualization, and many other use cases. And in the end, networking is just really a mind-boggling, complex thing. And it's been that way over the last couple of decades. But there are some commonalities. It's all about bringing programmability to the network and radically increasing flexibility. We've lived in an environment where needing to go to every switch in program, every switch for its control plane functions has just been the norm. And that makes networks very, very fragile. So moving that configuration, both the time in the software to someplace centralized is a key. There's lots of different good ideas on how to do this. And we're really, really young. I mean, we've watched Neutron as far as that goes, evolve as quickly as it has. There are lots of different ways of doing this and to bring more programmability to the network. So for us, as part of Open Daylight, making the project modular, flexible, and evolvable over time as we figure these things out is really key because doing this type of network programming and having such a programmable network, we are so early into it, we're not quite sure how best to do it. So being able to have a tool that can do that is really a lot behind the architecture of the project. So what is Open Daylight? It's a community. It's an open source project. It's not a company. So it's very similar to OpenStack as far as being just an open source community to do a focused technical activity, that activity being software defined networking. So we wanna create this evolvable SDN platform with some common abstractions and capabilities northbound of that controller or southbound of Neutron. And Neutron is obviously a very important use case for us. We wanna do intermediation between those northbound APIs and the southbound protocols that can be implemented down into the network, provide programmable network services, create network applications, and whatever else we need to do to actually make this work. So this is the basic framework of most SDN controllers and specifically of Open Daylight. So at the bottom you've got this set of southbound protocols. One of the most important is OpenFlow. For those that are following the software defined networking space, OpenFlow is the key protocol and is currently relatively young and is evolving pretty quickly. We have a service abstraction layer that is a key unique feature within the Open Daylight controller in that it presents the capabilities of those southbound protocols in a consistent manner to the northbound services and the northbound applications that ride above this controller. In the center you've got core network services that are done for any network controller. These include things like topology management, statistics management of the different switches in the network and so forth. There's a restful API that then is exposed to the northbound applications. So who is Open Daylight? Again, similar to OpenStack, it's a foundation and a nonprofit organization and these are some of the corporate members of that nonprofit to help facilitate the community, but it's really an open source community. So like any other project, it's all about whoever shows up to contribute code and to participate. We currently have, actually this is a little bit of a dated slide, we've got well over 100 active contributors and we're running somewhere around 120 to 130 commits a week. So again, for a project that started in April, we've got a lot of momentum and it's going really well. So what is Open Daylight delivering? So our first multi-release, again, is in December. There are 12 sub-projects. So an Open Daylight, as you could see, it's really formed as it's mostly Java-based. OSGI bundles is how we're putting things together and there are 12 separate projects underneath the whole umbrella. There's the core controller and then a variety of others and I'll show you those in a little bit. But we want to deliver a single coherent thing. So we're in the middle of doing full system and integration testing across those 12 projects and delivering that, again, as a unified entity in December. The code name for that is Hydrogen and specifically the date is December night. From a governance standpoint, again, your typical open source project, membership is open to all. It's got business leadership with a board of directors over that nonprofit organization. There's a technical steering committee that guides all of the technical aspects of the project for technical selection, project selection, arbitration of decisions and so forth. Fully meritocratic in a technical sense and totally transparent with your typical type of project life cycle management. Here's a little bit tighter view of the architectural framework. And again, so across the top layer, you can see the different types of northbound applications. We're expecting to be part of the integration effort with Open Daylight over time. To cloud platforms such as OpenStack as well as CloudStack, level four through seven services, your classic GUI and so forth. You can see in the middle the different types of base services, topology manager, statistics manager, the switch and device manager as well as least path forwarding and so forth. And then there are a set of extended services that are also part of this first release around doing virtual network, doing overlays, traffic redirection, storage services and so forth. And then again, a variety of southbound protocols down underneath the controller. From a project life cycle standpoint, again, we've pretty much taken the Apache model very similar to OpenStack where we'll have projects that are proposed. They typically go into incubation stage if they are accepted. And thus far, we actually haven't had anything not accepted as far as a project goes. When we first kicked off, we also had a bootstrap phase because we had some pretty significant and mature pieces of code that were contributed. So to get those as part of the project early on, we had a bootstrap phase as well. So about half those 12 projects are currently in bootstrap and the other half are in incubation. From there, once we go through our first release, we will start to have identified the projects as being more stable and mature. So we'll have a variety of those actually moving to the mature state and then eventually into core, right? Where core is an absolutely necessary and essential feature within the controller for it to really exist. So again, a somewhat typical project life cycle that's being maintained. So from a release standpoint specifically, these are the components that are in this hydrogen release, this first release we're doing in December. Again, obviously a core controller. In addition, we have virtual tenant network that was contributed by NEC. We decided to do a set of Yang tools to generate consistent data models that will be used both for the generation of the northbound APIs as well as for the southbound. There's an OpenFlow protocol library as well as an OpenFlow plugin. The protocol library was implementing the 1.3 spec of OpenFlow and the OpenFlow plugin is really built. We kind of refactored everything realizing that we need to be able to support multiple versions of OpenFlow as different switches are coming out and are compatible with different versions of OpenFlow. We need to be able to support the new versions of OpenFlow going to some switches and the older versions of OpenFlow going to existing switches. So having a method of being able to both quickly support new implementations or new versions of OpenFlow as well as supporting existing versions was important. So creating that type of a plugin so that we could do that was one of the key attributes of this first release. There's an affinity metadata service that is really good at doing policy management, identifying nodes, groups of nodes and the policies that will work in between those. Defense for All is actually a distributed denial of service attack application to detect and mitigate denial of service attacks, BGP LS and PSEP for protocols as well as OBSDB for configuration of virtual switches and OpenV switch. The Lisp flow mapping for doing location identifier separation, which is a good protocol for service chaining as well as SNMP for SDN. And this is doing, as it says, just doing basic management programming through SNMP which is a pretty common denominator for legacy devices out there. And then last but not least is distributed overlay virtual ethernet or open dove. And that's an overlay technology that is particularly applicable to OpenStack environments. So this is the whole release, right? And so again, as a Java based application set, if you go and download the code or if you were to acquire everything that was possible for this particular version, this is what the picture would look like. But again, it's really built to be modular and pluggable so you don't have to have all of these features implemented all at the same time. And actually we don't expect most folks to have all of these features selected at the same time. So we've got a base edition where it's really prototyping educational environments, simple, simple open flow SDN controller is really what this is about. We're currently under discussions to add OBSDB rather to this. We're not quite sure if we're gonna put OBSDB into this base edition or not. It kind of makes sense because again, with virtual switches being able to configure them to run open flow through it in an educational or prototype environment kind of makes sense. There's a service provider edition where we're bundling together the affinity service, the LISP service, as well as SNMP, BGPLS, PSEP, and the LISP protocol, as well as the denial of service application. Then there's a virtualization edition which would probably have the most applicability to folks in the open stack arena with the VTN coordinator, the denial of service tool, as well as the open stack neutron plugin. And that's going directly to an open stack service. So we want to work as part of the Ice House Rev. We're working on a protocol set that is basically implementing the exact same APIs for neutron in the REST API for Open Daylight. So it'll be a straight pass through from neutron down into the Open Daylight SDN controller. And then either the Dove overlay manager or VTN, the virtual tenant network slicing will be one of the two common network virtualization technologies that are used underneath open stack. So again, open source project, we're always looking for more folks to come and come play in our sandbox. If you want to get involved or you want to look up more information on Open Daylight, come take a look at the Wiki. All of the documentation for development, downloading the code is all there. Right at the very beginning of that, that Wiki is a getting started section. Go take a look at that. It'll show you how to get the code, how to get involved and how to bring it up and get it into your development environment. Lists.opendaylight.org have all of the mailing lists to which there's one called Discuss, which is the most popular. There's also an IRC channel, which is on FreeNode called Open Daylight. Again, a very active community, lots of folks on the mailing list, lots of folks on the IRC channel. So it's very, very easy to get started. We're very accommodating. We want more people to be working with this code and to come play with us in this project. So it's very easy to do that. And with that, I think that's it. The standard site for the non-profit is OpenDaylight.org. And if you want more information on that non-profit, just send mail to info at OpenDaylight.org. Thanks very much.