Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2018 (Copenhagen), 14 Nov 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes as an Abstraction Layer for a Connected Home - Scott Nichols, Google

Description

Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18).

Kubernetes as an Abstraction Layer for a Connected Home - Scott Nichols, Google (Intermediate Skill Level)

The home-of-the-future is vendor lock-in and disparate ecosystems that do not interconnect. Consumers are encouraged to stay within brand or risk lack of interoperability. The same can be said about Cloud Vendors. The Open Service Broker API (OSBAPI) is a standard that we can use to avoid Cloud Vendor lock-in. Can Kubernetes and OSBAPI also give us the open connected home consumers dream of? With Kubernetes used as a command and control platform for a connected home with a diverse collection of devices, complex interactions between currently incompatible devices becomes possible. With OSBAPI as the method of interoperability, it can also solve the challenge of a cloud based Kubernetes cluster controlling a on-premise Service Broker without a consistent internet connection or blocked in-bound network communication. This is going to be illuminating.

"About Scott
Scott Nichols is a Software Engineer at Google. His current focus contributing to the Open Service Broker API and Kubernetes' Service Catalog project. Scott has a passion for magic-like computer interactions."
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

Join us for KubeCon + CloudNativeCon in San Diego November 18 - 21. Learn more at https://bit.ly/2XTN3ho. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

A

Good morning,.

A

So I hope you're here to hear about home automation in kubernetes. This talk is a little bit of a lie and I'll explain why but bear with me I.

A

Joined a team inside of Google about eight months ago and their primary function is working on kubernetes, open service broker, API.

A

Kubernetes Service, Catalog and gke, and for this talk, I want to focus on open service broker and Service Catalog and I. Don't really expect everyone to know what those are, but if you do maybe a the fifth time you hear about it, might you might get it I will see.

A

We work in collaboration with a lot of partners, including Red Hat hazard, L, ASP, Cloud Foundry and a few others that are come and go. But usually these guys are the main ones and, as I was ramping up to the team, I saw a familiar pattern that these components could solve for me in a previous position and I wanted to see if I could like, if I could solve my past problems with the new tools really so I had a thought.

A

What if I, could use my home as an analogy for an on-prem deployments service, so I get kubernetes to control my home, sound premise right because well, I think it looks a lot like a hybrid solution. I think these components could solve some of the paint problems that I had in the past and if it's a little bit of fun right like who doesn't like using kubernetes to change your home home lights or whatever.

A

So this talk is that journey to see if I could solve my problem, but it's also an analogy which is the the lie part.

A

So here's what we're gonna go over today, the basic idea: what I? What I'm doing I'm gonna, give you a quick overview of OSP, API and then Service Catalog and then I want to preview. Some Google cloud platform service broker components because I use them in my solution and then we'll do a deep dive on what I actually built so I again, I wanted to use the cloud to control my lights and.

A

So why did I want to do this because I have a Raspberry Pi running at home? It does all the local calls, but I'm pretty resource constrained, and that problem is a lot like I'm an existing company and we want to. Maybe we have a seasonal workload that needs to happen, and we've heard about this new thing called kubernetes or this new thing called the cloud and well we don't want to sacrifice everything we currently have. So it looks a lot like cloud legacy to me.

A

So right, like the legacy piece is limited resources we need. We don't really want to invest locally, in maybe a seasonal thing, but we don't want to sacrifice all of our tooling that we already have so maybe kubernetes legacy would be an interesting thing.

A

But there's so there's a little bit of an issue where there's not a good way, currently well sort of in generic bland kubernetes you, you can't really map legacy stuff into kubernetes, because kubernetes really wants to manage things that it's it's actually hosting.

A

So that's where serviceworker comes in and you don't need to know what that is yet we're gonna go over it and now the problem becomes clouded broker, which is a little more manageable because user talk. So the the very general architecture that I ended up with was a gke managed, kubernetes talking with service catalog and then Service Catalog talks to a broker, and then the broker talks to my legacy code and the light.

A

So the components are Kate's which you should know about by now. It's day three of of the summit OSB API, which we're about to go over and Service Catalog, which we'll go over next.

