Hey guys, how you doing? This is your boy Rich from Rich TV Live and you too can join the club at richpixdaily.com where you can learn how to win and trade. And this is your boy Rich from Rich TV Live and richpixdaily.com where you can go and learn how to trade stocks and cryptocurrencies. We love Bitcoin. We love cryptocurrencies. We love blockchain technology. We love Legion Farm. For the first time ever, you are going to witness the first ever fight in the history of the metaverse right here exclusively on Rich TV Live thanks to Legion Farm, world champion retired now, Kabib against Max Holloway ex UFC champion still fighting in the metaverse exclusively here on Rich TV Live. So Legion Farm is a place where you can go and actually earn money while playing video games not only playing video games but also helping coach others learn how to earn and play video games. Absolutely wild a platform that is working and playing in the metaverse and also focused on creating and selling a collection of NFTs, NFC, NFT sale happening right here right now exclusively on Rich TV Live. Let's take a look at Legion Farm in a little bit more detail and let's watch Kabib go at it with Max Holloway in the metaverse. Says the stream is coming in 24 minutes and the first metaverse fight in the history of the earth. It says us in the metaverse guys. This is Rich TV Live at Rich Pigs Daily in the metaverse. This is our room, boom front row. We got front row right there. Perfect seats. Hey everybody, we are live. We are here in the metaverse Legion Farm. You can see us waving right now. You can see we have a whole bunch of esteemed guests. We're gonna introduce them in a second. First of all, thank all of you, whether you're watching in the metaverse, whether you're watching on Twitch right now, we really appreciate you being here. Why are we all here? My name's Arda, I'm the moderator here today. I'm excited to be the host for the Legion Farm grand event in the first sports studio in the metaverse. Glad to welcome all the guests who are watching us right now in the meta and our special guest rooms and all the viewers on our broadcast on Twitch. Don't forget to subscribe to our channel, by the way. Don't miss upcoming events. Specifically for our event guys from Legion Farm built an amazing location and we wanna show it to our viewers quickly. Take a look around. Just see exactly what we have here. We'll get to our esteemed guests. We have a great lineup here today. It's absolutely incredible, but this is a lot of fun. Thanks to all of you watching on Twitch, by the way, over 15,000 viewers already. Have a look around. You can see it's absolutely amazing and we'll get to see some of you as well. All right, let's get back to it now. Specifically our Legion Farm. We've shown you everything. We don't know if you see our Instagram stories before the broadcast. We did a short room tour. It's all fun and good. All right, let's get back to it. The reason we're having this event is to tell you a little more about the new stage on Legion Farm's expansion and the new possibilities opening up for the community as well as to give you both guests and viewers of the broadcast the opportunity to know better our special guests, the stars of Mixed Martial Arts, the UFC, Eagle FC, wherever you see them and find them, they are here to talk to you today. Witness a crazy show. Also our main event, the first metaverse fight in the history of Earth, of humankind. We are gonna have a fight in the metaverse with professional fighters. It's gonna be amazing. We hope for your activity in social media and giving away $1,500 total to the Legion Farm balance for the best screenshots from the event. So follow Legion Farm on Twitter, tweet the screen grabs and clips and tag us on the post for a chance to win. We also airdrop some NFTs during the broadcast only. We still have time to participate. It takes five minutes to register. Push the button below, sign up for Legion Farm, follow the guide. We'll tell you all the NFT benefits in a little bit, but for now you can check out the details through the banner below the broadcast. All right, let's move on to the much anticipated introduction of all of our incredible guests. Let me tell you, if you're an MMA fan, if you're a fan of NFTs, the metaverse, this is one heck of a panel that we have assembled here today. First of all, the legendary champ champ himself, he's a UFC commentator, one of the greatest fighters of this generation and also ESPN MMA contributor, DC Daniel Cormier. What's up, man? How are you? I'm good. I think I wanna live in the metaverse. I've been smacking people. I hit Habib, I hit Max. It feels good. There's no confidence to bully in people out here. You had a great reaction when you first come in here. It was amazing that it was like surreal to be in here, isn't it? It really is. It's a bit scary and it took an old man like myself a little bit to get used to the handles, but I feel like I've got it. I feel like I wanna live here opposed to coming back to reality. All right, our next guest. He's a world Russian combat Sambo champion, lightweight fighter. Many people say he will be the next UFC lightweight champion. I'm talking about Islam Mahachev. Islam, thank you very much for being here. How are you, sir? I'm good. What's up, guys? Good to see you, everyone here. You see a long time. I don't see you, but like six months. I'm ready to see you here. Could you please give a little bit more energy, brother? Please? Bro, this is today's Saturday, bro. It was a hard week, so tired. Of course, Islam is training for a fight as well. I'll be facing Banil Daryush in the UFC very, very soon. So we thank you very much for taking time out of your busy schedule to be with us today. How about another champ, champ, another champion in the UFC? The daddest man on the planet, if you're asking some people. I'm talking about Max. I'm getting into their skin. Just a little bit. We'll get to that later. Max blessed Holloway's in the house, man. How are you? And I'm doing good, brothers. I'm doing good. And you heard that D.C. That is man on the planet. D.C. also loves it in here because he looks about 100 pounds lighter. To be honest, A, for a long time, people say I should fight middleweight. I'm middleweight in the metaverse. Brother, you're like featherweight, brother, in the metaverse. And of course, one of the biggest superstars in UFC history, undisputed champion, superstar of the world of sports, one of the most popular and influential Muslims around the world, ranked in the top 10 most famous people every year. I'm talking about the champ himself, Habib Nurmohamedov. Habib, great to have you here. Very happy that you are a part of this. What's up, guys? How are you? How is everything? I'm very happy now we have metaverse and we can meet each other here, D.C. Because I don't see you long time. Hey, brother, I'm in the gym. I come to the gym Monday. I promise. Hi, guys. OK, please come Monday, brother. I hope I'm going to see you. Max, this is like, honor to meet you here in metaverse. Yeah, honor to meet you. You guys, please do a metaverse high five. Do a metaverse high five. I hope I'm going to come in metaverse in Hawaii because this is one of the best place in the world. I really want to come and join with you there. Oh, come. If not reality, but in metaverse. See you now. Shake his hand. Look right there. I wish I could take off my leg and give it to you. There we go. I wish I could give my leg to you. Good to see you, guys. This is my game. FIFA, I'm a best. FIFA? No one will beat me. Here's the fan cam, by the way. So these are all the people that are actually watching us on top of everyone on Twitch, by the way, which is over 18,000 right now. So we got some cool shirts here, some nice avatars. So everyone gets to customize their avatars, obviously. We got some custom avatars created for us, as you could see. But there's a guy in a three-piece suit, so he decided to dress up for the occasion. Very nice. DC, you got the chicken. Yeah, you want to come hang out? I'm in Houston right now at Chicken and Waffles this morning. Islam, what you eat, salad? This morning, no, oatmeal. Oatmeal. You sound very happy about it. You can feel free to wave, everyone with the avatars. Yeah, the fight is coming very soon. We promise you that the fight is coming very, very soon, because we are all, that's what we're, that's what most people are here for. They want to see the very first fight in the history of the metaverse and the universe and human history. This is history being made. To the metaverse, first fight. We are viewing this fight from the eyes of Max Holloway. Max Holloway as Rocky, Islam Makashev as Apollo Creed. Beautiful afro, 1970s style, just looking really good. And Makashev lands a beautiful right hand that hurts Holloway. But look at Holloway come back. As we saw in the Calvin Cater fight, constant movement with the hands, never stopping, continuing to just put the pressure on Islam.  Oh, Holloway's hurt. His gloves are blinking because he has thrown too much. I think he's getting fatigued. Oh my goodness, Makashev rocks him with another right hand. But Holloway goes right back to work. Makashev stunts him again. Holloway goes down in the first row. I won't let you. Wow, that's so cool. That could be right there on the right, guys. So Legion Farm is your place to play and learn from the best pros. Over 50,000 gamers worldwide played with our pros. More than 100 hours of coaching and fun games. So you can see here Call of Duty Warzone and Apex Legends. So they do coaching. Legion Farm also does coaching. This is their website, legionfarm.com. Your incredible experience in virtual worlds. You can also go and follow. You can see up at the top right here, their Discord and Twitter. This is their Discord page. I'm also a member of their Discord. This is their Twitter page, which is also on their website. You can see 11,500 followers. Your incredible experience in virtual worlds. Play with pros, creators and celebrities. Play and earn as creators and pros. Try it now. So this is an opportunity for you to earn an income playing video games. Something that many kids have grown up dreaming of. Many adults have grown up dreaming of doing. This is their YouTube page. I am subscribed to their YouTube page. You can see here Legion Farm. So they are creating a social media presence. And you can scroll down and you can see 60,000 customers and subscribers. 5,000 professional gamers play with pros, creators and celebrities. Have fun, improve, win, participate in tournaments, ranked and pubs. You can see here professional gamers play and earn as creators and pros. Make a living playing video games, contracts, paid hours, NFTs and hardware. So NFTs is something that everybody's talking about. Everyone's like, Rich, what's going on with NFTs? How do we get into NFTs, Rich? Well, take a look at Legion Farm. They have a new NFT collection. Just click on new NFT collection and you can literally earn NFTs and be a part of the Legion Farm NFT sale. The first step to Legion Farm. Our mission is to create 1 million new jobs within the metaverse. You can see here a collection of 10,000 NFTs, game heroes and club membership, what NFT owners get and coming soon the Legion Farm DAO. So all of this is coming soon. You can see here 10,000 NFT collection. Our community will form a Legion Farm DAO, a decentralized organization built with the help of sports stars, pro players, guild masters and web three enthusiasts, each one of our unique NFT servers as a key to unlock access to an exclusive community. So huge, huge, huge. And you can see here game heroes club membership. So, and you can see the Legion Farm DAO. So lots of exciting things coming for Legion Farm. You can see here the Legion Farm NFT collection, five sub collections featuring sports stars and pro players. Each card features one of those heroes in a great set in a gear set from game genres. And you can see here sci-fi, FPS and MMORPG. A great set has seven elements. There are three rarity levels of gear elements. You can see here gold, silver, bronze, where gold is the rarest. Each legendary card represents a complete set of one level. An epic card is an algorithmically generated set of elements based on all of the variables. Now, I don't personally own NFTs yet. We are creating NFTs here at Rich TV Live and selling NFTs. But this is an NFT that I would be very interested in owning that is so cool. These are so cool, these NFTs. And like I said, these are NFTs of celebrities, athletes, sports stars. So you can see here NFT tiers, legendary total 500, VIP access to the LF Gaming Heroes Club, private meetings with celebrities and creators at Metaverse and IRL events. Play with LF pros in AAA video games unlimited, lifetime, get bonus in DAO governance process. So this is an early stage project that I think everybody needs to be aware of. Legion Farm, put them on your radar, put it on your watch list. Epic total 9,500 access to LF Gaming Heroes Club events. Play with LF pros in AAA video games unlimited. First three owners of each NFT receive a bonus DAO governance process. And this is the NFT sale roadmap, total NFT supply, 10,000 NFTs. That's a pretty standard amount. We've seen that with other NFTs that we've covered. You can see here 4,000 boxes starting January 27th. We will launch 10 batches of 300 NFTs. Another 1,000 boxes are allocated for air drops, revealing dates February 20 to 25th, 2022. Revealing is a smart contract that exchanges your box for a one randomly chosen NFT from our 10,000 NFT collection and 6,000 boxes from February to March 22. And when you scroll down, you can have the option to just simply subscribe now. And there's a lot of upcoming events. Now we did cover the first metaverse fight in the history of the earth. Super exciting to watch Khabib win.  So we literally covered this and thank you guys for watching and hopefully you enjoyed the fight. And if you did, smash the like button, comment down below, share the video everywhere and subscribe. You can see future events, March 5th and 6th, 2022 in Mexico City, Club and LFSL League, guests, NFT holders, LF NFT holders, UFC champions. So more UFC champions will be back, Legion Farm, Warzone and Apex pros and creators and number of guests, 250. Activities include Web 3.0, panel discussions and networking. Web 3.0 is something I continue to hear about, NFTs is something I continue to hear about and metaverse is something I continue to hear about and Legion Farm is all over all of it. Warzone and Apex tournaments for the guests, prize pool, champion rings and glory, play UFC games against UFC fighters, shoulder to shoulder on the stage, the Dow launch, official ceremony after parties. Want to join, just click on I want to join. All right, you want to meet the team? This is the team at Legion Farm. So the founder and CEO is Alex Belenkin and the COO is Kate Kahn and Iskander Kaby Raham Men is the CPO. You can see the founder and you can see all of his information here. Feel free to learn more about the team and we always like to see a team that is not anonymous and you can see here since 2019 we have raised $17.5 million. You can see all the different funds and more members as you can see here. Just subscribe now to continue to learn more. You can sign up or log in and 5,000 plus pros and celebrities. And I mean, you don't get much bigger celebrities than Khabib, 100% win rate. I mean, it doesn't get much better than that. And you can see other celebrities as well. So really cool. And I think these guys are onto something here with these NFTs. I think they're going to be very popular. And these are the types of NFTs that I would personally be interested in owning just because I think that they're going to do quite well. You can see here UFC featherweight champion Max Holloway and you can see more UFC fighters and all kinds of cool opportunities here with Legion Farm. There's UFC heavyweight champion and UFC light heavyweight champion Daniel Cormier. So these are really cool NFTs, very interested in them. And like I said, I don't own any yet, but if I do purchase some I will definitely let you know, you can see here 5,000 plus players play in one squad with the world's best players by wins, kills or KD. Just simply join now and click on check our product to learn more. You can see here the Legion Farm community is united by a mission, create one million new jobs inside the metaverse. I think that's a fantastic mission. You can see here featured on Forbes and also featured on CNBC. You can see here CNBC says a 24 year old earns 3,000 a month as a professional video game coach. Here's what it's like. So you can earn rewards also as coaching. So pretty cool here. You can see Tech Crunch saying Legion Farm pairing pro gamers with amateurs raises 6 million series A. So they've been able to raise quite a lot of money. Venture Beat says the San Francisco company employs almost a thousand pro gamers who make real money as mercenaries in games. So cool. Join the Legion Farm community. Now I must remind you that Rich TV Live is strictly for information and education purposes, but we love these early stage companies that have a lot of presence. You can see their Discord, their Instagram, their Twitter, their YouTube and their Twitch. And we are following them as well on Twitch. We've shown you some videos of that as well.  It'll take you to their Instagram. And we are now gonna follow them on Instagram.  And when we were streaming the fight on, in the metaverse, they were also streaming on Twitch where they had almost 20,000 members watching live. The fight between Khabib and Max Holloway in the metaverse right here on the Legion Farm official channel. So very impressive. And love to know what you guys think and love to get your feedback on Legion Farm. You wanna read their white paper. This is always a great way to learn more about a project. Just click on white paper and learn more, learn about their terms of service, privacy policy, CCPA and blog. All right, that's Legion Farm, the Legion Farm NFT sale. And this is Rich from Rich to Be Live. We'd love to bring you early stage projects. We'd love to bring you NFTs. We'd love to bring you metaverse. This is a project that we think is extremely exciting. Put it on your radar, put on your watch list. Legion Farm, this is Rich from Rich to Be Live and I'm out.


