welcome back to the seaport in boston massachusetts with cities crazy with bruins and celtics talk but we're here we're talking red hat linux open shift ansible and ashesh badani is here he's the senior vice president and the head of products at red hat fresh off the keynotes had amex up in the state of great to see you face to face amazing that we're here now after two years of of the isolation economy welcome back thank you great to see you again as well and you as well paul yeah so no shortage of announcements uh from red hat this week paul wrote a piece on siliconangle.com i got my yellow highlights i've been through all the announcements which is your favorite baby hard for me to choose hard for me to choose um i'll talk about real nine right well nine's exciting um and in a weird way it's exciting because it's boring right because it's consistent three years ago we committed to releasing a major well uh every three years right so customers partners users can plan for it so we released the latest version of rel in between we've been delivering releases every six months as well minor releases a lot of capabilities that are bundled in around security automation edge management and then rel is also the foundation of the work we announced with gm with the in-vehicle operating system so you know that's extremely exciting news for us as well and the collaboration that we're doing with them and then a whole host of other announcements around you know cloud services work around devsecops and so on so yeah a lot of news a lot of announcements i would say rel nine and the work with gm probably you know comes right up to the top i wanted to get to one aspect of the rail 9 announcement that is the the rose centos streams in that development now in december i think it was red hat discontinued development or support for for centos and moved to central streams i'm still not clear what the difference is between the two can you clarify that i think we go into a situation especially with with many customers many partners as well that you know didn't sort of quite exactly uh get a sense of you know where centos was from a life cycle perspective so was it upstream to rel was it downstream to rel what's the life cycle for itself as well and then there became some sort of you know implied notions around what that looked like and so what we decided was to say well we'll make a really clean break and we'll say centos stream is the upstream for enterprise linux from day one itself partners uh you know software partners hardware partners can collaborate with us to develop rel and then take it all the way through life cycle right so now it becomes a true upstream a true place for development for us and then rel essentially comes uh out as a series of releases based on the work that we do in a fast-moving center-os environment but wasn't centos essentially that upstream uh development environment to begin with what's the difference between centos stream yeah it wasn't wasn't um it wasn't quite upstream it was actually a little bit downstream yeah it was kind of bi-directional yeah and yeah and so then you know that sort of became an implied life cycle to it when there really wasn't one but it was just became one because of some usage and adoption and so now this really clarifies the relationship between the two we've heard feedback for example from software partners users saying hey what do i do for development because i used you know centervis in the past we're like yup we have real for developers available we have rel for small teams available we have rel available for non-profit organizations up and so we've made rail now available in various form factors for the needs that folks had and they were perhaps using centos for because there was no such alternative or rel history so language so now it's this clarity so that's really the key point there so language matters a lot in the technology business we've seen it over the years the industry coalesces around you know terminology whether it was the pc era everything was pc this pc that the internet era and and certainly the cloud we we learned a lot of language from the likes of you know aws two pizza teams and working backwards and things like that became common commonplace hybrid and multi-cloud are kind of the the parlance of the day you guys use hybrid you and i have talked about this i feel like there's something new coming i don't think my term of super cloud is the right necessary terminology but it signifies something different and i feel like your announcements point to that within your hybrid umbrella point being so much talk about the edge and it's we heard paul cormier talk about new hardware architectures and you're seeing that at the edge you know what you're doing with the in-vehicle operating system these are new the cloud isn't just a a bunch of remote services in the cloud anymore it's on-prem it's a cloud it's cross-clouds it's now going out to the edge it's something new and different i think hybrid is your sort of term for that but it feels like it's transcending hybrid are your thoughts you know really really great question actually since you and i talked dave i've been spending some time you know sort of noodling just over that right and you're right right there's probably some terminology something sort of you know that will get developed you know either by us or you know in collaboration with the industry you know where we sort of almost have the connection almost like a meta cloud right that we're sort of working our way towards because there's if you will you know the cloud right so you know on premise you know virtualized uh bare metal by the way you know increasingly interesting and important you know we do a lot of work with nvidia folks want to run specific workloads there we announced support for arm right another now popular architecture especially as we go out to the edge so obviously there's private cloud public cloud then the edge becomes a continuum now you know on that process we actually have a major uh uh shipping company so uh a cruise lines that's talking about using openshift on cruise lines right so you know that's the edge right last year we had verizon talking about you know 5g and you know ran in the next generation there to then that's the edge when we talk to retail the store front's the edge right you talk to a bank you know the bank environments here so everyone's got a different kind of definition of edge we're working with them and then when we you know announce this collaboration with gm right now the edge there becomes the automobile so if you think of this as a continuum right you know bare metal private cloud public cloud take it out to the edge now we're sort of almost you know living in a world of you know a little bit of abstractions and making sure that we are focused on where uh data is being generated and then how can we help ensure that we're providing a consistent experience regardless of you know where meta meta cloud because i can work in nfts i can work a little bit we're going to get through this whole thing without saying metaverse i was hoping i do want to ask you about about the edge and the proliferation of hardware platforms paul comey mentioned this during the keynote today hardware is becoming important yeah there's a lot of people building hardware it's in development now for areas like uh like intelligent devices and ai how does this influence your development priorities you have all these different platforms that you need to support yeah so um we think about that a lot mostly because we have engagements with so many partners hardware right so obviously there's more traditional partners i'd say like the dell and the hpes that we work with we've historically worked with them also working with them in in newer areas uh with regard to appliances that are being developed um and then the work that we do with partners like nvidia or new architectures like arm and so our perspective is this will be uh use case driven more than anything else right so there are certain environments right where you have arm-based devices other environments where you've got specific workloads that can take advantage of being built on gpus that we'll see increasingly being used especially to address that problem and then provide a solution towards that so our belief has always been look we're going to give you a consistent platform a consistent abstraction across all these you know pieces of hardware um and so you mr miss customer make the best choice for yourself a couple other areas we have to hit on i want to talk about cloud services we've got to talk about security leave time to get there but why the push to cloud services what's driving that it's actually customers they're driving right so we have um customers consistently been asking us say you know love what you give us right want to make sure that's available to us when we consume in the cloud so we've made rel available for example on demand right you can consume this directly via public cloud consoles we are now making available via marketplaces uh talked about ansible available as a managed service on azure openshift of course available as a managed service in multiple clouds um all of this also is because you know we've got customers who've got these uh committed spends that they have you know with cloud providers they want to make sure that the environments that they're using are also counting towards that at the same time give them flexibility give them the choice right if in certain situations they want to run in the data center great we have that solution for them other cases they want to procure from the cloud and run it there we're happy to support them there as well let's talk about security because you have a lot of announcements like security everywhere yeah um and then some specific announcements as well i i always think about these days in the context of the solar wind supply chain hack would this have you know how would this have affected it but tell us about what's going on in security your philosophy there and the announcements that you guys made so our secure announcements actually span our entire portfolio yeah right and and that's not an accident right that's by design because you know we've really uh been thinking and emphasizing you know how we ensure that security profile is raised for users both from a malicious perspective and also helping accidental issues right so so both matters so one huge amounts of open source software you know out of the world you know and then estimates are you know one in ten right has some kind of security vulnerability um in place a massive amount of change in where software is being developed right so rate of change for example in kubernetes is dramatic right much more than even than linux right entire parts of kubernetes get rewritten over over a three-year period of time so as you introduce all that right being able to think for example about you know what's known as shift left security or devsec ops right how do we make sure we move security closer to where development is actually done how do we ensure we give you a pattern so you know we introduced a software supply chain pattern uh via openshift delivers complete stack of code that you know you can go off and run that follows best practices uh including for example for developers you know with git ops and support on the pipelines front a whole bunch of security capabilities in rel um a new image integrity measurement architecture which allows for a better ability to see in a post install environment what the integrity of the packages are signing technology they're incorporating open shift as well as an ansible so it's it's a long long list of cables and features and then also more and more defaults that we're putting in place that make it easier for example for someone not to hurt themselves accidentally on security front i noticed that uh this today's batch of announcements included support within openshift pipelines for sigstor which is an open source project that was birthed actually at red hat right uh we haven't heard a whole lot about it how important is zig store to to you know your future product direction yeah so look i i think of that you know as you know work that's you know being done out of our cto's office and obviously security is a big focus area for them um six store's great example of saying look how can we verify content that's in uh containers make sure it's you know digitally signed that's appropriate uh to be deployed across a bunch of environments but that thinking isn't maybe unique uh for us uh in the container side mostly because we have you know two decades or more of thinking about that on the rel side and so fundamentally containers are being built on linux right so a lot of the lessons that we've learned a lot of the expertise that we've built over the years in linux now we're starting to you know use that same expertise trying to apply it to containers and i'm my guess is increasingly we're going to see more of the need for that you know into the edge as well i i i picked up on that too let me ask a follow-up question on sigstor so if i'm a developer and i and i use that capability it it ensures the provenance of that code is it immutable the the signature uh and the reason i ask is because again i think of everything in the context of the solar winds where they were putting code into the the supply chain and then removing it to see what happened and see how people reacted and it's just a really scary environment yeah the hardest part you know in in these environments is actually the behavior change so what's an example of that um packages built verified you know by red hat when it went from red hat to the actual user have we been able to make sure we verify the integrity of all of those when they were put into use um and unless we have behavior that you know make sure that we do that then we find ourselves in trouble in the earliest days of open shift uh we used to get knocked a lot by by developers because i said hey this platform's really hard to use we investigate hey look why is that happening so by default we didn't allow for root access you know and so someone's using you know the openshift platform they're like oh my gosh i can't use it right i'm so used to having root access we're like no that's actually sealed by default because that's not a good security best practice now over a period of time when we you know randomly enough times explained that enough times now behavior changes like yeah that makes sense now right so even just kind of you know there's behaviors the more that we can do for example in in you know the shift left which is one of the reasons by the way why we bought uh sac rocks a year right right for declarative security contain native security so threat detection network segmentation uh watching intrusions you know malicious behavior is something that now we can you know essentially make native into uh development itself all right escape key talk futures a little bit so i went downstairs to the expert you know asked the experts and there was this awesome demo i don't know if you've seen it of um it's like a design thinking booth with what happened how you build an application i think they were using the who one of their apps um during covet and it's you know shows the the granularity of the the stack and the development pipeline and all the steps that have to take place and it strikes me of something we've talked about so you've got this application development stack if you will and the database is there to support that and then over here you've got this analytics stack and it's separate and we always talk about injecting more ai into apps more data into apps but there's separate stacks do you see a day where those two stacks can come together and if not how do we inject more data and ai into apps what are your thoughts on that so great that's another area we've talked about dave in the past right um so we definitely agree with that right and and what final shape it takes you know i think we've got some ideas around that what we started doing is starting to pick up specific areas where we can start saying let's go and see what kind of usage we get from customers around it so for example we have openshift data science which is basically a way for us to talk about ml ops right and you know how can we have a platform that allows for different models that you can use we can uh test and train data different frameworks that you can then deploy in an environment of your choice right and we run that uh for you up and assist you in in uh making sure that you're able to take the next steps you want with with your machine learning algorithms um there's work that we've uh introduced at summit around databases service so essentially our uh a cloud service that allows for deep as an easy way for customers to access either mongodb or or cockroach in a cloud native fashion and all of these things that we're sort of you know experimenting with is to be able to say look how do we sort of bring the world's closer together right off database of data of analytics with a core platform and a core stack because again right this will become part of you know one continuum that we're going to work with it's not i'd like your continuum that's that's i think really instructive it's not a technical barrier is what i'm hearing it's maybe organizational mindset i can i should be able to insert a column into my my my application you know development pipeline and insert the data i mean kafka tensorflow in there there's no technical reason i can't can't do that it's just we've created these sort of separate stovepipe organizations 100 right right so they're different teams right you've got the platform team or the ops team and you're a separate dev team there's a separate data team there's a separate storage team and each of them will work you know slightly differently independently right so the question then is i mean that's sort of how devops came along then you're like oh wait a minute yeah don't forget security and now we're at devsecops right so the more of that that we can kind of bring together i think the more convergence that we'll see when i think about the in-vehicle os i see the the that is a great use case for real-time ai inferencing streaming data i wanted to ask you that about that real quickly because at the very you know just before the conference began we got an announcement about gm but your partnership with gm it seems like this came together very quickly why is it so important for red hat this is a whole new category of application that you're going to be working on yeah so we've been working with gm not publicly for a while now um and it was very clear that look you know gm believes this is the future right you know electric vehicles into autonomous driving and we're very keen to say we believe that a lot of attributes that we've got in rel that we can bring to bear in a different form factor to assist with the different needs that exist in this industry so one it's interesting for us because we believe that's a use case that you know we can add value to um but it's also the future of automotive right so the opportunity to be able to say look we can get open source technology we can collaborate out with the community to fundamentally help transform that industry uh towards where it wants to go you know that that's just the passion that we have that you know is what wakes us up every morning you're opening into that yeah thank you for coming on the cube really appreciate your time and your insights and uh have a great rest of rest of the event thank you for having me metacloud it's a thing it's a thing right it's it's it's kind of there we're gonna we're gonna see it emerge over the next decade all right you're watching the cube's coverage of red hat summit 2022 from boston keep it right there be right back you

(upbeat electronic music plays) >> Hey everyone, welcome back to theCube's coverage of .NEXT 2021 Virtual. I'm John Furrier, hosts of theCube. We have two great guests, Rajiv Mirani, who's the Chief Technology Officer, and Thomas Cornely, SVP of Product Management. Day Two keynote product, the platform, announcements, news. A lot of people, Rajiv, are super excited about the, the platform, uh, moving to a subscription model. Everything's kind of coming into place. How are the customers, uh, seeing this? How they adopted hybrid cloud as a hybrid, hybrid, hybrid, data, data, data? Those are the, those are the, that's the, that's where the puck is right now. You guys are there. How are customers seeing this? >> Mirani: Um, um, great question, John, by the way, great to be back here on theCube again this year. So when we talk to our customers, pretty much, all of them agreed that for them, the ideal state that they want to be in is a hybrid world, right? That they want to essentially be able to run both of those, both on the private data center and the public cloud, and sort of have a common platform, common experience, common, uh, skillset, same people managing, managing workloads across both locations. And unfortunately, most of them don't have that that tooling available today to do so, right. And that's where the platform, the Nutanix platform's come a long way. We've always been great at running in the data center, running every single workload, we continue to make great strides on our core with the increased performance for, for the most demanding, uh, workloads out there. But what we have done in the last couple of years has also extended this platform to run in the public cloud and essentially provide the same capabilities, the same operational behavior across locations. And that's when you're seeing a lot of excitement from our customers because they really want to be in that state, for it to have the common tooling across work locations, as you can imagine, we're getting traction. Customers who want to move workloads to public cloud, they don't want to spend the effort to refactor them. Or for customers who really want to operate in a hybrid mode with things like disaster recovery, cloud bursting, workloads like that. So, you know, I think we've made a great step in that direction. And we look forward to doing more with our customers. >> Furrier: What is the big challenge that you're seeing with this hybrid transition from your customers and how are you solving that specifically? >> Mirani: Yeah. If you look at how public and private operate today, they're very different in the kind of technologies used. And most customers today will have two separate teams, like one for their on-prem workloads, using a certain set of tooling, a second completely different team, managing a completely different set of workloads, but with different technologies. And that's not an ideal state in some senses, that's not true hybrid, right? It's like creating two new silos, if anything. And our vision is that you get to a point where both of these operate in the same manner, you've got the same people managing all of them, the same workloads anyway, but similar performance, similar SaaS. So they're going to literally get to point where applications and data can move back and forth. And that's, that's, that's where I think the real future is for hybrid >> Furrier: I have to ask you a personal question. As the CTO, you've got be excited with the architecture that's evolving with hybrid and multi-cloud, I mean, I mean, it's pretty, pretty exciting from a tech standpoint, what is your reaction to that? >> Mirani: %100 and it's been a long time coming, right? We have been building pieces of this over years. And if you look at all the product announcements, Nutanix has made over the last few years and the acquisitions that made them and so on, there's been a purpose behind them. That's been a purpose to get to this model where we can operate a customer's workloads in a hybrid environment. So really, really happy to see all of that come together. Years and years of work finally finally bearing fruit. >> Furrier: Well, we've had many conversations in the past, but it congratulates a lot more to do with so much more action happening. Thomas, you get the keys to the kingdom, okay, and the product management you've got to prioritize, you've got to put it together. What are the key components of this Nutanix cloud platform? The hybrid cloud, multi-cloud strategy that's in place, because there's a lot of headroom there, but take us through the key components today and then how that translates into hybrid multi-cloud for the future. >> Cornely: Certainly, John, thank you again and great to be here, and kind of, Rajiv, you said really nicely here. If you look at our portfolio at Nutanix, what we have is great technologies. They've been sold as a lot of different products in the past, right. And what we've done last few months is we kind of bring things together, simplify and streamline, and we align everything around a cloud platform, right? And this is really the messaging that we're going after is look, it's not about the price of our solutions, but business outcomes for customers. And so are we focusing on pushing the cloud platform, which we encompasses five key areas for us, which we refer to as cloud infrastructure, no deficiencies running your workloads. Cloud management, which is how you're going to go and actually manage, operate, automate, and get governance. And then services on top that started on all around data, right? So we have unified storage, finding the objects, data services. We have database services. Now we have outset of desktop services, which is for EMC. So all of this, the big change for us is this is something that, you know, you can consume in terms of solutions and consume on premises. As Rajiv discussed, you know, we can take the same platform and deploy it in public cloud regions now, right? So you can now get no seamless hybrid cloud, same operating model. But increasingly what we're doing is taking your solutions and re-targeting issues and problems at workers running native public clouds. So think of this as going, after automating more governance, security, you know, finding objects, database services, wherever you're workload is running. So this is taking this portfolio and reapplying it, and targeting on prem at the edge in hybrid and in christening public cloud in ATV. >> Furrier: That's awesome. I've been watching some of the footage and I was noticing quite a lot of innovation around virtualized, networking, disaster, recovery security, and data services. It's all good. You guys were, and this is in your wheelhouse. I know you guys are doing this for many, many years. I want to dive deeper into that because the theme right now that we've been reporting on, you guys are hitting right here what the keynote is cloud scale is about faster development, right? Cloud native is about speed, it's about not waiting for these old departments, IT or security to get back to them in days or weeks and responding to either policy or some changes, you got to move faster. And data, data is critical in all of this. So we'll start with virtualized networking because networking again is a key part of it. The developers want to go faster. They're shifting left, take us through the virtualization piece of how important that is. >> Mirani: Yeah, that's actually a great question as well. So if you think about it, virtual networking is the first step towards building a real cloud like infrastructure on premises that extends out to include networking as well. So one of the key components of any cloud is automation. Another key component is self service and with the API, is it bigger on virtual networking All of that becomes much simpler, much more possible than having to, you know, qualify it, work with someone there to reconfigure physical networks and slots. We can, we can do that in a self service way, much more automated way. But beyond that, the, the, the notion of watching networks is really powerful because it helps us to now essentially extend networks and, and replicate networks anywhere on the private data center, but in the public cloud as well. So now when customers move their workloads, we'd already made that very simple with our clusters offering. But if you're only peek behind the layers a little bit, it's like, well, yea, but the network's not the same on the side. So now it, now it means that a go re IP, my workloads create new subnets and all of that. So there was a little bit of complication left in that process. So to actual network that goes away also. So essentially you can repeat the same network in both locations. You can literally move your workloads, no redesign of your network acquired and still get that self service and automation capabilities of which cookies so great step forward, it really helps us complete the infrastructure as a service stack. We had great storage capabilities before, we create compute capabilities before, and sort of networking the third leg and all of that. >> Furrier: Talk about the complexity here, because I think a lot of people will look at dev ops movement and say, infrastructure is code when you go to one cloud, it's okay. You can, you can, you know, make things easier. Programmable. When, when you start getting into data center, private data centers, or essentially edges now, cause if it's distributed cloud environment or cloud operations, it's essentially one big cloud operation. So the networks are different. As you said, this is a big deal. Okay. This is sort of make infrastructure as code happen in multiple environments across multiple clouds is not trivial. Could you talk about the main trends and how you guys see this evolving and how you solve that? >> Mirani: Yeah. Well, the beauty here is that we are actually creating the same environment everywhere, right? From, from, from point of view of networking, compute, and storage, but also things like security. So when you move workloads, things with security, posture also moves, which is also super important. It's a really hard problem, and something a lot of CIO's struggle with, but having the same security posture in public and private clouds reporting as well. So with this, with this clusters offering and our on-prem offering competing with the infrastructure service stack, you may not have this capability where your operations really are unified across multicloud hybrid cloud in any way you run. >> Furrier: Okay, so if I have multiple cloud vendors, there are different vendors. You guys are creating a connection unifying those three. Is that right? >> Mirani: Essentially, yes, so we're running the same stack on all of them and abstracting away the differences between the clouds that you can run operations. >> Furrier: And when the benefits, the benefits of the customers are what? What's the main, what's the main benefit there? >> Mirani: Essentially. They don't have to worry about, about where their workloads are running. Then they can pick the best cloud for their workloads. It can seamlessly move them between Cloud. They can move their data over easily, and essentially stop worrying about getting locked into a single, into a single cloud either in a multi-cloud scenario or in a hybrid cloud scenario, right. There many, many companies now were started on a cloud first mandate, but over time realized that they want to move workloads back to on-prem or the other way around. They have traditional workloads that they started on prem and want to move them to public cloud now. And we make that really simple. >> Furrier: Yeah. It's kind of a trick question. I wanted to tee that up for Thomas, because I love that kind of that horizontal scales, what the cloud's all about, but when you factor data into it, this is the sweet spot, because this is where, you know, I think it gets really exciting and complicated too, because, you know, data's got, can get unwieldy pretty quickly. You got state got multiple applications, Thomas, what's your, what can you share the data aspect of this? This is super, super important. >> Absolutely. It's, you know, it's really our core source of differentiation, when you think about it. That's what makes Nutanix special right? In, in the market. When we talk about cloud, right. Actually, if you've been following Nutanix for years, you know, we've been talking a lot about making infrastructure invisible, right? The new way for us to talk about what we're doing, with our vision is, is to make clouds invisible so that in the end, you can focus on your own business, right? So how do you make Cloud invisible? Lots of technology is at the application layer to go and containerize applications, you know, make them portable, modernize them, make them cloud native. That's all fine when you're not talking of state class containers, that the simplest thing to move around. Right. But as we all know, you know, applications end of the day, rely on data and measure the data across all of these different locations. I'm not even going to go seconds. Cause that's almost a given, you're talking about attribution. You can go straight from edge to on-prem to hybrid, to different public cloud regions. You know, how do you go into the key control of that and get consistency of all of this, right? So that's part of it is being aware of where your data is, right? But the other part is that inconsistency of set up data services regardless of where you're running. And so this is something that we look at the cloud platform, where we provide you the cloud infrastructure go and run the applications. But we also built into the cloud platform. You get all of your core data services, whether you have to consume file services, object services, or database services to really support your application. And that will move with your application, that is the key thing here by bringing everything onto the same platform. You now can see all operations, regardless of where you're running the application. The last thing that we're adding, and this is a new offering that we're just launching, which is a service, it's called, delete the dead ends. Which is a solution that gives you visibility and allow you to go and get better governance around all your data, wherever it may live, across on-prem edge and public clouds. That's a big deal again, because to manage it, you first have to make sense of it and get control over it. And that's what data answer's is going to be all about. >> Furrier: You know, one of the things we've we've been reporting on is data is now a competitive advantage, especially when you have workflows involved, um, super important. Um, how do you see customers going to the edge? Because if you have this environment, how does the data equation, Thomas, go to the edge? How do you see that evolving? >> Cornely: So it's yeah. I mean, edge is not one thing. And that's actually the biggest part of the challenge of defining what the edge is depending on the customer that you're working with. But in many cases you get data ingesting or being treated at the edge that you then have to go move to either your private cloud or your public cloud environment to go and basically aggregate it, analyze it and get insights from it. Right? So this is where a lot of our technologies, whether it's, I think the object's offering built in, we'll ask you to go and make the ingest over great distances over the network, right? And then have your common data to actually do an ethics audit over our own object store. Right? Again, announcements, we brought into our storage solutions here, we want to then actually organize it then actually organize it directly onto the objects store solution. Nope. Using things, things like or SG select built into our protocols. So again, make it easy for you to go in ingest anywhere, consolidate your data, and then get value out of it. Using some of the latest announcements on the API forms. >> Furrier: Rajiv databases are still the heart of most applications in the enterprise these days, but databases are not just the data is a lot of different data. Moving around. You have a lot a new data engineering platforms coming in. A lot of customers are scratching their head and, and they want to kind of be, be ready and be ready today. Talk about your view of the database services space and what you guys are doing to help enterprise, operate, manage their databases. >> Mirani: Yeah, it's a super important area, right? I mean, databases are probably the most important workload customers run on premises and pretty close on the public cloud as well. And if you look at it recently, the tooling that's available on premises, fairly traditional, but the clouds, when we integrate innovation, we're going to be looking at things like Amazon's relational database service makes it an order of magnitude simpler for our customers to manage the database. At the same time, also a proliferation of databases and we have the traditional Oracle and SQL server. But if you have open source Mongo, DB, and my SQL, and a lot of post-grads, it's a lot of different kinds of databases that people have to manage. And now it just becomes this cable. I have the spoke tooling for each one of them. So with our Arab product, what we're doing is essentially creating a data management layer, a database management layer that unifies operations across your databases and across locations, public cloud and private clouds. So all the operations that you need, you do, which are very complicated in, in, in, in with traditional tooling now, provisioning of databases backing up and restoring them providing a true time machine capabilities, so you can pull back transactions. We can copy data management for your data first. All of that has been tested in Era for a wide variety of database engines, your choice of database engine at the back end. And so the new capabilities are adding sort of extend that lead that we have in that space. Right? So, so one of the things we announced at .Next is, is, is, is one-click storage scaling. So one of the common problems with databases is as they grow over time, it's not running out of storage capacity. Now re-provisions to storage for a database, migrate all the data where it's weeks and months of look, right? Well, guess what? With Era, you can do that in one click, it uses the underlying AOS scale-out architecture to provision more storage and it does it have zero downtime. So on the fly, you can resize your databases that speed, you're adding some security capabilities. You're adding some capabilities around resilience. Era continues to be a very exciting product for us. And one of the things, one of the real things that we are really excited about is that it can really unify database operations between private and public. So in the future, we can also offer an aversion of Era, which operates on native public cloud instances and really excited about that. >> Furrier: Yeah. And you guys got that two X performance on scaling up databases and analytics. Now the big part point there, since you brought up security, I got to ask you, how are you guys talking about security? Obviously it's embedded in from the beginning. I know you guys continue to talk about that, but talk about, Rajiv, the security on, on that's on everyone's mind. Okay. It goes evolving. You seeing ransomware are continuing to happen more and more and more, and that's just the tip of the iceberg. What do you guys, how are you guys helping customers stay secure? >> Mirani: Security is something that you always have to think about as a defense in depth when it comes to security, right? There's no one product that, that's going to do everything for you. That said, what we are trying to do is to essentially go with the gamut of detection, prevention, and response with our security, and ransom ware is a great example of that, right. We've partnered with Qualys to essentially be able to do a risk assessment of your workloads, to basically be able to look into your workloads, see whether they have been bashed, whether they have any known vulnerabilities and so on. To try and prevent malware from infecting your workloads in the first place, right? So that's, that's the first line of defense. Now not systems will be perfect. Some, some, some, some malware will probably get in anyway But then you detect it, right. We have a database of all the 4,000 ransomware signatures that you can use to prevent ransomware from, uh, detecting ransom ware if it does infect the system. And if that happens, we can prevent it from doing any damage by putting your fire systems and storage into read-only mode, right. We can also prevent lateral spread of, of your ransomware through micro-segmentation. And finally, if you were, if you were to invade, all those defenses that you were actually able to encrypt data on, on, on a filer, we have immutable snapshots, they can recover from those kinds of attacks. So it's really a defense in depth approach. And in keeping with that, you know, we also have a rich ecosystem of partners while this is one of them, but older networks market sector that we work with closely to make sure that our customers have the best tooling around and the simplest way to manage security of their infrastructure. >> Furrier: Well, I got to say, I'm very impressed guys, by the announcements from the team I've been, we've been following Nutanix in the beginning, as you know, and now it's back in the next phase of the inflection point. I mean, looking at my notebook here from the announcements, the VPC virtual networking, DR Observability, zero trust security, workload governance, performance expanded availability, and AWS elastic DR. Okay, we'll get to that in a second, clusters on Azure preview cloud native ecosystem, cloud control plane. I mean, besides all the buzzword bingo, that's going on there, this is cloud, this is a cloud native story. This is distributed computing. This is virtualization, containers, cloud native, kind of all coming together around data. >> Cornely: What you see here is, I mean, it is clear that it is about modern applications, right? And this is about shifting strategy in terms of focusing on the pieces where we're going to be great at. And a lot of these are around data, giving you data services, data governance, not having giving you an invisible platform that can be running in any cloud. And then partnering, right. And this is just recognizing what's going on in the world, right? People want options, customers and options. When it comes to cloud, they want options to where they're running the reports, what options in terms of, whether it be using to build the modern applications. Right? So our big thing here is providing and being the best platform to go and actually support for Devers to come in and build and run their new and modern applications. That means that for us supporting a broad ecosystem of partners, entrepreneur platform, you know, we announced our partnership with Red Hat a couple of months ago, right? And this is going to be a big deal for us because again, we're bringing two leaders in the industry that are eminently complimentary when it comes to providing you a complete stack to go and build, run, and manage your client's applications. When you do that on premises, utilizing like the preferred ATI environment to do that. Using the Red Hat Open Shift, or, you're doing this open to public cloud and again, making it seamless and easy, to move the applications and their supporting data services around, around them that support them, whether they're running on prem in hybrid winter mechanic. So client activity is a big deal, but when it comes to client activity, the way we look at this, it's all about giving customers choice, choice of that from services and choice of infrastructure service. >> Furrier: Yeah. Let's talk to the red hat folks, Rajiv, it's you know, it's, they're an operating system thinking company. You know, you look at the internet now in the cloud and edge, and on-premise, it's essentially an operating system. you need your backup and recovery needs to disaster recovery. You need to have the HCI, you need to have all of these elements part of the system. It's, it's, it's, it's building on top of the existing Nutanix legacy, then the roots and the ecosystem with new stuff. >> Mirani: Right? I mean, it's, in fact, the Red Hat part is a great example of, you know, the perfect marriage, if you will, right? It's, it's, it's the best in class platform for running the cloud-native workloads and the best in class platform with a service offering in there. So two really great companies coming together. So, so really happy that we could get that done. You know, the, the point here is that cloud native applications still need infrastructure to run off, right? And then that infrastructure, if anything, the demands on that and growing it since it's no longer that hail of, I have some box storage, I have some filers and, you know, just don't excite them, set. People are using things like object stores, they're using databases increasingly. They're using the Kafka and Map Reduce and all kinds of data stores out there. And back haul must be great at supporting all of that. And that's where, as Thomas said, earlier, data services, data storage, those are our strengths. So that's certainly a building from platform to platform. And then from there onwards platform services, great to have right out of the pocket. >> Furrier: People still forget this, you know, still hardware and software working together behind the scenes. The old joke we have here on the cube is server less is running on a bunch of servers. So, you know, this is the way that is going. It's really the innovation. This is the infrastructure as code truly. This is what's what's happened is super exciting. Rajiv, Thomas, thank you guys for coming on. Always great to talk to you guys. Congratulations on an amazing platform. You guys are developing. Looks really strong. People are giving it rave reviews and congratulations on, on, on your keynotes. >> Cornely: Thank you for having us >> Okay. This is theCube's coverage of.next global virtual 2021 cube coverage day two keynote review. I'm John Furrier Furrier with the cube. Thanks for watching.

