Red Hat OpenShift Ask an OpenShift Admin | Red Hat Livestreaming, 20 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Ask an OpenShift Admin (E76) | MicroShift in Action

Description

Operating at the Edge is a very broad topic, so we’re continuing the conversation around the Edge by bringing Henry and Diego who are both Product Managers for MicroShift to discuss and show us MicroShift in Action.

Join Andrew Sullivan and Jonathan Rickard Wednesdays at 11 a.m. ET for a full hour explicitly designed to help OpenShift admins. Each episode addresses your questions and covers the different tools that containers need to run in a cloud-native environment.

Want to learn more?
https://microshift.io

Try Red Hat OpenShift: https://red.ht/3uVxkya

Follow us:
Andrew Sullivan https://twitter.com/practicalandrew
Jonathan Rickard https://twitter.com/jrocktx1
OpenShift https://twitter.com/openshift

Subscribe to Red Hat's YouTube channel: https://www.youtube.com/redhat/?sub_confirmation=1

About Ask an OpenShift Admin:
Do you have questions? We want to answer them! Every Wednesday at 11am ET, hosts Andrew Sullivan and Jonathan Rickard sit down to answer your questions about Red Hat OpenShift.

About OpenShift:
Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment.
OpenShift on redhat.com https://red.ht/3rYz5ZS
OpenShift on GitHub https://github.com/openshift/

#RedHat #OpenShift #Kubernetes #ContainerPlatform

A

B

Let's get into the big topic of open source, something that.

A

We actually have.

C

A

Is that process.

D

Hello and welcome to this week's ask an open shift. Admin office hours live stream. I am the host andrew sullivan technical marketing manager. I guess now I'm a manager manager uh for for the stream and I am joined as always by my co-host, mr johnny ricard. How are you, sir? Hey I'm good man? How are you uh you know? I can't complain it's. um I was just giggling a little bit because I um watching that intro movie or the little thing about the live streaming. There's uh one of the little clips is of me.

D

I always think like they must have like made me look thinner or something on that thing, but either that or I've like you know, the the coveted 25 has hit me harder than I expected because yeah, but uh it's.

B

50 in itself, yeah.

D

But yeah anyways, you know it's uh it's it's mid-july, it's hot kind of everywhere. Right now, I guess at least in the northern hemisphere. um You know I, our two guests today are both over in europe uh I'll we'll introduce them in just a moment, but um yeah, it's it's hot you're in in texas, and I think it's always hot there. It's yeah, I don't know.

B

That it actually always yeah.

D

And even when it's cold, it's still just yeah, it's yeah, it's texas, anyways, exactly uh yeah! So you know summer doldrums. I was gone last week. Congratulations on the uh show it it! I didn't watch the whole thing, but what I saw was really really good. So yeah.

B

Reese is a great guest man, he he came on and uh you know just kind of took control. Let it happen, you know it's, he he's got so much good information, though so it was easy to. um You know you just ask a question: he's just got so much and he could just answer a bunch of things. So it was great to have them on.

D

Yeah yeah, I was uh you know you, and I talked beforehand of course, and I told you I'm like reese's rhys is easy. It's it's. uh You know I can say the same thing about our two guests today, right you know, y'all are easy. I don't like we don't have to like extract information from you.

D

We don't it's uh you're, happy to volunteer it so uh yeah, but yeah summer, doldrums uh last week I was in training uh crucial conversations which uh it's always fun to me to go to those things, because it's um it's manager, training right, so I'm a new manager and all that, so it was always um it's interesting to go, because it's it's reassuring right, because it gives you this framework to kind of repeatably do things that have always come intuitively as opposed to like happening on it by chance, or you know, at least for me, like I didn't know that, like I was I feel like.

D

I should have known that about my employees or how to work with my employees or something like that. Instead, it's it's been, not nothing new, nothing earth shattering. Just you know. Here's how to do that better or.

B

D

How to do that repeatedly, but uh yeah? I guess I should take a moment to mention that um we'll be off air next week, which is partially my fault and and partially the world's fault, so I'll be uh we'll be having our off-site our first face-to-face off-site. Everybody of the whole extended teams is coming together here in raleigh, so I will be unavailable for our topic next week, which it's a really important one and it's really a fun one.

D

So we wanted to make sure that we had the whole team available here and that's talking about hosted, control, planes or hypershift and will be joined by adele, so adele, who has been on the stream before yeah. He came.

B

On for um the nested.

D

Containers, yep yep or uh uh no, it wasn't nested container. It was sandbox containers. There we go. Thank you. Jesus yeah, it was gonna happen. 76 episodes in johnny we're. You know.

A

D

If we forget one or two- oh man, all right well, uh hello to our audience. Thank you, everybody for joining us today. We really appreciate it. uh You know taking time out of your day, uh so this is one of the office hours series of live streams here on red hat live streaming, which means that we are here for you. Whatever questions are on your mind, whatever things that you might uh might have that you want to ask us, that's our job here. So, regardless of the topic, feel free to ask those questions in chat.

D

We'll do our best to answer those questions. If we can't answer them here on the stream, then we'll follow up- and uh you know maybe in the next stream or via blog post or social media. Whatever that happens to be uh we're happy to get those answered for you uh if you're not watching us live. uh We know that there's a bunch of folks who watch the recorded streams on on youtube and all that other stuff feel free to reach out to us. So you can reach me via email, andrew.sullivan redhat.com.

D

You can reach us on social media practical andrew all. One word across all the various things so, whether it's twitter or reddit or al, all of that everywhere- that there is um social media, that's known to me uh and then uh of course, the same for johnny as well: uh j-o-a-n-y j-o-n-n-y!

D

If I don't mumble my words here or my look uh at redhat.com, jrocktx1.

A

We also love to hear from and- and I see regularly some folks here in chats that can stream in from the community as well. So the kubernetes.

A

um That is, you know a couple thousand folks who are all like-minded and care about what's going on in openshift and okay, so both of us participate there along.

B

With a number of others,.

B

Hey andrew, your audio is kind of going in and out sounds like you're.

A

Well, bring the microphone closer.

B