Everybody forced here Rip in 2021 flawless football hobby two box full case of our 85 tier random team style find the results anytime at late in sports cards Dot com. Let's do it everybody Again, I think this is our last case as of right now. I mean we could get more theoretically But this is our last case that we have Maybe you shield Like sometimes the last one's just been just been begging to be opened You guys next up is national treasures basketball. It's down to three to go Down to just three to go All right, here we go. We had this at 950 two teams for spot Down to two to go on NT to go on NT next everybody All right, starting off with dual patch Colts Jonathan Taylor Michael Pittman, Jr. 8 of 10 Nice card Colts. You know if all this comes out we do like a few cases night. It's crazy Rookie showcase quad Raleigh rookie Kaderius Tony 10 of 20 for the Giants Kaderius Tony Giants. He's like the only person that takes the trash out. I do sometimes when it's here at the end of the night it's full, but It's like the only one Steelers Jets Alan Fannica auto at his career progressions auto four of 25 Steelers Jets, I imagine that I believe that's a random Steelers Jonathan C Jets James a random at the end of the Fannica and career progressions auto again here this time is just Cowboys I believe yeah, Cliff Harris five at 25 Cliff Harris on card a cliff Harris Dallas All right, we've got a veteran patch auto three color Terry McLauren nine at 25 with for the Washington football team as they are in this product Nice there you go commanders nine at 25 McLauren chiefs on the three color patch auto Marcus Allen Allen is a chief Seven of 15 Marcus Allen for Allen K Allen for Allen there. We got Hall of Fame autographs going to Denver Shannon sharp five out of ten Shannon sharp nice stuff solid hits in the inner there a lot of a lot of vets is all vets actually that's out of the Tony relic All right. Got Jalen Ramsey Ruby gem eight of 20 for LA Rams Jalen Ramsey Nice one here for the Jets Zach Wilson rookie showcase quadratic nine at 25 two patches glove and a ball relic We go New York Jets Shannon the sweater sharp yeah Think NT's down to one guys that last bottom NT. Thank you guys for getting that so close Now we had to push it back. Thank you for your patience as well for tonight a lot of breaks a lot of a lot of spot We didn't have one break sold out at like 4 30 p.m. Eastern Not one sold out. Yeah, this one was definitely marinating. This one's definitely marinating Who has this team? Joseph s. Joseph s has this team It is Patriots probably know who it is now Nike swoosh RPA Mack Jones Five of five Holy cow That has been marinating back there for sure emerald five of five swoosh RPA Michael McCorkle Jones That's big man, that's big Second one. Let's see some more heat. Let's see one of those crazy NT briefcases where there's like six encased autos or whatever it is There's like four in there. I feel so weird, but like it's even crazier. We get older stuff in and like wow That's like like when 12 13 I'm back Like 12 13 I'm like that I was like that's like 10 years old. Yeah, it's over 10 years old God dual patch rookie trace sermon four of 10 for San Francisco triple Patch card Broncos chiefs Cardinals Hall of Famers on their second teams Denver Brad Kay chiefs Allen Kay and Cardinals Allen Kay, this goes to Allen by majority. He has the chiefs in the Cardinals No random Allen Kay has majority Very nice card there though 13 to 15 Manning Montana Warner Browns of the patch auto Bernie Kosar two-color patch out of 25 at 25. That one's player worn Yeah, it's up a newer Browns newer Browns uni there flawless greats auto Dwight Freenie Colts three of ten Ruby gem rookie auto color match Rondale more Cardinals 16 to 20. It's all vets man Sometimes that means just a big hit in the in the briefcase though. Like it did last box Sometimes that's what that means There's a rookie there though Solid head Cardinals and a color match Ruby Ruby rookie auto Penmanship auto Vikings Fran Tarkin 10 numbered 12 out of 20 nice Tarkin 10 Viking legend Danian Tomlinson flawless flyers auto 17 of 20 Sick LT Sean M with the Chargers Okay, it's 2021 that was an older card 2021 there is the current year Most recent well as I should say Emerald gem James Robinson Jaguars three of five diamond guarantee Justin Fields rookie showcase quad relic 13 of 15 Good news for ever got this as it doesn't look like they're gonna trade fields. They're sticking with them We're gonna build around and they're trying to trade that pick now you go mark s. I Think it's the right move for them. Honestly pretty good pretty good hits here guys. I mean it's it's Pretty pretty pretty pretty good hits Who is it though, who is it? It's young QB Justin Herbert 205 on the that's like a charger like logo patch auto Sean M again had the LT and now Justin Herbert to a five patch auto Second-year Herbert dude, I cannot believe he had Mac to five and Herbert to five. That's crazy. I was not expecting that And we had the quad showcase fields and a lot of nice vet I guess all vets is like all vets really That's awesome, man Congrats on those cards Let's go ahead and do this random. Thanks everybody for filling that up Steelers jets. All right, again, it's an Alan fanica career progressions auto Steelers jets to 25 Good luck nine times six and three And whoever's up top gets it one two three four five six seven eight Nine jets jets get it real quick recap here Relics we had Cadarius Tony sawed one there for the Giants Taylor and Pittman for the Colts. This one went Cardinals chiefs same person had them Manny Montana Warner Trace Sermon Autos of Bernie Kosar Cliff Harris Terry McLauren Fran Tarkenton Lydanian Tomlinson Ron Dale Moore Marcus Allen as a chief Dwight Freeney Shannon Sharp Alan Fannica just went to the Jets in the random Case tits here Get an emerald of James Robinson Ruby of Jalen Ramsey rookie showcase Zach Wilson rookie showcase Justin Fields a Patch on a two of five Justin Herbert for the Chargers second year and RPA Nike swoosh five of five Mack Jones Holy cow Really good stuff there for the Chargers and the Patriots. Thanks everybody. I want to N.T. basketball