>>Hey, welcome to the Cubes coverage of Red Hat Summit 2021, the virtual experience, I'm lisa martin, I have two guests joining me. One is a cube alum kamal Shah is back, he's now the VP of cloud platforms at Brent had come on, it's great to have you back on the program. You're in a new role, we're going to talk about that. Thank you. And Kirsten newcomer is here as well. She's the Director of cloud and Death stickups strategy at Red Hat, Kirsten, Welcome and thank you for bringing the red hat vibe to the segment. >>Absolutely, very happy to be here. >>So looking forward to this conversation that we're going to be having in the next 20 minutes or so. We're gonna be talking about the last time come on, you were on, you were the ceo of stack rocks In January of 2021. The announcement that red hat plans to acquire stack rocks, it wouldn't be talking all about that. But I'd like to start with Kirsten, give us your perspective from red hats perspective, why is red hat a good fit for stack rocks? >>You know, there are so many reasons first of all as as you know, right? Red hat has been working with product Izing kubernetes since kubernetes one dato. Right, so so open shift three dato shipped with kubernetes one dot Oh, so we've been working with kubernetes for a long time, stack rocks embraces kind of is kubernetes native security embraces the declarative nature of kubernetes and brings that to security. Red hats, Custer's red hat enterprise customers, we have a great set across different verticals that are very security conscious and and during my five years at red hat, that's where I spend the majority of my time is talking with our customers about container and kubernetes security. And while there's a great deal of security built in to open shift as it goes to market out of the box, customers need the additional capabilities that stack rock springs. Historically, we've met those needs with our security partners. We have a great ecosystem of security partners. And with the stack rocks acquisition, we're now in a position to offer additional choice. Right. If a customer wants those capabilities from Red hat tightly integrated with open shift, we'll have those available and we continue to support and work with our broad ecosystem of security partners. >>Excellent customers always want choice. Come on. Give me your perspective. You were at the helm the ceo of stack rocks as you were last time you were on the cube. Talk to me about the redhead acquisition from your seat. >>Yeah. So as as Kirsten mentioned, we were partners of red hat. You're part of the red hat partner ecosystem. And uh, what we found is that was both a great strategic fit and a great cultural fit between our two companies. Right? And so the discussions that we had were how do we go and quickly enable our customers to accelerate their digital transformation initiatives to move workloads to the cloud, to containerized them, to manage them through kubernetes and make sure that we seamlessly addressed their security concerns. Right? Because it continues to be the number one concern for large enterprises and medium sized enterprises and frankly any enterprise that uh, you know, uh, working out today. So, so that was kind of the impetus behind it. And I must say that so far the the acquisition has been going on very smoothly. So we had two months in roughly and everybody and has been very welcoming, very collaborative, very supportive. And we are already working hand in hand to to integrate our companies and to make sure that we are working closely together to make our customers successful. >>Excellent. We're gonna talk about that integration in a second. But I can imagine challenging going through an acquisition during a global pandemic. Um but that is one of the things that I think lends itself to the cultural alignment. Kamal that you talked about, Kirsten. I want to get your perspective. We know we talk about corporate culture and corporate culture has changed a lot in the last year with everybody or so many of us being remote. Talk to me about kind of the core values that red hat and stack rocks share >>actually, you know, that's been one of the great joys doing during the acquisition process in particular, Kamal and and ali shared kind of their key values and how they um how they talked to talk with their team And some of the overlap was just so resonated so much for all of us. In particular the sense of transparency, uh, that the, that the team the stack rocks executive team brings and approaches. That's a that's a clear value for red hat um strongly maintained. Uh, that was one of the key things the interest in um uh, containers and kubernetes. Right. So the technology alignment was very clear. We probably wouldn't have proceeded without that. But again, um and I think the investment in people and the independence and the and the strong drive of the individuals and supporting the individuals as they contribute to the offering so that it really creates that sense of community um and collaboration that is key. Uh and and it's just really strong overlap in in cultural values and we so appreciated that >>community and collaboration couldn't be more important these days. And ultimately the winner is the customers. So let's dig in. Let's talk about what stack rocks brings to open shift Kirsten take it away >>man. So as I said earlier, um so I think we we really believe in continuous security at red hat and in defense and depth. And so when we look at an enterprise kubernetes distribution that involves security at the real core os layer security and kubernetes adding the things into the distribution, making sure they're there by default, that any distribution needs to be secured to be hardened, auditing, logging, identity, access management, just a wealth of things. And Red hat has historically focused on infrastructure and platform security, building those capabilities into what we bring to market stack rocks enhances what we already have and really adds workload protection, which is really when it comes down to it. Especially if you're looking at hybrid cloud, multi cloud, how you secure, not just the platform, but how you secure your workloads changes. And we're moving from a world where, you know, you're deploying anti virus or malware scanners on your VMS and your host operating system to a world where those work clothes may be very short lived. And if they aren't secured from the get go, you miss your opportunity to secure them right? You can't rely on, you know, you do need controls in the infrastructure but they need to be kubernetes native controls and you need to shift that security left. Right? You never patch a running container. You always have to rebuild and redeploy if you patch the running container the next time that container images deployed, you've missed, you've lost that patch. And so the whole ethos the whole shift left. The Deb sec ops capabilities that stack rock springs really adds such value. Right? You can't just do DEF SEc or set cops. You need to do a full infinity loop to really have def SEc ops and stack rocks. I'm gonna let Kamal tell you about it, but they have so many capabilities that that really drive that shift left and enable that closed loop. We're just so excited that they're part of our offerings. >>So can you take us through that? How does stack rocks facilitate the shift left? >>Yeah, absolutely. So stack rocks, which we we announced at summit is now being rebranded as red hat. Advanced cluster security was really purpose built to help our customers address the use cases across the entire application lifecycle. Right? So from bill to deploy to run time. So this is the infinite loop that Kirsten mentioned earlier and one of our foundations was to be kubernetes native to ensure that security is really built into the application is supposed to bolt it on. So specifically, we help our customers shift left by securing the supply chain and we're making sure that we identifying vulnerabilities early during the build process before they make it to a production environment. We helped them secure the infrastructure by preventing miS configurations again early in the process because as we all know, MIS configurations often lead to breaches at at runtime. Right? We help them address uh compliance requirements by ensuring that we can check for CS benchmarks are regulatory requirements around the C I P C I, hip hop and this and and that's uh you know, just focusing on shift left, doesn't really mean that you ignore the right side or ignore the controls you need uh when your applications are running in production. So we help them secure that at runtime by identifying preventing breaches the threat detection, prevention and incident response. >>That built in security is you both mentioned that built in versus bolt on Kirsten? Talk to me about that, that as really kind of a door opener. We talked a lot about security issues, especially in the last year. I don't know how many times we've talked about miS configurations leading to breaches that we've seen so many security challenges present in the last year. We talked to me a little bit Kirsten about >>what >>customers appetites are for going. All right now, I've got cloud native security, I'm going to be able to, I'm going to feel more comfortable with rolling out production deployments. >>It's, it's a great place to go. So there are a number of elements to think about. And if I could, I could, I could start with by building on the example that Kamal said, Right, So when we think about um I need to build security into my pipeline so that when I deliver my containerized workloads, they're secure. What if I miss a step or what if a new vulnerability is discovered after the fact? Right. So one of the things that stack rocks or redhead a CS offers is it has built in policy checks to see whether a container or running image has something like a package manager in it. Well, a package manager can be used to load software that is not delivered with the container. And so the idea of ensuring that you are including workload, built in workload, protect locks with policies that are written for you. So you can focus on building your applications. You don't necessarily have to learn everything there is to know about the new attack vectors that are really just it it's new packaging, it's new technology. It's not so much there are some new attack vectors, but mostly it's a new way of delivering and running your applications. That requires some changes to how you implement your security policies. And so ensuring that you have the tools and the technology that you're running on have those capabilities built in. So that when we have conversations with our security conscious customers, we can talk with them about the attack vectors they care about. We can illustrate how we are addressing those particular concerns. Right? One of them being malware in a container, we can look for stack. Rocks can look for a package manager that could be used to pull in, you know, code that could be exploited and you can stop a running container. Um, we can do deeper data collection with stack rocks. Again, one of the challenges when you're looking at moving your security capabilities from a traditional application environment is containers come and go all the time. In a kubernetes cluster nodes, your servers can come and go in a cloud native kubernetes cluster, right? If you're running on on cloud public cloud infrastructure, um, those things are the nodes are ephemeral to, they're designed to be shut down and brought back up. So you've got a lot more data that you need to collect and that you need to analyze and you need to correlate the information between these. Right? I no longer have one application stack running on one or more VMS, it's just things are things are moving fast so you want the right type of data collection and the right correlation to have good visibility into your environment. >>And if I can just build on that a little bit. The whole idea here is that these policies really serve as god rails right for the developers. So the it allows developers to move quickly to accelerate the speed of development without having to worry about hundreds of potential security issues because there are guardrails that will notify that with concrete recommendations early in the process. And the analogy I often use is that you know the reason we have breaks in our cars, it's not to slow us down but to allow us to go faster because we know we can slow down when we need to write. So similarly these policies are really it's really designed to accelerate the speed of development and accelerate digital transformation initiatives that our customers are embarking on >>and come on. I want to stick with you on the digital transformation front. We've talked so much about how accelerated that has been in the last year with everything going on in such a dynamic market. Talk to me Kamal about some of the feedback that you've gotten from stack rocks customers about the acquisition and how it is that maybe that facilitator of the many pivots that businesses have had to do in the last year to go from survival mode to thriving business. >>Yeah. Yes, absolutely. The feedback from all of our customers bar none has been very very positive. So it's been it's allowed us to invest more in the business and you know, we publicly stated that we are going to invest more in adding more capabilities. We are more than doubling the size of our teams as an example. And really working hand in hand with our uh the broader team at Red had to uh further accelerate the speed of development and digital transformation initiatives. So it's been extremely positive because we're adding more resources, We're investing more. We're accelerating the product roadmap uh based on uh compared to what we could do as a, as a start up as you can imagine. And and the feedback has been nothing but positive. So that's kind of where we are today. And what we're doing with the summit is rolling out a new bundle called open shift uh, Open shift platform plus, which includes not just Red hat A CS which used to be Stock rocks, but also red hat open shift hybrid cloud platform as well as Red hat advanced uh container cluster management, ACM capabilities as well as create the container registry. So we're making it easier for our customers to get all the capabilities that they need to for the drive digital transformation initiatives to get. It goes back to this whole customer centric city team that red hat has, that was also core value of stack rocks and and the winner and all of this, we believe ultimately is our, our our customers because that's where we exist to serve them, >>right. And I really like that if I could chime in kind of on top of that a little bit. Um so, so I think that one of the things we've seen with the pandemic is more of the red Hat customers are accelerating their move to public cloud and away from on premises data centers. Uh and and you know, that's just part partly because of so many people working remotely. Um it just has really pushed things. And so with Hybrid cloud becoming even more key to our joint customer base and by hybrid cloud, I mean that they have some environments that are on premises as they're making this transition. Some of those environments may stay that footprint may stay on premises, but it might be smaller, they may not have settled on a single public cloud. They could, in fact, they often are picking a public cloud based on where their development focuses. Google is very popular for ai and ml workloads. Amazon of course is just used, you know, by pretty much everybody. Um and then Azzurri is popular with um a subset of customers as well. And so we see our customers investing in all of these environments and stack rocks red hat A CS like open shift runs in all these environments. So with open shift platform plus you get a complete solution that helps with multi cluster management with a C. M with security across all of these environments, right? You can take one approach to how you secure your cluster, how you secure your workloads, how you manage configurations, You get one approach no matter where you're running your containers and kubernetes platform when you're doing this with open shift platform plus. So you also get portability. If today you want to be running an amazon maybe tomorrow you need to spin up a cluster in google, you can do that if you're working with the K s or G K E, you can or a Ks, you can do that with red hat a CS as well. So we really give you everything you need to be successful in this move and we give you back to that choice word, right? We give you the opportunity to choose and to migrate at the speed that works for you. >>So that's simplicity. That streamlining. I gotta ask you the last question here in our last couple of minutes. Come on, what's the integration process been like? as we said the acquisition just a couple of months in. But talk to me about that integration process. What that's been like? >>Yeah, absolutely. So as I mentioned earlier, the process has been very smooth so far, so two months in and it's largely driven by the common set of culture and core values that exists between our two companies. And so uh you know, from a product standpoint, we've been working hand in hand because I mentioned earlier, we were partners are working hand in hand on accelerating the road map the joint roadmap that we have here uh from a go to market perspective teams are well integrated. We are going to be rolling out the rolling out the bundle and we're gonna be rolling out additional uh options for our customers. We've also publicly announced that will be open sourcing uh red hat A. C. S. Uh formerly known as Stock Rock. So stay tuned for further news and that announcement. And, and so you know, uh, again two months and everybody's been super collaborative. Super helpful, super welcoming. And the team is the well settled and we're looking forward to now focusing on our primary objective is just to make sure that our customers are successful. >>Absolutely. That customer focus is absolutely critical. But also so is the employee experience. And it sounds like we both talked about the ethos and the and the core value alignment. They're probably being pretty critical to doing an integration during a very challenging time globally. I appreciate both of you joining me on the program today, sharing what's going on stack rocks now asks the opportunities for customers to have that built in cuBA and the security. Thanks so much for your time. >>Thank you. Thank >>you for Camel shaw and Kirsten newcomer. I'm lisa martin. You're watching the cubes coverage of Red Hat Summit, The virtual experience. Mhm

>>from >>around the globe, it's the cube with digital coverage of IBM Think >>2021 >>brought to you by IBM. >>Hey, welcome to the cubes coverage of IBM Think 2021. I'm lisa martin, I have to IBM alumni with me here today please welcome Brianna frank the director of product management at IBM and Jason McGee is here as well. IBM fellow VP and Cto of the IBM cloud platform, Brianna and Jason welcome back to the cube. >>Thank you so much for having us, >>you guys were here a couple months ago, but I know there's been a whole bunch of things going on. So Brianna, we'll start with you, what's new, what's new with IBM cloud? >>We are, it's just, it's been such a rush of announcements lately, but one of my favorite announcements uh, is the IBM cloud satellite product. We went g a back in March and you know, this has been one of the most fun projects to work on as a product manager because you know, it's all about our clients coming to us and saying, hey look, we're having these are the problems that we're really facing with as we, as we move to cloud in our journey to cloud and can you help us solve them? And I think this has been just an exciting place to be in terms of distributed cloud, this new category that's really emerging where we've taken the IBM cloud, but we've distributed into lots of different locations on prem at the edge and on other public clouds. And it's been a really fun journey and it's such a great fulfilling thing to see it come to life and see clients using it and getting feedback from analysts and um in the industry. So it's been a, it's been a great, you know, a few months. >>That's good. Lots of excitement going on. Jason talk to me a little bit about kind of unpack uh, the cloud satellite from, you see what flashing in Jason's background is an IBM cloud satellite. Me, I'm sorry, I love that. You talk to me a little bit about the genesis of it. What were some of the things that customers were asking for? >>Yeah, absolutely. I mean, so, so look, I think as we've talked about a lot of IBM, you know, as as people have gone on their journey to cloud and been moving workloads in the cloud over the last few years, um, you know, not all workloads have moved right. Maybe 20 of workloads have moved to the cloud and that remaining 80% sometimes that thing that's inhibiting that is regulation compliance data late and see where my data lives. And so people have been kind of struggling with, how do I get the kind of benefits and speed and agility to public cloud, But apply it to all these applications that maybe need to live in my data center or need to live on the edge of the network close to my users or need to live where the data is being generated or in a certain country. And so the genesis of satellite was really to take our hybrid strategy and combine it with the public cloud consumption model and really allow you to have public cloud anywhere you needed it, bring those public cloud services into your data center or bring them to the edge of the network where your data is being generated and let you get the best of both. And we think that really will unlock, you know, the next wave of applications to be able to get the advantages of as a service kind of public consumption um, while retaining the flexibility to run wherever you need, >>curious station, did you see any particular industries in the last year of, I don't want to say mayhem, but you know, mayhem taking really the lead and the edge in wanting to work with you guys to understand how to really facilitate digital business transformation, because we saw a lot of acceleration going on last year. >>Yeah, absolutely. I mean, it's interesting. Cloud is fundamentally pretty horizontal technology. It applies to lots of industries, but I think the past year, especially, um, with, you know, Covid and lockdowns and changes in how we all work have accelerated massively, um, clients adoption of cloud. Um, and they've they've been looking for ways to apply those benefits across more of what they do. All right. And, and I think there's different drivers, you know, there's, you know, security compliance drivers, maybe in, in places like the financial services industry, but there's also the industries like manufacturing and retail that have, you know, they have a geographic footprint, like where things run matters to them. And so they're like, well, how do I get that kind of remote cloud benefit in all those places too. And so I've seen some acceleration in those areas. >>And one of the interesting things that I thought has emerged from an industry focus is this concept of RFs file control. So we have specific control and compliance built into the IBM cloud and one of the most prevalent questions I get from clients, you know, when can I get this FSL controls in satellite, you know, in all of these different locations. And so we built that in that's coming later this year. But I was really surprised to hear every industry and I guess it shouldn't be surprised. I mean every, every industry is trading money so it's important to keep things secure. But those fs cloud controls being extended into the satellite location is something I hear constantly as a need no matter the industry, whether it's, you know, retail or insurance, you know, etcetera. So I think that the security concerns and being able to offload the burden and chores of security is, is huge. >>One of the things we saw a lot last year, Brianna along the security lines is was ransomware booming, ransomware is a service, ransomware getting more personal. Talk to a lot of customers and to your point in different industries that are really focused on, it's not if we get hit by ransomware, it's when. So I'm wondering if that if some of the things that we saw last year or maybe why you're saying this being so such a pervasive need across industries, what do you think? >>Absolutely. I think that it's something that you really have to concentrate on full time and you know, it has to be something you're just maniacally focused on. And we have all kinds of frameworks and actually, uh, groups where we're looking at shaping regulation and compliance and it's really something that we study. Um, so if when we can pass on that expertise to our clients and again offload them. So, you know, not everyone can be an expert in these areas. I find that, you know, relieving, you know, our clients of these operational security tours allows them to get back to what they want to do, which is actually just keep inventing and building better technology for their business. >>I think that's such a, I think that's such an important point that brand is bringing up to those like part of the value of something like satellite is that we can we can run these technology platforms as a service. Right. And well, what does that? The service means? It means you can tap into a team of people who are the industry's best at building and operating that technology platform, right? Like maybe you've decided that, you know, kubernetes and open shift is your go for or platform as a business, but do you have the team and the skills that you need to operate that yourself? You know, you want to use a I you probably don't want to become an expert in how to run like whatever the latest and greatest ai framework is, you want to actually like figure out how to apply that to your business. And so we think that part of what's really attracting people to solutions like satellite, especially now with the threat you described is that they can tap into this expertise by consuming things as a service instead of figuring out how to round all themselves >>to that point. A lot of times we see really talented developers, I really like talking to incubation teams where there, you know, they're building new and they're just trying to figure out how to create, you know, the next new thing and um, it's not that they're not talented enough, they could do whatever they put their mind to, it's just that they don't have enough time and they, you know, then it just becomes too, comes down to, you know, what do you really want to spend your time doing? Is it, you know, security and operational chores, or is it inventing the next big thing for your business? And I think that that's where we're seeing the market really shift, is that, you know, it's not efficient or you know, um you know, a great idea and really no one wants to do that, you know, so we can over, if we can offload those chores, then that becomes really powerful. >>It does resource allocation is key to let those businesses to your point, we're gonna focus on their core competencies, innovating new products, new services, meeting customers where they are as customers like us become more and more demanding of things being readily available. I do want to understand a little bit, Jason, help me understand how this service is differentiated from some of the competitors in the market. >>Yeah, it's a it's a totally fair question. Um so I would answer that in a couple of ways. Um first off, you know, anytime you're talking about extending a cloud into some other environment, you obviously need some infrastructure for that application to run on whether the infrastructure is in your data center or at the edge or somewhere else. And one of the things that we've been able to is by leveraging our hybrid cloud platform by leveraging things like open shift and Lennox, we've been able to build satellite in a way where you can bring almost any clinics infrastructure to the table and use it to run satellite. So we don't require you to buy a certain lack of hardware or particular gear from us. You don't have to replace all your infrastructure. You can kind of use what you have and extend the cloud and that to me is all about, you know, if the goal is to help people build things more quickly and consume cloud, like you don't want step one to be like wheel in a whole new data center full of hardware before you get started. Um the second thing I would say is we have built our whole cloud um on this, this containerized technology, on kubernetes and open ship, which means that we're able to deliver more of our portfolio through satellite. We can deliver application platforms and databases and Deb tools and ai and security functions all as a service via satellite. So the breath of cloud capability that we think we can deliver in this model is much higher than what I think our competitors are going to be able to do. And then finally, I would say the tide to kind of IBM view of enterprise and regulated industries, you know, the work brand I mentioned around things like FS cloud, the work we're doing in telco, like we spent a lot of our energy, I'm like, how do we help, you know, enterprises regulated industries take advantage of cut and we're extending all of that work outside of our cloud data centers with satellite to all these other places. And so you really can move those mission critical applications into a cot environment when you do it with us. >>Let's talk about some successes Brianna tell me about some of the customers that are getting some pretty big business outcomes and this is a new service to talk to me about how it's being used consumed in the benefits. >>Absolutely. You know what I I find a trend that I'm seeing is really uh the cloud being distributed to the edge and there's so many interesting use cases I hear every single day about how to really use machine learning and ai at the edge. And so you know, maybe it's something as simple as, you know, a worker safety app or you're you know, making sure that workers are safe using video cameras in an office building and alerting someone if they're going into a construction area and you're using the Ai and although the the images that's coming, they're coming in through the security cameras, you're doing some analysis and saying this person is wearing a hard hat or not and warning them, but that those use cases can be changed so quickly. And you know, we've we've seen that, I think I've talked about it before with Covid you change that to masks. Um you could change that. You could hook up the application of thermal devices. We've seen situations where you know, um machine learning is used at the manufacturing edge. So you can determine if there's an issue with your um production of, you know, in a factory there's we're seeing uh edge use cases and hospitals in terms of, you know, keeping the waiting room sanitized because of, you know, over usage. So there's all kinds of just really interesting solutions and I think this is kind of the next area where we're really able to um and even partner with folks that have extraordinary vertical expertise in a specific area and you know, bringing that to life at the edge and being able to really process that data at the edge. So there's very little latency and then also you're able to change those use cases so quickly because you're really consuming cloud native best practices in cloud cloud services at the end. So you're not having to install and and manage and operate those services at the edge. It's done for you >>imagine changing the ability to change use cases so quickly in a year that plus that we've seen so much dynamics and pivoting is really key for businesses in any industry Brianna. >>I agree. And that's the thing. You know, there hasn't been one particular industry I think, you know, of course we do see a lot in the financial services industry just probably because we're IBM, but in every industry, you know, we see, you know retail, it's interesting to see sporting goods companies want to have pop up shops in a specific sporting events and how do you, you know, have a van that is a sporting goods shop, but it's just there temporarily. And how do you have a satellite location at, in the van? So there's really interesting use cases that, you know, have emerged, um, you know, just over time due to, um, you know, the need to have this capability at the edge. >>Yeah, it's necessity is the mother of invention as they say, right, well thank you both so much for stopping by sharing what's going on with IBM Cloud Satellite, the new service, the new offerings, the opportunities in it for customers. I'm sure it's going to be another exciting year for IBM because you clearly have been very busy. Thank you both for stopping by the program. >>Thanks. Thanks so much lisa >>for Brianna frank and Jason McGee. I'm lisa martin. You're watching the cube live coverage of IBM, think. >>Mm

>>from around the globe. It's the Cube presenting enterprise. Digital resilience on hybrid and multi cloud Brought to You by Iota Ho. Hello, everyone, and welcome to our continuing Siri's covering data automation brought to you by Io Tahoe. Today we're gonna look at how to ensure enterprise resilience for hybrid and multi cloud. Let's welcome in age. Eva Hora, who is the CEO of Iota A J. Always good to see you again. Thanks for coming on. >>Great to be back. David Pleasure. >>And he's joined by Fozzy Coons, who is a global principal architect for financial services. The vertical of financial services. That red hat. He's got deep experiences in that sector. Welcome, Fozzie. Good to see you. >>Thank you very much. Happy to be here. >>Fancy. Let's start with you. Look, there are a lot of views on cloud and what it is. I wonder if you could explain to us how you think about what is a hybrid cloud and and how it works. >>Sure, yes. So the hybrid cloud is a 90 architecture that incorporates some degree off workload, possibility, orchestration and management across multiple clouds. Those clouds could be private cloud or public cloud or even your own data centers. And how does it all work? It's all about secure interconnectivity and on demand. Allocation of resources across clouds and separate clouds can become hydrate when they're similarly >>interconnected. And >>it is that interconnectivity that allows the workloads workers to be moved and how management can be unified in off the street. You can work and how well you have. These interconnections has a direct impact on how well your hybrid cloud will work. >>Okay, so we'll fancy staying with you for a minute. So in the early days of Cloud that turned private Cloud was thrown a lot around a lot, but often just meant virtualization of an on PREM system and a network connection to the public cloud. Let's bring it forward. What, in your view, does a modern hybrid cloud architecture look like? >>Sure. So for modern public clouds, we see that, um, teams organizations need to focus on the portability off applications across clouds. That's very important, right? And when organizations build applications, they need to build and deploy these applications as small collections off independently, loosely coupled services, and then have those things run on the same operating system which means, in other words, running it on Lenox everywhere and building cloud native applications and being able to manage and orchestrate thes applications with platforms like KUBERNETES or read it open shit, for example. >>Okay, so that Z, that's definitely different from building a monolithic application that's fossilized and and doesn't move. So what are the challenges for customers, you know, to get to that modern cloud? Aziz, you've just described it. Is it skill sets? Is that the ability to leverage things like containers? What's your view there? >>So, I mean, from what we've seen around around the industry, especially around financial services, where I spent most of my time, we see that the first thing that we see is management right now because you have all these clouds and all these applications, you have a massive array off connections off interconnections. You also have massive array off integrations, possibility and resource allocations as well, and then orchestrating all those different moving pieces. Things like storage networks and things like those are really difficult to manage, right? That's one. What s O Management is the first challenge. The second one is workload, placement, placement. Where do you place this? How do you place this cloud? Native applications. Do you or do you keep on site on Prem? And what do you put in the cloud? That is the the the other challenge. The major one. The third one is security. Security now becomes the key challenge and concern for most customers. And we could talk about how hundreds? Yeah, >>we're definitely gonna dig into that. Let's bring a J into the conversation. A J. You know, you and I have talked about this in the past. One of the big problems that virtually every companies face is data fragmentation. Um, talk a little bit about how I owe Tahoe unifies data across both traditional systems legacy systems. And it connects to these modern I t environments. >>Yeah, sure, Dave. I mean, fancy just nailed it. There used to be about data of the volume of data on the different types of data. But as applications become or connected and interconnected at the location of that data really matters how we serve that data up to those those app. So working with red hat in our partnership with Red Hat being able Thio, inject our data Discovery machine learning into these multiple different locations. Would it be in AWS on IBM Cloud or A D. C p R. On Prem being able thio Automate that discovery? I'm pulling that. That single view of where is all my data then allows the CEO to manage cast that can do things like one. I keep the data where it is on premise or in my Oracle Cloud or in my IBM cloud on Connect. The application that needs to feed off that data on the way in which you do that is machine learning. That learns over time is it recognizes different types of data, applies policies to declassify that data. Andi and brings it all together with automation. >>Right? And that's one of the big themes and we've talked about this on earlier episodes. Is really simplification really abstracting a lot of that heavy lifting away so we can focus on things A. J A. Z. You just mentioned e nifaz e. One of the big challenges that, of course, we all talk about his governance across thes disparity data sets. I'm curious as your thoughts. How does Red Hat really think about helping customers adhere to corporate edicts and compliance regulations, which, of course, are are particularly acute within financial services. >>Oh, yeah, Yes. So for banks and the payment providers, like you've just mentioned their insurers and many other financial services firms, Um, you know, they have to adhere Thio standards such as a PC. I. D. S s in Europe. You've got the G g d p g d p r, which requires strange and tracking, reporting documentation. And you know, for them to to remain in compliance and the way we recommend our customers to address these challenges is by having an automation strategy. Right. And that type of strategy can help you to improve the security on compliance off the organization and reduce the risk after the business. Right. And we help organizations build security and compliance from the start without consulting services residencies. We also offer courses that help customers to understand how to address some of these challenges. And that's also we help organizations build security into their applications without open sources. Mueller, where, um, middle offerings and even using a platform like open shift because it allows you to run legacy applications and also continue rights applications in a unified platform right And also that provides you with, you know, with the automation and the truly that you need to continuously monitor, manage and automate the systems for security and compliance >>purposes. Hey, >>Jay, anything. Any color you could add to this conversation? >>Yeah, I'm pleased. Badly brought up Open shift. I mean, we're using open shift to be able. Thio, take that security application of controls to to the data level. It's all about context. So, understanding what data is there being able to assess it to say who should have access to it. Which application permission should be applied to it. Um, that za great combination of Red Hat tonight. Tahoe. >>But what about multi Cloud? Doesn't that complicate the situation even even further? Maybe you could talk about some of the best practices to apply automation across not only hybrid cloud, but multi >>cloud a swell. Yeah, sure. >>Yeah. So the right automation solution, you know, can be the difference between, you know, cultivating an automated enterprise or automation caress. And some of the recommendations we give our clients is to look for an automation platform that can offer the first thing is complete support. So that means have an automation solution that provides that provides, um, you know, promotes I t availability and reliability with your platform so that you can provide, you know, enterprise great support, including security and testing, integration and clear roadmaps. The second thing is vendor interoperability interoperability in that you are going to be integrating multiple clouds. So you're going to need a solution that can connect to multiple clouds. Simples lee, right? And with that comes the challenge off maintain ability. So you you you're going to need to look into a automation Ah, solution that that is easy to learn or has an easy learning curve. And then the fourth idea that we tell our customers is scalability in the in the hybrid cloud space scale is >>is >>a big, big deal here, and you need a to deploy an automation solution that can span across the whole enterprise in a constituent, consistent manner, right? And then also, that allows you finally to, uh, integrate the multiple data centers that you have, >>So A J I mean, this is a complicated situation, for if a customer has toe, make sure things work on AWS or azure or Google. Uh, they're gonna spend all their time doing that, huh? What can you add really? To simplify that that multi cloud and hybrid cloud equation? >>Yeah. I could give a few customer examples here Warming a manufacturer that we've worked with to drive that simplification Onda riel bonuses for them is has been a reduction cost. We worked with them late last year to bring the cost bend down by $10 million in 2021 so they could hit that reduced budget. Andre, What we brought to that was the ability thio deploy using open shift templates into their different environments. Where there is on premise on bond or in as you mentioned, a W s. They had G cps well, for their marketing team on a cross, those different platforms being out Thio use a template, use pre built scripts to get up and running in catalog and discover that data within minutes. It takes away the legacy of having teams of people having Thio to jump on workshop cause and I know we're all on a lot of teens. The zoom cause, um, in these current times, they just sent me is in in of hours in the day Thio manually perform all of this. So yeah, working with red hat applying machine learning into those templates those little recipes that we can put that automation toe work, regardless of which location the data is in allows us thio pull that unified view together. Right? >>Thank you, Fozzie. I wanna come back to you. So the early days of cloud, you're in the big apple, you know, financial services. Really well. Cloud was like an evil word within financial services, and obviously that's changed. It's evolved. We talked about the pandemic, has even accelerated that, Um And when you really, you know, dug into it when you talk to customers about their experiences with security in the cloud it was it was not that it wasn't good. It was great, whatever. But it was different. And there's always this issue of skill, lack of skills and multiple tools suck up teams, they're really overburdened. But in the cloud requires new thinking. You've got the shared responsibility model you've got obviously have specific corporate requirements and compliance. So this is even more complicated when you introduce multiple clouds. So what are the differences that you can share from your experience is running on a sort of either on Prem or on a mono cloud, um, or, you know, and versus across clouds. What? What? What do you suggest there? >>Yeah, you know, because of these complexities that you have explained here, Miss Configurations and the inadequate change control the top security threats. So human error is what we want to avoid because is, you know, as your clouds grow with complexity and you put humans in the mix, then the rate off eras is going to increase, and that is going to exposure to security threat. So this is where automation comes in because automation will streamline and increase the consistency off your infrastructure management. Also application development and even security operations to improve in your protection, compliance and change control. So you want to consistently configure resources according to a pre approved um, you know, pre approved policies and you want to proactively maintain a to them in a repeatable fashion over the whole life cycle. And then you also want to rapid the identified system that require patches and and reconfiguration and automate that process off patching and reconfiguring so that you don't have humans doing this type of thing, right? And you want to be able to easily apply patches and change assistant settings. According Thio, Pre defined, based on like explained before, you know, with the pre approved policies and also you want is off auditing and troubleshooting, right? And from a rate of perspective, we provide tools that enable you to do this. We have, for example, a tool called danceable that enables you to automate data center operations and security and also deployment of applications and also obvious shit yourself, you know, automates most of these things and obstruct the human beings from putting their fingers on, causing, uh, potentially introducing errors right now in looking into the new world off multiple clouds and so forth. The difference is that we're seeing here between running a single cloud or on prem is three main areas which is control security and compliance. Right control here it means if your on premise or you have one cloud, um, you know, in most cases you have control over your data and your applications, especially if you're on Prem. However, if you're in the public cloud, there is a difference there. The ownership, it is still yours. But your resources are running on somebody else's or the public clouds. You know, e w s and so forth infrastructure. So people that are going to do this need to really especially banks and governments need to be aware off the regulatory constraints off running, uh, those applications in the public cloud. And we also help customers regionalize some of these choices and also on security. You will see that if you're running on premises or in a single cloud, you have more control, especially if you're on Prem. You can control this sensitive information that you have, however, in the cloud. That's a different situation, especially from personal information of employees and things like that. You need to be really careful off that. And also again, we help you rationalize some of those choices. And then the last one is compliant. Aziz. Well, you see that if you're running on Prem or a single cloud, um, regulations come into play again, right? And if you're running a problem, you have control over that. You can document everything you have access to everything that you need. But if you're gonna go to the public cloud again, you need to think about that. We have automation, and we have standards that can help you, uh, you know, address some of these challenges for security and compliance. >>So that's really strong insights, Potsie. I mean, first of all, answerable has a lot of market momentum. Red hats in a really good job with that acquisition, your point about repeatability is critical because you can't scale otherwise. And then that idea you're you're putting forth about control, security compliance It's so true is I called it the shared responsibility model. And there was a lot of misunderstanding in the early days of cloud. I mean, yeah, maybe a W s is gonna physically secure the, you know, s three, but in the bucket. But we saw so many Miss configurations early on. And so it's key to have partners that really understand this stuff and can share the experiences of other clients. So this all sounds great. A j. You're sharp, you know, financial background. What about the economics? >>You >>know, our survey data shows that security it's at the top of the spending priority list, but budgets are stretched thin. E especially when you think about the work from home pivot and and all the areas that they had toe the holes that they had to fill their, whether it was laptops, you know, new security models, etcetera. So how do organizations pay for this? What's the business case look like in terms of maybe reducing infrastructure costs so I could, you know, pay it forward or there's a There's a risk reduction angle. What can you share >>their? Yeah. I mean, the perspective I'd like to give here is, um, not being multi cloud is multi copies of an application or data. When I think about 20 years, a lot of the work in financial services I was looking at with managing copies of data that we're feeding different pipelines, different applications. Now what we're saying I talk a lot of the work that we're doing is reducing the number of copies of that data so that if I've got a product lifecycle management set of data, if I'm a manufacturer, I'm just gonna keep that in one location. But across my different clouds, I'm gonna have best of breed applications developed in house third parties in collaboration with my supply chain connecting securely to that. That single version of the truth. What I'm not going to do is to copy that data. So ah, lot of what we're seeing now is that interconnectivity using applications built on kubernetes. Um, that decoupled from the data source that allows us to reduce those copies of data within that you're gaining from the security capability and resilience because you're not leaving yourself open to those multiple copies of data on with that. Couldn't come. Cost, cost of storage on duh cost of compute. So what we're seeing is using multi cloud to leverage the best of what each cloud platform has to offer That goes all the way to Snowflake and Hiroko on Cloud manage databases, too. >>Well, and the people cost to a swell when you think about yes, the copy creep. But then you know when something goes wrong, a human has to come in and figured out um, you brought up snowflake, get this vision of the data cloud, which is, you know, data data. I think this we're gonna be rethinking a j, uh, data architectures in the coming decade where data stays where it belongs. It's distributed, and you're providing access. Like you said, you're separating the data from the applications applications as we talked about with Fozzie. Much more portable. So it Z really the last 10 years will be different than the next 10 years. A. >>J Definitely. I think the people cast election is used. Gone are the days where you needed thio have a dozen people governing managing black policies to data. Ah, lot of that repetitive work. Those tests can be in power automated. We've seen examples in insurance were reduced teams of 15 people working in the the back office China apply security controls compliance down to just a couple of people who are looking at the exceptions that don't fit. And that's really important because maybe two years ago the emphasis was on regulatory compliance of data with policies such as GDP are in CCP a last year, very much the economic effect of reduce headcounts on on enterprises of running lean looking to reduce that cost. This year, we can see that already some of the more proactive cos they're looking at initiatives such as net zero emissions how they use data toe under understand how cape how they can become more have a better social impact. Um, and using data to drive that, and that's across all of their operations and supply chain. So those regulatory compliance issues that may have been external we see similar patterns emerging for internal initiatives that benefiting the environment, social impact and and, of course, course, >>great perspectives. Yeah, Jeff Hammer, Bucker once famously said, The best minds of my generation are trying to get people to click on ads and a J. Those examples that you just gave of, you know, social good and moving. Uh, things forward are really critical. And I think that's where Data is gonna have the biggest societal impact. Okay, guys, great conversation. Thanks so much for coming on the program. Really appreciate your time. Keep it right there from, or insight and conversation around, creating a resilient digital business model. You're watching the >>Cube digital resilience, automated compliance, privacy and security for your multi cloud. Congratulations. You're on the journey. You have successfully transformed your organization by moving to a cloud based platform to ensure business continuity in these challenging times. But as you scale your digital activities, there is an inevitable influx of users that outpaces traditional methods of cybersecurity, exposing your data toe underlying threats on making your company susceptible toe ever greater risk to become digitally resilient. Have you applied controls your data continuously throughout the data Lifecycle? What are you doing to keep your customer on supply data private and secure? I owe Tahoe's automated, sensitive data. Discovery is pre programmed with over 300 existing policies that meet government mandated risk and compliance standards. Thes automate the process of applying policies and controls to your data. Our algorithm driven recommendation engine alerts you to risk exposure at the data level and suggests the appropriate next steps to remain compliant on ensure sensitive data is secure. Unsure about where your organization stands In terms of digital resilience, Sign up for a minimal cost commitment. Free data Health check. Let us run our sensitive data discovery on key unmapped data silos and sources to give you a clear understanding of what's in your environment. Book time within Iot. Tahoe Engineer Now >>Okay, let's now get into the next segment where we'll explore data automation. But from the angle of digital resilience within and as a service consumption model, we're now joined by Yusuf Khan, who heads data services for Iot, Tahoe and Shirish County up in. Who's the vice president and head of U. S. Sales at happiest Minds? Gents, welcome to the program. Great to have you in the Cube. >>Thank you, David. >>Trust you guys talk about happiest minds. This notion of born digital, foreign agile. I like that. But talk about your mission at the company. >>Sure. >>A former in 2011 Happiest Mind is a born digital born a child company. The reason is that we are focused on customers. Our customer centric approach on delivering digitals and seamless solutions have helped us be in the race. Along with the Tier one providers, Our mission, happiest people, happiest customers is focused to enable customer happiness through people happiness. We have Bean ranked among the top 25 i t services company in the great places to work serving hour glass to ratings off 41 against the rating off. Five is among the job in the Indian nineties services company that >>shows the >>mission on the culture. What we have built on the values right sharing, mindful, integrity, learning and social on social responsibilities are the core values off our company on. That's where the entire culture of the company has been built. >>That's great. That sounds like a happy place to be. Now you said you had up data services for Iot Tahoe. We've talked in the past. Of course you're out of London. What >>do you what? Your >>day to day focus with customers and partners. What you focused >>on? Well, David, my team work daily with customers and partners to help them better understand their data, improve their data quality, their data governance on help them make that data more accessible in a self service kind of way. To the stakeholders within those businesses on dis is all a key part of digital resilience that will will come on to talk about but later. You're >>right, e mean, that self service theme is something that we're gonna we're gonna really accelerate this decade, Yussef and so. But I wonder before we get into that, maybe you could talk about the nature of the partnership with happiest minds, you know? Why do you guys choose toe work closely together? >>Very good question. Um, we see Hyo Tahoe on happiest minds as a great mutual fit. A Suresh has said, uh, happiest minds are very agile organization um, I think that's one of the key things that attracts their customers on Io. Tahoe is all about automation. Uh, we're using machine learning algorithms to make data discovery data cataloging, understanding, data done. See, uh, much easier on. We're enabling customers and partners to do it much more quickly. So when you combine our emphasis on automation with the emphasis on agility that happiest minds have that that's a really nice combination work works very well together, very powerful. I think the other things that a key are both businesses, a serious have said, are really innovative digital native type type companies. Um, very focused on newer technologies, the cloud etcetera on. Then finally, I think they're both Challenger brands on happiest minds have a really positive, fresh ethical approach to people and customers that really resonates with us at Ideo Tahoe to >>great thank you for that. So Russia, let's get into the whole notion of digital resilience. I wanna I wanna sort of set it up with what I see, and maybe you can comment be prior to the pandemic. A lot of customers that kind of equated disaster recovery with their business continuance or business resilient strategy, and that's changed almost overnight. How have you seen your clients respond to that? What? I sometimes called the forced march to become a digital business. And maybe you could talk about some of the challenges that they faced along the way. >>Absolutely. So, uh, especially during this pandemic, times when you say Dave, customers have been having tough times managing their business. So happiest minds. Being a digital Brazilian company, we were able to react much faster in the industry, apart from the other services company. So one of the key things is the organisation's trying to adopt onto the digital technologies. Right there has bean lot off data which has been to manage by these customers on There have been lot off threats and risk, which has been to manage by the CEO Seo's so happiest minds digital resilient technology, right where we bring in the data. Complaints as a service were ableto manage the resilience much ahead off other competitors in the market. We were ableto bring in our business continuity processes from day one, where we were ableto deliver our services without any interruption to the services. What we were delivered to our customers So that is where the digital resilience with business community process enabled was very helpful for us. Toe enable our customers continue their business without any interruptions during pandemics. >>So I mean, some of the challenges that customers tell me they obviously they had to figure out how to get laptops to remote workers and that that whole remote work from home pivot figure out how to secure the end points. And, you know, those were kind of looking back there kind of table stakes, But it sounds like you've got a digital business. Means a data business putting data at the core, I like to say, but so I wonder if you could talk a little bit more about maybe the philosophy you have toward digital resilience in the specific approach you take with clients? >>Absolutely. They seen any organization data becomes. The key on that, for the first step is to identify the critical data. Right. So we this is a six step process. What we following happiest minds. First of all, we take stock off the current state, though the customers think that they have a clear visibility off their data. How are we do more often assessment from an external point off view on see how critical their data is, then we help the customers to strategies that right. The most important thing is to identify the most important critical herself. Data being the most critical assert for any organization. Identification off the data's key for the customers. Then we help in building a viable operating model to ensure these identified critical assets are secure on monitor dearly so that they are consumed well as well as protected from external threats. Then, as 1/4 step, we try to bring in awareness, toe the people we train them >>at >>all levels in the organization. That is a P for people to understand the importance off the digital ourselves and then as 1/5 step, we work as a back up plan in terms of bringing in a very comprehensive and a holistic testing approach on people process as well as in technology. We'll see how the organization can withstand during a crisis time, and finally we do a continuous governance off this data, which is a key right. It is not just a one step process. We set up the environment, we do the initial analysis and set up the strategy on continuously govern this data to ensure that they are not only know managed will secure as well as they also have to meet the compliance requirements off the organization's right. That is where we help organizations toe secure on Meet the regulations off the organizations. As for the privacy laws, so this is a constant process. It's not on one time effort. We do a constant process because every organization goes towards their digital journey on. They have to face all these as part off the evolving environment on digital journey. And that's where they should be kept ready in terms off. No recovering, rebounding on moving forward if things goes wrong. >>So let's stick on that for a minute, and then I wanna bring yourself into the conversation. So you mentioned compliance and governance when when your digital business, you're, as you say, you're a data business, so that brings up issues. Data sovereignty. Uh, there's governance, this compliance. There's things like right to be forgotten. There's data privacy, so many things. These were often kind of afterthoughts for businesses that bolted on, if you will. I know a lot of executives are very much concerned that these air built in on, and it's not a one shot deal. So do you have solutions around compliance and governance? Can you deliver that as a service? Maybe you could talk about some of the specifics there, >>so some of way have offered multiple services. Tow our customers on digital against. On one of the key service is the data complaints. As a service here we help organizations toe map the key data against the data compliance requirements. Some of the features includes in terms off the continuous discovery off data right, because organizations keep adding on data when they move more digital on helping the helping and understanding the actual data in terms off the residents of data, it could be a heterogeneous data soldiers. It could be on data basis, or it could be even on the data legs. Or it could be a no even on compromise all the cloud environment. So identifying the data across the various no heterogeneous environment is very key. Feature off our solution. Once we identify classify this sensitive data, the data privacy regulations on the traveling laws have to be map based on the business rules So we define those rules on help map those data so that organizations know how critical their digital assets are. Then we work on a continuous marching off data for anomalies because that's one of the key teachers off the solution, which needs to be implemented on the day to day operational basis. So we're helping monitoring those anomalies off data for data quality management on an ongoing basis. On finally, we also bringing the automated data governance where we can manage the sensory data policies on their later relationships in terms off mapping on manage their business roots on we drive reputations toe Also suggest appropriate actions to the customers. Take on those specific data sets. >>Great. Thank you, Yousef. Thanks for being patient. I want to bring in Iota ho thio discussion and understand where your customers and happiest minds can leverage your data automation capability that you and I have talked about in the past. I'm gonna be great if you had an example is well, but maybe you could pick it up from there, >>John. I mean, at a high level, assertions are clearly articulated. Really? Um, Hyoty, who delivers business agility. So that's by, um accelerating the time to operationalize data, automating, putting in place controls and actually putting helping put in place digital resilience. I mean way if we step back a little bit in time, um, traditional resilience in relation to data often met manually, making multiple copies of the same data. So you have a d b A. They would copy the data to various different places, and then business users would access it in those functional style owes. And of course, what happened was you ended up with lots of different copies off the same data around the enterprise. Very inefficient. ONDA course ultimately, uh, increases your risk profile. Your risk of a data breach. Um, it's very hard to know where everything is. And I realized that expression. They used David the idea of the forced march to digital. So with enterprises that are going on this forced march, what they're finding is they don't have a single version of the truth, and almost nobody has an accurate view of where their critical data is. Then you have containers bond with containers that enables a big leap forward so you could break applications down into micro services. Updates are available via a p I s on. So you don't have the same need thio to build and to manage multiple copies of the data. So you have an opportunity to just have a single version of the truth. Then your challenge is, how do you deal with these large legacy data states that the service has been referring Thio, where you you have toe consolidate and that's really where I attack comes in. Um, we massively accelerate that process of putting in a single version of the truth into place. So by automatically discovering the data, discovering what's dubica? What's redundant? Uh, that means you can consolidate it down to a single trusted version much more quickly. We've seen many customers have tried to do this manually, and it's literally taken years using manual methods to cover even a small percentage of their I T estates. With our tire, you could do it really very quickly on you can have tangible results within weeks and months on Ben, you can apply controls to the data based on context. So who's the user? What's the content? What's the use case? Things like data quality validations or access permissions on. Then, once you've done there. Your applications and your enterprise are much more secure, much more resilient. As a result, you've got to do these things whilst retaining agility, though. So coming full circle. This is where the partnership with happiest minds really comes in as well. You've got to be agile. You've gotta have controls. Um, on you've got a drug toward the business outcomes. Uh, and it's doing those three things together that really deliver for the customer. >>Thank you. Use f. I mean you and I. In previous episodes, we've looked in detail at the business case. You were just talking about the manual labor involved. We know that you can't scale, but also there's that compression of time. Thio get to the next step in terms of ultimately getting to the outcome. And we talked to a number of customers in the Cube, and the conclusion is, it's really consistent that if you could accelerate the time to value, that's the key driver reducing complexity, automating and getting to insights faster. That's where you see telephone numbers in terms of business impact. So my question is, where should customers start? I mean, how can they take advantage of some of these opportunities that we've discussed today. >>Well, we've tried to make that easy for customers. So with our Tahoe and happiest minds, you can very quickly do what we call a data health check. Um, this is a is a 2 to 3 week process, uh, to really quickly start to understand on deliver value from your data. Um, so, iota, who deploys into the customer environment? Data doesn't go anywhere. Um, we would look at a few data sources on a sample of data. Onda. We can very rapidly demonstrate how they discovery those catalog e on understanding Jupiter data and redundant data can be done. Um, using machine learning, um, on how those problems can be solved. Um, And so what we tend to find is that we can very quickly, as I say in the matter of a few weeks, show a customer how they could get toe, um, or Brazilian outcome on then how they can scale that up, take it into production on, then really understand their data state? Better on build. Um, Brasiliense into the enterprise. >>Excellent. There you have it. We'll leave it right there. Guys, great conversation. Thanks so much for coming on the program. Best of luck to you and the partnership Be well, >>Thank you, David Suresh. Thank you. Thank >>you for watching everybody, This is Dave Volonte for the Cuban are ongoing Siris on data automation without >>Tahoe, digital resilience, automated compliance, privacy and security for your multi cloud. Congratulations. You're on the journey. You have successfully transformed your organization by moving to a cloud based platform to ensure business continuity in these challenging times. But as you scale your digital activities, there is an inevitable influx of users that outpaces traditional methods of cybersecurity, exposing your data toe underlying threats on making your company susceptible toe ever greater risk to become digitally resilient. Have you applied controls your data continuously throughout the data lifecycle? What are you doing to keep your customer on supply data private and secure? I owe Tahoe's automated sensitive data. Discovery is pre programmed with over 300 existing policies that meet government mandated risk and compliance standards. Thes automate the process of applying policies and controls to your data. Our algorithm driven recommendation engine alerts you to risk exposure at the data level and suggests the appropriate next steps to remain compliant on ensure sensitive data is secure. Unsure about where your organization stands in terms of digital resilience. Sign up for our minimal cost commitment. Free data health check. Let us run our sensitive data discovery on key unmapped data silos and sources to give you a clear understanding of what's in your environment. Book time within Iot. Tahoe Engineer. Now. >>Okay, now we're >>gonna go into the demo. We want to get a better understanding of how you can leverage open shift. And I owe Tahoe to facilitate faster application deployment. Let me pass the mic to Sabetta. Take it away. >>Uh, thanks, Dave. Happy to be here again, Guys, uh, they've mentioned names to be the Davis. I'm the enterprise account executive here. Toyota ho eso Today we just wanted to give you guys a general overview of how we're using open shift. Yeah. Hey, I'm Noah Iota host data operations engineer, working with open ship. And I've been learning the Internets of open shift for, like, the past few months, and I'm here to share. What a plan. Okay, so So before we begin, I'm sure everybody wants to know. Noel, what are the benefits of using open shift. Well, there's five that I can think of a faster time, the operation simplicity, automation control and digital resilience. Okay, so that that's really interesting, because there's an exact same benefits that we had a Tahoe delivered to our customers. But let's start with faster time the operation by running iota. Who on open shift? Is it faster than, let's say, using kubernetes and other platforms >>are >>objective iota. Who is to be accessible across multiple cloud platforms, right? And so by hosting our application and containers were able to achieve this. So to answer your question, it's faster to create and use your application images using container tools like kubernetes with open shift as compared to, like kubernetes with docker cry over container D. Okay, so we got a bit technical there. Can you explain that in a bit more detail? Yeah, there's a bit of vocabulary involved, uh, so basically, containers are used in developing things like databases, Web servers or applications such as I have top. What's great about containers is that they split the workload so developers can select the libraries without breaking anything. And since Hammond's can update the host without interrupting the programmers. Uh, now, open shift works hand in hand with kubernetes to provide a way to build those containers for applications. Okay, got It s basically containers make life easier for developers and system happens. How does open shift differ from other platforms? Well, this kind of leads into the second benefit I want to talk about, which is simplicity. Basically, there's a lot of steps involved with when using kubernetes with docker. But open shift simplifies this with their source to image process that takes the source code and turns it into a container image. But that's not all. Open shift has a lot of automation and features that simplify working with containers, an important one being its Web console. Here. I've set up a light version of open ship called Code Ready Containers, and I was able to set up her application right from the Web console. And I was able to set up this entire thing in Windows, Mac and Lennox. So its environment agnostic in that sense. Okay, so I think I've seen the top left that this is a developers view. What would a systems admin view look like? It's a good question. So here's the administrator view and this kind of ties into the benefit of control. Um, this view gives insights into each one of the applications and containers that are running, and you could make changes without affecting deployment. Andi can also, within this view, set up each layer of security, and there's multiple that you can prop up. But I haven't fully messed around with it because with my luck, I'd probably locked myself out. So that seems pretty secure. Is there a single point security such as you use a log in? Or are there multiple layers of security? Yeah, there are multiple layers of security. There's your user login security groups and general role based access controls. Um, but there's also a ton of layers of security surrounding like the containers themselves. But for the sake of time, I won't get too far into it. Okay, eso you mentioned simplicity In time. The operation is being two of the benefits. You also briefly mention automation. And as you know, automation is the backbone of our platform here, Toyota Ho. So that's certainly grabbed my attention. Can you go a bit more in depth in terms of automation? Open shift provides extensive automation that speeds up that time the operation. Right. So the latest versions of open should come with a built in cryo container engine, which basically means that you get to skip that container engine insulation step and you don't have to, like, log into each individual container host and configure networking, configure registry servers, storage, etcetera. So I'd say, uh, it automates the more boring kind of tedious process is Okay, so I see the iota ho template there. What does it allow me to do? Um, in terms of automation in application development. So we've created an open shift template which contains our application. This allows developers thio instantly, like set up our product within that template. So, Noah Last question. Speaking of vocabulary, you mentioned earlier digital resilience of the term we're hearing, especially in the banking and finance world. Um, it seems from what you described, industries like banking and finance would be more resilient using open shift, Correct. Yeah, In terms of digital resilience, open shift will give you better control over the consumption of resource is each container is using. In addition, the benefit of containers is that, like I mentioned earlier since Hammond's can troubleshoot servers about bringing down the application and if the application does go down is easy to bring it back up using templates and, like the other automation features that open ship provides. Okay, so thanks so much. Know us? So any final thoughts you want to share? Yeah. I just want to give a quick recap with, like, the five benefits that you gained by using open shift. Uh, the five are timeto operation automation, control, security and simplicity. You could deploy applications faster. You could simplify the workload you could automate. A lot of the otherwise tedious processes can maintain full control over your workflow. And you could assert digital resilience within your environment. Guys, >>Thanks for that. Appreciate the demo. Um, I wonder you guys have been talking about the combination of a Iot Tahoe and red hat. Can you tie that in subito Digital resilience >>Specifically? Yeah, sure, Dave eso when we speak to the benefits of security controls in terms of digital resilience at Io Tahoe, we automated detection and apply controls at the data level, so this would provide for more enhanced security. >>Okay, But so if you were trying to do all these things manually. I mean, what what does that do? How much time can I compress? What's the time to value? >>So with our latest versions, Biota we're taking advantage of faster deployment time associated with container ization and kubernetes. So this kind of speeds up the time it takes for customers. Start using our software as they be ableto quickly spin up io towel on their own on premise environment are otherwise in their own cloud environment, like including aws. Assure or call GP on IBM Cloud a quick start templates allow flexibility deploy into multi cloud environments all just using, like, a few clicks. Okay, so so now just quickly add So what we've done iota, Who here is We've really moved our customers away from the whole idea of needing a team of engineers to apply controls to data as compared to other manually driven work flows. Eso with templates, automation, previous policies and data controls. One person can be fully operational within a few hours and achieve results straight out of the box on any cloud. >>Yeah, we've been talking about this theme of abstracting the complexity. That's really what we're seeing is a major trend in in this coming decade. Okay, great. Thanks, Sabina. Noah, How could people get more information or if they have any follow up questions? Where should they go? >>Yeah, sure. They've. I mean, if you guys are interested in learning more, you know, reach out to us at info at iata ho dot com to speak with one of our sales engineers. I mean, we love to hear from you, so book a meeting as soon as you can. All >>right. Thanks, guys. Keep it right there from or cube content with.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud, Native Computing Foundation and Ecosystem Partners. Hello, everyone. And welcome back to the cubes Ongoing coverage of Cuba con North America. Joe Fernandez is here. He's with Stephanie, Cheras and Joe's, the V, P and GM for core cloud platforms. That red hat and Stephanie is this s VP and GM of the Red Hat Enterprise. Lennox bu. Two great friends of the Cube. Awesome seeing you guys. How you doing? >>It's great to be here, Dave. Yeah, thanks >>for the opportunity. >>Hey, so we all talked, you know, recently, uh, answerable fest Seems like a while ago, but But we talked about what's new? Red hat really coming at it from an automation perspective. But I wonder if we could take a view from open shift and what's new from the standpoint of you really focus on helping customers, you know, change their operations and operationalize. And Stephanie, Maybe you could start, and then, you know, Joe, you could bring in some added color. >>No, that's great. And I think you know one of the things we try and do it. Red hat clearly building off of open source. We have been focused on this open hybrid cloud strategy for, you know, really years. Now the beauty of it is that hybrid cloud and open hybrid cloud continues to evolve right with bringing in things like speed and stability and scale and now adding in other footprints, like manage services as well as edge and pulling that all together across the whole red hat portfolio from the platforms, right? Certainly with Lennox and roll into open shift in the platform with open shift and then adding automation, which certainly you need for scale. But it's ah, it's continues to evolve as the as the definition of open hybrid cloud evolves. >>Great. So thank you, Stephanie jokes. You guys got hard news here that you could maybe talk about 46? >>Yeah. Eso eso open shift is our enterprise kubernetes platform. With this announcement, we announced the release of open ship 4.6 Eso eso We're doing releases every quarter tracking the upstream kubernetes release cycle. So this brings communities 1.19, which is, um but itself brings a number of new innovations, some specific things to call out. We have this new automated installer for open shift on bare metal, and that's definitely a trend that we're seeing is more customers not only looking at containers but looking at running containers directly on bare metal environments. Open shift provides an abstraction, you know, which combines Cuban. And he's, uh, on top of Lennox with RL. I really across all environments, from bare metal to virtualization platforms to the various public clouds and out to the edge. But we're seeing a lot of interest in bare metal. This is basically increasing the really three automation to install seamlessly and manage upgrades in those environments. We're also seeing a number of other enhancements open shifts service mesh, which is our SDO based solution for managing, uh, the interactions between micro services being able to manage traffic against those services. Being able to do tracing. We have a new release of that on open shift Ford out six on then, um, some work specific to the public cloud that we started extending into the government clouds. So we already supported AWS and Azure. With this release, we added support for the A W s government cloud as well. Azaz Acela's Microsoft Azure government on dso again This is really important to like our public sector customers who are looking to move to the public cloud leveraging open shift as an abstraction but wanted thio support it on the specialized clouds that they need to use with azure gonna meet us Cup. >>So, joke, we stay there for a minute. So so bare metal talking performance there because, you know, you know what? You really want to run fast, right? So that's the attractiveness there. And then the point about SDO in the open, open shift service measure that makes things simpler. Maybe talk a little bit about sort of business impact and what customers should expect to get out of >>these two things. So So let me take them one at a time, right? So so running on bare metal certainly performances a consideration. You know, I think a lot of fixed today are still running containers, and Cuban is on top of some form of virtualization. Either a platform like this fear or open stack, or maybe VMS in the in one of the public clouds. But, you know containers don't depend on a virtualization layer. Containers only depend on Lennox and Lennox runs great on bare metal. So as we see customers moving more towards performance and Leighton see sensitive workloads, they want to get that Barry mental performance on running open shift on bare metal and their containerized applications on that, uh, platform certainly gives them that advantage. Others just want to reduce the cost right. They want to reduce their VM sprawl, the infrastructure and operational cost of managing avert layer beneath their careers clusters. And that's another benefit. So we see a lot of uptake in open shift on bare metal on the service match side. This is really about You know how we see applications evolving, right? Uh, customers are moving more towards these distributed architectures, taking, you know, formally monolithic or enter applications and splitting them out into ah, lots of different services. The challenge there becomes. Then how do you manage all those connections? Right, Because something that was a single stack is now comprised of tens or hundreds of services on DSO. You wanna be able to manage traffic to those services, so if the service goes down, you can redirect that those requests thio to an alternative or fail over service. Also tracing. If you're looking at performance issues, you need to know where in your architecture, er you're having those degradations and so forth. And, you know, those are some of the challenges that people can sort of overcome or get help with by using service mash, which is powered by SDO. >>And then I'm sorry, Stephanie ever get to in a minute. But which is 11 follow up on that Joe is so the rial differentiation between what you bring in what I can just if I'm in a mono cloud, for instance is you're gonna you're gonna bring this across clouds. I'm gonna You're gonna bring it on, Prem And we're gonna talk about the edge in in a minute. Is that right? From a differentiation standpoint, >>Yeah, that That's one of the key >>differentiations. You know, Read has been talking about the hybrid cloud for a long time. We've we've been articulating are open hybrid cloud strategy, Andi, >>even if that's >>not a strategy that you may be thinking about, it is ultimately where folks end up right, because all of our enterprise customers still have applications running in the data center. But they're also all starting to move applications out to the public cloud. As they expand their usage of public cloud, you start seeing them adopted multi cloud strategies because they don't want to put all their eggs in one basket. And then for certain classes of applications, they need to move those applications closer to the data. And and so you start to see EJ becoming part of that hybrid cloud picture on DSO. What we do is basically provide a consistency across all those environments, right? We want run great on Amazon, but also great on Azure on Google on bare metal in the data center during medal out at the edge on top of your favorite virtualization platform. And yeah, that that consistency to take a set of applications and run them the same way across all those environments. That is just one of the key benefits of going with red hat as your provider for open hybrid cloud solutions. >>All right, thank you. Stephanie would come back to you here, so I mean, we talk about rail a lot because your business unit that you manage, but we're starting to see red hats edge strategy unfolded. Kind of real is really the linchpin I wanna You could talk about how you're thinking about the edge and and particularly interested in how you're handling scale and why you feel like you're in a good position toe handle that massive scale on the requirements of the edge and versus hey, we need a new OS for the edge. >>Yeah, I think. And Joe did a great job of said and up it does come back to our view around this open hybrid cloud story has always been about consistency. It's about that language that you speak, no matter where you want to run your applications in between rela on on my side and Joe with open shift and and of course, you know we run the same Lennox underneath. So real core os is part of open shift that consistently see leads to a lot of flexibility, whether it's through a broad ecosystem or it's across footprints. And so now is we have been talking with customers about how they want to move their applications closer to data, you know, further out and away from their data center. So some of it is about distributing your data center, getting that compute closer to the data or closer to your customers. It drives, drives some different requirements right around. How you do updates, how you do over the air updates. And so we have been working in typical red hat fashion, right? We've been looking at what's being done in the upstream. So in the fedora upstream community, there is a lot of working that has been done in what's called the I. O. T Special Interest group. They have been really investigating what the requirements are for this use case and edge. So now we're really pleased in, um, in our most recent release of really aid relate 00.3. We have put in some key capabilities that we're seeing being driven by these edge use cases. So things like How do you do quick image generation? And that's important because, as you distribute, want that consistency created tailored image, be able to deploy that in a consistent way, allow that to address scale, meet security requirements that you may have also right updates become very important when you start to spread this out. So we put in things in order to allow remote device mirroring so that you can put code into production and then you can schedule it on those remote devices toe happen with the minimal disruption. Things like things like we all know now, right with all this virtual stuff, we often run into things like not ideal bandwidth and sometimes intermittent connectivity with all of those devices out there. So we put in, um, capabilities around, being able to use something called rpm Austria, Um, in order to be able to deliver efficient over the air updates. And then, of course, you got to do intelligent rollbacks for per chance that something goes wrong. How do you come back to a previous state? So it's all about being able to deploy at scale in a distributed way, be ready for that use case and have some predictability and consistency. And again, that's what we build our platforms for. It's all about predictability and consistency, and that gives you flexibility to add your innovation on top. >>I'm glad you mentioned intelligent rollbacks I learned a long time ago. You always ask the question. What happens when something goes wrong? You learn a lot from the answer to that, but You know, we talk a lot about cloud native. Sounds like you're adapting well to become edge native. >>Yeah. I mean, I mean, we're finding whether it's inthe e verticals, right in the very specific use cases or whether it's in sort of an enterprise edge use case. Having consistency brings a ton of flexibility. It was funny, one of our talking with a customer not too long ago. And they said, you know, agility is the new version of efficiency. So it's that having that sort of language be spoken everywhere from your core data center all the way out to the edge that allows you a lot of flexibility going forward. >>So what if you could talk? I mentioned just mentioned Cloud Native. I mean, I think people sometimes just underestimate the effort. It takes tow, make all this stuff run in all the different clouds the engineering efforts required. And I'm wondering what kind of engineering you do with if any with the cloud providers and and, of course, the balance of the ecosystem. But But maybe you could describe that a little bit. >>Yeah, so? So Red Hat works closely with all the major cloud providers you know, whether that's Amazon, Azure, Google or IBM Cloud. Obviously, Andi, we're you know, we're very keen on sort of making sure that we're providing the best environment to run enterprise applications across all those environments, whether you're running it directly just with Lennox on Ralph or whether you're running it in a containerized environment with Open Chef, which which includes route eso eso, our partnership includes work we do upstream, for example. You know, Red Hat help. Google launched the Cuban community, and I've been, you know, with Google. You know, we've been the top two contributors driving that product that project since inception, um, but then also extends into sort of our hosted services. So we run a jointly developed and jointly managed service called the Azure Red Hat Open Shift Service. Together with Microsoft were our joint customers can get access to open shift in an azure environment as a native azure service, meaning it's, you know, it's fully integrated, just like any other. As your service you can tied into as you're building and so forth. It's sold by by Azure Microsoft's sales reps. Um, but you know, we get the benefit of working together with our Microsoft counterparts and developing that service in managing that service and then in supporting our joint customers. We over the summer announced sort of a similar partnership with Amazon and we'll be launching are already doing pilots on the Amazon Red Hat Open ship service, which is which is, you know, the same concept now applied to the AWS cloud. So that will be coming out g a later this year, right? But again, whether it's working upstream or whether it's, you know, partnering on managed services. I know Stephanie team also do a lot of work with Microsoft, for example, on sequel server on Lenox dot net on Lenox. Whoever thought be running that applications on Linux. But that's, you know, a couple of years old now, a few years old, So eso again. It's been a great partnership, not just with Microsoft, but with all the cloud providers. >>So I think you just shared a little little He showed a little leg there, Joe, what's what's coming g A. Later this year. I want to circle back to >>that. Yeah, eso we way announced a preview earlier this year of of the Amazon Red Hat Open ships service. It's not generally available yet. We're you know, we're taking customers. We want toe, sort of be early access, get access to pilots and then that'll be generally available later this year. Although Red Hat does manage our own service Open ship dedicated that's available on AWS today. But that's a service that's, you know, solely, uh, operated by Red Hat. This new service will be jointly operated by Red Hat and Amazon together Idea. That would be sort of a service that we are delivering together as partners >>as a managed service and and okay, so that's in beta now. I presume if it's gonna be g a little, it's >>like, Yeah, that's yeah, >>that's probably running on bare metal. I would imagine that >>one is running >>on E. C. Two. That's running an A W C C T V exactly, and >>run again. You know, all of our all of >>our I mean, we you know, that open shift does offer bare metal cloud, and we do you know, we do have customers who can take the open shift software and deploy it there right now are managed. Offering is running on top of the C two and on top of Azure VM. But again, this is this is appealing to customers who, you know, like what we bring in terms of an enterprise kubernetes platform, but don't wanna, you know, operated themselves, right? So it's a fully managed service. You just come and build and deploy your APS, and then we manage all of the infrastructure and all the underlying platform for you >>that's going to explode. My prediction. Um, let's take an example of heart example of security. And I'm interested in how you guys ensure a consistent, you know, security experience across all these locations on Prem Cloud. Multiple clouds, the edge. Maybe you could talk about that. And Stephanie, I'm sure you have a perspective on this is Well, from the standpoint of of Ralph. So who wants to start? >>Yeah, Maybe I could start from the bottom and then I'll pass it over to Joe to talk a bit. I think one of these aspects about security it's clearly top of mind of all customers. Um, it does start with the very bottom and base selection in your OS. We continue to drive SC Lennox capabilities into rural to provide that foundational layer. And then as we run real core OS and open shift, we bring over that s C Lennox capability as well. Um, but, you know, there's a whole lot of ways to tackle this we've done. We've done a lot around our policies around, um see ve updates, etcetera around rail to make sure that we are continuing to provide on DCA mitt too. Mitigating all critical and importance, providing better transparency toe how we assess those CVS. So security is certainly top of mind for us. And then as we move forward, right there's also and joke and talk about the security work we do is also capabilities to do that in container ization. But you know, we we work. We work all the way from the base to doing things like these images in these easy to build images, which are tailored so you can make them smaller, less surface area for security. Security is one of those things. That's a lifestyle, right? You gotta look at it from all the way the base in the operating system, with things like sc Lennox toe how you build your images, which now we've added new capabilities. There And then, of course, in containers. There's, um there's a whole focus in the open shift area around container container security, >>Joe. Anything you want to add to that? >>Yeah, sure. I >>mean, I think, you know, obviously, Lennox is the foundation for, you know, for all public clouds. It's it's driving enterprise applications in the data center, part of keeping those applications. Security is keeping them up to date And, you know, through, you know, through real, we provide, you know, securing up to date foundation as a Stephanie mentioned as you move into open shift, you're also been able to take advantage of, uh, Thio to take advantage of essentially mutability. Right? So now the application that you're deploying isn't immutable unit that you build once as a container image, and then you deploy that out all your various environments. When you have to do an update, you don't go and update all those environments. You build a new image that includes those updates, and then you deploy those images out rolling fashion and, as you mentioned that you could go back if there's issues. So the idea, the notion of immutable application deployments has a lot to do with security, and it's enabled by containers. And then, obviously you have cured Panetti's and, you know, and all the rest of our capabilities as part of open Shift managing that for you. We've extended that concept to the entire platform. So Stephanie mentioned, real core West Open shift has always run on real. What we have done in open shift for is we've taken an immutable version of Ralph. So it's the same red hat enterprise Lennox that we've had for years. But now, in this latest version relate, we have a new way to package and deploy it as a relic or OS image, and then that becomes part of the platform. So when customers want toe in addition to keeping their applications up to date, they need to keep their platform up to dates. Need to keep, you know, up with the latest kubernetes patches up with the latest Lennox packages. What we're doing is delivering that as one platform, so when you get updates for open shift, they could include updates for kubernetes. They could include updates for Lennox itself as well as all the integrated services and again, all of this is just you know this is how you keep your applications secure. Is making sure your you know, taking care of that hygiene of, you know, managing your vulnerabilities, keeping everything patched in up to date and ultimately ensuring security for your application and users. >>I know I'm going a little bit over, but I have I have one question that I wanna ask you guys and a broad question about maybe a trends you see in the business. I mean, you look at what we talk a lot about cloud native, and you look at kubernetes and the interest in kubernetes off the charts. It's an area that has a lot of spending momentum. People are putting resource is behind it. But you know, really, to build these sort of modern applications, it's considered state of the art on. Do you see a lot of people trying to really bring that modern approach toe any cloud we've been talking about? EJ. You wanna bring it also on Prem And people generally associate this notion of cloud native with this kind of elite developers, right? But you're bringing it to the masses and there's 20 million plus software developers out there, and most you know, with all due respect that you know they may not be the the the elites of the elite. So how are you seeing this evolve in terms of re Skilling people to be able, handle and take advantage of all this? You know, cool new stuff that's coming out. >>Yeah, I can start, you know, open shift. Our focus from the beginning has been bringing kubernetes to the enterprise. So we think of open shift as the dominant enterprise kubernetes platform enterprises come in all shapes and sizes and and skill sets. As you mentioned, they have unique requirements in terms of how they need toe run stuff in their data center and then also bring that to production, whether it's in the data center across the public clouds eso So part of it is, you know, making sure that the technology meets the requirements and then part of it is working. The people process and and culture thio make them help them understand what it means to sort of take advantage of container ization and cloud native platforms and communities. Of course, this is nothing new to red hat, right? This is what we did 20 years ago when we first brought Lennox to the Enterprise with well, right on. In essence, Carozza is basically distributed. Lennox right Kubernetes builds on Lennox and brings it out to your cluster to your distributed systems on across the hybrid cloud. So So nothing new for Red Hat. But a lot of the same challenges apply to this new cloud native world. >>Awesome. Stephanie, we'll give you the last word, >>all right? And I think just a touch on what Joe talked about it. And Joe and I worked really closely on this, right? The ability to run containers right is someone launches down this because it is magical. What could be done with deploying applications? Using a container technology, we built the capabilities and the tools directly into rural in order to be able to build and deploy, leveraging things like pod man directly into rural. And that's exactly so, folks. Everyone who has a real subscription today can start on their container journey, start to build and deploy that, and then we work to help those skills then be transferrable as you movinto open shift in kubernetes and orchestration. So, you know, we work very closely to make sure that the skills building can be done directly on rail and then transfer into open shift. Because, as Joe said, at the end of the day, it's just a different way to deploy. Lennox, >>You guys are doing some good work. Keep it up. And thanks so much for coming back in. The Cube is great to talk to you today. >>Good to see you, Dave. >>Yes, Thank you. >>All right. Thank you for watching everybody. The cubes coverage of Cuba con en a continues right after this.

>> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, (upbeat music) >> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, I've got the Keynote file there. YAMLs, I've got Dockerfiles, Compose files, all that good stuff. If you want to follow along, great, if not go back and review later, kind of fun. So let me tell you a little bit about myself. I am a former DOD contractor. This is my seventh DockerCon. I've spoken, I had the pleasure to speak at a few of them, one even in Europe. I was even a Docker employee for quite a number of years, providing solutions to the federal government and customers around containers and all things Docker. So I've been doing this a little while. One of the things that I always found interesting was the lack of understanding around labels. So why labels, right? Well, as a former DOD contractor, I had built out a large registry. And the question I constantly got was, where did this image come from? How did you get it? What's in it? Where did it come from? How did it get here? And one of the things we did to kind of alleviate some of those questions was we established a baseline set of labels. Labels really are designed to provide as much metadata around the image as possible. I ask everyone in attendance, when was the last time you pulled an image and had 100% confidence, you knew what was inside it, where it was built, how it was built, when it was built, you probably didn't, right? The last thing we obviously want is a container fire, like our image on the screen. And one kind of interesting way we can kind of prevent that is through the use of labels. We can use labels to address security, address some of the simplicity on how to run these images. So think of it, kind of like self documenting, Think of it also as an audit trail, image provenance, things like that. These are some interesting concepts that we can definitely mandate as we move forward. What is a label, right? Specifically what is the Schema? It's just a key-value. All right? It's any key and pretty much any value. What if we could dump in all kinds of information? What if we could encode things and store it in there? And I've got a fun little demo to show you about that. Let's start off with some of the simple keys, right? Author, date, description, version. Some of the basic information around the image. That would be pretty useful, right? What about specific labels for CI? What about a, where's the version control? Where's the source, right? Whether it's Git, whether it's GitLab, whether it's GitHub, whether it's Gitosis, right? Even SPN, who cares? Where are the source files that built, where's the Docker file that built this image? What's the commit number? That might be interesting in terms of tracking the resulting image to a person or to a commit, hopefully then to a person. How is it built? What if you wanted to play with it and do a git clone of the repo and then build the Docker file on your own? Having a label specifically dedicated on how to build this image might be interesting for development work. Where it was built, and obviously what build number, right? These kind of all, not only talk about continuous integration, CI but also start to talk about security. Specifically what server built it. The version control number, the version number, the commit number, again, how it was built. What's the specific build number? What was that job number in, say, Jenkins or GitLab? What if we could take it a step further? What if we could actually apply policy enforcement in the build pipeline, looking specifically for some of these specific labels? I've got a good example of, in my demo of a policy enforcement. So let's look at some sample labels. Now originally, this idea came out of label-schema.org. And then it was a modified to opencontainers, org.opencontainers.image. There is a link in my GitHub page that links to the full reference. But these are some of the labels that I like to use, just as kind of like a standardization. So obviously, Author's, an email address, so now the image is attributable to a person, that's always kind of good for security and reliability. Where's the source? Where's the version control that has the source, the Docker file and all the assets? How it was built, build number, build server the commit, we talked about, when it was created, a simple description. A fun one I like adding in is the healthZendpoint. Now obviously, the health check directive should be in the Docker file. But if you've got other systems that want to ping your applications, why not declare it and make it queryable? Image version, obviously, that's simple declarative And then a title. And then I've got the two fun ones. Remember, I talked about what if we could encode some fun things? Hypothetically, what if we could encode the Compose file of how to build the stack in the first image itself? And conversely the Kubernetes? Well, actually, you can and I have a demo to show you how to kind of take advantage of that. So how do we create labels? And really creating labels as a function of build time okay? You can't really add labels to an image after the fact. The way you do add labels is either through the Docker file, which I'm a big fan of, because it's declarative. It's in version control. It's kind of irrefutable, especially if you're tracking that commit number in a label. You can extend it from being a static kind of declaration to more a dynamic with build arguments. And I can show you, I'll show you in a little while how you can use a build argument at build time to pass in that variable. And then obviously, if you did it by hand, you could do a docker build--label key equals value. I'm not a big fan of the third one, I love the first one and obviously the second one. Being dynamic we can take advantage of some of the variables coming out of version control. Or I should say, some of the variables coming out of our CI system. And that way, it self documents effectively at build time, which is kind of cool. How do we view labels? Well, there's two major ways to view labels. The first one is obviously a docker pull and docker inspect. You can pull the image locally, you can inspect it, you can obviously, it's going to output as JSON. So you going to use something like JQ to crack it open and look at the individual labels. Another one which I found recently was Skopeo from Red Hat. This allows you to actually query the registry server. So you don't even have to pull the image initially. This can be really useful if you're on a really small development workstation, and you're trying to talk to a Kubernetes cluster and wanting to deploy apps kind of in a very simple manner. Okay? And this was that use case, right? Using Kubernetes, the Kubernetes demo. One of the interesting things about this is that you can base64 encode almost anything, push it in as text into a label and then base64 decode it, and then use it. So in this case, in my demo, I'll show you how we can actually use a kubectl apply piped from the base64 decode from the label itself from skopeo talking to the registry. And what's interesting about this kind of technique is you don't need to store Helm charts. You don't need to learn another language for your declarative automation, right? You don't need all this extra levels of abstraction inherently, if you use it as a label with a kubectl apply, It's just built in. It's kind of like the kiss approach to a certain extent. It does require some encoding when you actually build the image, but to me, it doesn't seem that hard. Okay, let's take a look at a demo. And what I'm going to do for my demo, before we actually get started is here's my repo. Here's a, let me actually go to the actual full repo. So here's the repo, right? And I've got my Jenkins pipeline 'cause I'm using Jenkins for this demo. And in my demo flask, I've got the Docker file. I've got my compose and my Kubernetes YAML. So let's take a look at the Docker file, right? So it's a simple Alpine image. The org statements are the build time arguments that are passed in. Label, so again, I'm using the org.opencontainers.image.blank, for most of them. There's a typo there. Let's see if you can find it, I'll show you it later. My source, build date, build number, commit. Build number and get commit are derived from the Jenkins itself, which is nice. I can just take advantage of existing URLs. I don't have to create anything crazy. And again, I've got my actual Docker build command. Now this is just a label on how to build it. And then here's my simple Python, APK upgrade, remove the package manager, kind of some security stuff, health check getting Python through, okay? Let's take a look at the Jenkins pipeline real quick. So here is my Jenkins pipeline and I have four major stages, four stages, I have built. And here in build, what I do is I actually do the Git clone. And then I do my docker build. From there, I actually tell the Jenkins StackRox plugin. So that's what I'm using for my security scanning. So go ahead and scan, basically, I'm staging it to scan the image. I'm pushing it to Hub, okay? Where I can see the, basically I'm pushing the image up to Hub so such that my StackRox security scanner can go ahead and scan the image. I'm kicking off the scan itself. And then if everything's successful, I'm pushing it to prod. Now what I'm doing is I'm just using the same image with two tags, pre-prod and prod. This is not exactly ideal, in your environment, you probably want to use separate registries and non-prod and a production registry, but for demonstration purposes, I think this is okay. So let's go over to my Jenkins and I've got a deliberate failure. And I'll show you why there's a reason for that. And let's go down. Let's look at my, so I have a StackRox report. Let's look at my report. And it says image required, required image label alert, right? Request that the maintainer, add the required label to the image, so we're missing a label, okay? One of the things we can do is let's flip over, and let's look at Skopeo. Right? I'm going to do this just the easy way. So instead of looking at org.zdocker, opencontainers.image.authors. Okay, see here it says build signature? That was the typo, we didn't actually pass in. So if we go back to our repo, we didn't pass in the the build time argument, we just passed in the word. So let's fix that real quick. That's the Docker file. Let's go ahead and put our dollar sign in their. First day with the fingers you going to love it. And let's go ahead and commit that. Okay? So now that that's committed, we can go back to Jenkins, and we can actually do another build. And there's number 12. And as you can see, I've been playing with this for a little bit today. And while that's running, come on, we can go ahead and look at the Console output. Okay, so there's our image. And again, look at all the build arguments that we're passing into the build statement. So we're passing in the date and the date gets derived on the command line. With the build arguments, there's the base64 encoded of the Compose file. Here's the base64 encoding of the Kubernetes YAML. We do the build. And then let's go down to the bottom layer exists and successful. So here's where we can see no system policy violations profound marking stack regimes security plugin, build step as successful, okay? So we're actually able to do policy enforcement that that image exists, that that label sorry, exists in the image. And again, we can look at the security report and there's no policy violations and no vulnerabilities. So that's pretty good for security, right? We can now enforce and mandate use of certain labels within our images. And let's flip back over to Skopeo, and let's go ahead and look at it. So we're looking at the prod version again. And there's it is in my email address. And that validated that that was valid for that policy. So that's kind of cool. Now, let's take it a step further. What if, let's go ahead and take a look at all of the image, all the labels for a second, let me remove the dash org, make it pretty. Okay? So we have all of our image labels. Again, author's build, commit number, look at the commit number. It was built today build number 12. We saw that right? Delete, build 12. So that's kind of cool dynamic labels. Name, healthz, right? But what we're looking for is we're going to look at the org.zdockerketers label. So let's go look at the label real quick. Okay, well that doesn't really help us because it's encoded but let's base64 dash D, let's decode it. And I need to put the dash r in there 'cause it doesn't like, there we go. So there's my Kubernetes YAML. So why can't we simply kubectl apply dash f? Let's just apply it from standard end. So now we've actually used that label. From the image that we've queried with skopeo, from a remote registry to deploy locally to our Kubernetes cluster. So let's go ahead and look everything's up and running, perfect. So what does that look like, right? So luckily, I'm using traefik for Ingress 'cause I love it. And I've got an object in my Kubernetes YAML called flask.doctor.life. That's my Ingress object for traefik. I can go to flask.docker.life. And I can hit refresh. Obviously, I'm not a very good web designer 'cause the background image in the text. We can go ahead and refresh it a couple times we've got Redis storing a hit counter. We can see that our server name is roundrobing. Okay? That's kind of cool. So let's kind of recap a little bit about my demo environment. So my demo environment, I'm using DigitalOcean, Ubuntu 19.10 Vms. I'm using K3s instead of full Kubernetes either full Rancher, full Open Shift or Docker Enterprise. I think K3s has some really interesting advantages on the development side and it's kind of intended for IoT but it works really well and it deploys super easy. I'm using traefik for Ingress. I love traefik. I may or may not be a traefik ambassador. I'm using Jenkins for CI. And I'm using StackRox for image scanning and policy enforcement. One of the things to think about though, especially in terms of labels is none of this demo stack is required. You can be in any cloud, you can be in CentOs, you can be in any Kubernetes. You can even be in swarm, if you wanted to, or Docker compose. Any Ingress, any CI system, Jenkins, circle, GitLab, it doesn't matter. And pretty much any scanning. One of the things that I think is kind of nice about at least StackRox is that we do a lot more than just image scanning, right? With the policy enforcement things like that. I guess that's kind of a shameless plug. But again, any of this stack is completely replaceable, with any comparative product in that category. So I'd like to, again, point you guys to the andyc.infodc20, that's take you right to the GitHub repo. You can reach out to me at any of the socials @clemenko or andy@stackrox.com. And thank you for attending. I hope you learned something fun about labels. And hopefully you guys can standardize labels in your organization and really kind of take your images and the image provenance to a new level. Thanks for watching. (upbeat music) >> Narrator: Live from Las Vegas It's theCUBE. Covering AWS re:Invent 2019. Brought to you by Amazon Web Services and Intel along with it's ecosystem partners. >> Okay, welcome back everyone theCUBE's live coverage of AWS re:Invent 2019. This is theCUBE's 7th year covering Amazon re:Invent. It's their 8th year of the conference. I want to just shout out to Intel for their sponsorship for these two amazing sets. Without their support we wouldn't be able to bring our mission of great content to you. I'm John Furrier. Stu Miniman. We're here with the chief of AWS, the chief executive officer Andy Jassy. Tech athlete in and of himself three hour Keynotes. Welcome to theCUBE again, great to see you. >> Great to be here, thanks for having me guys. >> Congratulations on a great show a lot of great buzz. >> Andy: Thank you. >> A lot of good stuff. Your Keynote was phenomenal. You get right into it, you giddy up right into it as you say, three hours, thirty announcements. You guys do a lot, but what I liked, the new addition, the last year and this year is the band; house band. They're pretty good. >> Andy: They're good right? >> They hit the queen notes, so that keeps it balanced. So we're going to work on getting a band for theCUBE. >> Awesome. >> So if I have to ask you, what's your walk up song, what would it be? >> There's so many choices, it depends on what kind of mood I'm in. But, uh, maybe Times Like These by the Foo Fighters. >> John: Alright. >> These are unusual times right now. >> Foo Fighters playing at the Amazon Intersect Show. >> Yes they are. >> Good plug Andy. >> Headlining. >> Very clever >> Always getting a good plug in there. >> My very favorite band. Well congratulations on the Intersect you got a lot going on. Intersect is a music festival, I'll get to that in a second But, I think the big news for me is two things, obviously we had a one-on-one exclusive interview and you laid out, essentially what looks like was going to be your Keynote, and it was. Transformation- >> Andy: Thank you for the practice. (Laughter) >> John: I'm glad to practice, use me anytime. >> Yeah. >> And I like to appreciate the comments on Jedi on the record, that was great. But I think the transformation story's a very real one, but the NFL news you guys just announced, to me, was so much fun and relevant. You had the Commissioner of NFL on stage with you talking about a strategic partnership. That is as top down, aggressive goal as you could get to have Rodger Goodell fly to a tech conference to sit with you and then bring his team talk about the deal. >> Well, ya know, we've been partners with the NFL for a while with the Next Gen Stats that they use on all their telecasts and one of the things I really like about Roger is that he's very curious and very interested in technology and the first couple times I spoke with him he asked me so many questions about ways the NFL might be able to use the Cloud and digital transformation to transform their various experiences and he's always said if you have a creative idea or something you think that could change the world for us, just call me he said or text me or email me and I'll call you back within 24 hours. And so, we've spent the better part of the last year talking about a lot of really interesting, strategic ways that they can evolve their experience both for fans, as well as their players and the Player Health and Safety Initiative, it's so important in sports and particularly important with the NFL given the nature of the sport and they've always had a focus on it, but what you can do with computer vision and machine learning algorithms and then building a digital athlete which is really like a digital twin of each athlete so you understand, what does it look like when they're healthy and compare that when it looks like they may not be healthy and be able to simulate all kinds of different combinations of player hits and angles and different plays so that you could try to predict injuries and predict the right equipment you need before there's a problem can be really transformational so we're super excited about it. >> Did you guys come up with the idea or was it a collaboration between them? >> It was really a collaboration. I mean they, look, they are very focused on players safety and health and it's a big deal for their- you know, they have two main constituents the players and fans and they care deeply about the players and it's a-it's a hard problem in a sport like Football, I mean, you watch it. >> Yeah, and I got to say it does point out the use cases of what you guys are promoting heavily at the show here of the SageMaker Studio, which was a big part of your Keynote, where they have all this data. >> Andy: Right. >> And they're data hoarders, they hoard data but the manual process of going through the data was a killer problem. This is consistent with a lot of the enterprises that are out there, they have more data than they even know. So this seems to be a big part of the strategy. How do you get the customers to actually wake up to the fact that they got all this data and how do you tie that together? >> I think in almost every company they know they have a lot of data. And there are always pockets of people who want to do something with it. But, when you're going to make these really big leaps forward; these transformations, the things like Volkswagen is doing where they're reinventing their factories and their manufacturing process or the NFL where they're going to radically transform how they do players uh, health and safety. It starts top down and if the senior leader isn't convicted about wanting to take that leap forward and trying something different and organizing the data differently and organizing the team differently and using machine learning and getting help from us and building algorithms and building some muscle inside the company it just doesn't happen because it's not in the normal machinery of what most companies do. And so it always, almost always, starts top down. Sometimes it can be the Commissioner or CEO sometimes it can be the CIO but it has to be senior level conviction or it doesn't get off the ground. >> And the business model impact has to be real. For NFL, they know concussions, hurting their youth pipe-lining, this is a huge issue for them. This is their business model. >> They lose even more players to lower extremity injuries. And so just the notion of trying to be able to predict injuries and, you know, the impact it can have on rules and the impact it can have on the equipment they use, it's a huge game changer when they look at the next 10 to 20 years. >> Alright, love geeking out on the NFL but Andy, you know- >> No more NFL talk? >> Off camera how about we talk? >> Nobody talks about the Giants being 2 and 10. >> Stu: We're both Patriots fans here. >> People bring up the undefeated season. >> So Andy- >> Everybody's a Patriot's fan now. (Laughter) >> It's fascinating to watch uh, you and your three hour uh, Keynote, uh Werner in his you know, architectural discussion, really showed how AWS is really extending its reach, you know, it's not just a place. For a few years people have been talking about you know, Cloud is an operational model its not a destination or a location but, I felt it really was laid out is you talked about Breadth and Depth and Werner really talked about you know, Architectural differentiation. People talk about Cloud, but there are very-there are a lot of differences between the vision for where things are going. Help us understand why, I mean, Amazon's vision is still a bit different from what other people talk about where this whole Cloud expansion, journey, put ever what tag or label you want on it but you know, the control plane and the technology that you're building and where you see that going. >> Well I think that, we've talked about this a couple times we have two macro types of customers. We have those that really want to get at the low level building blocks and stitch them together creatively however they see fit to create whatever's in their-in their heads. And then we have the second segment of customers that say look, I'm willing to give up some of that flexibility in exchange for getting 80% of the way there much faster. In an abstraction that's different from those low level building blocks. And both segments of builders we want to serve and serve well and so we've built very significant offerings in both areas. I think when you look at microservices um, you know, some of it has to do with the fact that we have this very strongly held belief born out of several years of Amazon where you know, the first 7 or 8 years of Amazon's consumer business we basically jumbled together all of the parts of our technology in moving really quickly and when we wanted to move quickly where you had to impact multiple internal development teams it was so long because it was this big ball, this big monolithic piece. And we got religion about that in trying to move faster in the consumer business and having to tease those pieces apart. And it really was a lot of impetus behind conceiving AWS where it was these low level, very flexible building blocks that6 don't try and make all the decisions for customers they get to make them themselves. And some of the microservices that you saw Werner talking about just, you know, for instance, what we-what we did with Nitro or even what we did with Firecracker those are very much about us relentlessly working to continue to uh, tease apart the different components. And even things that look like low level building blocks over time, you build more and more features and all of the sudden you realize they have a lot of things that are combined together that you wished weren't that slow you down and so, Nitro was a completely re imagining of our Hypervisor and Virtualization layer to allow us, both to let customers have better performance but also to let us move faster and have a better security story for our customers. >> I got to ask you the question around transformation because I think that all points, all the data points, you got all the references, Goldman Sachs on stage at the Keynote, Cerner, I mean healthcare just is an amazing example because I mean, that's demonstrating real value there there's no excuse. I talked to someone who wouldn't be named last night, in and around the area said, the CIA has a cost bar like this a cost-a budget like this but the demand for mission based apps is going up exponentially, so there's need for the Cloud. And so, you see more and more of that. What is your top down, aggressive goals to fill that solution base because you're also a very transformational thinker; what is your-what is your aggressive top down goals for your organization because you're serving a market with trillions of dollars of spend that's shifting, that's on the table. >> Yeah. >> A lot of competition now sees it too, they're going to go after it. But at the end of the day you have customers that have a demand for things, apps. >> Andy: Yeah. >> And not a lot of budget increase at the same time. This is a huge dynamic. >> Yeah. >> John: What's your goals? >> You know I think that at a high level our top down aggressive goals are that we want every single customer who uses our platform to have an outstanding customer experience. And we want that outstanding customer experience in part is that their operational performance and their security are outstanding, but also that it allows them to build, uh, build projects and initiatives that change their customer experience and allow them to be a sustainable successful business over a long period of time. And then, we also really want to be the technology infrastructure platform under all the applications that people build. And we're realistic, we know that you know, the market segments we address with infrastructure, software, hardware, and data center services globally are trillions of dollars in the long term and it won't only be us, but we have that goal of wanting to serve every application and that requires not just the security operational premise but also a lot of functionality and a lot of capability. We have by far the most amount of capability out there and yet I would tell you, we have 3 to 5 years of items on our roadmap that customers want us to add. And that's just what we know today. >> And Andy, underneath the covers you've been going through some transformation. When we talked a couple of years ago, about how serverless is impacting things I've heard that that's actually, in many ways, glue behind the two pizza teams to work between organizations. Talk about how the internal transformations are happening. How that impacts your discussions with customers that are going through that transformation. >> Well, I mean, there's a lot of- a lot of the technology we build comes from things that we're doing ourselves you know? And that we're learning ourselves. It's kind of how we started thinking about microservices, serverless too, we saw the need, you know, we would have we would build all these functions that when some kind of object came into an object store we would spin up, compute, all those tasks would take like, 3 or 4 hundred milliseconds then we'd spin it back down and yet, we'd have to keep a cluster up in multiple availability zones because we needed that fault tolerance and it was- we just said this is wasteful and, that's part of how we came up with Lambda and you know, when we were thinking about Lambda people understandably said, well if we build Lambda and we build this serverless adventure in computing a lot of people were keeping clusters of instances aren't going to use them anymore it's going to lead to less absolute revenue for us. But we, we have learned this lesson over the last 20 years at Amazon which is, if it's something that's good for customers you're much better off cannibalizing yourself and doing the right thing for customers and being part of shaping something. And I think if you look at the history of technology you always build things and people say well, that's going to cannibalize this and people are going to spend less money, what really ends up happening is they spend less money per unit of compute but it allows them to do so much more that they ultimately, long term, end up being more significant customers. >> I mean, you are like beating the drum all the time. Customers, what they say, we encompass the roadmap, I got that you guys have that playbook down, that's been really successful for you. >> Andy: Yeah. >> Two years ago you told me machine learning was really important to you because your customers told you. What's the next traunch of importance for customers? What's on top of mind now, as you, look at- >> Andy: Yeah. >> This re:Invent kind of coming to a close, Replay's tonight, you had conversations, you're a tech athlete, you're running around, doing speeches, talking to customers. What's that next hill from if it's machine learning today- >> There's so much I mean, (weird background noise) >> It's not a soup question (Laughter) And I think we're still in the very early days of machine learning it's not like most companies have mastered it yet even though they're using it much more then they did in the past. But, you know, I think machine learning for sure I think the Edge for sure, I think that um, we're optimistic about Quantum Computing even though I think it'll be a few years before it's really broadly useful. We're very um, enthusiastic about robotics. I think the amount of functions that are going to be done by these- >> Yeah. >> robotic applications are much more expansive than people realize. It doesn't mean humans won't have jobs, they're just going to work on things that are more value added. We're believers in augmented virtual reality, we're big believers in what's going to happen with Voice. And I'm also uh, I think sometimes people get bored you know, I think you're even bored with machine learning already >> Not yet. >> People get bored with the things you've heard about but, I think just what we've done with the Chips you know, in terms of giving people 40% better price performance in the latest generation of X86 processors. It's pretty unbelievable in the difference in what people are going to be able to do. Or just look at big data I mean, big data, we haven't gotten through big data where people have totally solved it. The amount of data that companies want to store, process, analyze, is exponentially larger than it was a few years ago and it will, I think, exponentially increase again in the next few years. You need different tools and services. >> Well I think we're not bored with machine learning we're excited to get started because we have all this data from the video and you guys got SageMaker. >> Andy: Yeah. >> We call it the stairway to machine learning heaven. >> Andy: Yeah. >> You start with the data, move up, knock- >> You guys are very sophisticated with what you do with technology and machine learning and there's so much I mean, we're just kind of, again, in such early innings. And I think that, it was so- before SageMaker, it was so hard for everyday developers and data scientists to build models but the combination of SageMaker and what's happened with thousands of companies standardizing on it the last two years, plus now SageMaker studio, giant leap forward. >> Well, we hope to use the data to transform our experience with our audience. And we're on Amazon Cloud so we really appreciate that. >> Andy: Yeah. >> And appreciate your support- >> Andy: Yeah, of course. >> John: With Amazon and get that machine learning going a little faster for us, that would be better. >> If you have requests I'm interested, yeah. >> So Andy, you talked about that you've got the customers that are builders and the customers that need simplification. Traditionally when you get into the, you know, the heart of the majority of adoption of something you really need to simplify that environment. But when I think about the successful enterprise of the future, they need to be builders. how'l I normally would've said enterprise want to pay for solutions because they don't have the skill set but, if they're going to succeed in this new economy they need to go through that transformation >> Andy: Yeah. >> That you talk to, so, I mean, are we in just a total new era when we look back will this be different than some of these previous waves? >> It's a really good question Stu, and I don't think there's a simple answer to it. I think that a lot of enterprises in some ways, I think wish that they could just skip the low level building blocks and only operate at that higher level abstraction. That's why people were so excited by things like, SageMaker, or CodeGuru, or Kendra, or Contact Lens, these are all services that allow them to just send us data and then run it on our models and get back the answers. But I think one of the big trends that we see with enterprises is that they are taking more and more of their development in house and they are wanting to operate more and more like startups. I think that they admire what companies like AirBnB and Pintrest and Slack and Robinhood and a whole bunch of those companies, Stripe, have done and so when, you know, I think you go through these phases and eras where there are waves of success at different companies and then others want to follow that success and replicate it. And so, we see more and more enterprises saying we need to take back a lot of that development in house. And as they do that, and as they add more developers those developers in most cases like to deal with the building blocks. And they have a lot of ideas on how they can creatively stich them together. >> Yeah, on that point, I want to just quickly ask you on Amazon versus other Clouds because you made a comment to me in our interview about how hard it is to provide a service to other people. And it's hard to have a service that you're using yourself and turn that around and the most quoted line of my story was, the compression algorithm- there's no compression algorithm for experience. Which to me, is the diseconomies of scale for taking shortcuts. >> Andy: Yeah. And so I think this is a really interesting point, just add some color commentary because I think this is a fundamental difference between AWS and others because you guys have a trajectory over the years of serving, at scale, customers wherever they are, whatever they want to do, now you got microservices. >> Yeah. >> John: It's even more complex. That's hard. >> Yeah. >> John: Talk about that. >> I think there are a few elements to that notion of there's no compression algorithm for experience and I think the first thing to know about AWS which is different is, we just come from a different heritage and a different background. We ran a business for a long time that was our sole business that was a consumer retail business that was very low margin. And so, we had to operate at very large scale given how many people were using us but also, we had to run infrastructure services deep in the stack, compute storage and database, and reliable scalable data centers at very low cost and margins. And so, when you look at our business it actually, today, I mean its, its a higher margin business in our retail business, its a lower margin business in software companies but at real scale, it's a high volume, relatively low margin business. And the way that you have to operate to be successful with those businesses and the things you have to think about and that DNA come from the type of operators we have to be in our consumer retail business. And there's nobody else in our space that does that. So, you know, the way that we think about costs, the way we think about innovation in the data center, um, and I also think the way that we operate services and how long we've been operating services as a company its a very different mindset than operating package software. Then you look at when uh, you think about some of the uh, issues in very large scale Cloud, you can't learn some of those lessons until you get to different elbows of the curve and scale. And so what I was telling you is, its really different to run your own platform for your own users where you get to tell them exactly how its going to be done. But that's not the way the real world works. I mean, we have millions of external customers who use us from every imaginable country and location whenever they want, without any warning, for lots of different use cases, and they have lots of design patterns and we don't get to tell them what to do. And so operating a Cloud like that, at a scale that's several times larger than the next few providers combined is a very different endeavor and a very different operating rigor. >> Well you got to keep raising the bar you guys do a great job, really impressed again. Another tsunami of announcements. In fact, you had to spill the beans earlier with Quantum the day before the event. Tight schedule. I got to ask you about the musical festival because, I think this is a very cool innovation. It's the inaugural Intersect conference. >> Yes. >> John: Which is not part of Replay, >> Yes. >> John: Which is the concert tonight. Its a whole new thing, big music act, you're a big music buff, your daughter's an artist. Why did you do this? What's the purpose? What's your goal? >> Yeah, it's an experiment. I think that what's happened is that re:Invent has gotten so big, we have 65 thousand people here, that to do the party, which we do every year, its like a 35-40 thousand person concert now. Which means you have to have a location that has multiple stages and, you know, we thought about it last year and when we were watching it and we said, we're kind of throwing, like, a 4 hour music festival right now. There's multiple stages, and its quite expensive to set up that set for a party and we said well, maybe we don't have to spend all that money for 4 hours and then rip it apart because actually the rent to keep those locations for another two days is much smaller than the cost of actually building multiple stages and so we thought we would try it this year. We're very passionate about music as a business and I think we-I think our customers feel like we've thrown a pretty good music party the last few years and we thought we would try it at a larger scale as an experiment. And if you look at the economics- >> At the headliners real quick. >> The Foo Fighters are headlining on Saturday night, Anderson Paak and the Free Nationals, Brandi Carlile, Shawn Mullins, um, Willy Porter, its a good set. Friday night its Beck and Kacey Musgraves so it's a really great set of um, about thirty artists and we're hopeful that if we can build a great experience that people will want to attend that we can do it at scale and it might be something that both pays for itself and maybe, helps pay for re:Invent too overtime and you know, I think that we're also thinking about it as not just a music concert and festival the reason we named it Intersect is that we want an intersection of music genres and people and ethnicities and age groups and art and technology all there together and this will be the first year we try it, its an experiment and we're really excited about it. >> Well I'm gone, congratulations on all your success and I want to thank you we've been 7 years here at re:Invent we've been documenting the history. You got two sets now, one set upstairs. So appreciate you. >> theCUBE is part of re:Invent, you know, you guys really are apart of the event and we really appreciate your coming here and I know people appreciate the content you create as well. >> And we just launched CUBE365 on Amazon Marketplace built on AWS so thanks for letting us- >> Very cool >> John: Build on the platform. appreciate it. >> Thanks for having me guys, I appreciate it. >> Andy Jassy the CEO of AWS here inside theCUBE, it's our 7th year covering and documenting the thunderous innovation that Amazon's doing they're really doing amazing work building out the new technologies here in the Cloud computing world. I'm John Furrier, Stu Miniman, be right back with more after this short break. (Outro music)

>> Hi, my name is Andy Clemenko. I'm a Senior Solutions Engineer at StackRox. Thanks for joining us today for my talk on labels, labels, labels. Obviously, you can reach me at all the socials. Before we get started, I like to point you to my GitHub repo, you can go to andyc.info/dc20, and it'll take you to my GitHub page where I've got all of this documentation, I've got the Keynote file there. YAMLs, I've got Dockerfiles, Compose files, all that good stuff. If you want to follow along, great, if not go back and review later, kind of fun. So let me tell you a little bit about myself. I am a former DOD contractor. This is my seventh DockerCon. I've spoken, I had the pleasure to speak at a few of them, one even in Europe. I was even a Docker employee for quite a number of years, providing solutions to the federal government and customers around containers and all things Docker. So I've been doing this a little while. One of the things that I always found interesting was the lack of understanding around labels. So why labels, right? Well, as a former DOD contractor, I had built out a large registry. And the question I constantly got was, where did this image come from? How did you get it? What's in it? Where did it come from? How did it get here? And one of the things we did to kind of alleviate some of those questions was we established a baseline set of labels. Labels really are designed to provide as much metadata around the image as possible. I ask everyone in attendance, when was the last time you pulled an image and had 100% confidence, you knew what was inside it, where it was built, how it was built, when it was built, you probably didn't, right? The last thing we obviously want is a container fire, like our image on the screen. And one kind of interesting way we can kind of prevent that is through the use of labels. We can use labels to address security, address some of the simplicity on how to run these images. So think of it, kind of like self documenting, Think of it also as an audit trail, image provenance, things like that. These are some interesting concepts that we can definitely mandate as we move forward. What is a label, right? Specifically what is the Schema? It's just a key-value. All right? It's any key and pretty much any value. What if we could dump in all kinds of information? What if we could encode things and store it in there? And I've got a fun little demo to show you about that. Let's start off with some of the simple keys, right? Author, date, description, version. Some of the basic information around the image. That would be pretty useful, right? What about specific labels for CI? What about a, where's the version control? Where's the source, right? Whether it's Git, whether it's GitLab, whether it's GitHub, whether it's Gitosis, right? Even SPN, who cares? Where are the source files that built, where's the Docker file that built this image? What's the commit number? That might be interesting in terms of tracking the resulting image to a person or to a commit, hopefully then to a person. How is it built? What if you wanted to play with it and do a git clone of the repo and then build the Docker file on your own? Having a label specifically dedicated on how to build this image might be interesting for development work. Where it was built, and obviously what build number, right? These kind of all, not only talk about continuous integration, CI but also start to talk about security. Specifically what server built it. The version control number, the version number, the commit number, again, how it was built. What's the specific build number? What was that job number in, say, Jenkins or GitLab? What if we could take it a step further? What if we could actually apply policy enforcement in the build pipeline, looking specifically for some of these specific labels? I've got a good example of, in my demo of a policy enforcement. So let's look at some sample labels. Now originally, this idea came out of label-schema.org. And then it was a modified to opencontainers, org.opencontainers.image. There is a link in my GitHub page that links to the full reference. But these are some of the labels that I like to use, just as kind of like a standardization. So obviously, Author's, an email address, so now the image is attributable to a person, that's always kind of good for security and reliability. Where's the source? Where's the version control that has the source, the Docker file and all the assets? How it was built, build number, build server the commit, we talked about, when it was created, a simple description. A fun one I like adding in is the healthZendpoint. Now obviously, the health check directive should be in the Docker file. But if you've got other systems that want to ping your applications, why not declare it and make it queryable? Image version, obviously, that's simple declarative And then a title. And then I've got the two fun ones. Remember, I talked about what if we could encode some fun things? Hypothetically, what if we could encode the Compose file of how to build the stack in the first image itself? And conversely the Kubernetes? Well, actually, you can and I have a demo to show you how to kind of take advantage of that. So how do we create labels? And really creating labels as a function of build time okay? You can't really add labels to an image after the fact. The way you do add labels is either through the Docker file, which I'm a big fan of, because it's declarative. It's in version control. It's kind of irrefutable, especially if you're tracking that commit number in a label. You can extend it from being a static kind of declaration to more a dynamic with build arguments. And I can show you, I'll show you in a little while how you can use a build argument at build time to pass in that variable. And then obviously, if you did it by hand, you could do a docker build--label key equals value. I'm not a big fan of the third one, I love the first one and obviously the second one. Being dynamic we can take advantage of some of the variables coming out of version control. Or I should say, some of the variables coming out of our CI system. And that way, it self documents effectively at build time, which is kind of cool. How do we view labels? Well, there's two major ways to view labels. The first one is obviously a docker pull and docker inspect. You can pull the image locally, you can inspect it, you can obviously, it's going to output as JSON. So you going to use something like JQ to crack it open and look at the individual labels. Another one which I found recently was Skopeo from Red Hat. This allows you to actually query the registry server. So you don't even have to pull the image initially. This can be really useful if you're on a really small development workstation, and you're trying to talk to a Kubernetes cluster and wanting to deploy apps kind of in a very simple manner. Okay? And this was that use case, right? Using Kubernetes, the Kubernetes demo. One of the interesting things about this is that you can base64 encode almost anything, push it in as text into a label and then base64 decode it, and then use it. So in this case, in my demo, I'll show you how we can actually use a kubectl apply piped from the base64 decode from the label itself from skopeo talking to the registry. And what's interesting about this kind of technique is you don't need to store Helm charts. You don't need to learn another language for your declarative automation, right? You don't need all this extra levels of abstraction inherently, if you use it as a label with a kubectl apply, It's just built in. It's kind of like the kiss approach to a certain extent. It does require some encoding when you actually build the image, but to me, it doesn't seem that hard. Okay, let's take a look at a demo. And what I'm going to do for my demo, before we actually get started is here's my repo. Here's a, let me actually go to the actual full repo. So here's the repo, right? And I've got my Jenkins pipeline 'cause I'm using Jenkins for this demo. And in my demo flask, I've got the Docker file. I've got my compose and my Kubernetes YAML. So let's take a look at the Docker file, right? So it's a simple Alpine image. The org statements are the build time arguments that are passed in. Label, so again, I'm using the org.opencontainers.image.blank, for most of them. There's a typo there. Let's see if you can find it, I'll show you it later. My source, build date, build number, commit. Build number and get commit are derived from the Jenkins itself, which is nice. I can just take advantage of existing URLs. I don't have to create anything crazy. And again, I've got my actual Docker build command. Now this is just a label on how to build it. And then here's my simple Python, APK upgrade, remove the package manager, kind of some security stuff, health check getting Python through, okay? Let's take a look at the Jenkins pipeline real quick. So here is my Jenkins pipeline and I have four major stages, four stages, I have built. And here in build, what I do is I actually do the Git clone. And then I do my docker build. From there, I actually tell the Jenkins StackRox plugin. So that's what I'm using for my security scanning. So go ahead and scan, basically, I'm staging it to scan the image. I'm pushing it to Hub, okay? Where I can see the, basically I'm pushing the image up to Hub so such that my StackRox security scanner can go ahead and scan the image. I'm kicking off the scan itself. And then if everything's successful, I'm pushing it to prod. Now what I'm doing is I'm just using the same image with two tags, pre-prod and prod. This is not exactly ideal, in your environment, you probably want to use separate registries and non-prod and a production registry, but for demonstration purposes, I think this is okay. So let's go over to my Jenkins and I've got a deliberate failure. And I'll show you why there's a reason for that. And let's go down. Let's look at my, so I have a StackRox report. Let's look at my report. And it says image required, required image label alert, right? Request that the maintainer, add the required label to the image, so we're missing a label, okay? One of the things we can do is let's flip over, and let's look at Skopeo. Right? I'm going to do this just the easy way. So instead of looking at org.zdocker, opencontainers.image.authors. Okay, see here it says build signature? That was the typo, we didn't actually pass in. So if we go back to our repo, we didn't pass in the the build time argument, we just passed in the word. So let's fix that real quick. That's the Docker file. Let's go ahead and put our dollar sign in their. First day with the fingers you going to love it. And let's go ahead and commit that. Okay? So now that that's committed, we can go back to Jenkins, and we can actually do another build. And there's number 12. And as you can see, I've been playing with this for a little bit today. And while that's running, come on, we can go ahead and look at the Console output. Okay, so there's our image. And again, look at all the build arguments that we're passing into the build statement. So we're passing in the date and the date gets derived on the command line. With the build arguments, there's the base64 encoded of the Compose file. Here's the base64 encoding of the Kubernetes YAML. We do the build. And then let's go down to the bottom layer exists and successful. So here's where we can see no system policy violations profound marking stack regimes security plugin, build step as successful, okay? So we're actually able to do policy enforcement that that image exists, that that label sorry, exists in the image. And again, we can look at the security report and there's no policy violations and no vulnerabilities. So that's pretty good for security, right? We can now enforce and mandate use of certain labels within our images. And let's flip back over to Skopeo, and let's go ahead and look at it. So we're looking at the prod version again. And there's it is in my email address. And that validated that that was valid for that policy. So that's kind of cool. Now, let's take it a step further. What if, let's go ahead and take a look at all of the image, all the labels for a second, let me remove the dash org, make it pretty. Okay? So we have all of our image labels. Again, author's build, commit number, look at the commit number. It was built today build number 12. We saw that right? Delete, build 12. So that's kind of cool dynamic labels. Name, healthz, right? But what we're looking for is we're going to look at the org.zdockerketers label. So let's go look at the label real quick. Okay, well that doesn't really help us because it's encoded but let's base64 dash D, let's decode it. And I need to put the dash r in there 'cause it doesn't like, there we go. So there's my Kubernetes YAML. So why can't we simply kubectl apply dash f? Let's just apply it from standard end. So now we've actually used that label. From the image that we've queried with skopeo, from a remote registry to deploy locally to our Kubernetes cluster. So let's go ahead and look everything's up and running, perfect. So what does that look like, right? So luckily, I'm using traefik for Ingress 'cause I love it. And I've got an object in my Kubernetes YAML called flask.doctor.life. That's my Ingress object for traefik. I can go to flask.docker.life. And I can hit refresh. Obviously, I'm not a very good web designer 'cause the background image in the text. We can go ahead and refresh it a couple times we've got Redis storing a hit counter. We can see that our server name is roundrobing. Okay? That's kind of cool. So let's kind of recap a little bit about my demo environment. So my demo environment, I'm using DigitalOcean, Ubuntu 19.10 Vms. I'm using K3s instead of full Kubernetes either full Rancher, full Open Shift or Docker Enterprise. I think K3s has some really interesting advantages on the development side and it's kind of intended for IoT but it works really well and it deploys super easy. I'm using traefik for Ingress. I love traefik. I may or may not be a traefik ambassador. I'm using Jenkins for CI. And I'm using StackRox for image scanning and policy enforcement. One of the things to think about though, especially in terms of labels is none of this demo stack is required. You can be in any cloud, you can be in CentOs, you can be in any Kubernetes. You can even be in swarm, if you wanted to, or Docker compose. Any Ingress, any CI system, Jenkins, circle, GitLab, it doesn't matter. And pretty much any scanning. One of the things that I think is kind of nice about at least StackRox is that we do a lot more than just image scanning, right? With the policy enforcement things like that. I guess that's kind of a shameless plug. But again, any of this stack is completely replaceable, with any comparative product in that category. So I'd like to, again, point you guys to the andyc.infodc20, that's take you right to the GitHub repo. You can reach out to me at any of the socials @clemenko or andy@stackrox.com. And thank you for attending. I hope you learned something fun about labels. And hopefully you guys can standardize labels in your organization and really kind of take your images and the image provenance to a new level. Thanks for watching. (upbeat music)

