So welcome to the docs meeting of the OKD working group meeting. So hi Eric and hi everybody and I'm going to put everybody on camera today just so that we there and I'm sort of working through the recap blog post. I've got a preliminary one in the okd.io blog this morning and most of the main stage videos have been uploaded and separated into their individual talks so there's one by Charo, one by Vadim, one by Jamie and one by Joseph. So those are there now plus the one long full on edited one and there goes a dog behind Mike. I love this. I don't have a dog anymore so I'm living vicariously through everyone else in zoomlands dogs these days. So that's happening. I just had and he won't be able to join us. Jamie from Umish has another obligation at this time but I just did a chat with him. He's I have run completely run out of disk space on all of my hard drives and the sessions, the track sessions were very long so I managed to get the homelab one edited enough and then ran out of disk space completely. I'm now so it's been one besides losing internet access I ran out of disk space on my editing machine. It's been a fun couple of days but that said I got the homelab one up. I just retweeted it and there should be a blog post shortly on okd.io. I just have to add in the links to the individual videos as they go up and Jamie from Umish is going to edit the other three sessions and upload them to YouTube for us and I am forever grateful for that and you can see what we're doing. The question that I wanted to discuss today and if other people have things on the agenda let me know was now that we've done the workshop and there's a number of stubs and Eric and Robert I don't think you were there this weekend. I didn't see your names on the weekend workshop and I'm not going to hold it against you but Mike if you can share your screen and show walk through the docs on the deployment and configuration guide where they are now so that Eric and Robert are up to speed on that. What I'd like to talk about is where they should live and now that we've done that and what else we need to do to them to kick off this and then the other thing I'd like to talk about is reviewing all of the docs that we have after we have this first conversation and trying to come up with a cohesive coherent documentation strategy for okd and I've had a lot of coffee so I'm going to try and not talk too much today which is impossible because it's me. So we did have a few pull requests against it I believe during the thing but I think it was all from known entities. Did we have any at all from attendees? Yeah probably not so I'm sorry I just need to unmute my mic there sorry yeah no we didn't it was just Shree and Jamie and Padine put up PRs. All right and I think the one that Charo did if you go to it is a good example Charo I think just put in a stub for his home lab that reached out to his blog post. Yeah I don't think he created a stub and he didn't create a PR yet I saw that oh boy now I don't know where it is it would link to me like a gist I think he had put together but yeah no he didn't he didn't put a PR up for here yet. Yeah so what I'd love to ask you to do Mike is if you can put in a stub for a home labs because there's and there's so that we have a stub there and because we in the workshops we ended up with I think three different approaches to home labs Craig Robinson's Shree's which is very specific to his work and Vadim's so I think that was I just noticed we got two bare metals there I need to clean that up a little bit so did you want to see like a top-level home lab okay because what it seemed like what people had been doing so far what I tried to encourage was people were going into bare metal and putting their you know putting their username with their deployment. Yeah so um yeah good yeah so that's probably not like great documentation process so there still needs to be some cleanup and editing on this on these configuration guides so that they have some uniformity to them and and to be quite honest I'll say what I said to Jamie earlier I we were looking at the OpenShift.com blogs and the home lab for 4.5 that Craig Robinson did that I reposted and OpenShift.com head is still in the top 10 of blog things that get hit on OpenShift so the wording the wording home lab is an attractant to developers and more so I think than bare metal um and I think bare metal is more along what Andrew and Justin Pittman did that it might be there and I think he also has some stuff to give us to track down but so I think this is this is the link sorry yeah yeah so that's that's Charo's stuff so we have some still some work to do here before it's ready to pull into another repo and make it live and breathe um yeah so my my druthers is that the bare metal one maybe get extended to be bare metal with I think he used live vert um yeah so that when you said that yeah like uh Jason or Justin and um you know blanking um yeah they're and Andrew um they're their lab yeah I wouldn't have called it bare metal so much as I might have called it live vert you know because that's really they were exercising the live vert pieces of the of the cluster to build there now did did they use overt uh this time uh as on top of that or I didn't get to see that because uh I was being the straight man for Charo yeah um I did put the raw file up on um YouTube um so I can share that let me just grab that mistake I I thought it was I thought they said live vert but I I mean I also joined late because I was at that session with you know Bruce and Charo yeah so let me just um yeah asking good questions yeah so I'm just gonna I was trying at least I'm just gonna go back in the chat and I'm gonna put a link it's so it's so don't share it quite yet everybody can take a look at this is Andrew's and just skim past the first 10 minutes because that's all them trying to figure out how to set up their screens um and that's what has to be edited out but um that's the video if um Bruce you want to look at it or anybody else wants to look at it so Diane I wanted to step back for a second though and go back to talking about the configuration note your guides uh repo because I agree with you like you know the more I was thinking about it over the weekend and the more we're kind of like you know we started to get some pull requests in there you know yeah I one thing I would love to have is like a template that we could use we could kind of say here you know and and I'll look at the sections we have now and maybe I'll just try and call out those sections and say you should have like a hardware section you should have section there um but then also like really the shape that this information is starting to take is yeah it's much more like a community response it's like here's how people in the community are deploying this but I don't really see it resolving into like a set of like oh here's the one I pick and like I'm going to follow this one exactly because right now it just feels very much like a you know like just community notes that people are throwing up there and saying here's how I did it you know so if there's a way to make that more useful to the community maybe by organizing it better or whatever like I you know I'm all yours for hearing about how we can kind of push in that direction was this two things that I wanted to say about that one is um is is you're absolutely right um and a template like in the readme file at the beginning of the configuration guys what you know what should be in your your stub or in your guide and then to figure out the categories better so bare metal should maybe Andrews and um Justin should get shoved into something called I think it's live for if you watch the video you can see it there um and I was also going to say this and everybody can argue with me about this is that I think it should live in the okd.io site um rather than OpenShift Origin or in okd land and I'll explain what I mean by that is one is if it's in the OpenShift repo it um has connotations of officialness um and it also means that we have to follow their guidelines for merging new content in um and ask their ask the engineering team that owns the repo or bug Vadim or bug Christian whoever has merge access and um frankly I don't even want merge access on the OpenShift repo at this juncture there are you know thousands of customers relying on it and if I screw up or I don't want my name on the front page of the Wall Street Journal for introducing some bug um however on the okd.io site I do own that um and um there are a couple other folks there so if we move this and then we could format it any way we wanted we could make it as beautiful as the porter.sh site um we could do whatever we want so what I you know and and I would not that I don't love you Mike but um I would love to move it over there sooner than later um so that people get into the habit of pushing stuff there if that's okay and yeah I'm totally happy yeah yeah and so um I'm gonna pause for a minute and Bruce you were about to say something so I'll shut up for a minute and then I'm gonna ask Eric and Robert because they're the newbies on this call what they think about it I was gonna say wait sorry not to interrupt Bruce but Robert had a question in chat too so maybe after Bruce let's pick up Robert's question okay well he can go first if you want I'm not you know standing on ceremony okay um so Robert had asked like what's the difference between the the guides repo that we're talking about now and kind of the official installer repo where you know you've linked to the upi so that those things you link to in the installer repo those are actually artifacts that I believe are used during by the installer to actually create the installations what this a really repo that I created originally we were just calling it notes because what we wanted to do was we wanted to collect information from people about what their clusters look like once they were actually deployed right so we wanted people to contribute like I know I'm running vSphere and I followed the standard you know IPI installation and I ended up with this but then maybe that that person says but I also run vMotion in my cluster and I have all my storage set up in vMotion so that I can you know move disks between nodes or something right and then they might have a section in their thing about like here's how I set up vMotion right and so the idea was to start getting all these user stories for the different ways that people are configuring their clusters kind of I don't want to say day two but once they get to day 1.5 you know once they've passed installation what does what does their configuration look like and are there any customizations that they've had to do you know to kind of get there so that was the intention on on creating these guides and just and so those and those are maintained by the red headers and the engineering team and not us for the most part we can make if something's wrong or grammar mistake it's linking or what you can make a poll record you because you're it's all out in the open but the stuff that we own and the stuff that I can control or give Jamie and other people in the community access to merge into it lives here in this github repo and if you're wondering what the CS stands for long time ago customer success so and it's also where project quay lives and the openshift commons website lives and hopefully soon commons will get lifted and shifted out of there and moved into if somebody's merging migrating to Drupal it feels like going back in time what is that movie with where you go back to the future part 21 that's like I'm going to a Drupal site yeah okay but uh hey a long time ago I was a big player in the Drupal community so hey I'll get to meet some old friends again so that's all good but um but this is where I think we should lift and shift the guides to like we have the blog the config community configuration the end deployment guides um are here and that way um and I'm going to keep putting in the porter dot sh site is my um fantasy island um site for really good documentation and I don't think I can wangle enough permissions for everybody in the community to do this under the openshift um re open source repo I I know I know because I own it I can do in the okd.io resource so that's and and that will also especially and this is what the way that Diane thinks is if we put in a lot of stuff about home labs like we have you know one of the guides is about home labs that will help drive traffic to okd.io um and get people more people involved in the working group um because um to be there are there are I would say probably just shy of 500 um people who have deployed openshift um okd for somewhere in the universe whether it's production or or edu use or you know or just your home lab there's there's a good chunk of people here um and that that's awesome um and and there's about I just under 400 people on the okd working groups so the thing is to try and get them to come to the okd.io as the portal into that links to everything and um and I think we can do that um and I think that deployment and configuration this is why I've been so hot on these doing the okd marathon and then do the these other things and getting up on youtube um is to keep driving awareness of okd for and it's been semi effective um and probably as effective as the sales team at openshift wants it to be um but it could be better um and it could be easier to to maintain so um what I was going to and and now I'm going to stop for a minute so Robert and Eric you're guinea pigs here today I don't know where either of you are from um what companies whether you're red hatters or not but um tell me what you think of that idea is that where you would go your I see the red hat sneaking out there Eric yes um behind you yeah I have one over there I'm just tilted the wrong way today um so tell me what you think is that am I thinking correctly about this and you can say no because I'm very good about say hearing you know so um what I like is the idea to summarize all of the okd related content on the okd website I also like that we have this new word okd for the free and open source part of openshift because it is it sounds very different and there's always this kind of confusion between the product and the actual open source project and having everything as okd and getting the okd letters more into the face of people will also teach people more what is actually the difference and what is the upstream project basically and um yeah with the documentation I I feel like there's something where I want to help so I'm personally very interested in the single node areas it's also why I want to look and I was also in the workshop with Charo and also afterwards we had to have a call so he could help me get the last steps done and I also made some changes to his scripts and would have some small changes that I would like to make to his blog post where I don't know where I can hand these changes in and having a central place where we put all these documents is very helpful and yeah it's it's really a little bit a question there's the open shift documentation that's on the open shift website right then there's some things that we are now doing for the okd stuff and there's also if you have a customer account you have some customer documentation as well right and it's also not one on one and there's also a little bit a difference in focus between what is on open shift on the public open shift website and what is basically the customer documentation where you need to have a subscription form and it's it's probably a good idea is that we have a clear understanding what we want to have in each and if I understand Mike sorry Mike is the correct name because it always says Emiko so I'm always not sure how I should go either one works either works then I then I call you Mike and if I understand you correctly what you basically want to show in the okd documentation is like what are what is the result of what people are making out of the documentation right and there are also some individual adaptations and to present different scenarios basically like in the past we also had these kind of deployment scenarios that like a solution architect could bring to a customer that we maybe have something like this as a focus for the okd page that sounds reasonable for me yeah so no big no from my side at the moment okay so Robert what's your perspective are you with red hat as well I don't see a red hat behind you so um I have no thanks so yeah I have a red hat from a conference but the girls are playing with it yeah it sounds very nice but I'm afraid how we can update or again the documentation and up to date state the whole time maybe it's maybe it's a good good idea to put it like a block because if it's like a block you know the date you know how old the stuff is and you know it's one year old it doesn't work maybe yeah so but but if it's put in a kit repo it's not that clear for which version it works and works not so I think Mike in your template that you're discussing much like with the blog posts um that um we have it has a date timestamp on it like it that's one of the things and you know it has the ability to tag so what if you look at the read me and I'll just share share to do something like if you can if you don't mind me asking you to do this is to to create sort of a template for what the should be in the guide um because Robert you're absolutely right these things one thing that I really despise is is documentation by blogging you'll always hear me rant about that because internally at red hat we've had this I I've been at red hat now eight years and we get a lot of brownie points and pats on the back for writing a good blog and just like Craig Robinson's home lab 4.5 blog is in the top 10 it's now completely out of date or not completely but just enough to make it nasty for someone trying to do it so um if we had a revision scheme and a freshener state in the um in the documentation I think that would help in the in if it were in the okd so that people would it would trigger people and instantly to go this is release 4.5 this is the version of it and then you could have sort of a bit of a hierarchy of that and um and then we could um what do you call it when you retire something um an older version yeah so we could retire deprecation thank you very much for that word today word of the day deprecation I want to deprecate myself um for a week and go on vacation um but I think that Robert that's a really good point um and as Bruce put in a link to yet another um set of documentation red hat is famous I think externally for like really complicated strategies for um in every business unit within red hat even though externally everybody thinks of us as duck red hat and thinks we are totally coordinated on every product silo um you you will find stuff like that Bruce he's he's linked out to the red hat dot com sys admin kubernetes cluster laptop um link there and um which is you know another resource but that is um I think it sort of worked yeah and is that one OC I didn't open it up but is that ocp and someone who has uh no no no I think that I think that was no kd1 um but uh it was back in the time of beta yeah um but but I mean if you look at the architecture that that he's using there um it's pretty similar to other guides uh but so maybe his I'm just taking a look at it so as a good template is that what you're suggesting with this uh well actually I guess I had a couple of comments uh although you know Eric and Robert you know made a number of excellent points uh in that uh things do quickly stop working and um you get to where um often something if you tried to follow it exactly it wouldn't work for a variety of reasons so for instance uh you know Charo has some excellent guides um most of them don't work because uh they're they're based on versions of centOS which you can't get anymore yeah okay uh so he's he's uh his cluster version um was based on a uh you know centOS which had a uh centOS minimal which the last centOS 8 version does not have and then that breaks everything uh and so he for about last year he's had a uh a note you know going to centOS stream maybe only six months but you know of course everybody's busy and that would be a big change you know like I'd be happy to have him help him work on getting it together but now he's getting paid by Red Hat to do actually useful stuff so that's going to impact his time presumably yeah but his wife is away for a week um and he's been editing everything so um we take advantage of when our partners leave um and and that's what I think uh just say I think one of the things that uh could I've actually tried a bunch of of those uh and uh sorry the first one that worked end to end was was Craig's 4.4 uh one and I actually liked his architecture better than his switch to 4.5 you know but uh and none of them quite worked but uh but uh you know with various changes I was able to get them to work and sometimes it's very minor things like in his uh uh one of the things I didn't look at when I was just doing it because it worked for a while was he he put in a uh non-default network in his install config and it turned out that that was the uh OpenShift SD in one which on vSphere broke and it took me about a week to go through and sort everything out and figure out that that was exactly what broke it and it was actually just a random comment that Christian made that clued me into what the problem was you know which I discovered on Slack so it was like just total fluky luck yeah that uh I went through did that but but uh and I think one of the things that uh now I'm making this is another point in my rambling one of the things that's difficult uh that people don't always clue in on is exactly what are the assumptions that that one of these guys has so for instance on VMware uh you have to dig down deeply through a guide before you know whether or not they're requiring command line access uh which uh means that uh if you're a developer you're not going to have that uh for your company because they won't give it the the system and people won't give it to you if you have a home lab then you do okay and uh sort of in passing uh Joseph uh commented that uh you know he'd bought a uh you know VMware license etc etc etc um that's the sort of thing that you probably want to make explicit up front if somebody's going to go through a guide they don't find out at the end of it that they need this other license and then they have to go through the hassle of getting that so you know like I think that uh and I guess Charo and his guides was pretty good up front saying what his assumptions were um but that's not something you know I mean like our assumptions are transparent to us we're not always even aware of them so I think that would be sort of a useful editorial thing for somebody to look at these and say okay if you're going to go through this guide this is what you're going to need to set up or this is who it's for there are also some problems with that right um things also change all the time like with Charo I'm also discussing like maybe we don't need the bootstrap node with the next version of OpenShift anymore and so that is already a big requirement that goes away and maybe in this single node installation we still create two VMs because we need the bootstrap node then maybe we don't even need to create VMs anymore we can just install it pure bare metal without any VMs so you know the expectations change a lot and we don't know yet how they change because we are not assure uh how the development will progress there and nobody can really tell you you know the developer who's currently working on it you also cannot tell you everything that he would discover during the development so yeah right but until until it actually happens it's not real right I mean you know like there are promises but they can be decommissioned in any version going forward right like the single node cluster was at one point promise for 4.7 I think it's currently promised for 4.8 we're not there yet I will commit to the 4.8 I have heard it from above it's coming so um I saw an official red hat documentation for 4.7 I know you did but you didn't hear it from me if I oh that's different this is the dine in commitment the okd commitment um mostly to the bank take it to the bank right and um the bank of Canada and um the bank of Walmart there you go um and it's recorded here um so I'm gonna move back again so I think what I would like to ask Mike to do and maybe work with Eric um because Eric was in the homelab one is to create a template in the readme file in the okd.io much like the blog post and use Charo's homelab example because we have his blog post and retrofit Charo's into that because Charo is pretty good um at helping that and see if we can get one and and folk not not I shouldn't say homelab single node cluster approach and then also have and we're doing it have a depreciation tag too so like because we know that the single node cluster approach of Charo's is going to get depreciated so some workflow of like this is the timestamp it's version 4.8 and if I share I mean see if I can share my screen again for a second so I'm not tucking out my um here um if it's okay to think this so this has uh but didn't go down I didn't push it like it if I go to github the go down to the readme here and it may you know right now create there's a little section here create a blog post um do something similar to that um for for the deployment guide so like this is something I was going to ask like I mean we could convert the deployment guide into a github page you know that's like Jekyll head matter is what that's what's going on there so like we could convert it into some sort of like you know static site generator if you want and use git and then we could just have like you know a github pages site where all this information will be assumed in there if you want to if you want to go that route we could certainly add all that marked on there yeah um I think well for me and this is Diane creating a blog article is is wicked simple um though I still and if we know the structure of what we want and everything that's in those things we should be able to do it and I know Joseph has figured out all of the ins and outs of adding the blog into the the okd.io site so it should be just rinse and repeat what we're doing for the blog but using the structure but the blog structure is slightly it's not as hierarchical it's just yeah I guess I guess that's the question do you like so here's here's what I got so far um we want to move bare metal to homelab change the bare metal stuff to homelab um make a template uh for people to use to create their guides and I've got a bunch of information here we want in the template like you know date and version prerequisites or assumptions description hardware target audience and then some of the information we have already um and then maybe we also want to move this at some point over and so like do we want to just you know I can I can convert that to be to look more like what the blog does structure wise and use like one of these you know static site generators I'll even I mean blog is just kind of a short way to say it but really it's just a static site generator that's you know templating all the stuff together I can add that in there if you like yeah we already have that for the site itself and and Joseph went through the the so just reach out to Joseph um we're using middleman and um there I think they are they upgraded to Jekyll's a later a newer version of it so that I don't think we have to pick another one I think we can use what we use for the site um so and we can have that conversation separate from here but I think we already have what we need for the build process for the site to do it it's just um I would I think I was thinking the blog is very simplistic it's not um it doesn't have the um hierarchical structure that you have in yours um not positive but we have it it shouldn't be tough to do but no no you could certainly configure it to bring all that stuff in I guess that's kind of my question is like do you just want the files in the guides repo to kind of match the format for the for the blog and then you could just pull them in later is that would that be the best way to do this um I'm just going to stop sharing for a minute I gotta think about that um I am not a documentation specialist um so um I have an opinion um I would like it to match the style of the okd.io site um and to use the header and everything else like that but um if there's a better way of doing it and I'm going to I keep saying this is my fantasy island thing um I'll just go to porta.sh and go to yeah I'm not I'm not super familiar with porta I haven't really used it much but I mean I've built a lot of documentation sites so yeah I have not so I actually would defer to you to to make a decision about that this is sort of this is you know yeah I would never go with that style actually it's too cutesy feely for me okay what that's why I prefer I prefer I prefer the okd.io style okay thank you sorry about that that's all right I that's it's a backhanded compliment because I created it um so I mean the thing is in some ways the the guides are kind of different from even like Charo's blog and whatnot you know the guides are more just kind of data that you could look at and kind of like use as a reference um they're not necessarily formatted in a way that's meant to read like you know like Charo's posted because he obviously put a lot of time into structuring it that way um so I mean I could take some I could take some first stabs at kind of organizing this stuff and then we can see where we get to and maybe you know kind of like assess at that point like my preference at this point would just be to have the guides as plain markdown and just kind of like doing what they're supposed to do which is being a guide for how a certain deployment went and then our next operation will be to figure out like okay do you want to pull those into a website somewhere do you want to put them on the blog like let's just get the data right and get kind of the categorization right and then we can decide how we want to display it you know next you know at a later date so what I would I'm going to back myself up then backtrack so in your directory right now in the read me file um to put some best practices template information in there for people who are coming to your directory right now let's and keep and I'm paraphrasing what I think I just heard you say if you can do that so like you should be have a date time stamp or release version assumptions hardware requirements and target audience I think those would cover out a lot of things here should be in sections pick the pick whichever one you you like I'm going to lean towards single node because I know Charo has time right now and Eric was in the session and it is one that we're going to have to depreciate soon so we'll go through the whole life cycle with it so well in my head take that one and format it the way we think it should be that like as the best as the standard in your directory in your repo um and then we'll get Andrew Sullivan and Justin Pittman to do the same thing for the Libbert one and then I can tap um Joseph and um Jamie to say that again I said Charles as well yeah so that's you know that like uh but the thing is Libbert's I think actually you almost we're almost getting enough guides that you need a taxonomy or a decision tree of what you want and I think that the the number of choices is actually not that great between them so you could actually organize them them fairly easily so that would be a lot clearer um you know the sort of top decision is okay so are you are using a cloud provider or your own hardware basically uh and if using cloud provider which one then you go off on on those and it would be nice to see open stack in there somewhere I mentioned that before I'll mention that again yeah we'll get we'll get there I have an open stack and then uh the next sort of decision is as uh uh you know are you going upi or ipi if you're going upi how are you setting up the prerequisites uh you've got choices for uh ghcp dns uh uh ha proxy sort of thing um load balancing as well as trying to think of uh and then next are you using any automation tools okay so I think that the main difference between charos and andrews was the automation types of things they're doing uh charos using bare bones uh bash scripts you know fantastic you know goes way back into antiquity and still works um you know other people using terraform or you know on and on and then you get to actually doing it yeah can I ask you to write up a taxonomy just in a gist file just take that not that we're going to use that right now to frame the documentation mic because I think right now if we just got right here single node and maybe an open stack um you know that would be a good start they could you know they could be referencing other chunks of other people's documents and stuff but um but I think what you're discussing is sort of the decision the taxonomy the decision tree of which guide to use um if you're a user right yeah because you come in you know fat dumb and happy and uh I can you know refer to myself in that uh and you have you don't have a clue so where do you go yeah and you've got 20 choices yeah so the guide to the guide is what you're talking about is and then you know say so you're using a cloud provider and um you want to do um UPI and you want to use Limbert I guess you know and or a specific load balancer then then the tree would take you would have maybe a list of suggested which guide to follow and that would be like rather than trying to structure the guides based on that because I I think we're only going to have like maybe four real guides maybe you know total um and then like with home lab there were three three different you know approaches to it and we can call them approaches right um there but I think the taxonomy that you're describing in my head that's the decision tree about which guide to take a look at um you know which one fits fits you best but realize it's not using the load balancer you want right yeah with a lot of the guides you can actually swap things in and out they're not that critical to the guide it's just that somebody made a choice and it works at least this week and uh but there were other choices that were possible without making a major change to the guide I think what you're describing is a guide to the guides maybe yeah and maybe eventually it's um once we get the baseline guides in a way to restructure the guides but I I don't hesitate to um redo all of the guides as we have them now in chunks like that like yeah but that's me I and and I am not a documentation specialist I'm just trying to get the guides in the right place with enough information and expiry dates that we can move forward a little bit um and you know and right now everything just at the blog post that I'm writing is going to link to Mike's repo um and a bunch of YouTube videos which isn't super effective um and not really maintainable over the long run so um we love Mike's repo uh I I was just I totally appreciated um but I'm a little I'm a little confused at this point because like I think maybe you know some of my intentions when originally creating that those you know notes as we called them back then and maybe where this is going are out of sync here so like if I understand correctly Diane what you'd like to see eventually in those guides is material like what Charo created like a full walkthrough of how someone can do an installation is that is that what you're thinking it would be lovely if all of them were that verbose and that detailed I don't expect all of them to be that verbose but it would give them opportunity for other communities like if somebody wasn't as verbose as that they could make a pull request and add verbosity um and detail so like if someone um just put a one liner in there use you know f5's load balancer um and someone else would say or use the one that come you know this other one whatever but what I'm my goal is is it's not just verbosity but it's giving people a place to put their guides as well with some guidance about what makes a good guide and an expiry day you know so so no note not everybody is going to be as verbose as Charo and I don't want it to be a replacement for the OpenShift docs or docs.okd.io so I'm not expecting you know superhuman efforts um and as I'll go back to the beginning of this conversation one of the things that I'm trying to do is drive people to come to okd.io or content blog be it blogs or these kinds of got community guides um and but I don't know if that really helps you um but it does to some extent I mean like the the other thing though being that I have to be completely transparent about like why we created that repo and what our intentions were when we created it and this is why we called it notes originally because we really wanted to capture you know where we were addressing a problem that we're seeing internally which is that you know especially for things like vSphere um users have an incredible number of options that they can exercise when deploying their cluster and um you know as someone who is kind of on the front line of debugging a lot of these things it's really difficult for us to find good examples of how like someone like I said might have installed vMotion in their cluster and they're using it right and so what we wanted to do was we wanted to just create a place where people could put notes about like all right I'm doing a UPI vSphere installation and I'm using vMotion for all the disk images that I'm using so like here's the hardware that I had set up and like here's a couple notes on what I had to do to get vMotion working so we weren't necessarily trying to get like full like front to back like install the whole cluster guides we wanted just a place where someone could go and say well I'm thinking about doing a home lab let's say and I want to use this type of hardware what what how much will I need and they could look at one of those guides and just say well I'm going to need six machines and they're each going to have to be four core and eight gigs of ram or you know whatever someone could just look very quickly and figure out like what would they need to start doing this right um so that was kind of our original intentionality like I'm I'm I think it's interesting what you're talking about in terms of having these richer guides there that's awesome content it's just it's a lot to ask people to kind of you know create when they're coming yeah so and this may be at odds with everybody else's so the way that I vision it is rather than Craig Robinson writing a medium blog post and Charo doing wherever his is and you know and Bruce you know finding something in Kubernetes cluster laptop sysadmin blog somewhere on red hat that this would be the home for that that we would require some basic things like date timestamps of release version the assumptions hardware requirements target audience and and I just added a thought of and maybe a link to a video walkthrough of your deployment there as you know if it's available um and as much verbosity as you can um with and and that and that I think and then and then we can also when a new release comes out they this has been depreciated you know this no longer works you know or and then then we could also add in make you know maybe in the guide um the way that I think this is the way Diane thinks as an appendix of like notes about the motion you know or you know things like that but what I want to first get is the ones that we have I want to get the verbosity of that blog post in there with these minor things you know details about the date and timestamps the release version assumptions hardware target audience and any links there added in so some of them have it and stop having and not I don't want people to stop writing medium blog posts this is not what I'm saying but I'm like that drives you know that's wonderful and I'm about to do a blog post talking about those three home lab things including craigs and that and so that people drive people to watch that video and I want to be able to link back to something at the moment in Mike's repo that um has references home lab right um so that's that's where I'm coming from and nothing in your repo right now does that you have a bare metal thing and you don't have the single note thing so those those little structural things I would love to see that done in the next couple of days so that I could put a blog post out and on openshift.com and on okd.io that drives everybody to okd.io and to this and the sooner we can get it out of me Mike's repo into okd.io the more one will be able to track who's contributing as opposed to contributing to okd versus contributing to Mike's repo which is important to me as a community person um and also give credit to folks and then you know if Mike gets hit by a bus and Diane gets hit by a bus okd.io still lives on and Diane is not planning or either of those things to happen um but I also think that yeah so so my short term ask of Mike and because we get seven minutes left is to look at what you have there get the structure of the guides to reflect at least at the bare minimum what we used for the workshop right and maybe move Vadim's and Shree's and Craig's notes into the homelab one and Caro's into the single note cluster one and if you have the time um put in those um date timestamps release version metadata tags in there um and then when you get to that point maybe that's next week we look at it at the Tuesday meeting for the okd working loop or prior to that if you would like we can lift and shift it into the okd.io so it'll be running in parallel for this week and then make what I would like to do is I'll hold off on doing the post on the homelabs blog post until the Wednesday after next week's meeting to make sure everybody's happy with the move from Mike's repo to okd.io and that we've done it well um and so that's my goal by by next week to have it moved out of Mike's repo with some semblance of structure that matches the workshop um and Eric if you want to weigh in and help him with the homelab one and at the homelab with the single note cluster one um that would be great and Bruce since you were sitting through all of Caro's stuff that one fits it and Robert you are guinea pig external viewer of this to see if we got the structure right how's that that's good all right so I okay so what were you asking me to do and I'm asking you to be a reviewer a cynical okay what did you say happy and and and whatever with the other one where it was and yeah fat dumb and happy yeah there you go um depending on the day I emphasize one of those more than the other but yeah and and then you know and the ask of you is Bruce is to to really to maybe make a just a gist file for next Tuesday's meeting that is a taxonomy of um where to point people to like think of it in terms of if you know if then else if you're using a cloud provider you know yeah yeah well I mean so some of the things I'm suggesting are more long term okay so I'm not trying to get into the way of the short term so don't don't get me wrong on that you know like if we never get the short term accomplished we never get to the long term but I don't want to capture that workflow the decision tree there that you're talking about because I think it's important and even if that to start with Bruce is just a blog post on okd.io to use Joseph's mechanism for how to make a decision about which guide to use or you know what are some of that that I think is important to capture um and and I think it is a good factor in the guides yeah I will get um Charo to change that um Robert yeah I think that's just um I don't know what I don't know some of the stuff is not obsolete as quickly as you might think if you can in other words like in theory I could install 4.4 and then update it yep okay now I haven't actually tried that but uh you know because I mean things get too stale it's you can't update it anymore but it doesn't have to be in the latest and greatest as long as it still works and you get something which is updateable okay and um Robert and Eric are both um pointing out a good thing is um what license are we going to put all this under and let's bring that one up at the um meeting next week and I will um poke Charo about it between now and then about why why he chose gpl3 I don't know um and if that's a stopper but as Eric points out it's text and maybe we just need to put creative commons there somewhere um but yeah that is a conversation we should have next week so um yeah I was because I had a similar thought to Eric's when I was looking at the Apache license I was I originally just put the Apache license in there because I knew it would be yeah I think like a cc by sa or something would probably work for everything there um yeah Charo's gpl3 notwithstanding um Diane like I loud and clear I hear what you're saying I'll try to get all these changes made um you know before next Tuesday so we could review it at the meeting I think you know most of this stuff should be straightforward I'd like to change a little bit of the language in the read me and kind of update it to make it more user friendly um and I'd also like to put read me's in the sub directories so that we can help index better what people are seeing there so they're just if people come and look they have an idea what's going on um writing rewriting some of Charo's stuff is going to be like difficult um but you know maybe we can just kind of maybe if we pull out some of the information about like the requirements and whatnot we can put that in there and then leave the instructions as like a rich link back to you know the work that that he has there so we're not really like stepping on his toes yeah so what I what I really like to do is and the same with Craig Robinson is like like putting in a link a link in the template as a link to the video walkthrough I'll link to the original source so that people get cross-reference and we get some flow going back and forth like this isn't to replace a medium blog post or an open ship.com or the even though the sys admin blog post that Bruce shared with us um those things we can cross link grab grab some of it with um as long as we reference them and um yeah and and then whoever that dude was on the sys admin one he better come over and help write up his so there there you go all right yeah I'm gonna I got that I got the additional links so I'll put that I'll make sure those are in there as well okay and people are going to join in about two seconds I'm going to stop recording now