A path breaker is driven in his work by a superseding sense of altruism, hence bringing about a new beginning, a renaissance. The seeds were sown, the path chosen was tough, but my growing up at Sevagram had taught me how to cope. Bapu's teachings were my very foundation, and I was only too glad to have found a wife in Rani who despite her privileged upbringing had similar beliefs as mine, but the journey was not to be an easy one. The death of the little girl could have been averted. I was right here and yet couldn't save her. What use was my medical education? I don't know if Dr. Kaka was sad or angry, but he definitely looked determined to solve the problem he had come to know about. Small small babies dying. My mother told me they call it child mortality and so Dr. Kaka and Kaki started the hospital in Argachiroli.  They also talked to mummies whose babies had died, you know, and they did all this to find the problems. Why were so many new, new children dying? But that was easier said than done. Nearly 92% of the women had gynecological problems. 40% of child deaths were caused by pneumonia. We doctors could treat it. But how could only two of us reach so many sick children? There was only one way out. When we came back to this, this was the beginning of getting pregnant. This was the beginning of getting pregnant for one minute. We had to start getting pregnant in the morning. After 10 weeks, we had to give birth in one minute. So, in one minute, we had to give birth in a red color. So, what did we have to explain to the baby? Good. Now you are a doctor. This way, illiterate birth attendants in villages were trained to diagnose and treat pneumonia in children. So, they could save their own children. This was aarok desvaraj, which meant people's health. In people's hands, such a simple idea notai the breath counter. With this machine, they saved many, many lives. And you know what? To make each one, it only cost rupees 12. In 1992, the Bung's research and their achievements were published in The Lancet, the most esteemed medical journal worldwide. What we wanted to know is how they brought the infant mortality rate down from 121 deaths per 1,000 births and what we saw amazed us. These community health workers in remote areas with few means at hand were no less than city gynecologists.


