Everybody Matt here for late in sports cards ripping one box of 2021 tops chrome baseball jumbo. This is for will born W Good luck. Yeah. Good luck. Well in contraris through prism mookie bets Didi Gregorius Alex Kearlaw rookie.  How strong do you think the chance is that? Gulchman Arnato split the vote and Machado slips in a onesie MVP. I hope it doesn't happen, but Chris Davis Brendan McKay, that's prism. You know Haneo Suarez and William Contreras, that's rookie refractor 6-0 Sanchez Casey Mice rookie 86 And rookie refractor Otto to 499 Jonathan stever steiver Mike trout refractor. Oh, you have a Goldie jersey Brady singer That is Brandon Lau prism refractor and That is captain's cloth Jersey Joey Votto Cool it can hit into my Aida Oh nice, Rory um We have two four box tops chrome brakes on Monday, uh, random division style 21 tops chrome jumbo On the lsc baseball channel Randy Rosarana brady singer rookie 86 and magenta Javier Baez It's christian Javier rookie prism And rookie auto Blake taylor ryan brawn. All right. Come on. We need a good auto here. There's alex balm Rookie police castillo that is Juan soto 86 jack flaherty christian pache pro star gradderall marcello zuna prism And rookie auto brandon bilack radugo soto satees and shoey otani 86 Two packs to go. I think we have one auto still coming Hopefully it's that color there Sanchez dylan carlson That is wil smith prism And blue wave rookie auto andrew vaughn There you go. Nice one wil 140 of 150 nice andrew vaughn Sam huff uh rookie refractor miggy castillo consul in andre seminez rookie 86 And joey bar rookie aqua refractor Nice one there. That is to 199 Tanner hawk rookie refractor on the back And that'll do it for your box. Thank you for the purchase. We'll appreciate it. We'll get these right out to you


There are moments in your career that I remember you being very angry. One of them was a BJ Penn fight. Well, if you almost stopped BJ Penn, the round ended and you jumped up and punched the turn, you punched the cage. Yes. Remember that? Yes. You were still mad. You need to canalize your emotion when you fight. You need to be stoic, no emotion. But there's times that it's time to use your emotion, but to use it to propel you, to use it to motivate you to be able, for example, to finish the round with more energy, even though you're physically exhausted, you use that dose of emotion to push yourself. But the emotion is a little bit like fire. It can help you cook your food, but it can burn you. It's like, it's like fear, fear. Because someone would say, if you have a huge ego, like I have an incredible ego, I'm very, very proud. I'm a very proud person, which helped me be a better fighter, but also it's an issue with some time in life. If I use my emotion when I get hit, like I did for Matt Sarah, because I wanted to give it back to him right away. I didn't like to be stunned. I've never been stunned in my life, never. It was the first time that I got stunned. And for me, it was humiliating, humiliated. He humiliated me. So I wanted to give it back right away so we can shut everybody's mouth.  And that's it. But if you use it for that particular thing, it could be a big mistake. You need to canalize it and knowing when it's time to use your emotion. You keep it inside of you. And when it's time, you let it, let it explode. Isn't that it?


