Thanks everybody for coming We'll go ahead and get started if that's okay So how many of you guys are really enjoying OpenStack? It's a trick question how many of you guys are asleep So my name is Michael a day. I'm from Heela Packard. We also have Eric sacks from Oracle and Glenn Foster from Oracle as well and We have Nigel Cook from Intel and today we're going to be talking about this interesting very polarized debate about pets and cattle and how we can how we can add some current best thinking to it as well as make OpenStack very safe for these kinds of adorable little animals that It's ironic. So this is Eric's cat and And whenever I saw this picture I said did the cat really look at you like that? Because I mean Correct me if I'm wrong, but that cat does not have the typical disdain that most cats have for their masters Correct. Doesn't this look more like admiration than disdain? So he must be doing something right with his cat and I suspect that's translating into Stuff that he's doing right in OpenStack, although the correlation hasn't been established yet. So How many people are familiar with the the argument around pets versus cattle? Okay, if you're you're in the wrong place you need to leave no, I'm just kidding We're not that polar here So pets versus cattle is a great argument for Building a community because it's it's very elementary. It's very binary It helps people understand the concepts But it's really bad if you it's really great for illustration But it's really bad for a community and the reason for that is because this is a very polarized argument And it and it really doesn't have to be Pets versus cattle is illustrative of the underlying Opportunities that we have within OpenStack and To approach this argument in the polarized way and that is currently being approached It's not a bad thing, but it does it does create an interest gap and it creates a an Exclusion and in reality OpenStack will be most successful when enterprises deploy OpenStack And I mean deploy OpenStack for more than just easy web workloads When they deploy OpenStack for critical workloads when they start using it for their their infrastructure their the spine of their organization and It is very well suited to do that in many cases and there are clearly some opportunities that remain but You know we want to begin depolarizing this argument as much as possible and understanding what the underlying implications are of this argument and The way that I generally think about this now is that it's no longer about pets or cattle It's more about whether you have a highly managed workload Or you have a workload that requires very little management a lightly managed workload so heavily managed workloads I equate to pets and Very lightly managed workloads. I equate to cattle and I think that if we if we can understand those those ends of the argument and the stratification within that spectrum then we can begin to address the shortcomings Inside of OpenStack that make it less acceptable for certain types of workloads So again OpenStack will win as infrastructure when it begins being deployed in areas of increasing criticality and In order to do that Will pick up workloads that are increasingly important to the enterprise these workloads Have some general properties they They become increasingly highly managed They tend to want to scale up instead of scale out They don't support the the architecture that's associated with cattle based applications and Or cattle cattle designed applications They have performance and reliability tied to the underlying infrastructure more closely And they might not be as tolerant of the mechanisms for for dealing with single points of failure as Cattle are and so it's this is not that they are bad They are they were designed with a generation of architecture that existed prior to what the current gen is People have been developing applications You know in various different schools over the last 25 30 40 50 years and these applications Have the architectural schools of developing these applications have moved on and so as as we start looking at these Some of these are applications that have been continuously maintained inside of the enterprise They still offer a supreme level of criticality for the enterprise and so there there's this principle of do no harm The art and you don't want a significant rearchitecture of an application if it's servicing a critical workload And and these applications don't just exist within the enterprise they also exist within the carrier space Within the service provider space So every or every audience has its own set of pets that is trying to maintain So more heavily managed workloads Happening in a variety of dimensions. We're going to talk about these dimensions throughout the presentation But I would posit that there are storage-centric workloads So we have Oracle Partnering with us on this presentation and obviously it's it's a pet breeder, right? No, no, no, not pejorative like that in a pejorative But then you also have network-centric workloads. So how many of you guys are participating in NFV working groups or working around NFV topics So obviously the network can be the source of pets as well Storage can be the source of pets network can be the source of pets I'm not sure about compute, but I want to fill that in so if anybody has any great examples of how compute is the breeder of Pets and that would be great So let's talk about pets and cattle. So So pets are born Because you need to service a workload you need to buy some hardware and You're going to buy that hardware in a very specialized way around that workload and You're going to rack and stack that hardware and that be and that is the beginning. That's the birth of the pet Right You install the servers you configure them you deploy and test all of these infrastructures are supremely specialized around The pet so the pet is not just the application The pet is the infrastructure to host the application The pet is all of the surrounding accoutrements that go I'm practicing my French they go along with That that application that make that application able to service the need that the application was designed for And then you have the ongoing goo, let's call it technical term Around the pet you have to buy bedding for the pet you have to feed the pet you have to walk the pet you have to pet the pet You have care and feeding that goes along with the pet You have to you have to manage the pet you have to monitor the pet you have to examine faults in the pet You have to understand when those faults have occurred respond to those faults very quickly Because this is a pet and you don't want the pet to die I prefer to call it again a highly managed workload. So this is highly managed by definition So failure in any component of the pet and I would argue that some pets are tolerant or some Highly managed workloads are more tolerant of failure in some components than others But this again is a specialized problem. So you have to understand the nature of the pet and you have to respond to the failures within the pet so anatomy of the birth of a cow or anatomy of a cow So or cattle depending on your perspective or or lightly managed workload, which I kind of prefer So you start with a workload you don't start with hardware You don't really care about hardware. You don't really care about infrastructure In fact, you don't really care about much of anything other than the application itself So this begins with a workload. So the workload is the birth of a cat of cattle and it's deployed across a whole slew of virtual infrastructure and It's deployed with very little dependence on underlying hardware and it's deployed with very little dependence on state So the cattle exist Without any dependency on the underlying infrastructure the cat and this is a this is a very well architected cow Okay, so bear with me on this They they have no dependency on state. They have no dependency on storage. They have no dependency on network They're just there if they fail You replace it you replace it with another instance and you resume Ideally, these are scale out.  So So cattle so lightly managed workloads everybody how many of you guys are transitioning enterprise workloads to OpenStack today Two people Am I in the right session? Is this the right? Oh, okay. Just checking. So So Two of you are transitioning enterprise workloads to OpenStack. That's awesome. You're probably dealing with You know, you're probably doing a lot of introspection right now You're probably looking deep into your soul and thinking is this really What I want to do with my life Probably thinking where did I go wrong? I have this thing.  Am I pretty accurate? We've all been there. Okay. It's a dark time. We're gonna see you through it because guess what happens The thing that you have is perfectly acceptable We accept you We accept your thing The there's nothing wrong with having a pet In fact, if you didn't have a pet, then you probably wouldn't have a business So we we want to support that and there are a variety of ways that we can So and you're gonna have these things for a long time because in the future You know, most people envision a future of nothing but cattle But pets are essential Highly managed workloads will always always exist. There will always be scarcity There will always be management required for these workloads You will always have to have some degree of infrastructure capability specialization because that's where performance comes from That's where capability comes from if you could deploy on any generation of processor any vendor of processor any vendor of network any Capability of network then that means that you're targeting say it with me lowest common denominator and Guess what comes from the lowest common denominator? Poor performance So you will always have various levels of management Associated with these workloads and that's not a bad thing The bad thing is whenever you have a dependency on something that doesn't exist in the system And that's the reason that we have Nigel talking about when the enterprise and the work that's being done there And that we have the rest of the presentation, which is far more important. So I'm going to continue So meanwhile back at the enterprise Clouds are forming right people are deploying clouds because clouds cool Clouds a new resourcing model clouds a new management model cloud represents a tremendous advantage to the enterprise Cloud represents the ability to fulfill business drivers for compute in new ways and address concerns that exist within servicing those types of business drivers, and so many enterprises have and will deploy Open stack and this is important Because it allows them to fulfill their business objectives and as they continue to grow They get all the benefits that open stack brings Elasticity scale all the benefits of the hard work that's being done within the community and they decouple their applications from their supporting infrastructure You want to take this? Yeah, sure. All right. I'm gonna hand it off to Eric because you're probably bored with me anyway No, no, thanks Mike No, I think I'm okay.  I sense it there you go. Okay, so to recap I think I think the position that we're seeing as we talk with a lot of enterprise customers sort of They're sort of caught between the promise and the interest of moving towards cloud and all the all of the benefits They see with cloud all of the agility benefits the ability to scale up And to have more of a centralized self-service infrastructure But at the same time they're sort of asking these questions, you know I've got you know the vast majority or some key subset of the workloads that I run in my enterprise Are pets and so what am I supposed to do? What's my migration path forward right and you know per the slide that Mike just talked about there's sort of the question of well Yeah, so should I be looking at taking my pet application and you know try to try to sprinkle some kitty dust on it And somehow form it into into cattle over time or look at look at rearchitecting it Is that something that's possible and you know in some cases it might be But you know this is this is kind of similar to What I think you know it's similar to sort of trend of you know where years ago the vast majority of applications We're all single-threaded and with the rise of multi-core and multi-threading You know you want to sprinkle on the multi-threaded dust and all of a sudden get some concurrency out of your application And that's hard to do in many cases you have to sort of rearchitect the application in a very fundamental way In order to do that and you know as Mike was mentioning there's a lot more to Pets and cattle than just the workload itself There's the infrastructure that's also sort of been designed or baked in when when considering and conceiving the pet So it's difficult. So I think that you know, there's one of two things here either You know as this plays out in the future You know either it will happen over time and folks will be successful with taking you know the applications that are implemented with pets and Being able to re-implement and re-architect those and as cattle and I can I can believe for a some Some set of workloads that will actually happen or maybe for some it won't ever happen, but in either case It's gonna take time So, you know, this is really kind of the crux of this presentation Which is you know really sort of putting forth the notion that it's not just pets or cattle It's both And both pets and catables sort of need to be brought into scope here for for open stack so years ago the matrix I Reminded of this scene the wisdom of the the young boy as he's talking to neo and for whatever reason I got to be thinking about this and You know, it's sort of you know answering this question around the conventional wisdom Okay, well if I can't re-architect my pet can I go ahead and move my pet into the cloud? And so to the the conventional of the wisdom around this today seems to go Something like this, you know, do not try to I won't do the the little accent But I'll at least try to say this as best I can do not try to run your pet reliably on cloud Infrastructure as a service that's impossible instead Only try to realize the truth. There is no reliable infrastructure as a service Then you'll see that it's not the cloud that needs to be reliable. It's only your pet And this this seems to be The belief that a lot of folks abide by now they just sort of okay. Yeah cloud is this way, right? It's a sort of this Unreliable infrastructure or it's this rely it's this infrastructure That exists and it's it's great for cattle and it's perfect for scaling out, but it's not really a suitable home for For my pet, but I think the thing that we would say Is What if we told you we can build a better cloud infrastructure so that pets can be managed to and Mike makes the point that you know what we're in a lot of cases what we're talking about our our SLAs some Applications have more SLA needs Than others, you know pets having more and cattle having less So this was this was also spoken to at the Atlanta summit Toby Ford from AT&T got up on stage And you know this was acknowledged in his talk You know and very clearly, you know, Toby was mentioning about how They've been one of the the leading enterprise customers that's been making a lot of progress towards Moving towards cloud adoption in the enterprise But they sort of acknowledge You know the one thing that he was really worried about when talking about open stack and the open stack ecosystem is That the scope is too narrow. It's not just really about cattle applications You know Toby says the pets have to be handled and they have to be managed and open stack really needs to bring pets Into scope more clearly So I'm gonna hand it over to to Nigel This really is a tag team episode here So I want to talk a little bit about when the enterprise how many people have heard about this this initiative within the Within the foundation some people have so let me give you a little bit of history on this part of what the open stack board does is Survey users of open stack and so Tim Bello soon publishes a six-monthly Survey and gets back comments about what the structure of folks clouds are What they're doing in the clouds and and more importantly comments about their clouds and about Open stack and the work that the community does and and based upon that feedback the the open stack board met and realized that they needed to kick off a initiative to look at the gaps that were Basically limiting enterprises from adopting but the community work and so this was kicked off in the Atlanta summit and Since then there has been a lot of work going on with a lot of people from a lot of companies looking at the feedback looking at sort of maybe anecdotes from their use of the cloud within their organizational or for their customers and and and sort of getting to a curated list of Here are some top issues that we really need to fix if we want to Accelerate the adoption of Open stack into the enterprise The the work groups have got sort of split off into a whole lot of application areas and as a result of those Those working sessions. There's a series of blueprints that have been proposed for kilo They're being discussed in the design summits over the next few days as well as some things sort of crept into Juneau as well There are sort of demos at various booths of some of the blueprint proposals which are aimed aimed at making Open stack more amenable to enterprise adoption and in those areas. There's a lot of items which sort of cover this this pets pets initiative The demos by the way, I'll give a slight plug here I am from Intel if you come to the Intel booth a number of the items here You'll see you can see demonstrations of those blueprints and some of the things that are being proposed at the summit here is a list and It's not so much of an eye chart but When you get the slides you can search for all these blueprints if you're interested in Both the topic areas and the proposals from various teams and how to address the problems that have been highlighted and you know if you look at Some of these areas you can also see things that were Mentioned in the keynotes either yesterday or today So I remember if you remember the time Warner presentation and the BMW presentation about Live migration of a VM with a volume components about live upgrade And and you know these and VM availability these components are areas that really Scored highly in some of the surveys that were sent out and people are looking specifically at an effort within the community to sort of solve these problems to get to a you know a new More stable more enterprise friendly Infrastructure and one that then is suitable for running both pets and cattle So, you know, I'm gonna sort of wrap up here We have time for a little bit more in terms of questions from folks So I want to just really recap about this You know if you if you want to build a solid house You build upon a rock and so the infrastructure and the infrastructure that you design for your cloud needs to be Needs to be a good one and in fact if you look at The the large public cloud providers and their infrastructures. They're actually very well designed actually use high-end components because what they're trying to do is get extreme density extreme performance And in fact, it's those same architectures which are also able to run those scale-up applications the carriers are Have quite demanding service level requirements as they look at the infrastructure They need to support they came back with these same sorts of things that actually really the enterprises have been saying as well You know, how do you upgrade? You know, what am I going to do? I have a firmware patch. How do I drain a machine to do that patch? Without disrupting everything in the system the same requirements coming back again and again From a compute perspective, there's a variety of different hypervisor models that are available KVM is great So is VMware. So is hyper V. So is Solaris They are all perfectly valid hypervisor choices that we need to support and and Which are being supported down the community to put to keep Enterprise workloads running happily and transitioning easily and then high availability is really about In my mind having an infrastructure which is a minimal to To common maintenance operations maintenance is the biggest cause of failure of an application And so if you can't maintain your infrastructure in a way without killing your cloud for six hours Then you know, you haven't got a cloud. That's really suitable for anything So that's our presentation Maybe Filling blinded by this light here If there's some questions of the people have to ask now we can jointly try to field them You guys are too kind.  So the question is for The assumptions stated in the slides was that cattle are largely stateless and How does it relate to? To applications that are dependent on new types of state Like those delivered through trove and other services like it. So the question further stated is When you have state state based applications applications that are relying on state are they pets or can they be cattle? and what I would argue is that pets and cattle are is a binary concept and That there is no cattle There is no notion of a cow and there is no notion of a pet that they exist in a continuum and That state is one of the factors that causes a workload to be highly managed And that concept has been socialized as a pet and So pets don't just come from state But they come from a lot of different factors. They come from dependence on hardware They come from dependence on other applications. They come from dependence on State they come from dependence on storage and all of these all of these Dependencies in aggregate are the definition of a pet Because the more dependencies that you have the more management you have to maintain the workload and so so I'm I I Agree with your point that state can move around But the notion of state the the requirement to have context Is a is a it creates a dependency which creates a management activity? Go ahead Want the microphone? Can you hear me? Yeah, so what about the idea that each? Applicates Applications that are suited for one type of hardware environment should remain there so an airline system that was built on the mainframe maybe is best run on mainframe and ERP SAP or Oracle is best suited for physical servers and maybe virtualized and Email and other three tier applications could be virtualized on a virtual You know VMware Zen KVM platform, but the new Open stack is designed for status cloud applications like streaming like Netflix like and Each yeah, you you you see here in Paris a small a small Economy car is where suited for the traffic in the parking, but if you want to drive down to the coast You may want something comfortable or a comfortable bus I think I think one of the I think one of the points of the presentation And I think we're seeing this with open stack, and I think this is one of the things that's Really quite appealing about open stack is its flexibility in enabling cloud deployers to Deploy a choice or a different mix of different technologies within the cloud itself And I could see it being a totally viable path where if you have a particular pet that has A particular need around infrastructure Being able to leverage the heterogeneous support that open stack offers for systems and virtualization To be able to take that system and bring that in the fold of the cloud, right? because I think I think that's sort of the the the false choice that so often exists which is you know either Either I can have the benefits of cloud infrastructure Or I can you know have my workload and have it have to sit outside of the cloud and not be managed And I think that you know as The open stack ecosystem enriches and grows and has support for a more diverse set of virtualization and system technologies The chances are going to be increasingly good that for a wider variety of enterprise deployed Applications that open stack will be able to manage those as well. I agree. Yeah, absolutely Thank you for coming guys. We really appreciate it. Yep. Thank you


Dominic Dawes show, I'm Joe Wombo, joined now with Ice Hockey head coach Dominic Dawes and coach. Two different types of games this week. One, first of all, the thriller and overtime on Friday night over Elmira. Yeah, no, I mean, Friday night was a great night, but we talked going into the game of we wanted to win our first league game and kind of get that get that monkey off our back and guys showed up, battled hard, hung with it. I thought got our heels a little bit late in the game, but I think we showed a lot of character and battled through it and you know, had a couple kind of bad beats in the game score or really score on yourself too often. But I think the guys handled it, handled it well, head on the highs and lows and got through it. We came away with two points. That's one of the interesting things about hockey is like that play is so rare, but it does happen. And then being able to bounce back and get that game time winner late in the game and overtime. I think it was it was huge. I think it was a big, a big step forward for us to know that we could, you know, handle some adversity and get through it and, you know, kind of come away with the with the win. And speaking of adversity throughout the game on Saturday with Hobart, a ranked team on your second conference game, you know, they it was a different type of game and guys spend a little quite a bit of time in the penalty box with that mentality. Yeah, I think as a whole, we played a much better game on on Saturday, except with the exception of the penalties. I think we were a little bit on disciplined at times and, you know, kind of flipped to the opposite of what we did Friday, kind of weren't able to handle it mentally. As the game went on, got a little, you know, just got lost, got lost in it and couldn't hang with it and took some some bad penalties or selfish penalties late. And that's what ended up ultimately. You know, it's a chance. I would argue that the game was, you know, called fairly, you know, they had their fair share of penalties. So you can't. Oh, absolutely. I mean, we, hey, we, I think they were two for 11 and we were, we were 0 for seven. So they definitely won the special teams battle and they won 3-1. That's the difference in the game. And we had our opportunity. So we had a couple of posts in there. We had quite a few quality chances late in the game and just, hey, that's gonna happen sometimes.  That's, that's the nature of the game, but you got to be able to hang with it and, you know, at least give yourself a chance to win. And I think that's what we didn't do. Right. You talked a little bit about, you know, our maturity level in your post-game interview after that game. Now that may change. Your experiences are gonna change this weekend on going on a trip on a road trip. Yeah. So this will be a good, good weekend.  In our sport, the guys usually love being on the, being on the road, being on the bus. So it'll be fun. But it'll also be a good, good challenge for us. Nazareth, Utica, both, you know, tough places to play. We're kind of still in that mode of creating some rivalries here within our, within our league. So it'll be a good chance for us. Is that what you're expecting? Some sort of rivalry or big crowds like we've been seeing here to see them on the road there?  So it should be a fun atmosphere for our guys to, you know, experience and be part of. Goals go in there and win. Yep. Well, we wish you the best of luck on these trips and we'll talk to you next week. Awesome. Thank you. He's Dominic Dawes. I'm Joe Wamban. This has been the Dominic Dawes Show.


