This is short description of Open day light (ODL). In this, you fill use case, pros & cons, architecture etc.

1. OpenDaylight
Presented By-
Utkarsh Soni
RA1511003020678
III / V / K

2. Soft Copy
Presentation (2)
Hard Copy
Presentation (2)
Explanation (2) Communication
skill (2)
Viva (2) Total (10)
Student’s Signature
Utkarsh Soni
RA1511003020678
Staff In-charge’s Sign
Mrs. R. Angeline

3. Introduction
The “OpenDaylight Project” is a collaborative open source project hosted by The
Linux Foundation. The goal of the project is to promote software-defined networking
and network functions virtualization. The software is written in the Java programming
language.
OpenDaylight is a highly available, modular, extensible, scalable and multi-protocol
controller infrastructure built for SDN deployments on modern heterogeneous multi-
vendor networks.
 Northbound API’s to apps (e.g. OpenStack)
 Southbound interfaces to network devices (e.g. OVS)

4. Challenges in real world
Communications providers and enterprises alike are eager to build or adapt their
networks to be more flexible and responsive to their organizations’ and customers’
needs. At the same time, they are driving network automation to improve operational
efficiency.
That’s how, a movement grew out of a simple question :
Why shouldn’t networking devices be programmable just as other computing
platforms are?

5. Software-defined Networking (SDN)
The answer of that question is SDN. The benefits of SDN:
 No more arcane protocols to learn.
 No more waiting and hoping for networking vendors to develop specialized features
you need.
 If you could develop your own features, you could then optimize your device
selection for price and performance independently of feature-richness.
 Interoperability of different physical and virtual device types from different vendors.
 Continuous visibility of flows from source to destination.
 Common management framework for all devices.
 Programmability to shape network behaviour according to users’ needs.
 Automation of and by policy.

6. SDN Platforms
 OpenDaylight
 Cisco ACI
 ONOS (Open Network Operating system)
 Floodlight
 VMware NSX
 Beacon
 OpenContrail
 VortiQa
 POX
 VSP (Virtualized Services Platform)

7. Origin & Releases
 Hydrogen (2013)
 Helium (2014)
 Lithium (2015)
 Beryllium (2016)
 Boron (2016)
 Current Carbon(2017)
 Nitrogen in September 2017 (tentative)
 Periodic release after 9 months

8. Keys
 Dynamic network services
 Dynamic intent-based policies
 Virtualizing functions with service function chaining (SFC)

9. Controller Architecture

10. Usecase
 SD – Core
• Traffic sharing between the switched and routed domains
 Zero touch installation
• Automated setup of the software profile and services configuration
 Brownfield adaption
• Integrates legacy systems and new SDN equipment in one-network with plug-ins

11. Usecase
 Network Configuration and management
• Manage network devices with a single, consistent interface
 Network analysis and policy control
• Automates analysis and action for pre-defined policies
 Alarming and notification
• Maps underlying devices/EMS data to normalized model

12. Pros
 Supports a wide variety of SBI protocols versions
 Active community
 Aligned with vendors and telco's
 Easy proposal of projects
 Easy development

13. Cons
 Complex to install and operate
 Not so good documentation (e.g. flavours)
 Development of modules requires a deep knowledge of ODL
 It’s not “Pure” SDN

14. User Interface (UI)

15. Thank You