is on. There we go. Cool. So you want to kick it off? Or maybe do you want to do an intro since we might throw this up on YouTube so people can see what we're doing. So I'm also San. I am actually working on the Fedora i3 window manager spin. So we are going to create a Fedora spin that's like that has i3 window manager pre-configured by default. So you can just like modify your configs and get this started with Fedora. So over to Justin. Yeah so my name is Justin also part of the i3 SIG. We're missing a couple other folks who were unable to be here today but we're gonna go through the agenda. I'm a part of the Fedora Council and I do a couple of the things in the Fedora community especially with docs but I'm also a hardcore i3 WM user and fan so that is why I am here and I'm excited to try to get this available as a new spin in the Fedora project. So back over to you. I would like to add just one thing is actually Justin's my mentor for Fedora and the one who introduced me to i3 window manager. So most of the work that I'm doing is thanks to his mentorships and Justin. It's all my pleasure. So I'll go and share our screen with the agenda really quick. Here we go. So you were talking a little bit about the ISO creation before we started the recording. Do you want to pick back up on that? Sure. So our current development cycle is that bi-weekly now we have bi-weekly meetings where we meet on the IRC channel and the other communication channels we have and we discuss what things do we need in this like what packages needs to be implemented, needs to be integrated or what type of configs we would like to add there. So after that what happens is that we have an awesome respin seg who collaborate with us and builds our kickstart files into ISO form into image formats and they upload it on a public location where you can download and test. So when we go to the spins creation process so the technical side will most probably be covered because they have a similar build process. So the next respin build that we'll be having is on 11th. Oh okay the last ISO that was created by the respin seg was around 11th August and it had some issues so we had mostly fixed them and the issues will be mentioned next and for the next respin that will most probably be in a week or two we are gonna have another respin that you can download test and provide feedback and let us know what things you need in that spin and we'll be most probably more than happy to integrate that. Oh you can join us as well. So what was wrong with the ISO image last time? Was this the GTK race condition or something else? So in some bare metal devices that included a think pad of some older model if I'm correct which Edward and some other folks reported that we have this GTK race condition bug like that's not that's not that's somehow related to Fedora but this bug for from my perspective I think this bug needs to be patched on the upstream GTK side things as well because that's not only the case with our i3 ISO but that also occurs in the sugar SOS what's the full form of that? Sugar on a stick? Yeah sugar on a stick spin as well. So we have that issue and to tackle that you can easily use the text installer which has like n-curses type of the terminal based installation or command line based installation and like it's user friendly as well like how you how you how you create your configs for the Linux kernel. So that was one of the issues and for the current status and the issue that we are currently facing is of the default wallpaper for the live ISO we do get that PNG and sim link but we are having a hard time with setting that wallpaper by default on the live side of things but once you install that we have like DM GTK as our display manager so you'll most probably get the wallpaper once installed but with the live side of things we are currently having some issues there so I am currently working on that so we are going to use something like fp or some other x related tool to get it done. Okay cool so it sounds like from from that side of things that we're really sorry are you familiar with what a golden image means in the context of Fedora builds? Pardon me Justin there was some lag in your voice so yeah I was asking do you know what a golden image is in terms of Fedora ISO builds? What a golden image? Yeah do you know what that is? No. So a golden image is in Fedora build speak it just is the image that's like the final image that we're going to publish on our mirrors and we'll get synchronized across the whole network of mirrors and file servers all that good stuff so the gold image from our standpoint would be the ISO that we ship that would be the ISO that we take in the change proposal for Fedora 34 so from that side of things well obviously we're probably still going to be working through the wallpaper stuff and maybe try to figure out a work round for the race condition I don't know how often that happens outside of those two things it seems like seems like we're on good track like I think we could probably start the change proposal now does that sound right to you? Yeah that's that sounds very great to me because once we tackle that race condition because race condition is something that was reported already on Buxilla by a southern gentleman from Riespensteg and I think Edward Lucena from IT Steg was also a contributor while creating that book so I think what's going on on that side of things from the for the golden ISO that we would like to ship for the change proposal I think we'll be pretty close to that because like all of those discussions that we had like these are the packages that's that's going to be involved or these are the packages that we would need to get in like most probably done and we have just some minor fixes and we would like just these minor fixes and then we'll be most probably be good to ship after some testing and collaboration with the Riespensteg for the change proposal any here I think it would be a great idea for now okay cool so I think that's probably something we can we can start I'll have to go fishing for a template maybe I'll start it in an either pad instead of putting it in a wiki just so we can get get something started so let me go to IRC and I'll just write a action for myself go ahead give me a second we did set up a wiki page for it and what we can do is like then we have the template here it's like not that modified yet but we do have I'm going to drop the link here so we just have changed the title actually that was the initial thing to do so we can like here it is okay yeah so we can just use this instead of an either pad for context maybe for anyone that's watching the recording and doesn't know so to get things so we were we want to make the fedora i3 iso an official spin to make it an official fedora spin we have to submit a formal change to the fedora engineering steering committee so that way it'll be discussed by the engineering folks in fedora ben cotton who is the fedora program manager will also get on his radar for the upcoming fedora release and we have to do a couple of things like how to test and about user experience contingency plans all these kinds of things so this is a procedural part that's not really code but in order to make i3 iso an official fedora spin this is a thing we need to do to get it published and get it out there to the rest of the fedora community so there's a little bit of context so in that case i can try to kick start a draft of this one question i had doesn't have to be answered necessarily right now since it's just me and you but um i asked ben cotton if a sig can own a change and he said a sig can there needs to be someone who is a point of contact for the for the change um so i was trying to think if uh so we could put the sig there because technically all of us are on part of this but we need one person to represent the change if there's questions or to relay it back to the i3 sig so my question was um since me and eduard are both already on the council maybe i was thinking either you or maybe defolos if he has time in bandwidth could be the point of contact for the change and i don't think it's going to be a lot of work but it just might mean showing up to a fedora release readiness meeting for fedora 34 um maybe going to a council meeting if there's questions maybe to introduce the iso the fedora i3 spin um it'd be stuff like that so it's not like you know when it comes to the core work it's still a team effort for the spin but we just need someone who's the point of contact you know ben cotton or if uh one of the fesco members has a question uh just a way to get in touch we could even put the email or the mailing list here but we could also it just needs it needs to be a single person that's what i got from ben over that's like a great idea like it would most probably be about the following up work and the collaboration stuff so i would love to be in that uh feel free to add nasa hm cool and if anyone else there's not it's not doesn't like it has to be a single person so say if defolos wants to jump in we can we can add him there too so that'll help me i'll just make sure to note that when i go i'll make a first pass and i'll probably put a i'll send a note to the mailing list once it's uh once there's something ready for review um so we meet every two weeks now right yeah okay so i think i could have a first draft by our next meeting in two weeks which should be october 20th if if i have that right um cool so i can try to get it i'm going to make a note to uh by next meeting on 20 october cool okay um so glad to know that we can start going on that that'll start getting us in gear for fedora 34 oh i have a question do you know what um this criteria is for the spins website oh you're muted uh so i did actually go through all those spin criteria so if you could just open that for me to get a refresher of what it is like it's been quite some time i did go through that i think that lives somewhere around fedora docs actually oh do you mean the actual like the the website nope i am referring to the spin creation docs like i think that lives around fesco oops i did go through that earlier while we were working on that and made sure that we are following all of those spin criteria process so i think i'll just have to find it it's not this is it changes policy uh is there something related to a spin around here so like that would be specific to what the spin criteria looks like i found this wiki page but looks like it's out of date it links to the docs website oh yeah it's most probably this one so i think what from the technical side of things it asks you to like rather than flattening all the kickstart into a into a single kickstart file you have to import the fedora live or the fedora base kickstart into a kickstart and then just have your have the fedora i3 related changes in that so actually these are the dos and don'ts that we are following and we are following all of them so that would be great if you could like drop the link here so i can like go through them again and if there's something that actually conflicts with these so we can fix this for the next meeting i can take that action item i put it in gitsi and an irc ah great thanks jesson so it's just some guidelines that you have to follow for the spin creation process what needs to be done what shouldn't be there there's like everything needs to be inside the fedora apple so there's something that's not packaged yet you have to package that and then you can use that in your kickstart so it's just all yeah i think i think we'll be in good shape for for this yeah because we don't actually have anything from outside everything that we're using is inside fedora's repos so we are most probably good with all of these awesome cool well that then that means this shouldn't be uh shouldn't be that hard to do that um so we have about 15 minutes left i know um this one is some work that eduard is doing on packaging some more stuff and also we talked about the package groups too a while ago of having like a base i3 and then having like an extended i3 um do was there any did we leave off somewhere in that conversation or do you want to add something there uh i would like to add just one thing on this pencil that if it would be really great if you could like add an action item on irc for me to uh just ensure that our spin and kickstart files are compliant with the spin criteria just to know you do because i was muted i just put it all on irc ah great thanks so i'll just like check that and make sure that we are in a good shape from those other things as well so what do we have next uh package groups so would you like to provide some context on what package groups uh what are you planning for and stuff yeah so what i remember from this conversation and maybe you could update me if i have anything wrong um i remember that we we were talking about having two options for i3 one being like a minimal base install and one being an extended i3 kind of package group so you could do dnf install at sign i3 extended and you could get an extended uh packages for for i3 or if you're running another desktop you don't even have to use the spin you could be running ganome and do sudo dnf install at i3 wm and pull in all those things for an i3 desktop um so i know that was something that we were really excited about and i think actually still does have value but um i don't know if that we've actually i don't know if we have someone who's like really owning that task or if someone who is taking responsibility for it um i don't know if there's any i have some thoughts on this that are probably new but i just don't know if there's any other details or info that i'm missing did i cover everything right there so i'd like to just add one thing here and that's you were right about everything uh for for this spin we'll be adding like those i3 extended packages as well so you have like a fully fledged i3 distribution uh for fedora but at the same time you're indeed right that we don't have someone working on uh specifically working on the package group so i'm just like coordinating with those packages and manually adding them one by one in the kick start file once we have the group we can just add the add sign and those packages okay got it i'm kind of thinking that do we have um do we have an issue open for that i'm a little behind and i need to catch up on our oops what am i missing here ah that's why i see if we have an issue for the package group so we have the kick start minimal packages but we don't have one for oh this can probably get closed out i can do an update in this one okay so looks like we might have a little bit of ticket follow-up to do um i can take an action to open an issue for the package groups just so we're tracking it and keeping tabs on it but i think we should focus on getting the spin done getting the change proposal done first because i imagine you know once people actually start using this we'll probably get feedback with people who are like oh how could you not remember this package or oh you know this is actually broken you know whatever the feedback is um we'll probably get some of that so maybe before we do the package group let's just think about getting the getting the spin off the ground and getting that done and then if we get some feedback we can make those changes and then finally publish a package group later either when we're we have less work going on with the spin or if somebody comes along and is like oh my gosh i totally want to do that let me do this right now does that sound like a plan that would be great like for uh you write that for first like once we get that spin out and that change proposal out we can gather that feedback and incorporate that for a package group so that will be a plus one from my side cool well in that case that that was all the agenda for today so it's open floor um anything else around i3 or the sig that we should talk about uh i have a small idea and that's like adding i3 related stuff into fedora quick talks and like having some bits and pieces like how to manage your windows and like what's tiling manager tiling window manager how to manage your layouts and we can like incorporate that in our i3 docs as well but i think quick docs would be a good place to yeah um you know i actually think our docs site so the thing about quick docs since you were on the the mentor the docs mentor call yesterday i know you have a little bit of context but we were talking about the quick docs project and just that it's a lot of content and there's just a lot of like it doesn't really use modules so it's really hard to navigate on the side bar it's not super well organized i actually think our i3 doc site would be normally i'm against like um like sigs or sub projects like owning user focused docs but i think in this sense it actually makes a lot or i think in this case it makes a lot of sense for the i3 sig to have some docs so that way people who are using the spin might jump on board and be like oh hey i want to edit um you know i have an affix for this or i have an improvement to this page or i have a new idea here let's add this um so we could maybe do like add a users module like for the users you know something like that and i think it's a great idea to add some i3 kind of docs i think it would be really helpful if we can make that in a fedora context yeah like we were discussing in the docs mentor call yesterday that what if we have those modules then and like we can create a users module and have all of those user related source pages there where you can like link to i3 user card and like list those stuff down so that would be a great help for someone who's just starting with i3 yes yes cool do you want to open a new issue on the spin tracker which i guess that would be the spin tracker or the docs tracker uh we have a separate repository for docs so it will most probably go there yeah okay so open down the docs repo we can keep track of that one that'll be a good thing i like that idea a lot i think once we get the spin off the ground and the change proposal done i think we can probably shift focus over to that um and hopefully start doing some cool things with user docs to get people excited about using the spin yeah that will be cool so i'll take an action uh can you assign an action item so for me to be accountable actually because i'm just gonna it's just gonna get valid in all those notifications and tasks so yeah uh by the way thank you justin for the awesome work you do with managing the whole i3 sick team regarding project management actions management and managing and being active on the ticket tracker at times and all that stuff so thank you very much for that oh i mean i'm a little late to the game it's really been you and adiward and defolos who's defolos i think he's he's the packageer for i3 right that's he's he owns those packages yeah he's the one who's maintaining the i3 package gotcha well all y'all are doing the hard work i i'm just jumping in after like a month of being like behind on things so i'm happy to help you happy to help out with the change proposal i think that will really start getting some excitement for this because that'll be the big that'll be the big deal that's when things will really start happening so i'm excited i am too and it was really great to have this video chat after some time on isc talking about i3 so i think we have a good amount of action items for the next meeting that we can follow up on and see if we have any roadblocks or challenges if someone would like to get involved like just if you could share your screen with the communication channels so if someone would like to get involved they can see where we live at and most well talk to us about i3 the spin creation if you would like to spin up your own fedora we spin or something related feel free or something related i3 feel free to reach out to us at fedora i3 telegram and mailing list so it would be great to have you there and what i'll do is i'll put links to all those things down in the description if you're watching the video so can find them there too all right well we can go and wrap up there thanks for your time this year and have a good rest of your evening it's night here so almost as if you're sleeping in an hour now have a good evening too i think see you next evening bye see you soon see you soon bye