Good morning. My name is Marco Cepi, I work at Canonical. I'm an engineer, DevOps engineer on a Canonical team. And my focus has really been about how we can make operations much more reusable, shareable, and just tractable amongst organizations. So I want to take you all through a journey of how we approach this idea of making operations truly open source and shareable and reshareable amongst people. Before I do that, I want to talk briefly about who we are. So we're Canonical. We're the company behind Ubuntu. As you can see, Ubuntu's been growing in popularity steadily since we released the product almost 12 years ago. Ubuntu is the free open source Linux distribution. That's welcome for anyone to download, try, and run today. And so today, we see about 34% of servers running Ubuntu. And that is a generally large market share for Linux servers today. In fact, the majority of people that are running clouds, whether you're running servers, clouds, are all running on top of Ubuntu. And we're the choice for developers. And so I want to highlight just a couple of stats. 70% of all instances launched on Amazon are Ubuntu images. 80% of Azure's Linux deployments are all Ubuntu. Where 65% of the large OpenSec deployments are built on top of Ubuntu. And because of this, this has given us a lot of insights into how people run operations. And so what I want to talk about is when we meet with people running and using Ubuntu for their clouds, we come across a common problem. The story plays out in every organization, from the large startups to the well-established and dominant industries today. Everyone that's running software and running software at scale is encountering these same problems. And the problem really is around how do we manage the increasing complexity of applications and services that are spawning today? If you look at the myriad of applications that are available for the people who are evaluating and deploying today from OpenStack, which, as you all may know, is not necessarily the simplest and most straightforward piece of software. You just don't go and put it on a machine. It's actually multiple components spanned across multiple machines that all come together to produce an interconnected single picture of how you provide a cloud service. In the same way, all of these other tools, whether it's Mezzo, Stalker Engine and Swarm, Kubernetes, Big Data, all of these things are providing a single picture of software, which is actually built from many smaller, complex components. And all of these components kind of lend themselves this idea of cloud-native architecture. The idea that it's not a single monolithic application on one or a few servers, but it's actually this huge amount of scale that spans the breadth of multiple machines. And all of this increase in scale and all of this increase in size is due mostly to the fact that software today is open source. It's very easy to get software today. In fact, there is an abundance of it. Where you compare that to 10, 15, 20 years ago, software was really the hard thing to get. You either had to go and purchase large licenses for software, or you spun up a development team in-house to produce the software that you needed to fill your needs. But because of a lot of what we see in the open source world today, we see that there is more and more software that you can just go and try and evaluate. In fact, there's more software that you'll ever be able to evaluate in a given time frame now than there was last year. And every year, that number grows more and more. If you look at the number of just in the container space alone, the number of container orchestrators that have spun up in the last year is quite a large number. There's probably about six or seven applications that do that today. Next year, I guarantee it'll double. And it'll just keep getting more and more complex in numbers. And what we're seeing is because of this explosion of open source software, because it's so much more readily available, the cost of actually acquiring software is really low. It's not that difficult anymore. In fact, I don't imagine most people pay for software licenses today outside of a few maybe longstanding or legacy software application stack that you still have to manage. But what really is becoming the most expensive thing in an organization, from both a time and a manpower resource, is operations. It's not so much knowing where to get that software and paying for it, but it's now knowing how to install, manage, and scale and operate that software. Past just day one, but day two, three, what happens weeks later, months later, how do you upgrade? How do you scale? How do you manage fault tolerance? All of those things that you need to either get expertise in-house or hire services to help manage that. And that's where the real cost today is in operating in software. It's not acquiring, but the operations of it. And so this is really what I want to focus my talk on, is how do we stop that curve from accelerating much higher to the point where it's prohibitive to even evaluate software? If there's 20 solutions that fix your problem and you only have to pick one and hope that one's the right one and run with it, because that's the expertise you have, or that's the choice you made, and it's too expensive for you to try something else, you just have to hope that's the right software solution for you, and if it's not, it's very expensive to step back and try another evaluation. So this is really where we're seeing this shift, is that in all these companies that we're speaking to today that are running a boot, that aren't running a boot, everyone today is having a problem where the scarcity of how they do software is not in acquiring the software, but it's how they operate it. And I want to talk about how we can potentially resolve some of these things. And the way we see it today is that the only way to truly make software operatable in today's world, where it is so abundant and so frequent, is to be able to model how software operates. And the idea behind modeling is that if we can model how you do installation, how you do configuration, how you do upgrades and management, if we can model that in the same way we model code, how you do inside of code, how do you do unit testing, how you do quality checking, if we can model it in that same way where it's software-defined models, we have a way to actually make software in this day and age much more tractable. So I want to take an example and kind of walk through a pretty straightforward example. This is MySQL. And more importantly, this is Oracle's MySQL. It's an open source database engine. It's quite popular in today's day and age. Most software stacks are built on top of either MySQL or something MySQL-like. But for the sake of this argument, it's a database. It's just a database server. This could be MySQL server. This could be Postgres. This could be even something like a NoSQL database like Mongo or another piece. It's just a very common component that you find in most stacks. Most software stacks today need to have a database to store their information. Even OpenStack today, you have to have store database. You need database to store your back-end information for Keystone. And you need things like message queues. And all of these things are common components that aren't unique to OpenStack. RabbitMQ or any MQ service is not part of the OpenStack tree. It's just a supporting service that's required to run it. And so when we see people modeling today, we've seen a lot of these companies model software by going to a whiteboard and drawing out, this is my architecture. So let's say you were running some big data service where you've got a bunch of Hadoop nodes that are all set up to do big data processing and you're using Hive to add your SQL-like query interface. That requires MySQL's database back-end. Let's take another example of a model. Something like a very simple blog app. If you're running ghosts to run your blog services, you need a database service in the back-end to store all that information. Or how about even OpenStack itself? If you look at all the components to get a bare minimum OpenStack where you can launch instances, you need things like Cinder, Nova, Keystone, Horizon, Glance, all of those things need to be connected together and they all rely on a database back-end to store that information. And so when we actually zoom in, when we talk about modeling, what does it mean to model a database? Or what does it mean to model any one of these components on the screen? So if we were to kind of take a dive into this, we'd see really what it means to be modeling is you need to model things beyond just the installation. We talked about modeling software and modeling big software. We're talking about how do you not just install an application, but how do you configure that and how do you mutate that configuration over time? If two weeks later, you need to change a configuration option, is that a redeploy of something? Is that just changing an action and running through some updated configuration? And then how do you do things like upgrade? How do you do things like clustering? And more importantly, how do you do things like integration? This is a MySQL database. I know that in order to integrate it with anything else, I need to provide the credentials to that application. I need to be able to say, here's my username, my password, my database schema, here's my host, here's my port, here's all the information you need to integrate with me. And every component has a unique set of information that's required for integration. And then there's other things that you need to model, things like how do you do everyday operational actions, the kind of things that are required for you to make sure the service is running and running well and healthy. For database services, it's usually things like how do I do a backup? How do I do a restore? How do I check integrity of my replicas? For other components, it could be things as simple as I need to take Nova out of, I need to, sorry, I need to drain Nova of all its workloads so I can take it offline and perform maintenance. I need to do an evacuation of the host. There are a number of everyday operations that we need to perform in order to ensure that the quality of our service is running over time. And these are all past that day zero installation. These are all things that we have to do every day. And that's all things that we have to grow in our organizations in order to be able to do that. We need to be able to learn what does it mean to do the proper way or the best way or the right way for us to essentially evacuate what's the best way to perform backups? What's the best way to do upgrades for a database service that we don't get any downtime? All of these things are important pieces of information. And today in these organizations, every organization's figuring that out for themselves. Now, of course there's resources like blogs and stuff, but for every piece of software there's not a best practice blog where you can go or community you can tap into to say, what's the right way to do that? Instead, you have to figure it out through trial and error and a lot of pain or you have to hire people who have already done that trial and error and pain. So what we want to aim to do is how do we encapsulate all this expertise? Because at the end of the day you're running these things, you're running these operational executions. And they're pretty common patterns. The installation process for a database server is, well, not the same, but it's very similar to what you do for any other number one of these components on the screen. Horizons, installing a set of packages or installing from the upstream or compiling code. And that's the same for most other components we found. So what I want to talk about is how we can actually start leveraging and resharing operations. When it comes down to my day-to-day activities, I don't want to be an expert in operating a database server. I'm already an expert in having to manage and install OpenStack or even just a simple component of OpenStack. And OpenStack is just one example of a workload. What happens when you start operating software on top of your OpenStack? Or if you're operating software on top of OpenStack and on top of public cloud and on top of another public cloud and on top of bare metal? All of these things require expertise in each of those components and we want to reduce the amount of friction and overhead it takes to do that. So I want to just skip slides. I just want to show what it's like to operate software today. How we operate software, how we operate large scale software. And not just the I installed some stuff and configured and I'm good to go. How do I actually manage that software over time? So I've got an example here. This is of Kubernetes deployments. So Kubernetes for those who don't know is a container orchestrator platform. It's a way for you to do scheduling and processing of Docker and Docker like containers. This is the workload that's running right now in Amazon. And what we actually have is we've modeled what it means to actually install not just Kubernetes but how do I do integrations with other things? How do I integrate Kubernetes to Ceph so I can get persistent disk volumes? How do I integrate Kubernetes with monitoring software? How do I integrate all of these components together individually together to produce a holistic operations dashboard? So I want to show how I set this up real quickly and walk through that process and show examples of how we can actually reshare and reuse operations code without having to go and reinvent it every single time. And the entire point of this demonstration is all this stuff is off the shelf available. So for instance, we're using Elasticsearch Beats and Kibana, it's the Elasticstack for monitoring and metric collection and log collection. And that's the same Elasticsearch and Beats and Kibana that's being reused by every other deployment that uses this. The same way for Ceph, every production deployment of Ceph we have today, this is the same operational knowledge encapsulated that I'm doing today here that anyone can reuse. The idea is that there are lots of people in the room that are really good experts in one or a few things, but there's rarely ever an expert that's an expert in everything. And if we can encapsulate the knowledge that we have today and reuse that across the board, people can actually get started quicker and evaluate software at a much faster pace. So we use Juju as a way for us to provide a modeling language. And Juju essentially what it does is takes care of how I get placement in machines. So Juju is a tool, it's a free and open-source software tool, allows you to say things like, here's my open stack, go provisioning machine's foot workloads on it. Here's a public cloud, go gather me that. Here's some bare metal, go put these workloads here. So we use Juju as a way to define our placement of software onto machines. And Juju uses charms as a way to encapsulate the operational expertise required to set up these components. So I'm just gonna create a new model and I'm gonna run through the same thing I just ran through earlier here. I'm just going to deploy Ceph. And what this is gonna do is gather all the things that are required to deploy a Ceph cluster. This is installing everything for Ceph OSDs, for Ceph monitors. It's making sure it's set up with the minimal requirement for these. So it's three nodes for Ceph OSD, three nodes for Ceph Mon. And it's adding in some additional monitoring and dashboarding capabilities so I can see the health of my cluster easily. Then I'm just gonna deploy a core-based Kubernetes. This gets me a master or a worker to run workloads on. And as well, a PKI for doing TLS encryption. So there's entire SSL encryption across the stack and Flannel for an SDM. And then I'm gonna deploy some other things like Elasticsearch, Kibana and Beats. And so what we've got is a whole bunch of software that's being installed and managed right now on Amazon. But this could have been on my own private open stack. This could have been on bare metal. This could have been on any other cloud. And what we see is what Juju's doing for us is it's grabbing machines, it's allocating resources, it's putting these workloads on them as I've described it. And then these workloads have code encapsulated to do all the operational knowledge. Now this is very similar to day zero stuff. I'm just installing software and configuring it. And that's the initial configuration. While this sets up, I'm gonna switch back to this, which is the same model, but it's running now. So it takes about 10 minutes, five, 10 minutes, depending on how fast the cloud is, to spin up these machines to get workloads running on them. What I'm gonna show is what happens after you get things running. So this is a command line version of this pretty gooey that I showed earlier. So if we switch over to Hello Open Stack, we'll see a whole bunch of these circles just kind of sitting all over the page. We can fix this up in a second, redesign it. But I'm gonna go back to the already deployed pre-baked model, great. So I've just replayed exactly what we've done here, but from a little earlier today. And what we get now is the ability to actually start managing this over time. And so we do that in a number of ways. The first is we can actually manipulate configuration of stuff. If something changes in your deployment where you need to actually tweak and tune an item, whether it's scaling up the amount of memory you wanna use for caching your database server, or it's tweaking the volumes you want Seth Mon to use, I mean, sorry, Seth OSD to use for creating Seth block devices, or any number of configuration options can be tweaked and tuned using Juju. So let's take a look at a couple of examples configuration options that we can kind of manipulate and modify.  If you have things like using insecure registries or other parameters, those are allow you to supply them and change them over time and tweak them. Things like defining ingress values, where to do proxy values, if you wanna install from upstream instead of local Docker, all these things you can manipulate over time. And each one of these charms, each one of these circles enumerates a set of options you can actually manipulate.  And because all these operations are encapsulated and distilled in a way that makes them reusable in that each one of these circles is just enough to define the characteristics required to install and set up that single component. That component then defines these set of integrations. These lines are integrations and components that you can tie into. And because we delineate that in a single circle and a single charm, it becomes actually truly reusable. So all these pieces are individual, reusable, scalable chunks of code that just define these is how I install, manage, configure, change and operate this piece of software. At any time we can switch these things out. If you're not a big fan of Beats and Elastic Search, why not Nagios? Why not Zavix? Why not Prometheus? Because each of these things define their own set of criteria and how to install, manage and integrate, you can actually start interchanging, swapping and removing components. I didn't have to write a single line of code to get an entire Kubernetes cluster running. I didn't have to download any kind of predefined scripts and weed through them and make changes to my environment. Juju has done the job of encapsulating and distilling what it means to get that provider specific information where you get your cloud credentials from, how you boot up machines in that infrastructure. All these little circles do, all these charms are concerned with is how do I, once I have a machine, how do I install and manage everything? These also give you the ability to run operational actions against. So, for example, when you're managing a Ceph cluster, there's quite a lot of things that you need to take into consideration.  It's great for remote block devices, but when you look at the actual operations for it, there's quite a lot of things that you can actually do during the life cycle of a Ceph cluster that you may need to run at any given time. And these aren't necessarily configuration options. These are just kind of one-off operational tasks, things like creating caching tiers, managing erasure pools, creating new actual RDB pools. All of these things are one-off tasks that get still modeled and still down to this charm level. So even charms themselves, beyond just things like installation and configuration, also define day-to-day operational tasks that you can execute in a repeatable, reliable, robust, and observable fashion. And that's the advantage of having this idea of open-source operations. Every single company that uses these charms, they feed back into them. This is how we do erasure pools. This is how we manage these actions. These are things that we find ourselves doing on daily tasks. All of that stuff funnels back in, just like an open-source software project, funnels back into the operations for that and produces a very reusable, reliable, and robust means of operating these pieces of software. So let's see how our deployment here is looking. So still a few pieces that are being spun up if I detangle these all, because I kind of mashed them on top of each other. We see that we have a Ceph cluster that's running. We've got Kubernetes that's just finishing up its installation, and we've got a bunch of Elasticsearch stuff hanging around. And so what we can do in order to finish and compare these pictures, while I didn't place them just right, a lot of the integrations haven't been completed yet. And Juju allows you to define these pieces of integration. So if we go here to here, to our model that we're just spinning up, I know things like Kibana needs to be connected to a certain piece of software. In this case, it needs to be connected to Elasticsearch. Elasticsearch needs to be connected to Beats. Beats needs to be connected to, come here, to all the workloads I want to monitor. So I want to monitor at CD, I want to monitor this, I want to monitor this, sure, I want to monitor Ceph as well. And I can draw these integration lines because I've declared how these integrations work. And now, oops, this one didn't get drawn. And now what I get is the same picture I've had before, where I have software deployed, integrated, and redone, and I can operate it just as I would any other workload. So coming back to slides here, the idea that we have is that just like open-source software, operations too will be actually shared amongst organizations because at the end of the day, the operations, how you operate and manage your infrastructure doesn't actually help you win. It's not how you run your open stack or you running your open stack better than another competitor that makes you win. It's the services and how you manage and provide service to your customer that really makes you win. And by sharing infrastructure and operations amongst companies, you guys are actually able to accelerate your innovation and compete where it really matters at the product level, not the infrastructure level. Just in the same way that a lot of these companies today, most everyone here I imagine is running some piece of open-source software today. And that's open-source software that you've probably either contributed to or your competitors are contributed to or other organizations that you've never even interacted with or compete within any level have contributed to. And by sharing our knowledge on how these base components are built, whether it be a database service or a cloud like open stack. In the same way, if we share our operations in that same vein, how do you install and manage, configure and operate that? It helps to reduce the overhead and cost that it takes to do operations today, ballooning infrastructure sizes, duration it takes to stand up stuff. If it takes you more than a couple of days to stand up at open stack, that's time invested and ultimately wasted in trying to get a product running for evaluation. And if you're using open stack today, ask yourselves how long does it take to upgrade my open stack? Are my running the latest version? Am I on Newton? Am I on Mataka? Are we still maybe even on an older version? By distilling this idea of operations and by using things like the open stack charms that we have, you're able to do things like upgrades, day zero releases, upgrades without any downtime, management of a cluster to produce a robust and reliable AHA production deployment.  And it's that idea of sharing that really helps to promote the reuse and reusability of operations. Here's just a couple of examples of things that we have today that have been produced as charms that you can go today and get operational expertise on and experiment and play with. Now I'm not saying that you don't need to know how to operate these pieces of software, but what I'm saying is that this is a really quick way to evaluate which piece of software you really want to go deep on. Maybe you want to evaluate all the different types of SQL databases for your application. And if it takes you a couple of days for each set of application to stand up instead of a couple of minutes, that's a lot of time spent gaining knowledge in an arena that you may not even be playing in. And so ultimately what this means is it's not gonna get any simpler.  Going beyond things like even container infrastructure, things like serverless, things like high performance computing, all of these things will lend themselves to larger and more complex pieces of software. The future is only going to be more complex. It's only going to be more problematic for us to operate the software. And if we don't start sharing operations and we're using operations, we will have a hard time innovating. And that's what Jujie does. I'll take any questions. I think there's microphones over there. If you guys just want to queue up in a microphone so people can hear your questions. Hey. Is there a way to try it freely without installing everything by ourselves? Yes, so Jujie itself is all free open source software. Everything I've shown you today is free and open source. There are much cheaper ways in paying for a cloud to try this software out. For instance, if you have a machine running modern version of Ubuntu or Linux, you can use Linux containers to model a deployment you wouldn't have cloud but on your laptop. And actually I'm just gonna pick that off in the background, that's a good question. So there are definitely cheap and free ways to try these things out. I will create a new controller on LexD.  For those of you not familiar with LexD or LexE, it's Linux containers. It's the same primitives you'd expect from containerized technology, super lightweight, namespace, no virtualization overhead, but you still have isolation and security.  Well, it's gonna download an update, but in order to basically play with Juju, model topologies without spending a dime either for resources in my organization on my cloud or even in the public cloud. So that's a great question. Juju works against a number of machines, including things like if you have a couple VMs running in Vagrant or a couple VMs running in VMware or somewhere else, Juju plugs in and works against those as well. But this is probably the fastest way to get started, yeah. Any other questions? Anything anyone's interested in seeing? Operations-wise, ask whether or not we have it, see it deployed, see it manipulated, maybe see it broken. Sorry? Backup and restore? The question is around backup and restore. It's a great question. I'm gonna leave this running in this tab and we'll go over here. So not everything has a backup and restore. For instance, I don't think Keystone has a backup and restore, but things like database services typically do. And that's all defined in the charm. So let me go, that's probably not the name of it. So ProcodedDB is a bit more robust of a MySQL data store. It's what most people running OpenStacks in production that we know of are using instead of Oracle's MySQL.  Oh, sorry, how to backup and how to pause and resume services for multi-clusters. And these are, let me deploy this so I can show you what that looks like. So let's take a few seconds to spin up, but we can still, because it's asynchronous, we can play with it before it's fully run up. So if I can do juju actions for Conan Cluster. So these are the things, the things I just showed you in that webpage, a little more to still do juju. We have backup and we have pausing and resuming the MySQL service for things like maintenance and whatnot. Because ProcodedDB has a heartbeat measure, if you pause the MySQL service, the cluster will know that that machine's down and not to use it for read and writes. As far as doing a backup, essentially what you would declare is a set of options.  Let's just say I want to put this in slash SRV. And if I want to do an incremental backup or not, that's all I need to do. Now, granted, ProcodedCluster is not running yet. It's still probably in the process of being set up. Yeah, so I'm waiting for a machine to come up still, but I can still queue an action to do that. Because we're modeling these things, juju knows the state of everything that's being modeled. And in this case, juju says, I've queued this action, and if we check its action status, we'll see it's still pending. It hasn't been able to run it yet. And it'll remain pending until it's derived that the workload is in an idle and ready state. Once it's idle and ready, that action will be queued and then executed. We'll get a backup in slash SRV. Now, granted, there's nothing to backup because I have no databases in there, but if we created the relations, we could deploy a blogging service, we could write a couple of blog posts in the next five minutes, and then we'll have a database, and we can back that up, and then the backups will be there. Now, from there, it's a matter of, do I SEP a down-to-line machine? Do I push it to a cold storage? All that is modeled in a separate charm. How do I do, how do I remove backups and do file synchings to an off-site thing? So for now, it's on that local machine, and I can either grab it directly to juju, or I could do another measure to have a charm that says every file in this directory gets pushed somewhere else. So that's just an example of running a backup action for a SQL database, and each charm delineates its own set of actions as it sees fit, depending on what the common operations are for that service. Great question. Any other questions? We have a few more minutes. I'm happy to show off a couple more things. We'll see how we're doing with Lex-D. It looks like we have a deployment. So if I run a Lex-D list, I've got a couple of other Lex-D containers I created, but here's the one that juju created. It's basically a super light VM. I can SSH to it, so it's here on my local network. Well, except I reuse my IP addresses a lot. I can SSH to it. It's a juju machine. I can run juju status. I have nothing in my payload here. I can do a juju deploy prokona cluster here. And what'll happen is juju will put this charm here inside of my Lex-D deployment. So in a few seconds, we'll see it requests the machine. If we run Lex-D list again, well, give it a second. We'll wait for it to request. There it is. Okay, now it's requested the machine. I've got another juju machine created. It's still booting. It'll get an IP address. Juju will do what it needs to in order to make the machine is ready. It puts the charm on there and all that operational code and then runs through the sets of events that needs to be required to do the installation. Do the setup, things like install, do the initial configuration, make sure all the services are started, make sure the workload's idle, and then it's ready for me to start doing integrations, running operational actions against it, or any other means. But it's a real workload. It's running on my laptop isolated completely without much resource consumption. And this is not a brand new laptop. You can see most of it's Google Chrome. I don't think I can even find where that workload is, but they're super lightweight VMs that allow you to do a lot of these kind of things without spending money on clouds. Great question. Yes, microphone, sorry, I can't hear you very well back there. If anyone else has any questions, feel free to just queue up over there. What's the difference between LXC and LXD? Ah, that's a fantastic question. So LXC is the same thing. It is the Linux container itself. So these are LXC containers. LXD is kind of like a hypervisor for that. It's an API, so whenever I run things like LXC list, I'm querying the hypervisor, the LXD daemon, on my machine to show me all my LXC containers. When I do like a LXC launch for an Ubuntu 16.04 machine, it's going to basically talk to the daemon running, so I can run a daemon on multiple machines. We can do things like run LXD inside of Nova, so instead of getting KVM machines, LXD asks as a hypervisor, so instead of Levert for creating KVM machines, you can do LXD to create LXC machines. And so that is essentially what LXD is. So it is slightly, they are slightly different, but they are very tangent to each other as far as products are concerned. And again, just like everything I've shown you, all free open source software. Fantastic question. Any others? So I'm just going to deploy a load balancer onto my local machine, and then I'll put some kind of workload that I can poke at, maybe Keystone. So the great thing about Keystone is, while it is part of the OpenStack project, it doesn't actually need very much to run. So as long as you have a database service, you can have a Keystone endpoint that answers queries for authentication, you can create credentials for it. So a lot of times when our developers are working on charms, they'll just deploy small fragments of things that make sense. So instead of deploying an entire OpenStack to evaluate a change to the operations of a charm, you can deploy the minimal set of code to do that. So I'm going to run an integration between Keystone and Percona cluster, and we'll just watch the status here. So despite things not even running yet, you can still do the integrations, you can still do the operational actions. Everything is essentially queued and managed as an event bus in Juju. So it makes it really reliant that you don't have to sit around and wait 20 minutes for everything to spin up, you can just set the things you want to do.  When I come back, Keystone will be connected to Percona, Percona will have provided all the credentials that needs to connect to a database schema, and then I'll be able to start poking Keystone, the API directly. That's an example there. Any other questions? We have a few more minutes. Any workloads people are interested in seeing? Let me know, otherwise. Yes, yeah, that's a great question. So I guess the question is who is creating these? Or yeah, so who's creating all of these charms? So who creates the Percona cluster? Who creates Keystone? Who creates MySQL? Who creates all of these things? That's a great question. And that is super dependent on who's the expert in that workload. So today in our charm store, we have a mixture. We have a small team in Canonical that builds out and does the operations for OpenStack. At Canonical, we actually deploy quite a few OpenStacks in varying degrees and we're very aggressive at our upgrades. Make sure that we have HA, all our production workloads. When you go to Ubuntu.com, you're hitting an instance on top of an OpenStack. So we have a lot of expertise in OpenStack. We've been running it for quite a long time in production. So we produce a lot of the OpenStack charms, but they live here in the upstream org for OpenStack.org. So the charms are there, the code is there. We have contributions for not just us, but from people like Walmart and other companies that we work with who deploy our OpenStack as well. And it's really a bit of a community effort. You'll find that a lot of vendors are the ones that actually end up creating their charms. So when you look at things like charms for either NFV or charms for common components, a lot of those are created by the vendors themselves. And they live in their upstream repos and they manage it. Now, not every upstream, not every developer is necessarily the best operator of their code, although they probably have a lot of insights into it. We also have charms that are created by community teams or consultants that actually end up being more of the experts at how that looks in the field and less so the upstreams. But it's definitely an effort across the board. Canonical is not the sole creator. We do curate the story, make sure there's quality code in there. These ends up in production deployment, so we're very critical about how well the code's formatted, making sure it's robust, doesn't do anything nasty per se, and generally follows good guidelines for integration and configuration. But outside of that, there are many people that contribute to charms today. There's a whole list of that slide before I show you all those icons. I may be overtaxing my poor T430, so. Well, yes. So a lot of these icons, these are the people creating their charms. And if not, it usually comes from someone in their community or an expert somewhere that's running it that just happens to distill their operational code and put it in as a charm. So fantastic question, but it comes from all over the place really. Great. I think we have time for potentially one more question. All right, great. Well, thank you all so much for your time. I appreciate it. If you have any questions about open source operations, it's a topic I'm really passionate about. So far, I've found juju and charms are one of the best way to actually reshare and reuse operational code. But I'm always looking to find how we can make sure that operations itself is just a lower barrier of entry for trial, error, and experimentation. So thank you all so much. Appreciate it. Enjoy the rest of your conference.


