VMware Lightboards - Cloud Native Fundamentals, 16 Jul 2018

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Delivering IT Service through Clear Contracts Between IT Abstraction Layers

Description

In this lightboard session, Steve Tegeler analyzes the layers in an IT organization in the on-prem model starting at the datacenter and working up to developer abstractions, and explains the clear contracts between each of the layers.

A

Hi, my name's Steve tickler I'm, a senior director of systems, engineering and VMware's cloud native apps business unit, and this lightboard session is around clear contracts in IT, and you know the the easiest example of a clear contract is between maybe a software developer and the way a public cloud operates today in that, when they go to that public cloud, they have an API that they interact with and they know all the features and functionality that are available and meanwhile that public cloud provider can do anything under the covers to that public cloud, provided they don't mess with the contract of the consumption model of that public cloud.

A

So what I wanted to do is analyze an on-prem situation and what that looks like and really take, really go through some examples here, all the way, starting at the just the data center and working our way up, and so, if we take a look at the data center here, you know those the facilities. Folks, they're, you know they're they're, choosing various like a PC and Leibert, for you know the cooling and the racks and all sorts of things and the clear contract that they have with the physical infrastructure.

A

Folks is that they're providing them a 19-inch rack they're, providing them, maybe some sort of a specific type of power plug and then they've got some air conditioning going on in there as well right, and so they have a contract with the infrastructure team that says, here's the parameters you get to work with.

A

Meanwhile, the infrastructure team gets to go and well I'm gonna choose a Dell R 610 for my server and I'm gonna choose, let's see: EMC / Dell for my storage, I'm gonna choose Cisco for my network and maybe Palo Alto for my firewall here and so provided all those things fit in a 19-inch rack and you've got the power and cooling requirements you're good to go right. So, let's move up to virtual infrastructure, so virtual infrastructure. What is there clear contract with the physical infrastructure folks?

A

Well, for them it has to be x86 and probably on. If we're doing VMware, it needs to be on some sort of hardware qualification matrix to ensure compatibility. You need I, P connectivity and you're, probably going to need some performance from storage like I, ops, so from a performance perspective or latency to an even connectivity right. Do I need shared storage or what not. So that's that's the the type of connectivity you need, or you may specify, and that's my clear contract so with that then I can go in and I can choose.

A

Vsphere I can maybe choose just traditional data stores and I'm going to use NSX for networking and potentially I've got some integrations with NSX from a security perspective, and so, if we take a look at this very simple example, if I have clear contracts here that allows these different teams to operate independently of each other and so so take for example.

A

What if I wanted to change out my server to the next next Dell server here, like the dell 6600 all right just made that up the dell 6600 here has eight sockets and 192 gigs or terabytes of ram right. It's great I want to use it. I'm able to change to that server because I haven't changed these parameters, the x86, the IP connectivity and as long as it's on the vSphere qualification, metrics you're good to go.

A

You know, maybe I want to swap out Cisco for Arista for switching, because the wrist is going to provide the same type of IP IP connectivity to support nsx I'm good to go. Ok next piece is the developer abstractions, and this is the important one because now we're talking about what the end consumer wants, and so in this case the developer abstractions. Let's call these out, maybe it's infrastructure-as-a-service, maybe it's docker, maybe it's kubernetes, or maybe it's Cloud Foundry.

A

These are some very common abstractions that / can work on top of okay, and so, as I look at these various technologies, they all need to integrate with some sort of infrastructure, and what that means typically, is that there's usually like some sort of plug in and I'm just using generic term plug in to work with the virtual infrastructure in this case here with each one of these solutions, and the trick is I can't swap out this technology unless an adequate plug-in exists in any given developer abstraction.

A

So this can be fairly unique depending on the technology and the and the capabilities. But you know certainly some of the you know the very common ones like take cloud foundry or kubernetes. In the case of you know, we've got our PKS right, those all leverage or those to leverage a technology called Bosh, which has the ability to deploy down to the vmware software-defined data center or leverage nsx and so forth. So, finally, here these are the developer, abstractions and so now I'm starting to provide this IT service to the software developer.

A

So, what's my clear contract with the actual consumer and that clear contract is actually pretty simple, it's about providing the native API experience.

A

So if we specifically call out some of the container ones like kubernetes right, I want to be able to provide kubernetes in a native way. I want to use upstream kubernetes so that the software developer, when they're figuring out you know how to actually architect they can go to Google and they can go search and figure out how to do things and I'm, not using some proprietary version of kubernetes, which requires me to use some completely different API and it's difficult for them.

A

So my clear contract here as a software developer or with the software development team, if I'm running the developer abstractions layer, is that I provide that API experience and that could potentially give me the opportunity to you know displace, maybe and I, as maybe we're talking about OpenStack right and maybe I'm running us. You know some version of opus AK, maybe I want to provide VMware integrated OpenStack, provided that gives the same upstream experience we're good to go same with kubernetes and PKS.

A

So hopefully, this gives you kind of a good model to think about as you're as you're staring at this stack and and- and you know, some of the decisions you can make, and you can really start to understand the power of giving these teams the independent decisions to choose the technology that affects their job function.

A

Thanks for watching.