A

So OSP API has nouns and verbs. So then the nouns here are service broker. Alright, the it's the thing you actually talked to from some platform and the broker provides a catalog which is the like the offerings, what it, what it actually can do, a service offering is a type of instance or sorry. It's a type of class of service and OSP is interesting because it doesn't really define what this means. So in my case, it could be something strange like a light.

A

A plan is a derivative of that and we'll go over this mark and then there's the the verbs and what you can actually do well. I can ask the broker hey, get the catalog or provision a thing or update or bind, and so I keep saying service broker the service broker. Is this: it's.

A

It's the way that you can, you know shim in front of something that you have that's custom, so you have to translate it into the OSP API and the broker can host it and then you can connect to it and it produces these things service instances an instance gets a parameter set and it produces the thing called a binding.

A

So you ask the broker for an instance to produce a binding and that thing comes back with a set of credentials and then that's how you use to connect to that instance that you provisioned there's two ways you can really use a service broker. There's there's this way, which is a may, be hosted black box. You, the broker, is somewhere else on the Internet.

A

You've got credentials, you talk to it and you ask, may I, please have a service and it says yes here you go it's somewhere on the internet and you don't really know, and you don't really care, because when you bind to it you get the credentials, and hopefully you have some way to network connect to it and we're working on that piece and that's coming later. Maybe the next good con, and now it's a cool solution for that. So this is like a SAS provider.

A

So if you are an existing SAS provider- and you want to plug in to provide a broker for other cloud providers to provision stuff, you you put a broker in front of your SAS interface. That's currently existing and all sudden. Now you, your OS B, API, compliant and I'll I'll, explain more what that means in a few minutes.

A

The other way people use it.

A

A

Is you launched you, you actually deploy the broker inside of kubernetes directly and then it kind of gray boxes, services back into your environment both are valid. Both are defiant like there's nothing against this setup either.

A

So, what's what's inside, of a catalog of service offerings and service plans and the service offering is kind of a template of a client's, but the definition doesn't really have to be that strict and a service plan is a variant of that service and again the definition doesn't have to be that strict.

A

So here's a result of my broker getting the catalog I'm doing curl here. So it's just rest. So it's nothing super complicated and here is how each verb interacts with that service citizens. So it creates it. It gets the credentials you can update the parameters. If the broker supports it, you can unbind, which is to delete the credentials lock it down again and then you could deep revision, which means delete the instance.

A

So I want to want to show you examples of like how we translate things between a couple. I'm gonna have a couple examples and I'll show you what this translation, so in the Google cloud platform service broker for pub/sub cloud pub/sub, they there's service offerings. So it's a topic and a plan which they didn't really use and a binding, which is a service account that gets to have rights on to that topic or a subscription to that topic.

A

And- and so you can take a look at that and then another for clout in MySQL. You know the instance is the database. The bindings is an account that goes in and has write access or heat access and I know what parameters you set and the bindings would be the that credential block that comes back and the again the verbs on how that how the OSB interacts so for my lighthouse, I decided that a service offering meant the the room that that light exists in and so in my mind, I serve a light.

A

Was a service like a thing that runs somewhere, but the plan is the type. So in my exact example, I have a bunch of rooms and then I have a colors, because I I made a cute copenhagen themed demo board, which will turn on in a couple minutes. So those are the those are the nouns. Oh sorry, sorry and a binding is the it's a credential.

A

So, in my case, it turns into a token that I'd used on the EPI, so a bit of a fennec ation, but I have abstract idli, FN, occasionally and so to provision a service class here is, is to reserve a light to bind to. It would be to get that credential and I've made a limitation where my broker the way it's implemented.

A

Is you can provision each light once and you can bind to it many times and I have a I have a manager that watches for tokens on the API and it redirects it and turns it on or off, depending on whether what the parameters came in and so the undying would be to delete that token and to D provision would be to reset the light release it.

A

So so quick service cow, like this is gonna, be super quick.

A