Good afternoon, everybody. It's nice to have you all here. We're going to be talking about the Linux system roles project And I think we will start out by introducing ourselves. My name is David Lehman. I'm an associate manager at Red Hat I focus on storage management for the platform Before that I was an engineer and I worked on anaconda the OS installer for many many years Yeah, hi Can you hear me? Okay? Hi, so I'm Shirley Ratko I'm from the Tel Aviv office, Israel I'm working at Red Hat. I've been at Red Hat for the past six years I'm a senior BI software engineer working on the over project and also on the Linux system roles So let's go over what we're going to discuss today a little bit So we're going to give you an overview of what Linux system roles are We're going to introduce you to two new roles. We've been working on the storage role and the logging role and We're going to show you a quick demo of How it actually works so I think many of us have been here before sitting pretty with some cool automation scripts and then something changes in the operating system and Not so cool all of a sudden New releases with new features and new configuration tooling have a tendency to break management scripts so some examples of this do you remember when Linux transition from system 5 in it to system D all the heartache that happened then How about going from manually editing system 5 network configuration files going to network manager More recently we switched from IP tables to using firewall D The list goes on and on But the common theme is that Things are changing and it's breaking people's automation You know sometimes in the thick of it It's hard to remember that these changes could also be thought of as progress or as technological advancement Because they present a you know, not only a real but an ongoing problem for systems management so We set out to try to improve the situation somewhat and One thing that became clear right away is The thing that's changing is not the what it's the how So we realized that we're still doing all the same tasks, right? We're setting up services We're configuring network interfaces firewall rules so on and so forth The thing that's changing is the tooling that's used by the operating system to manage these configurations so we realized that what we want here is to a Big piece of getting past this problem is a way to express the configuration such that it conveys the The essentials of the configuration itself without getting bogged down with the details of the implementation that's being currently used by the OS so Another way to say that and more common software terminology is that we wanted to abstract away the implementation so that the user can just express The important part that you know the pieces that transcend the current tooling of the operating system Okay, so For what David they mentioned we've developed the Linux system rules So what are the Linux system rules?  How many of you are familiar with Ansible? Nice nice. So I think at least one is not so let's quickly go over what Ansible is Ansible is an open source automation platform It's very simple to set up but very powerful It's composed of an engine and a YAML files That You can create your recipes And just call out the models from that engine It helps with configuration management application deployment tasks automation and Like I said, you can just create a recipe and deploy it on top of your environment Across flavors of Linux like Santos Fedora and well and on multiple hosts and get to the desired states of the machine And it does not use an agent on the remote hosts like puppet or self so The Linux system rules what we did is basically created an consistent configuration interface For rel Fedora and sentence like in an API basically So you don't need to be we created an abstraction layer From the implementation So you don't need to be bothered by the tooling underneath You just need to do your configuration will be the same even if the underlying Technology changes It's maintained by the subject matter experts Experts in networking storage and so on And it evolves with the subsystems So even in the future if we are changing the technology underneath your configuration and across Updates your configuration will stay the same. This is the intention It's compatible and tested in rel six seven and eight and also in Fedora Currently we have several roles that are already released and tested like the network and SELinux time-sync post-fix key dump and there are also a Roles that are a we've also started working on or planning to work on like the storage for example Which is supposed to be released in rel 8 and the logging wall, which is still a development and other additional roles for image builder Cockpit subhana and so on Okay, so now we're going to dig in a little bit to some of the details of two of the emerging roles We're going to start out talking about the storage role All right, so The first thing that I think everybody thinks about when they think about storage is complexity And this is unfortunate because we're not all trying to optimize something to get the absolute maximum number of IOPs or whatever The truth is that for most of us Storage management should be pretty simple because most of us have pretty pedestrian needs We want to create a couple of volumes put a file system on there and set it up to be mounted and that's it So when we set out to do the storage role the overarching Principle or goal was to simplify local storage configuration for the vast majority of cases So within that goal there were several other principles that sort of building blocks or pillars if you will so the first one is that if you're going to make things easier on people you have to Provide a nice concise way for them to express or define the configuration that they would like to see on their system a minimum of boilerplate and You know just as little typing as possible So the next thing is Which is something that helps us achieve the first thing is to provide reasonable defaults when that's possible. So for example The default volume type is going to be LVM the default file system type is going to be XFS That may change in the future, but the interface is going to remain the same. So for example Who knows in Fedora 35 the default volume manager may be Stratus But that won't change the interface of the system roll for storage. So The next thing is that we wanted to handle non-essential details Automatically, so partition allocation is a perfect example of this if you're creating an LVM volume You shouldn't have to know how partition allocation works. You shouldn't have to specify a Disclabel type a partition table type flags start sector and sector none of that All that's taken care of for you if you want to create an LVM volume group. You tell us what disks to use we do the rest Lastly we wanted to as much as possible. We wanted to use existing Logic to do the heavy lifting. There's already storage management APIs That have been tested and used for years One of those is blibbit. It's a Python module that's been used for storage configuration during The OS installation phase since Fedora 11. It was split out into its own package in Fedora 18 So it's been tested quite a bit and that's what we're using to do the heavy lifting here All right, so now we're going to do a couple of examples The first example is I think as simple as it gets What we're talking about here is just throwing a file system on a on an unpartition disk and then setting it up To be mount mounting it and then also setting it up to get mounted on boot And you'll see here that there's a list called storage volumes You put an item in the list You set the type to disk you specify a disk you specify a mount point And then you can optionally specify the file system, but it's going to default to xfs. So that's strictly optional And that's it And that's all you have to do and when that's over with you'll have your file system will be created and you'll have an FS tab entry and you'll be ready to go Okay, the next example is a little more complicated. This is an example creating a What we're calling a pool, but in this example what that translates to is an lbm volume group And we're going to use that volume group to store the data for a mongo db installation And so there's two volumes we want to have here ones for data And ones for logs So again, we're creating what we're doing here is we're adding an item into the storage pools list There's just two lists there's storage volumes and storage pools Volumes are for volumes that are not in a pool and that means disks So we put an item in the pools list We give it a name We don't have to say that it's type lbm, but we can if we want to We say which disks to use and then we create a list of the volumes in that pool The first one is data. You can see again, we're commenting out the defaults here just For hopefully a visual aid Really you can see that all you need to define a volume is a name amount point and a size And then Second one similarly simple Okay, so then one more example and this is just going to show some other options that are available to you Again, we're creating a pool and we are creating one volume in that pool and we're just showing that you can Specify a file system label. You can also specify options to make a fs And you can specify Options to mount and those mount options are obviously going to go into etsy fs tab as well So that should hopefully cover A good bit beyond the absolute simplest of use cases Um, let's see. All right, so now I'll give you a little bit of a feel for where we are and where we're going The current status of the project is that we just released Version 1.0.0 this week. It was released to galaxy on thursday And it's currently in testing in preparation to be released in an update of rel 8 We're hoping it will hit for the war 32 as well And the support there is for the whole disc example that I showed you You can also do a whole disc with a partition that spans the whole disc And the purpose of that is if you have a multi os situation that Partition table will signal to non-linux operating systems. Don't clobber this thing. There's something somebody put something here And then the last one is lvm now. We don't support yet. We don't have support for um thin provision to lvm Or cash volumes or raid or anything like that, but all that stuff is In the pipeline. It's just not in version 1.0 Okay, so um the roadmap this is the order of this is kind of arbitrary. This is subject to um change But obviously we're going to want to add support for block device encryption using lux and software raid The advanced lvm functionality likes and provisioning cash And lvm raid and we're going to want to add support for compression and deduplication using vdo And we're going to want to add support for stratus and all that stuff can be added without changing the interface Another thing that's good about this roadmap is that The underlying library blivet already supports All but I think two of these things so The amount of work is really limited to just the work in the role itself to plumb through to the underlying library So that means that it should be this roadmap should get traversed quickly Compared to if we had to implement our own storage library that is all right, so the next slide here is some challenging but possibly high value features that are Uh Maybe or maybe not at risk some things that seem like they would be really useful for a lot of users But there's a possibility that they're not going to fit within the constraints of of an ansible role And when I say that I'm talking about Some of the principles of ansible are that things should be item potent meaning if you run it twice they should get the same result and At least I'm not totally sure about this, but I think things are supposed to be deterministic as well I think that kind of Is a part of the first one And so there's a we're not totally we haven't worked out the details of how we can make these work, but We have varying levels of optimism for varying for the various features here, so I'll spare you the suspense here So automatic device names, you know a lot of the time you don't care what your logical volume is called Right, you just care about the file system in the map point So it seems like we could make things even easier for people You could go from having to specify three pieces of information to just having to specify two Another one automatic size is if you're creating a pool and you only put one volume in the pool It stands to reason that you could make that volume occupy the whole pool if if the user doesn't say otherwise Right, so that's another one that could be good, but I'm not sure if it's going to work or not Again automatic disk selection same deal You can go out and list the disks in the system and you can figure out which ones have something on them And you can use the ones that don't have anything on them The last one here is I think possibly the most useful of the bunch and also the one that I'm the most optimistic about And that's percentage based sizes I've been thinking about this the last few days and I think it's going to work In fact, I I implemented it the other day And this is like You can if you have a pool and that pool could be either a partition drive or it could be a volume group If you have multiple volumes within that pool It might be nice if you don't know the exact size of the drive It might be nice to be able to specify the sizes of the volumes as percentages of the total size of the pool and so I think it's looking pretty good for that Honestly, I don't think that's a risk for for item potents at all. So, um, you know Pending review and all that kind of stuff. We'll see how it goes, but I think that one's going to be good And that's really lit for the logging role So thanks guys and Shirley's going to tell you now all about the logging role um, okay, so logging role and Like we said, we intend to give a higher level architecture and sort of an api In the log and the Linux system role. So for the logging, we mean it's pretty basic What we want to do is to collect logs from different targets locations and then ship them to different destinations We want to make the configuration as simple as possible and to be able to spread them across our system And to the multiple hosts that we have So We want to collect multiple logs to multiple destinations and apply default settings when we can As the base of the logging role we used our syslog Our syslog has been in rel Since rel 6 it's almost 10 years now and it's become the basic Default tool for rel for logging and It's it allows us multi-threading secure connection diverse destinations That it supports it can filter any part of the syslog message Fully configurable output format and it's very it's suitable for class relay chains And by the way, we did try other Collectors, but At least for now this one is the one that we feel the most comfortable with in regards for performance So when you run the logging role by default Just like this What you'll get is that The row itself will make sure that you have the latest package of our syslog It will deploy the our syslog config the Default one which collects journal records and send them to files or based on their the the the application that send them and For example for valog messages for valochron And based on their severity, for example, if you have urgent Logs then you'll get notification if you have logged in users So this is the default and Another use case that is already implemented is If you already have your own syslog configuration file and you want to spread it across your environment, you you are able to use the custom files Here you have in the variables you have a logging outputs bar And which is a list of the outputs you want to configure In this case, there is the custom files and you simply need to state where that your file is located and it will be Deployed all across your system Another interesting use case is being able to ship your syslog data To elastic search. This is already implemented. So we have an output to elastic search And both with certificates are without So you can send your journal information to elastic search and have your own One source of logs to ship everything in and you'll be able to get your Platform to dig into your logs and see what's going on How we will do that this is an example So again, we have the logging outputs in this case the type will be elastic search You will need or simply need to state where is your elastic search instance What is the index you want to ship it to in elastic search if you have certificates? You can state where they are And you will mention which logs you want to collect in this case journal And We are already using the our syslog role in production in overt, which is the virtualization management System so we are shipping it We are using it for both shipping metrics and logs to elastic search. So For metrics we are using collectee and we added a plugin that sets the sensed metrics in syslog format To our syslog by tcp and we are also collecting the The overt application logs and we are sending them to elastic search. This gives us a full monitor solution It provides you the way to visualize everything with kibana and creating Prebuilt dashboards for example and alerting We are also going another step in our next release And creating a UI based on the linux system models and in everything so We will have the option to select the host list that we want to Deploy our syslog and collect dion and then this and in the underlying In the underlying infrastructure will create the vals for the linux system for the role And simply run it and all of the hosts that we've selected will be it will be Configured to send the logs to elastic search And this is the result you'll get The kibana dashboard You'll be able to drill down to your logs and Do the analysis there So the status of the logging role the logging role is still in in development It's still missing some of the features that we are planning to add Currently we support like I said the default artist log config The sending the journal to elastic search deploying custom configurations and it's already used by overt But on the roadmap we are planning to add profile based configuration and So we have the general use case, but we all we also want to add additional profiles for resilience and security We want to add additional inputs This is something that we are still Thinking about we are not sure what will be the additional inputs and if you can think of Good use cases and then we will appreciate it if you go in to the project and create an rfv This will certainly help And additional outputs currently the We plan to add remote artist log and the remote message buses like Kafka and mqp Now it's demo time Okay So this is a demo that was put together. It's going to use several of the system roles to configure a system It's going to configure some of the firewall some network interfaces Time sync and it's also going to set the system up To run the cockpit web client and Composer the image builder So the beginning here This is not live The beginning here. This is just going through some of this Showing that you have to have several of the system some of a couple of packages installed You have to have several of the system roles installed via galaxy So those are some of the prerequisites And so then we're just going through these are the top level variables for the file and Basically this is These variables are to set up a couple of network interfaces and set up time sync And as you see there the The way this playbook is structured is that the the time sync role is Invoked up there Directly and the other roles are done as tasks and that does two things One is it allows us to control the order of execution and the other one is that if one of the earlier Roles slash tasks fails. It won't try to keep going So that one right there is going to install the cockpit web console Nice and simple The next one is going to set up the firewall for cockpit Again Hopefully that's the the language there looks concise So then next thing is to set up a volume for image builder to use So it's going to create Using the storage role. It's going to create a pool with a single volume in it And it's going to set that up to mount it at Varlib Lorax composer And that's all based on the you know, it's conditionalized if you wanted to skip that for some reason So the next thing we're going to do here is set up the image builder GUI Again, I think that looks like less typing than Other alternatives And so then this is just an example down here of setting up a using the networking role to set up a bonded network interface I'm going to level with you. I don't really know the technical details of setting up a bonded network interface I was an RHC for real five it's been a while I think you can draw some part of your nature by making it your by macabre Yes Exactly and then of course the the other thing is that this is going to run on rel six or rel seven or rel eight or rel 25 Or you know fedora 32 So then setting up the components of the bond down there So All right, so then here This is just showing the initial Hitting and missing this mic on it. This is showing the initial network Interfaces you can see that there's two extras there that are not configured not being used And so then I think that the next step here is going to be to Run the role or run the playbook rather And then sort of verify the results. Okay setting up the time sink Configuring that setting up cockpit setting up its firewall. That's doing the storage Now that's done setting the mounts and then that's setting up image builder And setting up the bonded interface and that's it and you can see that Succeeded six of those plays changed things And now you can see they're gonna the bonded network interface is going to show up What's next I think Okay, this is the image builder services running will be verified here And then you can see among all the other file systems you can see the new one we created for image builder composer And to get a little bit more of a detailed view on that Here's a look at the lvm setup the last one there is the one we just created And incidentally They're already fixes written they're not in the they're not upstream yet, but there are fixes that you can see there He chose to make the Volume 19.5 gigs. That's because of the metadata used by lvm So if you just would try to run an lv create with 20 gigs It would not work because the disc is 20 gigs and this metadata usage So I've got a fix in my local tree that I've tested that will Just trim the the requested size as needed in that case And then of course the percentage based sizes will solve it even more elegantly I would say so What's that? So this is the way you can get the roles from galaxy you simply need to call them And here are the links to the landing page documentation github repo and We encourage you to go if you are an expert in your field and you want to contribute And that will be great and if you want to try it out some of the roles are already in galaxy some of them under are under github repo Give it a try Please And tell us what you need what other features you need And we'll try to integrate them in any questions Yeah, yeah, go ahead Um, my name is alex first off Let me thank you for the work that you've done as a sysadmin. I appreciate it a lot It's gonna help us a lot in our future projects And the first question is does it currently support non-red hat linux systems? That's a good question. And I think You could I could I could either um Be slimy and say that's unknown or I could say no Um, I don't think that we've put any effort toward Uh, running it on debbie and a rubin two yet Yeah Thank you Are there any plans to convert these to a red hat supported product? because You know All of us probably knows that puppet got the equivalent say Which is puppet enterprise Where they encourage all the other software developers communities even proprietary Companies to develop the puppet models and you know make them use Great question. Thank you. Uh, my name is terry and I'm on the rail product management team. So, um They do all the wonderful work. So Thank all of you But um, but yeah, I can answer that question. So yes, they are supported today So they're they're in galaxy as the linux system rolls. Uh, so you can install them that way They are shipped. Uh, michael de palo here with us. Uh, does the fedora packaging? So he packages those up as a fedora rpm Called linux system rolls in in rel They are in the extras repository for rel seven and they are in rel eight app stream repository as the rel system rolls and so Galaxy is the native Ansible native way of getting them and that's gonna match github So kind of like the latest greatest upstream as they add new functionality and then as we test it and document it and You know do all of the ci testing against it We will ship them as part of the rel system rolls package.  We make the ansible engine Accessible with your rel subscription So that it's easy to get to and we have so many layered products that depend on it now But if you want full broad ansible support, you still need to buy an ansible engine subscription But we support this as like our user contract if you will because we need to make rel consistently Configurable as you move from rel six to rel seven to rel eight and beyond So like we owe that to you. So we're we're committed to supporting that for free Yes, that's that's one of our friends who planted the seed for this project. So Thank you. Um So that's a long winded answer. I hope that helps Thank you, Terry So as somebody who's done ansible for a long time One of the things that often frustrated me is as my code got more and more complicated I couldn't refactor it because i'm In yaml and not in python and the underlying mechanism for all this stuff is python Has there been any thought of taking now that you got it working and taking what you've got working and making it into ansible modules And and perhaps even clearing cleaning up the internal object model within ansible so that those are reusable components So that for example, I don't have to go across the wire for each call Right because that really does slow down. I have to do an ssh call for each individual module task I also have to Maintaining state inside of ansible if you look at your Playbooks that you were you're specifying for these there you have global variable names Which as a long time programmer makes me wince I know that that's the tool that you have to work with that's what ansible puts in here But if they weren't insible modules, then they would be explicitly namespaced by those modules Has there been any thought and I as I get I understand you got something working This is the reason why ansible is so successful. So you can share your code this way But the next step is to make this stuff maintainable. Is there any effort going to be going into moving it into the right abstraction level, which is the Ansible module not roles for these I know it's I shouldn't be asking this question. It's something on the sales side, but I have to So I think it varies from role to role what the architecture is actually I initially implemented the storage role using pure ansible using the existing ansible modules that are out there But like you described the yaml became a nightmare And I got to the point where the next thing was block device encryption And I was just like I would rather quit my job than even try this in the yaml so Because in storage, right there's arbitrary Stacking of the different layers and and the animal just is not equipped to deal with that So what I did was and I refactored everything into a python module So really if you were to look at the tasks the main tasks file for the storage role, there's almost nothing like There's like this really embarrassing thing where I spent 200 lines Filling in default values in some dictionaries because I don't know if yaml very well And then there's one module called to obliv a module called blivitt And then there's another one more call to a mount the mount module and that's it So I don't know if that's standard practice, but I think that to a large extent I know that the networking module looks like that or the networking role is similar So we did think about that. I don't know. It's probably not perfect, but we thought about it Thank you for this and I really appreciate the fact that you've got it connected to red hat virtualization That's very cool The thing about storage though is it's really scary to get right and it's really easy to screw stuff up And from what I saw here today was hey whatever's in the playbook just happens if I find a disc there I just write all over it. Is there any sort of safety in there that says Ooh, there's already a file system there or oh, by the way, it's already mounted somewhere That that protects me against doing stupid stuff Well, so for example if there is already a file system there that is of the of the Same type. I think it's just going to get used There storage is it's funny because I agree with you that storage is scary But I I don't agree about how a store just scary I don't think it's scary that when I push go it goes But what I do think is terrifying is all the different permutations of how things can be right like I can say create me an xfs file system on sda and mount it at foo And then when I go to look at it in ansible there may be An xfs file system on sda, but it may not be mounted at foo There may be one already there and it's mounted at foo, but it's got the wrong stuff on it There could be one, you know, like the possibilities of what you have to manage are incredibly complex and For the most part you're going to get what you asked for Um, so if you for example if you have some if you have an lvm stack on vdc And then you tell us to create a file system on vdc. We're going to wipe it off before we do that Um, and you know, that's the thing is everybody likes to put the safety buttons in storage, right? Are you sure but you can't do that with automation because it's no longer automated So I would love to have a gentler Response to that, but I don't know what it would be So to kind of follow up on that actually, um a similar question I had to give a concrete example that concerned me You commented on having defaults for say the file system or the volume manager. Um, and that can change Oh, is it? I'm sorry Uh, should I just start from the beginning? Yeah, that'd be nice. I'm having trouble with mine too. So don't feel bad Okay. Yeah, my bad So to give a concrete example to what he just brought up, um that I um So With storage for you commented on having defaults for say the file system or the volume manager or something like that And there's of course the possibility that could change which is fine, but um Let's say I I run this on a system I upgrade and then I run it again and the file system changed what happens Do you like do you read my disc or What happens there that's an excellent question if you have the um if it's already set That's kind of our problem to solve if the thing is already set up and it already has the same mount point And we're going to assume that it's what it needs to be Um what we'll have to do we don't have it there right now because the default hasn't changed yet But what we'll just have to do is add an additional layer of logic that says it'll differentiate between You said LVM Or you didn't say anything You know what I mean? It will be just a little more gentle if you didn't say anything We'll know to be a little more flexible in in using what we found Okay, thanks. I'm glad you thought of that. I'm I'm I'm yeah, I mean, you know We don't know completely till we get there, but um We'll work it out What Oh screen was asleep Okay, uh, like my colleague here want to congratulate you on this effort as well I'm much appreciated. Um, thank you. I have many questions where I go to most glaring for me Is there plan to incorporate ice cozy or other Block over wire Or even nfs Or are they not working file systems Into the storage role or is there like a different storage role that Is dedicated to this this kind of technology Well, I'm suspicious of you now because there is as it happens there is a Sort of an in development A pretty nice prototype out there that is specific to remote storage And we have Talked about we haven't worked out the details But we have considered Dedicating this role to local storage and then having a dedicated remote storage role that can manage those sorts of things Thank you Thank you