All right, let's play this once through here. There's some sound No, no, no, no, no, no, no, this is very very bad. This is really bad Alright, so I like your new idea. I like the audio choice and everything I like the animal so I got a couple thoughts Mainly is that you could technically start the shot here No, no, no, no, no, no, no, and then technically you You just add whatever set you want. The reason why I'm saying this is because When he goes back here It's a bit I'll be careful that he doesn't look at the camera. So breaking that fourth wall unless that's something that you really want to do where You know the specific reason for looking to the lens for comedy or something But it's a bit subtle. They almost like what is he looking or not looking so be I don't I personally don't think you need to But again, he goes back needs to escape. It doesn't happen. The animal doesn't get it. He waits He was oh come on again. It's to camera But my main reaction is that He could say this to the creature and it would still work or he could say to himself and it would still work We don't need this but Since you are having this I would I would have a bit more fun with it meaning We see this There's no no, no, there's no an action. I mean you could add potentially an action But again, since this is clearly, okay, we're on the set and this is an actor pretending what I would do is Have that character in a different in a different attitude. It could be it could be whatever whatever you all I could be Totally bored looking at the watch or you know cleaning fingernails or whatever a classic thing that you're not there and then an action Or just doing nothing and then then changing into this or Almost like Jack Nicholson style in that Shining making of I brought this up here. Let's play this Look at how he That type of thing obviously it's much more How the guy here you have to go. Whoa. Hey guys. What's going on? Anyway, he continues on there Not that he has to be that emptied up But it's something where he's maybe hopping up and down and shaking his arms just getting ready and then Get into character and then you do all of this all of this all of this gets into character And then here he still tries to be in character realizes something's wrong But also with this I would have the creature just you know take one or two steps and maybe move towards us Or a bit away from us. Maybe a bit more. Maybe probably a bit more profile and then It's more him frustrated Looking up and then looking around and not not at us is looking at the set looking at You know stagehand at the director might be off-screen over there. So I would use that a bit more and then Come on and then oh come on because to me it would be Profile you can do the big thing of he's looking at the creature creature goes down And then you do the big C curve reverse. Oh come on So it's kind of push those poses a bit more or since you are having control over the auto And you're adding your own pauses it could be more like anger and then he gets off The thing and then stomps away or just something where we can see again a clear break of he's trying to stay in character He's trying to act and now he breaks character He's back to his own self and this would be just a fun thing of showing the differences between This is the actor in character and this is the actor normally and now freaking out So that's my main reaction because if you just keep it like this again, we don't really need this You could just basically do that have this reaction You know and that's it well, that's again totally up to you Other than that if you keep it like this again, I would just push this a bit more. So it's not just this rock Even I'm even just even if it's just lowering the head and maybe Bringing the butt a bit up and maybe one step just a bit more life It can still have this kind of not so smart demeanor, but And then go back It's almost like you could have Getting ready and he thinks okay now that I can continue and it gets back into character or gets back into being alright Let's go. Let's go and that was just the anticipation To go down there and then realize oh man, and this could be something where maybe what does he say? Oh, come on could be head down Holding on to this You know how to just to hit the creature but like oh come on or just you know I would just look for a bit of a bigger change at the end pose wise, but it's not just this Seems a bit bit little And again, I think the fun of having a character in green screen and Us as an audience knowing that this is on a film set I think you could push the fun of it a bit more and doing just a few bigger things And especially here either way character not in character when he gets here It's just weird that it just stops I Understand that potentially you want to go for a big whooping move and then contrast But I would still probably go and then maybe a little bit of pause and then maybe You know hitting the the boots in here or maybe tapping the creature just like one more thing of like come on Let's go go and then it's really that big pause of hmm what it's gone Those just to me don't be the biggest things if you keep everything the way it is a bit more movement that have a bit more fun with the creature So it's not just so still and then sitting down and it's something where he gets on there and with one more One more thing of come on. Let's go. Let's go through either a reshuffling getting maybe closer to this or or sitting back up again Something where it's a bit over pose adjustments, and then that's it even though it's will make a bigger thing out of the end And it's up to you if you want to look into Into the camera, but yeah, so these are all my overall thoughts from a technical point of view careful, these are clearly I care hands with Everything was very translating. There's not a lot of rotations, especially on this You can see how this rotation. There's no rotation. It's basically all goes down and the wrists they put the notice It's just early There's something to to look out for later on especially once you have this elbow movement without affecting any Rotation of anything in the wrist is an I can sign at this point. It's pretty broken the top view probably be like this the wrist Just throw a little thing I don't think you want to you want to start the shot with something like this or go That was not quite there. So once you're you're further along You know going up and then maybe yes to tighten here So it's so finger stuff and I know this is not now I'm just saying for the final product that would just get some good detail stuff in the fingers there Alrighty, that's it. Thank you All right, there's an email you can sign up you can start whenever you want You can submit whatever you want you get 16 submissions either way like and subscribe would be awesome. All right. Thank you