Feel free to ask questions sighs, so you have that service broker and it may or may not be inside of kubernetes directly and then Service Catalog is running inside of as a ape and it's part of the aggregated API, it's an API server, so it it extends kubernetes with some new nouns and verbs, the it's a. So you get some new resource types and then you can do things on those resource types that translates into OSB calls, and that's really all that Service Catalog does.

A

Is it just it Maps the imperative and s of kate's to the declarative, nosov OSP api, which is an exact match for kubernetes, but it kind of works and then the the actions of of OSB api is to. If you would like to produce a provision, you would create a service instance which is Kate's resource, and then you could change.

A

The parameters which may result in an update if that's supported and then unbind would be host to bind, would be to create a service binding on, and you give it a reference to that service instance and then to unbind into deeper version. It was need to delete those Kate's resources and those eventually trickle down and service catalogs job is to watch for changes and then translate those directly into rest calls to the broker.

A

So we just launched Google cloud platform service broker into beta a couple I think it's gonna be the last week and because I used it in the talk, I figured I'd, give you a preview of some stuff. Here's a wall of text from the blog post. You can go check that out, but basically, what it does is it provides you, the so Google GCP provides a bunch of API is that you can create stuff like pub sub cloud.

A

Spanner things like this, we have. This is what we currently support and more coming as we turn on more api's.

A

So why would you use this? It's a good question, so this is a example: deploy script in gke to deploy a simple application that provisions an instance of pub/sub provisions to it and then passes those credentials into the simple application, and let's say you run Kate's on Prem. This is the same script for doing it on Prem. So this is the benefit of SP API and Service Catalog. If you, if you tie the two together, your deployment scripts are exactly the same.

A

Assuming that you have a that same broker, inside of your kubernetes I mean, let me do it again. Watch for the change all right. It's pretty cool I! Think it's pretty cool.

A

So if you want to learn more here's the URL. This was mostly for like the print out. Okay.

A

Now that we got that out of the way we can talk about the LED house that I made I called it LED house, I didn't really feel like I wanted to bring a bunch of lamps and stuff on the stage. Cuz I was a hard percent sure that that would not work as a demo. So, okay, so again, I want to use the cloud to control my lights and we've already talked about how my lights are really OSB.

A

So it's the cloud controlling some OSB endpoint, which now is a very simple problem, because it looks like this because we have. We have the tools for service catalog service. Catalog knows how to speak. Osb api and I just have to write the the logic behind the inside of my custom broker. That speaks OSP api and.

A

Hybrid could look like this right. You've got your kate's cluster running service catalog, it talks you, a service broker talks to your legacy controller, whatever that is maybe puppet. Maybe it's a bunch of shell scripts.

A

And I thought that looked like home automation, so I figured it's a good match, so you want to see it working.

A

A

So I've got gonna, run a couple things that are local.

A

Okay and refer to my notes here so I'm going to.

A

Actually, I, okay, so the uh because we added custom columns, there's another tool called SP cat and me have heard about it. It's basically using coop cuddle, but it extends it and then makes the formatting a little different and it's going to be a plugin if the plugins story can be actually usable but I'm gonna use, SP cat directly, I'm gonna hold on gonna feed. I.

A

Think I need to ask for a fresh catalogue.

A

A

So now I can do a SP cat.

A

And I see that so this is this is SP can't get closer. The class, the the offerings and the I have two brokers installed.

A

So I have this: the GCB broker, which is a host one and I, have a broker proxy, which is actually injected inside of my Kate's cluster and I'll. Explain more about that later. So I want a provision. One of these I.

A

Want to take out so okay, this this thing is it's floors, one two, three four and then ABCD are ABC, so one AAA should be the lower corner, I'm going to take the red light, because that's the plan and then I'm gonna get a binding for it.

A

And then I'm gonna deploy this sorry. Yes,.

A

So now I have a instance of a 1 red which is class 1a, which is the room and it's a it's plan is red, alright. So but it's my abstraction and I'm going to deploy a demo.

A

And this is a little simple application that has a service. Alright, sorry, okay, I, didn't explain this, but OSP API uses overloads of the terms service, so we don't mean like a the proxy that, like the kubernetes service, it's it's actually like the app it's a little confusing.

A

A

Demo live demo. Why are you doing this to me.