Hello, everyone. I'm Sanjay Gupta. I welcome you on Sanjay Gupta Tech School in this video. I'm going to demonstrate a scenario based on trigger. Let's understand the trigger scenario first. So scenario says when an account record is created, then create a related opportunity as well. So upon creation of account record, there should be an opportunity record created automatically with the help of trigger. So we need to create trigger on account because we need to create account record from the UI. Then we need to create trigger handle class where we will be implementing the business logic. And then I will show you how we can implement the test class so that code can be covered. So jumping to developer console. Now I'm going to open account trigger. So for previous demonstrations, I already implemented account trigger. So I'm opening that here you can see three methods are already called. So I need to call one more method that will be responsible for creating opportunities. And here two events are mentioned before event and before insert and after insert. So when account is created and you need to create related opportunity. So in that case, you will be using account ID so that you can link that newly created opportunity with that account. So IDs on creation of account will be available in case of after insert only. So what I can do, I can just copy and paste it here and I'm modifying it to create related opportunity. Now I'm going to open its trigger handler. So here I'm going to implement the method. So I'm going to implement it here in the middle. So this way the block is created here. I'm just saving it and moving to trigger and I'm going to save it. So it is also saved and we are right now working on the insert part. So that is why I just trigger dot news pass because whenever you create any record or bulk record. So all those records will be stored in this trigger dot new. Now here I need to implement the logic. So first of all, I'm going to implement list of opportunity. So naming it as OPP list new list of opportunity. So there can be chances like you are creating bulk records bulk account records. So for each account record, you will be creating one opportunity. So here bulk opportunities will be created. So we just need to add those opportunities to a list and then list will be inserted in the database. So now I'm going to iterate on account list. So from trigger we are passing trigger dot new. So this trigger dot new is a list which will be storing all the newly created accounts and those account records will be passed into this ACC list here. So I'm iterating over this list. So as I hope, you know, like apex is case insensitive language. So we can write names and uppercase and lowercase that doesn't matter, but still try to follow as per best practice to follow the case sensitive nature. Right. So I'm just modifying these. Now I iterated on ACC list. So inside this, I just need to create opportunity instance. So this new opportunity instance is created. Now we need to fill the value. So first we need to set the opportunity name. So what I'm doing, like if you create any account, so you provide account name because it is required. So whatever account name is, I will be creating the opportunity with the same name. So I'm just passing account name here. Then we need to set the stage. So stage name by default I'm setting as prospecting. And third required field for opportunity creation is closed date. Right. So if you don't know, like how to check whether particular fields are required or not. So you can go and try to create new records. So I'm just trying to create new opportunity and clicking on save. So here you can see opportunity name, close date and stays. These three are required fields. So that is why I'm just populating values into them. For close date. I'm just populating system dot today. Now, after this, I just need to link the newly created opportunity with account as well. So I need to write OPP dot account ID equals to ACC dot ID. Right. So this ACC list is having all the account reports. And here we are calling this method in after insert context. So after insert context will be having IDs of the newly inserted account records and those IDs we can assign into this OPP dot account ID. Now here. In this opportunity list, we need to add newly created opportunity. So this way this loop will iterate on ACC list and for all the account reports, one opportunity will be created and that will be added into OPP list. Now, after this, what you can do. So for safe side, just apply a null check on OPP list. If it is not empty, then you can write insert OPP list. So your opportunity list will be inserted. And like whenever you will be creating any account record. So one opportunity will be there related to that account. Okay. Now if I go here and create any account record and click on save. So in the related list, you can see here one opportunity is created. Here one more opportunity is there. It is because of any other automation that is implemented in my own. But the trigger which we implemented here, we are using this name and we are using stays and dates. So all these information are populated. Now after this implementation, I'm going to show you how we can implement the test class for this method coverage. So I already have test class implemented. So this is account trigger handler test. It is for this trigger handler. So I need to cover this method now. So for that, I'm going to implement a method. These methods I implemented for previous demonstrations. So yeah. So here I'm going to write test method. So public static void create related OPP test. Okay. So whenever you implement any test class, so it should be annotated with at the rate test and the methods also should be annotated with at the rate test test. Now here we need to create the data. So here you can see I have already created data for testing context. So I'm just going to copy this so that I can reuse this. So here I created account list and I rated five times a loop and five accounts are created. Now after that, what I can do, I can just use this block of code. So this block of code is basically inserting account list and I'm using test dot start test and stop test so that we can ensure like fresh governor limits will be available for this method. So if your test class is having more than one test methods, so you can just enclose the DMS into these two statements so that you can have fresh governor limits for each method. Now after this, I'm just copying this piece and I'm pasting it here. So what I need to do, I need to convert it into opportunity. Then I'm modifying it to opportunity list, select ID from opportunity where account ID equals to ACC list of zero dot ID. So what I'm going to do, I'm just wearing opportunity record, which is related to a particular account. So if particular account is having one related opportunity so that will be available in this OPP list. Now here we need to use this OPP list. So if OPP list is not null, then this assert will pass. If it is null, then it will fail and it will display the message. Opportunity is not created. So this way you can implement your test method so that you can cover your trigger handler business logic. Now I'm going to run this test so that I can show you.  So here you can see test is passed and total four methods are available here. So this is first method, then second method, this one. Then we have third method and we have fourth method. So all four methods are passed, right? Now if you want to see the code coverage so you can come to your trigger handler and you can click here and click on all tests. So here you can see all the lines are covered, right? Because we executed the complete test class so all the methods are covered because we have test methods for all the methods. So this way, if you want to implement your test method for the code that you implemented to create a related opportunity on account, so I hope you understood whatever I demonstrated in this video. So follow these videos so that you can learn different, different trigger scenarios and how to implement their test methods. Thank you.


