WEBVTT

00:00:01.110 --> 00:00:05.350
Let's consider Software Defined Networks and Network Function

00:00:05.350 --> 00:00:09.600
Virtualization. With software‑defined networks, we find a system

00:00:09.600 --> 00:00:12.420
that is actually independent of the cloud.

00:00:12.650 --> 00:00:16.280
In fact, it was born in the same time as the cloud.

00:00:16.290 --> 00:00:20.980
Software‑defined networks are primarily concerned with separating the

00:00:20.980 --> 00:00:26.500
control from the data plane and making sure that there is forwarding of

00:00:26.500 --> 00:00:31.160
data from network to network, whereas network function virtualization

00:00:31.280 --> 00:00:37.240
is focusing on the abstraction of all network services and devices from

00:00:37.240 --> 00:00:38.460
their physicality.

00:00:39.540 --> 00:00:43.620
There are three layers of the software defined network,

00:00:43.630 --> 00:00:47.170
beginning with the application plane, going into the control

00:00:47.170 --> 00:00:49.940
plane, and then, finally, the data plane.

00:00:50.060 --> 00:00:55.470
It is the data plane that is concerned with the abstraction of infrastructure.

00:00:55.480 --> 00:00:59.510
The original abstraction of infrastructure included routers and switches.

00:00:59.520 --> 00:01:04.569
The data plane performs an abstraction that leads to the forwarding

00:01:04.580 --> 00:01:09.210
of data, and that forwarding of data makes it so that network

00:01:09.220 --> 00:01:13.230
engineers are not really concerned about the physicality of the

00:01:13.240 --> 00:01:17.320
infrastructure, so they're moving from an infrastructure‑centric

00:01:17.330 --> 00:01:20.450
behavior to a data‑centric behavior.

00:01:20.460 --> 00:01:22.230
That's an important testing point.

00:01:22.240 --> 00:01:26.440
The transition of infrastructure centric to data centric

00:01:26.480 --> 00:01:28.670
occurs with software‑defined networks.

00:01:28.840 --> 00:01:32.340
At the control plane, there's actually a controller

00:01:32.340 --> 00:01:35.200
card or a controller hardware.

00:01:35.210 --> 00:01:39.490
That controller hardware is the thing that interfaces all of

00:01:39.490 --> 00:01:43.360
the network connections into a control point.

00:01:43.440 --> 00:01:47.480
OpenFlow was the original language that was designed for

00:01:47.480 --> 00:01:51.750
software‑defined networks control at the control plane.

00:01:52.340 --> 00:01:55.290
Now, you have providers like Juniper,

00:01:55.290 --> 00:01:59.570
Cisco, Palo Alto, and others that have the capability of receiving

00:01:59.580 --> 00:02:03.830
Infrastructure as Code directly onto their devices so that they can be

00:02:03.830 --> 00:02:07.550
managed any way that is central in the control plane.

00:02:07.940 --> 00:02:13.030
The control plane connects to the data plane by means of southbound interfaces.

00:02:13.030 --> 00:02:17.500
These can include network protocols and traditional network operating

00:02:17.500 --> 00:02:22.160
systems that run on the devices. At the application plane, you have a

00:02:22.170 --> 00:02:26.490
interconnection between the control plane and the application plane by

00:02:26.490 --> 00:02:31.670
means of the northbound interfaces. Northbound interfaces can include

00:02:31.670 --> 00:02:37.900
things like HTTP, XML, JSON, it's the programmability capabilities that

00:02:37.910 --> 00:02:43.200
would allow you to manage the Infrastructure as Code going all the way down

00:02:43.200 --> 00:02:48.080
to the equipment. While software‑defined networks can exist independently

00:02:48.090 --> 00:02:49.110
from the cloud.

00:02:49.120 --> 00:02:53.110
If you were to integrate a software‑defined network into the cloud,

00:02:53.120 --> 00:02:57.330
it would be the management plane of the cloud that connects

00:02:57.330 --> 00:03:00.880
directly into the control plane of the SDN.

00:03:01.140 --> 00:03:06.980
There is an amalgam of services that are controlled by means of network function

00:03:06.980 --> 00:03:10.810
virtualization that could include network interface cards,

00:03:10.810 --> 00:03:13.050
firewalls, IDSs, IPSs,

00:03:13.410 --> 00:03:16.770
and this is how you would have an integration of the

00:03:16.780 --> 00:03:20.460
SDN and the NFV working together.

00:03:20.840 --> 00:03:24.250
Next, let's consider the virtualization of the

00:03:24.250 --> 00:03:27.460
resource pool that is compute services.