ipSpace.net » Workshops » SDN, OpenFlow and NFV Workshop
OpenFlow, Software Defined Networks (SDN) and Network Function Virtualization (NFV) technologies fuel the latest hype bubble in the networking industry and service provider environments.Based on vendor and industry press promises, well-published OpenFlow deployment with Google’s internal network, and numerous other industry initiatives, these technologies became an unavoidable boardroom discussion as service providers and enterprises try to seek new revenue streams or optimize their costs.
On the other hand, many engineers are left wondering what’s really going on behind the scenes and how useful these technologies might be in real-life networks.
This workshop describes the technology fundamentals of Software Defined Networking (SDN), OpenFlow and Network Function Virtualization (NFV), their advantages and pitfalls, and the potential use cases including a brief overview of some existing deployments. The focus of the presentation is on real-life deployment scenarios and design discussions.
See workshop contents for more details.
Network architects, designers and implementation engineers working in environments that are evaluating the viability or plan to deploy SDN solutions based on OpenFlow, BGP, NFV or other related technologies.
While the whole IT industry has been moving toward highly automated solutions in the last decade, networking has remained stuck – most networking engineers are still manually configuring individual devices.
There’s high time we change the deployment and operational processes and reduce the amount of time spent doing repetitive manual tasks; this part of the workshop will give you some high-level guidelines and explore the high-level aspects of SDN including:
The second part of this section focuses on technologies underlying SDN and NFV – OpenFlow, NETCONF, APIs, virtualization and virtual appliances. It will also try to answer the fundamental questions: When, Why and How should you program your network.
Software defined networking is not a new technology – we’ve been using the concepts of programmable networks for decades.
This section describes common SDN architectures and deployment scenarios including:
This section describes the concepts of OpenFlow, a new protocol used to decouple control plane (topology discovery, path calculation…) from data plane (packet forwarding). It covers the following topics:
OpenFlow concepts are not new and share scalability challenges with similar technologies and architectures including Frame Relay, ATM, ForCES and MPLS-TP. This section discusses the major OpenFlow scalability challenges:
Numerous SDN solutions use BGP as the controller-to-device communication protocol. This section explains the basics of BGP-based SDN, documents several typical use cases and gives practical deployment guidelines, including sample open-source-based controller implementation.
If you open a firewall, load balancer, WAN accelerator or almost any other network services appliance, you’ll find one or more x86 processors, standard GE/10GE NICs and some custom packet handling logic. Is there any reason we have to be tied to physical hardware? Wouldn’t it be better to deploy the same services in virtual machine format and make them flexible? That’s the fundamental concept of Network Function Virtualization.
Does it really make sense to replace physical network services appliances with virtual machines? What are the benefits and drawbacks of NFV approach? This section will give you the answers you need to start evaluating applicability of NFV in your environment.
NETCONF is a protocol widely used to configure networking devices (it’s supported by Brocade, Cisco, Juniper and other vendors). This section describes NETCONF and YANG (the data model description language used by NETCONF), their benefits and shortcomings, and the vendor-specific implementation details. It includes the following topics:
This section describes typical network automation scenarios, from device provisioning to automated troubleshooting and acceptance tests and guides you on a journey from manually-operated networks of today through network state abstraction toward automated provisioning and failure remediation.
On that journey you’ll also identify the common reasons for network automation, meet CLIs and APIs, and learn about typical caveats.
Chef, Puppet, and Ansible are the most popular server configuration management tools, and all of them get used in network automation solutions.
This section describes the fundamentals of all three tools, their typical implementation on network devices, and the potential benefits and drawbacks of using them. It then focuses on Ansible is one of, which is commonly the tool-of-choice due to its agentless design.
Networking solutions with centralized network intelligence or control plane have existed for almost half a century (IBM SNA, ATM, Frame Relay, Ipsilon Flow Management Protocols).
Not surprisingly, novel SDN architectures using centralized controller clusters exhibit similar challenges:
This section describes typical SDN deployment considerations, ranging from architectural and design challenges to security and operational considerations.
Service providers and enterprises are already deploying SDN, using NETCONF, BGP or OpenFlow as the implementation technology. This section describes numerous use cases based on real-life deployments:
Contact us for more details, pricing or if you want to customize the workshop with your specific design challenges.