Re: [PLUG] Fwd: VMware Releases Security Update

There's also the concept of the data plane and the control plane being separated. So, for instance, interior to a VMware cluster, you can route packets from one VM to another or from one subnet of VMs to another subnet. The trick lies in the fact that the "networking" might not even be exiting the cluster and the data may be being shuffled around on a few system buses instead of even hitting networking gear.

On Thu, May 17, 2018 at 7:55 AM, brent timothy saner <brent.saner@gmail.com> wrote:

On 05/17/2018 07:17 AM, Ron Mansolino wrote:
> Can someone provide a definition for "Software Defined" networking?
> (as far as I can tell, it's "We have a control panel for provisioning")
>

i'm not sure how vendors use it ;) but as a concept, it's treating
network configuration (firewall, routing, announcements, etc.) as
objects rather than device-specific policies/implementations.

in other words, it centralizes configuration so that instead of "saying"
that "route 1.2.3.4 needs to be served by gateway 1.1.1.1", you instead
implement something like "network foo needs access to network bar via
object baz in group quux".

for a rough analogy, classic topographical networking is to SD
networking as procedural or functional programming is to OOP.

i still think it's largely abused and i'd say 9 out of 10 deployments
don't really need it, though.

___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug

-Doug

___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug