>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 Special coverage sponsored by AWS Worldwide Public sector Welcome back to the cubes coverage. This is the Cube virtual in our coverage of AWS reinvent with special coverage of the worldwide public sector day. I'm your host, John Firrea. We are the Cube, and I'm joined by Trayvon's hyper scaler partner. Leave with Red Hat. Trey, Welcome to the Cube. >>Thank you. Great to be here, John. Very happy to be at my first virtual reinvent, but probably my third in a row reinvented itself. >>You know, it's super exciting and usually were in person, as you mentioned. But the Cube virtual your virtual. We gotta do it virtual this year, but the game is still the same. It's about learning is about getting updates on what's relevant for customers with the pandemic. A lot of things have been highlighted, and this has been the big fun of reinvent because you mentioned three years. This is our eighth year. We've been there every year since the since the except for the first year, but you just look at the growth right, but it's still the same cadence of more news, more announcements, more higher level services, you know, with with open shift We've been following that with kubernetes and containers Service meshes. You're seeing micro services. All this coming together around open source and public sector is the main benefit of that. Right now, if you look at most interviews that I've done, the mandate for change in public sector is multifold in every vertical education to military, right. So So there's a need to get off your butt and get going with cloud if you're in public sector, um, tell us more about Red hat and the partnership around public sector, because I think that's really what we want to dig into. >>Absolutely. And there definitely have been, uh, changes this year that have inspired innovation. Uh, Red hat native us have been on a path for innovation for quite a while. Red hat in working with the open source community and taking an iterative approach to what we call upstream first, which is essentially, uh, to develop, uh, in the open source communities to mature those into enterprise grade products and then thio iterative Lee, take those findings back to the open source community. So Red Hat and eight of us have had a long history of collaboration. Starting all the way back in 2007 with Red Hat Enterprise Linux being available within the AWS console continue on to things like AWS Quick starts, which are reference architectures for how to deploy products that you're managing yourself on then, More recently, recent being the last say, four years, Uh, Thio offer a open shift managed service within a W s. And now continuing that with a joint offering that's gonna be forthcoming. That's the Red had open shift service on AWS, which will be the first native offering and joint offering with a W s by A by a third party such as ourselves. So there's a history of innovation there in a history of collaboration, and I think we'll talk a little bit later on in the interview specifically about how that relates to public sector and their unique needs. >>Yeah, well, let's just get in there. What are the some of the unique needs? Because there's value in your partnership with AWS. You laid out a bunch of those services, so certainly there's customers that are in need. What specific requirements are there. Can you tell us how Red Hat and A W s work together to meet these challenges? >>Sure. So the public sector group is composed of many organizations and agencies both. When I think of public sector, I think of the federal civilian space. I think about the D. O. D uh, the state and local and education. All of those elements of public sector have different needs. But there are some standards that are very pervasive in the public sector, things like Phipps and how you articulate your compliance with particular validated cryptographic modules or with how you express a control statement using something like the uh minus 853 which is critically important for cloud service offerings. And so those are some of the things that Red Hat native us have a heritage of working together on also providing deep explanations for those organizations and their mission so that they can comfortably move into the cloud, do digital transformation by taking applications that maybe on Prem today and having the confidence to move those into the cloud with security and compliance at the forefront. So when I think about the overall mission of government and then the threats to that mission, whether they be state actors, you know, individuals there are serious. They're serious solutions that have been developed both in the open source community to provide greater visibility into security. And there are things that the government has done to kind of create frameworks for compliance. And those are things that we work with, uh, in the open. So we have, ah, process that we call Compliance is code which can be found both inside of repositories like git Hub. But also on our website, where we articulate how our products actually work with those compliance frameworks, uh, the cryptographic a while authorizations and some of the certifications for technology that the government's put forward. >>So if it's compliance, is code like infrastructure is code, which is Dev Ops. What do you call it? Gov. Dev Ops or Gove ops Compliant ops. It's kind of get a little Dev ops vibe there. I mean, this is a really real question. I mean, you're talking about making compliance, automated. This is what Dev ops is all about, right? And this is this is kind of where it's going. How do you how do you expand more on that? Take a minute to explain. >>Sure. So it's a red hat. Over the last 20 plus years has been doing things that are now called Dev Ops or Dev SEC ops any number of combinations of those words. But the reality is that we've worked in in things like small teams. We've worked to make things like micro services, where you have a very well defined and discreet service that could be scaled up and then that's been incorporated into our products. But not only that, we release those things back Thio the open source community to make the broader Linux platform, for example, the broader kubernetes platform to make those things, uh stronger onto also get more visibility to some of those security items. So that there is a level of trust that you can have in the software supply chain is being created not only with ease, but the things that the customers of building based on these solutions. >>Yeah, that's a good point. Trust and all that compliance is, too. But also when you have that trust, now you have a product you wanna actually deploy it or have customers consume it. Um, it hasn't always been easy trade and cover. You got Fed ramp. I mean, I talked to Teresa cross about this all the time at a W s. You know, there's all kinds of, you know, things. You got hoops you gotta jump through. How are you guys making that? Easier, Because again, that's another concern you got. You guys got a great channel. You got the upstream. First, you've got the open source. Um, you know, enterprises certainly do great. And now you're doing great in public sector. How you guys making it easier for partners to on Ram Pinto. All these Fed programs? >>Yeah. So what I think about the application transformation that organizations are going through we have, especially in the open shift environment. We have what we call the operator framework, which allows operational knowledge to be used as code on. That's gonna be a kind of a running theme for us, but to be able to do these things as code, uh, whether it's things like our compliance operator, which allow you to do testing of a production environment, uh, testing of operational elements of your infrastructure to be able to test them for compliance is Phipps enabled our cryptographic libraries being used, and at what levels are they being used by simply the operating system where they're being used in the kubernetes environment? Are they even being used toe access AWS services? So one of the big things that is important for redhead customers that are moving into the cloud is the depth at which we can leverage the cloud provider services such as the AWS services, but also bring new application services that the customer may be familiar with on Prem, bring those into the environment and then be able to test. So you trust. But you verify on you provide that visibility and ultimately that accountability to the customer that is interested in using your solution in the cloud. And that's what one of those success criterias is gonna bay. >>Yeah, and speed to is a big theme. We're hearing speed agility. I mean, Julie has been talked about all time with Dev ops deficit cops, and you know all these ops automation, but speed deployment. This brings up to the point about we kind of teed up a little bit of the top of the interview, but there's been a big year for disruption, pandemic uncertainty, polarized political environment. Geopolitical. You got stuff in space congestion contention. There you got the edge of the network exploding. So we all new paradigm shifting going on everywhere, right? So, you know, and all the all the turmoil pandemic specifically has been driving a lot of change. How has all this disruption accelerated the public sector cloud journey? Because we were talking earlier, You know, the public sector and didn't have a big I T budget that was never super funded. Like enterprises, they're not flush with cash on board. The motivation was to kind of go slow. Not anymore. Sure anymore, >>I think. Ah, lot of organizations have drawn inspiration from those factors, right? So you have these factors that say that you have a limited budget on that necessity brings out the innovation right, And the especially for government organizations, the the the spirit of the innovation is something that runs deep in the culture. And when faced with those kinds of things, they actually rise to the occasion. And so I think about things like the US Navy's compiled to combat 24 program which were part of and that program is leveraging things like automation, dep, SEC ops and the agile methods to create new capabilities and new software on, as the program name says, it's compiled to combat in 24 hours. So the idea is that you can have software that is created a new capability deployed and in theater, uh, within a short period of time. That's very agile, and it's also ah, very innovative thing, and that's all leveraging red hats portfolio of products. But it's also their vision that and their methodology to actually bring that toe life. So we're very fortunate and very glad to be a part of that and continue to iterating that that way. >>It's nice to be on the road map of the product requirements that are needed now. They're never because the speed is super important and the role of data and all the things that you're doing and open source drives that trade Great to have you on sharing your insight. What? Just a personal question. Hyper scale partner leaders, your title. What does that mean? It means you're going to hyper scales. You're hyper scale who your partner is. Just take a minute to explain what you do it. It's fascinating. It >>definitely means that I'm hyper scale 100% thea Other thing It means we view the cloud service providers as hyper scale er's right. They have capacity on demand pay As you go this very elastic nature to what they do, they offer infrastructure a za service that you can then use for the foundations of your solutions. So as a hyper scale partner leader, what I do is I worked very closely with the AWS team. I actually super long story short. I came from a W S after spending about three years there, so understand it pretty well on, uh, in this particular case, I am working with them to bring the whole portfolio of red hat products, uh, not only onto the cloud for customers to consume in a self directed manner, but also as we build out more of these managed services across application services A i m l A Z you mentioned with things like co vid, uh, there are discrete examples of things like business process, management decision making, that air used in hospitals and inside of, uh, places within the government. You know, uh, that are really wrestling with these decisions. So I'm very pleased with, you know, the relationship that we have with a W s. They're great partner. It's a great opportunity to talk. Especially now it reinvent So these are all really good things and really excited Thio be the hyper scale partner leader. >>That's great that you have that they had the DNA from the best. You know how to do the working backwards stuff. You know, the cultures, both technical cultures. So very customer centric. So nice fit. Thank you for sharing that. And thanks for the insight into, uh, reinvent and red hat. Thank you. >>All right, that was great to be here and look forward to learning a lot. This reinvent >>great. We'll see on the interwebs throughout the next couple of weeks. Trayvon's hyper scale partner manager Really putting in the cloud to Red Hat and customers and public sector. This is our special coverage of the public sector day here at reinvent and ongoing coverage Cube virtual throughout the next couple weeks. John, for your host. Thanks for watching. Yeah,