Hi everyone, happy Saturday. I'm Joe for jaspyscasebreaks.com coming at you with 2021 hip parade baseball limited edition series 24 It's a dual case break 20 boxes Some nice stuff here big. Thanks to everybody here for making this happen and all 30 baseball teams are in Let's roll it. Let's randomize it four and a four eight the hard way one two three four five six seven and eight After eight we've got Sean Oh down to Robert F four and four part eight for the teams one two three four five six seven and Eighth and final time After eight we've got the San Diego Padre San Diego and the Chicago White Sox on the bottom.  Let's sort by team by column B And here are the cases right here. So we've got limited edition series 24 right here and another case up here They're all hand number. This one's three out of ten. This one's four out of ten There you go. Now, I'm gonna pause the video allow for a little bit of trading time and when we come back We'll see if there's any trades And then we'll have the break stick around. We'll be right back and trade at your own risk All right, welcome back folks a little bit of trade chatter, but in the end no deals were done on a Saturday Thanks everybody for getting in So that list remains the same Here's the official list hot off the presses The little MLB network on in the background. What game are we on right here Phillies mess What Jacob DeGrom gave up two runs Please rub two one. I don't know if that second one was DeGrom's run, but all right, here we go Good luck everybody. Oh, Toronto put 12 runs on the Orioles Scratch a run back in the seven. That's crazy. All right first one out of the gate is is Logan Gilbert The big pitching prospect for the Mariners Joel.  I know he made his debut But I don't know if that was a That was a one-off sort of situation or if they're if he's just in the rotation now Okay, he has been making season seven starts 34 innings 36 strikeouts a 4-5 ERA All right, I think you went five five point two innings seven strikeouts. All right, so getting his career going Joel Hang on to that one these boxes on top. You see that in the top camera over there. All right. Ooh got a gold frame here He goes this way it's landscape mode It's Steve Carlton Two out of 20 Steve Carlton. That's pretty awesome Phillies that'll be for Jason Kersh Next we have Fernando Tetease, Jr 93 out of 99 This is what's yeah, it's from this is from tribute baseball. That looks really cool iconic perspectives autograph From 2020 tribute baseball, it's a cool look that goes to Sean and the Padres by another gold frame Next gold frame 18 out of 20 Juan Martial And that's for my rivals the Giants Joel with San Francisco Next one. I've been Rodriguez Pudge from 2019 Penini Donner's baseball Next autograph for the Rangers Try to trade couldn't trade mojo get all good All right, we have here we goes this way. Oh This way Nick Madrigal bow and first autograph It's having a really solid season before that hamstring issue knocked him out of the season, but Former fourth overall pick it's one to hang on to maybe even get graded white socks Robert Flores We have nice Adley Rushman six out of ten collegiate national team gold ink autograph Cool looking patch right here stars and stripes Baltimore Will be Rob big prospect for the Orioles Yeah, in situations like this folks where they're not in their pro uniform I won't we'll go by that. We'll go by this checklist. I guess if there was no checklist then we'd go by or no checklist rules obviously, but Checklist will surely say Orioles. It's only team's been on Proteins right a thicker card here and it's it's Walker Bueller 55 out of 150 Nice autograph. I like the bluish parallel right here color match with the team 2019 tribute baseball Daniel has my Dodgers landscape mode Three color patch auto Trevor Rogers Nice rookie patch out of out of inception baseball Miami Jason Trevor Rogers having a great season and the 10 the final box and another 10 coming up flawless all-stars patch auto Corey Kluber Cleveland Six out of ten Cleveland this is for you Sean O'Leary with the tribe All right, that was the first ten Let's see what's in the next here next ten. Good luck everybody. All right next one is you're done Alvarez Box open second this first case was pretty solid for for limited edition now if this was like sapphire Or platinum or VIP Yeah, we wouldn't know but for this level of hit parade Those are some really solid hits Next one is 35 out of 50 Vlad Guerrero, Jr Also hitting the ball a ton from 2021 tops tribute baseball blue jays Jason next box This way Yeah, Jose of brave from NT baseball 30 out of 99 treasure signature materials from 2017 NT Robert with the lights off Great autograph This guy's pretty good six out of ten Mariano Rivera Sean with the Yankees Nice some excellent penmanship from Moe here. He would definitely be Probably the keynote speaker at Jaspie's autograph camp. We have here Heston Kirkstad Horses have a lot of second overall pick My great prospects coming up the ranks at the rushman Heston Kirkstad so on and so forth Robert with the Orioles Be worth rating that Kirk sod as well We have here Auto fax signatures Justin Verlander Tigers edition 311 out of 700. That's from an old upper deck set from 2006 Daniel with the Detroit Tigers Nice Cubs prospect Ed Howard 86 out of 100 Great atomic refractor Cubbies Steve Wright with the Cubs tried to trade couldn't trade mojo. All right a few more to go The card stock here from triple threads five out of nine Corey Kluber Helping himself triple relic and autograph he can defensive acumen Can hold runners There you go. He is helping himself Cleveland. This is for you Sean oh with another Corey Kluber two more to go Spectrum spectra baseball Jersey and auto Joe Adele Good matter of time before he gets called up. He's Hitting it pretty well in the minors 48 out of 99 big angels prospect going to Dario The Los Angeles, California, Anaheim Angels of Orange County in Orange County of California of Anaheim All right and the final one. Good luck everybody This was 2021 hip-rate baseball limited edition series 24 dual case break Random teams the last one's gonna be Nice playoff ticket autograph 12 out of 15 nice low number here to Raphael Devers For a really good Red Sox team right now Robert Flores with the Boston Red Sox They get some starting pitching on that squad by the deadline Could be spicy spicy finish the ale east I'm Joe for Jasper jasperates calm. Thanks for getting into this one I'll see you next time for the next break. Bye. Bye


