Continuous Delivery Foundation Ortelius Project Meetings, 1 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: June 1, 2021 Ortelius General Community Meeting

Description

Summaries from the Ambassador Groups and the Champion Groups are included in this general meeting. Specific discussions includes building a podcast and pushing the communities first release in early August.

A

Let's do this, okay, um so siddharth, I'm gonna go ahead and let you give us an update from the ambassador site.

B

We'll just move all that.

C

Automatically, okay.

B

And um every time you do an update, even if even if it's a brand new um uh microservice.

B

D

Hello, everyone um good day, good morning, good afternoon and good evening, wherever you go, you are in terms of how we're performing in the uh linkedin space. I think our followers have increased in the last one week. I see the trend uh we have got over 30 followers of authors in the last one, so good numbers- uh I don't know what happened in last, one we have from what we got this uh so much traction.

D

The numbers, yes, are encouraging in terms of how we have progress. So now we have all over 81 followers. um If you see activities, I think one of the things we can ask earlier how about, if you guys, you know you have received this, uh the badges. How about you you start sharing your badges on the linkedin are crazy. uh Can you get mute? You can hear steve very loudly.

D

Is if you can start showcasing your badges, I think most of the people have done few are remaining, but it gets little more traction. One space, uh second, is. What I was looking forward is is remember the burst podcast, so I've created this document and the expectation is that you list out the expected topics that you think would be part of the podcast and it could be randomly any topic. So don't even think of what are you you know which topic you're expecting at least have some brainstorming over there.

D

What I'll do is I'll share this.

D

A

Would you share the one that you did so that everybody gets an idea of how you structured it, because it was really helpful to see how you had done it.

D

uh Okay, so do you want that to be shared right now or, as you can hear, as an attachment.

A

Or how do you want that now? You don't have to include it in the document. Just share it right now, so you can. Somebody can see what you're looking at trying to build because it was once I saw what you had done. I thought it was really helpful. All right. Let me.

D

So what I've done is mentioned earlier also is um this: we have done for our natwist community, even we we are inviting speakers from outside and we want them to share their stories around the devops journey. Let me tell you, how does it looks like.

D

So what we you know had a word: this is what it we call it as a partner trail station within the netflix group. So what we say is that the speaker will get 30 minutes start additional, followed by a q, a of 10 minutes, which is 40 45 minutes of session. So when you come up and share something, this is how your flow of event should look like.

D

So you should talk about your organization and then just see you work in the role that you play in your organization, the business problem that you have tried solving. How did you approach that? uh Then your challenges, then you choose the technique, whichever you use, so we are not emphasizing on tools and techniques, and technique is just one part of the conversation.

D

Then what was the outcome that you achieved and, most importantly, what we do is uh generally what happens in most of the events a speaker come up. He shares whatever great ideas and thoughts are, and then he leads the session. uh What we're doing within the netflix group is, we are having conversations also after the event answer. So the last thing that we ask from the speaker is call out what help you required from the community and how do you want uh what problems do you want the community to solve for you?

D

So what are doing is after this there is an open, ended conversation that remains, and so people have a conversation with the speakers that how they want their health to be after that. What we do is so when you're talking about this whole flow when you're talking about this whole flow. What categories and sub categories? What you said is the speaker should- and you know, go slow right right now.

D

The speaker need to select one category, whether it would origin absent cloud or it could be overcoming one way of working or it could be dynamic, learning and organization culture. So again, the important is not that, since we are a devops community, so we can only talk about devops, whose technologies and that set now we will also talk about diversity.

D

We would also talk about psychological, safe, we'll also talk about ldph, which is also part of it, and then, once you choose a category, we have chosen a sub categories also so, when you say dynamic, learning, organization, culture, what you're talking about is diversity, inclusion, psychological safety, team, empowerment, all those things so when you're coming up old days of working, what we're talking about is the dev agility power, the values management.

D

So what is happening is after we have created the structure. The speakers whom we are inviting and those who come up and have a talk. They get a great idea of what we are expecting from them to talk about, and this is how also the additional benefit of this is. We are creating our internal database of each of these categories. Also, so how much uh you know, let's say value stream management.