B

A

Get out of there.

A

Maybe I could just apply it.

A

Okay, so that should be launching and doing its thing. We can confirm that so there's a new thing cool and then, let's see what URL it's at.

A

A

A

So it made a very simple application. Hopefully.

A

A

Now shoot: okay! Well, let's move on to the better demo.

A

I'm short on time.

A

Okay, so oh thank you.

A

So if I wanted to extend functionality, I could launch an application inside my house and then push it back up to the app that's running in in the clout. So this is the hope right, like I, extend the functionality. I can do different types of maybe I have multiple service brokers.

A

That interface to multiple devices in my house and I can pull those back up into kubernetes in the cloud and then do complex integrations there, and so I know what you're thinking it sounds like a real bad idea that connect your house to the Internet and I agree. So really you wanted this, but in reality I. Don't really want my house to be able to talk to the cloud or to the cloud to talk to my house, so I need some sort of bridge and for that I use pub/sub know.

A

So that's why I used the GCP broker to create instances of pub/sub and it connects so I and because I used, oh s, P API I actually was able to just shimmy in the broker proxy. It takes requests it bundles it up, but stomp pub/sub takes it down, makes it curl call locally and then packages the response and puts it back on pub/sub, and then the service catalog doesn't know the difference between talking to local one or talking to a hosted one. So that was neat and so I figured out.

A

I could do some pretty weird things with this thing and I open-source this it's on my github page, and if you want to see the de três, it makes a bunch of calls and then that response comes back and eventually kubernetes you can. Actually you can get the status for it so notice that the coop cuddle side doesn't have to wait for all that magic to happen and that's the ops plane and the control plane. I did the similar thing application actually just talks directly on pub/sub, so I wanted to give a cool demo.

A

Let's see if it no, no.

A

If you could do me a favor and get ready with your Twitter devices and I have to do some creating of services.

A

So what I'm doing is I'm making an instance of every light that my board has and now I'm going to make an instance of or bind to every one of those.

A

And hopefully we have a couple seconds and then I'm going to deploy this guy.

A

A

Okay, so I made a Twitter scraper.

A

Let's try it again: okay, so I think if you tweet.

A

This this format, the lights, should turn on and so that I have a you know complicated, app, complicated, app running in GCP. It talks to pub/sub down to my laptop at the conference center and it there's a arduino up here talking to the board. So did anyone? Did it turn on come on.

A

Just any way anywhere it'll watch all of Twitter. It's looking for led house exactly.

A

Did it work anyone.

A

Shoot well pretend it worked. It was great. Oh man, that's a bummer. Well live demos. So anyway, if it worked, it did work in the conference room yesterday and it turns on its cool. So maybe you see me later and I'll get it working. So there's some good yet rebo's to get you started, there's so I actually built led broker based on ofc, starter pack and OSB broker live brokered lib gives you just the hooks to implement your business logic. That's very fast.

A

It's go based and then you figure out how to get it up and running wherever that means to you. Thank you.

A

I think maybe time for a couple questions if, if you have them.

A

C

So you talked about how you might have the service running inside the cluster at the ProCare. It creates something in the cluster yeah.

A

C

A lot about operators over the last few days and why you might create an operator for Postgres or whatever yeah.

A

C

Do you think these things relate? Do you.

A

Think operator would be very similar to that thing. What operator doesn't get you is to be able to bind an external black box service from a SAS provider on the internet somewhere, so.

C

I think, like my question, is like: does this work well within operation site? Should.

A

C

Use service protocol with operators that sort of thing or is that just overkill well.

A

They just announced it a couple days ago, so I need to go back and actually like see what they open sourced. So it might be that it's a good candidate for certain types of brokers and may be an easier way to do those the the the verbs on OSP API. So it yeah it's it's interesting and we might do something with it.

A

So I don't know.

A

B

So what happens when your Twitter scraper get something that it wasn't expecting it.

A

Should just dump it okay.

B

A

Shouldn't yeah I shouldn't: do anything, did it ever work, no I, don't know, maybe I'll set it up at the Google booth. um Maybe go there after if you want to play with it. So thank you.