We need to raise the ROI, address those KPQs, and meet our KPIs across all BUs B2B and B2C. It's the only way to keep the BOD happy without jeopardizing the AOR. Think outside the box, folks. Think paradigm shift. Alright then, are we all on the same page? Isachronomitis preventing your team from working toward the same goals? Getting and keeping great people is all about communication. Join us to find out how CMOs find and foster the top talent in the industry.


The Kastinah Police Command has confirmed the fine of 10 million Naira imposed on the communities by terrorists who have accused them of killing a bandit. The Command said the warhead of the area, Surajo Madawaki, has been arrested for alleged conspiracy in the matter. According to him, the Command had received a distressed call on October 19 that a farmer was attacked by a suspected bandit while working on his farmland. The farmer, overpowered his assailant, disarmed him, and killed the bandit. He said after killing the bandit, he took the recovered AK-47 rifle to the house of his warhead, who allegedly reported the matter to a suspected notorious terrorist commander and handed over the recovered AK-47 rifle to him. The Kastinah Police Command has confirmed the fine of 10 million Naira imposed on the community by terrorists who have accused them of killing a bandit while working on their farmland.


Here's a fun little exercise to make the best of your 2023. So I want you to look back and reflect on 2022 and list out all of the positive changes, accomplishments, anything that you can think of, whether it's internally or externally in your life and write them down. Then I want you to have thanks and gratitude for those things. Next, I want you to list out if you're looking at yourself this time next year and we're going into 2024, what are the internal and external accomplishments you would like to achieve? What are those changes you'd like to see within yourself? What are those changes that you'd like to see in your 3D reality and write those down? And then I want you to bridge the gap and use the gratitude and the love and the happiness you have from your accomplishments this year in 2022. And I want you to express that same gratitude for the things that you've already accomplished in 2023. Like and subscribe for more practical ways on how to improve your life.