Hello everyone and welcome back to navigating the road to cyber resiliency a summit made possible by Dell Technologies Jaspreet Singh is in the house CEO of Druva. Good to see you face-to-face. Good morning. Thank you having me here You bet. What's happening with Druva? Give us the update on the current state of data protection. It's great to see you Thank you having me here a lot is happening with data and data protection as we know it like as you see the world around us There are many many many cyber threats Happening with different political scenarios with different You know different motivation by different hacker groups or different intruders and and data is in the center of all of this And data is a centipening focus of many Hackers and attackers and and how you recover how you save card data Becomes an interesting factor for Druva. So we've been active and busy with all the cyber is around us Talk about this resilience piece in the recovery. Why is it getting so much traction right now? What's the focus? Why are people trying to figure this out? And what are they discovering as they look at the landscape for cyber resilience and cyber recovery? Absolutely. So look last 30 years of security We have spent a humongous amount of effort trying to detect and prevent Threats happening at once threats with some type happening at the endpoint level at the network level at the application level But we all realize more and more that security incidents are more a race condition, right? One vulnerability left unaddressed one application remains unpatched one network has a plug-hole, you know The intruder comes in when they come in The insider and intruder Are dominated the same, you know same personality as they it's through a credential leak how the intruder came in Right. So as a race condition is met and intruder comes in People haven't really thought through how the recovery piece Holistically happens and how recovery happens in Conjecture in in in confidence and in completely comparison with their security remediation, right? So cyber resiliency is all about how do you make sure? Recovery and security work together to make sure data and application are up and running in time and at scale Okay, so we saw that you know IDC had you in the market scape as a cyber recovery leader I want to ask you a some my semi tough question There's there's companies in the business that have pivoted and it said okay now. We're in security Talk about your roots in this space in terms of recovery you keep talking recovery and and convince us that it's not just a sort of cyber Security washing. Absolutely. It's a great question. So if you look at the holistic view of data prediction What was the roots of Drava and many of those are a domain like You can pretty much look at the market and in sort of Historically in two big buckets right the one big bucket being can I buy a software to sort of you know deploy it myself? Right and which and you had many many good companies doing a good software base approach And then the world thought you know Can I buy hardware and software a little bit more Integrated and have a better technology managing my data center and data Holistically and then he had many good examples and a deli is a great example to managing integrated Software hardware approach to managing data at scale right but then what when the equation is turning more and more to a security conversation The security conversation. What is the toughest part of cyber security today? It's how you operationalize the tools It's not buying one more tool. It's not getting one more alert How are you gonna holistically manage your risk better and a personalize better to the world last for a third choice thing Can I rather than buying hardware and software can I buy a service model? Which has a better levels to a personalize my entire data posture on my security posture holistically and that's been whole Drava's existence all throughout, you know, we launched the first cloud offering about 10 years ago And we consistently following and growing a footprint around a very sass oriented way to manage data and manage all Aspects of risk around it and we the only one pure play true to our cause and and delivering customers the outcome They want and not one of one more tool in the arsenal to manage motorists. I remember in 2017 when you first came on Can we actually just moved into the studio? It was early you guys were early in cloud a diverse specifically you guys just recently got an award for 80s global Storage partner of the year. Congratulations. Also crossed 200 million in sass revenue The clouds a major part of what you guys do obviously now get distributed computing you got on-premises and edge emerging Jenner VI is hot as could be roll of data is going to be critical How are you guys differentiating yourself now in this field because like Dave mentioned it's kind of crowded people Are kind of pivoting and you know washing this that and the other thing but the most part It's a really focused market on the data protection threat detection. It's all kind of coming together What's your differentiation right now as you look at this next wave of cloud and distributed computing absolutely? So so most people think of cloud as a sort of at least most in our space think of cloud as a technology Sort of you know a trend we think of cloud as not just technology but also business trend right people are not Only buying cloud they're buying the goodness of cloud right they wind the goodness of cloud Can I buy just in time? Can I can I scale on demand as I go across the globe? Can I can I predictively pay pay for a SLA and more critically for security? Can I pay for an SLA at the same price point across the globe right? It's a beauty of a model. We've scaled the business globally. We support the humongous amount of more regions We did about six billion backups with you know more procession than anybody in the market So our scale our maturity we added more and more certifications We got Fedram certified and going through a certification more and more So the scale maturity and the offering to truly deliver a customer outcome Far more critical than just another tool is what you've been positioned after and we've scaled and matured as business more than anything And yes, yeah, it's a very very interesting question because AI More and more the discussion or an AI our discussions also centered around the data and the data architecture and And I think AI helps in both the ways like your your tasks of managing security and data Often are extremely manual extremely painful and AI can definitely help in many many areas at the same time a lot of general purpose AI deployment trust and require you to have a centralized data architecture which is where cloud is also coming David I were talking on the intro around the title of this event and you know navigating the road to cyber resilience and the word navigation Prompt discovery people have to discover What architecture and you mentioned that what is the discovery? Point right now for practitioners as they look at this next-gen architecture because you want to set up for data as a competitive advantage But also it's a competitive advantage to be targeted. So what is some of those discovery challenges? Yeah, it's a fantastic question So, you know Majority of if you have a CIO conversation a CISO conversation if you ask them Like where have you been deploying your cyber resiliency practice and they go into a zero-trust network effort They go into vulnerability management effort, right? But then if you pivot the conversation saying that that's great, but where is your biggest risk in the business, right?  Customer. How do you differentiate your source code from third-party source code? You know, how do you differentiate your contract with the third-party contracts? How do you differentiate your research and the consent you have in the research then a third-party research, right? So data is far more connected now than ever in the past, right? But then this is where true understanding of my data What is my data comes into picture for understanding as the data gets more and more Decentralized to your point as it deploy more cloud more edge more services data management and data security has to get more And more centralized so you have a single view of your data assets You can then if once you have a single view you can understand them better You can then notify on on things like breaches better and you can assess your risk are far more better So the more distributed technology gets the harder it is to keep it in sync. Does AI help with this?  It's a great point and we call it internally the AI of things right like how do we the simplistic tasks of Managing your IT stack of your data stack can be managed through AI better, right? Like when men mobile came into picture, right? There wasn't a brand new mobile company well They were few but broadly almost everything we did from Salesforce to accessing application became more Mobilized right became better mobile friendly mobile first approach happened, right? So not a lot of AI first approach happening across the market. What does it mean for? Something like drover right so that the multiple factors on it like how do we deliver value and what customers can do on our platform? How do we deliver value to manage data there humongous amount of manual tasks around to your point? Can you can you pass through my logs? Can I become okay? Can I configure better policies? Can I handle it better? And yes, we we also launched something called drew AI we were probably last to high but the first two results We launched a successful co-pilot which could pass through your log as a customer not any generic log But your logs and identify particular error codes in those logs correlated product documentation and come back with recommendation And then you could even put into effect so very elegant and beautiful model to manage a data We also know on the other hand working through what do customers need from the data We are storing for them to power through their gen AI efforts within the company as well So so it's high fidelity data even though it might be messy as it's logs Is that a is that a rag that you've developed is that sort of a some kind of custom domain specific LLM What actually is that so you have to the LLMs for the broad range and they are many they are large their medium They're small Language models are coming in many forms and shape the first of all you have to understand what are the With the AI washing happening across the market the first and fundamental problem to solve is what are the top four or five Customer concerns which are possibly solved through AI right that's number one thing Otherwise technology is not for no use right once you understand those problems deeply then you understand who which system of record Has the best knowledge of it? How do I bring that system online and connect it to an LLM right? And then once you bring the system online How are the systems navigate and how do you manage security in privacy that while you pass on the customer information? And they're probably series of algorithm and series of question answers happening to resolve the outcome Which information is okay to pass on and which API should be better sealed it? What is a boundary of this language border to do and they build all those hard level and then finally how do you test it? How do you make sure it is predictable? It doesn't hallucinate. How do you make sure there's a QS system around it? So there's a whole new thinking around the interface interface to an application Will radically chain with this new gen AI approach and as we thought through all over again in terms of how the things connect How they test it and how they deliver the actual outcome you want. So it's more than just a narrow app Right, it sounds like an end-to-end system that you've embedded into your software and the domain knowledge along with it saying look This is the right answer the wrong answer go look here go prioritize this and then the Jenny I takes over and there's a beauty of the Jenny I model It's a very text oriented model to learn and grow along with your needs and desires very cool And this helps you up with your edge deployments and this distributed challenges. Well, absolutely So I think the broader the cloud gets to the edge and the other domains the the handling of data gets more error-prone Which is where you know a lot of AI-oriented systems can get or can bring automation at the same time Can can help sort of solve these long-tail problems of managing information? So you and I sat down with Travis V Hill from Dell last week We're going to be running that later on so you know you don't want to miss that but Explain just give us a little teaser. Why is that relationship so important? To customers like why should they care? Well any partnership has to be customer first, right? So if you look at if you look at Dell strategy around apex and bringing everything Dell as a service to the end customer And if you look at Dell's core domain and DNA It's it's how do how do they actually do the best job in data center and to the cloud? But starting with data center and really offer best of each services there, right? This the customer has a need and desire to solve have a best outcome in data center and the best outcome in cloud Right, so then do a partnership brings these two best of breed solutions together in a core portfolio under the same Umbrella of apex services where the customer likes and desires and wants to consume more and more in so ultimately Customer has a better choice and wins overall and you know, I actually said it's part of this program It's not part of this program. It's actually on our YouTube channel already We already released that so you might want to go check out youtube.com slash silicon angle And check that out. So thanks for doing that by the way and I appreciate the explanation. So look you've Had a long history in this space What are the things that customers should be thinking about that are that are maybe non obvious? You know some of the threats that are coming some of the how can they anticipate? What would you recommend in terms of customers thinking about all right the next four or five years? These are the things that we have to be concerned about whether it's you know, the uncertainty around AI Obviously the threat actors are getting more and more sophisticated. Where would you point customers in the future so they can prepare? Yes, a data. That's a phenomenal question So data I'm going to give an analogy to make my point here data is becoming so connected tissue in the organization To me when an incident happens when something happens around a company, it's that last supper You know where everybody is leaning forward and and you don't know who the last culprit was but everybody's leaning forward to sort of You know pay attention to a particular conversation happening right a data incident pulls in Legal pulls in privacy pulls in security pulls in infrastructure A lot of people come into to understand what might be the impact of the organization and today these departments Don't talk to each other. There's no single.  I think our recommendation to customers is that data and backups are not just a problem of a backup team The as as investments have gone deeply into detection and prevention They must go deeply into response and recovery and these Multiple silos organizations must talk to each other right the best thing could happen to a backup admin was to get fired Right. There was no nothing ever good came off a backup admin, right? So they never shared the data with anybody else So if while all the single source of truth was happening in the backup data There was never a confidence of discussion between security privacy and legal into that data and Rebring that truth to life by making the system connected in the cloud very actionable insights around the data My final question for you on this segment is as we've gotten to know you over the past six years on the cube I'll see ten years when you stop started the company a lot's changed the role of data and the importance certainly hasn't if anything It's become more Critical and more central to the value proposition for companies clearly Genevieve. I points to that and we've been reporting on At the cube what's changing in data as we look at down that road that we're going to be navigating The cyber resilience. What are the data challenges? What changes does the script flip does? Because if you think about what we're envisioning here, you got to build governance from day one You got to have all that stuff now integrated not siloed.  So the role of data will be a developer construct an application construct with Genovi So what's your vision on that road ahead for data the role of data what changes what stays? Yeah, to understand data. That's a great question again to understand data We must look at must understand the growth of and portfolio of applications, right? And we also must understand the use of data or this threaten data, right? So when you started off like when ten years ago when you build the first cloud offering the the broad the broad Set of application we used to talk to an admin about or a customer about like four to five dominant applications, right? Now it's down to like thirty five thirty six applications Which are like the call it the the spring of all the sass I might be more chill Oh, right, and now with the Jenny. I like Anybody can write an app with text You don't have to be a programmer You can write a text query and that becomes an application right with the new Amazon announcements and an open AI announcements, right? So new apps are text which means that the application will change Greatly and and will transform data right number two You got to look at like 90% of all data produced the whole of this year was actually unstructured data So data is not still while applications are changing data itself is a lot more unstructured Coming from machines or humans, but unstructured data or semi-structured data for the more degree number three threats are evolving rapidly, right? Threats used to be dominantly focused on a malware or a third-party threat have coming in now We have government issued orders. We have war crimes. We have insider threats We have systematic issues. We have API as and triggers calling mass functions. So Data is obviously growing but rapidly changing hands rapidly changing application rapidly growing into more and more threats The job gets complex, but that's why we have to you know, just be we're out of time I'd love to have you back and pick your brain a little bit about the the investment climate starting companies You know what you would advise so thanks so much for coming on absolutely. Thank you very much All right, keep it right there. You're watching navigating the road to cyber resiliency This is a summit made possible by Dell Technologies up next. We're going to talk to Herb Kelsey He's the lead at Dell Technologies for a thing called project Fort zero, which was announced in May of 2023 at Dell Tech World it's going to talk about the progress from date to date and Specifically a real challenge. How do you operationalize zero trust? Keep it right there