D

What are the talks we have done, so we can quickly simply are classifying it, so we can say in balanced demand when we have this four or five different talks that we have. uh Does it make sense to you? Does it helps you? uh Casey has seen it so I know her opinion, but what is the opinion of other quotes?

D

That is what we want. The end picture to be for our particular sport talks as well.

E

That's brilliant man.

A

So we need to sort of need to create our own version of um of this.

A

In different categories and what's the can you share the doc in the chat that you created.

A

And then I'll put it in the um notes.

E

Is the idea this is like a framework for presentations going forward? What costs.

A

Yeah so think about it. This way we're going to reach out to folks to ask them if they'd like to be part of our podcast to get uh speakers or our guests.

F

A

Them guests um and we could have, we could create a forum that has all of those uh options, and so they can, you know, specify what they would like to talk about and what I've learned that, if you give people more structure, it's easier for them to participate because they may not have their they. It may help them get some ideas about how they can be part of that conversation.

A

um But otherwise, if you don't give them some structure, they struggle more with coming up with an idea, so it just helps pull it together.

E

Oh, it's brilliant man, you put that all together.

G

Yeah and in the.

E

F

G

In the other side, I think we probably are going to have to to to uh scenarios uh just want to say like if you are not really sure how to put your idea on this framework.

G

um Reach reach the reach, the people or the team to support you, because we don't want to like people, don't try to do something because maybe it's it doesn't fit well on this. So in the other side, it's a good idea to try and then get super help for the result. People to to. I don't know to to fill this and structure this into this, but just don't don't uh don't stop trying doing things, because sometimes when you struck something uh it makes people don't try it. So that's like I thought I want to share.

A

Yeah we should have a and we should always have another category that says you know, choose a topic. What would you like to talk about.

A

You get somebody that says they want to talk about. You know rebuilding their transmission in the car. We may go yeah, it's probably not what we want to do.

G

Experimentation is a good thing too. So, if someone has like, I don't know some something is passionate to speak. uh Try it please try it yeah.

A

E

Sorry, just to say one thing: there was a guy at the sre thing at the devops devops institute, the sre skill updates, and he spoke about his racing team and he used that as an example of sre.

E

What sre is and how it fits together and it was all about how they bought their car and how they optimized it for racing. It was brilliant yeah, so you could you could in a sense use you.

H

E

H

Yeah I've heard that analogy before with a racing car.

E

um This guy was an actual racer. I mean he was in technology, obviously, and he's an extra real thing, but he used.

A

H

E

H

Yeah, it's I mean these days we're changing the tires as we go as we're driving.

E

H

The new world that we have today with the with kubernetes and and high availability and the whole architecture that was available now in microservices.

E

What are your devs, like the race, car and they're, putting into devops to get some new wheels and refuel.

F

Yeah, it's an interesting idea to you know, take stuff that is very accepted in the tech business and then try to.

B

F

It to something else, I saw in a series of articles a couple of years ago about devops for parenting, and you know real parents were talking about how they were doing these and how it was working out for them at home, and I'm like wow. You all are amazing.

F

H

uh One of our toc members, tim kelton, he's actually using kubernetes to drive semi trucks. He actually works for a companies and uh I think they just bought uber.

H

Or that or division of uber around the self-driving trucks so running it all with kubernetes.

H

So literally we're changing the tires as we go.

G

So we see that we just messing around with this.

D

And yes, congratulations to steve for making it to the cdf board. Thank you.

D

You may call it out. I think I have taken probably one of your things that you might have to share about steve.

H

You're on me, tracy, sam.

A

um Thank you for reminding me to congratulate steve for his new role on the toc board. Yes, and you know we other, the other thing we have to be proud of. Is that three of us nominated ourselves and got nominated to be uh potential members uh as well, so they have two general member uh representatives on that board and anybody who's part of a project can add themselves and siddhartha has is in the running. uh Garima is in in the running and brad is in the running and two others.

A