Today marks a new chapter, a new phase for the ministry as we introduce St. Lucia to our new mark, our new brand, which will make us stand out at formal events and gatherings. The question has been asked, why does the ministry want a separate logo? Not caught off arms ministries using it. It is our desire that this new logo will invigorate and re-energize our young people and the sports fraternity in accepting and embracing their identity. As we get started with this ceremony, I would like to express my sincere appreciation to all of you who generously helped us to make this event come together to become a success. Today is a new day, a day when we have the Ministry of Youth Development and Sports adopt a new face, a new identity. Mrs. Maki just told you that we are customary of using the coat of arms and I suppose this might be the last time that you will be seeing this on ministries, t-shirts and so on, or even if we have to make mass for the ministry. So once we continue to use coat of arms for all government agencies, we felt it necessary to bring the Ministry of Youth Development and Sports against this backdrop. We throw out a challenge to our young people and they responded well and the tale is behind us. We received more than 70 logos and then the prize winners were chosen. We are happy that the logo was brought to cabinet and they embraced it with open arms. Somebody even commented that it is similar to the artwork on the roundabout by government building. So after it's unveiling today, the logo will appear on all our literature, our sheets, our caps, you name it, in all print and digital media including the website, all of our social media platforms and all functions associated with this ministry. It is certainly a brand new day for us at this ministry and we are happy to share it with you. This logo now gives us instant recognition as it allows us to stand out from the crowd indeed. We have evolved. Our ministry and I'm not going to, I'll not be able to, it might take me the whole day to talk about our accomplishments here, but you know we sought to do a lot of things for our young people in St. Lucia and I mean I can include facilitated youth participation in the development process and we can go on and on and on to provide inappropriate support services to all athletes, sports federations and so on. So you might be able to fill in the blanks as we go along. So I'm thrilled that the logo now becomes us. I ask that you use it responsibly and when you do get a chance wear it with pride just like we wear this shirt with the coat of arms. Ladies and gentlemen, I thank you. Let us take this opportunity to impress upon you to continue to observe the necessary protocols as we continue our daily lives to coexist with COVID. God has been good to us. May he continue blessing us. A small team comprising of Mrs. Isabel Alexander Markey, Nixon Barry, Sarah Lee Williams, Bernal Centros and myself was charged with the responsibility of leading the selection of a design that would appear crisp, smart, youth-friendly and connected. The selected logo focuses heavily on portraying togetherness and patriotism as is highlighted in the use of our national colors, blue, yellow, black and white. In the logo, the trophy represents sports and women. The blue circular shape is not arbitrary, but instead serves the purpose of depicting the unity of our youth and showing the importance of all of us working together to ensure the improvement and continued development of the youth of our country. The youth on the logo are shown holding a Saint Lucian flag, just as our young people continue to fly the flag of Saint Lucia as they represent our nation with pride and dignity. We do hope that this new look, which will be unveiled shortly, that you will like, appreciate and wear with pride, as minister said earlier. As we continue to better serve our young people, we ask that you continue to look out for the launch of our brand new website in the coming days and continue to follow us on Twitter, Instagram and our other social media platforms. I do hope that you like the logo as much as we do.