Yeah, it goes in and out. It sounds like it's kind of like a like you're in a tunnel a little bit. Okay, that's much better! Now I blame mac os there we go me too yeah, yeah yeah. It's perfectly fine, though.

D

Yeah, it's it's. Never my fault! That's that's not it! You know just like my 14 year old, it's never been called. Nothing is ever his fault, it is always someone else's fault. Yeah,.

B

And just for christians awareness, everything else was fine, it's actually just christian settings, so he just needs to. He needs to mess with his stuff.

D

It's probably that you know I saw his tweet the other day, where he's using an m1 mac to like remotely connect into linux machines. So he's turned a fancy. You know laptop into what is basically a dumb terminal right he's got like a portable vt-100 in his lap. That's all you got to do yeah perfect hardware, for it selwyn, um you know, don't don't put that evil on me. Kovid's fault uh knock on woods.

D

I'm not gonna actually knock here, because it'll reverberate through the microphone and everything. Actually, my family has uh almost entirely avoided covid. Only one of my children got it. She self-quarantined and uh the rest of us have managed so far. So, let's, let's hope that it stays that way.

B

Yeah, that's awesome.

D

Yeah yeah, uh let's see jason from full bar. Can you change cpus.cfs periodus on okd openshift? If so, where's that setting managed, um I think you probably can using something like a performance profile. um Let me share my screen here: uh share screen window oops come on quick jumping around on me. So let's share this guy.

D

I want to go to the 4.10 docs here and I want to go to the performance really. No, oh, because I misspelled it performance if we go to this performance profile and the uh performance profile um which is part of where is it down here anyway?

D

So we can use these performance profiles to set low-level things like that, so I think you probably technically can, but I would suggest, checking with your account team checking with support to make sure that it's something that is, uh if you're using openshift proper and not okd, to make sure that it is something that is supported right, because uh we we can. You know core os at the end of the day or red hat enterprise.

D

Linux, core os is called rel coreos for a reason, because it's rel, it just happens to be using our pmos tree. So you you almost certainly can change that. The question is whether or not it's something that is supported with openshift proper so and I think, is it performance profile, um performance, add-on operator, yeah. That's what I was thinking.

D

The two are related, but I was thinking the performance add-on operator which allows you to go in and make like super level. Super low level changes to all those types of things so.

D

um Let's see so I do want to get to our top of mind topics um and all of that other stuff. So uh uh chandu we'll we'll address your question here. Real quick, I think, did I miss one or do I see you app answering it johnny.

D

uh Yeah, oh, why operators fail in ipi process of installing openshift cluster on vsphere, so there could be any number of reasons for that. I'll say that the most common one is when you see like the authentication and the ingress operator fail to deploy. That's because no worker nodes are able to deploy.

D

So I'm. I call that your question specifically chandu, because um one of my top of mine topics for today is vsphere, ipi and kind of why some of the things that it does so machine api and which is really run on the control plate nodes. It needs to be able to talk to vcenter.

D

So if you have like a separate network, there's firewalls or anything like that, just make sure that those nodes can communicate with vcenter because with ipi it's the control plane machine api that will talk to vcenter to provision those worker nodes, not openshift, install openshift install, does communicate with vcenter to create the vms for bootstrap and for control plane. It also needs to communicate with the sxi hosts, because it will upload the template vm the ova directly to an esxi host, but after deployment.

D

I believe you can reclose that firewall port, if you open it up but yeah, please keep the questions coming in we'll uh we'll talk top of mind topics, while those are coming in and we'll address any questions that come up as we can.

D

uh Let's see so we talked about no stream next week, um so tomorrow, at 10 a.m. Eastern is the what's new in openshift 4.11 product management live stream, so johnny- and I will be here- I think michael foster will be here along with a number of other folks, helping to answer any questions that you all happen to have about that and anything that we can't answer. We take those and we send them over to the product management team so that they can answer them.

D

So, if you're interested in what's new in 4.11, which that should also indicate to you that 4.11 release is coming up in the not too distant future be sure to tune in john, and I will also be spending a number of episodes coming up, we haven't fully planned it out yet talking about some new features in 4.11, so we've got.

D

I don't know we're up to like four or five different things that we want to talk about now, donnie, um so we'll figure out whether or not we need like dedicated episodes for some things, or we can combine two three, four of them together and figure out how that looks, but uh yeah look forward to our what's new in 4.11 for administrators live stream. Just like we follow up all of the what's new streams with that type of information.

D

B

And thanks r hope nine for posting. The link you know for tomorrow, so it'll be good.

D

Yeah yeah, I saw our hope, nine. I saw you also posted on reddit and all that other stuff. I think I've seen you on twitter as well, so yeah we're. um Thank you for your help with all the social media. That's that's important and.

D

I'll I'll admit that uh I am johnny was laughing at me earlier, because uh we both were sending each other messages at like 10 20 this morning. Right just a few minutes before the stream. Like hey, did you do social media? Yet? No, oh okay, which one you want me to do I'll. Do the others.

D

So yeah we do appreciate the help and that's not to minimize the work that um you know. Stephanie has worked um very hard with our corporate social media teams, um as well as with the bu social media teams, um colleen, who runs the openshift twitter account and uh linkedin and all the other stuff. She does a great job too, but yeah. It's just funny to me how johnny and I are always like the laggards, and you would think that with you know, we're the hosts. We should be on top of that right. Yeah.

B

It's that celebrity mindset, you know it's it's starting to wear on us.

D

Sure that's what we'll do.

B

And so stephanie's like kicking us into shins right now, andrew, so we need to um make sure you guys like and subscribe on youtube and twitch. So that way you get the updates and um you know just make sure that you're you're doing that. So you know what's coming out and you get the the content that we're doing.

D

Yeah yeah, especially for the uh the upcoming streams we've been trying to be better about updating the streaming calendar. So if you go to red.ht stream uh that'll take you to a landing page that has a calendar, a google calendar that you can subscribe to and uh we try to update all the episodes with what the topic is. um You know it's not always do we have a lot of uh advanced planning, we'll say.

D

Sometimes we don't figure out the topic until like the day before, um but when we do know it ahead of time, we we try and do our best to update those all right. uh Let's see other top of mind topics, I think I had one more and you had a couple johnny.

D