>> (upbeat music) >> production: From around the globe, it's the Cube covering Google cloud Next on-Air 20. (Upbeat music) >> Welcome back. I'm Stu Miniman and this is the CUBE coverage of Google cloud Next on Air 20. Of course, the nine week distributed all online program that Google cloud is doing and going to be talking about, of course, multi-cloud, Google of course had a big piece in multi-cloud. When they took what was originally Borg, They built Kubernetes. They made that open source and gave that to the CNCF and one of Google's partners and a leader in that space is of course, Red Hat. Happy to welcome to the program Sathish Balakrishnan, he is the Vice President of hosted platforms at Red Hat. Sathish, thanks so much for joining us. >> Thank you. It's great to be here with you on Google Cloud Native insights. >> Alright. So I, I tied it up, of course, you know, we talk about, you know, the hybrid multicloud and open, you know, two companies. I probably think of the most and that I've probably said the most about the open cloud are Google and Red Hat. So maybe if we could start just, uh, you hosted platforms, help us understand what that is. And, uh, what was the relationship between Red Hat and the Open Shift team and Google cloud? >> Absolutely. Great question. And I think Google has been an amazing partner for us. I think we have a lot of things going on with them upstream in the community. I think, you know, we've been with Google and the Kubernetes project since the beginning and you know, like the second biggest contributor to Kubernetes. So we have great relationships upstream. We also made Red Hat Enterprise Linux as well as Open Shift available on Google. So we have customers using both our offerings as well as our other offerings on Google cloud as well. And more recently with the hosted our offerings. You know, we actually manage Open Shift on multiple clouds. We relaunched our Open Shift dedicated offering on Google cloud back at Red Hat Summit. There's a lot of interest for the offering. We had back offered the offering in 2017 with Open Shift Three and we just relaunched this with Open Shift Four and we received considerable interest for the Google cloud Open Shift dedicated offering. >> Yeah, Sathish maybe it makes sense if we talk about kind of the maturation of open source solutions, managed services has seen really tremendous growth, something we've seen, especially if we were talking about in the cloud space. Maybe if you could just walk us through a little bit out that, you know, what are you hearing from customers? How does Red Hat think about managed solutions? >> Absolutely. Stu, I think it was a good question, right? I think, uh, as we say, the customers are looking at, you know, multiple infrastructure footprints, Be iteither the public cloud or on-prem. They'll start looking at, you know, if I go to the cloud, you know, there's this concept of, I want something to be managed. So what Open Shift is doing is in Open Shift, as you know it's Red Hat's hybrid cloud platform and with Open Shift, all the things that we strive to do is to enable the vision of the Open Hybrid Cloud. Uh, so, but Open Hybrid Cloud, it's all about choice, So we want to make sure the customers have both the managed as well as the self managed option. Uh, so if you really look at it, you know, Red Hat has multiple offerings from a managed standpoint. One as you know, we have Open Shift dedicated, which runs from AWS and Google. And, you know, we just have, as I mentioned earlier. We relaunched our Google service at Red Hat Summit back in May. So that's actually getting a lot of traction. We also have joint offerings with Azure that we announced a couple of years back and, there's a lot of interest for that offering as well as the new offering that we announced post-summit, the Amazon-Red Hat Open Shift, which basically is another native offering that we have on Amazon. If you really look at, having, having spoken about these offerings, if you really look at Red Hat's evolution as a managed service provider in the public cloud, we've been doing this since 2011. You know, that's kind of surprising for a lot of people, but you know, we've been doing Open Shift online, which is kind of a multi-tenant parcel multi-talent CaaS solution 2011. And we are one of the earliest providers of managed kubernetes, you know, along with Google Kubernetes engine GKE, we are our Open Shift dedicated offering back in 2015. So we've been doing Kubernetes managed since, Open Shift 3.1. So that's actually, you know, we have a lot of experience with management of Kubernetes and, you know, the devolution of Open Shift we've now made it available and pretty much all the clouds. So that customers have that exact same experience that they can get any one cloud across all clouds, as well as on-prem. Managed service customers now have a choice of a self managed Open Shift or completely managed Open Shift. >> Yeah. You mentioned the choice and one of the challenges we have right now is there's really the paradox of choice. If you look in the Kubernetes space, you know, there are dozens of offerings. Of course, every cloud provider has their offerings. You know, Google's got GKE, they have Anthos, uh, they, they have management tools around there. You, you talked a bit about the, you know, the experience and all the customers you have, the, you know, there's one of the fighters talks about, there's no compression algorithm for experience. So, you know, what is Red Hat Open Shift? What really differentiates in the market place from, you know, so many of the other offerings, either from the public high providers, some of the new startups, that we should know. >> Yeah. I think that's an interesting question, right? I think all Google traders start with it's complete open source and, you know, we are a complete open source company. So there is no proprietary software that we put into Open Shift. Open Shift, basically, even though it has, you know, OC command, it basically has CPR. So you can actually use native Google networks as you choose on any Google network offering that you have be it GKE, EKS or any of the other things that are out there. So that's why I think there are such things with google networks and providers and Red Hat does not believe in open provider. It completely believes in open source. We have everything that we is open source. From an it standpoint, the value prop for Red Hat has always been the value of the subscription, but we actually make sure that, you know, Google network is taken from an upstream product. It's basically completed productized and available for the enterprise to consume. But that right, when we have the managed offering, we provide a lot more benefits to it, right? The benefits are right. We actually have customer zero for Open Shift. So what does that mean? Right. We will not release Open Shift if we can't run open Shift dedicated or any of their (indistinct) out Open Shift for them is under that Open Shift. Really really well. So you won't get a software version out there. The second thing is we actually run a lot of workloads, but then Red Hat that are dependent on our managed or open shift off. So for example, our billing systems, all of those internal things that are important for Red Hat run on managed Open Shift, for example, managed Open Shift. So those are the important services for Red Hat and we have to make sure that those things are running really, really well. So we provide that second layer of enterprise today. Then having put Open Shift online, out that in public. We have 4 million applications and a million developers that use them. So that means, I've been putting it out there in the internet and, you know, there's security hosts that are constantly being booked that are being plugged in. So that's another benefit that you get from having a product that's a managed service, but it also is something that enterprises can now use it. From an Open Shift standpoint, the real difference is we add a lot of other things on top of google network without compromising the google network safety. That basically helps customers not have to worry about how they're going to get the CIC pipeline or how they have to do a bunch of in Cobra Net as an outside as the inside. Then you have technologies like Store Street Metrics kind of really help customers not to obstruct the way the containerization led from that. So those are some of the benefits that we provide with Open Shift. >> Yeah. So, so, so Sathish, as it's said, there's lots of options when it comes to Kubernetes, even from a Red Hat offering, you've got different competing models there. If I look inside your portfolio, if it's something that I want to put on my infrastructure, if I haven't read the Open Shift container platform, is that significantly different from the managed platform. Maybe give us a little compare contrast, you know. What do I have to do as a customer? Is the code base the same? Can I do, you know, hybrid environments between them and you know, what does that mean? >> It's a smart questions. It's a really, really good question that you asked. So we actually, you know, as I've said, we add a lot of things on top of google network to make it really fast, but do you want to use the cast, you can use the desktop. So one of the things we've found, but you know, what we've done with our managed offering is we actually take Open Shift container platform and we manage that. So we make sure that you get like a completely managed source, you know. They'll be managed, the patching of the worker nodes and other things, which is, again, another difference that we have with the native Cobra Net of services. We actually give plush that admin functionality to customers that basically allows them to choose all the options that they need from an Open Shift container platform. So from a core base, it's exactly the same thing. The only thing is, it's a little bit opinionated. It to start off when we deploy the cluster for the customer and then the customer, if they want, they can choose how to customize it. So what this really does is it takes away any of the challenges the customer may have with like how to install and provision a cluster, which we've already simplified a lot of the open shift, but with the managed the Open Shift, it's actually just a click of it. >> Great. Sathish Well, I've got the trillion dollar question for you. One of the things we've been looking at for years of course, is, you know, what do I keep in my data center? What do I move to the cloud? How do I modernize it? We understand it's a complex and nuanced solution, but you talk to a lot of customers. So I, you know, here in 2020, what's the trends? What are some of the pieces that you're seeing some change and movement that, you know, might not have been the case a year ago? >> I think, you know, this is an interesting question and it's an evolving question, right? And it's something that if you ask like 10 people you'll get real answers, but I'm trying to generalize what I've seen just from all the customer conversations I've been involved. I think one thing is very clear, right? I think that the world is right as much as anybody may want to say that I'm going to go to a single cloud or I'm going to just be on prem. It is inevitable that you're going to basically end up with multiple infrastructure footprint. It's either multicloud or it's on Prem versus a single cloud or on prem versus multiple cloud. So the main thing is that, we've been noticing as, what customers are saying in a whole. How do I make sure that my developers are not confused by all these difference than one? How do I give them a consistent way to develop and build their applications? Not really worry about, what is the infrastructure. What is the footprint that they're actually servicing? So that's kind of really, really important. And in terms of, you know, things that, you know, we've seen customers, you know, I think you always start with compliance requirements and data regulations. Back there you got to figure it out. What compliance do I need? And as the infrastructure or the platform that I'm going to go to meet the compliance requirements that I have, and what are the data regulations? You know, what is the data I'm going to be setting? Is it going to meet the data submitted rules that my country or my geo has? I got to make sure I worry about that. And then I got to figure out if I'm going to basically more to the cloud from the data center or from one cloud to another cloud. I might just be doing a lift or shift. Am I doing a transformation? What is it that I really worry about? In addition to the transformation, they got to figure it out, or I need to do that. Do I not need to do that? And then, you know, we've got to figure out what your data going to set? What your database going to look in? And do you need to connect to some legacy system that you have on prem? Or how do you go? How do you have to figure that out and give them all of these complexities? This is really, really common for any large enterprise that has like an enterprise ID for that multi-cloud. That's basically in multiple geographies, servicing millions of customers. So that has a lot of experience doing all these things. We have open innovation labs, which are really, really awesome experience for customers. Whether they take a small project, they figured out how to change things. Not only learn how to change things from a technology standpoint, but also learn how to culturally change things, because a lot of these things. So it's not just moving from one infrastructure to another, but also learning how to do things differently. Then we have things like the container adoption programmer, which is like, how do you take a big legacy monolith application? How do you containerize it? How do you make it micro services? How do you make sure that you're leveraging the real benefits that you're going to get out of moving to the cloud or moving to a container platform? And then we have a bunch of other things like, how do you get started with Open Shift and all of that? So we've had a lot of experience with like our 2,400 plus customers doing this kind of really heavy workload migration and lifting. So the customers really get the benefits that they see out of Open Shift. >> Yeah. So Sathish, if I think about Google, specifically talking about Google cloud, one of the main reasons we hear customers using Google is to have access to the data services. They have the AI services they have. So how does that tie into what we were just talking about? If I, if I use Open Shift and you know. I'm living in Google cloud, can, can I access all of those cloud native services? Are there any nuances things I need to think about to be able to really unleash that innovation of the platform that I'm tying into? >> Yeah, absolutely not. Right. I think it's a great question. And I think customers are always wondering about. Hey, if I use Open Shift, am I going to be locked out of using the cloud services? And if anything run out as antilock. We want to make sure that you can use the best services that you need for your enterprise, like the strategy as well as for applications. So with that, right. And we've developed the operator framework, which I think Google has been a very early supporter of. They've built a lot of operators around their services. So you can develop those operators to monitor the life cycle of these services, right from Open Shift. So you can actually connect to an AI service if you want. That's absolutely fine. You can connect the database services as well. And you can leverage all of those things while your application runs on Open Shift from Google cloud. Also I think that done us right. We recognize that, when you're talking about the open hybrid cloud, you got to make sure that customers can actually leverage services that are the same across different clouds. So when you can actually leverage the Google services from On Prem as well, if you choose to have localized services. We have a large catalog of operators that we have in our operator hub, as well as in the Red Hat marketplace that you can actually go and leverage from third party, third party ISV, so that you're basically having the same consistent experience if you choose to. But based on the consistent experience, that's not tied to a cloud. You can do that as well. But we would like for customers to use any service that they want, right from Open Shift without any restrictions. >> Yeah. One of the other things we've heard a lot from Google over the last year or so has been, you know, just helping customers, especially for those mission, critical business, critical applications, things like SAP. You talked a bit about databases. What advice would you give customers these days? They're, they're looking at, you know, increasing or moving forward in their cloud journeys. >> I think it sounds as an interesting question because I think customers really have to look at, you know, what is the ID and technology strategy? What are the different initiatives to have? Is it digital transformation? Is it cloud native development? Is it just containerization or they have an overarching theme over? They've got to really figure that out and I'm sure they're looking at it. They know which one is the higher priority when all of them are interrelated and in some ways. They also got to figure out how they going to expand to new business. Because I think as we said, right, ID is basically what is driving personal software is eating the load. Software services are editing them. So you got to figure out, what are your business needs? Do you need to be more agile? Do you need to enter new businesses? You know, those are kind of important things. For example, BMW is a great example, they use Open Shift container platform as well as they use Open Shift dedicated, you know. They are like a hundred hundred plus year old car, guess, you know what they're trying to do. They're actually now becoming connected car infrastructure. That's the main thing that they're trying to build so that they can actually service the cars in any job. So in one shoe, they came from a car manufacturing company to now focus on being a SAS, an Edge and IOT company. If you really look at the cars as like the internet of things on an edge computer and what does that use case require? That use case cannot anymore have just one data center in Munich, they have to basically build a global platform of data centers or they can really easily go to the cloud. And then they need to make sure that that application double close when they're starting to run on multiple clouds, multiple geographies, they have the same abstraction layer so that they can actually apply things fast. Develop fast. They don't have to worry about the infrastructure frequently. And that's basically why they started using Open Shift. And don't know why they're big supporters of Open Shift. And then I think it's the right mission for their use. So I think it really depends on, you know, what the customer is looking for, but irrespective of what they're looking for, I think Open Shift nicely fits in because what it does, is it provides you that commonality across all infrastructure footprints. It gives you all the productivity gains and it allows you to connect to any service that you want anywhere because we are agnostic to that and as well as we bring a whole lot of services from Red Hat marketplace so you can actually leverage your status. >> Well, Sathish Balakrishnan, thank you so much for the updates. Great to hear about the progress you've got with your customers. And thank you for joining us on the Google cloud Next On Air Event. >> Thank you Stu. It's been great talking to you and look forward to seeing you in person one day. >> Alright. I'm Stu Miniman. And thank you as always for watching the Cube. (upbeat music) (upbeat music)

(upbeat electronic music) >> From theCUBE Studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE conversation! >> Hi, everybody, this is Dave Vellante, and welcome to this CUBE conversation. You know, in this COVID-19 pandemic, we've been reaching out to folks that really have good visibility on what's going on out there. Tim Conley is here, he's a principal with the ATS Group, and partner of IBM. Tim, good to see you again man, thanks for comin' on! >> You got it, Dave, how are you today? >> Not too bad, you hangin' in there with all this craziness? How are things where you are? >> Yeah, we sure are, it's like groundhog day everyday, right? >> I know, the family's goin' crazy. They want to get out, and, well summer's comin', so hopefully the pandemic is going to calm down a little bit here, give us a breather. >> I hear that. >> But so, tell us what's goin' on these days with your company, with the ATS Group, what are you seein' in the marketplace? Give us the update. >> Sure, Dave. We've been in business 19 years now as a IBM systems integrator. Doin' a lot of work around storage. There's a lot of shiny new nickels out there these days that we're trying to make sure that we stay ahead of the game on. You know, our customers demand excellence from us, because that's what we've been giving them the last, you know, 19 years. So, they demand that from us, which is actually a great position for us to be in, but you know, with a lot of the new, shiny new nickels out there today, takes a lot of energy to focus on those, make sure we're talkin' to our customer about the right things, at the right times in the marketplace. >> I had Ed Walsh on the other day, and actually a couple times within the last six months, and he shared with us, actually in studio, when we didn't have to be six feet apart, the new announcements, the simplification of the portfolio. Presumably you've seen that. What was your reaction, how do you think the customer will react? >> That's a good question. Like I said, we're always looking to be bleeding edge, that's actually where we got our name from, Advanced Technology Services Group. So, IBM consistently comes out with some really good products and solutions, and we're constantly vetting that in our innovation center, in beta programs and things like that. A couple key things that are working now with us is Hybrid Multicloud. You know, IBM comes out, like I said, with some good solutions. We vet them out, and we're real excited about Spectrum Virtualize for Public Cloud. We've been using that for probably the last 12, 14 months, so trying to get the word out our customers on what it means, for partners as well, we can have a simple 10 minute conversation with our customers and our partners, kind of describe it at a high-level, and then they can gain interest at that point. It can be a little tricky, but we try to take that trickiness out of it, and let our customers know what's really goin' on, how it works for disaster recovery, for data protection to the cloud. Customers always want to talk about those things, but a lot of them really don't know those specifics, so we literally in 10 to 15 minutes can simply it to them, let 'em know how it works, and what scenarios it might work for them. Again, doing tests, and PoCs, things like that, it's really easy for us to do. One of our big federal customers want to call today at 12 o'clock, going over that implementation. They're pretty excited about tryin' it out, 'cause everybody thinks they want to move some things to the cloud, so Spectrum Virtualize allows us to do that pretty transparently. In fact, we used it ourselves last year, 'cause we took the journey to the cloud for SaaS offering. Took us over a year to do it, let me tell ya, it's not easy. You know, people make it sound like goin' to cloud is a snap, you know, spin up some OS instances, some EBS storage, and away we go. It's not that easy. >> I was just talkin' to a software executive who started his company 37 years ago, we both agreed, that's kind of when I started in this business, we both agreed that it just keeps getting more and more complicated. So, firms like yours are, but okay, so you talk about Hybrid Multicloud, of course IBM has cloud, but IBM itself says, "Hey, we hope people put their data into our cloud, "but we know there's other clouds out there." Well, hence Multicloud. So, what do you see as going on in the marketplace, specifically as it relates to Multicloud? And I wonder if we could weave in the COVID-19. Are you seeing people more receptive to cloud? >> Yeah, I'll tell ya, with COVID-19 we've had some opportunities delayed, because customers don't quite know where the market's going to go for themselves. We actually had one customer go out of business. So, that ultimately delayed a deal forever, right? But overall, things aren't that bad, but we do see customers, you know, lookin' to make some things easier for themselves. They might have been thinking about the cloud, but COVID's kind of brought it to the forefront, and they want to make things easier right away. Maybe you can save some money, right? So, we have a calculator we created for our customers to really go measure things to see what actually would it cost to go to cloud? You know, a lot of customers have no clue what it is. We could do that in five minutes for them, really interesting so, again we'll give them that information that hey, going to cloud might be an opportunity that they didn't think might be existent 'til now. >> So, Spectrum Virtualize, otherwise known you know, for those who have been around for a while like I have as kind of the roots of the SVC, the SAN Volume Controller, and the history of that product is software that enables you to virtualize, not just IBM storage, but anybody's storage, and of course one of the major use cases has been migration. So, in downturns, people want to get more value out of existing system. You know, maybe they come off lease, or maybe they want to elongate the life, and they may not have all the function so they can plug it into an SVC, and they get all the wonderful new bells and whistles, and the capabilities there. I wonder if we could talk about that, and again, what you're seeing just in terms of the current, you know, economic situation, and then specifically as it relates to cloud? >> That's a really a good point. So, you're tying to key things in today, right? Customers are looking to save money, because they don't want their financial outlook is based on COVID-19, so being able to help customers, and you nailed it, right? SVCs, Spectrum Virtualize has been around for, gosh probably 11 or 12 years now, 13 years actually. Right? So, we pride ourselves on bringing that to customers. Showing them how they can virtualize their environments in the storage arena. And we have some gigantic customers in the federal space, commercial space, so we don't just bring out white paper, say, "Eh, well it kind of looks good." Right? We actually have distinct customers, and talk to them about how they can drive their storage efficiencies up with IBM technologies, especially virtualization. And then, you know, reducing their overall cost. That's key, especially now. Customers are constantly looking to reduce their costs and whatnot with their storage, so that's a perfect inroad to that, and then bringin' in the Multicloud part of it, you're just extending Spectrum Virtualize to the cloud. You know, it was in IBM cloud first, it was in AWS back June of last year, and now we're working at IBM on puttin' that out into Azure. You know, so we can bring those savings to customers in the cloud, which they didn't know they could do that before. >> All right Tim, talk a little bit more about Multicloud, because you know, a joke recently, up until recently anyway, that Multicloud is more of a symptom of multi vendor, as opposed to a strategy, but with shadow IT, and sort of rogue systems, and the marketing department, the sales, everybody doing their own cloud, essentially Multicloud has become a strategy that the CIO has been asked to come in, "Hey, we got all these clouds." Clean up the crime scene I call it! What are you seeing today around Multicloud? >> That's a great point, I like that term, I'm going to steal it if you don't mind. Multicloud's customers are very much interested in, we have several customers doing Multicloud, IBM, Amazon, Azure. We actually did a study for an Azure customer, where we actually projected him to go to AWS with substantial cost savings. Some of that had to do with right-sizing their environment, where they weren't right-size in azure today. But I got to tell ya, you know, Cloud's not simple. It's not easy, again I mentioned earlier, we took that journey ourselves, spent a lot of time and energy with some really smart guys on my team to take that journey. So, Multicloud is a really great idea, and should be looked at, but I'm tellin ya' it's not quite that easy to just shift around, but there are definitely things to move to different cloud vendors. Again, if we bring it back to the storage arena, right? Spectrum Virtualize today's in IBM and Amazon, it's not in other clouds, so if you want to go that route, perfect opportunity to go Multicloud. >> Yeah, I mean I think you're makin' a good point. Let's face it, for our audience, we're in the early days of Multicloud. Yes, everybody has multiple clouds, everybody talks about having multiple clouds, but to be able to run applications natively in all these different clouds, whether it's the control plane, the data plane, the transport plane, all these disparate systems, and really be able to take native advantage of the local cloud services. That's not only very complex, it's really not fully baked out here today, but you know, we heard this week at IBM saying a lot of talk about Red Hat, containers, and Open Shift. So, we're starting on that journey, and that's really the promise of Multicloud, to be able to ultimately run applications anywhere, but as you point out, that's a very complex situation today for customers. >> Yeah, that's a good point. So, I totally would follow up with you on that, that's Multicloud, customers are looking at it, and their are some distinct advantages to the different cloud vendors. One could even say on-prem is a form of cloud, right? That's just your private cloud. So, keeping things on-prem for certain scenarios makes sense, be able to tie that back to the big cloud vendors, IBM, Amazon, Azure, right? Tying them together is the direction people are looking to go, and are kind of, some of them are there and have done it, but I'd say some, or more of them are in the infancy stage of that. >> What are you seeing in terms of, just kind of switching topics on you, in terms of things like governments, compliance, a lot of talk about cyber resiliency, especially given the pandemic. What are you seeing there with customers? >> Wow, that's a big topic. It's interesting, data classification, you think it'd be that easy, especially for some of our fed' customers, it's not that easy, right? Tryin' to classify the data, they just don't know, they might know the applications, but they don't know the content of that data. Is it able to be, what is it, section 126? Something like that. Is it able to go to the cloud? So, customers have a struggle on their hands tryin' to do that, right? The technology, groups within the customers, the storage folks, the OS folks, the Apps folks, they're all about the cloud, move things to cloud, but at the end of the day, it's the security folks that need to be able to do that data classification to see can the data even go there? Let alone the application or whatnot. Fairly easy to do that kind of stuff, but the data classification, we see that's the hard part. >> Okay, so you talked about shiny new toys at the beginning of this conversation. You know, IBM, you're tryin' to be a shiny old toy, (Tim laughing) they've been around you know, a century. >> Yeah. >> Why IBM though? What is it about IBM that you choose to partner with them? Give us the good, the bad, and the what you'd like to see improve. >> I would say, we've been a partner for IBM a long time, I used to work for IBM a million years ago. At the end of the day, our customers demand excellence from us, and they demand things to work, right? So, for me to put my company, and my resources into an opportunity for my customers, we can count on IBM. One, we have a great relationship with them, they have fantastic solutions, and then we vet them out. Our customers demand that of us, and I can give real world examples of one customer to another. So again, it's not like a white paper, I read it from vendor XYZ, at the end of the day we're implementing these solutions at our customers. A lot of times we're doing em in our lab first to make sure it works as designed, figure out with the shiny new nickels, you know, what's broken with that nickel? Why's it not so shiny? Or is it really as shiny as it appears to be, right? So, being able to do that stuff in-house is great, but at the end of the day, our customers demand excellence, and you know, we have to be bringing solutions to our customers, and IBM provides quite a few solutions, especially around the storage arena, where we live and breathe, that instant marketplace. So, we have to use great solutions that we can trust, and know work. >> So, my last question is what have you learned in the last, you know, couple of months with this pandemic. Now that we start to hopefully come out of it, at least for a little while, what are you learning? What's been accelerated, or pulled forward, and we're obviously not just goin' to 2019. So, how are you seeing your business, and your customers responding, what's the sort of mindset going forward? >> I'd say two things, so there's the COVID stuff, and then I talk about ransomware, cyber security, that could be another whole topic, right? But at the end of the day, I've been on a lot of webinars, and things of last three, four weeks, five weeks, listenin' to vendors talk about their shiny new nickels, and it's, quite frankly it's a bunch of mumbo jumbo, and that's not the world we live in, 'cause that's not what our customers are asking from us. But a lot of customers are really concerned about cyber security, ransomware. I have two customers locally that got hit with ransomware last fall, and let me tell ya, it's not a pretty scene, and they were not prepared for it, right? So, one of our jobs is to really help our customers understand where their gaps are within their organization, so that if they do get hit by cyber crime, or ransomware, that they can actually survive that, and not actually have to pay for it, then be up and running in a very small amount of time, which is key. Like I said, two customers got hit, just of mine, within 20 miles of our business, and they weren't prepared for it. >> I can't leave it there Tim, what do I got to do, if I'm an organization that's concerned about ransomware, probably every organization, what are the steps that I should take, like immediately? >> I would say a health assessment, and it doesn't have to be from ATS, it could be from anybody that's got the experience, and whatnot. We do health checks for customers consistently, and they don't have to be expensive, they don't have to be like, months. People always think, "A health check, oh my god, it's going to take so much time." It really doesn't. It's a quick health check, and we can look at those key things within your organization to see where you might not be prepared. And I'm talking like not prepared, like if you get ransomware tomorrow, you very well could be out of business. It's not hard to see those kinds of things. And you can make it more detailed if customers want that, right? But I would definitely have customers, if you're interested in that, call us, call any other vendor out there that's doin' those kinds of things. But it's fairly easy for folks like us and other vendors to be able to do those health checks, just take a quick look in your environment, see where your gaps are that you could literally go out of business tomorrow. >> Okay so, first pass is you're lookin' for open chest wounds that you got to close immediately and stop the bleeding, and then what? You start implementing things, you know, best practices, air gap. >> Air gap, you stole the word right out of my mind, air gap, right? You have to start, you know, look and see where, what's the requirements? First of all, make sure you can survive the event, and get back up and running in a reasonable amount of time, right? That one customer I mentioned was probably four or five weeks before they were able to restore all their servers, and they were fortunate that a lot of those were test thing that they could kind of wait a little bit long, but the other one they nearly went out of business, 'cause they just weren't prepared for it, right? So yeah, air gapping is a key thing, right? You know, where I put my data that it can't be touched, right? That's a fairly easy thing to start off with. >> Yeah, and then the whole process of recovery, who's on deck, you know, et cetera, et cetera. How communications occurs, there's technology, and of course as always, there's people in process. Well, Tim, I'll give you the last word, bring us home! >> Bring us home. Hey, but Dave, thanks very much for your time today. This is was a great time talking to you about some key things that we've worked with day in and day out over the last couple months. Again, bringing our solutions to our customers, that they demand that excellence from us. Bringin' IBM solutions that we natively know and love, and trust, because we've done 'em many, many times with other customers. So, pretty excited about what's goin' on in the industry, lookin' at all those shiny new nickels, and see which ones are actually shiny at the end of the day. >> All right, Tim, well listen, thanks for comin' back on theCUBE, it's great to see ya. I hope we get to see each other face to face. Stay safe. >> Sounds good Dave, thanks for your time, thank you. >> All right, you're welcome, and thank you for watching, everybody. This is Dave Vellante with theCUBE. Go to http://www.siliconangle.com to check out all the news, for thecube.net, where all these videos live, and http://www.wikibon.com, where I publish weekly. We'll see you next time on theCUBE. (relaxing instrumental music)

