SDN and NFV - VirtualizedGeek Tech Talk Episode 17
Transcript
hi this is Keith Townsend you're listening to episode 17 of virtualized Geeks Tech talks mixed a couple of weeks uh I'm traveling to the West Coast back and forth and I'm really having a hard time getting uh the time you write uh and plus I've had really poor internet connections so I can probably I could probably make a video but uploaded has been uh quite difficult so in the past couple of weeks kind of the focus for the um uh kind of uh virtualized geek and
Technology the general has been fdm I read a really or rather I watched a really interesting video uh that I posted to the blog that was given at Stanford a few weeks ago uh now going on a couple of months on basically the basics of SDM the state of sdn where's sdn Now versus where sdn was going to go thanks to Lenny for providing me the link I've watched the first 14 minutes of the video a couple of times just to continue to get my arms
around uh I think the final Concepts or the maturing concepts of sdn and uh where the kind of the industry leaders and the thought leaders are taking or trying to guide the technology and uh you know gist of it is pretty much what we've always said so you know you have kind of the open Flow Network operating portion of operating system portion of uh uh sdn determining um where packets go or how or what package should go and and whether or not they should be filtered
or router that routed and so forth and then there's kind of uh the network uh uh topology architecture how does that spread against you know spread across different uh network devices across your network so basically abstracting the control plane those two parts of control plane understanding uh where packets go and understanding the topology of the network so you know you can think about um replacing s SL I mean ACLS and uh ACLS and forwarding lists and all that with uh open view type I'm sorry open
flow type Technologies and then uh taking your diastra or open ospf or whatever your networking protocol is and having that run on the server and distributed across your whole all your network devices physical network devices what was a pretty interesting and pretty exciting was to listen to the speaker talk about how uh the killer app for sdn is actually Network virtualization so you know I've talked about Network virtualization a couple of times on the blog specifically about the difference between sdn and network virtualization so uh
you know taking it one step further and allowing you to virtualize the actual components of your network though that physical layer virtualizing that physical layer and abstracting the hardware so uh taking away uh I think the common term is now nfv Network function Network functions something another uh but oh I'm sorry Network virtualization function or network virtualization however the acronym goes the ideal is to take uh physical devices abstract that uh the underlying infrastructure into a virtualized device so you have you know many ports connected
at a uh physical layer those ports are assigned to Virtual devices such as router switches uh what the speaker talked as middle boxes so firewalls little balancers or whatever it may be so you can take those logical uh devices connect those physical associate those physical ports with them and now they can become any type of Port needed on your network that allows you to do some quite amazing things with networking uh I'm actually right writing a blog post on kind of the of uh you know
the Preamble exploring a little bit of the Preamble why sdn is even needed or even if it's needed at all you know uh one uh topic that I thought was pretty interesting was the ideal that networking to this point uh pre-sdn is just a big bag of protocols so we're not really teaching uh when you teach someone networking you're not teaching them a methodology a verse about or a uh some type of structured or layered technology but you act you're actually just teaching uh protocols so
how ospf Works how does STP work how does all these various routing protocols work versus how do you take those routing protocols extract them from the physical hardware and then allow that to be uh uh deliver a layered approach and now you have this network operating system sitting above the devices that may use these protocols to determine the shortest route or convergence or what have you but it's no longer associated with those physical devices so now just like the other part of the networking that's really
well written the uh data plane which is layer you know um which with the seven layers that can be independently programmed to or written to uh you you now have that at the uh control plane layer and network virtualization will enable that type of uh technology to to take hold and uh encourage Enterprises to be more accepting of network virtualization and sdn combined uh so that's the sdnps there's really not a whole lot more going on I've uh been pretty quiet if you noticed uh just
uh getting used to a new project uh doing a really large data center uh migration uh pretty exciting work but it's kept me busy hopefully I'll uh get a little bit more continuous on uh posting the blog post this week I actually hope to get another one in this week and uh get caught up um at least week wise versus the number of posts so thanks for listening to episode 17 of virtualized Geeks Tech talk we'll talk to you again uh later on this week thanks