So thank you for stepping up and putting your name out there and saying hey. Why not? Why not me? It was great to see three of our committers on the list of five way to go. That's awesome and I'm hoping that at least one of you get in there. We get to vote for two and.

H

Do you know when the voting is.

A

Well, I think that the uh uh I don't know if the it's an open vote, I think that the board votes.

H

Okay, I can't remember what the rules on that.

A

Pretty sure the board votes it's a board uh and it may be the toc board that votes.

A

I'll have to look.

I

Anybody right siddharthi, do you. Let me look I'll share that link, who is on the board of book and vote out?

I

A

So anyways we're rooting for our own and now, if it's the board or if it's the general board or if it's a toc board, you know that you're going to get our votes at least.

I

A

All right uh steve, you want to give a update on um what we're doing on the catalog the service catalog project, yep.

H

um So uh what we need to do, um we had I've been having meetings with uh the get ops group in australia uh as part of the um at thursday afternoon, meetings and they're focused on the get ops. um I talked to brad mccoy last week and we're in this weird transition um on our azure cluster.

H

I did manage to get another 25 000 worth of credits um to run our kubernetes cluster over azure and it's good for another year, so the accounting switch is happening, uh the third june 3rd. So I should have all of that switched over by the fourth or fifth, so uh taurus I'll I'll be able to get you once the accounting switch is done, I'll, be able to get people access that need access to the azure cluster after that.

H

So, let's just sit side on that front, um so that group is putting together white paper uh around uh git ops and, if you're interested in that reach out to brad mccoy on discord or taurus on the surface catalog, we have a lot of the the base, I would say the groundwork in place for the microservices and now we need to go ahead and uh basically ramp up and get this thing uh finished up.

H

So the you'll see a lot more issues and me bugging you to see if you're going to complete something, if you don't have time to work on something. That's perfectly fine. Just let me know to where we stand. I can shift that coding effort to somebody else. um So don't feel bad if we're we're going through this, I'm going to try to finish up the service service catalog in the next month month and a half to get it out the door.

H

So if there's anything that you um are working on that you're not able to just let me know and we'll get it taken care of no no big deal, I know. There's um people have other things going on with work and their their personal lives. So don't don't worry about that, um but on this service, catalog we've uh uncovered a couple interesting things: uh the swagger ui uh or the swagger piece. Bringing that in is going to be from what we've talked to microservice developers.

H

That's been a big interest as part of that and then also the cve and licensing is also a big interest that we're going to be bringing into the product um there. There is one of our potential customers from the deploy hub side. That said that our our service catalog for um that we're producing, wasn't what the their developers were looking for and I'm trying to get a meeting with them to find out what we're missing from a cataloging perspective.

H

So if anybody has any ideas on other things to add to the catalog, please drop me a note, so that's kind of where, where we're we're at on that front, oh um one, other thing is in discord. I did uh add a stand-up channel.

H

Basically the idea behind it is just to put your dependencies. You know if you're waiting on me for something or if I'm waiting on you um and just a a an idea of when it can be completed just so, we can do some coordination on that front.

H

On that discord channel, I'm going to go and delete things that have been uh completed so just be the short list that we can work from, and we can have conversations around those specific topics around the dependencies between people um longer dev dependencies on like coding, strategies or whatever would still happen in the dev channel, um but the stand-up channels, just literally to ping somebody and let them know that you're waiting on something from them. It's that that's the the purpose of it.

H

It's replacing our monday stand-up meetings that we're doing in the past um we're going to give it a try, see how it works, uh how it works and just play it by ear on that one. So that's kind of idea behind that.

A

Any questions no, but I do just uh I have a comment. um We want to be able to get this stuff, uh the the service catalog stuff done by uh like mid-august, so we can do some press releases. The uh the trade show kind of conference uh season hits in september. We have kubecon um and some other like devops world it would be, and it would be great to have that as a a news announcement for those shows so yep.

H