>> live from Boston, Massachusetts. It's the queue covering your red. Have some twenty nineteen brought to you by bread. Welcome back a few, but our way Our red have some twenty nineteen >> center along with Sue Mittleman. I'm John Walls were now joined by Robin Goldstone, who's HBC solution architect at the Lawrence Livermore National Laboratory. Hello, Robin >> Harrier. Good to see you. I >> saw you on the Keystone States this morning. Fascinating presentation, I thought. First off for the viewers at home who might not be too familiar with the laboratory If you could please just give it that thirty thousand foot level of just what kind of national security work you're involved with. >> Sure. So yes, indeed. We are a national security lab. And you know, first and foremost, our mission is assuring the safety, security reliability of our nuclear weapons stockpile. And there's a lot to that mission. But we also have broader national security mission. We work on counterterrorism and nonproliferation, a lot of of cyber security kinds of things. And but even just general science. We're doing things with precision medicine and and just all all sorts >> of interesting technology. Fascinating >> Es eso, Robin, You know so much and i t you know, the buzzword. The vast months years has been scaled on. We talk about what public loud people are doing. It's labs like yours have been challenged. Challenge with scale in many other ways, especially performance is something that you know, usually at the forefront of where things are you talked about in the keynote this morning. Sierra is the latest generation supercomputer number two, you know, supercomputer. So you know, I don't know how many people understand the petaflop one hundred twenty five flops and the like, but tell us a little bit about, you know, kind of the why and the what of that, >> right? So So Sierra's a supercomputer. And what's unique about these systems is that we're solving. There's lots of systems that network together. Maybe you're bigger number of servers than us, but we're doing scientific simulation, and that kind of computing requires a level of parallelism and very tightly coupled. So all the servers are running a piece of the problem. They all have to sort of operate together. If any one of them is running slow, it makes the whole thing goes slow. So it's really this tightly couple nature of super computers that make things really challenging. You know, we talked about performance. If if one servers just running slow for some reason, you know everything else is going to be affected by that. So we really do care about performance. And we really do care about just every little piece of the hardware you know, performing as it should. So So I >> think in national security, nuclear stockpiles. Um I mean, there is nothing more important, obviously, than the safety and security of the American people were at the center of that. Right? You're open source, right? You know, how does that work? How does that? Because as much trust and faith and confidence we have in the open source community. This is an extremely important responsibility that's being consigned more less to this open source community. >> Sure. You know, at first, people do have that feeling that we should be running some secret sauce. I mean, our applications themselves or secret. But when it comes to the system software and all the software around the applications, I mean, open source makes perfect sense. I mean, we started out running really closed source solutions in some cases, the perp. The hardware itself was really proprietary. And, of course, the vendors who made the hardware proprietary. They wanted their software to be proprietary. But I think most people can resonate when you buy a piece of software and the vendor tells you it's it's great. It's going to do everything you needed to do and trust us, right? Okay, But at our scale, it often doesn't work the way it's It's supposed to work. They've never tested it. Our skill. And when it breaks, now they have to fix. They're the only ones that can fix it. And in some cases we found it wasn't in the vendors decided. You know what? No one else has one quite like yours. And you know, it's a lot of work to make it work for you. So we're just not going to fix and you can't wait, right? And so open source is just the opposite of that, right? I mean, we have all that visibility in that software. If it doesn't work for our needs, we can make it work for our needs, and then we can give it back to the community. Because even though people are doing things that the scale that we are today, Ah, lot of the things that we're doing really do trickle down and can be used by a lot of other people. >> But it's something really important because, as you said, you used to be and I was like, OK, the Cray supercomputer is what we know, You know, let's use proprietary interfaces and I need the highest speed and therefore it's not the general purpose stuff. You moved X eighty six. Lennox is something that's been in the shower computers. Why? But it's a finely tuned version there. Let's get you know, the duct tape and baling wire. And don't breathe on it once you get it running. You're running well today and you talk a little bit about the journey with Roland. You know, now on the Super Computers, >> right? So again, there's always been this sort of proprietary, really high end supercomputing. But about in the late nineteen nineties, early two thousand, that's when we started building these these commodity clusters. You know, at the time, I think Beta Wolf was the terminology for that. But, you know, basically looking at how we could take these basic off the shelf servers and make them work for our applications and trying to take advantage of a CZ much commodity technologies we can, because we didn't want to re invent anything. We want to use as much as possible. And so we've really written that curve. And initially it was just red hat. Lennox. There was no relative time, but then when we started getting into the newer architectures going from Mexico six. Taxi, six, sixty for and Itanium, you know the support just wasn't there in basic red hat and again, even though it's open source and we could do everything ourselves, we don't want to do everything ourselves. I mean, having an organization having this Enterprise edition of Red Hat having a company stand behind it. The software is still open. Source. We can look at the source code. We can modify it if we want, But you know what at the end of the day, were happy to hand over some of our challenge is to Red Hat and and let them do what they do best. They have great, you know, reach into the into the colonel community. They can get things done that we can't necessarily get done. So it's a great relationship. >> Yes. So that that last mile getting it on Sierra there. Is that the first time on one kind of the big showcase your computer? >> Sure. And part of the reason for that is because those big computers themselves are basically now mostly commodity. I mean, again, you talked about a Cray, Some really exotic architecture. I mean, Sierra is a collection of Lennox servers. Now, in this case, they're running the power architecture instead of X eighty six. So Red hat did a lot of work with IBM to make sure that that power was was fully supported in the rail stack. But so, you know, again that the service themselves somewhat commodity were running and video GP use those air widely used everywhere. Obviously big deal for machine learning and stuff that the main the biggest proprietary component we're still dealing was is thie interconnect. So, you know, I mentioned these clusters have to be really tightly coupled. They that performance has to be really superior and most importantly, the latent see right, they have to be super low late and see an ethernet just doesn't cut it >> So you run Infinite Band today. I'm assuming we're >> running infinite band on melon oxen finna ban on Sierra on some of our commodity clusters. We run melon ox on other ones. We run intel. Omni Path was just another flavor of of infinite band. You know, if we could use it, if we could use Ethernet, we would, because again, we would get all the benefit in the leverage of what everybody else is doing, but just just hasn't hasn't quite been able to meet our needs in that >> area now, uh, find recalled the history lesson. We got a bit from me this morning. The laboratory has been around since the early fifties, born of the Cold War. And so obviously open source was, you know? Yeah, right, you know, went well. What about your evolution to open source? I mean, ahs. This has taken hold. Now, there had to be a tipping point at some point that converted and made the laboratory believers. But if you can, can you go back to that process? And was it of was it a big moment for you big time? Or was it just a kind of a steady migration? tour. >> Well, it's interesting if you go way back. We actually wrote the operating systems for those early Cray computers. We wrote those operating systems in house because there really was no operating system that will work for us. So we've been software developers for a long time. We've been system software developers, but at that time it was all proprietary in closed source. So we know how to do that stuff. The reason I think really what happened was when these commodity clusters came along when we showed that we could build a, you know, a cluster that could perform well for our applications on that commodity hardware. We started with Red Hat, but we had to add some things on top. We had to add the software that made a bunch of individual servers function as a cluster. So all the system management stuff the resource manager of the thing that lets a schedule jobs, batch jobs. We wrote that software, the parallel file system. Those things did not exist in the open source, and we helped to write those things, and those things took on lives of their own. So luster. It's a parallel file system that we helped develop slow, Erm, if anyone outside of HBC probably hasn't heard of it, but it's a resource manager that again is very widely popular. So the lab really saw that. You know, we got a lot of visibility by contributing this stuff to the community. And I think everybody has embracing. And we develop open source software at all different layers. This >> software, Robin, you know, I'm curious how you look at Public Cloud. So, you know, when I look at the public odd, they do a lot with government agencies. They got cloud. You know, I've talked to companies that said I could have built a super computer. Here's how long and do. But I could spend it up in minutes. And you know what I need? Is that a possibility for something of yours? I understand. Maybe not the super high performance, But where does it fit in? >> Sure, Yeah. I mean, certainly for a company that has no experience or no infrastructure. I mean, we have invested a huge amount in our data center, and we have a ton of power and cooling and floor space. We have already made that investment, you know, trying to outsource that to the cloud doesn't make sense. There are definitely things. Cloud is great. We are using Gove Cloud for things like prototyping, or someone wants a server, that some architecture, that we don't have the ability to just spin it up. You know, if we had to go and buy it, it would take six months because you know, we are the government. But be able to just spin that stuff up. It's really great for what we do. We use it for open source for building test. We use it to conferences when we want to run a tutorial and spin up a bunch of instances of, you know, Lennox and and run a tutorial. But the biggest thing is at the end of the day are our most important work. Clothes are on a classified environment, and we don't have the ability to run those workloads in the cloud. And so to do it on the open side and not be ableto leverage it on the close side, it really takes away some of the value of because we really want to make the two environments look a similar is possible leverage our staff and and everything like that. So that's where Cloud just doesn't quite fit >> in for us. You were talking about, you know, the speed of, Of of Sierra. And then also mentioning El Capitan, which is thie the next generation. You're next, You know, super unbelievably fast computer to an extent of ten X that off current speed is within the next four to five years. >> Right? That's the goal. I >> mean, what those Some numbers that is there because you put a pretty impressive array up there, >> right? So Series about one hundred twenty five PETA flops and are the big Holy Grail for high performance computing is excess scale and exit flop of performance. And so, you know, El Capitan is targeted to be, you know, one point two, maybe one point five exit flops or even Mohr again. That's peak performance. It doesn't necessarily translate into what our applications, um, I can get out of the platform. But the reason you keep sometimes I think, isn't it enough isn't one hundred twenty five five's enough, But it's never enough because any time we get another platform, people figure out how to do things with it that they've never done before. Either they're solving problems faster than they could. And so now they're able to explore a solution space much faster. Or they want to look at, you know, these air simulations of three dimensional space, and they want to be able to look at it in a more fine grain level. So again, every computer we get, we can either push a workload through ten times faster. Or we can look at a simulation. You know, that's ten times more resolved than the one that >> we could do before. So do this for made and for folks at home and take the work that you do and translate that toe. Why that exponential increase in speed will make you better. What you do in terms of decision making and processing of information, >> right? So, yeah, so the thing is, these these nuclear weapons systems are very complicated. There's multi physics. There's lots of different interactions going on, and to really understand them at the lowest level. One of the reasons that's so important now is we're maintaining a stockpile that is well beyond the life span that it was designed for. You know, these nuclear weapons, some of them were built in the fifties, the sixties and seventies. They weren't designed to last this long, right? And so now they're sort of out of their design regime, and we really have to understand their behaviour and their properties as they age. So it opens up a whole nother area, you know, that we have to be able to floor and and just some of that physics has never been explored before. So, you know, the problems get more challenging the farther we get away from the design basis of these weapons, but also were really starting to do new things like eh, I am machine learning things that weren't part of our workflow before. We're starting to incorporate machine learning in with simulation again to help explore a very large problem space and be ableto find interesting areas within a simulation to focus in on. And so that's a really exciting area. And that is also an area where, you know, GPS and >> stuff just exploded. You know, the performance levels that people are seeing on these machines? Well, we thank you for your work. It is critically important, azaz, we all realize and wonderfully fascinating at the same time. So thanks for the insights here on for your time. We appreciate that. >> All right, Thanks for >> thanking Robin Goldstone. Joining us back with more here on the Cube. You're watching our coverage live from Boston of Red Hat Summit twenty nineteen.