Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning OpenDaylight

You're reading from   Learning OpenDaylight A gateway to SDN (Software-Defined Networking) and NFV (Network Functions Virtualization) ecosystem

Arrow left icon
Product type Paperback
Published in May 2017
Publisher Packt
ISBN-13 9781782174523
Length 336 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Reza Toghraee Reza Toghraee
Author Profile Icon Reza Toghraee
Reza Toghraee
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Introduction to SDN - Transformation from Legacy to SDN FREE CHAPTER 2. Overview of OpenDaylight 3. OpenDaylight Installation and Deployment 4. Building a Virtual SDN Test Lab with Virtual Switches 5. Basic Networking with OpenDaylight 6. Overview of OpenDaylight Applications 7. Building SDN Applications for OpenDaylight 8. Network Function Virtualization 9. Building a Software-Driven Data Center with OpenDaylight

OpenDayLight's Virtual Tenant Networks


To support and better integrate with OpenStack's tenants, ODL has a specific module named Virtual Tenant Network (VTN).

VTN is one of the very interesting modules in ODL; we haven't discussed this yet. VTN integrates with OpenStack through the ML2 plugin. Technically, VTN is an SDN policy manager. It builds a list of tenants and their resources (virtual machines, networks, IP addresses, MAC addresses, policies, NAT, and so on).

Once we connect ODL and OpenStack using the ML2 plugin, any newly created tenant in OpenStack will be created in ODL's VTN too.

VTN allows users to design a virtual legacy L2/L3 network. Once the network design is finalized in VTN, it will get automatically mapped to the underlying physical network. This mapping is done via the ODL controller by injecting the required configuration to each individual switch or networking equipment, based on the southbound protocol supported by that networking gear.

The following picture from ODL...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime