Red Hat OpenShift APAC Hybrid Cloud Kopi Hour, 29 Jun 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: APAC Hybrid Cloud Kopi Hour | Validated Patterns: Going Beyond Reference Architectures

Description

Validated patterns are used by architects and developers to bring together products across the Red Hat portfolio in a specific use case that is tested and maintained across the product lifecycle. They are continuously tested, GitOps-driven, open source, repeatable, cross-vertical solutions that embrace cloud-native applications strategies while remaining intelligent business-centric solutions.

But how exactly is this done? How is a Validated Pattern created, used, and maintained? Come join us for the next APAC Hybrid Cloud Kopi Hour where we will sit down with Red Hat Senior Software Engineering Manager Andrew Beekhof and explore the world of Red Hat’s Validated Patterns!

A

A

A

Hybrid Cloud copy hour, uh yep we're back. uh It's been a little while since we've been uh online, uh but that's fine, so we're here now and excited to have a brand new guest and a new show, but first up a quick reminder. What we're talking about when we say Kopi Kopi is a beverage that's very common in in Asia and Southeast, Asia and Singapore. So uh just so, there's no confusion. We always do that.

A

uh As a reminder, my name is August simonelli I'm, a technical marketing manager here at Red Hat based in Sydney in Australia and as always I'm uh joined by my favorite co-host Dev shanbach Dev. How are you today.

B

I'm very August, thanks for asking I'm, really interested to hear what Andrew has to share today, um working with our customers in the region, specifically focusing on Consulting. We take a lot of what reference architectures, provide us and then work with our customers discuss what their specific needs are, and then you know craft something that they want and speaking with Andrew, there are certain things that you know specific and you know certain prescriptive things that we can use the validated patterns so really interested you here.

B

uh What Andrew has to share with us so really excited absolutely.

A

um So speaking of Andrew, hi Andrew welcome to the show uh hi put your details up, go ahead and introduce yourself tell us uh who you are and where you are in the world.

C

uh I'm Andrew breakoff I'm, a senior engineering manager in the ecosystem engineering team under each month, and we I work on validated patterns too um I'm based in Melbourne. The team is mostly in the US in uh Amir, but uh I I, look after them from here nice.

A

All right, so the topic today is uh I. Think what do we call it uh validated uh sorry um validated patterns going Beyond reference architecture so where I actually want to start with this before we jump straight into validated patterns, is what we're actually going beyond the reference architectures. So I wanted to share with you Andrew a little story. A little history of mine back in the day, I was uh back when I started Red Hat.

A

Over 10 years ago, I was um sent to a large Australian customer to install openstack, uh so a 10 years in openstack. So you know what that meant. It was utter. Chaos and I had nothing to go by. So I was given a reference architecture by I. Think some engineering team and we struggled through it and we got there and it came together and so I was sort of introduced to the power of reference architectures. It's not this one, but it was one where we did some crazy stuff.

A

We were, um we were even um uh using a thing called packstack for those of you who know openstack. You might remember it. It was very early on, as things evolved and and the industry got more intelligent or smart or whatever you want to say. You know, reference architecture has evolved. I even remember my first experience with the red hat team, who would write these reference? Architectures I think it was at uh I'd, have been a red hat Summit in 2012 before I even joined red hat, and they were a great group.

A

So eventually, I knew one day I'd get to write my very own reference architecture, which we're probably going to rubbish the heck out of today, but I I, don't know so. I wound up writing this. What I uh I did uh openshift on openstack and we wrote a very traditional reference architecture. So I worked, you know quite closely with the engineering team and the um marketing team and the product teams, and we came up with this. This document right so and went through all the details.

A

uh We explained the use cases and and why we needed a reference architecture and we had a great diagram. We set out this thing in stone of of how reference architectures and how a customer should deploy these very, very complicated Solutions, and that was my world of reference architectures and and to me that still exists. So the question becomes- and you know this is a reference architecture. What, then, is a validated pattern?

A

How are we moving beyond that and and before we throw it to Andrew I'm curious Dev, you know you're working with customers every day. Are they seeing documents like this exceptional reference architecture that I wrote two years ago and, and you know how are they exploring the space um and then we we go to Andrew I'll. Take this off the screen, but yeah so I.

B

Think um I do remember going through this particular reference architecture that you showed August. uh It was a good starting point and I think our customers really liked it because you know, like you said you know, openstack and openshift on openstack. At the time there was very little out there to look out for in terms of hey.

B

Where do we really start right and now fast forward today, there's so much out there, where you know guys um really a lot of knowledge out there, but you know in terms of wisdom, you know they try to bring in specialists in terms of okay. Take this and make this make it into something that is usable, um I, think our customers find Value in different approaches, but they want something specific as well.

B

So that's what a lot of customers ask as well in terms of okay, we've seen this, but what do you think about this particular problem? How is this solved so these? uh The questions today that we come up with are very specific from our benefits.

A

Right and probably more Dynamic right, so our reference architecture that was it didn't, have code it didn't have. It was very much a I I did the first version did have cut and paste. You could do implementation details, but it was very much. This is how what.

B

A

Yeah so Andrew, if we're looking at something like a validated pattern, it's just a reference architecture. Isn't it I mean come on? What's the difference, so maybe maybe give us a little introduction into what they actually are. Obviously, yeah.

C

So I mean reference. Architectures are great tool, I've been popular for many years for for a good reason. You know they're good at sparking an initial interest from a customer and demonstrating sort of the institutional knowledge. We understand this problem space, look at the building blocks that we use and we we ship all these or we know where to get all these and we know how to combine yeah to solve your problem, but at the point you've got the customer convinced then what, as you said, there's no code.

C

So turning if you're already familiar with the code, you can look at the diagram and go yeah yeah. You know, I know that if you're starting fresh, that's a huge mountain to climb to turn those slides into something that you can actually feel and touch, uh it's it's the gap between theory of practice um and when that happens you know say: you've got a group of people that are going to put together a proof of concept. Meanwhile your sales process is losing momentum, so we need something more and so validated patterns.

C

uh Reference architectures grounded in customer needs so they're, not speculative, that you can actually install and you can count on to install they installed yesterday, they're installing today and they'll install tomorrow as well. um So that's that's like the first level. You know that's the little introduction.

C

um Where do you want me to go from there? Yeah.

A

C

A

Grounded in customer needs right and that's a really good point, because you know we wrote the shift on stack reference architecture because we made assumptions and yes, there was absolutely demand, but how? How do you get a little bit more into understanding? Those customer needs. I mean where, where are you um who you in sync, with to sort of bring that stuff out.

C

uh So one of the, where are you sick, with a lot of different groups? um One of the one group is the chief architects who are talking to and the field generally who are talking to customers every day. You know sending back look. This is what we did so we're trying not to do. We try not to invent things around because we're not the SMS. You know you guys are the SMS. So what has already been done at a customer site that is sort of our that's our starting point?

C

How can we take what was already proven over customer site that met the customer requirements and make it a bit more generic and help sell the next deal and the deal after that? Not the first deal because then we'd be sort of again into that territory of guessing and making assumptions.

B

Is there any particular criteria, or you know, methodology that you use I know I mean with Cloud native um there's a documented app methodology, but in creating a validated pattern? Is there something that you follow.

C

So all the patterns have got the same technical underpinnings, um so we're very I think the arrival of devops and good Ops you know came at a good time for this idea, um or this idea came at a good time for that, so we're all in on githubs and what we try and do is we have the smallest. We identified the smallest possible seed, which is give us an open shift.

C

Cluster can be completely blank and then we'll put um a bunch of good Ops on it and a single application and from there, and that application will obviously point to a good repo and from there everything else, installs automatically. So it's sort of single click. uh Installation um yeah, is that answer. The question.

A

Yeah so so grounded in get Ops right, so you're you're, actually you're writing code for the reference architecture. Yeah.

C

Yeah, so this is code yeah.

A

And so how do you I mean code? Has a life right code? Is organic, it changes. So how are you? How are you managing that, like I mean, are you developers are you are? Is your team made up of Engineers? Is it QE? Is it you know? How do you yeah.

C

All of the above um yeah we definitely have Engineers um and we have. We have QA people so by automating. This and sort of sticking to that kind of declarative model we've made it really reliable to deploy and, at the point you've got something that you can reliably deploy. Then you can start ciing it. You can put it in CI and you can run tests against it, and so our one of our patterns, the first of our patterns, was industrial Edge and we've kept that going through four eight nine ten, eleven twelve and thirteen.

C

Now so I've kept it going across six different openshift releases. You know and when a new release comes out, uh we we test it and we see what breaks and we go all right that you know that API changed from V1 Alpha One to V1, Alpha, 2 or V1 beta 2, and you know we have to have to tweak it occasionally to keep it going, um but yeah we can yeah. The automation allows us to to keep things going along right.

A

So that that that was cool there right, it took me a minute. You said you know four or five, six and I'm thinking. What are you talking about so you're, literally tracking openshift releases, with these reference architectures at a what is it a minor level right, you're, not obviously changing for every Zed stream, but you are actually you're keeping.

C

Oh, no, we we see I, we run CI on each pattern at least once a week what's week, per Arc per platform that it's running on, so we're testing on AWS, gcp and Azure uh at the moment um and so we'll test every one of those combinations every week um against whatever the latest. You know, 4.13 uh openshift releases so we'll see if things are breaking and we'll we'll get the latest versions of The Operators and we'll see. If you know, if there's any backwards, compatibility issues of crafting and well, we've found a couple.

C

um We found them live during training as well. So no that's always fun right.

A

So customers who are using these I mean they're they're, getting I, don't mean to say this for free, but they're they're, getting like updates I mean my reference. Architecture was wonderful, really was, but um you know I couldn't update it every every week and you know if you looked when I showed it, it was very much pegged into a certain version of openshift and now we're working to update it coming soon, um but at the same time yeah so you're you're, really just you're able to crank through that. Are you?

A

Are you back and forth with customers on that I mean? Is that something that they're they're they're doing stuff and saying hey? Did you know? Are you mostly beating them to that? Oh we're.

C

Usually bigger than two that we're not getting a lot of feedback from customers like that dude yeah, because we're running we're running CR, constantly we're hitting it I think there was a there was a openshift get UPS change that uh had some adverse implications for us and we found it like within an hour. Actually. No, there wasn't no particular option. That's dumping on that team unnecessarily there was. There was a a release process outage which affected everyone. We spotted it and we pinpointed it um and got people on it like within an hour right.

A

So so this is a great case of kind of like security right I, don't want to see it I I I! You know when you talk about. You know proactive patching and being aware of things, and this is an opportunity where not hearing from customers means that you're you're helping you're beating the problem I think that's really cool yeah.

C

So we really try and advocate for the we try and put ourselves in the customers shoes so like okay, would it would this change affect a customer? Yes, then we need to do deal with it too. We need and we need to feedback to the product teams that this change, whatever the intention was. It would have broken customer scenarios like this, so we're.

A

Trying to you're you're right with those product teams, yeah.

C

Yeah we deal very closely with the product teams.

B

Are they in particular, um favorite or you know, commonly used validated patterns? You mentioned Industrial Age, but I mean I'm just curious to know. Okay, this is you know. One of the validated patterns that's used often, and the other question I had was. What is the next validated pattern that you are really excited about, which.

C

Okay, so uh patterns that are used, the most common um there's, probably two different answers. There, um multiplayer good Ops, is probably the most used of all the patterns, because it's the base of everything it's it's patent, light validated pattern light. It's the minimum, minimal viable pattern. It's got. It's got the the framework and, like the tiniest demo, that we can stick on top. So in terms of when you're trying to build on top there's the list amount that you need to get rid of before you start building.

C

Yeah, so industrial edges was the first pattern and that's all singing or dancing. That is huge. uh It's a tremendous amount of work for people uh and yet still the same single click, kind of installation process, so they've all got the same same installation process once you know how to work with one pattern.

C

You know how to work with all of them, um but the one that's probably getting the most traction and use at the moment is that our devsecops pattern um that that's security- it's it's very popular at the moment, so um yeah so there's there's some things around that were announced at Summit that it dovetails in with nicely gives people something they can play with. On-Prem.

B

B

um Come into validated patterns, that's.

C

Not something we've done, we've dealt with, yes, no, oh, and you also asked which one I'm excited about next.

C

um This is a bit of a left field one, but this is actually uh something one of our Engineers is working on. It's an ansible only gearbox pattern. So all our patterns to date have been around openshift, but you know technically technically. I need the underpinning of uh good Ops on openshift is rscd. Yes, that's a pretty common piece. You don't strictly need Argo CD to do good.

C

Ops, though you can do good Ops with pretty much any sort of rules engine, um and that includes ansible Tower, so we're working on a pattern and a pattern framework that extends that kind of get Ops approach to non container platform, both systems. So if even if you're just doing well, you can still bring that sort of get Ops approach to it. So that's that's one that I'm pretty excited about see where that goes.

A

Yeah see that is really cool, because I know that often we'll be speaking with customers and they'll say we know we need to be more get Ops and devops, but we're not we're not there yet, but I mean we use ansible, because we.

B

A

So you're you're bridging a gap there that I think will be exciting to watch because yeah I mean the more ways for them to get things done with the tooling they understand and have. But the methodology that they need is going to be wonderful.

C

So hopefully, in the next couple of weeks, we'll have something to say there at least like a uh an MVP version and then we'll be extending that next quarter.

A

Right so, and that that makes me wonder and something I did want to ask is so how do you decide which patterns I mean like? Is there a lot of pattern choices or is it kind of like you know? What do we do, or you know how? How is that being handled like, what's that, like in your team, when you guys sit down and go okay, there's five of us or 10 or 20 I, don't know. But what do we focus on? Where are you? Where are you? How are you doing that.

C

So you specifically mean way to waste. uh How do we decide what to work on not how does someone else yeah decide what.

A

To start I tell you, we need an open shift on openstack pattern, yeah what goes into the process, but not that one, but you know like what what's that like I mean? Are there a lot of patterns that you guys have on your your backlog? What's it look like yeah.

C

So I'm gonna evade first um we've actually spent quite a significant amount of time this year doing, uh enabling so that we are not the only people that know how to make patterns um because yeah we're Five Guys.

C

You know we can't do everything, there's more more ideas out there than uh than we can do, and so the more people that are able to do it, the better um so yeah, and that that allows us to be a bit more strategic, a bit more picky about what we what we get involved with, because it's no longer about. Why should this be a pattern we could say yeah. This is a great idea for a pattern, but the question is now: why? Why is it us creating a pattern?

C

How about you create the pattern so that that's like a first level of Defense, um but but once it's crossed that threshold? ah This is this is potentially something we need to be involved in. um It's it's a multi-dimensional prioritization process. So there's a lot of things that go into it. I mean the first criteria is: are there multiple Red Hat products involved? We work for Red Hat. You know it's. This is, this is just part of the territory for that, um so we definitely look for multiple products.

C

We don't want single his product teams, doing demos and putting putting the demos together. We don't need to go there, so we concentrate on multi-product Solutions um and then we look at how applicable that architecture is to other customers. So the customers are the verticals other patterns. Is this something that we can do? Can we use this work as an excuse to write this thing that we can actually make uh use of in other patterns as well? So these are.

C

These are some of the considerations that um to get looked at, how similar is it to an existing patent?

C

You know we'd rather spend the time doing something that opens up a whole new sort of set of use cases for people. uh Then you know minor variations on existing ones. um We look at demand and opportunity. Is there a time-based opportunity that we can that we can get involved with a sales motion or a customer engagement that would really amplifi we'd be amplifying them and they'd be amplifying us? So a lot of these factors go into it.

C

um Yeah yeah, so it's it's a bit. It's a process.

A

It's a process, but- and so this is an important point- is these patterns aren't Red Hat products right I mean they use red hat products, but they're not an owned by Red, Hat kind of thing, which is why I wanted to look at the actual the hybrid Cloud, the the website? Right, because we were talking about this. Obviously, as we were preparing for the show and as I was looking at the site, I mean you guys. This is sort of the I. Don't know what you call this.

A

The Upstream version of the site I mean this is this: is the available site I noticed across them that when I make my choice when I'm looking at my patterns, I can do like different types of validated by Red Hat, a community pattern I'm looking at Industries I'm looking at products? Can you talk to us a bit about this? This section here where I'm looking at these validated patterns and Community patterns that are are showing up on this site and what that means around. You know devast SLA, around support around that kind of stuff.

A

um A bit more about I mean if I'm I'm, seeing Community you've mentioned it a bit, but I can get involved in this right. I mean absolutely these things right absolutely. What is that about? Like yeah.

C

uh So yeah I mean there's more things that we can than we can. We can do. We want people to be able to write their own patterns and and we're happy to. uh We want to help promote your work. um Where do I go from here? It's uh every validated pattern represents a commitment for ongoing testing and Bug fixes and triage.

C

um So there's there's like a there's, a finite pool of patterns that we can do that we can that we can maintain, um but that shouldn't limit the number of patterns that can exist and so for everything else. We give them a community designation and we and we try and make it really easy for patterns or for people to create Community patterns, um and we do that by basically lowering the threshold. You know we have. You know when we do a valid pattern. It is the test plans.

C

There needs to be presentation, presentations, there needs to be recorded demos. You know scripts for, like once, you've deployed it. This is what this is, how you show it off um at this level at the community level, it's more about like hey I've, done something and we think it's really cool uh and with, and it uses the same technical underpinnings um so we'd like to you know would like to make. We would like to make it available to other people.

C

Young floundery.

A

Right help me out: no, that's great, that's great so so we talked earlier about this that if someone in the community actually has a validated pattern, they've been working on something or something you've actually got a way to reach out to to share that.

C

A

And with the team yeah.

C

So implements I mean we.

C

There are some implementation requirements, but they are quite low. It's pretty much don't go hard at hard coding secrets and things about your environment, and you know you use the products in the ways that they're intended, but once you, you know cross that you know like a database is not a messaging Riot. Let's not go there, um but as long as you're using doing things you know pretty reasonably, it can be a community pattern once you've got a community pattern and you think this look.

C

This is so great and everyone around you saying Hey I want this. I want this. You know this. This is something that should get the validated treatment. um We've got we're trying to do this as an open process, um so we've got hybrid Cloud patterns at googlegroups.com.

C

So it's it's linked on the site uh somewhere, probably under contact, UM and you can say, hey, there's this pattern and we think you know it's uh it's worthy of, though, that you know that that ongoing investment of validation um and and yeah- and so that's where we'll have a transparent conversation about you, know pros and cons um and but yeah anyone. Anyone could create a partner. Anyone could submit a pattern for validation, um we've had essays, we've had Consultants, we've had Partners, have taken patents and and improve them.

C

They've created their own new ones, um I'm, not sure if I should say names but uh yeah, it's it's definitely an open process um and we want your best ideas.

A

um Yeah I mean I'm again, I mean I'm, just I'm, looking at the different topics on here that I have on this on this page, and they you know between the validate and the community, they're just they're, so varied I mean the connected vehicle and and when you dig into it um you know it's it's opening up straight to GitHub. It's it's fascinating like it's just it's so Dynamic!

A

um You know, speaking of back to my shift on stack architecture which is literally a PDF. This is so exciting to me: I'm, not a consultant anymore, but when I was and same for you Dev, you know when we were down in the trenches to have this kind of toolkit and the support of knowing that um and I'll go back to it. The the testing that was being done like when I looked at one of these look at this you're showing the different versions, things are being validated on, am I.

A

Seeing AWS here as well, I mean, of course, right I'm, seeing platforms, yeah.

C

A

C

Yeah, that's how we avoid you know unintentionally, assuming things about the AWS platform that don't hold on other platforms. So we just test multiple platforms and that's how we find those things um and you if you click on status, you'll see like the whole. This is our live, CI dashboard um up next to the search bar uh uh yeah. So this is every.

B

Pattern that we've got really this is.

C

um And and as you, you kind of your glanced off it, but yeah like all the code. This is this: is all public code there's nothing hidden here. It's all. You know yeah everything's out there for everyone to see and you can take it and use it and that doesn't cost you anything um and you can improve it and if you know, if you'd like we'd love it, if you send any of the improvements back, which you know some people, do um you don't have to okay, so yeah.

A

Yeah, but knowing that this is getting out in the world whether it comes back and- and we you know like you said- we hope it does, because it opens up discussion and it makes just everyone better and it makes these platforms better so that consumers and our customers are in safer, more reliable environments, but so that's cool, but like I love the the testing across the different platforms, because I mean openshift is so portable, it's so it's so uh multi-cloud. So these things need to work.

A

That way, because you know that that translation layer that openshift is providing is, is it's just invaluable, and so the reference architectures need to do that validated patterns need to do that and I really love that I, really you know, just digging around the site is, is so kind of rewarding again I'll put that back up because I put in the chat, but because it is it's, it's like you've said Andrew I know, people know that we don't hide anything, but it really is there I mean you saw me link straight to um you know to the code.

A

It's there. It's the logic, the thinking um the documentation, it's it's, it's a devops reference architecture. It really is yeah.

C

It's a it's a living, breathing architecture.

A

Yeah and I just think: that's really really cool.

C

A

Right, yeah yeah, it's it's terrific, now, I know that you guys and and we're you have um a YouTube page and I'll just put the link to it up here. um But you know tell me about recording demos. Like you know, as the team is the team enjoying getting that kind of stuff out there, I never had to do that for a reference architecture. uh You know I kind of published it and moved on. So you know I.

C

Think, there's I think some of the team really enjoys it and some of the team really doesn't, um and you know it goes, It goes with the territory. Look. It.

C

It's good experience um and it's it's just a really powerful way to demonstrate some of this stuff, but yeah there's a bit of variety there. Some people will just record the the screen what's happening on the screen and some people get involved and do uh they speak overwritten business.

B

Looking at repo some someone would want to look at, you know how it is all put together, and you know a YouTube. Video is really a good way to for someone who is new to variety requirements. You just understand how the pieces are put together. I think.

C

And and saying how little work you do and then the end result like they are the sprawl of agar objects. um You know, particularly if you're talking over the top of it, while it's going in the background, and- and you know it's amazing where automation can get you and how you know these are really. These are mult. Some of these patterns are multi-cluster solutions and the pattern just rolls it all out.

B

um You did um just to be honest, um so you do talk about validated patterns by Red, Hat um I just had this question. um Do I mean customers using subscriptions as customers? You know, um can they call support if, if they needed support I know, you know we go through the whole, rigorous validation testing. You know performance scale all that. But what, if you know customer had you know some problem or some questions? Are they able to call support and say? Oh you know this validated pattern. I need help.

C

Yeah, so that's a really good question um today. Right now you cannot call up and ask, for you know industrial Edge support. You can call up and say: I've got a uh an anq streams problem. I've got an open ship, get UPS problem. I've got enough ship pipelines from I've got an open ship problem. You can call up and say all those things you can call um I forget who public is it?

C

You can come up and say: I've got a seldom problem to the partner that chip seldom I can't remember who that is but yeah. You cannot call up and say: I've got an industrial Edge problem. I've got a medical diagnosis problem. um Maybe we'll have something else, something to say about that in the future, but um yeah. No, no plans, uh no public plans about that. Yet.

A

And that's formal support I mean if a customer's got a Consulting team on site and they're going look. You know whether the customer said this is great. I want to use this or the Consulting team is saying we're going to work with this yeah.

B

A

Guess, they're not getting an SLA or you know, support but they're part of a team, that's backed by real people, your team, a real Community. We know this model, so this that's I think that's quite exciting. To think that you're, you really are no you're, not on your own. Yes,.

C

A

It really yeah.

C

I like to have like a glass half full kind of approach to it. You know some people go. Oh, it's still supported so I can't use it, but the reality is yeah you're, not alone you're, not alone, there's a group of other people um that are using this every day um and they're a motivated team of people that they want to find and fix problems. If you find a problem, they are intrinsically motivated to fix that problem.

C

They don't want to see it broken anymore than you do, and yeah just the comfort that you're on the Dalton path that some that other people are using the same thing same products in the same way that you are um that has to have value.

A

Yeah I mean, and that's that's their that's the open source model right. You know the they're saying it would be like saying an upstream Community doesn't support us. Of course it does it's. It's a you know and again I'll put this back up because I think if, if you're out there and you're looking to interact even even how you've set this up through Google Groups, you know it makes it clear: you're not you're, not throwing out your you're, not risking your IP or giving it to some corporate whoever.

A

You know it's very much a team and a community and I guess I'll admit you know. I I came I first heard about these ages ago at Red Hat, um and we were talking about that. We had just finished this reference architecture and they were talking about evolving them and I'm thinking. What does this mean and to have seen that change and and where it's gone is, is just it's just really good. It really fits. You know what we've always had. You know.

A

All of us have been at redhead a while, but have always been used to, um but to see it kind of almost come to an area. I didn't expect it to be possible to come to as need I'm curious. If you have a shout out to some of the people who kind of you know brought that here, because these are some people. I know I've worked with in the past, but you know where, like? Where did this come from? You know in the Deep there are dark days so to speak.

C

uh I think probably the Genesis was probably uh Nick Bassett and William Henry William Henry was in the portfolio architecture team at the time. Hence you know we try and work uh closely with them, um but it's really their brainchild um and I like to think I brought a little bit of uh a bit of technical uh expertise to it as well. As you know, I'm a manager now but I did have a technical background um and I spent a lot of time.

C

Building up the the relha Community, um so clustering, so I I brought some of that mindset of community building uh to this as well and I. Think that I think that's some of that. Some of that's like licked out as well in a good way.

A

Yeah yeah I think so too, because when I mean yeah the portfolio, it's the portfolio, architecture, team and I think that's really important because I know working with them in the past yeah the fact that they were pulling in all the pieces and that they're now in lockstep with engineering is super cool, because that is what it is. Our customers are doing that so we're doing that. It's natural! It didn't happen one because of the other.

A

It's just a natural progression, so I think it's it's worked out really well and I I mean there is actually a formal, Red, Hat page for validated patterns. So it there is, you know, there's a nicely branded uh uh page I think there's even a Snappy little marketing, video on there yeah yeah animation and everything. Oh yeah.

C

We've got a few people excited and you know people are quite happy to contribute their time and resources to promoting.

A

Yeah I think so and I think for you know as folks watch. This show there's a lot of levels to get involved in here and that it feels like the barrier to entry of involvement is quite low like it.

A

You know, I feel like I could be part of something like this and, and you know, I'm in the marketing side of the house and I say that with a bit of a joke because I feel like I, do know a bit more, but so I like that, and you know I again, I think it's important that especially our field teams and customers who see this realize that these things are out. There have a read, check them out um and understand the community.

A

That's behind them, because they're they're going to evolve what you do and not only are they going to give you great Solutions they're, going to teach you how to get to good Solutions and great Solutions.

C

A

That makes a huge difference.

C

Hopefully, these allow you to spend more time on higher value tasks, not just deploying a few operators, and you know, don't spend your time getting. Openshift installed, spend your time like showing the power of openshift to the customer um yeah. So we try, we don't try and be everything we try to give you like 80 of the start of the of the solution, and then you know every pattern: it's not something you're going to take to production, unmodified you're going to have to tailor it to whatever the customer's needs are, um but hopefully yeah we've.

C

Given you that starting point and um just back to your ease of use, Point like we really do fight against entropy, you know everything would do. Software is a constant fight to like. Are we making this too complex? uh You know, as you add, more power and flexibility, it's very easy for complexity to to creep in, and so we're constantly fighting against that and trying to make sure we, you know the powerful the hard things are possible, but the easy things are easy.

C

A

I I like that and then I think again, when you know you're bringing this to our customers, but when our customers can start using this, you know they really are able to yeah focus on their own needs and and get their products better and such but also learn great process from something like this.

A

Not only cultural process around being part of that contribution cycle, because they might not be missing me, you might have infrastructure guys who and gals who are trying to who can contribute back to a pattern because they've hit something in their industry that needs it, but they're not ready to compile their own kernel just yet, but they can still get involved with something like this and I.

A

You know I find that I find that really exciting and when we talk about going Beyond reference, architectures I think that really does that, because it makes it so living and breathing and and I I really really fascinated by that, which is why I was super excited to you know, took us a while with you know, various delays and stuff, but to have this conversation because I want some I want folks to just find those URLs and to start to read through them, because once you start doing that the AHA moments just boom boom boom.

A

They just start. It's really really good yeah.

A

Thanks for having me, oh yeah, no I, it's it's appreciated and it's a it's a fun format. We have here and it's worked out pretty well so um I I hope your team jumped on I hope you are mocked brutally when your next team meeting comes I, don't think they have anything to mock you for, but I really hope they do, because that's always fun, but no I do hope that uh that they had a chance to join.

A

We did have one person in the chat say hello, so I always like to say uh you know, let's go ahead and put that on there and say of course, action greetings hello and thank you for joining if you're still out there. It's um it's good to have viewers really appreciate that um so anyway, if you have any final Last, Words, uh Andrew I think you've basically covered that off really nicely, but please go ahead.

C

uh uh No I just we, we welcome everyone's perspectives and ideas and um yeah there's only so many of them we can do, but we certainly want to help you if you're interested in creating a pattern. We'd, certainly love to help. You do so.

A

Well, Dev: here we are again: we've got some exciting shows coming up, um we're in uh planning some nice ones, um so some stuff on ACM, so red hat Advanced cluster manager for kubernetes and some other areas in the Telco space.

A

um I had a yeah I, don't know if there's any others we want to reveal just yet there's some interesting demos and Labs coming up so uh keep an eye on that playlist like subscribe. All those various things, but one thing I do want to mention is next week we have our first ever Japanese language stream, so we're doing the uh the hybrid Cloud copy. Our Japan and um the team from uh in Japan has doing um a really neat session on cloud native. It is in Japanese.

A

So if you don't speak the language you'll, you won't be able to follow, but it's it's really great because we're getting these voices from APAC out there, so I've put the short URL to their brand new playlist, uh that is at 1pm Japanese Standard Time um next Friday July 7th, so I'm I'm really excited uh other than that always keep an eye on the streaming calendar as I like to do Dev. If you have any final words, uh please, you know, let us know, what's what's on for the weekend or uh just say, say goodbye.

B

um I just wanted to thank Andrew for coming, and you know sharing thoughts on validating factors really appreciate. It um really excited that you know every month we're coming up with these shows, and it's out there really interesting topics.

B

um Glad to be part of this. Thanks.

A

Heaps of fun all right folks, well, thank you, everyone for joining and for viewing this uh in the future. uh Andrew as Dev said. Thank you for your time today um and your passion and for you know, being such a great advocate of Open Source and making this happen, and just for coming on. The show I mean I've, I've heard always heard wonderful and great things about you and the teams and in previous roles as well. So thank you for being here and spending some time with us today.

A

Thanks very much for having me all right, cheers all have a good one and we'll catch you next time for some coffee see ya, bye, bye,.

A