One great-grandpa, Jacob R. Stiltner, fought in the 10th Kentucky, and great-grandpa Andrew Jackson Edwards, fought in the 21st Virginia Cav. And on the mother's side, I had 13 Confederate ancestors in hit. I'm trying to preserve history here and spread the word. The North tells a different story they don't want to admit. But we're just trying to spread the history and educate the people. Maybe they learned something here today they don't know. Not only could folks see what daily life was like during that era, but we're also able to get a glimpse of what it was like to be a soldier as a replica of the first successful combat submarine was on display and told the story of the brave men who manned the machine. What these men had to go through, they had to march seven miles just to get to it. They were inside of it eight to twelve hours. They marched seven miles back and they did that three times a week. They weren't wearing tennis shoes either. They were wearing what they called brogans and they're not comfortable. They put a spar on the front and what they called a torpedo. We don't know the exact kind of torpedo because all those records were destroyed, but we know that it carried somewhere between 90 and 135 pounds of powder. This particular type of spar torpedo was intended to impale the side of a ship and back off, leaving the torpedo to detonate. But that did not happen. It detonated upon impact. That 90 to 135 pounds of powder set off the powder magazine on the Houstonic where thousands of pounds of powder and ammunition were held. The Houstonic was over 200 feet long and over 38 feet wide. Not only did it break it in half, but it blew it slam out in the water. It had a crew of 160 men and only five pairs. So that left 155 to right near diaries, what kind of wild ride they went on that night.