Host an all opinion moment in bow. Hello people of the internet. My name is Johnny and welcome back to another tier list video I say welcome back, but we haven't properly done a tier list video I had a look back on the channel and we did that bracket fight with the fnaf characters to determine which one was my favorite But we've never actually done a tier list video of course this all changes today And eventually sometime in the future when the which fnaf game is the best one in the worst video comes out Which I mean who knows what's going on with that video am I right boys? Help me videos doing fine. I just need a bit more time to work on it because I've been lazy And I don't like the way I'm making it so far anyways getting back to this video because we are not going to have skins for a Little bit in fnaf AR. I thought now would be a perfect time to make a tier list for which ones I think look the best handle the best in game and other factors that we will get to later Keep in mind. This is all my opinion for some reason people are still like oh, why would you put that person at the bottom tier? They're clearly the best that's your opinion. You know what good for you. You think they're good. That's great I don't I tweeted earlier today that I was going to be making this video and I asked for your guys's opinion on these characters So I tweeted out the poll I tweeted out the tealess and you guys have some opinions that I don't agree with But I didn't reply to you guys like oh wow you think so-and-so character is better than this character How stupid of you I didn't do that because it's your guys's opinion I know I'm on this for a long time But for some reason people don't understand that other people think differently than you anyways So I have all of the skins from the first one which is Shamrock Freddy all the way up to the most recent one which is flaming spring trap pretty frost bear and a baby Are not on this list because they are not actually skins there for some reason characters So how about this let's not waste any more time And this is the tier list as you can see it goes from SS all the way down to F Should probably change that to double S because otherwise some people might think that means something that it definitely does not Yeah, I tried changing it and it doesn't work So we're just gonna go with that and I had these guys ordered from oh my god earliest to most recent but I guess they changed there you go So as you can see we have Shamrock Freddy chocolate Bonnie Easter Bonnie VR toy Freddy high score toy Chica system Aero toy Bonnie radioactive foxy toxic spring trap Firework Freddy. I think that's his name Liberty Chica flamethrower bear endo Broiler baby scorching Chica and flaming spring trap. Those are all the skins. We have as of August 16th 2020 so again, let's not waste any more time and let's get tier listing. So Shamrock Freddy I actually really like this guy. I don't know why maybe because he is the first skin But I really do like him. I don't think he's I don't think he's SST. I don't think he's S tier He's probably around maybe an A or B for me And I will after I put everyone up on the tier list go go on and change it up a bit afterwards But for right now, I'm putting him at a solid B. I think he's nice. I like the green I like the gold microphone. I like the gold chains overall I just think he's a very cool character even though his design is so simple chocolate Bonnie I like this guy too. I think out of these two Bonnie skins chocolate Bonnie is my favorite So don't at me. I really again. I really do like him. I will say it was only up until after Maybe maybe this guy radioactive Foxy that they had their own custom animations in the workshop But you know even without the new animation chocolate Bonnie still really cool I like I just like his overall idea and it might be me because I do like getting chocolate on Easter day But I really do like that he has a bite taken out of him. I like his new buttons I like his eyes his picnose all that stuff. So honestly, I'm kind of feeling an S All right now I know you guys probably gonna hate me for that but then again It is my opinion and I will change this afterwards, but I really like chocolate Bonnie Easter Bonnie is all right I don't think I like I definitely don't like him more than chocolate Bonnie. Maybe I might not like him more than Shammy I call him Shammy by the way if you're new Easter Bonnie. He's nice Again, I mean there's nothing really new with him. It's kind of like a white chocolate Bonnie You could say without the chocolate texture. I'm not sure what they were going with Easter Bonnie If I'm being honest, I know he says like happy Easter happy Eater on his tag right here But overall, it's like what were they trying to do with him now the arcade may may hamskins I thoroughly enjoyed these guys. I really do Especially toy Bonnie, I mean Toy Freddy and Torchica because they have their two Separate skins right you have VR Toy Freddy and then I honestly have no clue what this guy is called I know for Torchica. It's high score Torchica and then game over Torchica So if you guys know what this guy's called tell me in the comments But it's definitely gonna be a or more by the way if Frostbear was on here He'd be going in SS. I mean clearly a bit baby. I don't know where I would put her Maybe like a solid a or s I do really like her but because they're not skins They're not on the list. So going back to VR Toy Freddy. I do I do like him. I really do like him So probably probably a for now. I might again I'm definitely gonna come back and change him high score and game over Torchica Hmm. I feel like she's she's on the same level as VR Toy Freddy Maybe because she has the 8-bit cupcake and again the two skins So I'm probably gonna for now put her at a a Ranking along with VR Toy Freddy and I know I'm going pretty fast at the start But trust me I got a lot more to talk about when we come to the later characters Then also when I rearrange the list. So system era toy Bonnie. I definitely do like him I like his design. I like the particles that come off of him But honestly, I don't think I like him as much as these two his design is cool I get what they were going for but I don't know man. He doesn't have those two skins So I'm probably gonna put him along with Shamrock Freddy probably a little bit behind Shammy again, I'll probably go back and rearrange that because I have a feeling not many people are gonna like having Shammy ahead of System era fricking toy Bonnie. So radioactive foxy. All right, this guy. This guy is interesting because This this guy, right? I don't get the appeal for him Same thing with like toxic springtrap and flaming springtrap, but we'll get to those guys later I don't get why so many people like this skin. The only thing I like about it is that he has two hooks other than that It's just green glowing foxy. I definitely do like a more than Easter Bonnie I don't think I like a more than system era toy Bonnie. Do I maybe I do maybe I just have a thing for green characters, right? Yeah, maybe maybe even a bit more than Shamrock Freddy I might put him in a B tier for now. So toxic springtrap again I saw this on so many people's tier list as being like up near the S's At least in a but honestly Honestly, again, just like radioactive foxy. I don't see the appeal, right? It's just springtrap with some purple goo and guts all over him.  I don't think many people were I don't think many people were expecting a fourth of July skin But when they came out it was like, okay, sure. I guess they're here firework Freddy Weird character very very strange character. I definitely love the rocket and how he's charging at you With it. I love that his animations cool to how he like flicks his sunglasses up and down so That alone is probably gonna put them Maybe definitely in a B tier probably I probably I should probably move these guys up a bit But I'll save that for later. So for now. I'm gonna put them I'm gonna put them ahead of radioactive foxy again for now I know what keeps saying well put this guy here for now and then later I'll come back and change it but it's because I have to constantly remind you guys so I can stop you from going Oh, man, you put that character there. I'm like just hold up cuz I'm not done Hopefully you guys understand because when people make tier list videos The viewers and the commenters just go absolutely nuts. Be patient. This is just my initial pick So Liberty Chica is up next and I think again another interesting character because it's part of the fourth of July event Nobody saw that coming So Liberty Chica is nice. I like the cupcake. I like the um the I know it's not worst. It's like carbon It's it's oxidized copper not carbon Okay, so yeah, I like that I like how they have the the plaque with the fourth of July thing on it blaming color the cupcake though That's gotta be my favorite thing about this entire skin I think it's up there. I think it's definitely up there I I'm having a lot of B characters right now and again I gotta go back and change that but I think for now. I will put the I'll put them right here for now Again, there's a lot of green characters in that area So now I move on to the most recent event in the game And that is the sizzling summer event with the flamethrower bear endo broiler baby scorching chica and Flaming springtrap. I was like no, there's gotta be more creative name, but no, that's it So flamethrower bear endo, I know not many people are going to agree with me on this but personally Like he's up there. He is so fricking cool, and I don't think he gets enough credit I love the fact that they turned the endo skeleton into a welder with a flamethrower And he's got like the the welder helmet on too Honestly, it's so cool. Now my main problem with this Recent event the sizzling summer event is the fact that Fire particles just don't work with this came right when you're in the actual AR section and you're hunting for them on your phone Like flame particles don't show up Because of like optimization for certain phones and like technical stuff like that So that's my least favorite thing about these new four characters and we're gonna get to these two in a little bit trust me But yeah in the workshop.  I like her. Okay, definitely not as much as Flame thrower bear endo, but she definitely is up there. Honestly. I think I Mean I put her here just so I could talk about this guy But I think the a cat go is a good place for her whether she's in front of these two skins for your toy Freddy in high school Toy Chica, I don't really know because as cool as these two characters are They don't have that they don't have the sorry about that. I got distracted.  I'm gonna put her there But again these two like broiler baby and endo one flame thrower dude.  They're just the characters on fire. All right I mean I put them this way for a reason.  They're literally just the character on fire. Maybe I'll put them ahead of these guys, but like Really the only thing I like about them is their workshop animation Right what they look like in the workshop because really that's that's the best place to view these four new characters Is because the particle fire effects can actually appear in the workshop Also, they have their custom animations, which I love for all four of these so I'm gonna do a little bit of rearranging First off, let's start with these guys So SS is like is like the top tier what I really want them to keep doing and if I had to if I had to pick Honestly, I know you guys gonna make fun of me, right?  I Might I can't I might keep him at a s. I might keep him there. I think he's good. I definitely do like him a lot Is he better than Endo?   Are you kidding me? What is wrong with me? Whatever. It's my opinion. Um, these guys I'm probably gonna keep here Yeah, so moving on to the B tier might move system arrow Bonnie up a bit Thinking about it now. This guy's not all that good. Shammy. I love you, man Put you put you here. I don't think I'm gonna put anyone in the F tier Because truly I don't think any of them are terrible skins that Illumix should regret making I think they they're all good in their own way So again going back to these Firework Friday. I like I like you Yes, okay, I'm fine with I'm fine with be Coy moving on to see I think I think I'm good here. Yeah, so I'm pretty sure this is my final kill list Okay, I know people are gonna make fun of me so hard for having Endo or one up there But I think that this is it and maybe my opinion will change the more care the more skins we get for characters We all know that lefties coming out very very soon He's coming out the very end of August the final week of August So he's probably gonna have some skin So we're gonna have to check those out see where they go on the tier list Maybe later this year I'll come back and I'll update it if they keep releasing skins I don't know if they're gonna go back to releasing one every week. I wouldn't want them to do that I'd rather them stick to making characters even if we have to wait like two months. I'm fine with that I think skins are a good addition You know, they definitely kept us occupied during during the pandemic as Illumix was walking from their house I do appreciate skins I'm also making this video to show you guys that as much as I crap on FNAF AR right as much as I say Oh my god, this game is terrible. Illumix. What are you doing? I do love I do love the game and in a certain way in a very Very specific way. I love the game and I do really really do appreciate Illumix again I know I give them a lot of crap for a lot of stuff that they do with the game Prices skins all that stuff. I definitely do love them.  I definitely do still love it So that's another reason why I made this video to show even though I crap on the game I definitely do still love it. I love the people walking on it and I definitely do still love its content So again, this is my tealess. You cannot agree with me. That is completely fine. Leave a dislike on the video See if I care. I will leave it linked down below. I created this tealess myself So if you want to go make your own tealess, you can tweet them at me at Johnny blocks on Twitter again I tweeted out early on seeing your guys as tealess has been really really interesting All right, maybe we can have a talk in the comment section like why would you put this character here? I'm just kidding. I completely respect all your guys's opinions. Hopefully you respect mine. You listen. So yeah, that's it for me Thanks for watching. I'll see you all on the flip side. Goodbye