>> Narrator: From theCUBE studios in Palo Alto and Boston, it's theCUBE, covering IBM Think. Brought to you by IBM. >> All right everybody welcome back to theCUBE's continuous coverage of IBM Think 2020. It's digital event experience, my name is Dave Vellante, Aki Duvvur's here, he's the vice president of the IBM public cloud. Aki great to see you, thanks for coming on, hope you're safe and-- >> Hey Dave, Thanks for having us on. We're as safe as can be, appreciate it. >> Yeah, so your background is really interesting, your heading IBM cloud now, you got a CTO background, you been in sales, that's interesting to me because it gave you an opportunity to really try to understand the product market fit, if you will, from the customers point of view. But how did that shape your thinking about cloud generally and specifically where you're at today. >> Hey, great question Dave. So I'll tell you from my technology background it really gave me a good appreciation for how applications get built, from everything from the infrastructure all the way up and through the application itself. To all of the criticality around how those applications need to be built, how they need to be made highly available. With business continuance in mind, which is exactly what we're trying to do at scale right now from a public crown perspective, out from an architectural first principles perspective. And then I would say from a sales perspective it gave me a sense of speed and clarity of vision. In terms of just how you have to be very net in terms of the value proposition that you bring forward to a client and how you position the public cloud at large. So those two items or backgrounds have brought me full circle into my product role today and allow me to work with a sense of urgency for our clients and their journeys and their complex transformation as we build a cloud that is very enterprise centric to support their mission critical workload. >> I want to follow up with that. So I mean the traditional approach to developing enterprise apps, you walk inside any large financial institution and a healthcare, pharma, et cetera and you would have very much a waterfall approach. Understand the requirements, you'd have a development team, you'd have an operations team, they'd throw the code over the fence, they'd throw it back. Ah your code doesn't work, well it did when I sent it to you. And the cloud has really changed all that, hasn't it? And so now you're moving much faster, you're doing agile, how do you see that applying to sort of the traditional IBM base, is it being embraced? How is it being embraced? Is it different from other approaches? I wonder if you could address that. >> I think it's a transformation for the entire company, and when I say journey to cloud it really is around not just the public cloud as a destination but it's the entire hybrid approach that we have to take in delivering those applications you just alluded to. They're pretty much the mission critical heart of the enterprise, so it's a transformation from a public cloud perspective, it's a transformation from how our services schemes engage with our clients, how we migrate, how we modernize, how we take that middleware stack and we convert it into containerized software that we can actually leverage and deploy in the public cloud as part of this transformation,. So really it's a reinvention of not just the way our customers interact with the public cloud, but the way that we as a public cloud provider and a services provider can react and give our clients the best value across that entire hybrid transformation. >> So one of the things that of course IBM executives stresses, we've heard Ginni talk about it, we hear Arvind talk about it, across the whole company you guys are aligned on this topic, only 20% of the workloads have moved to the cloud, it's the hard stuff that hasn't moved, IBM has stated you want to be the preferred supplier for all the really challenging, hybrid, workloads et cetera. So what I want to get to is how you're approaching that, is it a combination of using open technologies and it's going to, blending those with your very large software state, what's your kind of secret sauce around succeeding with that vision? >> That's a really good question, so they're kind of three pillars to our strategy. Number one is around open technologies, embracing open technologies and one of the things that we did very early on in our transformation, in fact back in 2017, before any other cloud provider focused on this, we re-based our entire public cloud on Kubernetes as the base. Not only for the way we deliver up-stack services, whether it's Watson, our IOT or other service, but also in the way that we deliver our IaaS. So our entire control plane is built on Kubernetes. That was a big bet that we made probably two years before everybody else in the industry sort of followed suit. And we are the only cloud provider today that has their entire cloud based on Kube. That was one pillar, the second pillar was around pervasive security, so it's ensuring that our client have the controls required to be able to deliver pervasive security, whether it's encryption and flight at rest or in motion, but also ensuring that they're the only one's that have access to their keys. So nobody else, not even the provider can decrypt their data in the public cloud. And then finally it's around enterprise capabilities, so as you talked about this other 80% of workloads, a lot of those apps are brittle workloads, so they have upstream and downstream connectivity that creates a lot of complexity and chatter in the application itself. So you've got to be able to support those workloads from a public cloud perspective so that there is none of that chattiness and you can actually deliver those applications in a way that they can, one, be moved into the public cloud and then later transformed into microservices and or into microservices directly as part of that transformation, so that middleware content et cetera, delivered as containers allows for a lot of that transformation of different aspects of the cloud. >> Know what, take us back to that bet that you made, So Kubernetes obviously for portability, the decision had to be made strategically that, yeah, just going to try to lock everybody into the IBM cloud. You're going to support multiple clouds, and in all fairness you kind of were later to the cloud game so that became part of your strategy, hybrid is obviously a piece of that, but you embraced that. Many cloud providers out there were late to embracing that or flat-out don't embrace that sort of multicloud approach. Security's kind of table stakes and we're going to get into that later but that enterprise apps piece is critical. Take us back to that Kubernetes decision. What was that, was that the strategy of being open cloud and multicloud, was it sort of a Red Hat angle, pre-Red Hat acquisition where you had affinity towards not only Linux but OCP, maybe you can talk about that. >> I think it's a combination of many things, in fact it predates Red Hat too in that, this was back in 2017, and fundamentally after Google open-sourced Kubernetes, one of the big, if you look at the way that the virtual server platforms back in the late 90s, early 2000s, one of the big challenges was around management of those BM's at scale. So very similarly we saw containers as being a very rapid approach to application deployment and really sort of merging that DevOps transformation that many of our clients were going through. So we said that this was a perfect vehicle to not only deliver applications at scale but also ensure all of the attributes of a public cloud, which are higher levels of availability, self-healing and scale-up, scale-downing, able to turn on more storage, more memory so you weren't tied into the physical boundaries of a typical virtual machine. That really allowed us to sort of break the paradigm a little bit in terms of our approach. And the bet paid off, because we have a significant, almost 20,000 production clusters running across our enterprise clients today, so pretty significant footprint just on Kube alone. >> Well I can say and it gives clients the opportunity to have portability, hedges their bets, gives them an exit strategy if in fact they want one, and it just seems like good business. What about Open Shift, how does that fit in there in regards to OCP? >> Well I think Open Shift is a perfect complement right now. So as we talk about the fact that we have a cloud built on Kubernetes. Open Shift becomes the engine that runs all of our capabilities now. So as we think about how we deliver our services, how we deliver common sources whether it's logging or monitoring identity and access, all of the governance and orchestration required around a Kube environment, Open Shift is a terrific solution to be able to provide that at scale. Not just for our clients as a first class deployment in the public cloud but also as a look and deploy on prem so that they have multi-model deployments here with perhaps their applications that are very sensitive, that have PHI data, that they want to control on prem, they have that approach and they have the ability to be able to support it. They also have the ability to take advantage of strangler patterns, so parts of the application that sit, run perhaps in an Open Shift environment in the on prem environment with other aspects of it being controlled, orchestrated and run in the public cloud on our Red Hate Open Shift Kubernetes service. So we've got all of those attributes and capabilities to support that hybrid and even multicloud deployment. >> What if we get, sort of dive into security. You've seen this sort of interesting divergent narrative in the industry. On the one hand you've had executives like Pat Gelsinger come out and say security is broken. On the other hand you had, for instance, the CISO of AWS, say no security in the clouds great. So if you're a customer who do you believe? And you talk to CISO's and they say look it, it's on us, this problem will never be solved, it's an ongoing challenge. But I wonder if you could give us IBM's point of view on security, cause you're on both sides. You got the cloud, you got on prem, you got a deep history in security going back to Rack-F on the mainframes and so I wonder if you can share with us your thoughts on that. >> Well I think security is table stake, and always been table stakes and now more so than ever, especially as we look at that other 80% that we talked about. These are revenue generating applications, they're mission critical and they have significant impact if they're down in any way, shape or form, especially if there's a security attack of some kind and there's a breach. You're talking about businesses completely going out, I mean they're basically bankrupt at that point. So it is table stakes. We have taken a very long strategic look at how we build security, from the chip all the way up into the security architecture and into memory as well. Ensuring that every sort of attack vector is locked down. We have our dedicated HSM's with the highest FIPS, compliance FIPS 140-2 level four. As I mentioned before, we allow for keep your own key and bring your own key, everybody does bring your own key but keep your own key is a clients ability to bring and mange their own key in the public cloud. So if anybody tries to tamper with it, that just gets locked down and there's no access that even the provider could have in terms of decrypting. We have to get rid of that dedicated HSM at that point. So it really puts the control on our clients and ensures that every aspect of their environment from profiles to templates, you had mentioned CICD pipeline before, it's ensuring that we have a shift-left strategy which is really Sec DevOps because it really allows for us to focus on security in every interaction from the start of how code gets integrated and deployed into the cloud. So ensuring that we have that entire end to end approach nailed down is pretty important to us. >> One thing that's key if you're a CISO you don't want to have different security protocols for on prem and the cloud, you want that sort of end to end approach. Now maybe that doesn't happen overnight but presumably that's kind of the vision is that kind of consistency because every CISO will tell you the lack of skills is our biggest challenge. So the last thing we need to do is learn just a whole 'nother environment, all new processes. How have you made progress in terms of that end to end experience? >> Well we've tried to make it completely cloud native. We've tried to make it very API orientated. So it's basically really simple for them to integrate into the cloud and take advantage of the CICD pipeline as I mentioned. So if you look at how we deliver our code from a tekton perspective and if you look at how we can do signed images in the registry, so ensuring that developers are only authorized to run the appropriate applications that they have permission for and that they can't leverage other assets or pools that they're not. So ensuring that role-based access control is very tightly knit, ensuring least privileged access as opposed to opening up and ensuring that everybody has all access all the time and then working your way down into least privileged access is critical. So it's those core first principles that you would leverage in an on prem environment and extending it into the public cloud so that it becomes a very translatable experience for our client. >> Okay, I want to push you a little bit. We started out with openness and you sort of laid down the gauntlet as we made the decision early on to be open. What if I'm a security practitioner, I say hey I like Cloud Stripe or I like Okta or I want to use Zscaler. Can I use those in your environment? How open are you to that type of approach? >> You absolutely can and you can integrate into our security dashboard. So the nice thing about it is you can leverage our capabilities that we have in the cloud, or you can leverage your third-party tools and you can integrate them so you have a single plane of glass and you always know who's accessing your systems, where they're accessing them from, did they succeed or did they fail. This is table stakes allowing integration for best of class and best of breed security technology is core. >> So you're obviously cloud guy, the more cloud, better for you personally, your group, whatever. But what's the business case for moving those mission critical workloads in the cloud. Former CTO, I'm sure you've had a lot of discussions with customers, hey, why not just leave it there put a brick wall around it. It ain't broke, why fix it? What's the business case that you're seeing for putting those workloads in the cloud. >> I think the current healthcare crisis we're in is probably proving out a lot of the challenges of managing a data center in traditional sense, number one. And I think if you think about just the innovation agenda that many of our clients have, they're kind of hand strung by all of the legacy technologies and sometimes monolithic architectures that they've got deployed. They're unable to break out of that because of the amount of cost and the amount of resource it takes to manage those environments today and keep a lot of end of life infrastructure running. And really the move to public cloud and being able to transform and modernize your workloads frees up a lot of that budget in innovation that you can start to infuse into driving new revenue streams from a company perspective. I think that is the critical aspect to it and I think the current crisis just proves out that clients that have built for scale, who've kind of gone in with a cloud first set of principles are actually well setup to be able to navigate some of the current challenges a little bit better than others. >> Yeah and I think, listening to you talk reminds me of a conversation I had probably 10 years ago with a former IBMer legend, Steve Mills who said to me, look we spend way too much money on IT labor and it's just not productive so automation is key, you can't scale without it. I talked earlier about the skills gap, automation is at least one part of that answer. Because people just, to your point, if you're spending money on, wasting it on labor that's not giving you differentiation, that's stealing from the innovation budget. >> Yeah, totally agree Dave. >> So give me the final word, what's your vision for the IBM public cloud, where do you see all this in three to five years? >> Well I think we're just at the tip of the iceberg right now when it comes to a lot of the complex (murmurs) applications that we talked about before, ERP applications, mission critical back office apps that haven't moved and I think we are very, very early in that journey. And I think we're positioned really well to capture and win that marketplace. I think we have the right solutions, we have the right sort of core principles. As I mentioned open and secure and enterprise grade, having a multi-platform approach to support our clients applications, being able to modernize and kind of walk them through this crawl, walk, run approach to how they transform into the public cloud. And having all of the service expertise, so we're not just this CSP but we're also an MSP and we have sense around handling complex workload. We've done that all through our existence and we feel like this is where this starts to get interesting for our clients now as they take these next steps and as you probably heard last year with our announcement of the FFS ready public cloud with Bank of America. We're trying to bring all that together in terms of how we meet our client and ensure that we can take care of their regulatory requirements, which continue to change as well regardless of industry. >> Well it's a multi-trillion dollar, trillion plus dollar opportunity that you guys are after. And you're in the cloud game, a lot of people tried and failed, IBM made it through that knot hole and now you're in a position to really compete and participate in that modernization of those workloads. We've done research that shows that a lot of this, especially for the hard to move workloads is about risk, and to the extent that you can maintain that compatibility if you will, between what's on prem and what's in the cloud. You dramatically de-risk the cloud move and the decision, so yeah, I think you're in a good spot. And I really appreciate you coming on theCUBE. >> Hey Dave, thanks for having me. Appreciate it. >> All right, our please Aki. This is Dave Vellante for theCUBE, this is our continuous coverage of IBM Think 2020, the digital event experience. We'll be right back right after this short break. You're watching theCUBE. (calming music)

>>from around the globe. It's the Cube with digital coverage of Red Hat. Summit 2020 Brought to you by Red Hat. >>Yeah. Hi. And welcome back to the Cube's coverage of Red Hat Summit 2020 on stew. Minimum in this year's event, of course, happened globally. Which means we're talking to Red Hat executives, customers and partners where they are around the globe on and happy to welcome back to the program. One of our cube alumni, Badani, who is the senior vice president. Cloud platforms at Red Hat is great to see you. >>Yeah, thanks a lot for having me back on. >>Yeah, absolutely. So you know, the usual wall to wall coverage that we do in San Francisco? Well, it's now the global digital, a little bit of a dispersed architecture to do these environments. Which reminds me a little bit of your world. So, you know, the main keynote stage. You know, Paul's up There is the, you know, new CEO talking about open hybrid cloud. And of course, the big piece of that is, you know, open shift and the various products, you know, in the portfolio there, So ah, personal. We know there's not, you know, big announcements of, you know, launches and the like, But your team and the product portfolio has been going through a lot of changes. A lot of growth since last time we connected. So bring us up to speed as to what we should know about. >>Sure. Thanks s Oh, yes, not not a huge focus around announcements, this summit, especially given everything going on in the world around us today. Ah, but you know, that being said, we continue our open shift journey. We started that well, you know, many years ago. But in 2015 and we had our first release both the stone kubernetes in a container focused platform. Ever since then, you know, we continue to groan to evolve Atlassian count now over 2000 customers globally. I trusted the platform in industries that literally every industry and also obviously every job around around the globe. So that's been great to see you. And last summit, we actually announced a fairly significant enhancement of a platform with a large fortune before big focus around created manageability ability to use operators which is, you know, kubernetes concept to make applications much more manageable. um, you know, when they're being run natively within within the platform, we continue to invest. There s so there's a new release off the platform. Open shift 4.4 based on kubernetes 1.17 big made available to our customers globally. And then really, sort of this this notion of over the air updates right to create a platform that is almost autonomous in nature, you know, acts more like your your your mobile phone in the way you can manage and and update and upgrade. I think that's a key value proposition that, you know, we're providing to our customers. So we're excited to see that and then be able to share that with you. >>Yeah, so a chef won't want to dig into that a little bit. So one of the discussions we've had in the industry for many years is how much consistency there needs to be across my various environments. We know you know Kubernetes is great, but it is not a silver bullet. You know, customers will have clusters. They will have different environments. I have what I do in my data centers or close. I'm using things in the public clouds and might be using different communities offering. So you know, as you said, there's things that Red Hat is doing. But give us a little insight into your customers as to how should they be thinking about it? How do they manage it? One of the new pieces that we're building it into a little bit, of course, from a management sand point is ACM, which I know open shift today, but going toe support some of the other kubernetes options you know down the road. So how should customers be thinking about this? How does Red Hat think about managing? Did this ever complex world >>Yes, So Student should have been talking about this for several years now, right with regard to just the kind of the customers are doing. And let's start with customers for us, because it's all about you know, the value for them so that this year's summit we're announcing some innovation award winners, right? So a couple of interesting ones BMW and Ford, um, you know BMW, you know, building It's next generation autonomous driving platform using containers. And then, you know, police Massive data platform an open ship for doing a lot of interesting work with regard to, uh, bringing together. It's a development team taking advantage of existing investments in hardware and so on, You know, the in place, you know, with the platform. But also, increasingly, companies that are you know, for example, in all accept. All right, so we've got the Argentine Ministry of Health. We've got a large electricity distribution company adopting containers, adopting middleware technology, for example, on open shift until great value. Right. So network alerts when there's electricity outrage going from three minutes to 10 seconds. And so, as you now see more and more customers doing, you know, more and more if you will mission critical activities on these platforms to your points to your question is a really good one is not got clusters running in multiple markets, right? Perhaps in their own data center, across multiple clouds and managing these clusters at scale, it becomes, you know, more, more critical up. And so, you know, we've been doing a bunch of work with regard to the team, and I actually joined us from IBM has been working on this. Let's remember technology for a while, and it's part of Red Hat. We're now releasing in technology preview. Advanced cluster management trying to solve address questions around. What does it mean to manage the lifecycle of the application process? Clusters. How do I monitor and imbue cluster help? You know, regardless of you know, where they run. How do I have consistent security and compliance for my policies across the different clusters. So really excited, right? It is a really interesting technology. It's probably most advanced placement. That's our market. What? IBM working on it. We know. Well, before you know, the team from from there, you know, joined us. And now we're making it much more >>widely available. Yeah, actually, I just want one of things that really impressed some of those customers. First off. Congratulations. 2000 you know, great milestone there. And yeah, we've had We're gonna have some of the opportunity to talk on the cube. Some of those essential services you talk Ministry of Health. Obviously, with a global pandemic on critically environment, energy companies need to keep up and running. I've got Vodafone idea also from India, talking about how communication service is so essential. Pieces and definitely open shift. You know, big piece of this story asst to how they're working and managing and scaling. Um, you know, everybody talks about scale for years, but the current situation around the globe scale something that you know. It's definitely being stressed and strained and understood. What? What? What's really important? Um, another piece. Really interesting. Like to dig in a little bit here. Talk about open shift is you know, we talk kubernetes and we're talking container. But there's still a lot of virtualization out there. And then from an application development standpoint, there's You know what? Let's throw everything away and go all serverless on there. So I understand. Open shift. Io is embracing the full world and all of the options out there. So help us walk through how Red Hat maybe is doing things a little bit differently. And of course, we know anything right Does is based on open source. So let's talk about those pieces >>Yes, to super interesting areas for us. Um, one is the work we're doing based on open source project called Kube Vert, and that's part of the CN CF incubating projects. And that that is the notion off bringing virtualization into containers. And what does that mean? Obviously There are huge numbers of workloads running in which machines globally and more more customers want, you know, one control plane, one environment, one abstraction to manage workloads, whether they're running in containers or in IBM, I believe you sort of say, Can we take workloads that are running in these, uh, give, um, based which machines or, uh, VMS running in a VM based environment and then bring them natively on, run them as containers and managed by kubernetes orchestrate across this distributed cluster that we've talked about? I've been extremely powerful, and it's a very modern approach to modernizing existing applications as well as thinking about building new services. And so that's a technology that we're introducing into the platform and trying to see some early customer interest. Um, around. So, >>you know, I've got ah, no, I'm gonna have a breakout with Joe Fernandez toe talk about this a little bit, but you know what a note is you're working on. That is, you're bringing a VM into the container world and what red hat does Well, because you know your background and what red hat does is, you know, from an operating system you're really close to the application. So one of my concerns, you know, from early days of virtualization was well, let's shut things in a VM and leave it there and not make any changes as opposed to What you're describing is let's help modernize things. You know, I saw one of the announcements talking about How do I take job of workloads and bring them into the cloud? There's a project called Marcus. So once again, do I hear you right? You're bringing V M's into the container world with help to move towards that journey, to modernize everything so that we were doing a modern platform, not just saying, Hey, I can manage it with the tool that I was doing before. But that application, that's the important piece of it. >>Yeah, and it's a really good point, you know, We've you know, so much to govern, probably too little time to do it right, because the one that you touched on is really interesting. Project called caucuses right again. As you rightly pointed out, everything that is open source up, and so that's a way for us to say, Look, if we were to think about Java and be able to run that in a cloud native way, right? And be able to run, um, that natively within a container and be orchestrated again by kubernetes. What would that look like? Right, How much could be reduced density? How much could be improved performance around those existing job applications taking advantage off all the investments that companies have made but make that available in kubernetes and cloud native world. Right? And so that's what the corpus project is about. I'm seeing a lot of interest, you know, and again, because the open source model right, You don't really have companies that are adopting this, right? So there's I think there's a telecom company based out of Europe that's talking about the work that they're already doing with this. And I already blogged about it, talking about, you know, the value from a performance and use of usability perspective that they're getting with that. And then you got So you couple this idea off. How do I take BMC? Bring them into contempt? Right? Right. Existing workloads. Move that in. Run that native check. Right? Uh, the next one. How do I take existing java workloads and bring them into this modern cloud native Kubernetes space world, you know, making progress with that orchestra check. And then the third area is this notion off several lists, right? Which is, you know, I've got new applications, new services. I want to make sure that they're taking advantage, appropriate resources, but only the exact number of resources that require We do that in a way that's native to kubernetes. Right? So we're been working on implementing a K native based technologies as the foundation as the building blocks, um, off the work we're doing around serving and eventing towards leading. Ah, more confortable several institution, regardless of where you run it across any off your platform prints up. And that will also bring the ability to have functions that made available by really any provider in that same platform. So So if you haven't already to put all the pieces together right that we were thinking about this is the center of gravity is a community space platform that we make fully automated, that we make it very operational, make it easy for different. You know, third party pieces to plug in, writes to sort of make sure that it's in trouble in modular and at the same time that start layering on additional Kim. >>Yeah, I'm a lot of topics. As you said, it's Siachin. I'm glad on the serverless piece we're teasing out because it is complicated. You know, there are some that were just like, Well, from my application developer standpoint, I don't >>need to >>think about all that kubernetes and containers pieces because that's why I love it. Serverless. I just developed to it, and the platform takes care of it. And we would look at this year to go and say, Well, underneath that What is it? Is it containers? And the enter was Well, it could be containers. It depends what the platform is doing. So, you know, from from Red Hat's standpoint, you're saying open shift server lists, you know? Yes, it's kubernetes underneath there. But then I heard you talk about, you know, live aware of it is so, um, I saw there's, you know, a partner of Red Hat. It's in the open source community trigger mesh, which was entering one of the questions I had. You know, when I talk to people about serverless most of the time, it's AWS based stuff, not just lambda lots of other services. You know, I didn't interview with Andy Jassy a few years ago, and he said if I was to rebuild AWS today, everything would be built on serverless. So might some of those have containers and kubernetes under it? Maybe, but Amazon might do their own thing, so they're doing really a connection between that. So how does that plug in with what you're doing? Open shift out. All these various open sourced pieces go together. >>Yes, I would expect for us to have partnerships with several startups, right? You know you name, you know, one in our ecosystem. You know, you can imagine as your functions, you know, running on our serverless platform as well as functions provided by any third party, including those that are built and by red hat itself, Uh, you know, for the portal within this platform. Because ultimately, you know, we're building the platform to be operational, to be managed at scale to create greater productively for developments. Right? So for example, one of things we've been working on we are in the area of developer tools. Give the customers ability. Do you have you know, the product that we have is called cordon Ready workspaces. But essentially this notion off, you know, how can we take containers and give work spaces that are easy for remote developers to work with? Great example. Off customer, actually, in India that's been able to rapidly cut down time to go from Dev Productions weeks, you know, introduced because they're using, you know, things like these remote workspaces running in containers. You know, this is based on the eclipse. Ah, Apache, the the CI Project, You know, for this. So this this notion that you know, we're building a platform that can be used by ops teams? Absolutely true, but the same time the idea is, how can we now start thinking about making sure these abstractions are providing are extremely productive for development teams. >>Yeah, it's such an important piece. Last year I got the chance to go to Answerable Fest for the first time, and it was that kind of discussion that was really important, you know, can tools actually help me? Bridge between was traditionally some of those silos that they talked about, You know, the product developer that the Infrastructure and Ops team and the AB Dev teams all get things in their terminology and where they need but common platforms that cut between them. So sounds like similar methodology. We're seeing other piece of the platforms Any other, you know, guidance. You talked about all your customers there. How are they working through? You know, all of these modernizations adopting so many new technologies. Boy, you talked about like Dev ops tooling it still makes my heads. Then when I look at it, some of these charts is all the various tools and pieces that organizations are supposed to help choose and pick. Ah, out of there, they have. So how how is your team helping customers on kind of the organizational side? >>Yes. So we'll do this glass picture. So one is How do you make sure that the platform is working to help these teams? You know, by that? What I mean is, you know, we are introducing this idea and working very closely with our partners globally and on this notion of operators, right, which is every time I want to run data bases. And you know, there's so many different databases. There are, you know, up there, right? No sequel, no sequel. and in a variety of different ones for different use cases. How can you make sure that we make it easy for customers trial and then be able to to deploy them and manage them? Right? So this notion of an operator lifecycle because application much more manageable when they run with data s O. So you make you make it easier for folks to be able to use them. And then the question is, Well, what other? If you will advise to help me get that right So off late, you probably heard, you know, be hired a bunch of industry experts and brought them into red hat around this notion of a global transformation and be able to bring that expertise to know whether you know, it's the So you know, Our Deep in Dev Ops and the Dev Ops Handbook are you know, some of the things that industry is a lot like the Phoenix project and, you know, just just in various different you know what's your business and be able to start saying looking at these are told, music and share ideas with you on a couple that with things like open innovation labs that come from red hat as well as you know, similar kinds of offerings from our various partners around the world to help, you know, ease their transition into the >>All right. So final question I have for you, let's go a little bit high level. You know, as you've mentioned you and I have been having this conversation for a number of years last year or so, I've been hearing some of the really big players out there, ones that are, of course, partners of Red Hat. But they say similar things. So you know, whether it's, you know, Microsoft Azure releasing arc. If it's, you know, VM ware, which much of your open ship customers sit on top of it. But now they have, you know, the Project Pacific piece and and do so many of them talk about this, you know, heterogeneous, multi cloud environment. So how should customers be thinking about red hat? Of course. You partner with everyone, but you know, you do tend to do things a little bit different than everybody else. >>Uh, yeah. I hope we do things differently than everyone else. You know, to deliver value to customers, right? So, for example, all the things that we talk about open ship or really is about industry leading. And I think there's a bit of a transformation that's going on a swell right within the way. How Red Hat approaches things. So Sam customers have known Red Hat in the past in many ways for saying, Look, they're giving me an operating system that's, you know, democratizing, if you will. You know what the provider provides, Why I've been given me for all these years. They provided me an application server, right that, you know, uh, it's giving me a better value than what proprietary price. Increasingly, what we're doing with, you know, the work they're doing around, Let's say whether it's open shift or, you know, the next generation which ization that we talked about so on is about how can we help customers fundamentally transform how it is that they were building deploy applications, both in a new cloud native way. That's one of the existing once and what I really want to 0.2 is now. We've got it least a five year history on the open shift platform to look back at you will point out and say here are customers that are running directly on bare metal shears. Why they find, you know, this virtualization solution that you know that we're providing so interesting Here we have customers running in multiple different environments running on open stack running in these multiple private clouds are sorry public clouds on why they want distribute cluster management across all of them. You know, here's the examples that you know we could provide right? You know, here's the work we've done with, you know, whether it's these, you know, government agencies with private enterprises that we've talked to write, you know, receiving innovation awards for the world been doing together. And so I think our approach really has been more about, you know, we want to work on innovation that is fundamentally impacting customers, transforming them, meeting them where they are moving the four into the world we're going into. But they're also ensuring that we're taking advantage of all the existing investments that they've made in their skills. Right? So the advantage of, for example, the years off limits expertise that they have and saying How can we use that? Don't move you forward. >>Well, a chef's Thank you so much Absolutely. I know the customers I've talked to at Red Hat talking about not only how they're ready for today, but feel confident that they're ready to tackle the challenges of tomorrow. So thanks so much. Congratulations on all the progress and definitely look forward to seeing you again in the future. >>Likewise. Thanks, Ian Stewart. >>All right, I'm still Minuteman. And much more coverage from Red Hat Summit 2020 as always. Thanks for watching the Cube. >>Yeah, Yeah, yeah, yeah, yeah, yeah.

>>live from Orlando, Florida It's the cue covering Microsoft Ignite Brought to you by Cho He City >>Welcome back, everyone. And welcome to the cubes live coverage of Microsoft Ignite Here in Orlando, I'm your host, Rebecca Night, along with my co host Stew Minimum. We're joined by Nicholas Djerassi. Moto's He is a cloud computing evangelist at Red Hat. Thank you so much for coming on the Cube. It's a pleasure. Thank you. So tell us a little bit about what you do at Red Hat. >>So I work with a lot of red, have partners really trying to foster the ecosystem and build red have products and solutions that can actually be deployable, repeatable for different customers. So different verticals. Financial health care doesn't really matter. For the most part, I try and just focus on cloud computing and really just evangelizing a lot of our technologies that we have. >>Okay, so So what are the kinds of things you're doing here at ignite? >>So I've been spending a lot of time actually working with some of the partners, like a center IBM. We've been doing a bunch of different webinars a little bit of hands on workshops that kind of educating people about distributed computing edge computing on dhe some of the technologies that we've been working along with Microsoft. So, uh, co engineering of sequel server The man is service offering that we're doing with open shift, which is our enterprise great kubernetes platform along many other >>different things. So So, Nicholas, you know, it's been a couple of years now that we've gotten over some of the gas. Wait. Microsoft has not said that, you know, we're killing the penguins, you know, off on the side. I was in Boston for Red Hat Summit. Tatiana Della's up on stage there, you know, Red hat. You know he's not hiding at the show. So bring us inside. You know where customers deployments are happening where engineering efforts are working together. You know, we know we've been hearing for years red hats in all of the clouds and partnering all of the merit. So what? What, you know, different or special, about the Microsoft relationship? >>I mean, honestly, I think the relationship is just evolving and growing because our customers were asking for it right there, going towards hybrid and multi cloud type of strategies. They want to be able to take advantage of, you know, running rail within their own data. Centers were running rails specifically on top of Microsoft Azure, but they're also looking at other club service providers. I think it's gonna be mandated eventually at some point in time where customers are gonna start looking at diversification when it comes to running applications, wherever it makes sense, taking advantage of different you know, cloud end of service is different providers. So we've been getting a lot of time like understanding what their needs are and then trying to build the engineering to actually address those needs. I think a lot of that has really come from the co engineering that we have going on. So we have a red head engineer sitting alongside bikers, off engineers, spending a lot of time building things like the Windows distraction layer wsl things along those lines, All >>right, so I'll be a Q Khan in a couple of weeks and kubernetes still, a lot of people don't really understand where it fits Way have been saying in a Cuban eight is gonna be baked into every platform. Red hat, of course, is not really a major contributor but has a lot of customers on open shift. We had Microsoft, you know, this week, talking about as your arc is in preview. But you know, they're they're the David Taunton who does partnership, Engagement says. You know, this does not mean that we will not continue to partner with open shift in the best place to run open shift is on azure. It's the most secure. It's the best. So help us understand his toe. You know where this fits In the overall discussion of that multi hybrid cloud that we were talking about earlier. I >>think everybody wants kind of a single pane of glass for manageability. They want ability to actually look and see where their infrastructure is being deployed. One of the pitfalls of moving to the cloud is the fact that it's so easy to spend a resource is that a lot of times we lose track of where these resource is. Our or individuals leave companies, and when they leave, cos they leave behind a lot of leftover items and instances, and that becomes really costly over a period of time. Maybe not so bad if you have, you know, 100 or 500 instances. But when you talk to some of these enterprise customers that are running 110,000 instances and spending millions of dollars a month, it could get very costly. And not only that, but it could also be a security risk is well, >>so let's talk about security. What kinds of conversations are you having with regard to security and data protection at this conference? >>So you know, one of the biggest things that we've had a lot of customers asking about his redhead insights so ready in sizes away it's a smart management application that actually ties into looking at either workloads or configuration management. It could actually tell you if you have a drift. So, for example, let's say you install sequel server on well, and you miss configure it. You leave the admin account running on it, it can actually alert you and make recommendations for remediation. Or maybe in general, you're using you know, S E. Lennox is disabled. The things along those lines so insights can actually look into, uh, the operating system or the applications and tell you if there's miss configurations all right, >>a lot of discussion about developers here, You know, day to keynote was all about, you know, AP Dev And, like Sathya have been a lot of time talking about the citizen developer. Seems like that would be an intersection between what red hats doing in and Microsoft. >>Um, so I would say, you know, we're obviously very developer first focused right when we built things like Open Shift Way kind of. We're thinking about developers. Before you were thinking about operations, and later on, we actually had to build more of the operations aspects into it. Now, like, for example, in open shift, there's two different portals. There's one for the developer Focus and one for the I T admin focus with operations groups because they want to see what's going on. Developers don't really care specifically about seeing the distraction of where things are. They just want to deploy their code, get it out the door as quickly as they can, and they're really just not too concerned about the infrastructure component pieces. But all of these developers, they want to be ableto right there, applications right there code and deploy it essentially anywhere and everywhere and having the easiest process and We're really just trying to make that as simple as possible, like visual studio plug ins that we have for open shift, you know, Eclipse G and other things. So really, I mean, Red has always been very developer focused first, >>so does that seeing Microsoft Satya Nadella up on the stage talking about this developer first attitude that Microsoft is really embracing the developer. And, as you said at development for all that does seem like a bit of a cultural shift for Microsoft much more aligned with the red hat way and sort of open source. So are you talking about that within without your cut with your colleagues? That red hat, about the change that you've seen the evolution of Microsoft? >>Absolutely. I mean, if you look at, like Microsoft, the contributions that they're putting towards, like kubernetes or even contribution towards open shift, it's It's amazing, right? I mean, it's like the company's gonna complete 1 80 from the way that they used to be. There's so much more open the acquisition of Like Get Hub, for example, all these different changes, it's it's amazing. He's done amazing things with the company. I can't say enough positive things about all the wonderful things that he's done. So >>all right, so Nicholas Red Hat has an interesting position in the marketplace because you do partner with all of the clouds on the environment. While IBM is now the parent owner of Red Hat and they have a cloud, your customers touch all of them. I'm not gonna ask you to competitively analyze them. But when you're talking to customers that are choosing Azure, is there anything that calling out as to why they're choosing Microsoft where you know they have, you know, a advantage of the marketplace or what is drawing customers to them on then? Of course, redhead. With that, >>I think Microsoft is more advanced when it comes to artificial intelligence and machine learning. A, I and ML and computing. I think they're light years ahead of everyone else at this point in time. I think you know, Amazon and Google are kind of playing a little bit of catch up there, Um, and it's showing right. If you look at the power platform, for example, customers are embracing that. It's just it's fantastic looking at a lot of the changes that they've implemented and I think it's very complimentary toe the way that people are starting to build their applications. Moving towards distributed infrastructures, Micro Service's and then obviously cloud native service is as well >>in terms of the future will be. We are really just scratching the surface when it comes to to the cloud. What do you see 5 10 years from now in terms of growth rates and also in terms of the ways in which companies are using the cloud. >>So I kind of like Thio equate it towards, like, the progression that we've had with cars. I know it sounds so simple, but, you know, we went from steam engine to regular piston engines, and now we've gotten to a point where we have electric cars and there's gonna be self driving cars. I think we're gonna get to a point where code is gonna be autonomous in a sense, right self correcting ability to actually just write code and deploy it. Not really having to worry about that entire infrastructure layer. Everybody's calling it server lists. There's always gonna be a server per se, but I think we're gonna have a point where next 5 to 10 years that all of that is gonna be completely abstracted away. It's just gonna be focused on writing the code and machine learning is gonna help us actually evolve that code and make it run faster and make it run better. We're already seeing huge benefits. And when it comes to machine learning and the big data analytics and things on those lines, it's just natural progression. All right, >>love, you know what's top of mine from the customers that you're talking to Earth event. Any new learning is that you've had or, you know, things that have kind of caught your attention. >>I think the biggest thing, honestly, is really been them. The multi cloud Polly Cloud methodology that everybody seems to be embracing. It seems like every customer I'm talking to is looking at trying to avoid that vendor lock and per se, but still have that flexibility to deploy their applications wherever and still utilize cloud Native Service's without actually specifically having to, you know, go completely open source >>and one of the challenges there is every cloud. I need different skills to be able to do them. If I'm deploying it, it's the people and being able to do that. You know, we all lived through that era of trying to do multi vendor, and often it was challenges. So have we learned from what we've done in the past? Can multi cloud actually be more valuable to a company than the sum of its parts? >>I think so. And I think that's the reason why I, like Microsoft, is investing in art. For example, I think those methodologies way No multi clouds, tough. It's never gonna be easy. And so these companies need to start building in developing platforms for it. There needs to be be great if there were standard AP ice and such right, but they're never gonna do something along those lines. But I think the investments that they're putting forth now are gonna make Multiplied and Polly Cloud a lot easier in the future. And I think customers are asking for it. Customers ask for it, they're gonna build it. >>What does this mean for the workforce, though? In in terms of the kinds of candidates that cos they're going to hire because, as we said, it does require different skills and and different capabilities. So how what's your advice to the young computer scientists coming up in terms of what they should be learning. And then also, how do you think companies are making sensible of this? >>So I know from a company respectable. It's challenging a lot of companies. Especially, for example, I was talking to a very large financial institution, and they were saying that their biggest issue right now is hiring talented people to deal with Micro Service's kubernetes. Any time to hire someone, they end up getting poached by the big cloud companies. So you know, it's one of those things where people are gonna have to start diversifying their talents and look at the future. So I mean, obviously, Micro Service's are here. They're gonna continue to be here. I would say people should invest in that. But also look a server Lis, you know, I definitely think serverless these days towards the future. And then when it comes to like learning skills of multi club, I think cloud competing, that's just the number one growing in general. >>So since you didn't bring up server Lis, you know, today I hear serverless and most customers that I talked to that means a W s number two in the space probably is Microsoft, but there's efforts in to try to help, you know, give a little bit of open source and standardization there. Where's Red Hat? Stand on this. What do you see? What from Microsoft? What are you hearing from customers? >>Were heavily contribute all the different, you know, projects, trying to make server lists like easier to use and not so much specific vendors, Right? So whether that's, you know, Apache, spar or whatever you want to consider it to be, were trying to invest. Invest in those different types of technologies. I think the main issue we serve earless right now is we still don't really know how to utilize it effectively. And it's still kind of this gray area in a sense, right? It's cutting edge, bleeding edge emerging technologies. And it's just, in my opinion, it's not perfectly ready for prime time. But I think that's specifically because there's just not enough people that are actually invested in it. This point in time. So >>So what are you gonna take back with you when you head back to Phoenix from from this conference? What are the things that have sparked your interest the most. >>Gosh, I live, I would probably have to say, Really digging in deep on the Ark announcement. I think that's the thing that I'm most interested in, understanding how how we can actually contribute to that and maybe make that plug double for things like open Shift. You know, whether it's open shift on premise, open shit, running in the cloud on another, Well, architecture's, you know, things like insights. Being able to plug into that, I really see us trying to work with Microsoft to start building those things. >>Well, Nicholas, thank you so much for coming on. The cubit was really fabulous conversation. Thank you. I'm Rebecca Knight for Sue minimum. Stay tuned for more of the cubes. Live coverage from Microsoft ignite.

