Hello hello hello That's not what we actually have a lot of mice. We'll need that for people to talk Oh, we'll need to give that to the speakers. We do have we have name tags to thank you rich bowen We'll need this later. We have a props. We have the Apache con lightning talks are a long long tradition of Five minutes to talk about whatever you want to talk about that's Something related to Apache and your community or your technology here. Oh, really? So they're wow Jeez the voice of God and the beer comes in and the beer comes in and Jim's voice goes up real high because the beer's in And we have one really important rule. No slide. No slide five minutes No slide no slide minimal heckling Unless unless Shane is talking then you can heckle as much. Yeah, no, I'm the practice speaker. Okay, so Okay, I can't wait for rich's talk We do have one exception with slides that there's the rich bowen rule where Sometimes you just have to have slides for the heartwarming and interesting message So that is the one exception, but no, this is not yet It's a beer and the in the in the back booth. We just need a timer. We don't need those yet Just the timer not the slide just the timer. I believe the beers are open and available. So yes as we Coming like monkeys up here people start going grabbing some beer That's very very good It helps everyone enjoy both Shane and I immensely We become much funnier Yes more you drink So I would suggest drink heavily and and you should probably start drinking before we do if that's your kind of thing Yes, thank you. Oh, I thank you. We didn't even have to ask And Jillian the that the we need the timer, but not the slides yet. Thank you and Just a reminder that everyone who does talk gets one of these fancy little Capital one Cable rolls if we have any leftover I will be lobbing them into the audience They do have little hard things on there so that they hit you don't sue us But they will be kind of nice would like to another another beer another beer. Yes Well Jim since since capital one since capital one is sponsoring the beers you get to right I get to I get to So hopefully I'll be funnier to after two beer So I think we should we should get moving so people can get going we should get started. Yes if David North is here David North David North is David. Yes. He is and he has David has a great dirt. I mean not that I'm biased But ooh even better So David will be talking while we're we're getting our beers about Actually, it's oddly Appropriate for getting beers because he wants to talk about beer. Well, no, but after beer. Oh, okay I'll I'll see a patchy HTTP D Right. Thank you. Jim. Everybody else and our office shower. Oh, that sounds very five minutes for our first speaker victim Excuse me. Thank you very much Hello, yeah, right. Okay So I wanted to talk about this which was the last sort of little fun side project I did but I was wondering where's the Apache angle and then I realized that actually there is Apache software at the heart of this project But it works so well and I've used it for so long that I'd almost forgot it was there It's that good So flashback about a month ago. I work in an office with 70 other people and As the weather gets warmer more and more of us cycle to work and that's all fine and good The problem is that we only have one shower in our office building So if you've got 10 people cycling to work in the morning, it gets a bit Contention and it was really boring standing outside waiting for the shower to be ready And if I go and sit at my desk and do work, I keep finding that I've missed my opportunity to get into the shower So what I wanted was somewhere being able to tell from the comfort of my desk that the shower was available So what I did was I got hold of a magnetic door sensor This is the IOT part of the project stuck that to the door and people usually leave it open when they're done So it's a reliable but not 100% indicator This then calls out when the door opens or closes over the internet At the other end. There's the Apache HTTP server running a little CGI script that does the updates so we get events for door open door closed and Thanks to the magic of Apache It's really easy to put a little hook there with the CGI to receive these events integrate with our office single sign-on system so that the crucial corporate data of whether you can use the shower or not is protected by login and It all just works and so I know I'm not allowed to have slides But I would like to show you just to prove that this is real you can see here because it's gone. It's Yes, it's five minutes to 11 in the UK so oddly enough the answer is yes The shower in our office is currently free and the door has been opened since 11 minutes past to Florida time So that was my most recent internet of things project and it's saved me many minutes every morning So it's all all thanks to a bit of Apache software at the heart of things Estic I was a little worried when he says IOT and The office shower like is this surveillance or something? Well, it is the internet of things Yeah, I guess it depends on but though Thank you. I do that is so old school. I mean that is great. I mean hopefully it was pearl. Were you running pearl? Maybe oh It would have been even more more beautiful No, so I'm so glad and let's it's a good notice to let's let's keep it clean. Let's get polite. We'll keep it fun Okay, I mean well very clean sudsy keep it at sudsy would be good, too You know, right? So we're not all fun and games. No, no, we're not. We are dead serious sometimes So So next we have mr. Trevor Grant. Yes, mr. Grant here, please Yes, yes, he is Wow, I mean I've impressed you brought your own your own Cheerleader catch a Trevor Grant would like to talk about Apache Mahoot out with the map reduced and in with the GPU Hmm. Very cool How you doing? Yeah, you can clap. That's fine There we go. There we go. I'm started Trevor Grant I am by night a PMC on the Apache Mahoot project and by day I'm actually paid to be an evangelist in open source Which means I get to go around and just get people all jazzed up about working on open source projects that I like I Usually when I'm doing this job don't take notes but I was kind of nervous coming up here and then thought I'd be cool and have a beer with me and Then didn't think about what I was doing and I have all my notes on my hand. So I'm gonna have to wing this one a Apache Mahoot has been around for a little while. How many people have heard of it hands a lot Keep those hands up. If you think that Apache Mahoot is machine learning on map reduce There we go, and that's the problem and why I wanted to get up here We have not done that with them deprecated since like 2014 and if you've been anywhere near me It's shared a table had some lunch had some coffee the entire time. I've been out here There's a good chance I cornered you and gave you the long-form version of this talk about how Apache Mahoot is doing all these exciting things We're engine neutral. We run on spark. We run on flink. We run on h2o. You can write your own bindings We run things on each GPUs native solvers CPUs. It is the coolest machine learning library You've ever been a part of but Everyone thinks oh map reduce because for every blog post that comes out about all the cool new stuff We're doing two more people right. Oh, I learned how to do recommenders on map reduce in the moon It's very hard to get people the word out and so that's what I want to be up here doing I want to if you take nothing away from Apache con of all the cool talks you did remember Mahoot is no longer map reduce We're on spark. We're on all these cool things. We create huge GPU clusters. It's great Also an important thing to remember about the moon project not the most important thing, but very important. We've got the best swag koozies Very nice Three more minutes I can dive into the stack why not So I've been saying some crazy things like we have distributed engines we're engine native How many people work on a project that's like big data big distributed data? Probably a few or interested in getting involved in something any Big data distributed data structure how we do that is we wrap it in a matrix Whatever the native structure is for your engine and then someone who's a real expert in your engine thinks okay How do we do a matrix transpose? What that lets you do is we have a scholar DSL that sits on top and you can write in a very Python like way in a very are like way Matrix algebra now. This is another problem that we run into Because everyone likes machine learning to be this bag of algorithms this one minor with methods And I set some hyperparameters and then I fire it off and then magic happens and then everything comes back and ta-da And it's not like College math. I don't have to like explain the statistics or anything. It was just it went off into hyperspace Machine learning happened and it was great We don't have quite the big as big of a Target audience because you have to go remember that terrible College linear algebra to really get the exciting usefulness of it But that's where all the magic happens because using a patchy mohut you deploy Well, I won't say you read it. Let's say you read a machine learning Journal of statistics are at all cool on Monday morning.  It is a really really really big pain and that's really the exciting. That's the fun punch line 38 seconds left. I am able to read a couple of these Apache streams incubator project check it out the coolest social data. You've ever Coolest social data project and all the patchy if you want to hear more about mohut We're doing a birds of a feather talk coming up at five six thirty. What are we on Eastern? Okay soon coming soon Come out see me. I really appreciate it 1311 seconds left to clap Thank you, thank you. I have to admit Mahoot has been really really on the top of my mind I've really been you know thinking about getting much more involved with it So this is really really cool stuff besides I like just like the name Mahoot. That's a that's a huge of a name Perfect and perfect timing perfect time there. Yes, so let's go So I just wanted to bring out one point is we also support those of us You know who don't choose to imbibe for whatever reason for whatever reason, you know if alcohol is not your thing I know the other half of us. It's caffeine, right? So we go both ways. This is the first I'll be honest with this the first real beer I've had in about five weeks I've been one of those low-carb diets and so and this is most probably one of the hardest things I had to give up. I was drinking Michelob ultra. Oh Well, that's that just burns right off Whiskey just burns right off beer's got the cards not the whiskey So I didn't say this is the first drink I had in five weeks I said this is the first beer I had in five weeks big difference So, but I think we should go back to a little old school. Yes, that's why we're here at Apache con And I would love to welcome Rich Bowen who would like to talk about why I love Apache con or rather they say mr. Apache con so Save that keep it All right, I'm going to talk about why I love Apache con It's kind of a tradition in these lightning talks to have somebody come up here and talk about why they love Apache or hate Apache or whatever Apache con is the high point of my year every year going back to March of 2000 in in late 1999 Ken core Sent me email and said I should submit a talk to this new conference called Apache con and I said you're crazy I have nothing to talk about and submitted three talks and they were all accepted and So I found myself in Orlando standing on a stage in front of a few hundred people who thought I knew what I was talking about And that was a great feeling So, you know, that's that's part of why I love Apache con I've made a career out of playing that game and standing on stage and letting people believe I know what I'm talking about This is the 28th Apache con since the creation of the Apache software foundation You might say 29 if you count the one that was before Apache was a foundation. I don't count that because I didn't get to go In in fact, I've been to every Apache con except for the one in Cinshine, Germany in 2012 and I will never forgive my manager for Preventing me from going but I think that I hold the record for Attending more Apache cons than anyone else. I've been to 27 of them. That's awesome. I love being on stage I love having all you people look at me and think I know what I'm talking about So that's part of why I love Apache con But there are there are many other reasons Apache con is where I come to see my oldest friends many of whom I met at Apache con And and I met several new ones this week. So this is why I love Apache con I love Apache con because it shows me that I'm not alone working on this open source stuff I see all these other people and you know, CS Lewis famously said I read To know that I'm not alone except that he didn't actually say that that's a quote from a movie what that was about him But we'll pretend that he said it I Love Apache con because I love Apache and Hawaiian shirts You'll notice that everyone that's been up here so far has been wearing some kind of Hawaiian shirt and there's no mistake Cat here. I've always enjoyed Shane's lightning talks and so I thought I would be Shane today. I Love Apache con because of the passion that I see in the people that attend Several of us that have been doing Apache con forever Start to wonder if we're the only ones that care about Apache anymore And then we come here and we see the amazing people working on amazing new projects People half our age that are still working on this open source thing and that's really exciting to me I the the sessions here range from the esoteric and philosophical to the deeply practical But at the heart of everyone is this desire to solve real problems in the real world to scratch your own itch as the saying goes I Love Apache con because of our sponsors Talking to sponsors about why they're here at Apache con has the effect of re-centering us because it shows us that It's about solving real worlds in the real problems in the real world that are making lives better and and I spend Yeah, people people depend on Apache software because we have a reputation for our vendor neutral high quality Software and it's sustainable because of those esoteric philosophies that we cling to in the face of practical realities. I I Love Apache con because it's part of how I identify I identify myself I've spent my entire adult life working on Apache con so it's it's a real it's a part of identity my identity I sometimes refer to it as my life's work. I've spent hundreds of hours on it, but I'm not the only one Other people including our amazing producers there at the back of the room our numerous volunteers our tireless infrastructure contractors our beloved Melissa and Our supportive board of directors Apache con is built on my sweat and tears, but also on yours It's older than two of my kids and the other kid has grown up watching me Go off to Apache con and knows that it's such an important part of my life The wall of my office is covered with those 27 Apache con badges and all the people that attend video calls with me say what's that behind you on the wall? So as we look forward to the next Apache con details coming very soon, I hope We need to figure out what you want in Apache con and make it that Apache con is primarily about building community Thank you so much for coming my friends I hope that you'll come again, and I hope that you'll love it as much as I do, but I don't think that's possible Well, I don't envy the person who goes after that Yeah, wow that rich man, man. Oh, man. That's gonna be rough riches Whoo, I will just say thank you to rich bow and both for Mr. This is mr. Apache con so just a round of applause just for rich for keeping all the rest of us focused on And I want to thank rich in particular because I often I don't know how many years now I've given my talk. I have no idea many seems like why he's actually why I love. Oh, I'm sure it Why I love I don't boom. Why I love the ASF is a traditional talk I've given since 2007 at least if not longer will you be giving it today. No, I will not because rich has given We've had the the keynote with the love letter and we've had rich with the heartfelt Why I love this though, but I would like to say that the next speaker will be me Now one we have one two rules right the five minutes and what's the other rule no slides no slides unless you are rich bow and so Jillian See, that's rich. Yeah, so rich bow and is allowed slides at the lightning talk, right? So See so we've got this you didn't know we were this organized and the other rule is Jim gets now off the stage We didn't know we were disorganized either so Um So my lightning talk is why I love the ASF. Oh wait, no, sorry. No, let me forget My lightning talk is five things.  No, really. It's me, but I'm already up here. You can't kick me off Five things I never could have imagined doing and growing up that I think are important for the community and Better world that if you told me as a kid, I would have I wouldn't even laugh to you I just would have had a blank stare like I would do that. I don't understand first one doing open source So we can all raise our hand if we use one of these The first computer I actually hacked on Yeah, not not many first computer. I hacked on was a trash 80 Which I actually got my father to send back because it wasn't good enough And he actually got one of the first Apple 2 pluses ever made the story he tells he got it from big jobs, but I don't believe that But I didn't actually get into coding then I actually went off to become an engineer and then work elsewhere in software and it wasn't until late in my career that I actually came back to open source and It wasn't I didn't plan it. I just ended up here my job ended up here I was interested in it. I asked questions. I got involved. So my message there is I Couldn't imagine doing this, but when you come up to an open source project ask the questions and people will welcome you I didn't always have a great childhood and I don't actually remember most of my childhood, which is good and I could not have imagined Having a child when I was growing up when I was in college after college. I had convinced my friends I would never have children and low and behold. I met my wife and things changed. We have a daughter my daughter's Roxanne, she's 12 and this is was a huge thing for me most important thing in my life and the method lesson here is We are all here as volunteers helping out with Apache come on helping out with their projects We have a day job, whatever we also have families and The family your family your friends those are more important than all the rest of it So we need to be patient with other people in our communities when they don't show up in a project Maybe they have real life to deal with and that's okay It's okay that we're not all on our Apache project 24-7 So having a daughter who loves animals who loves horse riding leads to other questions No, you can't have a pony Well, I could not Unimaginably unimaginable that we now own a pony So He is a Welsh pony 13 hands high his name is Quincy My daughter absolutely loves him and the barn owner was going to kick him out and said I don't want him So we bought him for a dollar and last weekend. We actually had him trailered up to his new home Where apparently he's actually a lot happier So my daughter knows this is not a long-term proposition. We're looking for a new home for him Now if you want a pony, let me know But what's important here is it's not about getting the pony It's about maintenance So we paid a dollar for a big horse pony. It's about maintenance It's a it's about a thousand dollars a month to feed and give it a house So the lesson for project communities is it's not about just getting the code out there It's getting the docs out there answering the questions fixing the bug. It's helping new contributors Be able to figure out what you have and then help you build the next thing So what I could never have imagined when I was a child or anywhere before that is becoming a public speaker so This is a great photo by Julian cash who's done a lot of high-tech conferences who does painting with light But I've been doing Apache con speaking for years. I've been doing a proscon And I've been doing Osconic night, which is an awesome kind of Lightning-talk thing. I could never have imagined doing that earlier in my career and it's still hard for me I still get nervous before I come here the lesson here is Just do it we all have a hard time getting up on stage and There are a lot of us who once you ask somebody else and you realize they're worried too That helps you that helps them too and then those of us who have been speaking We want to help you build better CFP's build better missions for confidence We have a lot of knowledge in Apache that we can bring to a lot more confidence and I never could have imagined growing up with just my parents. I'm the only child really not cousins uncles anybody else I Never could have imagined becoming part of such a large family as rich says His oldest friends are here. I don't just think that he means his oldest friends are here his longest friends, but This is from 2007 and I believe these are Apache members in 2007 I believe I've had a meal with every one of them and With a number of people here and the family in the community is why the patchy is so successful So thank you and try to do things you never could have imagined you do Wow, very very nice Congratulations to Shane Shane that was great. That was really good What? Yeah, we did look a lot better back there in the old days, didn't we? Yeah. Yeah That's what happens with time. It just though is Mel here Yes, they're coming up So we'll do a little serious talk when we all you know, so nobody can wait But here's your tears up tears like the way Mel would like to talk about collective responsibility For open-source software risk so part of the model of foundations perhaps what he's talking about giving you a better experience Thank you. Yeah, that works so I feel like a bit of a corporate shill coming up here because I actually get paid to come to conferences, but You know, those are very emotional appeals From previous speakers and I think that it's something special about Apache that elicits that kind of emotion Right that being said, you know when we talk about open-source I think that there's certain Responsibilities that we have that I think that as a community you guys are very much aware of so First of all, I'm gonna fall back to things that you guys talk about in your your Apache way with regards to hats I have different hats, right now. I'm here as the open-source product manager for synopsis software integrity but essentially, you know Synopsis is a very large company, right? But software, especially in IOT has kind of spurred them to this towards this innovation Also, I'm the current administrator for something called co-varity scan So just as a show of hands who here is familiar with co-varity scan a Few of you, right and I think it's very much project dependent, right? So essentially since 2006 Co-varity scan has been providing static analysis to open source projects It's continued up to this today, and we have roughly 4,300 active open-source projects and about 19,000 developers Who have actually interacted with our system now the current Apache projects include Hadoop, Cassandra, Tomcat, HTTBD, traffic server, right, NiFi, Pig, Spark, Storm So some of the larger projects are already aware of what we can potentially provide and what does that mean, right? Essentially, what we're doing is we're helping open-source projects mature over time, right? And you know while we don't really get a lot of credit I'm assuming that the issues that are found are actually being remediated in these projects, right and Providing long-term stability for the end users, right? Now I'm going to switch hats, right? I think that you know as an open source Well as a beneficiary of open-source, right? I really appreciate that you know all of this developer effort goes into what is essentially enterprise-grade software, right? and I Think the Apache way and you know the number of successful Apache projects is a realization of how transformative collective collaboration Can be when developing software, right? But at the same time I think we need to acknowledge the role of users who actually consume and rely on the software that we produce Right, so software is imperfect. I think you know as a developer. We don't write perfect code It's not a realistic assumption that we can actually do that, right? But I think this is due to the fact that you know Software development is a largely human endeavor and we as humans are imperfect, right? So another aspect of modern, you know software development is the increasing complexity of the software we develop So, you know Linus's law, which is essentially given enough eyeballs all bugs are shallow is challenged by some recent Bugs and code that had the benefit of public scrutiny, right? So, you know, I think when you talk about risk in open source, right? It's not the quality of the software is necessarily inferior, right? But, you know, we can test so far, right? Edgar Deekstra's famous words are Testing shows the presence not the absence of bugs and I think that you know That tells us that risk is inherent, right? Regardless of the overall quality of the software and the development practice of individual projects, right? so Things we collectively rely on put us at risk and we can talk about, you know Heartbleed shell shock stage fright all those things that, you know, we've probably at some point been affected by but essentially, you know What we do when we actually talk about those incidences are things that, you know Their vulnerabilities that we we only know about but they don't actually give us any Indication with regards to preventing future exploitation. So, you know I only have 30 seconds left here. I think I I Put a little bit too much with regards to my content But essentially what I like is that this idea of maturity being part of the ASF's incubator project and I would like to Put a challenge out there or a call to action to, you know, subscribe as many of these projects that have High visibility, high impact, right, into scan because I think that you could benefit from it. Thank you Thank you. Thank you This is for you An incredibly valid point, um, you know Open source really is the way that the world is eating software So as much as we can do to make sure that our code is is reliable as stable as secure as we Hope and think it is. Let's take the opportunity to do that And that helps all of us because we're using the software as well as the rest of the world That's right. And it's a lot of other people who are using it. So a lot of people have been using our software in the past in the future All around the go way in the past So maybe you have some ideas about how far away back. Yeah, I do I do I've got some ideas about that You want to take it off? Is this a good opportunity? Yeah, I'll do that. I'll do that. Hopefully. I'm not taking anybody spot No, but How many Jim how many people here are familiar with the way back machine just raise your hand Now how many of you are familiar with the origin of the way back machine with mr. Peabody and his voice Sherman raise your hand, okay? And I'm not even talking that terrible CGI movie. I'm talking about the old school fractured fairy tales, okay For the next four minutes or so I'm going to be mr. Peabody and you will all be my boy Sherman Yeah, I love history. I really do. I think it's very very important Tradition is also very very important to me because history and tradition are what define and create a community Sometimes you codify that tradition and it becomes what we call policy But they're all very very important It used to a long time ago was a real comic book fanatic Loved them up until they started reconning everything like how Jordan was a bad You know green lantern and then you know Peter Parker was a clone and stuff like that forget it You know give me old-school stuff But the thing is about comics is that you can know everything you need to know about a superhero by their origin story Okay Batman his parents got killed spoiler. Sorry about that if you didn't know, okay, but wow that defines the character Okay, Peter Parker gets his powers a burglar runs away the burglar kills his uncle great power great responsibility. Wow So an origin story provides so much detail about things So I'm going to use the wayback machine and give you the origin story of a patching But 1994 1995 or so There was this web server called the NCSA web server bunch of people were using very very popular most popular web server out there Everybody was using it very very happily But then the person He was responsible for creating it Rob McColl Got a great opportunity to go off the Netscape. It was right, you know the same people who were doing Netscape The server, you know the NCSA web server were also doing mosaic they left We were screwed We had businesses Protocols all kinds of things dependent on a piece of software that was now completely Completely dead nobody was working with it not a single soul was working on it That's a terrible position to be Thank goodness There were people with the right mix of skills and talents and capability to basically be able to Rekick off that community which is hard to deal very very tough to deal But we succeeded And that was the start of the Apache group Which is what became the Apache software foundation, but the key takeaway from this is that we realized how painful it was To be dependent on a piece of software That could you just go in a second in a minute because there was no one around to maintain it And that's where our focus on community over code came from Because as long as you have a fully engaged community behind it No one else will hopefully have to suffer from the pain and anguish that we had to back when the Apache group started so Kudos for everyone for keeping the vision alive. Thank you and Kudos to Jim for still being here. God knows how many years later. I'm not gonna say no no no no kudos No kudos required Yep Sympathies maybe would be good. I'd appreciate some sympathies, but no kudos. Please please We have done we have done a lot over the years and it has been a long journey and it's been not just Not just the code that we give away, but the the model Yes, definitely think of all the other open source foundations that are copying what we do essentially copy-copy cat copy cat But we need to also spread open source around the world. You need to spread it like Johnny Apple seed So we have a patchy open source in China From at at Apache rocket MQ they in here They're our next fan Vaughn Gosling and Wang Zhe'arou No, I'm not doing a very good job. Oh my goodness. They're not here No, oh, that's your rocket MQ guys aren't here. I guess they're not here. Okay Terrible. Well, I mean we know a little bit of what's going on, you know in the open source in Johnny It's really a huge It could you know system for Open source really starting to pop up I mean if you look at some of the downloads of Apache software foundation projects Chinese most probably one of the biggest ones There is huge interest. There's huge uptick It's about getting it organized and it's about trying to take some of that culture and see how you can explain The culture of sharing here with that kind of culture there and definitely kudos to to Alibaba and Huawei We're helping to really push that effort inside of China. I know there's a couple Projects inside the ASF, you know sponsored and donated by both So please find them out and be sure to contribute back to them Yes, and one of the fastest Apache projects ever Apache rocket MQ literally takes your messages on Rockets transcontinental rockets and so them in an MQ, which is a Magic Q. Yes, which makes them go like tachyons like really fast So you get it even before it's sent It's really cool. So that's how you get your messages when you can send them across with rockets, then you So if we don't have a technical talk here, which is fine We have plenty of community talks here We have plenty of we do have community talks love of community talks here And I think the person knows who they are if I say the love of community. He loves community He loves this I love this community I need to say your name Daniel come on up Daniel come on up and tell us your story about please please and As he's walking up if everyone wants to get up and get a beer maybe take a smoke Bathroom break or something. Oh here he comes. Okay. Thanks. So just before we talk earlier today actually Jim said Oh gosh, I'm so tired. I could really use a nap. I think now would be a great time. Where should I do it? Oh Daniel, where are you talking? Thanks, Jim What's up everyone? Hey for those that I haven't had the pleasure of meeting my name is Daniel and One of the things that Jim pointed out actually in his talk just a few minutes ago is one of the taglines we have at the ASF is Community over code and he talked about the reasons why But the thing that I really love about Apache I get to kind of come and talk with Frankly the smartest people in the world, right? I have a slight confession to make I'm an infrastructure guy I've written code that's reached production in 13 different languages though so I'm like a closet developer and as we're out on the floor, I'm able to talk with folks and I'm learning that I'm not the only one that experiences the the highs and lows of writing code You guys know what I'm talking about right in like 15 minutes.  I can't believe I did that, right? so I Love it here because you know, we get to meet and hang out with a lot of folks that maybe we don't meet or see during our day job So what I would like you guys to do a little uncomfortable Think about some things about yourself And we're going to talk with someone that you haven't met yet look around pick someone out I don't know that guy or I don't know that guy and Figure out what you're gonna tell that person so to kind of get the juices flowing. I always do this and Come up with a few things about myself So here's how you may want to go ahead and approach the conversation And I'm going to give back whatever time is left so we can all kind of meet each other that we haven't met yet So hi, my name is Daniel this year. I taught a class on open-source software development at a local University thank you, thank you and Seriously, if anyone's interested I will give you the curriculum. That's the hard part. I want other people to do this Hi, my name is Daniel, and I really think we need to acknowledge this awesome new feather Guys, this is great Hi, my name is Daniel and every year when I head to Apache con I forget something But this year luckily it was just my razor so not so bad Hi, I'm I'm Daniel and I just got Accepted to be a member of the foundation this year, which is really cool Something else weird happened this year. Hi, I'm Daniel. I've got a college student now Wow So it's a conversation starter, so let's do that. Let's try that out look around the room find somebody you haven't met Somebody you haven't talked to and introduce yourself. Tell them something about you and we have a Minute and 45 seconds maybe even longer if we can maybe stretch the rules to do that so Go okay, so let's wrap it up Don't stop the conversation though Keep talking keep hanging out everybody smile So thank you guys. I I love that we just kind of grew our community And and there's one last thing. Hi. I'm Daniel and I love this community. Thank you guys Thank you. Thank you Daniel another reminder of This has been sponsored by Capital One. There's still more beer left more soda to those snackies over there Beers and snacks. Oh my goodness. So be sure to indulge Enjoy yourselves have fun This is supposed to be a happy occasion. Yes. Oh my goodness. Thank you skinny pop pop delivery service carbs. These are carbs Weren't you listening? But this is we try and help But our community is is people and that's the most important thing But it is codes important too. I mean, that's what gets us here. That's what gets new people here It's the glue. Yeah, that solidifies this homogeneous lovely nuket filled mass of people is the code Okay, well, we'll take your word on that one for Jim So let's switch it up and do a little bit of technology with will about Apache Edgant That sounds like a TV show technology with will Yes, the will could come up. I hope wills here. We're just we'll be awfully. We're okay. Yes. Yes, and His hockey. I think it's going to be edgy. Isn't it? Totally edgy, right edgy. No And thank you. Thank you very much. Hi everyone. I'm will I'm a committer for Apache Edgant And it kind of sounds like it's Apache committers anonymous up here like hi. My name is will I'm a committer. I One time committed code without running all the tests. I don't know but um So yeah, Apache Edgant.  You barely finish in time Congrats, and then the next month you get a bill in the mail for $70,000 because you are sending Raw video feed over a 4g connection to put that a different way $70,000 is about 8,750 Chipotle burritos, which is a lot So the point is there are a lot of streaming technologies out there But a lot of them are designed to run in a cluster So you wouldn't want to run spark on a on a phone or at least I haven't seen it. It wouldn't run a You can like write a Kafka connect What do you call it client on on a phone? I guess but um the point is there are a lot of operations which need to be run in a Streaming manner on edge devices on things like bones on things like raspberry pies and By streaming I mean the way in which data is consumed from devices that might not turn off for for example, if you have like a temperature sensor that's looking at the the temperature of an engine and If if the temperature goes too high then you like turn off the engine But the point is you can't wait until all the data is there because it doesn't turn off You have to consume it as it comes in so that's sort of the idea behind streaming and this needs to happen In a streaming framework at at the edge and this is exactly how edgent is positioned It's an it's an IOT framework. It's written in Java. It runs on the JVM So it's supported on Android devices that runs on raspberry pies really really anything that has a JVM And it does data streaming For example the kinds of applications you could write you could create a smart microphone something which only sends Sound information when the decibel level goes high enough like like when somebody's talking on a microphone And you wouldn't want to send data otherwise because then you're just sending Uninteresting information you're just you're paying for every kilobyte that you send over a network and you need to do streaming processing beforehand for example streaming processing could also be like windowing so if you you need the last like Three minutes of data and you need to do some operation on that pool of data if you wrote that yourself you'd It's a lot of boilerplate code that we aim to remove the developer from and in addition There are so many ways in which you can talk to a Backend from from an edge device for it. There's mqtt. There's Kafka. You could use a web socket rest That like just raw sockets if you want to go that far So edging comes with a lot of connectors that you can use to to talk to your back end So that's more boilerplate code that you don't have to write but Yeah, I guess That's all I really wanted to say but check out edging. It's it's it's a cool incubating project and Save the burritos. Yeah I Thank you edge devices. I think are kind of edgy obviously you didn't get the pun Yeah, I don't think anyone got the pun so it's a it's an aptly named device And I'm not gonna stay any pun about the name of their you won't he's allergic to puns makes him break out in hives so we Well apparently for years we've been doing lightning talks I've been either helping or giving them yes, yes, yes, yes And we often have to we used to have to go out and sort of beat people not not literally no literally literally we have to do that To get them to submit and there are some people who I've asked regularly for doing lightning talks And you know either they can't do it or they're busy or this doesn't work That's okay, but I would like to say I would like to welcome. Oh, no, what it's not Not him. Yes. He's not doing one. Is he? Well, I gave him the title so oh my god, no problem. So I'd like to buy my Henry. This is an historic day Oh my goodness. I would like to welcome Henry yandell and the title of his lightning talk is Thank You Henry for finally doing a lightning talk. Yeah Thank You Shane So yes every ten years for the last ten years or so Shane's asked me Can you do a lightning talk and my answer is always I haven't prepared anything?  You need to start thinking of yourself as an open-source recruiter Look at people who do recruiting for a living and say to yourself. I don't want to do that. I don't want to act like that I don't want to do that as my style, but how should I be doing that? How should I be going to a Contra a contributor potential a community that's near me and lure them into becoming part of my project Ask them. What do you want to do with my project? What changes would you be thinking of?  Thank you Well, thank you Henry That was Well worth the wait. That was well worth the wait very very insightful really and the Best lightning talk in the shortest amount of time. I've heard because usually we tend to you know Some of us tend to take a lot of time some like when the year I you know, right you got thrown off stage because I wouldn't stop talking That's right. Well, I mean it's because we take pride in what we do You know we're not going off the cuff like that. So that's that's what it is. It's just that that level of Professionalism that we bring to this solemn event. Yes, I think that's exactly what it is. I think what I really enjoy Cashew clusters. I love cashew clusters. They are the best kind of clusters of all I cannot imagine any kind of clusters that could possibly I see where you go. It is then cashew clusters. I dare you You suggest something that could be better than cashew clusters. I mean you're gonna dare somebody Daring it's a dance double dare go ahead The sun will set try upon your premise because at here at Apache we have a better cluster solution No, yes, we have an entire stack of them To the clouds It's called our very own Apache cloud staff And we actually have somebody an expert who's gonna tell us really cool stuff about how cloud stack does that stuff and Cluster management and all that kind of stuff if Dan is here I want to hear more everybody does right right, right? Yes cloud stack cloud stack is is of all those big things Cloud stack is the the project that has the code and the people in the deployments But doesn't have the marketing budget of some of the other people, but better in other every other way that's gonna change tonight Let me correct some things Apache cloud sec doesn't do clusters Apache has a project for that. It's called maces and What will actually plug-in was written for cloud sec lately By shape blue company that I recently joined. I'm not gonna spend more slides on them now Which is called container clusters It's using Kubernetes and the idea come from that that we need a more generic solution for all types of Clusters not just containers, but also well also maces of course, but also Hadoop or Galera or Seth or maybe some SDN kind of application or maybe your application that you define with five kinds of roles in a multi-tier environment and you can just Define those roles in cloud sec and then start them up and Okay, all this is not there But the start is there and there's a functional spec and I want feedback on that so this Is kind of a question to all of you to go to the wiki to the C wiki and then find application cluster service look at what's there and see whether your project needs something like that or Whether it doesn't apply and you need something else and leave a comment there, and then I'll look at it and then We're gonna implement something great Because that's what we do so I Think that's that This was very lightning right Lightning enough that was very late. Thank you guys Well Shane has proved me wrong there are better things than cashew clusters application clusters with cloud stack color me chagrined What color is chagrined is it is that like mom? Kind of like that, you know a little bit with sparkles. It's you wouldn't think it'd be with sparkles But it's with sparkles. I could do sparkles. You know you wouldn't think of it, but I could So we some of us do and I'll say me sometimes I like to talk a lot and Apparently we've been talking too long and our very nice producers are warning us that they really need to get us out of the Room, yeah, we'll have one final speaker one final one and then close our evening one one and I Don't know. I want I usually say thank you for attendees, right? Yes Yes, but Nick Burke is going to talk about Nick Being thankful for things being thankful for coming to Apache con Speaking Apache con for being part of our family in our community. Thank you. Thank you. Thank you. Perfect Thanks There's a lot of things to be thankful for here not least the beer. Thank you. Jim and capital one for beer Another thing we can be thankful for is new experiences at the event. So Who here has met someone from their project for the first time? Let's be thankful for that Who here has learned about a new project? Come on. Are you saying that the rest of you without your hands up had never heard of edgant? Let's be thankful for new projects Okay, who's Reported a bug either for the first time or the first time to a new project new bugs Who's contributed a patch This week Yes, we've had some new patches this week to patches Who's given their first talk? Who's made a new friend? Hey Who's visited a new country coming here? Who's made an introduction introduced someone to someone else? Who's been sprung on when I've made an introduction of them? Sorry, it was good though Okay, who's felt their passion recharged by being here who's eaten something new and Finally, who's told someone else not here that they've really got to come next time You all need to put your hands up come on So To next year to new friends to Apache. Thank you. Thank you. Thank you very much Nick That is a perfect ending almost ending to our evening. We have the fling of the night The fling of the night right here for all the speakers. We have our special one Yes, one just raise your hand. I will try to get and we have a few extras So if you want one come get it now. Well, and you would Jim and I would be happy to stand up here and just throwing them around Well, okay, as long as they're not the plague for God's sake have been there We'd be happy to We'd be happy to speak all night But I hear that our producer friends are gonna have the hotel. Don't forget there are boss tonight as well Yes, so You know we went a little long. So there are people who don't have So there is a sign-up sheet over by the registration desk There's a whiteboard over there that lists all of the buffs and the location that they are in So, please go have a look Admire Trevor Grant's art you on the whiteboard and pick a talk to attend Okay, buffs are the next hour or so and there's six really really good ones So let's move on to that with our beers And we see you all pretending there are no keynote sessions tomorrow So thank you all so much for attending if I don't get a chance to talk with you again Really appreciate you being here come again next year


All right, let's see how many people we got 7 people here. Let's wait like 2 more minutes before we get started. Christian is here. Looks like there's a network issues. Yeah, let's wait like 2 more minutes before we get started. And if you notice, I have a hack and D. Link in the discussion. And so that's. Um, an attempt to create sort of a linear documents of an agenda and that I think will. Um, be helpful folks to have that on hand. Could could we add in attendees to that as well? If you want, absolutely. All right, so that would be good. That's really all I have been tracking in in actual notes. For each each event everybody. Hey, sorry, I haven't been I couldn't make it the last couple of times, but now I finally got my OKT T-shirt. And I haven't gotten one yet. It still hasn't been to Canada. It got to Germany and it hasn't come to Canada. I'm going to arrive today actually. Yeah, my guy here is sweet. I also got mine fits perfectly. Yeah, it's awesome and we will get more of these. So, if someone's coming on and they didn't get 1, don't worry. We'll put them in the. In a work, a LinkedIn store that you can a linkable store where you can self service and get them. So, there you go. Some day we'll have a meeting where everybody has an OKT T-shirt on. All right, well, looks like we've got enough folks here to at least. Get rolling here. So, again, there's a link in the. Then I'll post it again. For anyone new that joined, please put your attendance at the very top of that. And note, or what you represent.  So, let's get started with some quick introductions. I'm Jamie and a member of the working group for over a year now, a year and a half. And using OKD in University of Michigan various environments in the University of Michigan. We'll be spending up probably later today a cluster that's going to be used for a couple dozen developers doing data. Heavy applications in the political and social sciences. And anyone else want to introduce themselves? Diane, maybe we'll go next to Diane. I'll go next. I'm Diane Neeler, the director of community development over at Red Hat in the cloud platform BU and 1 of the instigators and chairs of this working group along with everybody. So, I haven't been here in a bit. So, I'm Christian Glombeck and I am an engineer. In the open shift arc in within Red Hat. And I've also been one of the co-chairs of the over the. You want to introduce yourself. Hey, so I'm Timothee Arvier and I work at Red Hat on the Federaq Chorus, well Chorus team, which among other things, does a lot of the work for Federaq Chorus. Bruce, you want to introduce yourself? Sure, you know, I was just trying to sign or put my name in the document unsuccessfully, even though I logged in, but I'm Bruce Link and I'm just a user. I teach at BCIT and managed to put several students through the experience successfully doing projects and things like that. So that's been a lot of fun. Joseph. Yeah, I'm Joseph Meyer from Germany. I'm working for Odeon Schwartz as a cloud architect and I'm an OKD user and support is since more than three years now. And the man who needs no introduction, Vadim. I'm Vadim Blukowski and my webcom is apparently broken. I work Red Hat, focusing on upgrades and release activities for OCD. Excellent. Neil, do you want to introduce yourself? Yeah, hey, my name is Neil Gampa. I work at Datto as a senior DevOps engineer, focusing on software delivery systems, including source code, package management, container stuff and things like that. And, you know, I'm here in the OCD working group, working as both a person in Fedora and to a lesser extent a person from Datto to do awesome things with OCD 4. Excellent. Anyone else want to chime in that we didn't get, yeah. Tree, you want to say hi? Sure, I can say hi. Yep. Hi, everyone. My name is Shreer Manajam. I work with Neil at Datto as a senior software engineer. Working on various products and services that are, you know, built on top of our in-house Kubernetes and open chip clusters. So. And I'm also here as an interested hobbyist, especially in like the home lab states and looking to expand OCD's presence there and sort of bring up its cache and that community. Oh, yeah. And Shreer is a master of disaster recovery. I'm led to believe. Did you get it back up yet or no? Well, the cert thing that that other person mentioned, I don't have his name right now. It didn't work for me. So I just blew it away earlier this morning. I'll re-spin it probably after a week. Oh, you haven't responded yet. I was, I was wondering if you'd actually brought it back online after everything fell apart. No, not yet. After work probably. All right. All right. Well, let's jump into the agenda items. I do like to have the intros because there's always going to be people listening or watching that aren't familiar with who we are and what we're about. And again, OCD is the communities, Kubernetes community supported Kubernetes technology that is supported by a very. Interesting and lively group of individuals from a diverse with diverse backgrounds and it's a real fun project to be involved with. So let's get into release updates with Vadim. Sure. So we didn't release for a release candidate this week because the code freeze is planned to be happening this week or next week. Once it happens, we'll release a new release candidate that it shouldn't have can changes, just a bunch of bug fixes. So if you could give an OCD for a try, that would be very appreciated. Meanwhile, on for seven, we released a new stable release. It the main highlights of it is that machine OS moves to the door 34. And we might have an upgrade issue number 668 affecting for seven to to the latest stable upgrade. I was still looking into that seems like we missed including one package. And the most concerning part is that it was not called by CI. We'll do our best to fix it quickly, see if the workaround is feasible. If it's not, we'll move to a new way of building machine OS content for a release patch release. The issues that also we're seeing quite a lot of table clusters of greatest release version, something about 16 telemetry. So we'll need to figure out more information about this issue. So if you could give an upgrade a try on your test environment and reply to this bug, I would be very appreciated. I think that's all we have from the technical standpoint. Okay, great. And we always like to bring our, our friends from fedora core OS on to give an update on that so Timothy, Timothy, you want to give us an update. Sure. So, right now we have two items on the agenda. The first one is about system D, which is a new part of a new demon, I think from system D that is being introduced in federal 34 if I'm correct. And that is not yet enabled in federal chorus by default. And we're looking at whether it makes sense for container workloads to have that part of the system. Just to give a short of you, I think the system view on D essentially is is a is a demon that is using the new secrets be to and PSI interfaces from the common to figure out which process it should kill in the case where the kernel of the system lacks memory is under pressure and so she essentially on okay D. Well, this might have this consequences. Maybe we don't. Well, we don't we don't actually know if what would be the consequences of using that that in okay D. So yeah, the idea is to bring that out to your attention and trying to figure out if we should enable that you should remember that by default. Of course, it could be enabled in federal course but disabled in okay D to so, but well if, if it doesn't generally makes sense for container workloads and we just probably won't enable it at all. And well, this is like the right time to gather feedback if you have any on this issue. That feature seems to be very useful but now it won't affect us because it requires the group. And it's not clear if it would be default and for nine even. Another problem is that it's probably undesirable in various world because the few blood cannot read system D events to find out if your pod has. Oh, and that reads kernel events.  Again, we would need to work upstream in in communities to reconcile this two approaches until we can enable this by default. So what we can do now is to to stop depending on on Fedora course decision on this really and just disable it in our custom payload. But that's probably the input from the okay D on this. All right, well that's that's great. I'll pass us forward to the records teams. Right. And in the chat James is asking teach KS to talk to omd or vice versa. So there is a when you Google this cubelet. Oh, and there's a talk coming up by a redhead employee that is mostly about secrets. So maybe this is Giuseppe. And so maybe we should just be getting his opinion on this because he probably knows a lot more than we do about this whole complex. Okay, does someone want to reach out and. And gather some information from that person or at least maybe invite them to. Come here and talk with us. I'll reach out and ask whether he wants to join next, next time. Otherwise, I'll just ask him to give me a few words about sure. Awesome. Thank you. Right to see what's next. Yes, the single nighting is a little bit more like forward thinking thing, because it's about 35 so we've just we based for the 34. So it's not coming right away. It's coming in approximately six months. And it's the right time I would say to look at what's going to change. And see how it might impact. So the, yeah, we essentially the changes that are going to be certified and so far we haven't identified anything. So that would be strong. I'm just going to mute other people and unmute yourself. You need to. Okay, go ahead. All right, so federal certified sentries mostly nothing stands out so far, but we're tracking that and the federal change process window is not closed yet if I'm great sir. So yeah, this is this is ongoing. And that's mostly it for me for federal careers. There are any questions. Any questions. Let's write that Fedora. Of course, 34 is coming in half a year but is used now in okay D. No, no, we've. So as the team said, federal careers based on federal 34 is coming right now in okay D just right now is federal 34 has been released couple of weeks. Okay, thank you. And so yeah, we finally finished all the rebates for federal careers. And right now we're starting to look at Fedora 35, which is coming in approximately six months. Okay, thank you to make sure that we catch up things before they happen before we can provide feedbacks for everything is in fixed. So the looks of the changes that doesn't look anything would break us but I think there was a good practice which we applied for for eight release we our machine OS content has been using Fedora's next development stream to fetch the latest changes which would only land and stable in a couple of weeks so we can catch them and the installer for for eight is also currently using testing. Requires rather recommends you to use testing ice. The initial Fedora cross images. So that we would change check that both of those are perfectly valid once they land and stable. I think we'll, we'll do the same for okay you for nine or for 10 until it becomes stable. So that we could verify the changes I had that has in pretty valuable as we caught quite a few regressions were able to report them before it lands in for seven or in for the across table. Anything else. All right, let's move on now to issues. Let's take a look at our issues and one of those is that I wanted to highlight actually before we get into sort of the general overview of issues is. The operator wish list so this came up in conversation in an email thread. Do you want to summarize that the email that that was sent to the group and sort of explain your response to that and maybe also Christians response to that. About the operator wish list or. Yeah, you know that we received basically asking for clarity and for documents change. In regards to what was actually available. And what was supported and whatnot and there was actually a okay D document change because of it. Right, that's because, for instance, we had to repel some parts of the documentation because those are logging operator is not directly available and no kitty. And while we are in for folks to create a new kitty. A catalog for the operators to start pushing the upstream versions of that we would have to remove some parts of the documentation. I don't think we have any estimate on this yet but will be it's because effectively out of our hands for we. What we need is the collaboration between various teams to commit to supporting those in no kitty isn't. Supporting by community nevertheless not redhead support but nevertheless it's still some level of commitments required. And once it happens we will be able to bring those parts of the documentation back. But until then we effectively have to remove them. And tell folks that they unfortunately have to build those operators manually or look for alternatives and community. A catalog we have and that's basically that's the current state. Good day are like a few probably months by now back. We talked about having an OKD specific catalog just for OKD has there been my question is, has there been any development on on that side. I haven't heard any. It's mostly the talks between the teams. They want to ensure that we don't plan additional work on them. But still this catalog gives them benefit of well community support. It appears that technical part of this should be trivial. It's just a matter of ensuring that the teams actually commit to supporting those versions of the operators before they land in the official redhead operators or. Or they want to develop entirely different community version. It's just a matter of how they would structure their work. Creating a catalog itself is fairly trivial. It's just a matter of making teams commit to that. I wonder whether we should be setting up or just helping the people that would do that set up this catalog. So we have something the respective teams could then release to not worrying about, you know, this kind of like it doesn't even exist yet. And also I think, well, while this is probably more internal, the management has now given them more clear. I think mandate to the teams to release to the community catalog or release a community version of their operator. So maybe if we kind of make it as easy as possible for them to actually release the operator that will help with that process. One thing that I was thinking about is when we talked about this at the time and I put a link in the chat to the particular issue that Christian created. We've got the wish list, but we don't actually have an explanation of what needs to happen. We've got them categorized currently unavailable available in community, etc. Is it possible to maybe put a little explanatory text in that issue as a comment or we create a separate page that's like, hey, this is actually what needs to happen for these various components to come together so people can understand what needs to happen. And then also we can look at timelines and also for the people who in this group or who are interested in OKD development for them to get started on this, maybe some tips to provide them some guidance as to hey, you know, someone's like, I would really like to see this operator in OKD. Well, it needs to be rebuilt. There's some general place to look about how to do that or something like each repository for each repository for each operator is going to have specifics but it might be nice if we inspired people who are interested in OKD to take this on by giving them a little lift. Yeah, well, probably we should regroup them into two major groups as an additional order of attacks like maintained by Red Hat and something like others. The problem is that why we can submit logging operator, for instance, into the community operator because is that OCP users would see them duplicated. They would see official Red Hat's logging operator and one coming from community and they would be very confused by which one is actually being supported. I think that was the main reason. Engine separator. Have your KD catalog, right? Yeah, exactly. But there is an engine separator, which is totally fine to submit to stream operators and community can start working on this right now. And it's already listed in the wishlist. So what we need to do is to review the list, find a list of things folks can start submitting right now like engines. And I think a video operator or maybe I'm wrong. And after careful review, we can start. We can find a documentation on how to submit, who wants to take care of it, how to hear the responsibility. Should we include these kind of new wishlist items into these meetings or who would maintain them? And so on and so forth. The other internal Red Hat operators, they would need a bit more work because there is a whole team behind each of those. And we need their support and they would be maintaining it without OCDs or group kind of requirements and such. Okay, well, let's put this on the agenda for the next meeting and in between now and then if folks could think about how we could organize this.  It'd be the main group and we'll talk about in the main meeting, but how we can move forward on this because it's been lingering like Christian, I think, published this in January. Like so we have a list that we can start working on. We can be adding stuff to it as well. If we start moving on it, I think it makes OCD more attractive to have because some of the ones in there are pretty significant, right? And it's things that people are really looking for. So I think one thing that. Oh, go ahead, Christian. Yeah, sorry. So one thing I think that the community can definitely already get started on is looking at the currently unavailable operators and all of those which aren't in the open shift organization. Or even the open shift K native organization. So all non redhead operators. Those won't be released by us anyways. So, and those would be going into the upstream catalog, I guess, or if they're, if they're really made just for open shift, then they would go into the community catalog. But any of those all of those operators that aren't owned by redhead that are currently are unavailable. Those would definitely be good candidates for the community to look at them and add them to the respective catalog on operator hub. There's also that there have been some changes recently to the operator hub so people can more release new versions by themselves without having an admin from the operator hub repository. Have to acknowledge those changes so that there's going to be, I think, owner files for each operator. So when you submit an operator, you'll become the owner of it. And then you can also update it without anybody else having to acknowledge that from a third party. So maybe if there's interest within the community to get one of those operators released right now. And all the non-rated operators would definitely be good candidates for you to look at for us internally all the. Operates that haven't been released yet. We obviously want to get them released to okay or okay by the respective teams. Yeah, we can also take some. Excellent. All right, so we'll put that on the agenda for, for our meeting in two weeks. I'm going to talk about this more and have fleshed it out a little bit more and probably put in a separate page as opposed to this issue. Actually, maybe put an okay D page either on the website or something like that. That we can actually edit in line as opposed to just adding comments to etc that that we can improve upon and update the list and whatnot. Moving on, are there, there's a new issue that was submitted. Vadim, do you want to talk about this?  Looks like it was submitted an hour ago. Is this the documentation one? Yeah. Yeah, so I was going to talk to that just quickly. We just spent the prior hour to this meeting with Bruce and Mustafa Mustafa from elderberry from red hat and Bruce from BC it. And this is I'm just bringing it up here to give sort of an example of. Of how we're working through. The docs.okd.io to find defects in the documentation and report them back. And so we've we've done our 1st pair pair, not programming, but pair review. And we're trying to document the process and there is a recording that will I'll put up as soon as I figure out what the YouTube issues. But this example and I'm just going to share my screen. I'm just going to grab 1 of them here and I'm just going to share the troubleshooting 1. Is the process if you find a defect or an issue in the documentation that we're we're using right now. And we'll we I will document it in a brief blog post on the okd website. And as well so basically just finding the section and we're reviewing it with Michael Burke who's I don't think on this call. The documentation team for open shift. And so this isn't about actually fixing the issue so in some examples there are code examples that need to be reviewed and retested but this is a good way of make sure you put the bracket okd in the the subject line. Put the link to the section that the issue you're finding in and then potential resolutions. And if you don't have privileges like most of us don't to assign this to somebody that slash assign at the bottom of my screen there for Michael Burke and myself will allow us to track it. And at the moment I don't have privileges to add a label to it. So I'm going to work on that I'm going to double check with Michael he may have privileges. But there are two labels that we're using one is okd dash only and the other one is that it's documentation. So there's another label in there for that. So what once we figure out I don't think you can assign like you can do the assign a person to that I don't think there's a slash label function and GitHub to do it without privileges. So this is we're going to start working through as many of the issues I think Bruce we found like there's 20 references to our cause in the okd documentation and so we're going to use that to flush out all the issues and then move towards doing that. So what the ask is for this group is if you find something especially right now we're focusing on the docs.okd.io. If you could use this approach to tagging them and I out for them and we will do this and try and work with the docs team to make sure that with each release there's a process in place for these things these patches to be applied correctly. I'll stop sharing if anyone has any questions, but that's that's what that issue is. So you'll see a bunch of them pop up on the issues list. And right now they aren't properly labeled. And that's that's my issue to figure out this week. Many issues. All right, it's that the the okd repository. Because I seem to be able to edit labels on that repo. You have more privilege. Yeah, I don't know why that's repo right. Yeah, I don't I can add stuff, but I can't edit that so I'll figure it out and maybe in the interim if you can take those ones and just add okd only label and the documentation label to all of them that would be helpful. But Mustafa is going to keep motoring through and working with Bruce. And if other people want to get paired up with someone, Mustafa, if you recall, is one of the newbies to the the red hat open shift team. And what we're trying to do is pair people, the newbies up with external folks who have used and deployed okd so that there's some life experience lived experience going through this. And then once we figure out this process and get a few of them through there, what I want to do is set up a hack the docs. See, you don't have privileges either. See, it's not just me. Christian does can add them. So what I'd like to do is sometime this summer when everybody's feeling fine is to do a hack the docs day. And hopefully we'll catch everything in the docs.okd.io and then move to like the guides that that everybody's created and the actual read me files and take on each of those using the hop in platform. Because that's what I want to do on my summer vacation. Excellent. All right, I put a little note there. Mentioning that Diane is going to organize the hack the docs day. So we can look forward to that. The next thing I want to move to is if you could give a quick couple sentence explanation of the. Good first issues label and what that means and what your hope is. Right, so we've been. Looking for easy bugs for community to get started for quite a long time and when we wrote. A log bundle issue of notice that. Paying some missing there, for instance, we're using additional services to update from Fedora Chorus to OCD specific. To get a specific payload. Normally, those are not a problem, but when things break, we would like to get logs from them as well. So. A few issues to fix that have been packed and these are mostly touching the installer and our fork of it. So it would be very useful for community to get started with building their own installer. That would effectively spin up a new guide how to build your own OCD installer until it merges in upstream. And we would add. Some more services to collect using log bundle and. Well, it picks up this item to verify meaning break their cluster collect log bundle and ensure that all the logs are in place. So this kind of a small things would help us write better guides and explain how all things are interacting with each other. Hopefully this would affect the troubleshooting the bootstrap. And log bundle analysis documentation and so on so forth. I think that would be a great starting point for folks to understand the complexity of how we build the system and how we analyze the problems meaning log bundles and math gives us are essential for us to collect all the information we need to find out all the details about the bug. This might be something that the group could take on as a regular section of our meeting or a subgroup could meet to basically like go through these and sort of bootstrap each other into, you know, because a lot of these involved little bits of knowledge that maybe one person has a little bit here one person has a little bit there. And maybe someone needs a jumpstart just to be able to dig a little deeper and help out. So it might be worth us thinking about how we could as a group sort of approach these and share a little bit of information to get people bootstrapped into being able to help as sort of group developers or group support people or whatever. And this sort of runs into that concept of, we talked about at the last meeting of having basically people who have who commit themselves to being supporters, basically like supporting, you know, questions and whatnot and that specifically make themselves available, or say that they will specifically be active, right to do that. So any thoughts about. Yeah, perhaps we could suggest. We could have an open floor ish style of suggest your own favorite paper cut or an issue. So there we could file it. I could help with if it touches some OCP part that could help with filing a proper bugzilla ticket and driving it to the team. So that we could see how it gets fixed in master or release for a van gets every fixed for seven and explain how how soon do we get it and how to how to interact with other teams. Probably that should help us fix a bunch of things which are left behind but very very easy to fix actually. I would also suggest that what we're doing with the docs, the pair programming or pair reviewing process might be a good way to flush out the workflow around these, what we need. And they may all be different because they may be, you know, something may be a fedora corals but I think if we do, if we have those tagged now. We could use the same team of group of folks that must have us coming from the newbie Red Hatters to pair them with external resources who are willing to help mentor them to do some of these first. First paper cuts. Maybe motor through it that way to get the process flushed out. And I'd be happy to do facilitate that. So do we have a bunch of first cuts listed or first I'm calling them paper cuts, but because you refer to them that but as a label. Yeah, there's a label. There's like five of them right now. Yeah, or five. Maybe what the thing is is to reach back out to forget who the team lead is for Mustafa and see if we can get a couple of those five looked at by that team. One on one and pair them with whomever is appropriate externally and then see who's missing because that's what that's where like Michael Burke came in with the docs he understood the workflow for docs. Wow. Some of these are pretty like, like so for example I'm looking at the one that's that's ownership of the authorized key. Like that's something that we should be able to look at pretty quickly, you know, and just figure out, well, okay, how is this how could this happen but you know, I don't know. All right, so let's put this on that we've got 18 minutes left and I do want to make sure we have time to get to all of the other things without rushing the other folks that are reporting in. So let's put this on the agenda for the next meeting and sort of flesh out ideas and sort of be prepared to to move forward on that at the next meeting. I admit folks can chip in on those. And again, these are, these are issues that are tagged in the okd repository with a good first issue label. All right. Is there anything else in terms of issues that anyone wanted to bring up the team or Christian or anyone else that you want to bring our attention to in the in the submitted issues. No. Okay, and what about discussion items so we talked before about subgroups. And do do we want to start documenting the proposed we've got these ideas for you know people that would be supporter like dedicated to doing support and what not should we create a spreadsheet of some kind and start having people. And basically submit their names and what it is that they'd specifically like to help with. Does that sound like a good way to start. Just as people log in each time put who you're affiliated with and then maybe underneath that put what your interests are and contributing in the community. Or is that too much do you think for people to put into into the document thoughts. Now, okay, I guess no one has any particular opinion about it. So, let's do that at the next meeting we'll ask folks to put not just who they're affiliated with but also what part of okd they might be interested in. So maybe at the top of that document, we can have a list of ways of like some labels that would be, you know, ways to participate and then people can just sort of list those under their name and ways in which they might be interested in participating. So give it a shot. We'll see how it goes. It just seems like a good way to start forming groups and knowing who wants to do what and keep track of that right. We already talked about system and any other discussion items that folks want to bring to our attention anything else that was submitted that was submitted in the discussion section of the repo that you think we should pay attention to in particular. Actually, Jamie, I just have a comment on kind of the whole subgroup plan, which I think is absolutely great. I do think that that's going to help focus people on a specific task and get that task done more quickly. So, in our charter which we wrote at the very beginning of this working group, we already kind of had the idea of sub working groups. And there's a little section in the chat about that. Just to link I linked it here in the chat. So, yeah, I'll put it in the dark as well. So, yeah, just, I just wanted to voice my support for the idea in general and there already is kind of a process, although we haven't flashed it out, I think, of how to create one of these groups or get it started. I definitely appreciate this. Absolutely. And so I'll reference back to that and then build on it and sort of weave that into the next meeting starting with the next meeting. Excellent. And if folks want to chip in ideas and hit me up between now and then have discussion about it, please do. This is a group effort by all means. Any other discussion items that folks want to bring to our attention anything that was submitted in the discussion section doesn't look like there was that many handful. Okay. Just a short question the inside feature that shows up in OKD is overview on the web console is this. Yeah, does this feature do something or is this just a remainder of OCP feature. It's an inside separator which if you have red heads full secret would collect data from your cluster periodically and save it in red heads servers. Just a small subset of data, which is very useful for us to identify problems early. Again, if you don't have a valid full secret, there is nothing to upload rather you cannot authenticate with the red head server. If there's been some data uploaded it can also give you your recommendation. There's R8 GB which is too small and things like that. It kind of does not apply to OCD, but that gives us a valuable stats on how people are using the OCD. And that's the only stuff we have meaning we are very tempted to use it to make valuable decisions. For instance, there is a bunch of four or five clusters. And barely any for eight clusters live. That means we need to push for a advertisement on every single meeting like that so that people would give it a try. Is it representative of what people without the full secret are using. I don't know we don't have any data for them. So that's that's basically what we've got. Is that thanks providing the telemetry you talk about when we do upgrades, or is that something else. It complements telemetry because telemetry is actively sending things rapidly but insights makes a snapshot every couple of hours do or maybe four hours. And telemetry is able to send metrics while insights is actually making a snapshot of control plane objects and anonymizes them and sends us here. So we get some information based on metrics for instance we can kind of find out your operator state based on metrics. But it's a bit tricky. And if we want some more details, we look into insights archives because those are actual snapshots of the project. Okay, and well, but it doesn't work if you don't have a full secret. Yeah, again, everything. The insights operate is essentially just the client side of this. Then send all that data collect to go back and that redhead has. But I'm not sure I'm not even sure there's a an open source repository for that. I'm not sure how you would use this. If not for the only use case it has sending the data back to redhead. And obviously that only works if you have the right full secret, the official redhead full secret. I mean, I'm not sure. I mean, it's definitely helpful for our SRE team. I think that's a big data source for them. But yeah, I was, I've always been wondering whether we could kind of make that warning of that noted notification that you could connect the or install the insights operate inside more data that we kind of don't have that show up on OKD. But on the other hand, you could also use a redhead full secret and install it on the OKD cluster and then send the data to redhead. Although probably nobody has done that so far. Yeah, Christian, I think and Vadim, it actually would be helpful. I think if somewhere it was written down the precise boundary of where you could use the redhead full secret and not. Because I've heard many things informally. And certainly, like, you know, anybody that has developed redhead developer account, which is anybody can get one that's valid for 60 days. And then seems seems to continue to be valid after that. And there are some maybe mysterious way where you can say that you're self supporting or not. Anyway, the like that. That touches the topic which I don't really know a lot about which is subscriptions. So all of that is outside of our reach. There is a service in in front of all the redheads. Which we maintain internally called do both. And what it does is it effectively validates the full secret and tells us to this data proceed further or it needs to be thrown off. Right. It might be ready a Diane issue. Yes. Well, there was a nice talk about subscriptions recently an open shift to be. And it's slightly different from engineering standpoint like. Are not set in stone. They can if you're a educational for instance facility, you can ask for a subscription which enables you the sale of supported stuff. Good luck with that. Well, yeah. Actually put in a request a year ago. Hold on. Let's let's we have seven more minutes and we do want to get report from the docs folks. We will investigate. I think subscriptions and that boundary for pole secrets. We'll see what we can find out. Let's add that to the list of to dues. Okay, so we have Joseph on the call and I don't see Mike, but I know Joseph and Diane both have things related to docs and outward communications to bring to our attention. So take it away folks. Joseph, you want to go first and what you have so go for it. I have to admit that I was not was not in the docs meeting at the last time. So no news from my side. Okay, not to worry. And I think I pontificated a little bit earlier in the issues section about what we're doing around docs and and trying to tag things and create a flow around the docs. Okay, the dot IO. The other thing and I will create use Joseph your blog on the site to create a little documentation around that and awareness for that. The other thing I think I added it in the lower section. Let me just popping between things. We did update. I'm not sure anyone noticed in Slack. The community support texts at the very top of the open ship dev and open ship users to point people to the OKD working group for community support. So that's key. And I mentioned in the chat on the side on June 25 post red hat summit. I'm gathering we're going to take a number of the end user stories that people that were pretty popular, including Joseph's talk on OKD to Azure and restream them live on open ship TV with sort of a mystery science theater approach. So we may pause them and put in new references and things like that and updates. And if you're if you're around and you want to join us, the link is embedded into the notes here. And we'll be dreaming. I think it's about four hours long. But there were some awesome talks. Interest identification of members is the other thing here. Not quite sure what you meant by that Jamie, but I'm the OKD working groups doc subgroup meets every other Tuesday at the same time as this one. So if you are interested in joining that group, same time, same place one week later. Sorry, that was connected to what we were talking about earlier with people basically denoting their interests somewhere within the documentation. Yeah. Okay, cool. Thank you. Yeah. So, and that's, that's that and if anyone has a talk that they want to give. I have podium via OpenShift Commons and OpenShift TV to do that. So, I'm looking for other OKD related talks over the summer that if someone has one, I would love to hint hint John Forton to do an interview style or whatever style you like.  I will try, I'm going to have a very busy summer. We will try to convert some of that work into something I may be able to present. Yeah, no worries. Yeah, and I think there was one other thing that I was trying to think of. Yeah, and I know the summer is going to be busy for everybody and people are going to start taking vacations. But, you know, coming up with a date for the hack the docs once we're there, I can see Jamie's got his hands full. But yeah, with a good kind of hands full. Yes, I'll put something out with maybe a doodle or something on the working group list to see if we can come up with a date for that. And now I can see for my next meeting a few people popping in because this is my channel. And maybe what we'll do is we'll get a separate channel for the OKD working group Jamie at some point so that they don't overlap. Yes, and that is definitely the OKD's working groups youngest member ever. And he has not yet gotten a panda thing. So we're going to have to figure out how to get panda diapers. I think our panda t-shirt. This is Leo. All right. Any last minute we have three more minutes left any last minute items that folks want to talk about before we sign off. And Shri, I just wanted to mention I saw your post in the working group about the messaging around OKD and we'll have a I'll have a conversation with you about that and see how we can move that whole conversation forward. So look for me in Slack sometime when I'm I'm hanging out and you think I'm I don't look busy and you don't busy. You're on European time or are you on the West Coast? No, I'm on Eastern Eastern. Okay, I'll look for you and we can we can move that forward. We can if you go to the Slack channel and post your question there, lots of people can pop on. There's lots of people doing homelab setups. And we do actually have a couple of documents that we can point you to that are on the website. Joseph, if you have that link, maybe throw down the the homelab link that we have up on the documentation. But yeah, if you go in the Slack channel and ask your question, we can definitely help you out. Yeah, I mean, this is just for like value ads for OKD for, you know, eventually we'll put a section of the read me try to flush that out, make it more clear what you get. Yeah, I know it is tiny bit unclear. But yeah, I can definitely drop a line in there. I don't remember if I did before, but I'll put another one in now that it's. It also might be fodder for a good talk as well.  I think that might be a good Monday open shift. I do upstream stuff so I could do an open shift OKD, you know what the value prop is for OKD from data point of view. And have you what event would we be doing this in or is this a dedicated event or something like, I guess I missed a little bit because I'm juggling like 3 meetings at the moment. That's okay. So I host I have on OpenShift TV a channel called OpenShift Commons in which on Mondays I do upstream talks and OKD qualifies as an upstream project so or sibling stream or whatever. Oh, that sounds like fun. Yeah, sure. There's this next meeting coming up and there's already people joining. Yeah, so let's let's move it to the channel and say thanks to Diane and Christian and Vadim and Timothy and everyone else for contributing and Bruce say goodbye.