What's up, everybody? Ricky Caruth here. Welcome back to my channel. Today I want to talk about what my favorite follow-up line is. This is if you're in a situation where you might have had to follow up with someone, but you don't quite know where to go from here. You don't know exactly what to say. Maybe you showed property to this buyer Saturday, and maybe it's Tuesday or Wednesday. You haven't heard back. You don't really know which direction to go in. So that's what I want to talk about these kind of situations. I want to give you my favorite line that I use as kind of a way, a reason, if you will, to call them and to keep that conversation going and to literally find out where they stand and where we're going from here. I like to use this anytime. It can be used in so many different situations, so I think you're really going to like this. It's going to take the edge off. It's going to take the pressure off of you of how do I follow up? What's a good line we can use? What's a good reason to call someone back and kind of ask them what's going on? Or, you know, how can we do this to where it doesn't feel awkward? And how can we do this in a way that it makes them feel like we're providing a service to them? That we're providing value to them. That we care about them. That we want the best for them. All the things that I preach about in my coaching program on this YouTube channel and the way I live my life. This doesn't have to be one of those awkward situations where you don't know kind of what's going on. It could be something that you know what's going on. Are you sending email and you're supposed to follow up and you know exactly what's going on. So it doesn't have to be one of those confusing moments. It could be used both ways. Okay, so the line that I like to use, I'll call the prospect back. Let's just say a scenario here. I've showed property. Maybe it's a couple days later. All right, I don't really know what's going on. They said that they were really interested. They hadn't really got back. You know, I sent them a couple of messages. They haven't responded. So now I'm thinking, what's going on here?  I'm going to go through my script. You know, hey, it's Ricky. How are you doing? Yeah, I'm enjoying the day. Isn't it gorgeous? You know, look, I don't want to take it too much of your time, but you know, I showed you some houses or whatever the case was and I just wanted to make sure I wasn't leaving you hanging in any kind of way. I love that right there. I just wanted to make sure that I'm not leaving you hanging with anything, or if there wasn't anything that I was supposed to do. I've used this so many times and it works like a charm to keep the conversation going and figure out where they stand on the situation. I've even used this with, you know, agents. I've used this with developers. I've used this with buyers, with sellers, with everybody. It's just a good way to follow up and say, look, I don't know how we left it. I can't remember what was what or if I was supposed to do something or you were supposed to, but I just wanted to make sure I wasn't leaving you hanging or that you weren't waiting on me for anything in particular, if there was anything that I needed to do for you. And you may be in a situation where you might have forgotten if there was anything you were supposed to do or you might know that there's really nothing that you were supposed to do. However, now that some time has went by, there may be some things. The buyer may say, yes, actually, could you look up properties in this other price range with this other criteria, this other size house, this waterfront. We want to look at things in a different criteria. Okay, boom.  I just want to make sure I'm not leaving you hanging on anything. Well, no, but now that you're here, now that you're mentioning it, you know, I think we're ready to pull the trigger. We're ready to put this condo, this house, it's a lot on the market. So this is my favorite line. It really creates some engagement. It gives you a real reason to call someone and genuinely ask them, is there anything else I can do for you? So I hope this helps. I wanted to share this with you. I've been using it for years. I don't think I've ever actually set it on a video or in my coaching program or anything.   Let me know if there's anything in the world I can do for you. Comment below, like this video and we'll see you on the next one. Let's go.