I have Cedric Claiborne, an OpenShift Developer Advocate into one, presenting on cloud native CI CD in under 15 minutes. Take it away, Cedric. Thank you so much. And it is true within 15 minutes or your money back. That's 100% guarantee on my part. So we'll go ahead and get started here, but I just want to say thank you all for being here. My name is Cedric Claiborne. I'm an OpenShift Developer Advocate. And I'm here to kind of tell you and give you a little bit of a hands-on intro to cloud native CI CD working with OpenShift Pipelines. And so how we're going to structure this is we'll start with a brief overview of CI CD and more specifically what CI CD is. And then we're going to introduce some OpenShift Pipeline concepts. And then we'll actually be making a real world pipeline right here in under 15 minutes guaranteed. So if you're like me, probably 8 to 10 months ago, a little bit of background, I'm a student, but I'm also getting some experience. It's my second summer interning at Red Hat. I love it. I love the people. It's a great place. But you're probably wondering, if you were me, what the heck is CI CD? So I've gone ahead to pull up the definition from the Red Hat website. And I believe it really encapsulates the process of CI CD. So it's introducing ongoing automation, specifically automation and continuous monitoring throughout the lifecycle of apps from integration and testing phases to delivery and deployment, the CI part and the CD part. And if we think about it, CI CD has a few different meanings. It's split up in half. The CI is continuous integration, which is this automated process for developers like us. Think of the building, the testing, the merging process and a GitHub repo that we're used to. I was 25 minutes ago just doing this on Jenkins for some of my Java projects I'm working on, which can solve issues of having too many branches in an app in development at once that could possibly conflict with each other, things like unit test, all that. The latter part though is CD, which refers to continuous delivery or deployment kind of each get used interchangeably. But what's important to note is this kind of helps illustrate how much automation is happening. So continuous delivery means that devs changes to an apps or automatically bug tested, uploaded to a repo, whereas continuous deployment refers to kind of getting that in production much faster. So whereas people like you and me can access it right after that. So it's that next step and builds upon the benefits of continuous delivery right here in the middle. But let's get to the fun part of what the cloud native version of CI CD is. So it essentially refers to a few different aspects. Firstly, on the left here, containers. It's got a support apps that run on containers orchestrated by Kubernetes or in our case, OpenShift. Secondly, it's got to be serverless, meaning it can run and scale on demand without meeting a central itch in to maintain that. And then finally up here on the right, it's built with devout practices in mind, meaning teams can have their own delivery pipelines alongside apps they build without the dependency on other teams having to weigh things like that. So our CI CD should be able to perform all of this with this in mind. And you already know, but there's plenty of options for your projects to choose from. For example, Jenkins we use here at NC State University. I have a love hate relationship with this guy, at the end he normally helps me out, but the one we'll be taking a look at today is called Tecton. So it's a powerful and flexible open source framework for creating cloud native CI CD systems. Been around for a minute, super, super flexible, super easy to use, integrate straight into Kubernetes and allows you to build, test and deploy across cloud providers and on-premise systems. And so OpenShift pipelines that we'll be talking about today is this native integration of Tecton into OpenShift and introduces a set of tools that are compostable, declarative, reproducible and cloud native to make building pipelines as easy as can be. So let's quickly go through the building blocks that Tecton provides, also known as OpenShift pipeline building blocks. And these are the main concepts that make up OpenShift pipelines. So steps, tasks and pipelines, they already make up the bulk of our CD system. Firstly, we've got a step which is a single unit, a single operation that we perform on our code. Say, for example, the unit test on your Python code which Tecton can perform inside of a container which you provide. So the one that we've got on the top right, that little screenshot that's building our app with Maven and the bottom right, it's gonna parse our Python code. So super simple, super basic, you can build upon these. And then secondly, we've got a task. So a task is a collection of steps that we just mentioned. So one, two, three, four, five, however many you want from unit test to building apps, all those types of things, Tecton runs these tasks in sequence inside of a Kubernetes pod, which in turn can run independent of pipelines. And then finally, the most important part, we've got the pipeline, which as we talked about before is a collection of tasks that can run in a variety of ways with different conditions that specify when to start the task and when to run the task in a variety of ways. So these are reusable across projects with it, which is definitely my favorite part. So it saves you and me valuable time that we could be spending on pretty much anything else. So we talk about this reusability. So this works with these input and output resources. So everything from Git repos to PRs to images, all sorts of things, you can use the pipeline with to be essentially flexible and reusable. So whether you're working on project A, project B, project C, it can all be run with the same pipeline. So I think that's super awesome. Definitely saves me a lot of time. And then lastly, we've got task runs and pipeline runs. So these simply define the execution of a pipeline. And I'm going to show you this a little bit later in this hands-on demo that we're going to run, but this specifies exactly what to be put into the pipeline. So for Git repository, anything like that, that is going to be the specific. So the pipeline run and the task run are kind of going to tell the pipeline what specifically to do.  So feel free to take a screenshot and check it out later because these pipelines are honestly a little bit fascinating. But let's get to the fun part of actually working with OpenShift pipelines. I promise you guys a demo, we're going to do that today. So as mentioned before, pipelines is the native integration of Tecton onto the OpenShift platform. And it offers all of these awesome developer features from being Kubernetes native, serverless, running pipelines in isolated containers and even going as far to having a visual studio code extension that you can install. So a lot of different features that they offer, but to install it, you can simply go to your cluster and search it on the operators hub, just the pipelines operator. And it's super easy to use. There's also a web interface for people who are more visual learners. But for me, I'll be running the Tecton CLI. So TKN is what we're going to be using for the rest of this demo to show you how dang easy it is to make your own pipeline. So if you'd like to follow along with this demo and you don't already have an OpenShift cluster ready, I've got you because we've got a hands-on lab that me and my team at Red Hat actually work on. So it's over at learn.openshift.com which provides a set of Catechota scenarios that are completely browser-based. Like you don't even have to have anything ready that'll allow you to follow along and learn not just OpenShift pipelines, but we're talking pork is serverless AI and a whole bunch more demos using OpenShift. So let's go ahead and hop into there. I'm going to stop sharing and reshare so I can switch tabs, but that's where we're going to be continuing. So it's learn.openshift.com slash middleware slash pipelines if you want to follow along with this demo. So give me two seconds here and I'm going to go hop in. I do like the pun. But yeah, give me two seconds here and I'm going to go and share my screen from the learn.openshift.com side. So let's see that should be sharing right now. So once you're in this side of our learn.openshift.com site, you'll go in and you can get a brief outline of what you're going to be doing through this workshop. Remember, you don't even have to have anything installed. These are completely free. We've got a lot more that I work on as well, but this is one that I've contributed to in the past year. So the first step to working, of course, with OpenShift pipelines is installing the operator. So I've gone ahead and done this. It takes a couple seconds. You can either do it going from, of course, the web console as we talked before, going to Operators Hub and installing through there or simply with a YAML file, applying that to the Kubernetes cluster. And then you can verify the installation with this quick script that'll run every five seconds to make sure you've installed it. So once you've installed it, great, congratulations. Let me go ahead and clear this real quick. See. A little bit buggy. But what we'll go ahead and do from this point on is create a new project. Actually, I might need to refresh the page. I think sharing on Hoppin can be a little, a little bit tricky on Chrome. So give me like two seconds here. That should still be able to see it. So yeah, as I mentioned before, you've got the outline brief right here. And we'll go ahead and reinstall this real quick, but give us two seconds. Sweet, cool. So it configures it for you. There we go, we can type. All right, cool. We'll log back into the cluster and go ahead and install the operator through this super easy OpenShift object. And then we'll go ahead and verify the installation. And so next step, of course, is gonna be super easy, creating our Kubernetes project or our OpenShift project. And you can either do this through the console here, through the terminal here, go to the web console right up here, which will bring you to a new page where you have your own personalized web console that you can use for up to 60 minutes, completely free. Again, you don't have to pay for any of this, which is super cool, don't tell anybody. But we'll go ahead and create this once the operator is finished installing. But let's take a look here at our first task, which I think is super awesome to see this live. So a task is, as we mentioned before, a series of steps that run in a desired order, doing everything from a unit test to building something. And we've got pretty much the most basic tasks that you can see right here, simply echoing hello world to the console. So let me create this project real quick. And let's go ahead and work with this sample task. So we've got this here, and it's already on this file system in the directory task slash hello.yaml, it's already there. So as you can see, we've got a little bit of data about it. The name is hello for our task. The step is called say hello, just literally running a UBI image and outgoing hello world of the console. So all we have to do is use the command OC apply, apply that, and then we can use the command TKN task start to really just go ahead and start this and see it in our console. So it's as easy as that to really get started using these different tasks. We'll give it a second here and it's gonna go ahead and spin up this UBI image and do this command to the console. And we should see it here in a couple of seconds. It's gonna look a little bit like this. So we'll wait for this task run. As I said before, task run kind of gives you the specifics on configuring these different tasks and pipelines and stuff like that. So we just ran our task right here and it gave us the output of hello world. So super cool to be able to see that live. Working with task resource definitions can kind of allow us to make custom pipelines and a whole lot more. So this is a great example of a task that has a whole bunch of different parameters. So things from a manifest directory to the different steps of applying an image. Here you can see the specific image that we have an origin CLI. And then also arguments like we had before where it was super easy. We were saying echo hello world and we saw that right there with through the say hello step. Well, we're gonna be doing this just a little bit more with applying custom manifest to kind of build our application when we start this pipeline. So we'll go ahead and apply these three tasks which I'd love to get into more detail with but we gotta run through this real fast and I wanna take up you guys's time too much but we've applied these three different tasks right here from a persistent volume claim to updating deployment and manifest. And if we run TK and task LS this is gonna show us what kind of tasks that we have active. So the hello task from before we can see that that we applied it a minute ago and then apply manifest and update deployment. So this one is the apply manifest we can see that it's been here now. And so now we can see it and let's get to the final part of actually creating a pipeline. So a pipeline is a collection of these different tasks that we can use different parameters to start to stop things like that. The tasks that we're actually running is combining a API and a UI for a voting application and pushing that out using the two different tasks that we had before apply manifest, update deployment to actually spin up a pod, actually two pods that'll be live on our OpenShift deployment and be publicly accessible to the web. So if you keep on following this along within 10 minutes, you'll be able to actually see this live but let's just take a quick look before we end up at this pipeline and what things are gonna really look like when you're working with OpenShift pipeline. So what this is made of, you've got the same metadata as before, our build and deploy pipeline is right here. A bunch of different parameters and specifications here. So as I talked before, these are completely reusable. So you're not gonna see any specifics when you're working with these pipelines. So deployment name is gonna be custom, get URL. Of course, there's no specific URL that we're working with but we know it's a string. And then actually you get down here you can actually see all the commands that are gonna be run. You can see everything from a builder, yeah, working with builder down here to creating workspace and using the apply manifest task before. So there's a bunch of different steps and the last part here is actually using a pipeline start and triggering this pipeline with a bunch of different custom parameters from our URL to our image to our registry and then actually deploying that live to a cluster which you can do after this presentation. And I highly encourage you to do so because it's a great learning experience and you can continue on to verify the deployment and actually have this live. So unfortunately, I don't have enough time today to be able to do that but I do have enough time today to be able to thank you for being here. I appreciate your time and I hope you learned something today about cloud date of CINCD, how to get started, how to do tasks, how to work with pipelines and once again, I appreciate your time. My name is Cedric Clyburn. Feel free to reach out. I just created a Twitter, I might be in college but I'm just not too tech savvy with Twitter. So feel free to follow me, I follow back, see some of my other presentations I've worked with, OpenShift pipelines a lot but other things like Odo, Odo's a favorite of mine and getting started with work with OpenShift. So I have different presentations I've done on that but again, thank you so much for being here. My name is Cedric Clyburn and enjoy the rest of your day at DefCon. I'm happy to stay on here and answer any questions if you all have any. Yes, good. Okay, that's where you just jump off before I ask you. Can't do that. So not many questions yet. I dropped one in earlier. I don't know if this is a free view or not but here you go. So can you comment at all on something like Argo workflows versus tech on pipelines? How do you see them fitting together in like grand scheme of things? Yeah, wait, what was your last question? How do you see them? How do you see them fitting together on a system? If they fit in at all, do they like compete against each other or? So yeah, I've worked a little bit on our workshops that we have with Argo and I honestly think they're great complementary tools. So I've personally, I've never used both of them at the same time. I feel like they have great applications for different purposes. If I want to be a little bit more nitty gritty and see the specifics of what I'm trying to run and all the steps and everything, I would definitely go with Argo. OpenShift Pipelines is more if you're, if you like to be a CLI type person, if you like working with YAML files right in the terminal. I actually was introduced to OpenShift Pipelines first in my CICD journey. So I, that's what I'm more familiar with but I think they both have their distinct advantages and disadvantages but I'm a big OpenShift Pipelines guy but you know, I'll love. Exactly, right, we're all just trying to solve problems. Yeah, exactly, exactly. And I feel Argo CD is very, if you want more specifics but Pipelines is very native to the whole OpenShift ecosystem. So it's literally built in like if you know, they've got an entire web console within the OpenShift console. So it's easier to work with if you're a visual person and you just want the simple steps. If you're still here, so normally that whole presentation takes an hour. I was running through it but it takes 50 minutes to an hour. So half an hour is the presentation, half an hour is the lab but I had to condense it to 15 minutes, actually 10 minutes beforehand but they gave me a little bit more time, which I appreciate. So I tried to condense all the information but there's definitely more out there. And if you search YouTube, I've got a whole presentation and my team has the full hour talk about using OpenShift Pipelines and a great introduction as well. So yeah, good question. Do you have any links that can drop in chat for our audience right now?  It's not me specifically but it's Brian from our team, which I love in the door. So he's a great talker. So I'll go ahead and throw that in there if you're still here. Like two seconds. So yeah, bro, thank you so much and I do appreciate it. Yeah, I mean, outside of that, it doesn't seem like we're getting too many questions. So I won't keep you for too long. I don't get a sign.