what's up guys you guys hear me all right so i'm testing out something new today going back on streamlapse because i kind of missed it it was pretty good um as opposed to we stream so let's check out some of the earnings we got coming out today so stock market bubble today ups ran up like crazy all day um some of the fertilizers and steel stuff are going up netflix was all pretty good today xo m as well a lot of bullish uh tickers on the day with some some getting pretty beat up again um etsy can't catch a break for the life of them we got some pretty big earnings today we have uh amv we've got alphabet um electronic arts micro strategy so some of them are already coming out so let's check them out here oh my screen just got messed up there you go all right so let's check out some of the earnings that's going on today um then we'll look at some charts and discuss some other stuff amd didn't get a chance to close today really excited for amd i'm looking to really see them beat let's see how micro strategy perform so micro strategy q4 earnings per share is negative a43 says they may not compare it to dollar 49 estimate sales is 134 mil as opposed to 133 mil the company is says this is down 18 dollars no 100 sure google just just flopped some of the guy says hmm for some reason i can't get the checkbox to pop up here where is the chat box oh guys try to type in in the chat box again i want to see if that pops up all right so we play some earnings today let's see gillia science also reported as well q4 earnings per share 69 cents may not compare to dollar 58 sales is 7.2 billion as opposed to 6.64 uh down a little bit tiny bit after hours uh sales is pretty good but eps wasn't doing that well electronic arts also reported as well wow got beat up pretty hard here what's the earnings they say maybe up 22 to 20 percent year every year um compared to a year ago they actually down a lot so this might be interesting for electronic arts we'll take a look at that later on i want to focus on google and starbucks and then amd as that comes out oh wow google did it again dude holy smokes how how how you keep doing this google so google's earnings per shares 30 30 and 69 cents beat estimate of 2748 sales was 75.33 billion as opposed to 72.13 billion they said this is a 37 percent increase in earnings per share from the same period last year and 32 percent increase in sales compared to the same year period last year um but at the same time last year the company was trading around two thousand dollars so two thousand dollars times one point was that 1.35 ish 2700 um yeah 1.32 ish 2640 so google's actually um the price of the stock is trading at much higher and um then you know what um what the what they're making in terms of revenue whoa whoa whoa oh snap there we go boys there we go we just got a stock split for this quarter i knew somebody was gonna do it but god damn why why did it have to be google oh forget it man this is gone it's gone it's over 221 can you imagine that 221 bro holy smokes 2900 divided by 20 that's 145 dollars oh my gosh hold up i gotta go pick some up this is too stupid not to pick it up i mean like i can't imagine i can't imagine a stock doing a split let alone be freaking google at this point man half amazon doesn't follow with a stock split i will i will never trade that company ever again man forget it oh man the only i swear to god the only stock that i don't expect to split goals and splits what a scam what a freaking scam what a freaking scam yo 2945 what a scam i don't i i'm not even gonna get filled i can't even chase it i put an order in for 2945 and it hits like 2960 the next second come on give me a break give me a break man let me get in please please bro it's taking me so long just like it's taking me so long it's just a log into the god damn account right now gotta put in my security code two factor authentication and everything come on let me let me catch a break oh my god bro i can't even catch this right now i keep trying to chase the order every time i'm chasing the order it keep going i put 2960 it goes to 2967 i can't freaking catch the order it's freaking annoying man god damn man i forget it forget it man i'm not even gonna bother man i'm not even gonna bother forget it i'm just gonna slam tqqq how much buying power do i even have anymore sorry guys the formal is real here no i'll probably wait for tomorrow we're probably having another opportunity honestly at this point like it's already run so much it's already ran so much i don't even like i don't even want to chase it because i'm just gonna wait till tomorrow and this setup spreads for it because it's it's already too damn expensive it's a great it's a great split 20 to 1 i mean this is the dream right um for a 20 to 1 split and it usually end up running a lot when they do more than uh more than a five to one but damn 20 to one is like the dream right now but i i can't catch it i can't catch it just keep it kept running so it's pretty weird it's unreal though for sure let's see what starbucks did aw starbucks scam oh no i was uh i was just busy trying to buy the dip before there's so much things going on i was because we just got a big stock split from um oh my gosh we're going to the moon bro holy smokes forget it like the um things that things are gonna fly at this point because we just had a crazy earnings um what's up blue collar thanks for following so we just had a crazy earnings from google right and it was no actually google had a pretty mediocre and and crappy earnings um matter of fact but they did a 20 to 1 stock split so this is pretty big you know that 20 to 1 stock split approval and usually when we get a big split like that it's it's huge just kind of run the market up um and then you know amd just came out with earnings and amd just had another phenomenal earnings so amd you know q4 eps is 92 cents as well as the 76 cents sales is 4.83 as opposed to 4.52 this is a 76 increase compared to the same period last year right and 48 increase in sales compared to the same period last year so i was pricing them around 60 increase but 45 percent is like not as great um but but you know meh um but let's see what the guidance says honestly so the guidance is where they're really killing it they um they're expecting a phenomenal 2022 year look at this guidance here this is like this is like big big guidance this is like i'm gonna smack it really good um q2s like 4 year 22 sales is 21.5 billion as opposed to 19.27 right that's two billion dollars over the the guidance of estimate like they said you're gonna make so much money we're gonna make two billion dollars over what we think the estimate is or what everybody else think the estimate is so that's huge there and then on top of that the next q1 they they said they're not slowing down you know this quarter they pulled in 4.8 next quarter they're gonna pull them 4.9 to 5.1 as opposed to 4.3 so people were expecting them to have a slower quarter but they're like nah we're not slowing down we're gonna kill it so it just it's just getting stronger and stronger you know um i don't know what to say this is probably one of the most bullish earning days ever Jesus man but you know the annoying thing is man i i actually set up a lot of stocks to to play for splits right um i have amazon set up looking for a split i have like i have i have Shopify set up looking for a split i have chipotle set up looking for a split the only stock i didn't think was going to split was google because i thought it would be too damn complicated for them to split i mean hell i even got netflix set up for split so i set up all these stocks for splits thinking that if they do a split we're gonna see a 20% run and and all these like june and july contracts that i set up would benefit dramatically from it but the only one that i didn't do that i didn't do it for was google and that ended up being the one that split it's kind of annoying man jesus i hope amazon follows through because oh can you imagine if amazon did a 20 to 1 split can you imagine that like i mean just look at amazon right 20 to 1 split 300 stock i mean hell 30 to 1 split can you imagine a 30 to 1 split like if they divide that stock by 30 it'll be 100 dollars who would not be buying amazon 100 dollars man jesus i didn't do tesla because um tesla had already reported earnings they already split i didn't think they were gonna split this quarter i thought maybe there was split next quarter if anything i figured it was too early for them to do a split right now but damn amy is doing good amy is heading back heading our mark really well um i mean look we had the we had the 120 to 125 this is the exact area i'm expecting them to hit you know expecting to burst 125 um and it's it's setting the area right now it's beautiful because it honestly it sold it sold off so much it's just like why did it even sell off this much you know we all know how bullish we all knew how bullish tsm's earning was and i said that tsm earnings you know was gonna be in it don't buy tqqq because google is not in the holdings what do you mean we talking about google is in here t google is in the in the in the tech index in qqq i mean it's not the biggest but it's in there but you know obviously this whole thing is probably going to carry the whole market up market was waiting for a reverse opportunity you know the market was waiting for a nice reversal opportunity something like this could carry the potentially carry the market up a lot oh my bad we have some people on the youtube side that and this that as well um darn toad in darn toad inside join the discord about 10 others enjoy about four days oh if you want to get your trial period extended um feel free to message out our message out to our support team um i'm sure they'll be able to help you out with that guys correct on revenge trading right damn gotta stop with the revenge trading vwop trader all right let's take a look at paypal let's see what's up with that amd is still running man holy smokes yo this is the best earnings ever but terribly happy isn't that x y is that x y man x y is here with us on this amd earnings big amd fanboy right here oh man nasty mate you closed out your spy long i feel you bro i mean i was expecting market to pull back a little bit as well you know i didn't think market was gonna run like crazy but it just it just it just carry i think it's just gonna carry everything oh my god jesus look at paypal what happened here let's look at this paypal earnings man paypal earnings per share one dollar and 11 as opposed to 112 this estimate but it was a 2 increase compared to the same period last year dude last year paypal was trading at 238 dollars right now it's 155 what the hell sales is 6.9 billion as opposed to 6.8 paypal sees four year 22 sales excluding ebay to go up 19 to 21 percent year over year four year earnings per share is going to be around 460 to 475 which is still going to be pretty in line with what they're going oh geez man they barely miss and they got punished so hard where is the paypal earnings let me see uh paypal didn't we don't have the paypal sec thing yet oh wait i'll wait to find out that paypal report um that's going to be interesting to dig a little bit into that because it's kind of blew my mind how much they dropped and that's also one of the reason i didn't want to play paypal for the earnings challenge account i'll show you why you can see on the technical side um that it was kind of kind of scary so if you look at the technical side right we have this resistance um we have this resistance right here so we have this resistance in the 176th area and that's exactly where you hit today right um and then if you dig it into further you'll see that it's also been struggling at this moving average also as well and that happened to be the same moving average it touched today so there was two things that was like same rejection um but obviously earnings it could be tricky sometimes earning can just gap over it too as well so since it was at such a like a wear area i wasn't sure because if it gap over you know it could gap over to potentially 188 or if it's really gap harder it could potentially gap over to the 200 plus area um which i thought it would it could have potentially gone but i didn't want to play it because it was just too too weird right now it's just like on this whole downward slope so the ideal area to really come into paypal i don't know if they'll ever get here honestly i i mean at this point the way that's going this death spiral that's going right now it could um but paypal kind of have the same setup as roku if you guys remember um roku has a double top setup like it did over here so this is the major double top setup which is pretty bearish right um a major double top bad pattern and if it if it could come to this 122 area that would be huge buying opportunity because that's the same price it is at february 2020 so that's that's the area i've been waiting for um i think i think it's gonna be like it's gonna be like netflix it's going to become a a um interesting buying opportunity very soon probably good good point to take some leaps on it midday tomorrow depending on how the analysts on wall shrew report to like to to the earnings but let's go back to um a and d that i miss anything else let me see a question that you guys have cg2ks how does this affect the split for abc oh how does um i i think that i think when um when google splits they're gonna they're gonna change they're probably gonna split both if they don't split both um i can see them just keeping the other one as well because even though that they're trading two different um symbols it doesn't really affect that i guess at this point because they're they're really just they're not really diluting or anything it's still gonna be um the same amount of percentage but it's just different numbers of shares areas will other stocks fall tomorrow if people pull money out to put into google tomorrow i'm not sure how many people are gonna put money into google tomorrow because um you know google's gonna be at a point where they're so like they're so like expensive that's going to be hard for people to put money into i think most people will probably just end up buying qqq which will essentially drive the market up itself or they'll buy into spy that will essentially drive the market up itself what about gm people could be yeah we could see a little bit profit taking tomorrow morning um and then another huge run up let's check out gm got you guys oh gm had a pretty good earnings um in terms of eps so q4 earnings per share is dollar 35 as opposed to dollar 19 sales is 33.58 billion as opposed to 34 this is 46 percent decrease compared to the earnings of 252 um last last year um sales is 10 percent decrease compared to last year actually not a great earnings revenue this year compared to last year small change for four million dollars um but margin is actually a lot better though net income compared to this year to last year's or 2021 compared to 2020 so you can see the margin increased a little bit over there so they said four year net income between 9.4 to 10.8 what was it this year um this year was 10 so it's going to be pretty in line with this year and i've seen much growth nothing really special on the gm earnings it's trading around the same price it was last year the two year basis it's ran up almost 50% nothing really crazy there copper magic said had butterflies on amd and google oh man what kind of butterfly did you have on them i hope i hope you you like priced in the number correctly man otherwise it's gonna it's gonna be bad erie says i was thinking about selling my google shares right now it's a profit and go back in when the price dips yo that's kind of risky diki it's already it oh it actually did have a dip i wonder if my order got fail then my order can fail broken wing on the bullish side why didn't you just do a calendar um like a diagonal calendar instead isn't that pretty like similar to the broken wing but you're just doing two legs instead of three legs because because if you do three legs um you're exposing yourself to more danger right but if you're doing two legs um there's less danger because sometimes even the brokerage themselves some of the people working there they don't understand it that well and if you're doing like multiple legs they might you know you might get in trouble oh i got phil i got phil at 2945 actually we'll see yeah a lot of his gap and go like uh like sean says solid port from google personally not a fan of the split but i guess it's good for people that wants in we looked at i looked at xom this morning um popper what's going on let's take a look so xom this morning we ported you know uh earnings per share q4 was 2008 cents the dollar 89 estimate they said that was pretty bullish and then um surprise this is not running and then um q4 sales was 84.97 billion as opposed to 91.2 so they missed that um even though they missed that they said that was an 82 increase compared to the same period last year i mean last year was an easy year to beat so you know reasonable to beat that but what was really bullish about xom was the fact that um they they talked about they they talked about this 10 billion dollar share we purchased we purchased program and i think that's what really drove it up today you know them like them like creating their own demand for that that's usually pretty bullish overall for wall street um but they also said you know they had a record quarter of generating cashflow 48 billion the highest level since 2012 more than covering capital investments that reduction in dividend as well we do structural costs by additional 1.9 total savings in nearly five billion compared to 2019 and they also pay down a lot of debt so they're having a great quarter i mean as most oil companies are because the price of the oil just gone up so much right during this these last few quarters so it's easier for them to make money but i think i think it's also gotten a little bit too crazy because they're also pricing this um they're also pricing the next four to five years to really continue you know going in this trajectory but if if interest rate a end up taking control of inflation then you know trajectory of the crude oil price going up it's gonna change real quick but that's just that's just my thought though on the economic view of things but who knows hit me up blue collar oh um blue collar just just reach out to young bo in the chat room or and and let him know your screen name and stuff and they'll help you out why is xof falling i think xof might be having some pay pound there as well it's been a pretty good had a nice double bottom it's is is xof falling though felt a little bit probably probably due to having a little bit pay pal and uh in that all right let me check out the amd earnings that way so i was going back to go go go go go go go amd go to the moon oh my gosh wait hold up isn't video up after hours as well yes go go go go go go go go everything's going up man holy smokes it's a good day it is amd's guidance for next quarter was insane bro everything everything is about to come into play yes the 150 call at this point might come into play like it might just get that crazy tomorrow that the 150 call might just go crazy i don't know but it just may at this point things are so nuts okay so revenue so q4 2021 as opposed to q4 2020 right up 49 percent quarter over quarter is actually slowing down a little bit at only 12 percent of course profit is still doing pretty good profit is up 67 percent which is what we saw in the eps earnings per share quarter over quarter is still up 16 percent net income year over year this is down a little bit down 45 percent so that's the only bad number there um quarter over quarter is still doing pretty good could be probably from expense yeah it's from uh spending a lot of money i think amazon reports tomorrow terribly happy x y is like 150 call just woke up we're i almost got too crazy today man so i took um i took like i took nvidia calls right for the earnings for february 18 to like the next week after that i think 25th and then i picked up some tsm um calls as well from 130 to 135 let me see if tsm is up actually so oh my gosh spy is up so heavy right now jesus so tsm is up to um double dollar not as much as um nvidia and stuff but i got so bullish that i i had the amd i had the nvidia i had the tsm and i was like yo if amd kill it like they should things are going to go things are going to go to the moon the only thing i regret was not playing more of it in a challenge account should have done at least two man jesus so they said lisa lu says lisa su says 2021 was an outstanding year for amd record annual revenue and profitability um each of our business is performing extremely well with data center revenue doubling year over year driven by growing adoption of amd's epyc processor they expect another year of significant growth in 2022 um as they ramped up current portfolio and launch our next generation of pc gamian data center products ah you know that amd needs to do an expo i might be crazy to say this but god dang if amd can do a split right now oh my god if they say if they were to say split in this report anywhere i'm gonna jump off my chair it would be the craziest thing ever can you guys imagine that i think amazon reports tomorrow thursday wait is it already monday nah sunday can you guys imagine that man that's that would be so crazy oh amd announced that we receive approval um from samr of the of the republic of china for the acquisition of xo and x so that's pretty bullish as well um that's also another interesting play there i mean yo amd used to be a two dollar stock i mean i can see them do a split honestly i don't see why not i mean we've seen other stocks at like less than 100 dollars they were split before i mean imagine amd doing a four to one split yo everybody in their mother is going to be having amd in their portfolio 25 a share hell yeah or even if they do five to one hell yeah it's a good deal i mean or even a two to one man i'd be happy they'd be close to intel's price i don't think amd is going to do a stock buyback though i don't think they have the cash for that i could be wrong let me see they do have the cash for that they are pretty cash cash heavy right now they could do a stock buyback you're right did you guys know the history of how amd overtook intel oh here's the graphic i was looking for this whole time yeah i think google is going to be around 150 hundred dollars 150 ish it's going to be pretty sexy just take the current price divided by 20 yo cg2k that's a math smart bro you bought s o xl calls jesus now the story of how amd overtook intel um i'll tell you so it was actually really funny because intel was so good right intel was so freaking like efficient and powerful that it literally became a monopoly it was so good that it literally got to the point where it had like 95 percent of the market share and it became a monopoly right and and like regardless of what amd did they just kept flopping like every time they came over something they couldn't like they would just keep flopping back to back so eventually at one point they had um they had an antitrust lawsuit and they they sue intel for being a monopoly right and and keep in mind amd is like cash trapped it's like poor as hell it's like about to die right so they end up suing intel like for being a monopoly and they won the lawsuit they got so much money from intel um you know because they like the US government agreed that intel wasn't monopoly at that point so they ended up getting so much money um and then intel couldn't do marketing anymore so because of all that between them getting so much money and intel couldn't do the marketing anymore amd was actually able to come back from it thanks to intel like they literally got an investment from intel from the lawsuit but it wasn't an investment because it was just free money so for the longest time intel couldn't like really do marketing they couldn't really do anything because they literally had to let amd take back market share otherwise they were gonna get sue some more oh they said they did purchase we purchased a lot of stocks i forgot what i saw last time on amd that that um i thought 2022 was gonna be even a better year for them i think they i think they got into ai's or something or cars or something like that does anybody remember amd is like tesla yo look at that quarter over quarter growth nuts in 2020 this company was only making 1.7 billion per quarter that was making 4.8 that kind of growth is it's crazy look at that they just barely started making money too and now they're making mad money but the thing about good growth is that you know these things like when you grow so well you can only grow so well to a certain extent because keep in mind um i remember when we were looking at the amd earnings last quarter not last quarter i mean last year at some point there was one quarter where we were looking at amd during the earnings report and they had a 99 percent year over year increase in eps and revenue right and i looked and i was like yo this is nuts this is crazy and the amd stock had dropped that that that's a specific earning quarter as well and and i was like yo this is nuts like amd is a super by the dip right now and we're gonna buy in the dip the next day and just moon right um but but things like that has changed now so you know that was a 99 percent year over year increase now we're at 68 percent right so things has definitely slowed down so you got to be mindful sometimes when the quarters are so good it can slow down even tesla even tesla was was doing like almost 100 percent year over year increase now is pricing in for like a 50 percent year over year increase because you can only beat your sales so much like even when i used to work for the sales company i used to work for this major company and and they would give us bonus based on how our yearly sale did compared to last year so you know like we used to kill it but to a certain extent we were also like we were also like hide the numbers at the end of the year like for example if i would really hit 100 percent year over year on my sales and then come december i would literally book my sales for january from december so that the sales wouldn't get rung up so that i know that i'm stacking myself next year because i have already grown so much because that's how like you that's how you get paid bonus but you'll get to a certain extent where your territory where your sales territory can only grow 100 percent year over year and we'll have like sometime we'll have some other sales people well they'll be like damn you know like i'm at a point where i can't even grow anymore and they will literally kill their territory they will literally like sabotage themselves for one whole year so that the next year they can come back wow look at the cash that they're stacking so for year 2022 right so they just had a 60 something percent growth 67 growth so we're just talking about that how they have 67 growth for the next year 2022 now obviously they they expect to have a good year but they think they're gonna grow much slower at only 31 so that's what i was talking about before how you know when you have good growth it's hard to grow even further i'm actually kind of disappointed at the graphic this quarter um i felt like they're slacking here man like intel i mean not until um like tesla they kind of slack in the graphic this quarter i remember last quarter the graphics were way sexier um there was a lot more hype stuff but this quarter it was like pretty man man they gotten too good they're like yeah we don't need to do a good powerpoint anymore the apes just buy us because they buy us um evo let's see what's up with this evo company evtty i don't see it this one i don't think we have that here man what's this company about evtty two v's gambling company operating internet service sector live casino allows human dealers to run the real-time casino table wow that's pretty cool gangsta it's hard to trade though not much of volume um so they have a 50 growth revenue year over year so coming back to the last year's price pretty pretty cheap 104 dollars um it's probably the future at this point man eps is 78 percent year over year um trading 40 dollars at some point prior to covid on the two-year base that's interesting um i mean like this online type of uh casino and stuff is probably the way things are moving to all right let's take a look at let's take a look at alphabet whoa so they said q4 saw a growing strong growth in advertising business for quarter revenue of 75 billion up 32 percent year over year which is honestly not that much when you compare it on a year-over-year basis especially compared to the way the stock it has already ran to a certain extent it has already been priced in but let's see where that growth is coming from google search and others pretty good youtube ads man google advertising killing it holy smokes the advertising really carrying them google cloud pretty man hedging games oh they are gonna split between across all three's so they said they're they're doing 24 one split in former one-time special stock dividend each shares of the companies a b and c the stock split is subject to stockholders approval if the approval is way what oh i'm not liking the split i'm not liking the split at all so they said if approval is obtained each of the company stockholders of record at the close of business on july 1st the record date will receive after the closed business of july 15 the additional 19 shares oh no how dare you google scam us yo i don't like the split at all i hate it in fact i i i'm sorry guys i'm sorry i just went from being extremely bullish to not bullish at all the reason behind that is because they said they're gonna split in july 1st yo that's so far away that's so far away that's like months man that's like five months away so usually when they do start split right they usually split it in the next 30 days or something and and and when when they split in the next 30 days is usually pretty bullish because a lot of buyers are coming in their height they're like yeah yeah yeah let me buy the stock buy the stock rate so everybody's buying in but because they did is so far away in july which is two more quarters away right um being the fact that is like two quarters away it's actually gonna not like generate a lot of bottleneck as much as now right so if they had to do it right now then it would be a huge bottleneck and everybody would get in and and it would naturally drive the stock price up because everybody would want to be ready for that right but they're gonna do in july that gives a lot of people to plan it gives a lot of you know know things to happen they have two more earnings to happen right so the next two earnings might not be as great who knows you know um and and because of that it's it's iffy there's too much things on the line like i don't even know what's gonna happen to me between now to july 1st you know you know who knows what's gonna happen to me it's like it is so far away it's five months away it's like asking me to plan for something five months away i don't know what's gonna happen five months from now man i might not even be new york you know who knows who knows man might be new whole new variant coming up i might get killed by covid who knows five months away bro i don't know what's gonna happen five months away but yeah that's pretty much it that's pretty much it i'm gonna end the stream here guys we'll be back in tomorrow we'll take a look at some other stuff between facebook welcome um t-mobile align this is gonna be pretty interesting one but damn google disappointed for real that was a huge disappointment it went from hella bullish to like i'm gonna sell that share that i bought before i'm gonna sell that that that position that i picked up earlier i'm gonna unload boys take care guys thanks for stopping by and hanging out have a good night