Okay, so I'll be speaking about our paper measure rewind measure tighter quantum random oracle model proofs for one way to hiding and CCA security. The authors are Veronica Kuchta, Amin Saxad, Damien Steele, Ron Steinfeld and Sifeng Sun. We are all from faculty of IT Monash University Australia except for Damien Steele who is from ENS Leon in France. So I'll be talking about the Fujisaki Okamoto transform and its security in the quantum random oracle model and the core technique behind such proofs is the one way to hiding lemma and I'll talk about prior work that used a query-based secret extraction technique which suffers from a square root advantage loss limitation and I'll explain the origins the quantum origins behind it and then I'll introduce our new technique called measure rewind measure or MRM for the one way to hiding lemma which is based on a measurement based secret extraction technique and I'll summarize our new one way to hiding lemma that avoids the square root loss in the tightness of the reduction and then I'll apply our tighter one way to hiding lemma to the Fujisaki Okamoto cure on proof without square root loss and I'll conclude with some open problems. So the Fujisaki Okamoto or FO transform is very commonly used in practice for transforming public encryption schemes that are secure against chosen plaintext or CPA attacks into more secure schemes that are secure against chosen ciphertext attacks or CCA and this technique this transformation is very commonly used in the for example the NIST post-quantum cryptography competition for strengthening the security of public encryption schemes. Now we will focus on the FO perp knot scheme which uses two hash functions h and h prime that are modeled as random oracles. The function h prime is used to make the scheme deterministic so the original scheme is randomized but the new scheme has its randomness derived from the message by hashing with the function h prime in order to make it deterministic. So this is the T transform part of the FO transform and there is another transform called U which derives an encapsulated key k as the hash of the message in the ciphertext using the function random function h. So this is used to make a key encapsulation mechanism as the result of the FO transform where the encapsulated key k or the encrypted key k is the encrypted value and we're going to be assuming certain assumptions on the underlying CPA secure public key scheme that I'll mention later on. So security proofs in the quantum random oracle model or QROM they model the access of the adversary to these hash functions used in the FO transform as queries to a quantum oracle that will denote by UO that given an input states that encodes the input x to the function produces an output quantum state that encodes the output of the function or O of x at this point and in the quantum model attackers can query super positions of inputs lots of x's to the oracle and get an output which is a superposition of the corresponding evaluations of the oracle at those inputs. So they are potentially so this model is potentially much more powerful than the classical random oracle model and it's such a model arises against quantum attacks because quantum attackers can implement the hash function as a quantum circuit and now these kind of quantum random oracle model attackers can be modeled as a sequence of steps denoted by a sub i where a sub i is the ice part of the attack that outputs the ice query to the oracle and this is followed by the application of the oracle so that overall after n such queries there is a final measurement M produced done by the attacker in order to produce its output. Now in prior security proofs of the Fujisaki Okamoto transform in the quorum the results that were obtained were of this form so the advantage of any attack against the CCA security of the FO transform scheme was upper bounded by the square root of the advantage of attacks against the CPA security of the underlying original scheme and there was also a square root of Q multiplicity factor in this security proof reductions where Q is the number of queries of the oracle. So this is not a tight reduction especially because of that square root which leaves the possibility that CCA secure that FO schemes are much less secure in terms of CCA security than the corresponding CPA security of the original scheme. Now in our work we have we show the first security proof for Fujisaki Okamoto where we avoid this square root loss in the advantage so we show that the advantage of a CCA attacker against the FO scheme is at most Q squared times the advantage of the CPA attacker so although we don't have the square root we do pay a bit in the multiplicative cost which is now Q squared. Now the the core tool in CCA proofs for the Fujisaki Okamoto transform in the quantum random oracle model is the so-called one way to hiding lemma and this lemma essentially argues allows us to argue that if any if an attacker can distinguish the encapsulated key K from a random key then there exists another attacker called the extractor that can extract the secret that is that was hashed from such an attacker and the way it's formulated in the Q in the Q-ROM in the quantum random oracle model is by a game like this so this is the one way to hiding game introduced by Unruh in 2014 so here the distinguisher A is given an oracle O that is either H or G now H and G are both random functions but they differ only at one point X star which is that secret point at that point they output independent values Y H and Y G and so what the one way to hiding lemma tries to show is that given any distinguisher A that can distinguish whether it's given being given access to the oracle H or to the oracle G there exists an extractor algorithm B that using the distinguisher A can extract the secret X star with a significant probability so that's the advantage of B is the probability that B can extract this X star and therefore contradict the one wayness of the original encryption scheme that encrypts X star now the original strategy for doing this extraction in used by Unruh was what I call the query based extraction method and in fact all subsequent work until ours use this approach and the approach is in order to extract the secret X star from a distinguisher that distinguishes the hash of X star from random the idea is to just measure a random query of the distinguisher A and hope that since one of these queries should contain X star in some sense that the result of this measurement of the queries will give X star and what the Unruh was able to show using this extraction query based extraction method is that the advantage of any distinguisher A is bounded by the square root of the advantage of this query based extractor B up to a multiplicity factor of Q the number of queries of A now subsequent work culminating in Dindal et al last year removed this factor of Q but still left the square root on the advantage of the extractor and so it's still far from being a tight reduction now last year there was a paper by a Jiang et al that asked the question about whether this kind of square root advantage loss is inevitable in such query based extraction and what they proved is in fact a kind of impossibility result that says yes it is in fact unavoidable if you use query based extraction to have a square root loss and what they showed in fact is that there is a quantum distinguisher A that achieves a square root advantage in terms of the advantage of the query based extractor and so it's impossible to remove that square root if you use a query based extraction now in this paper our main observation is that if we look more closely into that square root distinguisher we can it suggests in fact another way to do extraction of the secret from a this from such a distinguisher that can circumvent that square root loss and we call this idea a measurement based extractor because instead of extracting the secret from the queries that the distinguisher makes to the oracle it extracts the secret from the measurements the quantum measurements that the distinguisher makes so let's see in order to see how this works we'll review Jiang et al's distinguisher this optimal distinguisher that achieves the square root advantage now what that distinguisher does is it queries a superposition of input to the oracle and it gives each of these some amplitude that will denote by square root of px prime so the the secret x star has an amplitude of square root of px star and if we measure using the query based extraction if we measure this input register in this state we'll get x star we'll get the secret x star with probability px star so assume that this extraction probability is very small and we want to extract it with a much higher probability of square root of px star or so or even higher so what we do is in the case of this distinguisher the response of the oracle is going to be either psi h or psi g now the psi h is the state where the output corresponding to x star is the output of h and psi g is where it is the output of g now to distinguish whether the oracle is h or g what this distinguisher does is it makes a measurement called a projective measurement with respect to some measurement vector v and v is chosen as a vector in the span of psi h and psi g at an angle of 45 degrees from psi h and at the end of this measurement the distinguisher will return one with probability that is effectively the squared length of the projection of the state along the measurement vector v so let's see how the geometry looks like of this situation we have in in blue the psi g and in red the psi h you can see that the angle between them theta is in the order of square root of px star now if the attacker makes the its projective measurement on v which is shown in purple here the projections of psi h and psi g are shown by the dotted lines and if we square those projection projected lengths we get a difference between the squares that is indeed a square root of px star up to a constant and so we can see that the attack this distinguisher using this purple vector v can achieve a square root advantage now our observation is that in fact in order is that in order to make such a high advantage distinguishing measurement the attacker effectively has to know the secret x star in order to make such a measurement and in the following sense that if we if we somehow make the system go into the state v the projection the measurement vector then if we measure the input register to the oracle in the state v in fact what we get is the secret x star with probability close to a half so basically the measurement vector itself reveals the secret x star now how do we get the state of the system to be v that's our second observation is that in fact if we just let the attacker perform its measurement with respect to v then after this measurement of the attacker the state of the system collapses to v that's the collapsing property of quantum measurements and so by doing this we can transform the system state to be v and it happens also with a high probability of about a half so what we end up with is our measurement based extraction algorithm shown here which first runs the attacker to output its oracle query then we process this query with the oracle g it transforms the state to psi g then we let the attacker perform its projective measurement with respect to v which collapses the state to v with with high probability and finally we we measure the input register in the state v and it it gives us the secret x star with again a high probability so overall this extraction this measurement based extraction succeeds with a high probability of one quarter now in fact the attacker that performs this this projective measurement with respect to v because v is not a so-called computational basis vector this attacker has to implement that measurement at step three as the following three sub steps 3.1 to 3.3 they involve first a unitary operation then a computational basis measurement and finally a rewinding back to the query phase so these three sub steps 3.1 to 3.3 are equivalent to the step we said before we call it three and so if we write it in this way we can see that in fact our method involves running the attacker and letting it do its measurement M then rewinding the attacker back to the query phase and finally making a final measurement of the input register to extract the secret and so this measurement rewind measurement process is the reason for why we call our technique measure rewind measure or MRM now in fact in our paper we show how to generalize this approach this MRM approach to work for general and not necessarily optimal distinguisher's a and the main idea for this modification of our method is to switch the oracle that we give to the attacker from from being g to a kind of superposition of g and h and the superposition oracle you can see outputs the sum of g of x and h of x states with an amplitude of a half and the difference of these two states with also with an amplitude of a half and we have an additional entangling bit here that is zero in the first case and one in the second case so this is what's called a double-sided oracle and it can be efficiently implemented by the extractor if it's given access to both the g and the h oracles so this is what's called a double-sided extraction as as was called by Bindel at our last year and so our modified the generalized MRM technique uses this superposition oracle and then it measures this entangling bit and if the bit is zero so it gets that sum of states it performs an MRM extraction on that sum otherwise if the bit is one it uses the query-based extraction on the different state and if we analyze this in our paper we analyze this generalized MRM technique and what we show is that the advantage of any distinguisher a can be upper bounded by an inner product between the this the this different state and the projection of the sum state along the the measurement subspace of the attacker so overall what we what we end up showing is that the advantage of the distinguisher a is upper bounded by the maximum up to a factor of four the maximum of the advantage of the query-based extractor b and the MRM-based extractor c and all this was done for only one oracle query so in our paper we also generalize it to handle any number q of queries and the main idea is to use the classical hybrid techniques over the q oracle queries to show that effectively the advantage of a with q queries is reduced to the advantage of the attacker for one query up to a factor of q multiplicative loss now we also observe that the multiplicative factor of q can be reduced to in fact d where d is just the query depth of the attacker in the case where the attacker makes a lot of parallel queries it's only the sequential depth that actually matters here and as a consequence our reduction is nearly tight for low depth attackers that corresponds to low query depth attackers that corresponds to highly parallelized attacks so here's a statement of our generalized one way to hiding lemma and you can see that we achieve a relation between the advantage of a distinguisher and the advantage of the extractor that is within a factor linear in the query depth d of the attacker and with no square root advantage loss now compared to earlier one way to hiding results you can see here that our result uses a double-sided oracle with h and g used by the extractor similar to bindel et al but we avoid the square root advantage loss in the previous work and instead have a multiplicative loss of the query depth d another difference is that our distinguishing event for the distinguisher is whether the distinguisher outputs one whereas in previous work it could be an arbitrary or not necessarily efficiently checkable event now in our application of our one way to hiding to fuji sake okamoto cca security in the quorum as we said we focus on the variant of fuji sake okamoto which doesn't explicitly reject the cipher text but instead if the cipher text fails the decryption check it returns a pseudo random value depending on the cipher text now our cca proof for this this variant of fuji sake okamoto because it uses our new double-sided one way to hiding lemma we need a a proof that can work with such double-sided extraction and such a proof was given by bindel et al but using their old square root loss one way to hiding lemma so we adapt their proof a variant of their proof to work with our new one way to hiding lemma and there's just one slight variation in our proof compared to bindel et al's is that because their proof used applied the one way to hiding to a non-efficiently checkable event and our new lemma only works with efficiently checkable events we have slightly modified their proof to work with our efficiently checkable events for the distinguisher so in order for this proof to work it it needs to simulate the decryption oracle in the proof without the secret key and as part of this the simulation of the decryption oracle has to replace the hash of the message and cipher text by another evaluation of some other random oracle r on the cipher text only and in order to correctly simulate the original oracle during this replacement we need two properties on the underlying deterministic encryption scheme first is injectivity which means that the encryption function is injective the deterministic encryption function is injective except for sufficiently negligible probability over the choice of the key and second is the usual hardness to find cipher text that cause a decryption failure and so the statement of our result for the u transform of the fuji sake okamoto is shown here you can see the multiplicative factor of d and the other terms related to ffc and this is the final result for the ncca security in terms of the cpa security of the original scheme and you can see that we just lose a multiplicative factor related to the query depth of the attacker so our result is nearly tight for low query depth but we avoid the square root loss on the ncpa advantage and there's other terms related to the injectivity and ffc now in the ongoing and future work we are looking at how to improve the tightness of our result in particular to reduce the dependence on the query depth d by replacing the hybrid argument we used by tighter techniques such as the techniques by bindel et al or zendri's query recording technique we're also working on removing the double-sided oracle so that our extractor can use a single-sided oracle and to remove the injectiveness requirement from our cca proof for fuji sake okamoto and we're also have already some preliminary results on the injectivity analysis and concrete implications of our results for the nist pqc encryption candidates and finally it would be interesting to see if there are other applications of our mrm technique in other areas of cryptography so that's all i'll stop here and thank you very much