So I wanted to note that- um and I actually saw this over on reddit um so gateway api is or has been officially released as beta in upstream kubernetes. I know we normally don't talk about upstream things. um You know it's, it will be a while before any of it is relevant to openshift and stuff like that, because you know once it hits beta is usually when we begin evaluating how to productize it.

D

How to incorporate it into openshift and all that other stuff, but this one I feel, is going to be an important one and it's a pretty significant change in how ingress and a number of other things are done. So I would definitely encourage you know. Anyone who is is interested, who cares about ingress and all that with their cluster, to start paying attention to what's going on with gateway api.

D

So I will, um let's see, let me find twitch here, so I will post this link to the kubernetes sig for gateway api into the twitch chat. So that way it gets rebroadcast across all the others, and I will also post a link to the blog post over on kubernetes.io that talks about it.

D

um So you know kind of nothing for right. Now, more of a hey heads up. This is going to be something that's big and important in the future, and I think that we should start paying attention to it and when the time is appropriate, of course, johnny and I will uh we'll dig, dig into it and dive deep.

D

um Let's see the there's. The last two things here are, I think, from you: johnny yeah,.

B

Just just updates, like I was looking out on the um the blog website this morning and I noticed that there was a blog for what's new in red hat acs, um so for all of you security-minded folks, um it's a pretty good blog, just kind of going over some of the new features that are coming out and a shameless plug for an episode that we have coming up in the first or second week of august, where we're gonna have somebody from the acs team come out and demo acs and talk about the the capabilities that are coming with that product.

B

um So just keep that in mind. If, if you, if you're, not sure what acs is it's a container scanning software, it does a lot more than I'm really doing a terrible job of you know selling this. But it's it's a um it's a very uh inclusive product that comes with red hat.

B

That's part of the the um the platform plus subscription, but just keep an eye out for that that uh stream that's coming out and check out this blog for, um for so you can see what's going on with it uh and then the other one and I'm sorry, I'm trying to talk and do things at the same time, which we know is a struggle. um The other one is uh there's a another blog on open id connect.

B

So if you watched a couple weeks ago where um we did the open id connect in the um open shift, I you know using key cloak as well as just github.

B

There's a couple blogs out there that are showing um just more detail on that and we'll have our own blog on what we did uh as well coming up. So those were the two things and the one one like thing that I just thought of, as I was looking at uh christian's uh response earlier, is that his book is is out now. So, if you, um if you're interested in learning about, I think it's called getting get ops. uh It's it's available now for download at developers.redhat.com, so go out and check that out and congratulations.

B

Christian, that's a pretty awesome achievement.

D

Yeah, I uh I think I've said before that, having having also co-authored a book before that is a uh it's quite the undertaking, um and I, while I uh looking back great rose-colored glasses and all of those other things it, um you know it's been slightly romanticized now after uh six years, seven years, um I also remember the massive amount of work that it was so congrats christian all right. uh So I I. um I realized that I kind of jumped ahead here right.

D

Normally, we um johnny and I banter a little bit and then we we introduce the topic and we introduce our guests and then we do the top of mind topics, and uh so my apologies to our guest. Today I alluded to y'all earlier, um so I'm very happy to be joined by two of the folks from my extended team, uh so henry and diego uh so I'll anri I'll ask you to introduce yourself. First thanks.

C

Andrew so I'm original, I'm a film product manager, uh we're indeed from the same extended team. I take care about all the edge and hardware enablement topics.

D

And henry and I have been working together now for like a year or so and and I I usually rely on onreef for like all of the super hards like ansible type things and he created a whole set of scripts to deploy like an open shift. All in one cluster like take a single physical node and deploy a whole bunch of you know either or I say, a whole bunch like either one single node, openshift or a full openshift cluster and like automate the deployment of odf and all this other stuff.

D

So uh andre don't understand uh I. I would encourage you not to understate the amount of effort that you put into those things and it's been super helpful.

C

Well, to be fair, I come from consulting so I I do like uh playing with labs and that kind of stuff, so yeah.

D

C

Kind of my go-to stuff.

D

Well, thank you for your help there. uh So we are also joined by diego um and henry you're in france, san diego, I believe you're in spain. So I I'm my apologies for asking you earlier like I I you know it was kind of noisy and we said. Oh, do you mind turning off the fan and then like? Oh, but it's so hot there. I feel I feel so guilty asking you to do that. Yeah.

E

Yeah no worries, you know it's difficult to work here with the windows close, but you know it's something that you need to do so yeah thanks for having us today here and let us know, let us just come here and talk about microchip. So I'm diego alvarez, I'm from spain. As you said, I'm part of the customer and film engagement team as a technical product manager, I'm focused on edge technologies.

E

um Yeah. I don't know what else to say. Well, I joined red hat six months ago, so I think I'm still brand new here in the company but yeah. I studied communications engineering here in spain too. Previously I've been working on the cyber.

B

E

Side also with identity and access management, um yeah, that's pretty much all yeah.

D

Well, uh well welcome to the stream we're happy to have you here and uh six six months in so it's still uh still a bit of a fire hose. I would imagine.

E

Yeah yeah still I'm trying to you know, learn some new things. There are a lot of different technologies products, so you know we are getting into it.

D

A

I think it took me.

D

uh The better part of a year before I really started feeling like I understood what was going on right. Oh.

C

D

Well uh so, as we kind of mentioned before- um and I think, as both of you have said, today's topic is around microshift and you know: we've talked about microchip before we had a couple of the engineering folks on.

D

I think reece talked about it last week, briefly right as kind of how it fits into the overall strategy- and I thought you know when the opportunity to have you all on to showcase this johnny, and I both, uh I think, almost literally jumped up in excitement, because it's really one of those like the the proof is in the pudding type of things. um I hope that that turn of phrase translates well. um So it's a proof of concept right.

D

It's it's a visible way that we can see exactly what we mean when we talk about microshift and how it fits in and all that other stuff. So I don't want to spoil anything here, but I know that we're you know we're going to be looking at a machine learning. I say machine learning. I don't know if it's actually machine learning or ai, but an application, that's running on an edge device using microshift, um so I'll kind of hand it over to you all from there to uh to tell us about it.

E

