Search results

In this module, you will learn about the motivation and history behind the separation of the control and data plane, as well as the challenges and opportunities that this architectural paradigm offers. Задачи обучения Explain the difference between control and data plane. Produce examples of functions provided by each plane. Demonstrate the function of each plane.

In this lesson, you will gain experience with OpenFlow/SDN control, gain some exposure to different SDN controllers, learn about the tradeoffs of using different SDN controllers, and gain some experience of using SDN to customize control-plane behavior. Задачи обучения Summarize how an SDN controller can populate a switch's forwarding table. Describe the benefit of using an SDN controller to control multiple switches in a single network. Create a controller and basic switch environment. Compare the design tradeoffs between some of the more commonly used SDN/OpenFlow controllers. Set up controller in Mininet that can perform basic operations.

By the end of this module, you should have a good understanding of what network virtualization is, what it is used for, and how it relates to software defined networking. Задачи обучения Discover what network virtualization is and why it is used. Identify various ways of implementing virtual networks. Explain why Mininet is useful. Practice how Mininet works.

This module is relatively independent from some of the other modules, as programmable data planes involve new types of technology. Still, you should by now have a very good understanding of SDN-based control and virtualization. OpenFlow's design was somewhat of an accident of the hardware support that was available at the time. More recently, people are exploring how programmable hardware can help us design a control protocol with the benefit of being able to change the data plane. Задачи обучения Describe why programmable data planes are needed. Discuss the limitations of OpenFlow and how programmable data planes can address some of these limitations. Appreciate some of the design decisions associated with programmable data planes. Compare the tradeoffs between hardware and software programmable data planes (i.e., flexibility vs. performance).

In this part of the course, you'll learn about programming languages and controllers that make this programmability possible. We will focus on one language in particular, Pyretic, which is from the Frenetic family of languages. We will also look at a runtime and northbound API called Resonance, which allows network programmers to write policies that respond to changing network conditions (e.g., security events, shifts in peak vs. off-peak time, traffic fluctuations or link failures). Задачи обучения Describe why SDNs need higher-level programming languages. Distinguish between the applications and use cases of different SDN programming languages. Implement simple network policies with SDN programming languages.

In this module, we will apply that knowledge to explore how SDN can be used to solve problems in various networking domains. We'll start by looking at data-center networking, where SDN has arguably gained the strongest foothold (to date). We'll then explore applications of SDN to interdomain routing, where new applications and deployments are emerging. Finally, we'll explore the application of SDN in home networks, which has seen some preliminary work, deployments, and ideas. Задачи обучения Relate the challenges of network management data center networking. Discuss how SDN can help solve some of the problems that data center network operators face. Review the basics of Internet peering and interdomain routing, how BGP supports interdomain routing policies today, and things that GBP does not do well today. Compare the advantages and challenges of using SDN for interdomain routing. Explore how SDN can be used to simplify network management challenges in homes.

In this module, we'll be looking at another control framework built using Pyretic called "Kinetic". Kinetic is a domain-specific language embedded in Pyretic that allows programmers and network operators to automatically verify the correctness properties of the control program. Your previous experience with Pox and Pyretic should provide you with very useful experience and perspective for comparing the three ways of programming a controller. In the assignment, we ask you to compare Kinetic to either Pox or Pyretic, so the experience you gained from those assignments should prove very useful. Задачи обучения Describe the different types of ways to verify the correctness of a network configuration and behavior. Distinguish between methods of checking assertions in model checking. Write control programs and automatically model check them using Kinetic.

author - Дарья Сидоренко