All right, so our final speaker for this morning is George Castro. George Castro comes from us from the Cloud Native Computing Foundation. He manages DevRel there. And he's going to talk to us about what's happening at the CNCF and what the Linux Foundation is doing to help shape the future of GenAI. So, George, please come on up. Hey, how y'all doing today? All right, I'm George Castro, a little bit about myself. I grew up in the Linux era, worked on Ubuntu for about a decade, moved over to Kubernetes when that started to come out post 1.0. And I've worked as a community manager for the Kubeflow communities and Cloud Custodian. These are all Cloud Native projects. And I am on month six of working at the CNCF on the projects team. There are 174 projects in the CNCF. So when you are perusing the buffet of technology to consume, we are charged with keeping those projects healthy and ensuring that contributors are finding their place and helping to drive the innovation that is consuming so much good stuff. I cannot wait to talk to you. This is my first AI anything. I've been learning a lot, playing with it locally on my computer and just kind of crash coursing myself. I find it having grown up through the Linux era and the Cloud Native era, it feels like everything just keeps accelerating. And just when I started to get a handle on the software, the hardware is also moving at this absurd rate. So I'm going to tell you today about some projects and organizations that are using Cloud Native technologies and production. Talking about 20,000 nodes, high throughput computing, about 100,000 jobs scheduled per minute, this kind of scale. This is Kubernetes now. There are CNCF members who are doing this today. I'm going to highlight some of the projects that people are using and organizations such as Bloomberg, CERN, OpenAI, NVIDIA, and Adobe, and of course, Hugging Face. I'd like to talk to you today about the next trillion core hours. We just had KubeCon and Cloud NativeCon in Chicago last month. And one of the key notes was talking about, first of all, it was a reminder that Kubernetes turns 10 next year. And we're starting to come to the point where projects such as this start to need to look at what the next decade looks like. We kind of cut our teeth figuring out the first decade. I was there. It was a lot of, how do you get the flywheel going? How do you become more efficient? How do you on-ramp folks? Documentation, all of the things that make open-source work. When Jim yesterday talked about how users are kind of demanding that AI be open and collaborative, these are the kinds of things that we're talking about. And I'm gonna talk a little bit about those in a little bit more detail at the risk of preaching to the choir. Because I think it's important for us, especially those out in the audience that might be watching this on video and things like that, that we need to start thinking about the long-term sustainability of these contributors and how we can continue to keep things moving. So what does open look like? So in a Kubernetes mindset, great primitives, API-driven, strives to be a universal interface for resource consumption. And users love the extensibility. A lot of the people that are using Kubernetes in production today are using it because of the ability to extend that API and get what they need done. But open also means exercising the processes. That means when end users take the extensibility of those APIs and they're able to move and get what they need in production, that they are able to communicate back to those open source projects to ensure that the common primitives are making it back to core for a few reasons. Maintainability and it's cheaper. So as it turns out, having end users be able to extend these APIs and then communicate that back into core, making that loop nice and tight and as fast as possible is something that we prioritize. I'm gonna talk about a few things today. The first is hardware enablement. This is something that's very front of mind for Kubernetes folks and associated projects, GPUs, TPUs, FPGAs, all of that kind of things. I'm gonna highlight two Kubernetes enhancement proposals. Those are what CEPPS means. The first is gonna be dynamic resource allocation. This is an alpha. Is there anybody here involved in these discussions? These are some of the more lively discussions that are happening in cloud native today. This is a very nuanced topic that takes a lot of thought because it does kind of change a little bit on how you might consider how Kubernetes is allocating resources and those conversations need to be concluded. And of course, CEP3545, which is the improved multinomial alignment in the topology manager, another CEP. There's multiple CEPs in these areas and then I'm gonna show you the website at the end where you can look these up and checking them out. But the TLDR is you all wanna slice and dice your GPUs and all that hardware and all sorts of different combinations. Next I wanna talk about workflow enablement. This is about reducing complexity. Index jobs actually landed in Kubernetes 1.24 and job tracking for massively parallel batch workloads and this is where you're getting up to 100,000 concurrent pods that actually landed in Kubernetes 1.26. There's a few batch systems that I like to put on your radar. The first is Volcano, a CNCF project and Q with a K. Make sure you take a picture of that one. And there's also two batch working groups I found out, one at the Kubernetes level for the cluster folks and then one at the CNCF level that kinda covers everything else. So do be cognizant that when you say batch, sometimes you need to be a little bit more specific about where you need to be. Lastly, I wanna talk about application development. So I'm a former Kubeflow community manager. Kubeflow just made it to release 1.8 in November and it continues to be used in production, notably at CERN. Always have great conversations with those folks on how they're consuming that and that project is now in incubation in the CNCF. I'd also like to point out Carmada which went into incubation yesterday which is for multicluster application management which I'll get to in a minute. And lastly, I like to talk about Kube edge of Sedna which is about pushing that AI workload to the edges. There's many nascent projects in this area and those are three that I thought you might wanna check out. And of course, as this starts to be consumed more, we're starting to talk about things as they consume those primitives, users are gonna wanna be able to grow those integrations with all the other tools that they're using in their clusters like Averno and OPA, so all your policy management and all that stuff is lined up. And as I'm talking to people who are doing this, sometimes they kinda wonder what's the relationship between OCI artifacts and alimonyms? Are we just shoving these into registries? I don't know, but I'm really looking forward to seeing the discussions that people come out with. Because for us, it's gonna be about unlocking these new primitives and bring them down to the cluster level. Clayton said, inference is the new web app in the first kind of decade of Kubernetes' growth. It was all about getting those web app. The first demo I ever ran of Kubernetes was like a web app. So if inference is gonna be the new web app, what I really wanted to say today is that Kubernetes is already the web server for a lot of production AI workloads. And as these features and the feedback loop from end users feedback into the system, it will only get better from here and then y'all keep adding zeros to everything. It just makes it really hard. And we're now moving what I call scrambling up that stack where it's not just about the individual cluster or the individual pods or the nodes. You're now thinking at a multi-cluster level and how we're gonna manage that across regions. I think you've sat in enough talks to see the level of scale that some of you are consuming this technology with, and it's really exciting. We'll also take multiple organizations. I'm just highlighting three here. The level of complexity that we're dealing with is just something that just one organization can handle. It takes multiple organizations and multiple verticals working together. I know there's many people in this room. You are multiple hats, multiple foundations. And I just wanted to point that out that this is something that we're all doing together because that's what we do. So I invite you to build the scaffolding with us. If you go to kubernetes.dev, you will find all the kept enhancement proposals there that you need to be able to go as with anything with open source. Everything is open, meetings are open. Meeting videos are always on YouTube and we're always looking for people to participate if you're an end user. Thank you and I will be here all day if you have any questions on how we can help you and hope to see you all in Paris and next year.