Okay, so yeah, actually we have prepared some slides. So if you want, I can share my screen quickly.

E

Let me know if you can see it.

E

B

E

To go okay, perfect, so well. This set of slides was presented by henry a couple of weeks ago, things on the opencv comments in london, but we can use it to illustrate what we want to say.

E

So you know the main part here will be the demonstration, but we wanted to give you some background about microsieve and why it's important in our architecture so yeah- I don't want to be here just talking. So if you want to add something or if there are some comments or whatever just raise your hand, and we will.

A

E

Okay, so um basically, I want to start talking about edge computing with opencv.

E

Well, nothing new here, basically, opencv is about delivering applications anywhere and when we talk about anywhere also, we are talking about edge, so it was built on top of three main pillars, and one of them was consistency for id or developer teams. You know they have their existing architecture and they want to scale it. So it's quite easy with openshift.

E

Also another one is flexibility. um When we are talking about it, sometimes it's difficult to give an specific definition for it. So, for example, it's could be different from one customer to another from one person to another one, so we needed something that gives our users the flexibility to choose what they want and well, as you can see, the third one is choice.

E

uh Here we want to give the opportunity to choose on what red hat our partner ecosystem, which product or technology, works better for deploying applications, so yeah, nothing new here, I don't know if you have any questions.

D

I, like that, you pointed out there that edge can be many different things. um You know I've worked for organizations before where there was kind of a central location. That was, you know the the the core right, the data center and then everything else they considered the edge.

D

Even though, in some cases those edge sites were as large or larger from a compute and resource perspective than that core data center, and then, of course, you know it went all the way out to like you know, in vehicle things and stuff, like that, you know that were truly you know remote disconnected edge type of things so edge doesn't have to be. You know, ultra small, disconnected you know type of scenarios. It can be a whole lot of different things.

E

Yeah exactly it could be whatever you want to compute some data. You don't want to send it to your central core uh cluster, so yeah everything that is you know, processing data on the field could be its devices.

C

E

So well here I saw last episode and I think that rhys oxerham was talking about the opencv architecture for the edge, so we can skip this part really quickly. So we have three different options depending on the use case. One of them is a single node edge servers that gives you a really low bandwidth and works pretty well with disconnected sites. So here what I, what we are doing is just deploying a single node on the far edge with both control and worker capabilities.

E

At the same time, um another option also is a remote worker node, so it works on environments that are very space constrained constrained, and so here we are deploying a work node, but it's managed from the regional data center and the last one is the three node cluster which give us the most similar experience that we could have with uh opencv on traditional architecture.

E

But here we have three different nodes, uh also with control and work capabilities and yeah. That gives you a.

B

E

Availability, while we are keeping in mind that we need to reduce the footprint, because we are talking about edge devices which typically are low in resources,.

D

So I want to pause there um if you'll go back for just a second, and I know this is one of the core topics or core principles from last week, which is kind of all of these edge architectures. All of these edge things um so kind of ranging from- um and I think what's missing here is the very top and the very bottom so very top being micro shift, and I think it's it's missing because well it's not a red hat product right. It's still. It's still an open source project.

D

It's still community project, it's just one that is really interesting and you're, seeing a lot of activity from us around and then at the very bottom right. It's just a regular cluster. You know, there's three node clusters and then there's the five plus node clusters that exist inside of there.

B

D

Selwyn had a question a little bit earlier that I wanted to because remote worker knows is on the screen. I'll take the opportunity to talk about it. I was asking about some best practices or some other documentation around remote worker nodes. um So I don't know that there has been anything published on the blog um johnny. I don't know if you know of anything off the top of your head. I don't know.

B

I think, and I'm asking back.

D

Channel too so, okay, no, I'm not aware um so yeah. Generally speaking, those you know, practices or anything like that are going to be dependent on your application. So, for example, you say here that uh you know details on how to keep the vip traffic routing correctly. In case the route site loses network connectivity.

D

So it's going to depend on a number of things, one being what's hosting each one of those right. If it's in a hyperscaler does that hyperscaler have something like a global load balancer that can simply redirect to one of the other quote. Unquote remote sites is, it are those ingress controllers? Are they hosted in the same location as the control plane, which means that you know there can be other bigger problems that are happening there.

D

At the same time, it could be solved other ways so, for example, having a sharded or a a sharded ingress or multiple ingresses, with different ones hosted at each one of those remote sites. So there's a number of different ways. You can address that. I wouldn't say any one of them is better or worse than the other. It just depends and we'll see if we can dig up some information on that. So sorry to uh interrupt you today, yeah.

E

What is, though, so well here we have at the right side what you were talking about: the typical data center.

E

So here we are trying to map all these architectures into our different h, edge, tiers that we have so we're, starting on the right side, with the code data center, with five four plus opencv nodes down to the edge server. So, basically, on this range you can use different architectures for openshift, even on the edge server. We could have maybe a single node, openshift or remote working on. But the problem here is what happens when uh we have smaller devices.

E

For example, we have another two at tiers, the edge gateway and the edge endpoint, for example, the edge gateway. We could have a remote worker node, but at the edge endpoint we have really little of tiny devices. So we have to provide a solution for that here. We have some examples of those really small devices. For example, we have uh imx, we have jetson and on the right side you have interneuk.

E

So what solution we provide for all them and we are providing rel forage so yeah red flags- is the operating system for the enterprise edge. um Among some other benefits. I highlighted four of them, so the first one, if this quick image generation, where basically you are using image builder tools for building your own operating system, built on purpose for your architectural challenge that you're facing on the edge another one could be, of course, management at the edge in a secure way. We have zero touch provisioning.

E

We have also a fido that I'm going to talk about it later and at the bottom you can see uh efficient over there updates and intelligent products. This is uh an advantages that came from using rpm ostrich, so it's way easier to perform um an upgrade or a rollback if something's going wrong so.

D

Yeah, so can you can you talk about any of the differences between rel for edge and rel core os.

E

Well, I don't know exactly, maybe I cannot give you a answer for that. So I don't know if henry have some background.

D

I mean I, I can talk at a high level about it, but it would be. It would be interesting to know um some more, maybe johnny, maybe you and I can follow up on that. um If.

B

D

Where um so one- and I I think the important thing to note is so rail for edge- is rel like rail, rail, it is managed it is deployed as using rpm os tree, which sounds and looks and tastes a lot like how core os is managed right.

D

I think the biggest difference is that core os everything is a container right. Basically, it is only the what what is managed as a part of that base operating system through rpmo. History is only enough to get like kublet, and you know creo and container d and or cryo everybody always corrects me to cryo. I don't know why, um basically only enough to get containers running and then literally, everything is a container inside of that operating system well for edge. You can certainly do that through something like podman and creating.

D

You know, systemd units to start containers and stuff like that, but that it's not intended to be. You know done like that. um You know it's more like a traditional rel operating system. You know you need to install packages, you install them into the rpm os tree layer and then you can deploy it out to that, using whatever tools are available to you.

D

I'll also add that- and I think we'll probably talk about this more in a moment. The management principles are different right, rel for edge. You know you use the the fleet management tools, use, ansible, automation platform. You use all those types of things to manage it in kind of a very close to traditional rail type of method, whereas core os, you know rel core os, is only available through openshift and it is intended to be managed through openshift, using machine config operator and all of the other mechanisms inside of there.

E

Okay, yeah thanks for the information because I didn't know exactly the difference so yeah that was useful, so I mentioned rpm o3, so rpm, mostly it's inside real, for it is not something new. We already implemented it a long time ago we even before core os, so I think it was with with a atomic operating system. I think so so. Basically, here we have a operating system based on immutable, binaries.

A

E

So it's also based on transactional updates from a to b, which means that if you want to perform an upgrade, you need to make it in one single step altogether. So it makes everything more easy.

E

Also we don't have in-between state and during the update, this means that you can, for example, perform an upgrade in the background, and then you can apply it just rebooting, node and also another good thing is that now migrations from rail 8 to 9 are supposed a support and it enables seamless major release, upgrades and rollbacks, and the last thing that I want to show you is fido device, onboarding, also known as fdo.

E

We were talking about it when I said that we can manage everything at the edge, so this solves the problem of late binding device uh to your edge platform.

E

Basically, you have zero touch provisioning by deploying devices on your factory plan, then you can pre-configure everything ship them into the ads and just plug into your management platform and it works. So this was implemented in well 8.6 and also is available, of course, in 129.

E

And here I wanted to just summarize what I've been talking. uh Of course, this slide is quite.

B

E

The one that I saw at the beginning- but if you see at the top we have added the small footprint it's operating system, that's run for it, so it works for memory, constrain servers and just needs one core and two gifs. So if we compare it to the smallest one that we had before, which was the remote working on with two cores and eight gigs, so yeah quite low the requirement for that, uh but maybe you're asking. Where is microsoft here?

E

You asked that before so that's why we are here, because maybe we could have a remote worker node on the edge, but we don't have the connectivity to the data center. Another option could be using single node, but or devices are not enough talking about hardware resources.

E

So that's when we wanted to take openc further into the edge with microchip.

E

So yeah I don't know, do you have any question on the chat? Maybe.

D

No, I don't. um Let's see english asked about uh two node cluster, which we answered in chat. um So short version is on the roadmap. There is uh going to be a uh the opportunity to take a single node openshift, which is a one node control, plane and worker and then add additional worker nodes, but it would still be a single control, plane node with additional work nodes, but there is no intention, as far as I'm aware, to have like a a cluster that has two control plane nodes, because fcd just wouldn't function right.

D

It can't establish quorum.

E

Okay, so henry do you want to continue with talking.

A

C

E

C

Sure so, basically, this is where red dots emerging technology comes into play. uh So reddit, emerging technologies is part of our office of cto they're working on technologies that are still taking shape in the enterprise or research communities.

C

You can find all their projects on next.freddah.com all the work they do is completely upstream and community based they often work on existing community projects. They also often create their own, which are made available on their public github, not.

B

Everything they do is.

C

Followed by products there's actually quite a lot of things, they've been working on that never uh never happened as products. They have also multiple areas of focus, as you can see. So this.

B

C

Edge security data and ai quantum computing, even all kind of stuff, next slide. Please.

D

All I'm hearing is open shift on quantum computers. What.

C

Well, that should come pretty sooner than later,.

D

I I thought I remember somebody talking about, um I think it was ibm had like a api where you could reach out and, and you know, make requests schedule things on quantum computers and somebody was like. Oh we've is there an operator for that? No.

C

Not yet, but hopefully we will get there at some point.

C

So what exactly is microshifts microshift is an experimental flavor of openshift, that's optimized for the device edge. It's basically openshift, not just fodmap, running on realforage. That provides you with standardization of for your software lifecycle, uh consistency for your devops across all your footprints, uh and it can be, of course, managed.

B

Brain orchestrators.

C

Such as open cluster management or advanced voice, it's.

A

C

To leverage uh natural optimized linux os, so all the advantages that diego just talked about, uh it is uh meant to be using fido device onboarding to be configured and set up with zero touch provisioning. It's meant to use the rpm os 3 transactional, updates model.

C

It is distributed as a single binary that can be deployed either as a package or as a container on your existing container devices, basically container running devices, uh so it allows you to make fully customizable os image uh already embedding your microchip.

C

It really aims for a very low resource, some footprint. uh It basically takes for two cores and two gigs of ram as a minimum for your devices. It does support currently both amd 64 and arm 64, but it can easily be extended to risk or other kind of devices.

C

It's very uh small in terms of payload, so you don't have much to download or update over the wire and it got very low storage requirements uh right now. I believe it's in the four gigs.

D

Space, so a couple of things here um so is the best way to describe microshift something like kind right, kubernetes in docker, where it provides the kubernetes api as a container image. That is then run inside of docker, so it it looks like sorry for banging the microphone. You know it it. It would be the same or similar to deploying you know, kubelet and all those components directly on the operating system, but instead they're in containers, or is this different than that.

C

Well, it kind of provides.

D

C

Option to run like a kid would because, well you can have it as a container that you then run with privileges and then you can manage your cryo, etc.

C

We also have the option to have it as a binary. So then you don't have to have a privilege enabled container running there.

D