What if I were to tell you that there might already be a team being built at Activision, the specific part of Activision that makes Call of Duty to make future versions of Call of Duty for Nintendo platforms? This is before the Microsoft deal acquisition goes through and they spend the $69 billion to acquire them. I know there's a lot of legal battles going on with that acquisition and Microsoft did make a public promise of 10 years of support to Nintendo with Call of Duty. Of course, they don't control the company. So what is going on? Why is this happening? And how do we know? Well, let's get into it after I remind you of today's sponsor, E-Win Racing. E-Win Racing makes office chairs just like the one I'm sitting in right now. They have a bunch of different varieties for all shapes and sizes. I have an XL chair over at my desk. I don't really need an XL chair, but I wanted to just try out a different type of E-Win chair after using this one for years. And honestly, I couldn't be more happy with the product. I can't suggest it enough. You can check out E-Win Racing through the link down in the description and use code NINTENDOPRIME for 20% off. Also did you know it's a good time to get an E-Win chair because they now have the ability to split your payments up into four different payments using two completely different payment systems. I find this to be really, really nice for people that maybe can't afford. You know, they're $180 after discount chair today, but could afford to do four monthly payments. Look, it's just another way to get your E-Win chair. Highly suggest you go check out their website. Well, first, I need to give credit to the hiring post extraordinaire, the LinkedIn sleuth of sleuths when it comes to Nintendo related stuff, DOCTRAY81. You guys should definitely go check out his YouTube channel. He's a small content creator, but he's always been on top of this stuff. And when he is, we typically cover it because he's not boring us by giving us a random person on Twitter or someone on the reset era forums gave us information. Now, this person is legitimately looking at actual stuff that's out there and sharing it with all of us. And here's what we know, right? So according to LinkedIn profile and a hiring post, there is someone being hired for Call of Duty for a brand new studio and you might go, okay, so they're hiring someone for Call of Duty for a new unnamed studio. What's the big deal with this new studio? May in fact be related to Nintendo because as is listed on the top right corner of this post, five former Nintendo employees also have been hired for this studio. Five former Nintendo employees. Now this studio is going to be located in Texas and when you think about former Nintendo employees in Texas, you're probably thinking of retro studios. So it seems that there might be some former retro studio staff working at this studio. Five of them in relation to Nintendo directly. So this is a brand new studio. It's hiring more stuff, a UI designer in this case. Honestly, this does seem highly likely that it could be a specialized team working on Call of Duty games for Nintendo platforms. Now, are they working on something for Switch right now? I don't know. Are they working on something for the next generation of hardware? I don't know, but what does seem interesting is that we know all of the current Call of Duty studios. We know even the projected roadmap of Call of Duty games. What we don't know is what this new studio is doing with Call of Duty and why it has, you know, a handful of former Nintendo employees concentrated on it. We have no idea, but what we do know is that this is exciting to think about. The idea of Call of Duty either on Switch or future Nintendo hardware, obviously fulfilling the Microsoft promise, maybe with or without Microsoft. I do find it interesting that Activision seems to be dedicated to this now and spending money on this now. Obviously they would have to if there's going to be future support, but I do find it interesting that regardless of the acquisition going through, or maybe this is just a vote of confidence that Activision Blizzard thinks the acquisition is going to go through that they're just getting ahead of the game here, or maybe Microsoft strong armed them into starting this. I don't know how they can, they don't have any control of the company. I think it's interesting. I don't think Nintendo needs Call of Duty, obviously it doesn't. It is, according to VG charts, now sold over 120 million units.  They don't really have a lot of high quality military shooters there are. A few out there, we got Sniper Elite and a couple others, but nothing to the degree and level of Call of Duty. Obviously a lot of us would like to see Warzone and stuff come over. Look, I don't know what's going to happen with this studio if they are going to make Nintendo stuff, but it is notable they have a bunch of Nintendo former employees and it's a brand new Call of Duty studio when we see them nearly already know the road map for Call of Duty. So what is this studio doing? Well, it could be handling ports and or versions of Call of Duty specific for Nintendo. I think this is nothing but good news in this era where a lot of people talk about developers abandoning Nintendo. I find that, I find that remark to be quite interesting when people talk about AAA developers not supporting Switch because in the end they've never had full AAA support. We've had a few sparing games sure and in particular Bethesda was a pretty big supporter with the Wolfenstein, two Wolfenstein games and two Doom games, but they've also not released anything in Wolfenstein and Doom since the last ones. So, okay, how do we know that support has fallen off? Well, Microsoft bought them, so if that support was going to fall off because of that acquisition, well it was going to fall off anyways. There hasn't been a new Mortal Kombat game since the last Mortal Kombat game we had. There hasn't been a new Civilization game since the last Civ game we had and technically the new Diablo is not out yet and we got the last Diablo. I find it just really fascinating when we mention third party AAA support is falling off for Switch when one and never really had a ton of major AAA third party support in the first place. Example, Call of Duty's never been on Switch, but also the ones it did get we haven't had new versions of yet. You know, we got Skyrim, well we don't have the new Elder Scrolls, so how the hell would we know what's going to happen? It's kind of the frustrating part that comes out when people mention that now is the time for new hardware, which by the way, I want new hardware, but if your main argument is AAA games and we're not getting the AAA games, blah blah blah. We weren't getting the AAA games anyways. Like if this isn't new, it's been this way since launch and the games we did get haven't had sequels yet. You know what I mean? How do we know we won't get Mortal Kombat 12? Because Mortal Kombat 12 is not here. What are we talking about? There hasn't been a major AAA franchise that came to Switch that has new versions come out that we haven't gotten while we've gotten the previous ones. The only thing you can argue is maybe the fact we got the GTA trilogy, but we didn't get GTA V, I guess if you want to argue that, but we never had GTA V. And GTA V, running on Switch shouldn't be a problem, it runs on Xbox 360. Look, we've been down this road many, many times. People want new hardware. I want new hardware. A lot of these people clamoring over AAA games aren't people that really play Switch. Anyways, some that did buy Switch specifically for AAA games, you know, like oh well I played the Witcher and because it had cross days of the PC that's really cool. Where's our new Witcher game? Well, maybe you don't got that one, but what about Cyberpunk? I'm like okay, well Cyberpunk struggles to run on a PS4. What are we even talking about here?  Are we really going to go to the Cyberpunk route when they couldn't even make it run on the originally announced hardware? Let's just maybe hit pause on that. Maybe CD Projekt Red isn't the be all end all developer that we all thought they were after obviously the success of Witcher 2 and Witcher 3. And obviously the old ports and stuff they did to build up their company, you know what they bit off more than they could chew with Cyberpunk. I think I think it's not even controversial to say that. So my point is that I think Call of Duty coming to Switch is a good get. It is something we haven't had. If this studio is going to be working on it. I don't think it's going to be in anything this year, but it could mean something for 2024 or beyond, which obviously would be likely the next hardware. Hey, I'm excited about this. So you let me know if you're excited about Activision Blizzard seemingly building a team for Call of Duty with or without Microsoft for Nintendo. I think this is nothing but good news. I don't know how big the team is going to be. I'm assuming to be quite small, maybe 15, 20 people. That's about what you use to port games. So I think that that could be what this is a port studio, specifically targeting Nintendo hardware. And I'm very interested to see what they have coming right now.  Black Ops 2 was really good back on the Wii U. So I would love to see that come back in a remaster on Switch. Anyways, I'm just throwing out a possibility for like a really quick game. Maybe they could get out this year. But I am with Andrew Rubble Jets from Nintendo Prime. You guys, let me know what you think about this down in the comments below. And I'll catch you in the next video.