That's that's the goal to get it out. I'd like to get out at least a month before that, um like you said end of july time frame is kind of like the latest I'd be wanting to make something available, um so you can get all the press releases, all the we can make sure all the documentation is updated. You know there's still a lot of work. um You know the coding site's, not that bad, but all the things that go along with coding.

A

Just just take just as much.

H

Training, all that has to come along, be pulled along for a ride.

A

Okay and then before we lose, uh we've got eight more minutes left the next. The next uh kind of govern government, organizational tasks that we have for ortillius is. We need to put together our own governing board and then we need to figure out. We need to bring on probably two members from the community to be on our official technology oversight committee board, so garema has taken on the task of figuring out how jenkins does their elections and how they run their govern their own governing board.

A

So she's going to work reach out to oleg who is on the um who's, basically running jenkins and he's going to do sit down with her and go over all of their docs and how they have their governing board. So once we understand how we do that, then we'll put we'll put nominations out: you'll be able to nominate yourself for the governing board and then we'll do an internal election um across the 120 people that we have on our mailing list. And so that's how that will happen.

H

And the purpose of the governing board is to be a representative from the project up to the cdf uh organization, outside of all this, all the sigs and stuff like that, they they need somebody. They need a point contact um to work work with from the cdf and the linux foundation from a governance standpoint.

H

So if anybody wants more paperwork.

A

A

But that will be coming and that's kind of the last thing that we need in terms of putting the structure of the uh of our I mean you, don't have to have a governing board, a screwdriver doesn't have one, but it it seems like. It is a better structure if you do have one.

A

So, for example, if we wanted to say we want to identify somebody as a product manager, we could the governing board could say we're going to have a role as a product manager, and then we would put that out as a nominee nominate yourself and we'll vote for who's going to be our product manager. Those kinds of structural things that allows us to do easier.

H

And it looks like we have for last. Five minutes looks like we have some new people um that have come across.

H

um I've talked to a couple of them before, but they haven't been at a uh a general meeting, yet so bala and devendran, and those are the two new people. If you could just introduce yourself to the group and say hi.

J

Yeah hi all so I'm paula vignesh, so I'm an india sre. So I am new to this field and I think I have earlier talked to steve on that tracy and I think I will learn new things here.

H

Perfect welcome aboard.

J

K

J

K

Myself davindra I've been like a python developer for like seven years now, and I worked on some of the devops uh tools as well and apart from technology, I like to look after this as well. So I play tennis and to talk about.

H

That perfect welcome aboard um we are.

H

We may need a few other people to help mentor some of the new folks that are starting out with programming microservices. So um I may I may be bugging a few of you. I like.

E

I, like mentoring,.

H

All right, you're, a pro at it now sasha, your wife is rubbing off on you, you're becoming a famous professor here.

E

You must remember this very smart guys.

H

Awesome well welcome everybody. I think that's all I had unless I'm missing something.

H

Nope, I think I'm good for now. If anybody has anything, um let me know, oh and just uh just to comment on the whole stand up and the um this push that we're going to have you know it's, I may be bugging you just don't uh take it personally.

H

Just trying to keep things keeping everything moving along.

G

um I was thinking about uh from the beginning. This is just a thought. I'm going to try to to put it in some kind of this description, but I think the the the growing in linkedin uh on the the success with the batches are being really great. I think maybe we can move out to uh like a next step. I think that probably there there is people that can contribute, but in a really spot way like doing something really specifically.

G

So I was thinking like. Maybe we have like a uh not batches bro, like kind of points you know, you're moving like five points to the win, a batch, and still you can recognize that. I I don't know I make a blog post. I make one talk and if you you can share that on or linkedin it's going to be successful as well, because at the end linkedin is each pulse make that impact. So I.

F

G

We will have something like that, so I'm going to try to I'm just going to try to do to draw.

F

G

Funny to maybe okay that, and maybe after that, we can put it in a you know in this inside the structure of the batch yeah that works.

H

Cool yeah, always always stuff like that rewards, are always fun to have, especially with the way you you uh come up with these ideas of how to uh represented it in an image.

H

All right, everybody, uh thank you, so much and we will be in touch, have a good one. Take care.

E

E