And I also I always like to point out that micro shift isn't open shift. It is, but it isn't right in that and the reason why we don't call it micro open shift or anything like that is because it doesn't have the full set of things that make open shift openshift. So, for example, there's no olm yeah.

C

Okay, so that's where I was coming actually with my next slide: what actually differs uh between openshift and microchip.

D

C

Is really meant to run on cloud providers bare metal vms, you name it, but it really needs to be able to have some control over both the operating system, which is real core os and the underlying hardware.

C

So this is basically provided by cluster operators that we decided to tear down from microshift because hey we don't need to manage the underlying systems, because that will make it well. First, we are using small devices there into the edge. We don't have any bmc. We don't have stuff to manage there per se. So there's no.

A

C

In having to use cluster operators that takes a lot of memory, etc, when you don't have anything to give them to manage, uh also you don't obviously you're, not we don't see microchips as something that you would go and install on aws, azure, etc. It's really.

A

C

For small edge devices, so yeah nothing really to manage. Also those edge devices usually need to have very specific driver sets which makes it pretty difficult to have them integrated with real core s, because you then need to modify too much of the underlying operating system for it to really stay manageable by openshift.

C

So again, no point in having a core os that we would manage with cluster operators. So.

B

Microshift really is just.

C

The kubernetes components that you need at minimal to have a kubernetes cluster, basically well, a onenote cluster.

D

And we we've got a couple: questions go ahead: johnny yeah.

B

I was just going to say the same thing, um so jason from fullbore asks is: um are microsoft are microshift nodes under the control of a normal openshift cluster, or are they separate cluster managed by acm.

C

So they would in this case be separate clusters, because if you have several nodes, then you have several clusters and you would of course be able to manage the workloads with acm.

B

But you don't necessarily have to have acm to manage that cluster right, like microsoft, could be completely independent, then, on its own right, yeah.

C

It can be completely independent and managed as any kubernetes cluster. Basically.

B

Awesome and then christian says that he wants a multi-cluster micro shift.

C

Well, that might happen someday, but right now.

D

Christian, I know you've already gone through the pain of deploying olm on microshift, so I'm I'm expecting a pull to see a pull request for multi-cluster from you anytime. Indeed, and uh dwayne also asks about any compliance needs for micro shifts.

C

uh I don't get the question.

D

I think and dwayne please feel free to correct or clarify. um I I think you're asking whether or not there is specific compliance requirements or compliance needs associated with microshift um or maybe even compliance profiles.

D

My interpretation is that this is the way that it's done today is it's going back to the openshift 3 model of you're managing the operating system independently of the kubernetes on top of it. So you would apply, you know, hardening rules and all those things for whatever your compliance standards are to rail for edge and then, if you need to further, you know harden the the kubernetes micro shift. On top of that, then you would take actions at that level, but I don't think oh yeah, you clarified their profiles.

D

Yes, so I I don't think we've published, I mean it's not a it's, not a product, yet it's still a project. So there's nothing like compliance um operator or stuff like that, that's available for it. Yeah.

C

I'm not that different.

D

Yeah does microshift need two cores for far edge with worker plus control plane reduced number of required cores. um I thought we.

C

A

C

Requirement for running microshift so that embeds the of course, worker and master which are running on the same note.

C

D

Yeah mark, uh thank you for the help mark rail compliance would follow. Microshifts yeah. That was kind of my thought as well as that would be done at the rail level or uh well for edge and to be clear, you don't have to use rail for edge with micro shift. You can use regular rail rail not for edge rail for data centers. No, let's not go back. There.

C

Actually, right now, with microchip doing a community project, you can pretty much use any flavor of linux. uh I myself during the demo, that's gonna follow um using the nvidia linux distribution that comes with the jetson, because that's the only way to get 3d acceleration.

A

D

Nice I'm. uh I wish I had a couple of jetsons in my home lab myself, but all right I'll, stop interrupting you um for any of anybody in our audience. Please keep asking questions we'll uh we're happy to answer those. Yes,.

C

Please do so. What does microshift do also is enabling flexible usage models where you can either have your os system, image with, which would be embedding microshift and your operating system, uh which would be connected to the network. So you can then talk with device management software and have an application.

B

Management software.

C

As well, that would then point it to the kubernetes applications to run, or you can have a model fully. That's fully disconnected where you have your usb key. Embedding your operating system micro shift all your kubernetes application that needs to run, and then you can send updates to the factory in the form of usb keys that would be plugged and perform the update of both the operating system and potentially applications.

C

So this microchip project, actually our friends in ibm, liked it so much that they didn't decided to send it into space. I believe we did. These have been presented many times already to you guys but yeah. This is the endurance project. uh You're welcome to go and register. uh I don't know.

B

C

Plan to open it to others, then educational purpose at some point, but you never know.

C

A

C

Time so let me share my screen.

C

So this is my little jason uh running it so right now I only have the card microchip treading.

C

C

Hope everyone can read correctly yeah. That looks good. Thank you.

C

So this is just plain microshift going to start some opencv workload there. uh So computer vision, I'm using small cameras, very tiny one esp32 type.

C

So first I am gonna start my wifi server, because I need to connect this camps to my cluster.

C

C

Let's also have a look at the camera connecting that just to make sure everything works before we start the rest.

B

A

B

Of json, are you using are using a nano or using one of the the more higher end.

C

Well, I got the irm agx, but this would work on the nato as well nano and nx as well awesome. This is actually all available on the emerging tech guitar. You can find the whole demo, which is ai4h microchip demo.

C

It's all there for you to try if you want- and there are even bits to make it work on your raspberry pi. Actually, if you don't have a jet.

C

So now we have our camera connected. Let's apply the computer vision server because we want to do something with these pictures oops taking too fast.

C

So here we should see the camera registering.

C

Oh no, I need to expose it first.

B

And for those that can't see behind our our beautiful faces, uh he's just running oc exposed on the service to make sure that the route's populated so.

C

So now we did create the root service and now actually our camera should register.

C

So now we can see the camera is being registered.

C

And we can grab a browser window.

C

That should no be getting our camera feed and, as you can see, you know recognize me.

C

It could actually well, I don't see your faces anymore. How can I recognize you.

D