The Ministry of Education has detailed plans for the reopening of schools on Monday, January 11, 2021 following the abrupt closure due to community spread of COVID-19. After an extensive consultation process, the ministry decided to open the second school term and allow students to return to the classroom. However, the opening is being guided by strict protocols. During this week, January 4 to 8, teachers are at their various schools for school term planning, meetings with the chief medical officer and to receive psychosocial support facilitated through counselors. Minister for Education Honourable Dr. Gil Rigabet on Monday, January 4 addressed a meeting of stakeholders, including district education officers, principals and head of departments. Minister Rigabet spoke to the consultation during a live update to The Nation on Wednesday. The meetings held over the last two or three days in particular have been very detailed, outlining the various education-specific protocols and, very importantly, the education sector continuity plan in a COVID-19 environment. The latter is the outcome of a joint effort by the many partners aforementioned who participated meaningfully. I wish to thank the very hard-working caretakers, watchmen, groundsmen and janitors who have had to work exceedingly hard to guarantee the readiness of schools to receive students. The opening of the second school term is being guided by the Education Sector Continuity Plan in addition to guidelines contained in the OECS Continuity of Learning Plan, as well as regulations by the WHO and UNICEF. Chief Education Officer Dr. Fiona Phillip-Mayer informed that as with the reopening of school in September, all small school populations will operate using the whole school approach. We do have 34 schools that will be still on the alternate day approach because of the numbers that they have as part of the phased reopening of school. But what we've endeavored to do is to ensure that all of those students in those 34 alternate day schools get at least three days of face-to-face instruction complemented by online presence and a virtual learning platform. So those individual schools will be contacted by the administration of the school as to their students and when they can come. Important for the public to note is that where possible, we have endeavored to ensure that all students of kindergarten, grade six and from five return for as many face-to-face days as per the cycle. And that I speak to in relation to those 34 schools. You would note that many of those are secondary schools. We have in district seven, for example, only one school and in district eight only one school in that category. But as compared to say district two that has very large school populations, we have more schools using that method of instruction. In the classroom, students will be seated three feet apart from each other. They are to wear face masks and or face shields. Chief Environmental Health Officer Parker Ragnanan says there will be mass breaks as determined by teachers. He outlined the other safety measures. We encourage that hand sanitizers be placed at strategic locations throughout the school. And therefore, indeed assessments will have to be done to determine the best places to have these sanitizers located so that maximum use can begin from them. It is important for surfaces, the buildings, the floors, the desk, the classrooms to be adequately cleaned and sanitized on a daily basis. So we expect that there's going to be intermittent disinfection that takes place. However, at the end of a full day of school, we expect that there's going to be a full scale cleaning and disinfecting exercise that takes place. And as part of that, we encourage schools to educate the cleaning personnel, the janitors and so forth as to how to use the disinfectants and the cleaning agents is important to know. We also encourage schools to develop a very clear cleaning schedule, who is to clean, where they are to clean, how it's to be cleaned so that everybody is guided. And therefore, we have an effective cleaning and disinfecting exercise taking place within the schools. Sporting activities at schools are limited to small group physical engagements and non-contact sporting activities. Additionally, mass crowd gatherings at schools are not allowed and students and school staff upon the return to school premises must adhere to the established protocols, which include temperature checks, sanitizing of hands, physical distancing and the wearing of masks.