Hey, welcome to another Microsoft soundbites. I'm Gez. I'm Stratis. And today we're going to look at Python virtual environments, what they are, why you should care about them, and how we use them in Microsoft. So let's jump straight into it. What are Python virtual environments? That's a good question. I think I would start with a problem statement more than a definition. So why don't I just run Python straight on my system? And the answer to that is oftentimes you have a pollution of projects. If you've got a lot of Python projects on your system, maybe you've done a pip install, and you've got various competing packages, or sometimes there is a need for different versions of the same package for various reasons. And so this is a problem, because if you're just installing things, you could accidentally overwrite a critical Python library to your operating system, or you could accidentally mess up a project that you were working on previously by updating a package that you weren't planning to. So the solution to that is a Python virtual environment, also known as VMV. Yes, they are often referred to as just VE and VE, which I say VEMV for some reason, but VEOMV, VEMV depends, you know, if you live in French, Canadian or not. They're a virtual environment that provides an isolated environment for your Python project. And so particularly if you're working on multiple different projects, then they give you an isolated environment for your project. And so as you said, you can have different versions of the same package installed in different environments. And I think the other really useful thing, at least for me, because I set up and rip down projects all the time, is that because they're contained, once I'm finished with the project, I delete that project directory from my system. And all of those Python dependencies that it's installed, they've taken, you know, they're deleted as well. All right. So here we are in the command line. And we're just going to take a quick look at what lives inside of Mycroft Core. So I'm currently in my Mycroft Core directory. And when you create a virtual environment, it creates a directory called .vomv. And so it's a hidden directory. And inside of this directory is everything that the system needs to create your Python environment for this project. So if I go inside, take a look inside of bin, you can see that there's a bunch of stuff already here, including PIP. So whenever I need to do a PIP install, or if I do for this project, there are there's a bunch of binaries in here. So as we were saying, we can see that there's the MSN binary that's inside of the bin directory. But it's not in my path yet. And that's because when you want to take advantage of the virtual environment, you have to do what's called activating it. Now in this case, there is a shell script that Mycroft provides called vomv activate. In Bash, you can either type source vomv, or you can also type . and then vomv. Either of these will work.  So now I have MSM and I can access those binaries because it's now edited my path. And these things are now available to me. That is Python virtual environments. And we haven't gone into a lot of detail, you know, there's plenty of resources online, if you want to dig into it more. We mostly wanted to explain really quickly what they are, because a lot of Mycroft's commands, they are interacting with the Mycroft virtual environment and they help to remove the need for you to interact with it directly. But it's still useful to know that it's there. Another really useful reason for virtual environments is that you can actually use a different Python interpreter for each project. So, you know, if one project is requiring Python 3.5 and another one requires Python 3.7, depending on which version of Python you use to set up your virtual environment, that is what's going to be used for everything within that virtual environment. Now, I think that about covers it. The goal of this wasn't to give you a tutorial on how to set up a virtual like we talked about. Really, it's just the idea of getting you used to how Mycroft functions and giving you some tools on helping you troubleshoot if you need to. In the next videos, we're going to look at some of the Mycroft tools that use virtual environments. So, we'll look at Mycroft PIP, Mycroft MSM, and yeah, they'll help you to do a lot more with your skills and get deeper into development. Sounds good. We'll look forward to kicking that off next time. Cool. Thanks, all.