It's uh oh stephanie, can you can you turn back on our images on the uh on the side, because I I said on social media that uh johnny and I provided our our images. So, let's see if we break the model, yeah.

C

Oh, that's a bit small.

E

D

Here it is so uh o ob, o o um your question. There uh would you mind issuing an oc co um so that actually won't return anything because there are no cluster operators. Hey it recognizes me. um So there is no operator lifecycle manager. There is no cvo, that's deployed or cluster version operator, that's deployed with microshift. So all of those operators that show up with oc get co are the ones that are managed by cluster version operator and since there's no cvo with microshift, therefore those those don't show up.

D

I don't think that's the already even exists.

C

That's it. The the resource, the resource type, doesn't even exist.

D

um Let's see srikanth, uh if there are any upgrades to binary, then do we need to wire the whole binary to edge devices. um Maybe so I think in this instance the application is deployed as a pod. um I don't want to speak for you andrei or or diego. So in that instance, you would be. When you go to update the application, you would be pulling down a new container image and whatever is inside of here, but.

C

In my case, I'm using the binary version, so basically the binary itself, as you can see, is only 144. So that's what you would need to update. It will, of course uh you he will download.

C

Well, actually, no, it won't download anything. This binary can work offline so so.

D

It's not so big, so yes, maybe I I think it's nice.

C

But I believe that there should be a way to actually update the the image of all the the parts in individually.

C

I don't know that it's currently, but although.

D

Yeah this, um I I think we're going to see some more about how to manage. You know rail for edge devices, micro shifts and the the applications and services that are running in there coming out of you know. Various teams inside of red hat as time goes on, um especially for you know, as we get more comfortable more familiar with how to do this, for you know very remote, very low bandwidth type of scenarios.

D

um You know to your point: 144 megabytes isn't a lot unless you're on, like a satellite link, you know and you're you're getting. You know, dial-up speeds because it's you know, that's that's reality in some places, um I'm thinking of uh like cruise ships or or you know other other things out at sea, where you have very little bandwidth and you still want to be able to do those indeed,.

C

And that's also, where the possibility to have it fully disconnected and managed by an rpm os3 that we can have on a usb key or sd card, or whatever makes it also convenient for those kind of use cases I mean if.

B

You can send someone with.

C

Like a small sd card or sending by by post or whatever, then you you can sort those issues as well, uh but yeah they will need to be a mean to get. This android makes that.

D

Yeah, the the ansible team, uh ansel automation team had a really cool demo that I saw recently where that's kind of what they're doing they're they're using openshift in a full deployment to do app, dev and sort of outer loop activities right basically generate a container image with the application, and then they take that and stick it on.

D

A thumb drive that that container image and then they take it out to one of those locations and it uses ansible automation platform to go through, and you know, push configuration updates and platform updates and application updates out to all of those nodes and the tech doesn't have to really do anything right. They plug it in they start the interface for ansible automation, platform. They click the task and you know, go get a coffee for 20 minutes, come back, pull the thumb, drive and move on to the next one.

C

Yeah and that's exactly what we're having further yeah.

D

All right, so this has been like fascinating to me. um It's always. It's always always always interesting to me to see these different kinds of use cases- and I know we've had um you know on the marketing side of things, because for a long time I have technically had marketing in my title. So I try and stay aware of what's going on right.

A

D

Got a lot of like industrial edge and stuff like that, um you know, use cases that we've talked about and johnny there's. Even um isn't there a validated pattern that uses something like this to do: image recognition for um different things, yeah.

B

Yeah there is it's: uh we've done one for medical diagnosis, which is doing uh object, detection for pneumonia uh we've done industrial edge, which is like sensor, monitoring and stuff like that, so um uh yeah there's a bunch of people. That's! I was super amped when, when you're talking about uh coming on and doing this, this is awesome.

D

Yeah and I'm thinking of all the ways that we're you know we're effectively modernizing application, not just deployment but development in many cases, and that's really cool to me. So this has been really enlightening to me um for audience. It is a little bit after the top of the hour.

D

I want to be respectful of diego and henry who are in in europe, and it is both the uh the end of their day, we're standing between them and and dinner, or maybe a pre-dinner beverage um and as well as uh it's hot, and I don't want you all to be cooped up no longer necessarily getting some.

C

D

Have a uh a lemonade or something like that, I won't make any you know us. Americans, love to have, you know, be stereotypical about europeans and ice, like americans love ice and our drinks and europeans- it's not very common. You know I, I won't be stereotypical.

B

If I could, I would like to ask one question about the application if you could give like a 30. Second like hey, this is what it is and mainly like. We talked about it a little bit yesterday and you're saying it's it's based off of like uh uh clear vision. Right can.

B

Can you kind of give like the the elevator pitch of like what the app is on the back, I mean, obviously it's doing image recognition through the camera and stuff like that, but like how is it how's that output together, like how's the modeling working? How are you doing all the training? If you can do that, that's right, I'm trying to have you do it quickly, but.

C

Well, let me share my screen again then it is, I mean it is really uh using some samples of uh computer vision in python.

B

It is version sorry yeah.

C

So most of the the logic actually all of the logic is just there uh so.

B

C

First step where we do basically fit it with uh the pictures to teach him to recognize different people, and then we have yeah just a little bit of code. First, we resize the picture because well even with gpu acceleration.

C

Treating full-size pictures is a bit too much for this kind of smaller devices. Also, we wanted to have it working potentially with raspberry pi with that acceleration.

C

So here we have the so cnn basically tells it to use the hardware accelerated version of the face location um from opencv and we're just basically using basic opencv methods there to try and recognize.

A

There is a face fair.

C

First then match it against the faces. We know, and then we do add the small name box.

C

The other components of that are basically the wi-fi access points that will provide um that that will provide first and last ap configuration basically and that way that will push some information uh into mdns to the camera, to provide it to a point where to register and there's.

B

The third component.

C

Which is some code running on the camera itself, because that's esp32.

C

So this is responsible for basically telling the camera that it needs to connect to connect to the micro shift cam server using the the information it will be getting from the the wi-fi ap server and that's pretty.

B