Welcome back to another OpenShift Commons briefing and as we like to do on Mondays, we are going to have an Ask Me Anything question with one of the most wonderful upstream projects, Fedora CoreOS. We have a number of the members of the team from Fedora CoreOS as well as a few of the OKD working group folks who are also leveraging Fedora CoreOS in a big way. Today we have Dusty May who is going to kick us off with an intro to Fedora CoreOS and a bit of a demo and then after that we will do live Q&A and we are streaming in Twitch, Facebook and YouTube so we will aggregate all the questions and feed them to our lovely contestants today. So with that Dusty, take it away. Hey everybody, thanks for the intro Diane. So my name is Dusty May, I work for Red Hat and I'm here to talk about Fedora CoreOS today. So briefly I'm going to talk about what is Fedora CoreOS, I'm going to talk about some of the features of Fedora CoreOS, how it relates to REL CoreOS and also how does it relate to OKD and then I'm going to give a short demo and hopefully dig into a lot of questions from people. Okay, so here I had planned to start the demo. The demo is actually an install of OKD on top of Fedora CoreOS but I realized that the install time would take longer than my talk so I started it early today so we'll get to that in just a little bit. Okay, Fedora CoreOS, what is it? It's an emerging Fedora edition. It came from the merging of two communities. One was CoreOS Inc's Container Linux community and also Project Atomic's Atomic Host Community. It incorporates the Container Linux philosophy or what we've been referring to as the Container Linux philosophy, the provisioning stack and the cloud native expertise of Container Linux and it also incorporates Atomic Host's Fedora Foundation, the update stack and the enhanced security with SC Linux. So first I want to talk a little bit more about the philosophy behind Container Linux because it really has driven what we've done with Fedora CoreOS. So first off, Container Linux focused primarily on automatic updates which means that the administrator by default has no interaction with the system in order to keep the system up to date. And the goal there is that staying up to date in a default automated manner means that security fixes get automatically applied and your systems stay more secure, so more secure by default. Container Linux also had all nodes start from approximately the same starting point and they used ignition in order to achieve this goal. So you would use ignition to provision a node wherever it started, whether it be on bare metal or on cloud and they all essentially start from the same starting point. Container Linux also focused on immutable infrastructure. So for example, if you'd need a change, you're encouraged to update your configuration and reprovision this kind of guarantees that your changes make it back into your configuration and it's tested because guess what, you've tested that provisioning when you brought up a new node. Also user software runs in containers which means that applications don't depend on the host and the host updates are more reliable. When you have automatic updates, you need them to be reliable. So now we're going to talk about Fedora Core OS and you're going to hear a lot about those features that I just mentioned or the philosophy I just mentioned. The first one being automatic updates. So Fedora Core OS features automatic updates by default and if you have automatic updates, you need them to be reliable. How do we achieve this goal? So we achieve this goal by having extensive tests in automated CI pipelines. We also have several update streams which I'll touch on in a minute that allow users to preview what's coming. Users run the various streams so that they can know when changes are coming that they need to either address or report issues for. We also have managed upgrade rollouts. So upgrades, upgrade windows happen over several days. If people hit issues early in the rollout window, they report them and we can address the issue, stop the rollout window if we need to. And then of course, things will go wrong at some point. For when things go wrong, we have RPM OS tree rollback which can be used to go back to the previous version. And in the future we plan to have some sort of automated rollback functionality where a user can specify, hey, if this particular health check doesn't pass, I want you to automatically go back to the previous version before this update. That's a future feature, not something we have just yet. Okay, I mentioned multiple update streams. Right now we have three update streams which we offer that have automatic updates. One is next. That stream is focused more on experimental features or Fedora major release rebases. So for example, when we switch to C Groups V2, right now we're on C Groups V1 in Fedora CoreOS. When we switch to C Groups V2, we'll land that in the next stream first. It will have some soak time there. Hopefully people report any issues. We get them fixed. And then eventually they'll go into testing and stable. Also for example, when we switch from Fedora 32 to Fedora 33, that will happen in next first. So it's an opportunity for us to put those breaking changes that are going to happen or possibly breaking changes that are going to happen in there and get them tested. Okay, so testing is basically a preview of what's coming to stable. It's a point in time snapshot of Fedora stable RPM content and that is going to go directly into stable in two weeks if we don't find issues. So the goals of having these update streams are to publish new releases into update streams every two weeks and also find issues and get them fixed so they don't hit the stable stream. The Fedora CoreOS release promotion, I touched on this briefly. We have a version number that basically incorporates the Fedora major. The date at which content was snapshotted from Fedora stable repos and then also a number that indicates which release stream we're on. So we have three release streams. We have testing stable and next and that number corresponds to a release stream and then we have a revision. So if we do an ad hoc fix to a content set, we will bump that revision number and re-release. So for the YUM repositories, if this represents the YUM repository moving in time, we will snapshot that on, in this case, the 23rd of March. That becomes the testing stream. We do a testing stream release and then hopefully we don't find any issues. Two weeks later, that gets promoted to stable and people in the stable stream get that content. Okay, the next feature is automated provisioning. So Fedora CoreOS uses ignition to automate provisioning just like Container Linux did. Any logic for machine lifetime is encoded in the config. So it's very easy to automatically reprovision nodes. An example of this is earlier this year, I have a node sitting on my desk in the office that runs Fedora CoreOS and it also happens to be an IRC client server set up that I have. Yet I lost power to it at some point and it didn't turn itself back on. So I wasn't able to get to it and I also wasn't able to get into the office because of COVID. So I took the configs that I used to bring up that server and I just spun up a VM at home and I was back up and running in 10 minutes. So that's an example of because everything is baked into these ignition configs, it's really easy to get a new node up and running in the same profile as the one that you had. And then because we're using ignition, we have the same starting point, whether we're on bare metal or cloud, we use the approximately the same image everywhere. So because we can use ignition everywhere as opposed to kickstart for bare metal and cloud init for cloud, it kind of unifies the whole experience. Okay, so the details of ignition. Ignition is a declarative JSON document. It's machine friendly, so not very user friendly unless you like to read JSON. It runs exactly once during the init remfs stage on boot. It can write files, system to units, users, groups, partition, disks, etc. The key point here is if provisioning fails, the boot fails. So you don't end up with a half provision system. Sometimes with cloud init, you could have part of it succeed and part of it not succeed and then you've got an application up that's half running. With ignition, it's good because you know the machine didn't provision correctly, but it also can be bad because it's hard to debug in the init remfs. So there's good and bad there, but we like it overall. Particularly, ignition is not very human friendly. So we have a tool called the Fedora CoreOS config transpiler. That is a lot more human friendly. It's written in YAML. And it also has what we call sugar on top that will automatically write out some of the more tedious parts of ignition for you. So the next feature I'd like to talk about is basically cloud native and container focused. Software runs in containers and users have two options. They have Podman or Moby Engine, which is also known as Docker. Those two container runtimes, if you're coming from container Linux, you still have Docker if you want to use that, or if you want to try out Podman, that's there for you. It's ready for cluster deployments. So you can spin up 100 nodes and have them join a cluster because ignition configs are used to automate the cluster join. It kind of takes care of everything for you.  So that's kind of more of the cloud native piece of it. It's also offered on a plethora of clouds and vert platforms. So we're trying to be on any major cloud platform and we're adding new ones every day. OS versioning and security. So this is one that I'll dig into a little bit. Fedora Core OS uses RPM OS tree technology. I like to describe it as like get for your operating system. So we have, for example, a particular version of Fedora Core OS, which is kind of like a tag. You have a version and also a Git commit, or sorry, an OS tree commit hash. And this single identifier tells you all the software that's in a particular release. It tells you all the RPM content, tells you all the config default settings that are delivered. And that is important when you are trying to report issues or share information. So as a user, you can report an issue and say, hey, I'm on this specific commit of Fedora Core OS and I run these steps and I see this problem. And that's really powerful. Because it uses RPM OS tree, it also has read only file system mounts, which prevents accidental OS corruption. So if you happen to RMRF on the wrong directory, and it also prevents some, you know, novice attacks from modifying the system. We also have SE Linux enforcing by default, which prevents compromised apps from gaining further access, which is not something that Container Linux had. Okay, so what's in the OS? We have the latest Fedora-based components built from RPMs. We have hardware support. So hopefully anything that Fedora supports, we can support with Fedora Core OS. We have basic administration tools. We have container engines and not much else. So we don't have Python. The goal here is that we encourage users to run their applications in containers and not run things directly on the host. That makes our updates more reliable. We don't want to update the host and break your application. Okay, so coming soon, we have more cloud platforms that we're adding. We also are trying to get support for multi-arch. We've got more, you know, human-friendly helper functions that we want to add to Fedora Core OS config transpiler. We want to make our package layering more reliable in cases that might need that. We want to have more slash improved documentation and then also tighter integrations with OKD. When you talk about Fedora and RHEL Core OS, you want to know what's the difference. So at a high level, the biggest difference is obviously based on RHEL package set versus based on a Fedora package set. But probably the larger thing is Red Hat Core OS is only designed or meant to be used directly with OpenShift itself and not meant to be used standalone. So the updates for Red Hat Core OS are delivered and controlled by the cluster itself and not independently of the cluster. With Fedora Core OS, you can use it either standalone or you can use it as part of a cluster. So for example, with OKD, in the standalone case, you get the updates directly from Fedora Core OS' release servers. In the case of OKD, you get the updates similar to how Red Hat Core OS gets its updates from containers in a registry. So you can use Fedora Core OS standalone with other cluster orchestration technologies or with OKD. OK, specifically OKD is installable with OKD's installer. So the same one that OCP uses, OpenShift install. The cluster controls the OS upgrades, as I mentioned a minute ago. Upgrades are provided as machine OS content containers. And then the cluster can manage and bring up new machines automatically, which I think is the coolest point there right at the end. OK, so let me go into demo. Diane, do we have any questions before I go into demo? Do your demo first and we'll queue up the questions afterwards because then... OK, perfect. Let me switch my screen share. See if this is the right one. And you guys see my terminal window. OK, perfect. So I was going to start this at the beginning of the talk, but I realized that it takes a little while, 35 minutes to bring up a cluster. So I started a while back. So in this case, what I've done is I brought up an OKD cluster running on Fedora Core OS and I'll hop over here to another window and I'll actually show that running. So I'm using a terminal user interface called K9s, I guess, which is pretty awesome. I like it a lot. OK, so this is my cluster. In this case, I have one, two, three of our primary nodes and then two worker nodes. One thing that's really nice is I can dig into each of our nodes and I can actually search Fedora Core OS. And the cluster knows what operating system is running underneath, which I think is pretty darn cool. So this is the Fedora Core OS release of Stable that we just released on Friday. It's from a content set from June 29th. So that's when we froze the content set, we did a testing release, and then we did a subsequent Stable release two weeks later. OK, so this is the node and I can dig into each node. I can see what's running on each node. I think one of the coolest things that you can do with OKD these days, and it represents the tight integrations with the operating system is if we go and we look at the machine sets for this particular cluster, I only brought up two worker nodes. So there's a third machine set here, which has no nodes currently in it. So if I go and I edit that particular machine set and I change the replicas to one, so it will start to bring up a node. And if I want to edit another one, I can bring up some even more nodes. So let's make this one two. And now I can go look at the machines in the cluster and we can see we have two that are provisioning right now. Regarding OKD itself, as those predict provision, you know, typically if you want to look at the help of the cluster, I look at the cluster operators and these kind of give you a sense of the health of the cluster. In this case, it looks like we have one cluster operator that is in a degraded mode, which is not good. I'll need to look into that one. But in general, as long as all of these typically say faults, then you're good. Let's see if those, those haven't come up as nodes yet. But yeah, so this is kind of the demo. I can run OCD bug node to get into any particular one of these machines if I want to. But this is just kind of a representation of the integration with the OS that we have with Fedora Core OS and OKD that makes things like this possible. I can scale out a cluster, you know, depending on my workload. And because it uses Ignition to serve all of these new worker nodes, essentially their role in the cluster, those come up automatically and join the cluster. And then, you know, that's the end of the story. So I think that's all for me unless anybody wants me to poke around here and show anything else off. Someone Jeff was asking maybe, and this might be where, are you able to show off some of the features of your Ignition config? Like a specific Ignition config? Perhaps. Let's see what I have. The one you use to bootstrap the cluster. Okay, let's see if there's anything in here. I don't know if I have those specific Ignition configs, but... And Christian is saying that those are typically created by the installers automatically. And I'm just going to unmute a few folks here so other people can try them and call in Christian. Yep, yeah, so here I just highlighted one Ignition config in the terminal here, which is more or less the one that's used to bring up the bootstrap node, which is essentially what kicks off the entire install of the cluster. So this Ignition config has some user information where it sets SSH keys. It writes in different registry configurations. It pretty much defines everything that needs to be set for this cluster in order for it to do everything it needs to do. So we've got CA information. We've got services that start. It's just a whole host of different things. Does anybody know of a particular thing that might be good to show off? Well, one thing I would add to this. So part of what came from CoS was container Linux, but also Tectonic. A lot of OpenShift 4 and OKD now is based on an evolution of Tectonic design. And so for OpenShift 4, the Ignition configs are actually cluster objects themselves, like Dusty, if you want to do OC get machine config. So as an addition to the CoS model, the integrated machine config operator will support day two changes. So as was kind of mentioned, the Ignition is provided in install time. And so OpenShift and OKD work the same way as any other workload on top of Fedora CoS. But in addition to that, the MCO kind of takes over day two. And so you can create a machine config object with OC and that will that change will roll out to the cluster. Someone is asking also, what happens when you create a machine config that breaks the host? For example, a mistake in the system D unit, will it automatically roll back? Yeah, I'll just echo it. Vadim said basically the MCO today only rolls out a change to one noted it. So you can adjust that and you may want to do that in larger clusters. But so if you create a system D unit file that breaks boot up, then only one node will go. He's again asking. So the node will stay disabled for scheduling? Yeah, yes. And it depends where you break it. But yes. So from YouTube, someone's asking, what about support for hardware raid controllers for bare metal servers like HP Gen 10 and super micro servers? Also VLAND and bond support for network cards? Have we gone there yet? Yeah, we should have support for complex networking configurations. Anything that network manager supports should be just fine. As far as the, did they say hardware raid? Is that what you said? Hardware raid, yep. So as far as hardware rate goes, assuming that you don't need a special driver in order to bring it up, then the hardware raid just shows a disc to the OS, right? So like whatever is configured in hardware raid, it usually just shows a single device to the OS. So that should work. Is that specifically a question about like modules and or drivers? Yeah, Vivian has not said that yet. So we'll see if she clarifies that. Okay, gotcha. Do that. Yeah, software raid, a slightly different story. We're working on complex root device. Stuff, we're not quite there yet with the root partition at least. We're shipping a regular Fedora kernel and Fedora core OS and a regular rail kernel and rail core OS. So in terms of just strictly drivers, anything that works for those destroyers should work here. Good to know. Thanks. Well, lead asked the question, and I think it might have been answered in the chat. Would it be possible to report back to Red Hat satellite foreman for overall inventory security stand? And he said it came to an internal audit for rail core OS nodes. We're not part of the satellite host's inventory. Yeah, I can take this one. So, you know, I think one of the, I guess for all of the open shift, certainly a huge design point was that open shift and, you know, OKD should be self-driving by default. Like it shouldn't require you to run external infrastructure to say, spin up a cluster at AWS or GCP or public cloud, we definitely want to integrate with an external system. So I think the short answer to this would be, you can always run a demon set or a system D unit file that runs on each node that does, you know, a web request to foreman and asserts the machine health. I think that's probably the shortest answer. But, you know, it's actually interesting because the demo Dusty did of the machine API is actually the cluster itself, like you can spin up new machines using OC, like your user experience is OC to control the inventory of things. One other question. What is the proper way of accessing Fedora CoreOS when network is not working or the SSH private key gets lost depending single to the kernel parameter didn't work for him. So I guess it depends on how long ago this person tried that because we did some work maybe a month ago or so to make sure that a pending single to the kernel command line should drop you in appropriately to an admin shell or whatnot. So you should be able to set a password or change an SSH key. If they didn't set a password, maybe there was an SE Linux problem when they got into that Dell. But I would say open a bug and we can try to go through that. We do have a doc page that kind of says what to do when you're trying to recover your system. So that's on the docs. So hopefully those steps work now. If they don't, please do open a bug. Could you pull up and share the docs page for that? Just that might be a good segue here. Sure. And then there's a bigger question. There's always a bigger question, a less technical question. But I'll throw it out there now because one of our guests did earlier. And here we go. Perfect. Thank you. So it's about the relationship between REL, CentOS, and Fedora. And you knew we would get one of these questions and I figured that. So from Fedora REL and CentOS, he knows that Fedora is upstream with the latest features. Whereas REL is the stable enterprise version and CentOS is the stable free version, which leads to many enterprises appreciating CentOS for stability. How does Fedora CoreOS fit into this pattern? I want to take that, Dusty. And we can have a conversation about that. And maybe also incorporate a little bit about CentOS Stream and what that might be. They might not be familiar with that. Okay. Yeah, I'm trying to think of the best way to answer this question. Obviously, there's a lot of different ways to answer it. But in general, we have Fedora CoreOS. We try to do everything upstream there. REL CoreOS actually follows very closely with the development that's going on in Fedora CoreOS. With a slight package set tweak that includes things that are specific to OpenShift, like Cryo and the container runtime there. So it's a little bit different than normal Fedora to REL. It's kind of like the set of packages is the traditional Fedora to REL, except for some of the packages that we focus on more like Ignition and things like that, which kind of get updated a little faster. As far as CentOS goes, right now, we don't have any plans to make a CentOS CoreOS, mainly because it's taking all of our efforts just to work on Fedora CoreOS. But I do know some people have expressed interest in that, especially in the OKD working group, making essentially a CentOS version that OKD can run on top of. But I don't have any plans for that right now. Was the question specifically for plans related to it or how does it fit in? Our guest, I'm going to unmute to see if he can do this. He's on mobile device, so it might not be able to follow up on that. But I know we've had a lot of conversations about this in the OKD working group and we have Christian and Vadim with us from that as well. A lot of it has to do with resourcing. And there is in the CentOS world a PaaS, a PaaS working group, where that conversation has been taking place. So Christian, if you want to chime in a little bit, if we can hear you, I can see you now. Yeah. I can hear you now. Can you hear me too? Okay, perfect. So yeah, the reason we chose Fedora for OKD as a starting point is because we get that feedback loop and we actually complete a feedback loop by having changes trickle down naturally because Fedora is the upstream. So everything below that will get those fixes eventually. While CentOS is the end of the most downstream thing and anything that gets fixed in CentOS isn't landing anywhere else. So CentOS is essentially a repackaging of rel. So even in the standard CentOS, if anything is fixed in CentOS, first it doesn't really land in rel naturally. So for us it was just we... And that was kind of broken in the OKD 3.x releases because that was also just a repackaging of OpenShift. So we really wanted to make sure that we get a feedback cycle working where any bugs we hit in upstream will also be fixed downstream. So I think from a Reddit perspective it may make sense to also create a CentOS stream based CoroS that would run OKD. I'm not sure we will invest any resources into, at least not ourselves, into creating a CentOS CoroS OKD, which would be, again, it would be downstream and none of the other products would benefit from it. Yeah, I think... Go ahead, Colin. Yeah, just one aspect to this I think is really interesting is containers fundamentally change how we think of the operating system. So in this whole conversation we've been talking about the host and for some people that's important, but all... You can run the Rally UBI container on Fedora CoroS, right? And not only can you, you should, right? Like that's a totally normal and expected thing to do. So for application developers, you don't have to... You still get the benefit of Rally and the CentOS stability for your app stream while newer hardware enablement and all that stuff comes in in Fedora CoroS and that only impacts the system administrative side. Yeah, so I think that split is really important. I think that one of the very early slides that Dusty put up was about where the container Linux and the project atomic project came to live was in the Fedora world. So collaborating with them made sense for the OKD working group in terms of stability and in resourcing the effort. So that's been, from the working group's perspective, it's been a really nice relationship building period. Yeah, another thing on the resourcing front, like with Atomic Host, it was kind of more of a a lot more passive relationship with Fedora where we would build the same package that was in Fedora. We essentially only have one stream in the terms of what we're doing with Fedora CoroS. So it was a lot more passive and a lot less resources required. Now we have three streams. We kind of need to keep up with features that are in next versus the other two. We need to triage bugs that are against ones versus the others. When we do automatic update rollouts, we need to kind of focus on, did this update break anything? Does it need to be rolled back? So that's why it was a lot easier to do a CentOS Atomic Host in Fedora Atomic Host because it was a lot less resource intensive. But because we wanted to focus on automatic updates, we needed to put some of this other stuff in place. And that's why when people talk about doing a CentOS CoroS, it's like, oh man, that's a lot of work. But we want to enable people to do that if people want to step up and do that. So we would love for it to happen. It's just a lot of work. Yeah, it's a lot of work, but I think the pattern has been established and a lot of the difficult hoops have been figured out. It really truly is a matter of resourcing, I think. And if the community wants to step up, happy to help drive that as well. But I think it really comes down to that. And I think as Colin, so aptly put out, containers changed everything. So that would be that.  There was another question from Paris, Lucas from YouTube. What is the status of the Fcause OpenShift code ready container? Boy, we've talked about that one a lot in the working group. Christian, try a couple of things. You want to give a... So I think Vadim may know more about this, but I think we've been able to build it. And there is sort of preview or a proof of concept that it works. We haven't been able to actually change the project to build on top of OKD by default, as opposed to OCP. So there's still some discussion whether we want that, whether we want to keep that R-Cos, OCP, OpenShift, OpenShift platform-based, or switch it over to OKD, or maybe do both, which is, again, work we haven't tackled yet. So technically, it's possible. And we have some guides for similar things, like OneNote installations of OKD already. So there is definitely some discussions that are going on. Yeah, so this is an AMA around Fedora Core OS, and we had one the week before on OKD working group. But if you want to join the OKD working group, there's a whole thread about the single-node cluster with a whole bunch of people who've done some homelab stuff and some really great stuff, but it has not filtered down into an official code-ready container. Yeah, Vadim, I think you should be unmuted now if you have anything to add to that. Right, from the technical part, we built an OKD-based CRC bundle, and now it's the team deciding which way do they want to go, the CRC team deciding which way do they want to go. And it's a really hard choice, because the OKD's features are not that important in code-ready containers. We'll be keeping an eye on that, because the difference is just the basis for do they want to go with Fedora Core OS or El Core OS, and it's up to them to decide what's best for their product. So there's nothing that keeps us from creating something similar on the community side, other than I'm always going to say the word resources and maintaining it once you build it, because we've all been there before creating VMs for the early origin that we had to maintain with every release as a community thing. It was fun, and keeping up to date is a thing. And also, we've been having a conversation in the OKD working group about ARM64 architectures, and Ryan's asking any news about Fedora IoT and the new provision site looks really nice and interesting, but maybe you could talk a little bit about the roadmap or the visioning for Fedora IoT and Fedora Core OS. Everybody just nods. Yeah, so I know we do, like I mentioned earlier in the slides, we do have a plan to have an ARH64 stream or set of streams for that platform. We don't have that just yet. I don't think we have any official plans to merge Fedora Core OS or Fedora IoT together. I think there's some slightly different goals there. One of them being Fedora IoT, obviously plans to run on some 32-bit ARM hardware, and that is not really a goal that we had from the outset, because we're focused a little more on servers. ARH64 just seemed like a good line in the sand to draw. But yeah, I don't think we have any official plans for merging the efforts, but that is something to talk about and explore. We're always interested in how to make things better. Somebody else might be able to speak to this better than me. That would probably be Peter Robinson, or Robinson, rather, and so we'll have an AMA on Fedora IoT some time soon and make him come and talk. There's also a little confusion out there in the marketplace and I think or in the community space around that, but I think, as others have said, ARM is becoming ubiquitous out there in the IoT land and it comes up often. And I think that's there. From YouTube, back to that hardware question from Vivian, for the hardware question again, I mean, not only installing a preconfigured RAID volume, but also configuring RAID levels from ignition configuration. At the moment, it's possible to do that for, I'm going to say that acronym wrong, MDADM only, and not for hardware RAIDs. Yeah, that might be something where we need a specific issue to dig into, but basically, I guess, they're asking for support for ignition to be able to configure hardware RAID controllers. Yeah, that seems slightly out of scope. I guess there's typically a tool that is shipped to talk to them or maybe there's a kernel interface that already exists. But yeah, I think maybe a specific issue, I think her name was Vivian, would be good and we can hash out some details there. I can link to the issue tracker for Fedora Core OS and we can kind of take it from there, I think. If you could share your screen and go there, that would be great because that person is not in the blue jeans. Okay, perfect. Well, maybe we'll see where the issue tracker is. Let's go back to the presentation. And I have a slide for getting involved. So if you want to go just grab Fedora Core OS or view our releases, we have the top level get fedora.org slash core OS. For any issues or kind of design discussion related stuff, we usually open tickets in our Fedora Core OS tracker. So that's github.com slash core OS slash fedora dash core OS dash tracker. So you can open an issue there and that's where we can kind of dig into the details of the hardware rate controller support. And we also have a forum if you have kind of like a more of a user-related question related to, you know, I can't, how do you set a password or things like that? The forum's a good place for that. We have a mailing list and we also have Fedora Core OS on FreeNode. Should I go to the issue tracker, Diane, or is this good enough? Just go for a quick, quick ride over there to Fedora LAN. All right. So this is kind of our issue tracker where we try to triage things and it's got everything from, you know, actual bugs to let's discuss things, right? So here's something about how do we want to integrate with, you know... We're still just seeing your slides, so maybe you have... Oh, okay. Hold on one second. Split screen personality. Yeah. Let's see if we can, I think, does this look better? That's it. There you go. Okay. Yeah. Sorry. Popped open a new window and I clicked on that link that was not shared. So, yeah. So this is the issue tracker and we kind of have everything in here from actual bugs to discussion topics. So this particular one is where we're chatting about how we want the OKD release schedule and the Fedora Core OS release schedule to relate to one another. Should they be related? Should they not be related? How do we want to go about it? So a little bit of everything in there. And one of the guests is asking, and I think you had a slide on it already, is Fedora Core OS already usable in Azure, AWS, GCP, and elsewhere? There was a slide. The answer is yes. So if you go to our download page, so there are two regions or two clouds in which we have automatically uploaded images right now. Those are AWS and GCP and we're trying to work on other ones. However, we also have images created for a lot of different clouds. So we have Alibaba, AWS, Azure, DigitalOcean, ExoScale, GCP, OpenStack, and a few others. We also have VMware images. But in general, if you go to our doc site and you click on the provisioning machines breakout, you can see how to actually provision a machine on a lot of different cloud providers that we have. So for example, you asked about Azure. On Azure, because we're not currently uploading directly to Azure or at least we're not able to share an image that others can use, we show you how to download it and then upload it before you start to launch an instance. So if we don't have it automatically uploading, we hopefully have steps to show you how to do that. Thank you for that. And thank you for all the effort that you guys obviously put into making this happen everywhere because it's making a lot of OKD people very happy. And hopefully when we get to GA, we'll have a lot more feedback on some of this. Let's see if we've gotten everybody's questions answered. Can you talk for me a little bit about Ignition 3 support versus Ignition 2 support? I know that's been something that we've had a conversation with in the working group about having it there. Where is Ignition at right now in terms of Fedora CoroS? Oh, I can best detect it. No, I'll let you take it, Christian. The TLDR is it's very close and Christian's been working on it very hard. So yeah, in Fedora CoroS, we started with Ignition V3 from the get-go. So that's always been V3 in Fedora CoroS. In Red Hat CoroS and OpenShift Compute Platform, we started out with Ignition configs back V2. And now in the upcoming release 4.6, we will switch OCP to Ignition spec V3 as well. So it'll be the same.  And OCP will switch to V3.1 as well in the future. And Vadim is pointing out that it's shown the machine config pool screen, which had shown both Ignition spec 2 and Ignition spec 3 machine configs. Yeah, that was, we kind of had a, in the MCO, we added dual support so we can provide either one and it'll be translated to spec 3.1 for OKD and 2.2 for OCP. So just to facilitate that migration for OCP to move from spec 2 to V3. But that's really an implementation detail. And OKD users should always be using spec 3 or spec 3.1. And that should be fine. I think I'll just add on top of this is we're really close to fixing a lot of, like building on top of a whole lot of infrastructure that we spent the last like two years or so building and there's a whole lot of new features coming in Ignition around. I think Dusty may have briefly mentioned around managing the root file system and a whole bunch of encryption and a whole bunch of other stuff that I think a lot of people will really appreciate. So this is all kind of coming together now that we have spec 3 supported by OKD and will be used by ARCOS 2. Interesting to watch the resources or the people who are working on all the different projects here. And Christian seems to have his finger in just about every patch here out there. So it's quite useful having you on the OKD team as well as watching all of this other stuff. Mike Rogford asked a question. I'm not sure we answered it. But in terms of OSs and use how or would you create a split between RHEL's UBI based images and the builder templates and those derived from Fedora. It's trying to figure out the best way to even phrase the question. So that makes sense to folks. Could you repeat the question? It's in the chat as well and I think he's still with us. So maybe he can like if you want to unmute you can clarify that. Not to put you on the spot but yeah to put you on the spot. But are Fedora container images a goal for OKD? So I think it's a secondary goal for us to obviously build out that Fedora container ecosystem. So in the future the OKD working group we've already talked about this last week will meet up with the Fedora container SIG and yeah obviously we're interested in delivering all of our operators on Fedora containers as well. It also works the way it is now with UBI based containers or CentOS based containers. But obviously yeah we do want to encourage people to to build a Fedora containers and use Fedora containers for everything. Now someone asked me earlier today in Slack about the OCP's operators the operators that weren't in operator hub.io yet. And if there's a few operators that are specific to the operator hub that comes with open ship container platform and if we were we the working group was going to rebuild all those on Fedora CoreOS and I think that's a bit of a significant effort and I think it's also some other other questions around that as well which ones and I think it's specifically they were talking about service mesh and Istio making sure that there was one-to-one parity with what is available in operator hub.io. Yeah as far as like rebuilding things on Fedora images I think that would be it would be great to have but you know a question to have is or a question to think about is like is there a trade-off for doing that work is there other work that we you know should do instead if for example that was going to push the OKDGA out to January of next year would that be something we'd want to do. And the other thing too is you know if things are able to use a UBI base and we have only one version of them it's a lot easier to maintain. So it's just like there's a lot of trade-offs to think about when you start to go down that road which is the exact same thing which we were discussing earlier with a Fedora CoreOS and CentOS CoreOS right. Resources often are the limiting factor but we want to do things and we want to get more involvement from the community as well to help us achieve those goals. I think that maybe related to ICO is this concept of host dependent containers because I think ICO ends up programming IP tables and things like that and so that is a tricky topic to handle. We have some discussions around that around how you best have a container that you know partially executes on or manages the host but hopefully we can get to the point where even these host dependent containers like ICO work in both cases without needing to rebuild. I think the first step we're going to do here is just building those containers that aren't currently publicly available without a subscription that are rail based, rebuilding them in Fedora just to have feature parity with the community version. I don't think we don't have to rebuild all the UBI8 containers because there's just no benefit to it really. Yeah I think that that'll that'll be good and that might be a good way of doing it. Getting parity is what we want and then you know if third parties want to go and build something out there and host it in operator hub.io god bless them if the working group either the OKD or the Fedora CoreOS or some other working group the Fedora container working group decides to take on that then bless them and find a resource. I think that the really what we're just trying to do today and I think Dusty's got another talk on Community Central this week and we're going to be doing a lot of talking around OKD4 is really getting the word out about how to engage with these communities, how to test the the work that we're doing and give us your feedback on Fedora CoreOS. Make sure that the cadence of release cycles and stable releases are working for everybody and that we all stay in sync and connected on these things so it's and we recruit new bodies to continue to do more work so I think that's really been there. In terms of the roadmap for Fedora CoreOS Dusty and Colin what's next? So I would say we've got a few issues that are kind of you know periodically come up that we're trying to work on next. I mentioned one earlier which was multi-arch so we have you know some very motivated people in the community that kind of maintain a secondary pipeline for different architectures and we want to make that like part of our official pipeline right so we want to try to release stable for you know all architectures at the same time. We want to have the artifacts show up on our download page. We want to have them signed by Fedora Release Engineering like our current 64-bit Intel artifacts are so that's something we're going to try to work on next. We mentioned complex root device stuff that's in the works right now. We're always doing something around networking it feels like so we're trying to enhance it so that for example right now we default to DHCP when you first bring up a node which is a same default but in some cases it can be problematic so we're going to try to change it so that if you don't actually need DHCP on that first boot we're going to not bring it up right. Let's see what else oh so even though we discourage package layering in Fedora Core OS sometimes it is advantageous to do that for maybe some small feature that's like a host level type thing that is just not very easy to containerize or either a very big maintenance burden to containerize so we're going to try to make package layering more reliable. We've had this problem for a long time with our OS tree based distros silver blue atomic host Fedora Core OS so we're going to try to tackle that problem on the Fedora Release Engineering and infrastructure side and see if we can help that out a little bit so a lot of small things cloud providers you know if you're a cloud provider and you want Fedora Core OS running on you we would love to have make that happen so yeah just more of the same for right now obviously OKD is just now getting to GA but we want the relationship with OKD to be tighter right so we've been doing a lot of foundational work in Fedora Core OS haven't had a lot of time you know Christian and Vadim have done an amazing job without a lot of help from us right and we want to make sure that that integration is better right we also want to look at other Kubernetes distros like Kubernetes distros like Typhoon who are also using Fedora Core OS underneath right how can we be a better platform for them so those are the types of things that we're looking at you know in the short to mid-term. Perfect well I think it's um it's a great relationship I think we're just going to have to foster more of them in the coming months and weeks and days and move it forward if you want to throw back up your final slide with how to get a hold of everybody that might be a great way to end and we'll definitely have you guys back on and continue to collaborate with you across lots of different communities so thank you all for joining and we look forward to many more releases in tandem with OKD and others. That's fine, thank you all. All right thank you all for joining take care today.


