shortage of network engineering projects named after the term Open these days. Besides the Open vSwitch and OpenFlow projects, that we have already studied in the last two chapters, there are community driven projects such as Open Network Operating System (ONOS, http://onosproject.org/), OpenDaylight (https://www.opendaylight.org/), and OpenStack (https://www.openstack.org/). Furthermore, there are other projects that are open in nature but arguably heavily backed or bootstrapped by commercial companies (such as Ryu with NTT); for example OpenContrail (http://www.opencontrail.org/) with Juniper Networks and Open Compute Project (http://www.opencompute.org/) bootstrapped by Facebook. There is also the Open Networking User Group (ONUG, https://opennetworkingusergroup.com/) that, according to their mission statement, enable greater choices and options for IT business leaders by advocating for open interoperable hardware and software-defined infrastructure solutions.

On one hand, it is terrific to see so much innovation and community involvement in the network engineering field. Many, if not all of them, use the term Software Defined Networking (SDN) and Network Function Virtualization (NFV) to describe their mission and features when it comes to the technology they bring forward. Many of the projects utilize the same technology, such as OpenFlow, but add different orchestration engines or APIs on top to target slightly different audience.

We have already discussed in detail about OpenFlow in the previous two chapters. In this chapter, we will take a look at the two other projects that have general industry support amongst the community and vendors:

• OpenStack: It is an open source Infrastructure-as-a- Service cloud platform with integrated components for the datacenter environment. There are many different components within the project, such as compute, storage, and networking resources. We will focus on the networking portion, code name Neutron, within OpenStack.
• OpenDaylight: It is a community-led and industry-supported open source project with aims to accelerate the adoption of SDN and NFV with more transparency. The project was administrated by the Linux Foundation from day one and the founding members include industry leaders such as Cisco, Juniper, Arista, Brocade, Microsoft, VMware, Red Hat, and many more.

When discussing the two projects, we will look at how each project implements NFV. NFV is a concept where we can use software and virtualization technologies to simulate traditional network functions, such as routing, switching, load balancing, firewalls, caching, and more. In the previous chapter, we saw how we can use OpenFlow and Ryu controller to simulate functions such as routing, switching, and traditional firewall, all using the same Mininet Open vSwitch.
Many full size books have been written on both OpenStack and OpenDaylight. It would simply be a false hope trying to cover the two topics in depth within the constrains of a chapter. Both these subjects represent important steps forward in the network engineering world, that are worth spending time understanding. In this chapter, we will try to establish a solid basic understanding of both projects from network engineering perspective, so the reader can dive into each topic deeper in the future.

Additionally, we will cover the following topics:

• Networking in OpenStack
• Trying out OpenStack
• OpenDaylight Programming overview
• OpenDaylight example