Much it awesome yeah. The reason why I wanted you to kind of like walk through it, because I think it's important for people to understand like this. What you've done is you've done. One model, that's doing image, recognition on faces and pictures right, but then, if you think about it, you've got a camera hooked up, so you could have a camera hooked up outside of your door and looking for wildlife or looking for certain things right. So there's there's all these things that you can do that.

B

Don't necessarily have to be like facial recognition, but they could be object. Detection or um you know something else right, and then you can stream that in and you can put your model and you can train your model and then use a tool like microshift at the far edge to kind of like execute that model and then essentially report back and then retrain. So there's this like whole workflow between openshift at the data center and then microshift at the edge that you can.

B

Actually, you can have implemented and then have just like this nice continuous loop of you know the model being deployed and then the model being trained and then you know ultimately fed back into the the edge. So I think it's really awesome what you guys are doing with this. This is insane.

C

Yeah guys, you need quite a good example of using the camera, which is basically an iot device that you can program as you will uh to just send pictures. I I could also do some transformations directly on the camera if we wanted to like turning the image around left or right or upside.

C

If your camera is positioned in a non-standard way, uh there's and yeah.

B

That that's basically.

C

Proper edge scenario, where you have these edge devices, that's providing connectivity to your iot device, getting data from it, processing the data locally, and then you can do whatever you want with the data.

B

C

This this is exciting. It.

B

Really is it's because we're now we're opening the can right, so we've had these ideas for a long time of, like man, it'd be sure would be cool. If I could do this, you know and and now we're getting that capability and we're able to put it in people's hands, and I I think that it's this is just going to be awesome.

B

I think that the doors that are opening with microsoft, I'm really high on microsoft, by the way, if you can't tell like I I'm I'm super excited about this um but yeah, I I think the doors that are opening with this are going to be it's going to be awesome and the tech that's going to come out is just going to be incredible. To see yeah.

D

Duane asks about uh whether it can be done on a raspberry, pi and uh yeah. My microchips will run on a raspberry pi. um I don't know about the machine learning part, because there's no uh acceleration like with the gpu.

C

So this demo does work on a raspberry pi. It is a bit slow. I mean you, you wouldn't get as many frames per second that I could just get with the jetson using gpu, uh but it does work uh and it does work pretty well actually.

D

Yeah, I'm curious um or well, you can do micro shifts on you know raspberry, pi's and stuff like that. Usually, when folks ask about that at least on our stream, it's usually because well, I want to learn openshift right. I want to be an open shift administrator and the microshift admin experience is I'll just say nothing like openshift, proper yeah. So just a fair warning there, it's not to say it's not worth learning how to do like. You know, rel rail, for edge management.

D

um You know getting familiar with ansible automation platform, you know microshift and acm and how all that works together. um You know there's tons of stuff to learn there. It's just it's not open shift openshift. So you know.

C

Furnace, it is still kubernetes so that there's still some stuff to be learned. This way.

D

Yeah, that's absolutely.

B

True yeah, if you're fundamentals right, if you're trying to get your baseline like your deployments and you know all that stuff, then yeah definitely but like andrew. I get exactly where you're coming from right. If you're trying to learn like how to deploy operators and stuff like that, probably not the tool you want to use.

D

So, uh just a few minutes left again, I want to be respectful of diego and henry's time, so any questions that you'll have out the audience. Please feel free to send those in we'll do our best to address them. uh If anything comes up afterwards, if we missed your question, we didn't answer your question well enough. If uh again, if you're not watching us live and something comes to mind, don't hesitate to reach out. So if you're on youtube or one of those, you can always leave us a comment. I now have a little script.

D

That runs a couple of times a day. That tells me when new comments appear so don't hesitate to leave comments there and we'll do our best to answer those or you can always connect with us via email, andrew.sullivan, redhat.com or johnny, j-o-n-n-y, redhat.com and, of course, social media. So at practicalandrew on twitter, on reddit, on all those and at jrocktx1 for johnny and last but not least, uh the slack team.

D

So I've I've been trying to get better about encouraging folks to go over to the kubernetes slack channel and look for openshift users over there, because that that community really is great and um it's not just johnny, and I right there's a ton of folks over there who are willing to help not just with upstream okd but also with uh or upstream okd and kubernetes, but also with openshift as a whole, so don't be afraid to take advantage of all of those tools.

D

uh With that being said, um if you haven't um and if just a gentle reminder please subscribe to the channel, um it's a great way to stay in touch and be aware of what it is that we're going to be talking about and win as well as uh some other things that hap that are happening across live streaming, so get ops, guide to the galaxy and the level up hour and uh well, the what's new and what's next right, the uh the new, the what's happening and the roadmap presentations for openshift are all broadcast through there.

D

So and I don't see any other chat coming in so um yeah. That's all I got johnny uh or excuse me, uh diego, I'm I'm saying diego and looking at johnny. So that's why my brain didn't agree. um So uh diego henry, thank you so much for joining us today. um You know we really appreciate it. This has been just absolutely fascinating, like johnny said, I'm a fan of microshift and all the possibilities that are going on there and I'm constantly learning about it as well.

D

So this has been really helpful for me to really see an implementation to see what it looks like and see how we can take advantage of all those things. So thank you again for joining us. We really do appreciate it.

C

Thanks a lot for having us giving us the opportunity.

D

Yeah, thank you as always. Thank you in the background for stephanie, for all of your help and keeping us organized keeping us on task and on targets and johnny. uh Thank you thank you for joining me every week and and for covering for me when I'm gone, uh yeah man. So with that I'll uh I'll leave you with last words, johnny.

B

Yeah, so just uh don't know what you said about stephanie stephanie: we you know you make that you make us awesome, uh but I also want to say thanks to rhys too, for you know actually positioning uh diego and andre for us, because uh you know reese kind of approached us and was like hey. You guys got to listen to this and it's I'm so glad that he did because this was. This was great. um I am super excited with the andrew.

B

I think that, like I said once, I think once microsoft gets out there and people start using it, like the doors are just gonna open up and there's gonna be some cool tech that comes out of this. So thanks again guys for coming on. This is really awesome and I'm gonna try and get my nano out of the box and install micro shift on it.

D

All right: well, we will see you all in two weeks, but don't forget that tomorrow is the what's new in openshift 4.11 live stream at 10 a.m. Eastern.

A

A