Him? His only reason is how you look beautiful today. Nah, gee, if you really dip it, I'm not a simp. Who is the biggest mama's boy? I love my mommy to death. I can't lie to you. My mom does everything for me, but she puts my underwear, my room. This guy was breastfeeding to the age of 14. Who's most likely to get posterized on the court? Michael! Michael! Michael! Michael! Hey, that's my son right there. Everyone, I've got a B. Ready? Duh. Duh. Duh. Now we out in summer jam, you know I'm the man. All my bubbles rich and we're trying to get some bands. Call me Michael Jordan, I'ma hit you with a jam. Ballin' cause you know that's who I am. And I never number two. I been movin' with my gang and we movin' pretty smooth. I better be on TikTok. No, my Rick Ross, I'ma be like a Rick Ross.


7 Awesome ESL Conversation Activities to really get your students talking. We all know what it's like to teach a class with reluctant students who don't want to talk. It's like pulling teeth. However with these 7 Awesome ESL Conversation Activities, you can really get your students talking. 1. Icebreaker Jenga. 2. Get to know you bingo. 3. Mystery Party Guest. 4. 20 Questions. 5. Play a game. 6. Apples to Apples. 7. Choose your victim. These 7 activities will definitely get your students talking, and make your classes interesting at the same time. Thanks so much for watching. We are ITTT, the leading provider for TEFL and TSOL training courses. If you like this video, please subscribe by clicking that button down here, and click on any of the videos here on the left for more interesting teaching tips for getting certified to teach English abroad and online.