>>live from Atlanta, Georgia. It's the Q covering answerable Best 2019. Brought to you by Red Hat >>Hey, welcome back, everyone. This is the Cubes. Live coverage here in Atlanta, Georgia, for Ansel Fast, part of Red Hats Annual event with their customers, their community. I'm Chon hurry with the Cuban stupid men. My co host. Our next guest is Jason Smith, vice president. North America Service is for Red Hat. Jason, welcome to the Cube. >>Thanks. Thanks for having me. >>So mostly the service is wrapped around this or huge opportunity because of the impact that the automation is having the tasks people's jobs shift on the things they can do, more things. That service is opportunity, bigot. You just take us through kind of your strategy of how you look at answerable in context of the red hat portfolio. >>Sure, yeah. So from the service's perspective, we're really responsible for ensuring customer success and sex successful adoption of all of our technologies. So across the entire portfolio and so as opposed to a service. This company that's focused on surfaces were really focused on driving customers success and making sure that customers were successful so overall, from the service's perspective we have obviously are consulting, which really focused on working with customers. Implement solutions around red technology is expanding the use of redhead technologies. We have our training business, which is our education and certification business, which has on sites, open enrollment. But also over the last couple years we released our Red Hat Learning subscription, which is basically gives customers access to the entire portfolio of training on demand in the self paced way, which is been really fast growing part of our business. And then I think we've talked to you a little bit about this before, which is our open innovation labs, which is really focused on people in process and helping customers go through that digital transformation type of journey and focus around culture and things like that. >>It's interesting you look at the interviews we had yesterday with some of your customers. It's actually have a couple different profiles. You have the man. We nailed it. Now I gotta bring us across the entire organization, get a champion driving change. Other groups are standardized with that substrate for answerable. Others were like, Wow, I have other stuff. I need to really figure this out, take us through how you guys would approach those use cases because they're different. But all would want more. Service is some to accelerate either, say a champion, some to get a new prospect on board. >>Right? So, um, we've laid out We'll release is about 90 days ago, which is called Dark Automation Adoption Journey. And this is a five phased approach where we've worked with customers hundreds of customers around the world, in every phase of adoption of automation, obviously specifically around answerable. And this really looks at helping customers go from more of a tactical strategy, typically is what we're seeing today. A lot of customers have and school in different pockets, doing a lot of tactical things that are driving a lot of value. But how do you take that? And then really get two more of an enterprise strategy? So that's really what we've focused on taking what we've learned with customers at all of those phases and really taking those best practices and coming up with a standardized approach that we can really work with customers to be ableto get through that journey with him. >>Jason could bring us inside the customer base a little here. You know, what we hear is it's really easy to get started. But when you lay out those five steps is everybody looking to get to st five? Is that a, you know, year journey? Are some people okay? Just being at phase two or three. Help us understand a little bit, Kind of. And we know it varies greatly, but some of the characteristics as toe how fast they move along where the end journey is for most organizations, >>right. So as I mentioned this, customers are coming in. Some have been early adopters of answerable for a long time. So we've been working at more of a department departmental level with customers where they're driving value at that departmental level. Others were kind of coming to us for the first time, saying we're hearing all about this automation stuff. We know we need it, but we need to get started. And so we're really looking at, um, kind of starting out. We typically start with the Discovery session, and so we're bringing in our architects and consultants to come in and meet with their business and technical stakeholders to really understand where they are in that journey and really defined kind of their goals and objectives. So every customer is different, so really understanding what their goals and priorities are and then being able to help kind of craft that road map with, um to get through that journey. But I'd say most of our customers looking to figure out how to take it from kind of more of those tactical implementations to how do we leverage that in a more scalable, consistent way and be able to manage it more across the enterprise? >>Well, it's a direct software development often is different at different, different parts in an organization. If you look a kind of a dev ops movement, it's, you know, trying to get a little bit consistency across those, and it sounds like answerable plays well, toe help get collaboration and you know those playbooks that could be used across and know that I have something that is supported and works, and my organization buys into it >>exactly. So a lot of customers air doing great things in those pockets. But like you said, how do you take those and not reinvent the wheel every time but take them and kind of break them down into consumable chunks, kind of validate those and then publish them. So you have a standard set of playbooks that people can use and reuse versus developing them again for the first time. Because we know that answerable. You can do things quickly, but you don't want to redo them 10 different ways to do the same thing. So having that kind of blessed standardized way and then publishing them out managing them is really important. >>Great feedback from customers on that two on. Then they get more playbooks to get more. I gotta manage that. But one of the interesting things we talked about yesterday with Stephanie Cheers with on the rail side was connecting, answerable to rail the insights. Was the analytics certainly compelling? A lot of benefits scare coming into the rest of red hat. Well, where is that opportunity? How do you guys servicing those pieces? >>Yes, so we're really looking at answerable to be part of most of the red hat portfolio. So as we're working with customers and they're adopting more and more of the Red Hat technologies, answerable becomes a bigger part of that. So whether it's kind of bringing in our training to help train and enable customer associates on using answerable not only for automation but whether you're a real admin or open shift, or no matter what kind of product you're using, being ableto have the training enablement and service is around that to help everyone learn to understand how to use an school in leverage danceable across any area of the plot. >>You guys aren't new to platforms. Answer would have been a great product. Now the platform approach, any things you guys are gonna do different is going to the same Red Hat playbook dealing with other platforms like Open shift in other things. You guys been successful with similar playbook for you guys, or what's the? Is there a nuance with the platform of sensible automation? Ours business as usual? >>Yes. From the service's perspective, we've tried to really standardize on a set of offerings, um, and leverage kind of a consistent approach, whether it's with open shift for helping customers adopt containers or helping customers build a hybrid cloud. Or we've even got a adoption journey around huts for Tokyo's the leverage to create an NFI architecture. It's the same kind of process and framework. So we try to build a standardized process and no matter kind of what type of solution customers air building We look to follow those types of >>dreams. Nice glue layer kind of fits everywhere on a personal question for you. What's the show been like here for you share with the people watching who weren't here? Why is this year important? This seems to be an inflection point for answerable fest, the vibe, the number of attendees, the moment in history where the cloud journey on premises What's What's your take on? This is your personal view. It's >>been great. I mean, I think just the size talking a lot of people that have been coming here for many, many years, even prior to the redhead acquisition of Answerable. This is really community driven event, and it's still set up like a community driven event. You won't see a big red hat stuff everywhere. It's really kind of by the community for the community. And just to see the sheer size of on the number of attendees here, and really kind of the evolution of what customers are being able to talk about on stage with a value they're getting out of answerable is pretty tremendous. So just seeing the pure return on investment of leveraging, answerable and looking at all of the large customers they're here, speaking even on the panel last night was really incredible to see them talk about their journeys over the last couple of years, going from just starting to be work with, answerable to really kind of driving that across the enterprise and getting continually >>local on feedback. But they're also vocal on success. They have all these building in champions inside your inside the customer base, >>and they're all very, very excited about when you have excited customers. >>So, Jason, I'm wonder if you could help us connect the dots with how automation ties into the other journeys customers are going through. You know, the digital transformation, modernizing their applications, changing their hybrid and cloud hybrid and multi cloud environment. What's the role of automation to, you know, enable that and participate in those journeys? >>Yes, it's and it really has kind of a part in all of those journeys. So we work with lots of large customers that are going through a kind of different parts of those different journeys, and it seems like ants will becomes a part of it. And so, for instance, one of our customers that working we're working with right now through a large digital transformation, kind of across the entire enterprise from a both people process and technology perspective on this is leveraging things like open shift and modernizing all of their applications and breaking down things in the micro Service's and really transforming their business. But part of that is leveraging, answerable. And so one of the CEOs mottoes was, If we do something more than twice, we're gonna automate it. And so I hear that kind of over and over again, no matter what type of customer we're working with, no matter what type of kind of solution we're implementing, they're coming up with these monsters that they get really excited about around automation. Um, so we're not going to do things the old way with these new projects. We wanna automate everything, and I just seeing a ton of value and efficiency out of it. >>Awesome. What's the biggest surprise that you've seen over the past year on the service aside and just in terms of enterprise readiness Enterprise and appetite. Adoption, Any observations you could share around what's going on with automation, Observe, ability, a big part of the business. We're seeing that, too. Automation Observe ability to hot new sectors. Just exploding opportunity. >>Yeah, I think just continuing to see this kind of digital transformation effort across so many different customers and get everybody's really focused on not only the technology and the technology, especially things like open shift in Ansel and Rail. They're enabling all of this change in all of this movement to the cloud and the automation, but really working with customers to focus on the people in process so they can leverage those capabilities because just adopting the platforms doesn't give you all of the benefits without changing your people in process. So we spent a lot of time talking about really around the culture, and customers are looking at us saying Red Hat Service's Don't just come in with the technical experts would help us really understand how we transform our people in process along the way to really take advantage of the innovation that's going around right now with the cloud. >>So, Jason, uh, IBM Zach Wizard Read had been very clear keeping the brand, the products, the people of Red Hat. IBM knows a thing or two about service is though we think that, you know, service is really are the main focus that that will happen there. So give us a little insight as to how the scale of IBM will increase what redhead service is able to be able to dio. >>Yeah, So it's great for Red Hat, right? Because we now have a company the size of IBM out driving the adoption of our technologies. So everything that we're able to dio to date from a red hat perspective got us to one level of scale. But IBM is gonna take us to that next level of scale. And from a service's perspective, IBM already has service's departments around all of their different technologies. And so we really are gonna be treated kind of service department. So we're gonna continue to be the experts around Red Hat Technologies. But it really doesn't change that much for us because we worked with large s eyes. Um, since the time we started here and were always part of a lot of largess, I implementations so although IBM will be a very important partner of ours. They won't be on. The other part of the only partner will still work with all >>the flights. IBM That's right. And so we worked at >>IBM before the acquisition as a partner will work with him after the acquisition. But IBM What will change is on the IBM side, they will be building much larger delivery organizations around Red Hat Technologies, which will allow us to kind of get the the customer started on that journey. But when they look to really scale out than IBM can take in and kind of take that to the next level, that we would never have the scale to be able to get to that side. So it's good for us. It's good for our customers, and it's good for red hat driving adoption. >>Jim pointed this out on the many times on multiple calls around the broad portfolio. You guys have an IBM. They have somewhere broad portfolio. Thanks for coming on, sharing your insights. What's new for you? Take a quick minute to plug in what's going on your organization and what you're up to? >>Yes, So we're just continuing to scale. So, um The good news is IBM has a large service's organization, but that also drives a lot of demand for us. So we're continuing to scale, will continue to improve. Our offerings were continuing to help our customers reach those goals, moving to the cloud and everything they're looking to try to accomplish. >>Great. Thanks for coming. I appreciate it to Cuba. Coverage here. Danceable fast. I'm John for a student. Stay with us. More day, too. Live coverage after this short break.

>> Narrator: Live from San Francisco celebrating 10 years of high tech coverage, It's the Cube! Covering VM World 2019 Brought to you by VMware and its ecosystem partners >> Hello everyone and welcome to the Cube's coverage here in San Francisco, California of the VMWorld 2019. I'm John Furrier with my cohost Dave Vellante Dave, 10 years covering VMWorld since 2010, it's been quite a ride, lot of changes. >> Dave: Sure has. >> John: We're going to do a Power Panel our format we normally do it remote guests in our Palo Alto and Boston studios in person because we're here. Why not do it? Of course, Keith Townsend, CTO Advisor friend of the Cube, Cube host sometimes and Sarbjeet Johal, cloud architect cloud expert, friends on Twitter. We're always jammin' on Twitter. So we'll have to take it to the video. Guys, thanks for joining us on the Power Panel. >> Good to see you, Gents. >> Good seein' ya. >> Good to be here. >> Yeah, I, I hope we don't come to blows, Sarbjeet. I mean we've had some passionate conversations over the past couple months. >> Yeah, Santoro, yes, yes. >> John: The activity has been at an all time high. I mean, snark aside, there's real things to talk about. >> Yes. >> I mean we are talking about VMware a software company, staying with their roots. We know what happened in 2016 The Amazon relationship cleared the air so to speak, pun intended. Vcloud air kind of goes it's way stock prices go up and to the right Yeah, fluctuations happening but still financially doing well. >> Keith: Yeah. >> Customers have clarity. They're an operate. They run, they target operators not developers. We're living in a DevOps world we talk about this all the time dev and ops this is the cloud world that they want Michael Dell was on the Cube Dell Technologies owns VMware they put Pivotal on VMware moves are being made. Keith, how do you make sense of it? What's your take? You've been on the inside. >> Well, you know, VMware has a tough time. Pat came in, 2013, we remember it. He said we are going to double down on virtualization. He is literally paying the cost for that hockey stick movement VMware has had this reputation of being an operator based company Infrastructure based, you go into accounts, you're stuck in this IT Infrastructure cells movement. VMware has done awesome over the past year. Few years, I had to eat a little crow and say that the move to eject Pivotal was the right thing for the Stock but for the reputation, VMware is stuck so Pat, what, tallied up 5 billion dollars in sales, in purchases last week to get out of this motion of being stuck in the IT Infrastructure realm Will it pay off? I think it's going to be a good conversation because they're going to need those Pivotal guys to push this PKS vision of theirs. This PKS and Kubernetes vision that they have >> Well they got to figure it out but certainly it's a software world and one of the things that's interesting we were talking before we started is, they are stuck in that operator world but it's part of DevOps, Dev and Ops. This is the world that they operate in Google's cloud shows how to do it. You got SRE's run things and developers this program infrastructure is code. This is the promise of this new generation. Sarbjeet, we talk about it all the time on Twitter developers coding away not dealing with the infrastructure, that's the goal >> Yeah, traditionally, developers never sort of mucked around with infrastructure. Gradually we are moving into where developers have to take care of infrastructure themselves the teams are like two person teams we hear that all the time. They are responsible for running the show from beginning to the end. Operations are under them, it's Dev and Ops are put together, right? But I'll speak from my own personal experience with working at VMware in the past that from all the companies which are operations focused, that's HP, IBM, and Oracle to a certain extent. So portfolio and all that. And BMC, and CA, those are pure companies in the operations space, right? I think VMware is one of those which values software a lot. So it's a purely, inside the VMware it's purely software driven. But to the outside, what they produce what they have produced in the past that's all operations, right? So I think they can move that switch because of the culture and then with Pivotal acquisition I think it will make it much easier because there's some following of the Pivotal stack, if you will the only caveat I think on that side is it is kind of a little bit of interlocking-ish, right? That is one of the fears I have. >> Who's not, even RedHat these days is, locking you in. >> Yeah, you know, I pulled some interesting stat metadata from a blog post from Paul Fazzone announcing the Pivotal acquisition. He mentioned Kubernetes 22 times. He mentioned Pivotal Cloud Foundry once. So VMware is all in on this open-shift type movement I think VMware is looking at the Red shift I mean Red OpenShift acquisition by IBM and thinking, "Man, I wish we didn't have this "Sense of relationship with Pivotal "So we could have went out and bought RedHat." >> Well that's a good point about Kubernetes, I think you're right on that. And remember, we've been covering Open Stack up until about a year ago, and they changed the name it's now something else, but I remember when Open Shift wasn't doing well. >> Keith: I do too! >> And what really was a tipping point for them was they had all the elements, but it was Kubernetes that really put them in a position to take advantage of what they were trying to do and I think you're right, I think VMware sees that, now that IBM owns RedHat and Open Shift, it's clear. But I think the vSphere deal with Project Pacific points out that they want to use Kubernetes as a distraction layer for developers, and have a developer interface to vSphere. So they get the operators with vSphere, they put Kubernetes in there and they say, "Hey developers, use us." Now I think that's a hedge also against Pivotal 'cause if that horse doesn't come across the track to the finish line, you know... >> It's definitely a hedge on Containers just a finer point of what you were saying there was a slight difference in the cash outlay for RedHat, 34 billion versus the cash outlay for Pivotal was 800 million. So they picked up an 800 million dollar asset or a 4 billion dollar asset for 2.7 billion. >> Hold on, explain that because 2.7 billion was the number we reported you're saying that VMware put out only 800 million in cash, which, what's that mean? >> That's correct. So they put out 800 million in cash to the existing shareholders of Pivotal, which is a minority of the shareholders. Michael Dell owns 70% of it, VMware owns 15% of it. So they take the public shareholders get the 800 million >> John: They get taken out, yep. >> Michael Dell gets more VMware stock, so now he owns more of VMware. VMware already owns 15% of Pivotal, so for 800 million, they get Pivotal. >> So, the VMware independent shareholders get... they get diluted. >> Right. >> Did they lose out in the deal is the question and I think the thing that most people are missing in this conversation is that Pivotal has a army of developers. Regardless of whether developers focus on PCF or Kubernetes is irrelevant. VMware has a army, a services army now that they can point towards the industry and say, "We have the chops to have "The conversation around why you should "Come to us for developing." >> So I want to come back to that but just, a good question is, Do the VMware shareholders get screwed? Near term, the stock drops, right? Which is what happens, right? Pivotal was up 77% on the day that the Dow dropped 800 points. Here's where I think it makes sense, and there are some external risks. Pivotal plus Carbon Black, the combination they shelled out 2.7 billion in cash. They're going to add a billion dollars to VMware's subscription business next year. VMware trades at 5x revenue multiple, so the shareholders will, in theory, get back 5 billion. In year two, it's going to be 3 billion that they're going to add to the subscription revenue so in theory, that's 15 billion of value added. I think that goes into the thinking, so, now, are people going to flock to VMware? Are Kubernetes developers going to flock to VMware? I mean to your point, that to me, that's the value of Pivotal is they can get VMware into the developer community. 'Cause where is VMware with developers? Nobody, no developers in this audience. >> That's true. >> What are your guys' thoughts on that? >> Yeah, I think that we have to dissect the workload of applications at the enterprise level, right? There are a variety of applications, right, from SAPs Oracles of the world those are two heavyweights in the application space. And then there's a long trail of ISVs, right. And then there's homegrown applications I think where Pivotal plays a big role is the homegrown applications. When you're shipping a lot as an ISV or within your enterprise, you're writing software you're shipping applications to the user base. It could be internal for partners, for customers, right, I think that's where Pivotal plays Pivotal is pivotal, if you will. >> I think that's a good bet too, one of the things we've been pulling the CESoEs data for when we got reinforced we started pulling CESoEs in our network, and it's interesting. They're under the gun to produce security solutions and manage the vendors and do all that stuff they're all telling us, the majority of them are telling us that they're building their own stacks internally to handle the crisis and the challenge of security, which I think's a leading indicator versus the kind of slow, slower CIO which LOVES multi-anything. Multi-vendor, control, a deal with contracts CESoEs, they don't have the DOGMA because they can't have the DOGMA. They got to deliver and they're saying, "We're going to build a stack "On one cloud. "Have a backup cloud, "I want all my developer resources "On this cloud, not fork my team "And I'm going to build a stack "And then I'm going to ship APIs "And say to my suppliers, in the RFP process, "If you support these APIs, "You could do business with us." >> Keith: So, if you don't -- >> That's kind of a cutting edge. If you don't, you can't, you can't. And that's the new normal. We're seeing it with the Jedi deal with Oracle not getting, playing 'cause they're not certified at the level that Amazon is, and you're going to start to see these new requirements emerging this is a huge point. I think that's where Pivotal could really shine not being the, quote, developer channel for VMware. I think it's more of really writing apps >> And John, I think people aren't even going to question that model. Capital One is probably the poster child for that model they actually went out and acquired a start-up, a security, a container security start up, integrated them into their operations and they still failed. Security in the cloud is hard. I think we'll get into a multi-cloud discussion this is one of the reasons why I'm not a big fan of multi-cloud from an architecture perspective, but from a practical challenge, security is one of the number one challenges. >> That's a great point on Capital One in fact, that's a great example. In fact, I love to argue this point. On Twitter, I was heavily arguing this point which is, yeah, they had a breach. But that was a very low-level it's like the equivalent of a S3 bucket not being configured, right? I mean it was so trivial of a problem but still, it takes one whole-- (hearty laughing) One, one entry point for malware to get in. One entry point to get into any network where it's IOT This is the huge challenge. So the question there is, automation. Do you do the, so, again, these are the, that's a solvable problem with Capital One. What we don't know is, what has Capital One done that we don't know that they've solved? So, again, I look at that breech as pretty, obviously, major, but it was a freakin' misconfigured firewall. >> So, come back to your comments on multi-cloud. I'm inferring from what you said, and I'd love to get your opinion, Sarbjeet. That multi-cloud is not an architectural strategy. I've said this. It's kind of a symptom of multiple vendors playing but so, can multi-cloud become, because certainly VMware IBM RedHat, Google with Anthos, maybe a little bit less Microsoft but those three-- >> Dell Technologies. >> Cisco, Cisco and certainly Dell all talking about multi-cloud is the clear strategy that's where CIOs are going, you're not buying it. Will it ever become a clear strategy from an architectural standpoint? >> Multi-cloud is the NSX and I don't mean NSX in VMware NSX it's the Acura NSX of enterprise IT. The idea of owning the NSX is great it brings me into the showroom, but I am going to buy, I'm going to go over to the Honda side or I'm going to go buy the MDX or something more reasonable. Multi-cloud, the idea, sure it's possible. It's possible for me to own a NSX sports car. But it's more practical for me to be able to shop around I can go to Google via cloud simple I mean I can go via cloud simple to Azure, GCP or I can go BMC, I have options to where I land, but to say that I am going to operate across all three? That's the NSX. >> If you had a NSX sports car, by the way, to use the analogy in my mind is great one, the roads aren't open yet. So, yeah, okay great. (hearty laughing) >> Or you go to Germany and you're in California. So, the transport, and again in the applications you could build tech for good applications all you want, and they're talking about tech for good here but if it's insecure, those apps are going to create more entry points. Again, for cyber threats, for malware, so again, the security equation, and you're right is super important, and they don't have it. >> Dave: What's your thought on all (mumble)? >> Sarbjeet: I think on multi-cloud you are, when you are going to use multi-cloud you going to expand the threat surface if you will 'cause you're putting stuff at different places. But I don't think it, like as you said Dave, the multi-cloud is not more of an architectural choice, it's more like a risk mitigation strategy from the vendor point of view. Like, Amazon, who they don't compete with or who they won't compete with in the future we don't know, right? So... >> You mean within the industry. >> Yeah, within the industry right-- >> Autos or healthcare or... >> Sarbjeet: Yeah, they will, they are talking about that, right? So if you put all, all sort of all your bets on that or Azure, let's say even Azure, right? They are not in that kind of category, but still if you go with one vendor, and that's mission critical and something happens like government breaks them up or they go under, sideways, whatever, right? And then your business is stuck with them and another thing is that the whole US business, if you think about it at a global scale, like where US stands and all that stuff and even global companies are using these hourglass providers based in US, these companies are becoming like they're becoming too big to fail, right? If you put everything on one company, right, and then something happens will we bail them out? Right, will the government bail them out? Like stuff like that. Like banks became too big to fail, I think. I think from that point of view, bigger companies will shift to multi-cloud for, to hedge, right, >> Risk Mitigation >> Risk mitigation. >> Yeah, that's, okay, that's fair. >> I mean, I believe in multi-cloud in one definition only. I think, for now, the nirvana of having different workload management across utility bases, that's fantasy. >> Keith: Yeah, that's fantasy. >> I think you could probably engineer it, but there might not be a workload for that or maybe data analytics I could see moving around as a use case, certainly, but I think-- >> D-R! >> The reality is, is that all companies will probably have multiple clouds, clearly like, if you're going to run Office 365, and it's going to be on Azure, you're an Azure customer, okay. You have Azure cloud. If you're building your security stack on Amazon, and got a development team, you're on Amazon. You got two clouds. You add Google in there, big tables, great for certain things you know, Big Query, you got Google. You might even have Alibaba if you're operating in China So, again, you going to have multiple clouds the question is, the workloads define cloud selection. So, I've been on this thing, if you got a workload, an app, that app should choose its best infrastructure possible that maximizes what the outcome is. >> And John, I think what people fail to realize, that users, when you give them a set of tools, they're going to do what users do, which is, be productive. Just like users went out and took credit cards swiped it and got Amazon. If you, if in your environment you have Amazon you have GCP, you have Azure, you have Salesforce, O-365, and a user has access to all five platforms, whether or not you built a multi-cloud application a user's going to find a way to get their work done with all five, and you're going to have multi-cloud fallout because users will build data sets and workloads across that, even if IT isn't the one that designed it. >> All right, guys, final question of the Power Panel Dave, I want to include this for you too, and I'll weigh in as well. Take a minute to share what you're thinking right now is on the industry. What's taking up your attention? What's dominating your Twittershpere right now? What's the bee in your bonnet? What's the hot-button issue that you're kicking the tires on, learning about, or promoting? Sarbjeet, we'll start with you. What's on top of the mind for you these days? >> I think with talk about multi-cloud all the time, that's in discussions all the time and then Blockchain is another like slow-moving train, if you will, I think it's arriving now, and we will see some solutions coming down the pike from different, like a platformization of the Blockchain, if you will, that's happening, I think those are two actually things I keep my eyes on and how developers going to move, which side to take and then how the AWSs dominance is challenged by Microsoft and Google there's one thing I usually talk about on Twittersphere, is that there's a data gravity and there's a scales gravity, right? So people who are getting trained on Amazon, they will tend to stay with them 'cause that's, at the end of the day, it's people using technology, right? So, moving from one to another is a challenge. Whoever throws in a lot of education at the developers and operators, they will win. >> Keith, what are you gettin' excited about? >> So, CTO advisor has this theory about the data framework, or data infrastructure. Multi-cloud is the conversation about workloads going here, there, irrelevant, it's all about the data. How do I have a consistent data policy? A data protection policy, data management policy across SAS, O-365, Sales Force Workday, my IAF providers, my PATH providers, and OMPRIM, how do I move that data and make sure another data management backup company won Best of VMWorld this year. This is like the third or fourth year and a reason it's not because of backup. It's because CIOs, CDOs are concerned about this data challenge, and as much as we want to talk about multi-cloud, I think well, the industry will discover the problem isn't in Kubernetes the solution isn't in Kubernetes it's going to be one of these cool start-ups or one of these legacy vendors such as NetAp, Dell, EMC that solves that data management layer. >> All right, great stuff. My hot button is cloud 2.0 as everyone knows, I think there's new requirements that are coming out, and what got my attention is this enterprise action of VMware, the CIA deal at Amazon, the Jedi deal show that there are new requirements that our customers are driving that the vendors don't have, and that's a function that cloud providers are going to provide, and I think that's that's the canary in the coal mine. >> I've got to chime in. I've got to chime in. Sorry, Lenard, but it's the combination what excites me is the combination of data plus machine intelligence and cloud scale. A new scenario of disruption moving beyond a remote set of cloud services to a ubiquitous set of digital services powered by data that are going to disrupt every industry. That's what I get excited about. >> Guys, great Power Panel. We'll pick this up online. We'll actually get the Power Panels working out of our Palo Alto studio. If you haven't seen the Power Panels, check them out. Search Power Panels the Cube on Google, you'll see the videos. We talk about an issue, we get experts it's an editorial product. You'll see more of that online. More coverage here at VMWorld 2019 after this short break. (lively techno music)