We're shaking. My name's Cam and welcome back. Welcome back to another video. Happy 2021 everyone. I hope you had a great Christmas. I hope you had a good New Year's.  Show it who's boss, you know? Consensually, of course. Personally, I'm planning to square dance my way through the next 12 months as productively as possible. I have a lot of plans and goals for my writing and for this YouTube channel, but that's another video. So not counting my short story in the Booktuber horror anthology local haunts right here, I don't actually have any published books out right now. I did have a self-published fantasy series like a while ago, but I did have to put that one down like a dog with a gambling debt, unfortunately. I actually made a video not too long ago on that fantasy series and why I actually killed it. I'll leave a card up here. I consider myself and anyone else who writes, be that recreationally or professionally, a writer. But without any published work out there in the world, I'm really hesitant to call myself an author. Authortuber, yes? Author, no. Come on. Keep up, guys. Keep up, guys.  The moment that I and like three of you watching this have been waiting for is coming up. In less time than it takes to grow a beard, for me at least, I will have a full length novel for sale. On the 25th of January, my psychological horror book that I've been working on for nearly two years will be available for purchase. It's called Welcome Descent. I'm sure a lot of you already know that. I mean, it is the talk of YouTube at the moment, but there is a reason I'm making this particular video today. I have some updates regarding the release of the book that I want to share with you. At the end of this video, I actually have some new stuff to show you that you probably haven't seen yet. And I also want to just very quickly discuss some of the issues that I had with the final steps of publishing this book, because Jesus, my dude, I had some issues. First things first, the book is actually technically available right now on Amazon. You can find the link in the description below, or you can go to my brand new author website, camwolfbooks.com. I just want to add I got a new author photo taken recently, and I think, I think I look very handsome.  Girls, multiple, multiple girls, bitches. My friends have already given me the obligatory amount of smack for the pose in this photo. I know, cringe, whatever. But hey, being sexy has a price. Like, like being alone all the time. So you can technically pre-order Welcome Descent right now. I wanted that option to be available to you more than a month ago, but we had some major editing issues, unfortunately. Some stuff that kind of flew under the radar and was noticed, luckily, at the last minute and had to be ironed out. The thing is though, you can pre-order the ebook and the physical copies on a lot of Amazon pages, including like Australia's Amazon page. But for some reason, a lot of others like the US Amazon page only has the ebook for pre-order right now. I don't know why I did my best to look into it, but it's a real eff around. It doesn't matter though, you can pre-order the ebook right now if you want to, or you can wait until the actual release date 25th of January and get yourself one of these very pretty physical copies. There is the paperback or the hardcover, and I think both look really awesome. I like the paperback because I went with like a snug kind of size. This is the old trade paperback, sizes that you don't see much of anymore. It just reminds me of the old school horror books and I like how it fits snugly in your hand. But then obviously the hardcover is the hardcover. It's very pleasing to look at. It's, you know, nice as well. I know a lot of people prefer getting hardcovers for the aesthetic and for the comfort, so that's an option as well. If you're in the US, you can pre-order the ebook now or you can wait and you can pick up one of the physical copies or you can get none at all. It's cool. It's not like I need to eat or anything. Jokes aside, I really, really do appreciate all of the love and support you guys have been giving me so far. It really does. It means a lot. It's kind of blown me away, and to be honest, it's more than I deserve, so thank you. Now, I published through IngramSpark, mainly because it was the only option really where I could have a hardcover. And for the most part, it really has been great, but I did have some issues. I plan on making a full video diving into the pros and cons in my experience with publishing through IngramSpark because it's really different to when I published through CreateSpace or KDP as it's now called. But one thing I do want to say in this video is that the fee for uploading new files for your books is absolute BS, man. It's absolute robbery. I had to fix a minor error with the formatting like just last week, and to upload new interior files, it was about $30 for each, like for the ebook, hardcover, and the paperback. It cost me nearly $90 just to upload new interior files for books that weren't even being sold yet, and I just, I think that's kind of bullshit. I'll also be making a full video about the costs involved with self-publishing this book, but I do want to wait a little bit until the book's been selling for a bit so I can see what the return profits look like, and then I can also include that in the video to try and see like how much I lost or how much I made kind of thing. What I will say though is that I have spent a ton, man. I've spent a lot of money on this. That was my choice, and to be honest, I just, I really don't see myself making it all back. It's just a lot of money, but you know what, that's okay. Surprisingly, I'm actually really okay with that. I would simply be happy if people are reading it and enjoying it. That's, that's really all I can ask for, you know? Another, another weird issue that I had for a bit there was that the genre categories for welcome descent were all listed as like erotica genres. I'm not joking. I can't find the screenshot right now. I did screenshot it, and if I find it I'll put it up here on the screen, but you know how it lists like three categories? It was like erotic horror, erotic thriller, and erotic psychological. I have no idea why or how that happened, but luckily it was fixed after one email. I don't know, man. Maybe they heard about the groundbreaking bizarro erotica book I wrote for a laugh ages ago on YouTube. Maybe they saw that and thought it was like a shared universe, you know? Like BMCU, but for horny nonsense. So those weren't the only issues I had during the publishing and formatting of this book, but like I said, there will be other videos. There will be a whole other video going into the intricate details of that. I just wanted to make this video to let you guys know that we're nearly there. What I've been working towards for like nearly two years or more. It wasn't easy. It was an intense story. It was a difficult process, and it took a lot out of me, but I'm proud of myself for finishing it. And in retrospect, I'm really proud of the finished product as well. If you want to know more about what Welcome Descent actually is or the story involved, I'll leave a card up here for a video where I talk all about that. You can watch that or you can stick around for just a minute or two longer because I have something very special to show you. I'm going to show you two things. The first one you might have already seen because I showed it a little while ago, but that's the book trailer for Welcome Descent. I'm going to show you that in just a second. Like I said, you might have already seen it, but I'm showing you again. So shush. The second one, I am very excited to show you. No one's seen this yet. It is a snippet from a professional audio recording of Welcome Descent chapter one.  I don't have a full audio book for Welcome Descent at this point. It's just it's just too expensive. Like I said, I've already spent so much money on this and I just I literally can't afford to get a full audio book done. But people have been asking for a sample of the story like the first chapter or something like that and I'm happy to give that to you. But rather than just post up the first chapter and writing, I thought I would do something special. I thought I would get it professionally narrated and I did that. I had the full first chapter narrated. It's about 51 minutes long. So I can't post the full thing in this video, but I'll show you a snippet of it. And if you want to listen to the full chapter one audio recording, I will also leave a link in the description below to go check that out. Or you can just hop over to my horror YouTube channel, Wolf's Inferno. That's where I put up the book trailer and stuff as well. Anyway, that's it. That's all the info I have for now. Thank you so much guys for all of your love and support. It is just it's meant the world to me. So thank you. I will see you in the next video. But for now, enjoy. Catch ya. One week was all it took. I used to have everything before, before it happened. My cars, the house, my wife. They're all gone now. I've been hearing things since that storm arrived. Voices. Voices that shouldn't be there. They're just outside my door. Welcome Descent by Cam Wolf. Enjoy the climb. Beware the fall. Welcome Descent by Cam Wolf. Chapter One. Steel and Concrete. On the closest thing to a good day, it would be a resilient beam of morning sunshine that woke Joe. Blistering golden light would slice through even the densest mid-morning cloud and creep its way to the snoring, farting, massive limbs named Joseph, still tangled in his sheets. On this particular Friday, however, it was his radio alarm or, more specifically, the opening brass band notes of Jingle, Jingle, Jingle by K. Kaiser that did the job. Yippie-yay, there'll be no wedding bells for today.  He flailed an arm to silence the ear-splitting merry tune failing spectacularly and knocking over a whiskey bottle instead, the now empty bottle that had helped him get to sleep the night before. It fell to the floor with an almighty hollow thunk.  He had turned 42 the week before and everyday since had been a taunting, spiteful reminder of how easily his body would give in under the slightest physical strain. Apparently, now simply waking up was asking a little too much. He gave one more strenuous groan and threw himself out from the bedsheets, nearly landing on the bottle he had just backhanded. The vile mix in his stomach rolled in place, launching a bitter, battery-fluid taste of acid reflux into the back of his throat. God damn, he said with a scowl. He ran a hand through the thinning pale hair of his temple and stepped up to the floor to ceiling window, stretching his arms out at unnatural angles. It was a shitty day to say the least. The congested city street below was bathed in a miserable sheet of mist and stark blue shadow cast down from the impenetrable gray clouds high above. They were tumbling over each other like the fourth of a swelling evening tide and barely a candle's glow of sunlight could be seen through the black. Joseph imagined the heavens were mocking him, daring him to hope for a good day.  I dare you. I see half a smile and I'll be shitting hail. All the pedestrians in cars, eleven stories below, were dulled in detail and volume, sealed away behind that magnificent two-inch glass. Joe liked a view from up here. It was the distance he enjoyed, the distance between himself and the swarm of always stinking, always staring nobodies. He regarded the impending storm once more before making his way across the small studio apartment into the conjoined kitchen. He made sure to nudge the bottle with his heel so that it rolled under the king-sized bed with a prolonged rumble. The final notes of the swing jazz monstrosity had finally burst through and distorted squawks and now the day's news was being read by the world's least entertaining DJ. His voice was a droning bass and he sounded about as pleased with his job as Joe was about his breakfast, the brittle remnants of a long expired box of cereal. We have a big one coming in, folks. We're looking at a category two for now, but keep me close because we may have a three on our hands. You don't want to be strolling around the streets of Dawn Valley during this one, that's for sure.  Joe snorted.  He grabbed one of the last few apples from the fridge and gripped it between his teeth before snatching the Oxford button down from the back of his one and only dining chair. The shower would have to wait until after work. He had set the wrong time on the alarm again and the large red numbers were blinking at him with merciless repetition. 1034. Shit. He didn't dress quickly enough, however, to avoid seeing his reflection in the darkened glass of the window across the room, there's nothing quite like spotting yourself in poor lighting, especially while bent over trying to fish a tie from a pile of dirty laundry. He was by any definition well groomed. He kept his hair cut tidy and his face clean shaven, but below the neck he was hiding a chest of tangled white hair and the early warning signs of a beer gut. After deciding two seconds of self pity were two seconds too many, he finished his wins or not, slipped on his black suit jacket and laced up his derby shoes. One of the greatest pleasures for Joe in his day was the feeling of the finely woven wool of the suit pants against his knees and the way the sleeves hugged his biceps. This suit, a pristine Valentino, was the last remaining survivor of his collection. The rest had been sold for a painfully slight margin of their original costs, just to secure his place in what, for the last 10 months, was now his reluctant home. In a matter of minutes, he looked as though he could have been escorting the United States president across the White House lawn. Of course, the reality was far from being that glamorous. He stepped up to the window, doing his best to erase the admittedly still slightly intoxicated shirtless sad sack from his memory and replace it with the new well-dressed doppelganger. It was while adjusting his tie a third time that something smacked the glass with such force that it rattled the frame. Listen to the rest of chapter one of Welcome Descent at Wolf's Inferno, or find the link in the description below.