(upbeat music) >> Hello, welcome back to the Cookie Conundrum, A Recipe For Success an industry conference and summit from Quancast on the demise of third-party cookies. We've got a great industry panel here to break it down. Chris Guenther, senior vice president global head of Programmatic at News Corp. Chris, thanks for coming on. Xiao Lin, managing director solutions at Xaxis, and Somer Simpson, vice president of product at Quancast stellar panel. Looking forward to this conversation. Thanks for coming on and chatting about the cookie conundrum. >> Thank you for having us. >> So, Chris, we'll start with you at News Corp obviously major publisher. Deprecation of third-party cookies affects everyone. You guys have a ton of traffic, ton of audience across multiple formats. Tell us about the impact to you guys and the reliance you guys had on them. And what are you going to do to prepare for this next level change? >> Sure. I mean, I think like everyone in this industry there is a, you know, a significant reliance and I think it's something that a lot talk about audience targeting, but obviously they realize that third party cookies pervasive across the whole ad tech ecosystem, MarTech stack. And so, you know, we have to think about, you know how that impact, you know, our vendor the vendors we work with, what it means in terms of our use cases across marketing, across advertising across site experience. So, you know, without a doubt, it's significant. But you know, we look at it as listen. It's disruptive in disruption and change is always a little scary, but overall it's a it's a long overdue reset. I mean, I think that, you know, our perspective is that the the cookies, as we all know, is it was a crutch, right? It's sort of a technology being used in way it shouldn't. And so, as we look at what's going to happen presumably after Jan 2022, then it's a good way to kind of fix on some bad practices practices that lead to data, leakage, practice sort of devalued for our perspective. Some of the, you know, we offered as, as publishers. And I think that this is a key thing is that we're not just looking to as we look through post gen world, not just kind of recreating the prior world. Because the prior world was flawed or I guess I could say the current world since it hasn't changed yet. But the current world is flawed. Let's not just replicate that. You know, let's make sure that third party cookies goes away other work around like fingerprinting and things like that, you know, also go away. So, you know, philosophically that's where our head's at. And so, you know, as we look at how we are preparing you look at sort of what are the core building blocks of preparing for this world. Obviously one of the key ones is privacy compliance. Like how do we treat our users with consent? You know, obviously are we aligned with the regulatory environments? You know, in some ways we're not looking just to Jan 2022 but Jan 2023, where there's going to be the majority of our audiences, we covered by regulation. And so I think from regulation up to data gathering, to data activation, all built around an internal identifier that we've developed that allows us to have a a consistent look at our user is whether they're logged in or obviously, anonymous. So it's really looking across all those components, across all our sites, and all in a privacy compliant way. So a lot of work to be done, a lot of work in progress but you know, we're excited about what's going on. >> I like how you framed it, you know, old world or next gen kind of the current situation is kind of flawed. And as you think about Programmatic, the concept is mind blowing and what needs to be done. So we'll come back to that because I think that original content view is certainly relevant. It's a huge investment, and you've got great content and audience consuming it. Xiao, from a major media standpoint get your perspective on the impact because you've got clients who want to get their message out in front of the audience at the right time, at the right place and the right context. Right? So yeah, privacy, you got consent and all of these things kind of boiling up how do you help clients prepare? Because now they can go direct to the consumer. You know, everyone, everyone has a megaphone now everyone's you know, everyone's here, everyone's connected. So how are you impacted by this new notion? >> You know, if the cookieless future was a tik tok dance, we'd be dancing right now and at least until the next year. This has been top of mind for us and our clients for quite some time. But I think as each day passes the picture becomes clearer and more in focus. The end of the third party cookie does not mean the end of Programmatic. So clients work with us in transforming their investments into real business outcomes based on our expertise and based on our tech. So we continue to be in a great position to lead, to educate, to partner, and to grow with them along this cookieless future. The impact will be all encompassing in changing the ways we do things now and also accelerating the things that we've already been building on. So we take it from the top. Planning will have a huge impact because it's going to start becoming more strategic around real business outcomes. We're omni-channel. So clients wants to drive outcomes through multiple touch points of a consumer's journey. Whether that's programmatic, whether that's as a cookie free environment like connected TV, out of home, audio, gaming, and so forth. So we're going to see more of these strategic holistic plans. Creative will have a lot of impact. It will start becoming more important with Creative testing, Creative insights, you know, Creative in itself is cookieless. So there will be more focus on how to drive a brand dialogue, to connect to consumers with less targeting, with less cookies. With the cohesiveness of holistic planning, Creative can align through multiple channels. And lastly, the role of AI will become increasingly important. You know, we've always looked to build our tech, our products, to compliment new and existing technology as well as the client's own data and tech stack to deliver these outcomes for them. And AI in its core is just taking inputted data and having an output of your desired outcomes. So input data could be DSP data beyond cookies such as browser, such as location, such as contextual, a publisher taking client's first party data, first party CRM data like store visitation sales site activity. And using that to optimize in real time regardless of what vendor or what channel we're on. So as we're learning more about this cookieless dance, we're helping our clients on the steps of it, and also introducing our own moves. >> That's awesome. Data is going to be a key value proposition, you know connecting in with content real time. Great stuff. Somer, with your background in journalism and you're the tech VP of product at Quancast. You have the keys to the kingdom over there. It's interesting, journalism is about truth you know, good content, original content. But now you have a data challenge, problem, opportunity on both sides, brands and publishers coming together. This is a data problem in a way. It's a tech stack, not so much just, you know getting the right ads to show up at the right place, the right time. It's really bigger than that now. What's your take on this? >> You know, I, so first I think that consumers already sort of accept that there is a reasonable value exchange, you know, for their data, in order to access free content. Right? And that's a critical piece for us to all kind of understand. Over the past. Yeah, probably two years, since even before the GDPR, we've been doing a ton of discovery with customers, both publishers and marketers. And so, you know, we kind of known this this cookie going away thing is, has been coming and you know, Google's announcement just kind of confirmed it. And it's been really really interesting since Google's announcement how the conversations have changed with our customers and other folks that we talk to. And I've almost gone from being like a product manager to a therapist because there's such an emotional response. From the marketer perspective, there's real fear there. There's like, Oh my God, how you know, it's not just about delivering ads. It's about how do I control frequency? How do I measure, you know, success? You know, because the technology has grown so much over the years to really give marketers the ability to deliver personalized, you know, advertising good content to consumers and be able to monitor it and control it so that it's not too, too intrusive. On the publisher perspective side, we see a slightly different response. It's more of a yes. Right? You know, we're taking back control and we're going to stop the data leakage. We're going to get the value back for our inventory. Both things are a good thing. But if it's not managed, it's going to be like ships passing in the night. Right? In terms of, you know, them coming together. Right? And that's the critical pieces that they have to come together. They have to get closer. You got to cut out a lot of like that LUMAscape in the middle so that they can talk to each other and understand what's the value exchange happening between marketers and publishers and how do we do that without cookies? >> Yeah. It's a fascinating, I love your insight there. I think it's so relevant. And it's got broader implications because, you know, if you look at how data is impacting some of these big structural changes and refactoring of industries look at cybersecurity, you know no one wants to share their data but now if they share, they get more insight more machine learning, benefit, more AI benefit. So now we have the sharing notion but that goes against counter the big guys that want a walled garden. They want to hoard all the data and control that to provide their own personalization. So you have this confluence of, hey I want to hoard the data and then now I want to share the data. So Chris and Homer, in the wheelhouse you've got original content and there's other providers out there. So is there the sharing model coming? with privacy and these kinds of services is the open come back again? How do you guys see this? The confluence of open versus walled gardens. Because you need the data to make machine learning good. >> I'll start off. I mean, listen, I think you have to give credit to the walled gardens I've created. And I think as we look as publishers, what are we offering to our clients? What are we offering to the buy-side? We need to be compelling. We shouldn't just be, obviously, as journalists I think that there is a case of, you know the importance of funding journalism. But ultimately we need to make sure we're meeting the the KPIs and the business needs of the buy-side. And I think around that, it is, you know there's sort of three core pillars to that. It's ease of access, it's scope of activation and targeting, and finally, measurable results. So as I think, as us, as an individual publisher of so we have multiple publications so we do have scale, but then in partnership with other publishers perhaps organizations like Prebid, you know I think we can, we're trying to address that. And I think we can offer something that's compelling and transparent in terms of what these results are. But obviously, you know, I want to make sure it's clear that transparent terms of results, but obviously where there's privacy in terms of the data. And I I think we've all heard about like data clean rooms, a lot of them out there flogging those wares. And I think there's something valuable, but you know I think it's who is sort of the right partner or partners, and ultimately who allows us to get as close as possible to the buy side. And so that we can share that data for targeting shared for perhaps for measurement, but obviously all in a privacy compliant way. >> Somer, what's your take on this? Because you talk about the future of the open internet democratization. The network effect that we're seeing in virality and across multiple omni-channels as Xiao pointed out, it's happening. That's the distribution now. So that's almost an open garden model. So it's like >> Yeah. And yeah, it's, it's, you know back in the day, you know, Nightrider who was the first group that I, that I worked for, you know each of those individual properties were not hugely valuable on their own from a digital perspective. but together as a unit, they became valuable. Right. And got a scale for advertisers. Now we're in a place where, you know, I kind of think that each of those big networks are going to have to come together and work together to compare in size to the, to the walled gardens. And yeah, this is something that we've talked about before, an open garden. I think that's the definitely the right route to take. And I agree with Chris. It's about publishers getting as close to the marketers as possible, working with the tech companies that enable them to do that, and doing so in a very privacy centric way. >> Xiao how do we bring the brands and agencies together to get ready for third-party cookies? Because there is a therapist moment here of it's going to be okay, the parachute will open. The future is not going to be as grim. It's a real opportunity, but if managed properly. What's your take on this? Is it just more first party data strategy? And what's your assessment of this? >> So we're collaborating right now with ball grants on how to distill very complex cookieless future you know, what's going to happen in the future. To six steps that we can take right now and marketers should take. The first step is gather Intel on what's working on your current campaign analyzing the data sets across cookie free environment. So you can translate those tactics eventually when the cookies do go away. So we have to look at things like temporal or time analysis. We can look at log level data. We can look at site analytics data. We can look at brand measurement tools and how Creative really impacts the campaign success. The second thing we can look at is geo-targeting strategies. The geo-targeting strategy has been underrated because the granularity and DL data could go down all the way to the local level, even beyond zip code. So for example, the census block data. And this is especially important for CPG brands. So we're working closely with the client teams to understand not only the online data, but the offline data and how we can utilize that in the future. We want to optimize investments around markets that are working, so strong markets, and then test in underperforming markets. The third thing we can look at is contextual. So contextual by itself is cookie free. We could build on small-scale usage to test and learn various keywords and content categories based sets, working closely with partners to find ways to leverage their data, to mimic audiences that you are trying to target right now with cookies. The fourth one is publisher data or publisher targeting. So working with your publishers that you have strong relationships with who can curate similar audiences using their own first party data and conducting RFIs to understand the scale and reach against your audience and your future roadmap. So work with your top publishers based on historical data to try to recreate your best strategies. The fifth thing, and I think this is very important, is first party data. That's going to matter more than ever in the cookieless future. Brands will need to think about how to access and develop the first party data starting with the consumer, seeing of value in exchange for the information it's a goldmine and understanding your consumer their intent, their journey. And you need a really great data sciences team to extract insights out of that data, which will be crucial. So partner with strategic onboarding vendors and vet their ability to accept first party data into a clean room environment for targeting, for modeling, for insights. And lastly, the sixth thing that we can do is begin inform prospecting by dedicating test budget to start gaining learnings about cookieless. One, one place that we can start, and it is under invested right now, is Safari and Firefox. They have been cookieless for quite some time. So you can start here and begin testing here. Work with your data scientist team to understand the right mixes to target and start exploring other channels outside of just programmatic cookies. Like CTV, digit auto home, radio, gaming, and so forth. So those are the six steps that we're taking right now with our clients to prepare and plan for the cookieless future. >> So, Chris, let's go back to you. What's the solution here? Is there one, is there multiple solutions? What's the future look like for a cookieless future? >> I think the one certain answer is there definitely is not just one solution. As we all know right now, there seems to be endless solutions, a lot of ideas out there, proposals when the W3C, work happening within other industry bodies, you know, private company solutions being offered. And you know, it's a little bit, it's enough to make everyone's head spin and to try to track it to understand it and understand the impact. And as a publisher, we're obviously, you know, a lot of people are knocking on our door, you know they're saying, hey, our solution is one that it's going to bring in lots of money. You know, all the buy-side is going to use it. This is the one like unlock all the spend. And it's our experience so far is that none of these solutions are, cause I think everyone's still testing and learning. No one on the buy side from our, from our knowledge is really committed to one or a few. It's all about a testing stage. I think that, you know, putting aside all that noise I think what matters the most to us as publishers, actually something Somer mentioned before. It's about control. You know, if we're going to work with a, you know, again outside of our sort of independent internal identifier work that we're doing, if we're going to work with an outside party or an outside approach, does it give us control >> As a publisher to ensure that it is, you know we control the, the data from our users, you know there isn't that data leakage, it's privacy compliant. You know, what information gets shared out there? What is it what's released within, you know within the bitstream? If it is something that's attached to a, someone, a declared user, a registered user that if that then is not somehow amplified or leverage off in another site in a way that is leveraging bit stream data or fingerprinting and going again. And so I think that the spirit of what we're trying to do in a post third party cookie world. And so those controls are critical. And I think to have those controls as publisher we have to be collectively be disciplined. And you know, what solutions that we sort of we test out and what we eventually adopt. But even when that adoption point arrives it definitely will not be one. There will be multiple because there's just too many cases to address. >> Great, great insight there from you guys at News Corp. Somer, let's get back to you. I want to get your thoughts. You've been in many waves of innovation, ups and downs. We're on a new one now. We talked about the open internet and democratization. Journalism is under a lot of pressure now but there's now a wave of quality people, really leaning in towards fighting misinformation, understanding truth and community and data is at the heart of it. What do you see as the new future for journalists to reward journalism? Is there a way, is there a path forward? >> So there's what I hope is going to happen. And then I'm just going to ignore what could, right. You know, there's a trend in market right now at a number of fronts, right? So there are marketers who are leaning in to wanting to spend their marketing dollars with quality journalists, focusing on BiPAC owned and operated, really leaning into supporting those businesses that have been and those publishers that have been ignored for years. I really hope that this trend continues. We are leaning into helping marketers curate that supply, right. And, and really, you know, speak with their dollars about the things that they support and value in market. So I'm hoping that that trend continues. And it's not just sort of like a marketing blip but we will do everything possible to kind of encourage that behavior and give people the information that they need to find. You know, truly high quality journalism. >> That's awesome. Chris, Xiao, Somer, thanks for coming on and sharing your insight on this panel on the cookieless future. Before we go, just quick summary, each of you if you don't mind just giving a quick sound bite or bumper sticker of what we can expect. If you had to throw a prediction for what's going to happen in the next 24 months. Chris, we'll start with you. >> It's going to be quite a ride. I think that's an understatement. I think that there, I wouldn't be surprised if if Google delays the change to the Chrome by a couple months. And may give the industry some much needed time. But no one knows, I guess, I guess I'm not except for someone somewhere, we are deep within Chrome. So I think we all have to operate in a way that changes that happen, changes that happen quickly. And it's going to cover across all facets of the industry, all facets of, you know, from advertising and marketing. So just be prepared. >> Okay. Xiao. Along those same lines, be prepared. Nobody knows what's going to happen in the future. You know, we're all dancing in this together. I think for us, it's planning and preparing and also building on what we've already been working on. So omni-channel, AI, Creative, and I think clients will lean more into those different channels. >> Awesome. Somer, take us home. Last words. >> I think we're in the throwing spaghetti against the wall stage, right? So this is a time of discovery of leaning and trying everything out learning and iterating as fast as we possibly can. >> Awesome. And I love the cat in the background over your shoulder. I can't stop staring at your wonderful cat. Somer, thanks for coming on. Xiao, Chris, thanks for coming on this awesome panel industry breakdown of the Cookie Conundrum, a Recipe for Success data AI open the future is here. It's coming. It's coming fast. I'm John Furrier with theCUBE. Thanks for watching.

(upbeat music) >> Announcer: From the keeps studios in Palo Alto in Boston, connecting with that leaders all around the world. This is theCube conversation. >> Welcome to theCube conversation here in Palo Alto, California. I'm John Furrier, host of theCube. With a special content series called, Leading with observability, and this topic is, Keeping watch over microservices and containers. With great guests, Patrick Lin, VP of Product Management for the observability product at Splunk. Patrick, great to see you. Thanks for coming on remotely. We're still in the pandemic, but thanks for coming on. >> Yeah, John, great to see you as well. Thanks for having me. >> So, leading with observability is a big theme of our content series. Managing end to end and user experience is a great topic around how data can be used for user experience. But now underneath that layer, you have this whole craziness of the rise of the container generation, where containers are actually going mainstream. And Gardner will forecast anywhere from 30 to 40 percent of enterprises still yet, haven't really adopted at full scale and you've got to keep watch over these. So, what is the topic about keeping watch over microservice and containers, because, yeah, we know they're being deployed. Is it just watching them for watching sake or is there a specific reason? What's the theme here? Why this topic? >> Yeah, well, I think containers are part of the entire kind of stack of technology that's being deployed in order to develop and ship software more quickly. And, the fundamental reasons for that haven't changed but they've been greatly accelerated by the impact of the pandemic. And so I think for the past few years we've been talking about how software's eating the world, how it's become more and more important that company go through the transformation to be more digital. And I think now that is so patently obvious to everybody. When your only way of accessing your customer and for the customer to access your services is through a digital media. The ability for your IT and DevOps teams to be able to deliver against those requirements, to deliver that flawless customer experience, to sort of keep pace with it the digital transformation and the cloud initiatives. All of that is kind of coming as one big wave. And so, we see a lot of organizations migrating workloads to the cloud, refactoring applications, building new applications natively. And so, when they do that oftentimes the infrastructure of choice is containers. Because it's the thing that keeps up with the pace of the development. It's a much more efficient use of underlying resources. So it's all kind of part of the overall movement that we see. >> What is the main driver for this use case microservices and where's the progress bar in your mind of the adoption and deployment of microservices, and what is the critical things that are there you guys are looking at that are important to monitor and observe and keep track of? Is it the status of the microservices? Is it the fact that they're being turned on and off, the state, non-state, I mean take us through some of the main drivers for why you guys are keeping an eye on the microservices component? >> Sure, well, I think that if we take a step back the reason that people have moved towards microservices and containers fundamentally has to do with the desire to be able to, number one, develop and ship more quickly. And so if you can parallelize the development have API is the interface between these services rather than having sort of one monolithic code base, you can evolve more quickly. And on top of that, the goal is to be able to deliver software that is able to scale as needed. And so, that is a part of the equation as well. So when you sort of look at at this the desire to be able to iterate on your software and services more quickly, to be able to scale infinitely, staying up and so on. That's all like a great reason to do it, but what happens along those lines, what comes with it is a few kind of additional layers of complexity because now rather than have, let's say an end to your app that you're watching over on some hosts that you could reboot when there's a problem. Now you have 10's, maybe 100's of services running on top of maybe 100,000's, maybe 10,000's of containers. And so the complexity of that environment has grown quite quickly. And the fact that those containers may go away as you are scale the service up and down to meet demand also adds to that complexity. And so from an observability perspective, what you need to be able to do is a few things. One is you need to actually be tracking this in enough detail and at a high enough resolution in realtime. So that you know when things are coming in and out. And that's been one of the more critical things that we've built towards a Splunk, is that ability to watch over it in realtime. But more important, or just as important in that is, understanding the dependencies and the relationships between these different services. And so, that's one of the main things that we worked on here is to make sure that you can understand the dependency so that when there's an issue you have a shot at actually figuring out where the problem is coming from. Because of the fact that there's so many different services and so many things that could be affecting the overall user experience when something goes wrong. >> I think that's one of the most exciting areas right now, on observability is this whole microservices container equation, because a lot of actions being done there, there's a lot of complexity but the upside, if you do it right, it's significant. I think people generally are bought into that concept, Patrick, but I want to get your thoughts. I get this question a lot from executives and leaders whether it's a cloud architect or a CXO. And the question is, what should I consider? What do I need to consider when deploying an observability solution? >> Yeah, that's a great question. Cause I think they're obviously a lot of considerations here. So, I think one of the main ones, and this is something that I think is a pattern that we are pretty familiar with in the this sort of monitoring and management tool world. Is that, over time most enterprises have gotten themselves a very large number of tools. One for each part of their infrastructure or their application stack and so on. And so, what you end up with is sprawl in the monitoring toolset that you have. Which creates not just sort of a certain amount of overhead in terms of the cost, but also complexity that gets in the way of actually figuring out where the problem is. I've been looking at some of the toolsets that some of our customers have pulled together and they have the ability to get information about everything but it's not kind of woven together in a useful way. And it sort of gets in the way actually, having so many tools when you are actually in the heat of the moment trying to figure something out. It sort of hearkens back to the time when you have an outage, you have a con call with like a cast of 1000's on it trying to figure out what's going on. And each person comes to that with their own tool, with their own view, without anything that ties that to what the others are seeing. And so, that need to be able to provide sort of an integrated toolset, with a consistent interface across infrastructure, across the application, across what the user experience is and across the different data types. The metrics, the traces, the logs. Fundamentally I think that ability to kind of easily correlate the data across it and get to the right insight. We think that's a super important thing. >> Yeah, and I think what that points out, I mean, I always say, don't be a fool with a tool. And if you have too many tools, you have a tool shed, and there are too many tools everywhere. And that's kind of a trend, and tools are great when you need tools. To do things. But when you have too many, when you have a data model where essentially what you're saying is, a platform is the trend, because weaving stuff together you need to have a data control plane, you need to have data visualization. You need to have these things for understanding the success there. So, really it's a platform, but platforms also have tools as well. So tools or features of a platform if I get what you're saying, right? Is that correct? Yeah, so I think that there's one part of this which is, you need to be able to, if I start from the user point of view, what you want is a consistent and coherent set of workflows for the people who are trying to actually do the work. You don't want them to have to deal with the impedance mismatches across different tools that exist based on, whatever, even the language that they use but how they bring the data in and how it's being processed. You go down one layer from that. You sort of want to make sure that what they're working with is actually consistent as well. And that's the sort of capabilities that you're looking at whether you're whatever, trying to chart something to be able to look at the details, or go from a view of logs to the related traces. You sort of want to make sure that the information that's being served up there is consistent. And that in turn relies on data coming in, in a way that is sort of processed to be correlated well. So that if you say, Hey, I'm I'm looking at a particular service. I want to understand what infrastructure is sitting on or I'm looking at a log and I see that it relates to a particular service. And I want to look at traces for that service. Those things need to be kind of related from the data on in and that needs to be exposed to the user so that they can navigate it properly and make use of it. Whether that's during kind of, or time during an incident or peace time. >> Yeah, I love that wartime conciliary versus peace time. I saw blog posts from a VC, I think said, don't be a Tom Hagen, which is the guy in The Godfather when the famous lines said, you're not a wartime conciliary. Which means things are uncertain in these times and you've got to get them to be certain. This is a mindset, this is part of the pandemic we're living in. Great point, I love that. Maybe we could follow up on that at the end, but I want to get some of these topics. I want to get your reactions to. So, I want you to react to the following, Patrick. it's an issue in a topic, and there it is, missing data results in limited analytics and misguided troubleshooting. What's your reaction to that? What's your take on that? What's the Splunk's take on that? >> Yeah, I mean, I think Splunk has sort of been a proponent of that view for a very long time. I think that whether that's from the log data or from, let's say, the metric data that we capture at high resolution or from tracing. The goal here is to have the data that you need in order to actually properly diagnose what's going on. And I think that older approaches, especially on the application side, tend to sample data right at the source and provide hopefully useful samples of it for when you have that problem. That doesn't work very well in the microservice world because you need to actually be able to see the entirety of a transaction, to a full trace across many services before you could possibly make a decision as to what's useful to keep. And so, the approach that I think we believe is the right one, is to be able to capture at full fidelity all of those bits of information, partly because of what I just said, you want to be able to find the right sample, but also because it's important to be able to tie it to something that may be being pulled in by different system. So, an example of that might be, in a case where you are trying to do real user monitoring alongside of APM, and you want to see the end to end trace from what the user sees all the way through to all the backend services. And so, what's typical in this world today is that, that information is being captured by two different systems independent sampling decisions. And therefore the ability to draw a straight line from what the end user sees all the way to what is effecting it on the backend is pretty hard. Where it gets really expensive. And I think the approach that we've taken is to make it so that that's easy and cost-effective. And it's tremendously helpful then to tie it back to kind of what we were talking about at the outset here where you were trying to provide services that make sense and are easy access and so on to your end user. to be able to have that end to end view because you're not missing data. It's tremendously valuable. >> You know what I love about Splunk is, cause I'm a data geek going back when it wasn't fashionable back in the 80's. And Splunk has always been about ingesting all the data. So they bring all the data, we'll take it all. Now from at the beginning it was pretty straightforward, complex but still it had a great utility. But even now, today, it's the same thing you just mentioned, ingest all the data because there's now benefits. And I want to just ask you a quick question on this, distributed computing trend, because I mean everyone's pretty much in agreement that's in computer science or in the industry and in technology says, okay, cloud is a distributed computing with the edge. It's essentially distributed computing in a new way, new architecture with new great benefits, new things, but science is still kicking apply some science there. You mentioned distributed tracing because at the end of the day that's also a new major thing that you guys are focused on and it's not so much about, it's also good get me all the data but distributed tracing is a lot harder than understanding that because of the environment and it's changing so fast. What's your take on it? >> Yeah, well fundamentally I think this goes back to, ironically one of the principles in observability. Which is that oftentimes you need participation from the developers in sort of making sure that you have the right visibility. And it has to do with the fact that there are many services that are being kind of strong together as it were to be able to deliver on some end user transaction or some experience. And so, the fact that you have many services that are part of this, means that you need to make sure that each of those components is actually kind of providing some view into what it's doing. And distribute tracing is about taking that and kind of weaving it together so that you get that coherent view of the business workflow within the overall kind of web of services that make up your application. >> So the next topic, I want to get into, we've got limited time, but I'm going to squeeze through, but I'm going to read it to you real quick. Slow alerts and insights are difficult to scale. If they're difficult to scale it holds back the meantime between resolving. And so, it's difficult to detect in cloud. It was easier maybe on premise, but with cloud this is another complexity thing. How are you seeing the inability to scale quickly across the environments for to manage the performance issues and delays that are coming out of not having that kind of in slow insights or managing that? What's your reaction to that? >> Yeah, well, I think there are a lot of tools out there that we'll take in events or where issues from cloud environments. But they're not designed from the very beginning to be able to handle the sort of scale of what you're looking at. So, I mentioned, it's not uncommon for a company to have 10's or maybe even 100's of services and 1000's of containers or hosts. And so, the sort of sheer amount of data you have to be looking at on an ongoing basis. And the fact that things can change very quickly. Containers can pop in and go away within seconds. And so, the ability to track that in realtime implies that you need to have an architectural approach that is built for that from the very beginning. It's hard to retrofit a system to be able to handle orders to magnitude more complexity and change in pace of change. You need to start from the very beginning. And the belief we have is that you need some form of a realtime streaming architecture. Something that's capable of providing that realtime detection and alerting across a very wide range of things in order to handle the scale and the ephemeral nature of cloud environments. >> Let me ask a question then, because I heard some people say, well, it doesn't matter. 10, 15 minutes to log in to an event is good enough. What would you react to that? (chuckles) What a great example of where it's not good enough? I mean, is it minutes is it's seconds, what are we talking about here? What's the good enough bar right now? >> Yeah, I mean, I think any anybody who has tried to deliver an experience digitally to an end user, if you think you can wait minutes to solve a problem you clearly haven't been paying enough attention. And I think that, I think it almost goes without saying, that the faster you know that you have a problem, the better off you are. And so, when you think about what are the objectives that you have for your service levels or your performance or availability. I think you run out of minutes pretty quickly, if you get to anything like say, three nines So, waiting 15 minutes, maybe would have been acceptable before people were really trying to use your service at scale. But definitely not any more. >> And the latest app requires it. It's super important. I brought that up and tongue in cheek kind of tee that up for you because these streaming analytics, streaming engines are super valuable, and knowing when to use realtime and not also matters. This is where the platforms come in. >> Yes, absolutely. The platform is the thing that enables that. And I think you have to sort of build it from the very beginning with that streaming approach with the ability to do analytics against the streams coming in, in order for you to deliver on this sort of promise of alerts and insights at scale and in realtime. >> All right, final point. I'll give you the last word here. Give a plug for the Splunk observability suite. What is it? Why is it important? Why should people buy it? Why should people adopt it? Why should they upgrade to it? Give the perspective, give the plug. >> Yeah, sure. I appreciate the opportunity. So, I think as we've been out there speaking to customers right over the last year as part of Splunk and before that, I think they've spoken to us a lot about the need for better visibility into their environments. Which are increasingly complex and where they're trying to deliver on the best possible user experience. And to sort of add to that, where they're trying to actually consolidate the tools. We spoke about the sprawl at the beginning. And so, with what we're putting together here with the Splunk observability suite. I'd say we have the industry's most comprehensive and powerful combination of solutions that will help both sort of IT and DevOps teams tackle these new challenges for monitoring and observability that other tools simply can't address. So you're able to eliminate the management complexity by having a single consistent user experience across the metrics and logs and traces, so that you can have seamless monitoring and troubleshooting and investigation. You can create a better user experiences by having that true end to end visibility, all the way from the front end to the backend services, so that you can actually see what kind of impact you're having on users and figure it out within seconds. I think we're also able to help increase developer productivity. As these high performance tools that help the DevOps teams get to a better quality code faster, because they can get immediate feedback on how their coachings are doing with each we would see each release and they're able to operate more efficiently. So, I think there's a very large number of benefits from this approach of providing a single unified toolset that relies on a source of data that's consistent across it but then has the sort of particular tools that different users need for what they care about. Whether you're the front end developer, needing to understand the user experience, whether you're backend service owner wanting to see how your service relates to others, whether you're owning the infrastructure, and needs to see, is it actually providing what the services are running on it need. >> Well, Patrick, great to see you. And I just want to say, congratulations has been following your work, going back in the industry specifically with SignalFx, you guys were really early and seeing the value of observability before it was a category. And so how has more often so relevant as you guys had saw it. So, congratulations and keep up the great work. We'll keep a competition's open. Thanks for coming on. >> Great, thanks so much, John. Great talking to you. >> All right, this is theCube, Leading with observability, it's a series, check it out. We have a multiple talk tracks. Check out the Splunk's a series, Leading with observability. I'm John Furrier with theCube. Thanks for watching. (upbeat music)

>> live from Mountain View, California It's the queue covering definite create twenty nineteen Brought to you by Cisco >> Hey, welcome back to the cave, Lisa Martin with John Barrier. We're coming to you Live from the Computer System Museum at the third annual Cisco Definite Create twenty nineteen Excited to be joined by Joycelyn Developer Advocate from Postman Joyce Welcome to the Q Thank you. So you are a developer advocate. But postman is a tool that helps the community learn about Cisco ap eyes Postman is a Cisco was a customer of yours but a little bit about your experience at definite cry Because you have an interesting story from last year, which was your first year of this event >> Exactly last year. We just happen to stop by. And as I was walking through this very room you hear all these workshops going on behind us My ears perked up cause I heard somebody say python in postman or two of most powerful tools And I was like, Hey, I >> work a postman >> So I like, stopped in to see and I slapped my team back immediately at the office there, really using postman to teach Cisco Technology here. >> That was surprising to you. And here you are now here a year later. Tell us some of the things that you're expecting to learn and hear and feel and see from twenty nineteen. Create. >> So this year I hear about all these people learning postman learning about tech through postman. So I'm actually giving to talks this afternoon The first talks talking about building the community because a lot of people use postman in the second talk is about using mock servers. Had a fake an AP I until you actually coded and deploy it. >> Take a minute to explain. Postman. Why is it so popular? Why Francisco jazzed about it? What are they using it for? How they bring that in take a minute to talk about what you guys do >> Well, several years ago, when postman started as a side project was primarily for developers and help developers do their day to day jobs. But we found a lot more People are interacting with technology or working at tech companies where they might not have the setup to initiate a request. AP I request, and so postman allows them tio on their desktop be able. Teo interact with the tech in a way that normally they wouldn't have the whole set up to do it. >> So So in terms of developers, what's is a freemium model? They do have a free hand leads >> premium. And I think within the last year we've scooch almost anything that used to be a paid feature down to free so you can try it out. And in fact, if you have a small business or a side project, it's it's free. >> And what's the talk track? You're gonna have to get to talks. One on community, one on serve servers. Monster. >> Yeah, So Mock service is something that I thought might be interesting to this crowd. But a lot of these people have are in charge of managing the infrastructure or supporting existing AP eyes or services that are out in the cloud. And so mock servers are a way that you can essentially mock an FBI for parallel development or to build a prototype put into >> you. And so this helps develop, get faster app up and running. And then what happens when they have to get rid of mock server and put a real server on there? They had built out the re p I. Is that what happens? >> Typically, they're spinning Oppa marks over first, and then they're building out their own servers. So, yeah, they would swap out the mock with their own. >> And what's the other talk on community? Just how did do a community open sores? What's the aspects of the community talk? >> It's kind of on >> odd topic for this kind of crowd, but a lot of people work for companies that are or work for teams where they're just trying to build, like, a sense of community or foster some sort of mission. And so just telling the Postman story and Postman was free for absolutely free for a super long time in growth has just been astronomical. >> You're six million developers on the planet working on that, but I can't say on the company's one hundred thirty million plus AP eyes. And that's all. Just since the company was established in twenty fourteen after this sort of side project that you talked about so pretty, >> pretty quick >> growth trajectory that you guys are on >> and a lot of it was word of mouth. I mean, until I came here last year and heard all the system people talking about how they're using postman. We did not know that. >> So how have how has Postman actually evolved your technology in the last year? Just since you stumbled upon? Wow, this we're actually really hot here. We are really facilitator of developers. This community that's now what five hundred eighty five thousand members strong Learn about Cisco AP eyes. I'd love to know how that has sort of catalyzed growth for postman. Well, back in the >> day, Postman started as developer first. So here's an individual developer. How can they work more effectively? But teams like Cisco you'll be lucky if you find a team of ten people these air hundreds and thousands of developers coming together to work together. So postman as a tool has shifted from focusing on on ly the developer to how do you support developers working in larger teams? >> So what? The community angle? Because one of the things that Lise and I were just talking about you she does a lot of women in tech interviews with Cube and we're building out these communities ourselves and in Silicon Valley, the old expression fake it till you make it. It's kind of a startup buzzword, but people try to fake community or by community. You really can't get away with that. In communities, communities are very fickle. A successful open source projects you've gotta contribute. You've gotta have presence. You've got to show your work to get you to the bad actors. It's >> pretty >> efficient. But things air new now in communities this modern era coming into slag, you got tools. How is community evolving? That's your perspective on this. >> That's an interesting question. I think the community you never wanted fake community absolutely agree, and something that Postman is kind of lagged on is the community's been huge, but we haven't really been involved. So around the world we have people giving workshops that we don't even know about, like around the world. And how can we support them and allow them to tell, teach things consistently and teach best practices? So I wouldn't say unfortunately, well or fortunately, we're not in the position where we have to encourage the growth, but rather just support the people that are already doing this. This >> is the pure ingredient Teo Community development, because you're enabling other people to be relevant with their communities. So you're not so much like just trying to be a community player. You're just your product enables community growth. >> Absolutely. Yeah. >> You just gotta come feed >> postman as a tool. And then postman, the seeds >> of community. >> Yeah, we're healthy. >> So talk about some of the where you guys locate. How many people in your company? What's this? What numbers >> were headquartered in San Francisco. We have a huge engineering department in Bangalore where our founders air from. And I think just a few months ago, we started having distributed people. So now we're everywhere. I think we're about a hundred head count. Uh, fifty five percent of that is engineering. So where? I don't know where a >> start off. I mean, they were started hunting with number two hundred thousand companies using the technologies. We said over six million developers. How do you get a handle on to your point earlier supporting all of these groups that are out there enabling us Johnson enabling and fueling communities like Deb. Nanny? How do you start that with a one hundred person organization? >> Yeah. I'm so glad you're like, Wow, that doesn't seem like a huge organization because other people are like I thought you are way bigger than that. One thing is that we do listen to our community. And so if they're having a pain point way, try to aggregate all those voices and then come out with a cohesive road map because what might be the loudest voice for even a lot of voices might not be what's right for the tool. The other thing is, we're not open source company, but we have a ton of open source projects. So the community has again developed converters, integrations all these open source tools that for their specific workflow works for them. And actually, they're sharing with the community. >> How did you get into all this? How did you join the company? What attracted you and what's what story? >> Well, I'm in San Francisco, so I work for a tech company. I have a hodgepodge background, but I won't go into because it just sounds confusing. Some people call me the Wolverine at work. >> That's a nickname. >> Um, hopefully it's not because I'm so Harry, but because I've had many lives, so I I kind of bring a little bit of that, too. My developer advocate role, a little bit of product, A little bit of marketing, little bit of the business side. >> It's good versatility, lot of versatility. Yeah, let me ask a question. One of the things we've been covering is actually we love cloud nated. We've been covering cloud in the early days. Oh, wait. Oh, seven All the way through Love Cloud native We get that check enterprises Ha! You see Cisco using your stuff. Enterprise developers are hot right now. People are fast filling applications has got a cloud native flare to a definite create. It's also gotta integrate into the classic enterprise. What's the difference in your view and your experience, your observations between enterprise developers and then your classic You know, hard core cloud native developer >> I would say that's something that postman, as an organization is dealing with right now because we started developer first. Now we're finding Oh, it's a different person making these decisions. What tools should we use? Sometimes it's top down, but at the end of the day, it's always the developer that is going to support a top down decision. A developer that's going to find the utility out of certain tool. So we're shifting our focus. But not necessarily by that much. Because long as you focus developer first, it's still >> so enterprise. Kind of taking more of a classic cloud developer or native cloud native developer. You think that kind of profile you in your mind? >> Well, again, you have an enterprise developer. But what? Where's that enterprise developer going to be in two years? So we're not hanging our hat too much on Enterprise? Only now >> what do you want? The Ciscos measures of programming. The network. I mean, infrastructure is code. That's kind of a nice value proposition. Take the complexity away. What's your take on reaction toe that vision? >> I don't know what you're talking >> about. I don't know what part. >> What part of tell you are. >> Well, they're saying developers shouldn't have to configure hardware. You know, abstract the network capabilities out and make it code. So the developers just it just happens. >> Got it? Yeah, And if you think about how you Khun scale, can you scale linearly or exponentially? Enabling every developer or team to deploy their own code at their own pace with their own tools is something that allows you to scale exponentially. So things like mock servers that were talking about earlier. If I'm relying on somebody, that's my bottleneck. To spin this up with the normal workflow for the organization, that's a bottleneck. Spin up your own mock server. >> Find mock servers were great. Resource because remember the old days and mobile the emulators kind of had to have an emulator to kind of get going. Okay, that was, like five years, but similar model like, Hey, I don't need I can't build that out now. But I need to know what it's gonna look like so I can get this done. >> And that allows you to iterated at the fastest >> level at the local >> developer level. >> We've been covering the old days here in the Cube world. >> Throwback. Joyce, thanks so much for your time joining us on the cue program this morning. It a definite creed. Best of luck in your two sessions later on today. We look forward to seeing you next time. Great. Thank you. Nice to meet you for John Ferrier. I'm Lisa Martin. You're watching to keep live from Cisco Definite create twenty nineteen. Thanks for watching

>> Live from San Francisco, it's theCUBE. Covering Google Cloud Next 2018. Brought to you by Google Cloud and its ecosystem partners. >> Hello everyone and welcome back it's theCUBE coverage live in San Francisco at Moscone South for Google Cloud Next 18, I'm John Furrier with Dave Vellante, next guest is Jennifer Lin, Director of Product Management, Google Cloud featured in Forbes as one of the power women at Google Cloud. Congratulations on your Forbes distinction. >> Thanks so much John. >> Great to see you. So we had a chat before the event, couple weeks ago leading up to it around Istio, Kubernetes. You're in charge of a lot of the cool, I would say the modern middleware. >> Yes. >> That's going on. I want to say middleware kind of in quotes, it's not really middleware, it's cloud, it's horizontally scalable. Take a minute to explain some of the areas you're working on and then the importance of Istio's announcement today that 1.0 generally available, huge news, it's kind of nuanced it's not as big as the cloud sources platform and some of the Cisco relationships, but huge progress. >> Yes. >> In this services, microservices, this is the key part. Take a minute to explain. >> Yeah, we're really excited to get to this week and I think the announcement of the cloud services platform of which, obviously, the evolution of Kubernetes and Istio are a key part. Now we've kind of changed the way people manage container environments, and now people are really writing really innovative services and microservices and the ability to manage that easily is really what Istio's all about. And do that in a secure way. >> So we had the CEO Sundar Pichai on the stage, of Google proper, as Diane Greene was also on stage. Sundar made the comment, this is the only event I could make a containers and Kubernetes joke. >> Yes, with the big containers. >> Translate, he's smart, he knows tech. Very strong tech culture here. Jennifer, explain to the people why Google Cloud is differentiating around APIs and services and open source. Why is that so important? >> At heart I think we really are a software innovation company, and Google is a company of developers that want to do creative things with software. As Diane said this morning, I think the, sort of, ability to do that in a way that hides the complexity, but also excites emerging developers with all the things that they can do, I think that's what we're seeing in cloud. Originally we started very much with the cloud natives who were doing very new types of consumer applications. As Sundar said, when we moved into doing business applications and more and more people were developing enterprise applications with a cloud native model, we started to see a big uptake and adoption of our cloud platform. And I think with a lot of the things we're doing in security and the ability to enable administrators to kind of, manage that in a more automated way, that's a lot of what I think we're differentiating around. >> So one of the headlines that I can see happening on these on SiliconANGLE or TechCrunch or some of the blogs and publications out there is Google Doubles Down on Kubernetes. >> Yes. >> And the announcement of Istio's general availability of 1.0 certainly is good news, what does that mean? What should people know about the importance of Kubernetes doubling down as a momentum point for Google and the importance of Istio? What is the real benefit to the customer? >> We've had a managed Kubernetes environment on GCP for four years now, but before that, Urs talked about a decade worth of understanding how to scale Kubernetes in an operational environment. So we've learned a lot of domain knowledge there that we're kind of baking into the software platform itself. Istio really models the way we do microservice management, as we launch billions of containers a week. So how do we essentially secure the service environment? How do we give really good visibility? We showed the service graph where we can see the latency between two services, and really hide a lot of the back end complexity that really, from an operational perspective, is causing a lot of toil for application developers as well as operators. >> I notice toil is a word that's being kicked around the Google community a lot, toil being headaches, pains, but I wanted you to take a minute to explain for the folks that are learning about Kubernetes for the first time. Kubernetes was donated, or donated by an open source but by Google, but prior to Kubernetes, you guys have been running Borg, which is the internal system. >> That's right. >> That's been the foundation of the scale of the service management for all of Google. >> That's right. >> Explain that important history there, and how you're making Kubernetes easy to consume because most companies aren't Google. >> Yes. >> Explain the little history and then how it translates to consumption. >> I think Borg was really built and designed to keep developer agility up and make sure that developers could be very productive, but we could run essentially at global scale the container orchestration environment. When Kubernetes was donated to the open source community, there were some things that needed to be defined, such that the abstractions could be very clean outside of a Google environment. But that framework, obviously, held up very well and hence the growth with Kubernetes. Istio, I think similarly, models a lot of the way that we've done service management with the service mesh within Google. Obviously the names are slightly different, but there's a lot of operational domain knowledge on best practices and how to essentially enable automation at a much more granular level of applications. Where it's not a bunch of proprietary applications, but you have a lot of loosely coupled systems coming together. >> So, Jennifer, the maturity curve of the developer community, obviously is in some bell shape. >> Yes. >> How does Google approach engaging with those developers? Are you trying to get leading edge guys that want to develop software the way Google develops software? Obviously you're trying to reach a bigger market, so how do you balance those two? >> I think that's where open source is the most exciting, 'cause whether it's kids in school or very experienced developers, number one the transparency, things move so fast, a lot of that is about developer reach. But also about the participation of developers to give back to the community and help evolve the system. For something like Kubernetes, obviously, and Istio, Google sort of bootstrapped that and donated it to the community, but since then, we've seen just incredible participation at things like Kubecon, and developer hackathons, et cetera. So that's both a model for growing the community, but also just to educate and share, essentially, a lot of the best practices in a different type of way than most software companies, I think. >> Well, and you've worked at a lot of very successful enterprise companies, some very profitable enterprise companies. I get the sense that profit is an outcome of doing good work at Google. >> Yeah. >> You don't wake up in the morning and say okay, how am I going to make money? >> Yeah. >> You say, how am I going to do work and you don't seem to be stressing. I guess it helps that you have $100 billion in the balance sheet. But is that the right way to think about how you guys think about the marketplace? >> Yeah, I think the goal is very clear for us and I know Sundar talked about it a lot, the alignment between our original mission at Google and the opportunity we see in Cloud. Data is exploding, new applications are being written in a way that really brings together worlds that didn't come together before. Healthcare applications where you need to share a lot of data, people need to do research, and you need to make it very easy to share, but at the same time it needs to be highly secure. We're under the same pressures as any other enterprise in terms of regulatory environments, et cetera, so making all of that easy, I think is the reason why open source and open ecosystems make a lot of sense to us. It's just the only way to move fast, and actually make sure that we're bringing the whole community with us. >> But not everybody takes that philosophy, obviously. It's one that you're attuned to. But when you think about Google's posture in this community, I mean you started kind of late to the enterprise game, don't seem to be too stressed about it, you're developing the ecosystem. We've seen in this world, some of the companies you work with, it's winner take all. >> Yeah. >> Is Cloud just so big that there's plenty of room for everybody? Or is it winner take all in different segments? How do you think about that? >> Our leadership, to Diane, basically really sees this as we're playing the long game. And it is about driving adoption more so than essentially quarter to quarter revenue. When we're reinventing how software is designed and delivered, and published, et cetera, and shared? I think it is not going to be the monetization per quarter, which, many of the companies, I think, have to be under the pressure for. Within Google, I think we really do see this as the future of software, and that's going to take some time, but yeah. Urs talked a lot about spend has gone up in many enterprise environments despite the fact that they are changing their environment. Automation is a way to bring down a lot of the cost, so we believe there's a lot of value to be captured there, but we're not in a race to essentially monetize every piece of every product we put out there. >> So how do you measure your success? Is it just a feeling that, yeah we're doing good work? Or adoption, or? >> Adoption and the happiness of our customers and the lead partners that we work with. Our leadership is very focused on that. We want to prove it out with some trusted partners and customers, and I think some of those were on stage today. Make sure that it's replicable, and make sure that we leave our options open. 'Cause you never know what's going to happen in the next year. >> I got to ask you about the on-prem solution that was demoed today >> Yup. >> Actually they put a little easter egg in the demo and then came back and said, oh by the way, that node was on-premise. >> Yep. >> And Cloud. One of the things we talked about, and you've been harping on this, about Kubernetes orchestrating an abstraction at higher levels of services. >> Yes. >> Both in the cloud and on-premise. >> Yes. >> It's happening now, that was really elegant. Is that a demo? Is that actually shipping code? How far along are you? >> Yeah. >> Where's the head room in this? Explain this important phenomenon, because this is multi-cloud, and I've been really negative on multi-cloud, until we see things like this. This is easy to understand. >> Yeah. >> Your thoughts? >> Now that you really have workload portability and a common abstraction layer, and a single point of administrative control, there's a lot you can do there. And that was really hard to do, I think, with the proprietary systems. That wasn't just a demo, a lot of customers are starting to see that they have to think about hybrid and multi-cloud in a different way. And using some of these innovative technologies with containerization, you don't have to worry about the kernel version and the OS and a lot of the toil that was in the system before. So yeah, I think we're coming at hybrid cloud and multi-cloud in a way that no other cloud provider is, and that was, I think, the start of what a lot of customers have waited for. >> Yeah, and certainly this is the benefit of a Kubernetes and Istio now has got some capabilities into it, policy and that's still going to evolve. The question I want to put to you, and I'll play the devil's advocate role. Shouldn't the multi-cloud be an independent group? Or if I'm going to say, "Okay Google, I'm nervous, you're going to do all this stuff." There's a trust there, how do you guys answer the naysayers who might say it should be an independent organization handling multi-cloud. What's the answer to that? >> I think that's why a lot of the partners that we worked on initially with something like Istio, IBM and Lyft, they also didn't want to be locked into any one cloud provider. And we've done some things in the marketplace where we believe that the future is hybrid and multi-cloud. I think from a technology perspective, just making sure that essentially we can define those interfaces in a way that's not tied to a vendor implementation, be transparent. We have in Istio things like partner mixer adapters, that ecosystem is growing very quickly, so that pluggable adapter model allows the whole ecosystem to participate. >> And the role of open source in all this, obviously STO, we were at the Linux Foundation's CNCF covering this pretty heavily in Denmark just recently, we've spoken about it. How does all the action happening here at Google Next impact open source? What's going upstream, what are some of the updates, can you share what's going on in open source with Google? >> Istio 1.0 is essentially an announcement about the open source effort. I think we also saw that many of our enterprise customers want a managed environment. So just like Kubernetes, we have the open source Kubernetes which is rockin' and rollin' along, we have our managed Kubernetes commercial offer. Now that there's a level of maturity in the managed Kubernetes environment, and people are excited that Istio 1.0 is getting more mature, they want that to be a part of the evolution of their managed Kubernetes environment. Which is why we're starting to see just the whole stack evolve. First we abstracted the infrastructure, now we can manage services, and then we can bring in a whole new type of ecosystem. So, it's very exciting. >> So here's a philosophical question for you, Dave and I always like to talk about old new way. So old IT is like horse and carriage, and buggy, and cloud is like the first car, now you got sports car. How do you explain all the under the hood examples of the engine? >> Yeah. >> The car just drives. You don't have to feed the horses the hay, what's the new benefits that the old world won't see with clarity? Can you tease out, from your perspective, what are some of those things that go away and say, wow, we used to do that? What are some of the things? >> I think, even within how we build our products, we're very focused on user experience. And sometimes the user is a developer, sometimes the user is an administrator, and sometimes the user is the end user, in our case, maybe the customer's customer. So we do a lot of UX research, but like you said, there's a lot of complexity in a car, but when I drive a car, I just want to drive the car. So the user experience for the driver is very different from the mechanic who's fixing the engine. There's no doubt that there is a lot of complexity in these large-scale, global distributed systems, but many of our enterprise customers don't want to know every little bit of how it's built. What they want to know is some declarative end-state of what they want to get to. The functions that they want or application that they're trying to drive. That is the maturity level that we're at, where Istio hides a lot of that complexity, provides a common service abstraction, but still gives essentially the administrators the things that they need out of the system. >> Well and it speaks to as well, and you guys talked about this in your interview, how software's being developed and how that's changing. When I deal with Spotify, if I have a problem, I don't call up. >> No. >> Their billing department, or their customer service department, I just do it. >> Yes. >> And that's the way software is going to be developed in the future. >> Yes. >> Versus the way most enterprise. >> And you talk about a great customer of GCP, Spotify, I use them everyday as well, but yeah, that is a lot about user experience. But what they've done with machine learning, to basically serve up the song that I want to hear that day, based on the playlists I had before, it really is changing how software is done. >> So if you look at some of these old metaphors like horses versus cars, you mentioned that. Jobs get automated away with that old model, but yet there's new jobs are created. >> Yes. >> So I want you to talk about what's going away and what's evolving. 'Cause the value is shifting up the stack with higher level sets of services and new abstractions. >> Yup. >> Which you don't need to know all the details, just magic happens for the customer. There's new value being created. >> Yup. >> You could almost look at the market and say, IT operations, decimated. Manual configuration, decimated. >> Yes, well. I mean that's the history. >> That's my words. >> Of technology. The history of technology is moving forward and automating things. For Google, obviously, we don't think of the software layer as just the infrastructure layer. A lot of what we're trying to get to is essentially with things like machine learning and analytics, and that's real business value that people really had too much toil to essentially stitch the systems together. >> Yes. >> Now as the platform evolves, I think it just becomes one stack. And we can put those tools into-- >> Is there an API administrator? 'Cause you start to see people starting wiring services together. >> Yep. >> Between building blocks. >> Yes. >> So almost the cloud model. Right? >> Yep. >> So is that a API administrator? Is it code? >> You know-- >> There's still a human component. We agree. >> Yes, yes. >> But what is that new role? >> I think we've always had the notion of API management, with cloud endpoints and our apogee acquisition. APIs are evolving with microservices, and a lot of the partners that essentially have been in that space are all re-basing on something like Istio where they can do service management at a higher level. The API is part of it. Within Google, we use things like protobufs, where you have structured data and message protocols that essentially are not just an API. We think about API and service management hand in hand. Both of those things I think are changing. >> So my final question for you, I want to get your advice to any of the practitioners out there or customers that really want to take cloud native because with the containers, Kubernetes and Istio, you can actually manage lifecycle of old stuff and still bring in the new. >> Yup. >> You guys do API service management, you got cloud endpoints, billing, commerce, marketplace, Kubernetes serverless, and Istio is kind of a focus group. What's your advice and what's coming next that people should be aware of? For the folks who want to go cloud native, want to put the more gas, less brake, put the pedal to the metal with cloud native and not foreclose or have to do a rip and replace. Manage their existing lifecycle applications and to bring in the new with cloud native. What's your advice? >> I think build for the future, make sure you don't get stuck in a silo. We often see that different pace of customers and the way they're moving to cloud native. Our tagline for this conference was also, we're bringing the cloud to our enterprise customers, they can move at their own pace. We recognize that sometimes the migration challenges are pretty tough with their legacy systems. But they have a much clearer view now, in terms of where software is going, so depending on the steps they want to take, we want to enable that either natively, with what we're doing with CSP, or enabling partners to take phased approach to that end state. >> Awesome, and ultimately the developers for the applications >> Absolutely. >> Will win on this. Jennifer Lin, Director of Product Management at Google Cloud here inside theCUBE, breaking down all the action around APIs, service management, and why it's important as the modern middleware within the cloud, enabling developers. I'm John Furrier with Dave Vellante. Back with more live coverage here in San Francisco after this short break. Stay with us. (electronic music)

>> Man: Let me check. >> Announcer: Live from Las Vegas, it's The Cube. Covering InterConnect 20 17. Brought to you by IBM. >> Okay, welcome back everyone. Day two, we are here live in Las Vegas for IBM InterConnect. This is Silicon Angle's The Cube coverage of IBM's cloud event. The CEO, Ginni Rometty, was just on stage. We're kickin' off wall to wall coverage for three days. I'm John Furrier, my co-host, Dave Vellante, here for all three days. >> And, our next guest is Andy Lin, who's the VP of (mumbles) Mark Three Systems. A, 20 plus year IBM platinum partner. Doin' some real cutting edge work with cognitive as Ginny Rometty said cognitive to the core, is IBM's core strategy. Data first, enterprise strong is kind of the buzz words. Andy, welcome to The Cube. Appreciate you comin' on. >> Thanks for havin' me. >> So, obviously, enterprise strong, you know, it's, it's a kind of whole nother, you know, conversation that we can go deep on, but data first and cognitive to the core is really kind of the things that you guys are really getting into. All kinds of data types. Automating it and making it almost frictionless to move insights out. So, take a minute to explain what Mark Three's doing and what your role is with the company. >> Sure. Absolutely. So, I'm Vice President of strategy in Mark Three, so I work sort of across all our initiatives, especially areas that are emerging. Just a little bit about Mark Three, just historically for background purposes. So, we're a 22 year IBM platinum partner, as you pointed out. We actually started in the mid 90's, actually doing IT infrastructure around the IBM stack at that time. So, we sort of been with IBM over the last 20 years since the beginning. We've sort of grown up throughout the stack as IBM's evolved over the last two decades. About two and a half years ago, we started a digital development unit, called BlueChasm. And what BlueChasm does, is it basically builds open digital and cognitive platforms on the IBM cloud that are around a lot of services you pointed out. And, we basically designed it based on use cases that the ecosystem and our clients talk about. And, to give you a couple examples, one of the, one of the big ones that we're seeing a lot of interest around is called video recon. Video recon is a video analytics platform that's API enabled and open at it's core. So, regardless of where the video comes from, if it's a content management system, if it's a camera, we're able to basically take in that video, basically watch and listen to the video using Watson and some elements of our own intellectual property. And, then basically return insights based on what it sees and hears along with time stamps, back to the user to actually take action. >> Yeah. I love the name BlueChasm. It brings up, you know, Jeffrey Moore's Crossing the Chasm. Blue, IBM, big blue, so you know, it's a nice clever play. The BlueChasm opportunity. So, in your mind, for people watching, squint through some of the trends and extract out where you see these opportunities. Because if you're talkin' about new opportunities are emerging because of cloud horsepower and compute and storage and all the greatness of cloud, and you got real time analytics kind of really hittin' the main stream. That's going to, that's highlighted by internet of things is you can't go anywhere these days without hearing about autonomous vehicles, industrial (mumbles) things, AI, Mark Benioff was sayin', you know, we've seen the movies like Terminator and we've all dreamed about AI, so we can kind of get excited about the prospects. But, the chasm you're talkin' about, this is where these things that were ungettable before, unreachable new things, what are some of those things that you guys are doin' in that chasm? >> Yeah, so I think some of the things that we're doing are basically enabling, like I'll use video recon as an example, right, we're enabling a class to be able to get new insights using basically computer vision, but in an open and accessible way, that they've never had been able to do before. Vision itself, I don't think is new or revolutionary. You know, a lot of folks are doing it, self driving cars, etcetera. >> John: Yeah. >> But, I think what is new is being able to make it open and easily accessible to the normal enterprise, the normal service provider. Up to now, it's been, you know you've had, really had to have your own team of, you know, really, really deep AI develops or PHD's to be able to produce it for your own platform. What we're trying to do is basically demarketize that. >> John: Yeah. >> So, to give you an example, some use cases that we're, we're sort of working on today, the ability to do things like read meters and gages, as an example, with a camera. That way you can avoid a situation where somebody has to walk around all the time, you know, look at different things that could be dangerous. That there could be issues actually looking at what you see from a metering perspective. Or to be able to, for instance, for in the media entertainment industry or the video production industry, be able to do things like identify shot types, be able to more quickly allow our enterprise users in that particular space to be able to create video content quickly. And, the underlying theme with all this, I think it's really about speed to market. And, how quickly can you iterate and please whatever your customers in that particular space that you're in. >> So with the video recon, so your, your videos are searchable, essentially. >> (Andy) Correct. >> So, so what do you do? Use Watson, natural language processing to sort of translate them? Now (mumbles), of course, you know, NLP is maybe I don't know 75, 80 percent accurate, how do you close that gap? >> Yeah, so video recon does both visual and audio. So, the audio portion you are correct. There is some degree of trade off in accuracy relative to what I think the average human can do today. Assuming the human is focused and able to really tag these videos accurately. So, we are able to train it based on things like proper words and things that are enterprise focused. Because I know there, there are a lot of different ways that I think you can maybe attack this today from a video analytics perspective, where we're focused primarily just on the enterprise, solving business problems with, with video analytics. So, you know, taking advantage of if Watson improves, cause we do use (mumbles) tech at it's core from, on the audio perspective. Applying some of our own techniques to basically improve the accuracy of certain words that matter most to the enterprise. One of the things we've noticed is it's an entirely collaborative relationship with our, with our, with our enterprise clients but really partners. Because what works well for one, may not work well for another. One thing about cognitive is it really depends on the end user as to if this is a good idea or not. Or if this will work for their use case, just based on error, as you pointed out. >> So, to your point, you're identifying enterprise use cases and then tuning the system. Building solutions, essentially, for those use cases. >> Andy: Absolutely. >> Now, you said 22 year IBM platinum partner, so you obviously started well before this so-called digital transformation. >> Andy: Yes. >> You see digital transformation as, you know, revolutionary, or is it more of an evolution of your business? >> I'd definitely say it's an evolution. I think, you know, a lot of the industry buzz words out there are all around, you know, transformation or transition, but for us it's been completely additive. You know, at the end of the day we're just doing what our clients want, you know. And, we're still continuing the core part of our business around modernizing and optimizing IT infrastructure, tech sacks in the data center, also infrastructure service in the cloud. Also, up through the middle where it's still really as strong as ever. I mean, in fact that business has actually been very much reinforced by some of these capabilities that we brought in on the digital development side. Because, at the end of the day, you know, clients may have a digital unit and they may have, you know, IT, but they're really viewed sort of all in the same. A lot of people try to put 'em in two different buckets bimodal or whatever you want to use. But, you know, inevitably, you know, clients just see a business problem they want to address. >> Yep. >> And, they're saying how can I address it the fastest and the most effectively as relative to what their stakeholders want. And, we just realized early on that we had to have that development capability, be able to build platforms, but also guide out clients. If they don't want one of our platforms, if they don't want video recon or cognitive call center platform, that's perfectly fine. We're more than happy to guide them on how to build something similar for their developers with our developers relative to their tech stack, you know, hopefully on the IBM cloud. >> Andy, one of the things you were pointing out that I think is worth highlighting is the digital transformation buzz word, which has been around for a few years now, really is in main stream right now. >> Andy: Yes. >> People are really working hard to figure this out. We're seeing the disruption on the business model side. You mentioned speed and time to market, that's agility. That's not just a technical development term anymore. It's actually business model. It's business related. >> Andy: Yes. >> But there's two axes of things going on. There's the under the hood, heavy lifting stuff that goes on around getting stuff digitally to work. That's IT, security, and you know, Ginni Rometty talks about a lot of that on stage. That's being enterprise grade or enterprise strong. The other one is this digitization of the real world, right? So, that's creative. That requires insights. That requires kind of a different, it's actually probably maybe more fun for some people, but I mean it depends on who your profile is, but you have kind of two spectrums. Cool and relevant and exciting and intoxicating, creative, user experience driven. You mentioned reading meters. >> Andy: Yeah. >> That's the analog world. >> Andy: Yes. >> That's actually space. That's the world. That's like, you got the sky you got the meter. >> Andy: Yeah. >> You got physical impressions. This is the digitization of our world. What's your perspective? How do you talk to customers when they say, "Hey I want to digitize my business." >> Andy: Mm hmm. >> How does it go? What do you say? I mean, do you break it down into those axes? Do you go, did they see it that way? Can you share some color on this digital transformation of digitizing business? >> Yeah, so I mean it really depends on, I think, it normally it has to do with interacting with some other stakeholders in a certain way, you know. I think from our perspective it really is about, you know, how they want to interface. And, most of the time you pointed out speed. Speed I think is the number one reason why people are doing the digital transformation. It's not really about cost or these other factors. It's how quickly can I adjust my business model so I can win in the market place? And, you know, I think I pointed this earlier, but like, you know IOT is huge now. It covers what I call three out of the five senses in my mind. It covers basically touch, smell and taste in many ways. And, for us, I think we're basically trying to help them even get beyond IOT with video. Video really covers, you know, sight and hearing as well. It covers all the five senses. And, then you take that and figure out how do I digitize that experience and be able to allow you to interact with your stakeholders. Whether it be your customers, your suppliers or your partners out in the market place. And, then based on that we'll take these building blocks on how we, you know, extend the experience, and work with them on their specific use case. >> So, you got to ingest the data, which is the, you know, the images or data coming in. >> Correct. >> Then you got to prep it available for insights. >> Correct. >> And, produce them in, like really fast. >> Andy: Yep. >> That's hard. >> Andy: It is, yeah. >> It's not trivial. >> No it is not, it's not a trivial problem. Yeah, absolutely. And, I think, you know, there's a lot of opportunity here in the space over the next I think two to two to five years. But you're absolutely right. >> John: Yeah. >> I mean it is, it is a challenging. >> And, I want to get your thoughts too, and if you can share your reaction to some of the trends around machine learning, for instance. It's really kind of fueling this democratization. >> Andy: Yeah. >> You mention in the old days it was really hard, there was kind of a black art to, to machine learning or unique special, specialties. And, even data science that's at one level was really, really hard. Now you have common people doing things with visualization. What's the same with machine learning? I mean, you got more data sets coming in. Do you see that trend relevant to what you guys are working on in BlueChasm? >> Absolutely. I think at the core of it, and this wasn't our plan initially three years ago, we didn't realize that this was happen, but every single one of the platforms or prototypes or apps we've built, they all incorporate some degree of machine learning, deep learning within it's core. And, this is primarily just driven by I think what, to give a client a unique platform or a unique service on the market. Because, much of the base digitization, I mean Ginny likes to talk a lot about, you know, the key to being, differentiating yourself from digital world is being cognitive. And, we've seen this really play out in practice. And, I think what's changed, as you pointed out is, that it's easily accessible now to sort of the common man, as I put it. In years past, you really had to have people that are highly specialized. You build your own product. But now through open source- >> There's building blocks out there. >> Absolutely. >> You can just take an open source library and say hey, and then tweak the machine learning. >> Absolutely. And, the ramp up time has come down, you know, dramatically, even for our developers. Just watching them work. I mean, the prototype to video recon was built over the course of a weekend by one of our developers. He just came in one Monday and said, you know, is this, is this interesting? >> He's fired. >> Exactly. And, we were like, yes I think this is interesting. >> Well this is the whole inspiration thing that I talk about, the creativity. This is the two axes, right? >> You try to do that in the old days, I got to get a server provision. >> Andy: Yeah. >> I'm done. >> Andy: Right. >> You know, I'm going to go have a a beer. Whatever. I mean, there's almost an abandonment going on. We talked to Indiegogo yesterday about how they're funding companies. >> Andy: Yeah. >> You have this new creative action. >> Andy: Mm hmm. >> So you guys are seeing that. Any other examples you can share in terms of color around this kind of innovation? >> Yeah, so we, at BlueChasm we try to let our developers sort of have free reign over what they like to create. So video recon was spawned literally by a, on a side project, you know as with a lot of companies. It was, you know, a platform that sort of evolved into a commercial product, almost by accident, right? And, we've had others that have been anchored by like what clients had done, but like around the cognitive call center, which basically takes phone calls that are recorded and then basically transcribes and makes them easily searchable for audit reasons, training reasons, etcetera. Same kind of idea. We built things around like cognitive drones. A lot of folks are trying to do things with drones. Drones themselves aren't really not novel anymore, but being able to utilize them to collect data in unique ways, I think that industry is definitely evolving. We've built other things like, what I call the minority report board, after the scene in the movie where the board sort of looks at you and then based on what it sees of you, of different data points, it shows you an ad or shows you a piece of visual content to allow you to interact. >> John: Yeah. >> I mean, these are, these are examples. You know, we have others. But, you know we've just seen like in this organization if we allow creativity to sort of reign, you know, have free reign. We're able to sort of bring it back in along with some of the strengths of core Mark Three about being (mumbles). >> I mean the cognitive is really interesting. It's a programmatic approach to life. And, if you think about it, it's like if you have this collective intelligence with the data, you could offer an augmented reality experience- >> Andy: Yes. >> To anybody now, based upon what you're doin'. >> Absolutely. So I mean, I think that the toughest part I think right now is figuring out which of the opportunities to pursue. Because, there are so many out there and everyone has some interest in some degree, you know. You have to figure out how to prioritize about, you know, which, which of the ones you want to address first. >> John: Yeah. >> And, in what order. Because, what we've noticed is that a lot of these are building blocks that lead to other greater and greater platform concepts, and part of the challenge is figuring out what order you want to actually build these into. And, through you know, microservices through retainerization all these, you know, awesome evolutions as far as like with cloud and infrastructure technology, you're really able to piece together these pieces to build amazing (mumbles) quickly. >> The cloud native stuff is booming right now. >> Yeah. >> It's really fun to watch. Microservices, (mumbles), this orchestration, composability is just kickin' ass. >> Absolutely. >> And, all your clients are basically becoming software companies. They're takin' your services and building out their own sas capabilities. >> Andy: Right. >> Right? >> Without a doubt. I mean, you know the cloud (mumbles), container revolution's been significant for us. I mean we, we added the audio component to video recon based on some of the work we've been doing on the call center side. It was almost by accident. And, we were able to really put them together in a day because we were able to basically easily compose the overall platform at that time, or the prototype of the platform at that time just by linking together those services. So, we see this as a pattern moving forward. >> Andy, thanks for coming on The Cube. Really appreciate it. In the quick 30 seconds, what are you doin' here at the show? What are you guys talkin' about? What's some of the activity? Coolest thing you're seeing? Share some insight, what's going on here in Las Vegas. Share some perspective. >> Yeah, absolutely. So, we have a booth here in Vegas. We're demoing some of the platforms we talked about: video recon, cognitive call center. We're at booth six 87, which is toward the center back of the expo center. We have four break outs that we'll be doing as well. Talking about some of these concepts, as well as some of our projects that involve, you know, modernization of the data center as well. So, the true what I call IBM full stack. >> And, for the folks that aren't here watching, is there, the website address? Where can they go to get more information? >> Yeah, absolutely. You can go to Mark Three sys. M A R K triple I S Y S dot com, which is our website. If you want to learn a little bit more about video recon you can go to video recon dot I O. We have a very simple demo page, but you know, if you're interested in learning more or you want to explore if we can accommodate your specific use case, please feel free to reach out to me. Also, Mark Three systems, M A R K triple I systems at Twitter as well, and I can get back to you. >> Well, you know we're going to follow up with you. Going to get all of our Cube videos into the cognitive era. You'll be seeing us, pinging you online for that. >> Yeah. >> Love the video recon, just great. BlueChasm, great, great initiative. Congratulations on that. >> Thank you. >> Thanks for comin' on. Its The Cube live here in Las Vegas. Day two of coverage, wall to wall. I'm John Furrier with Dave Vellante. Stay with us. More great interviews after this short break.

>>Welcome to the Cube's Continuing coverage of AMD's fourth generation Epic launch. I'm Dave Nicholson and I'm joining you here in our Palo Alto Studios. We have two very interesting guests to dive into some of the announcements that have been made and maybe take a look at this from an AI and ML perspective. Our first guest is Milland Doley. He's a senior director for software and solutions at amd, and we're also joined by Shamus Jones, who's a director of server engineering at Dell Technologies. Welcome gentlemen. How are you? >>Very good, thank >>You. Welcome to the Cube. So let's start out really quickly, Shamus, what, give us a thumbnail sketch of what you do at Dell. >>Yeah, so I'm the director of technical marketing engineering here at Dell, and our team really takes a look at the technical server portfolio and solutions and ensures that we can look at, you know, the performance metrics, benchmarks, and performance characteristics, so that way we can give customers a good idea of what they can expect from the server portfolio when they're looking to buy Power Edge from Dell. >>Milland, how about you? What's, what's new at a M D? What do you do there? >>Great to be here. Thank you for having me at amd, I'm the senior director of performance engineering and ISV ecosystem enablement, which is a long winter way of saying we do a lot of benchmarks, improved performance and demonstrate with wonderful partners such as Shamus and Dell, the combined leverage that AMD four generation processes and Dell systems can bring to bear on a multitude of applications across the industry spectrum. >>Shamus, talk about that relationship a little bit more. The relationship between a M D and Dell. How far back does it go? What does it look like in practical terms? >>Absolutely. So, you know, ever since AM MD reentered the server space, we've had a very close relationship. You know, it's one of those things where we are offering solutions that are out there to our customers no matter what generation A portfolio, if they're, if they're demanding either from their competitor or a m d, we offer a portfolio solutions that are out there. What we're finding is that within their generational improvements, they're just getting better and better and better. Really exciting things happening from a m D at the moment, and we're seeing that as we engineer those CPU stacks into our, our server portfolio, you know, we're really seeing unprecedented performance across the board. So excited about the, the history, you know, my team and Lin's team work very closely together, so much so that we were communicating almost on a daily basis around portfolio platforms and updates around the, the, the benchmarks testing and, and validation efforts. >>So Melind, are you happy with these PowerEdge boxes that Seamus is building to, to house, to house your baby? >>We are delighted, you know, it's hard to find stronger partners than Shamus and Dell with AMD's, second generation epic service CPUs. We already had undisputable industry performance leadership, and then with the third and now the fourth generation CPUs, we've just increased our lead with competition. We've got so many outstanding features at the platform, at the CPU level, everybody focuses on the high core counts, but there's also the DDR five, the memory, the io, and the storage subsystem. So we believe we have a fantastic performance and performance per dollar performance per what edge over competition, and we look to partners such as Dell to help us showcase that leadership. >>Well. So Shay Yeah, through Yeah, go ahead >>Dave. What, what I'd add, Dave, is that through the, the partnership that we've had, you know, we've been able to develop subsystems and platform features that historically we couldn't have really things around thermals power efficiency and, and efficiency within the platform. That means that customers can get the most out of their compute infrastructure. >>So this is gonna be a big question moving forward as next generation platforms are rolled out, there's the potential for people to have sticker shock. You talk about something that has eight or 12 cores in a, in a physical enclosure versus 96 cores, and, and I guess the, the question is, do the ROI and TCO numbers look good for someone to make that upgrade? Shamus, you wanna, you wanna hit that first or you guys are integrated? >>Absolutely, yeah, sorry. Absolutely. So we, I'll tell you what, at the moment, customers really can't afford not to upgrade at the moment, right? We've taken a look at the cost basis of keeping older infrastructure in place, let's say five or seven year old infrastructure servers that are, that are drawing more power maybe are, are poorly utilized within the infrastructure and take more and more effort and time to manage, maintain and, and really keep in production. So as customers look to upgrade or refresh their platforms, what we're finding right is that they can take a dynamic consolidation sometimes 5, 7, 8 to one consolidation depending on which platform they have as a historical and which one they're looking to upgrade to. Within AI specifically and machine learning frameworks, we're seeing really unprecedented performance. Lin's team partnered with us to deliver multiple benchmarks for the launch, some of which we're still continuing to see the goodness from things like TP C X AI as a framework, and I'm talking about here specifically the CPU U based performance. >>Even though in a lot of those AI frameworks, you would also expect to have GPUs, which all of the four platforms that we're offering on the AM MD portfolio today offer multiple G P U offerings. So we're seeing a balance between a huge amount of C P U gain and performance, as well as more and more GPU offerings within the platform. That was real, that was a real challenge for us because of the thermal challenges. I mean, you think GPUs are going up 300, 400 watt, these CPUs at 96 core are, are quite demanding thermally, but what we're able to do is through some, some unique smart cooling engineering within the, the PowerEdge portfolio, we can take a look at those platforms and make the most efficient use case by having things like telemetry within the platform so that way we can dynamically change fan speeds to get customers the best performance without throttling based on their need. >>Melin the cube was at the Supercomputing conference in Dallas this year, supercomputing conference 2022, and a lot of the discussion was around not only advances in microprocessor technology, but also advances in interconnect technology. How do you manage that sort of research partnership with Dell when you aren't strictly just focusing on the piece that you are bringing to the party? It's kind of a potluck, you know, we, we, we, we mentioned P C I E Gen five or 5.0, whatever you want to call it, new DDR storage cards, Nicks, accelerators, all of those, all of those things. How do you keep that straight when those aren't things that you actually build? >>Well, excellent question, Dave. And you know, as we are developing the next platform, obviously the, the ongoing relationship is there with Dell, but we start way before launch, right? Sometimes it's multiple years before launch. So we are not just focusing on the super high core counts at the CPU level and the platform configurations, whether it's single socket or dual socket, we are looking at it from the memory subsystem from the IO subsystem, P c i lanes for storage is a big deal, for example, in this generation. So it's really a holistic approach. And look, core counts are, you know, more important at the higher end for some customers h HPC space, some of the AI applications. But on the lower end you have database applications or some other is s v applications that care a lot about those. So it's, I guess different things matter to different folks across verticals. >>So we partnered with Dell very early in the cycle, and it's really a joint co-engineering. Shamus talked about the focus on AI with TP C X xci, I, so we set five world records in that space just on that one benchmark with AD and Dell. So fantastic kick kick off to that across a multitude of scale factors. But PPP c Xci is not just the only thing we are focusing on. We are also collaborating with Dell and des e i on some of the transformer based natural language processing models that we worked on, for example. So it's not just a steep CPU story, it's CPU platform, es subsystem software and the whole thing delivering goodness across the board to solve end user problems in AI and and other verticals. >>Yeah, the two of you are at the tip of the spear from a performance perspective. So I know it's easy to get excited about world records and, and they're, they're fantastic. I know Shamus, you know, that, you know, end user customers might, might immediately have the reaction, well, I don't need a Ferrari in my data center, or, you know, what I need is to be able to do more with less. Well, aren't we delivering that also? And you know, you imagine you milland you mentioned natural, natural language processing. Shamus, are you thinking in 2023 that a lot more enterprises are gonna be able to afford to do things like that? I mean, what are you hearing from customers on this front? >>I mean, while the adoption of the top bin CPU stack is, is definitely the exception, not the rule today we are seeing marked performance, even when we look at the mid bin CPU offerings from from a m d, those are, you know, the most common sold SKUs. And when we look at customers implementations, really what we're seeing is the fact that they're trying to make the most, not just of dollar spend, but also the whole subsystem that Melin was talking about. You know, the fact that balanced memory configs can give you marked performance improvements, not just at the CPU level, but as actually all the way through to the, to the application performance. So it's, it's trying to find the correct balance between the application needs, your budget, power draw and infrastructure within the, the data center, right? Because not only could you, you could be purchasing and, and look to deploy the most powerful systems, but if you don't have an infrastructure that's, that's got the right power, right, that's a large challenge that's happening right now and the right cooling to deal with the thermal differences of the systems, might you wanna ensure that, that you can accommodate those for not just today but in the future, right? >>So it's, it's planning that balance. >>If I may just add onto that, right? So when we launched, not just the fourth generation, but any generation in the past, there's a natural tendency to zero in on the top bin and say, wow, we've got so many cores. But as Shamus correctly said, it's not just that one core count opn, it's, it's the whole stack. And we believe with our four gen CPU processor stack, we've simplified things so much. We don't have, you know, dozens and dozens of offerings. We have a fairly simple skew stack, but we also have a very efficient skew stack. So even, even though at the top end we've got 96 scores, the thermal budget that we require is fairly reasonable. And look, with all the energy crisis going around, especially in Europe, this is a big deal. Not only do customers want performance, but they're also super focused on performance per want. And so we believe with this generation, we really delivered not just on raw performance, but also on performance per dollar and performance per one. >>Yeah. And it's not just Europe, I'm, we're, we are here in Palo Alto right now, which is in California where we all know the cost of an individual kilowatt hour of electricity because it's quite, because it's quite high. So, so thermals, power cooling, all of that, all of that goes together and that, and that drives cost. So it's a question of how much can you get done per dollar shame as you made the point that you, you're not, you don't just have a one size fits all solution that it's, that it's fit for function. I, I'm, I'm curious to hear from you from the two of you what your thoughts are from a, from a general AI and ML perspective. We're starting to see right now, if you hang out on any kind of social media, the rise of these experimental AI programs that are being presented to the public, some will write stories for you based on prom, some will create images for you. One of the more popular ones will create sort of a, your superhero alter ego for, I, I can't wait to do it, I just got the app on my phone. So those are all fun and they're trivial, but they sort of get us used to this idea that, wow, these systems can do things. They can think on their own in a certain way. W what do, what do you see the future of that looking like over the next year in terms of enterprises, what they're going to do for it with it >>Melan? Yeah, I can go first. Yeah, yeah, yeah, yeah, >>Sure. Yeah. Good. >>So the couple of examples, Dave, that you mentioned are, I, I guess it's a blend of novelty and curiosity. You know, people using AI to write stories or poems or, you know, even carve out little jokes, check grammar and spelling very useful, but still, you know, kind of in the realm of novelty in the mainstream, in the enterprise. Look, in my opinion, AI is not just gonna be a vertical, it's gonna be a horizontal capability. We are seeing AI deployed across the board once the models have been suitably trained for disparate functions ranging from fraud detection or anomaly detection, both in the financial markets in manufacturing to things like image classification or object detection that you talked about in, in the sort of a core AI space itself, right? So we don't think of AI necessarily as a vertical, although we are showcasing it with a specific benchmark for launch, but we really look at AI emerging as a horizontal capability and frankly, companies that don't adopt AI on a massive scale run the risk of being left behind. >>Yeah, absolutely. There's an, an AI as an outcome is really something that companies, I, I think of it in the fact that they're adopting that and the frameworks that you're now seeing as the novelty pieces that Melin was talking about is, is really indicative of the under the covers activity that's been happening within infrastructures and within enterprises for the past, let's say 5, 6, 7 years, right? The fact that you have object detection within manufacturing to be able to, to be able to do defect detection within manufacturing lines. Now that can be done on edge platforms all the way at the device. So you're no longer only having to have things be done, you know, in the data center, you can bring it right out to the edge and have that high performance, you know, inferencing training models. Now, not necessarily training at the edge, but the inferencing models especially, so that way you can, you know, have more and, and better use cases for some of these, these instances things like, you know, smart cities with, with video detection. >>So that way they can see, especially during covid, we saw a lot of hospitals and a lot of customers that were using using image and, and spatial detection within their, their video feeds to be able to determine who and what employees were at risk during covid. So there's a lot of different use cases that have been coming around. I think the novelty aspect of it is really interesting and I, I know my kids, my daughters love that, that portion of it, but really what's been happening has been exciting for quite a, quite a period of time in the enterprise space. We're just now starting to actually see those come to light in more of a, a consumer relevant kind of use case. So the technology that's been developed in the data center around all of these different use cases is now starting to feed in because we do have more powerful compute at our fingertips. We do have the ability to talk more about the framework and infrastructure that's that's right out at the edge. You know, I know Dave in the past you've said things like the data center of, you know, 20 years ago is now in my hand as, as my cell phone. That's right. And, and that's, that's a fact and I'm, it's exciting to think where it's gonna be in the next 10 or 20 years. >>One terabyte baby. Yeah. One terabyte. Yeah. It's mind bo. Exactly. It's mind boggling. Yeah. And it makes me feel old. >>Yeah, >>Me too. And, and that and, and Shamus, that all sounded great. A all I want is a picture of me as a superhero though, so you guys are already way ahead of the curve, you know, with, with, with that on that note, Seamus wrap us up with, with a, with kind of a summary of the, the highlights of what we just went through in terms of the performance you're seeing out of this latest gen architecture from a md. >>Absolutely. So within the TPC xai frameworks that Melin and my team have worked together to do, you know, we're seeing unprecedented price performance. So the fact that you can get 220% uplift gen on gen for some of these benchmarks and, you know, you can have a five to one consolidation means that if you're looking to refresh platforms that are historically legacy, you can get a, a huge amount of benefit, both in reduction in the number of units that you need to deploy and the, the amount of performance that you can get per unit. You know, Melinda had mentioned earlier around CPU performance and performance per wat, specifically on the Tu socket two U platform using the fourth generation a m d Epic, you know, we're seeing a 55% higher C P U performance per wat that is that, you know, when for people who aren't necessarily looking at these statistics, every generation of servers, that that's, that is a huge jump leap forward. >>That combined with 121% higher spec scores, you know, as a benchmark, those are huge. Normally we see, let's say a 40 to 60% performance improvement on the spec benchmarks, we're seeing 121%. So while that's really impressive at the top bin, we're actually seeing, you know, large percentile improvements across the mid bins as well, you know, things in the range of like 70 to 90% performance improvements in those standard bins. So it, it's a, it's a huge performance improvement, a power efficiency, which means customers are able to save energy, space and time based on, on their deployment size. >>Thanks for that Shamus, sadly, gentlemen, our time has expired. With that, I want to thank both of you. It's a very interesting conversation. Thanks for, thanks for being with us, both of you. Thanks for joining us here on the Cube for our coverage of AMD's fourth generation Epic launch. Additional information, including white papers and benchmarks plus editorial coverage can be found on does hardware matter.com.

>>Hello, everyone. Welcome to the Cube's live coverage here in Boston, Massachusetts for AWS reinforce 2022. I'm John fur, host of the cube with Dave. Valante my co-host for breaking analysis, famous podcast, Dave, great to see you. Um, Beck in Boston, 2010, we started >>The queue. It all started right here in this building. John, >>12 years ago, we started here, but here, you know, just 12 years, it just seems like a marathon with the queue. Over the years, we've seen many ways. You call yourself a historian, which you are. We are both now, historians security is doing over. And we said in 2013 is security to do where we asked pat GSK. Now the CEO of Intel prior to that, he was the CEO of VMware. This is the security show fors. It's called the reinforce. They have reinvent, which is their big show. Now they have these, what they call reshow, re Mars, machine learning, automation, um, robotics and space. And then they got reinforced, which is security. It's all about security in the cloud. So great show. Lot of talk about the keynotes were, um, pretty, I wouldn't say generic on one hand, but specific in the other clear AWS posture, we were both watching. What's your take? >>Well, John, actually looking back to may of 2010, when we started the cube at EMC world, and that was the beginning of this massive boom run, uh, which, you know, finally, we're starting to see some, some cracks of the armor. Of course, we're threats of recession. We're in a recession, most likely, uh, in inflationary pressures, interest rate hikes. And so, you know, finally the tech market has chilled out a little bit and you have this case before we get into the security piece of is the glass half full or half empty. So budgets coming into this year, it was expected. They would grow at a very robust eight point half percent CIOs have tuned that down, but it's still pretty strong at around 6%. And one of the areas that they really have no choice, but to focus on is security. They moved everything into the cloud or a lot of stuff into the cloud. >>They had to deal with remote work and that created a lot of security vulnerabilities. And they're still trying to figure that out and plug the holes with the lack of talent that they have. So it's interesting re the first reinforc that we did, which was also here in 2019, Steven Schmidt, who at the time was chief information security officer at Amazon web services said the state of cloud security is really strong. All this narrative, like the pat Gelsinger narrative securities, a do over, which you just mentioned, security is broken. It doesn't help the industry. The state of cloud security is very strong. If you follow the prescription. Well, see, now Steven Schmidt, as you know, is now chief security officer at Amazon. So we followed >>Jesse all Amazon, not just AWS. So >>He followed Jesse over and I asked him, well, why no, I, and they said, well, he's responsible now for physical security. Presumably the warehouses I'm like, well, wait a minute. What about the data centers? Who's responsible for that? So it's kind of funny, CJ. Moses is now the CSO at AWS and you know, these events are, are good. They're growing. And it's all about best practices, how to apply the practices. A lot of recommendations from, from AWS, a lot of tooling and really an ecosystem because let's face it. Amazon doesn't have the breadth and depth of tools to do it alone. >>And also the attendance is interesting, cuz we are just in New York city for the, uh, ado summit, 19,000 people, massive numbers, certainly in the pandemic. That's probably one of the top end shows and it was a summit. This is a different audience. It's security. It's really nerdy. You got OT, you got cloud. You've got on-prem. So now you have cloud operations. We're calling super cloud. Of course we're having our inaugural pilot event on August 9th, check it out. We're called super cloud, go to the cube.net to check it out. But this is the super cloud model evolving with security. And what you're hearing today, Dave, I wanna get your reaction to this is things like we've got billions of observational points. We're certainly there's no perimeter, right? So the perimeter's dead. The new perimeter, if you will, is every transaction at scale. So you have to have a new model. So security posture needs to be rethought. They actually said that directly on the keynote. So security, although numbers aren't as big as last week or two weeks ago in New York still relevant. So alright. There's sessions here. There's networking. Very interesting demographic, long hair. Lot of >>T-shirts >>No lot of, not a lot of nerds doing to build out things over there. So, so I gotta ask you, what's your reaction to this scale as the new advantage? Is that a tailwind or a headwind? What's your read? >>Well, it is amazing. I mean he actually, Steven Schmidt talked about quadrillions of events every month, quadrillions 15 zeros. What surprised me, John. So they, they, Amazon talks about five areas, but by the, by the way, at the event, they got five tracks in 125 sessions, data protection and privacy, GRC governance, risk and compliance, identity network security and threat detection. I was really surprised given the focus on developers, they didn't call out container security. I would've thought that would be sort of a separate area of focus, but to your point about scale, it's true. Amazon has a scale where they'll see events every day or every month that you might not see in a generation if you just kind of running your own data center. So I do think that's, that's, that's, that's a, a, a, a valid statement having said that Amazon's got a limited capability in terms of security. That's why they have to rely on the ecosystem. Now it's all about APIs connecting in and APIs are one of the biggest security vulnerability. So that's kind of, I, I I'm having trouble squaring that circle. >>Well, they did just to come up, bring back to the whole open source and software. They did say they did make a measurement was store, but at the beginning, Schmidt did say that, you know, besides scale being an advantage for Amazon with a quadri in 15 zeros, don't bolt on security. So that's a classic old school. We've heard that before, right. But he said specifically, weave in security in the dev cycles. And the C I C D pipeline that is, that basically means shift left. So sneak is here, uh, company we've covered. Um, and they, their whole thing is shift left. That implies Docker containers that implies Kubernetes. Um, but this is not a cloud native show per se. It's much more crypto crypto. You heard about, you know, the, uh, encrypt everything message on the keynote. You heard, um, about reasoning, quantum, quantum >>Skating to the puck. >>Yeah. So yeah, so, you know, although the middleman is logged for J heard that little little mention, I love the quote from Lewis Hamilton that they put up on stage CJ, Moses said, team behind the scenes make it happen. So a big emphasis on teamwork, big emphasis on don't bolt on security, have it in the beginning. We've heard that before a lot of threat modeling discussions, uh, and then really this, you know, the news around the cloud audit academy. So clearly skills gap, more threats, more use cases happening than ever before. >>Yeah. And you know, to your point about, you know, the teamwork, I think the problem that CISOs have is they just don't have the talent to that. AWS has. So they have a real difficulty applying that talent. And so but's saying, well, join us at these shows. We'll kind of show you how to do it, how we do it internally. And again, I think when you look out on this ecosystem, there's still like thousands and thousands of tools that practitioners have to apply every time. There's a tool, there's a separate set of skills to really understand that tool, even within AWS's portfolio. So this notion of a shared responsibility model, Amazon takes care of, you know, securing for instance, the physical nature of S3 you're responsible for secure, make sure you're the, the S3 bucket doesn't have public access. So that shared responsibility model is still very important. And I think practitioners still struggling with all this complexity in this matrix of tools. >>So they had the layered defense. So, so just a review opening keynote with Steve Schmidt, the new CSO, he talked about weaving insecurity in the dev cycles shift left, which is the, I don't bolt it on keep in the beginning. Uh, the lessons learned, he talked a lot about over permissive creates chaos, um, and that you gotta really look at who has access to what and why big learnings there. And he brought up the use cases. The more use cases are coming on than ever before. Um, layered defense strategy was his core theme, Dave. And that was interesting. And he also said specifically, no, don't rely on single security control, use multiple layers, stronger together. Be it it from the beginning, basically that was the whole ethos, the posture, he laid that down >>And he had a great quote on that. He said, I'm sorry to interrupt single controls. And binary states will fail guaranteed. >>Yeah, that's a guarantee that was basically like, that's his, that's not a best practice. That's a mandate. <laugh> um, and then CJ, Moses, who was his deputy in the past now takes over a CSO, um, ownership across teams, ransomware mitigation, air gaping, all that kind of in the weeds kind of security stuff. You want to check the boxes on. And I thought he did a good job. Right. And he did the news. He's the new CISO. Okay. Then you had lean is smart from Mongo DB. Come on. Yeah. Um, she was interesting. I liked her talk, obviously. Mongo is one of the ecosystem partners headlining game. How do you read into that? >>Well, I, I I'm, its really interesting. Right? You didn't see snowflake up there. Right? You see data breaks up there. You had Mongo up there and I'm curious is her and she's coming on the cube tomorrow is her primary role sort of securing Mongo internally? Is it, is it securing the Mongo that's running across clouds. She's obviously here talking about AWS. So what I make of it is, you know, that's, it's a really critical partner. That's driving a lot of business for AWS, but at the same time it's data, they talked about data security being one of the key areas that you have to worry about and that's, you know what Mongo does. So I'm really excited. I talked to her >>Tomorrow. I, I did like her mention a big idea, a cube alumni, yeah. Company. They were part of our, um, season one of our eight of us startup showcase, check out AWS startups.com. If you're watching this, we've been doing now, we're in season two, we're featuring the fastest growing hottest startups in the ecosystem. Not the big players, that's ISVs more of the startups. They were mentioned. They have a great product. So I like to mention a big ID. Um, security hub mentioned a config. They're clearly a big customer and they have user base, a lot of E C, two and storage going on. People are building on Mongo so I can see why they're in there. The question I want to ask you is, is Mongo's new stuff in line with all the upgrades in the Silicon. So you got graviton, which has got great stuff. Um, great performance. Do you see that, that being a key part of things >>Well, specifically graviton. So I I'll tell you this. I'll tell you what I know when you look at like snowflake, for instance, is optimizing for graviton. For certain workloads, they actually talked about it on their earnings call, how it's lowered the cost for customers and actually hurt their revenue. You know, they still had great revenue, but it hurt their revenue. My sources indicate to me that that, that Mongo is not getting as much outta graviton two, but they're waiting for graviton three. Now they don't want to make that widely known because they don't wanna dis AWS. But it's, it's probably because Mongo's more focused on analytics. But so to me, graviton is the future. It's lower cost. >>Yeah. Nobody turns off the database. >>Nobody turns off the database. >><laugh>, it's always cranking C two cycles. You >>Know the other thing I wanted to bring, bring up, I thought we'd hear, hear more about ransomware. We heard a little bit of from Kirk Coel and he, and he talked about all these things you could do to mitigate ransomware. He didn't talk about air gaps and that's all you hear is how air gap. David Flo talks about this all the time. You must have air gaps. If you wanna, you know, cover yourself against ransomware. And they didn't even mention that. Now, maybe we'll hear that from the ecosystem. That was kind of surprising. Then I, I saw you made a note in our shared doc about encryption, cuz I think all the talk here is encryption at rest. What about data in motion? >>Well, this, this is the last guy that came on the keynote. He brought up encryption, Kurt, uh, Goel, which I love by the way he's VP of platform. I like his mojo. He's got the long hair >>And he's >>Geeking out swagger, but I, he hit on some really cool stuff. This idea of the reasoning, right? He automated reasoning is little pet project that is like killer AI. That's next generation. Next level >>Stuff. Explain that. >>So machine learning does all kinds of things, you know, goes to sit pattern, supervise, unsupervised automate stuff, but true reasoning. Like no one connecting the dots with software. That's like true AI, right? That's really hard. Like in word association, knowing how things are connected, looking at pattern and deducing things. So you predictive analytics, we all know comes from great machine learning. But when you start getting into deduction, when you say, Hey, that EC two cluster never should be on the same VPC, is this, this one? Why is this packet trying to go there? You can see patterns beyond normal observation space. So if you have a large observation space like AWS, you can really put some killer computer science technology on this. And that's where this reasoning is. It's next level stuff you don't hear about it because nobody does it. Yes. I mean, Google does it with metadata. There's meta meta reasoning. Um, we've been, I've been watching this for over two decades now. It's it's a part of AI that no one's tapped and if they get it right, this is gonna be a killer part of the automation. So >>He talked about this, basically it being advanced math that gets you to provable security, like you gave an example. Another example I gave is, is this S3 bucket open to the public is a, at that access UN restricted or unrestricted, can anyone access my KMS keys? So, and you can prove, yeah. The answer to that question using advanced math and automated reasoning. Yeah, exactly. That's a huge leap because you used to be use math, but you didn't have the data, the observation space and the compute power to be able to do it in near real time or real time. >>It's like, it's like when someone, if in the physical world real life in real life, you say, Hey, that person doesn't belong here. Or you, you can look at something saying that doesn't fit <laugh> >>Yeah. Yeah. >>So you go, okay, you observe it and you, you take measures on it or you query that person and say, why you here? Oh, okay. You're here. It doesn't fit. Right. Think about the way on the right clothes, the right look, whatever you kind of have that data. That's deducing that and getting that information. That's what reasoning is. It's it's really a killer level. And you know, there's encrypt, everything has to be data. Lin has to be data in at movement at rest is one thing, but you gotta get data in flight. Dave, this is a huge problem. And making that work is a key >>Issue. The other thing that Kirk Coel talked about was, was quantum, uh, quantum proof algorithms, because basically he put up a quote, you're a hockey guy, Wayne Greski. He said the greatest hockey player ever. Do you agree? I do agree. Okay, great. >>Bobby or, and Wayne Greski. >>Yeah, but okay, so we'll give the nada Greski, but I always skate to the where the puck is gonna be not to where it's been. And basically his point was where skating to where quantum is going, because quantum, it brings risks to basically blow away all the existing crypto cryptographic algorithms. I, I, my understanding is N just came up with new algorithms. I wasn't clear if those were supposed to be quantum proof, but I think they are, and AWS is testing them. And AWS is coming out with, you know, some test to see if quantum can break these new algos. So that's huge. The question is interoperability. Yeah. How is it gonna interact with all the existing algorithms and all the tools that are out there today? So I think we're a long way off from solving that problem. >>Well, that was one of Kurt's big point. You talking about quantum resistant cryptography and they introduce hybrid post quantum key agreements. That means KMS cert certification, cert manager and manager all can manage the keys. This was something that's gives more flexibility on, on, on that quantum resistance argument. I gotta dig into it. I really don't know how it works, what he meant by that in terms of what does that hybrid actually mean? I think what it means is multi mode and uh, key management, but we'll see. >>So I come back to the ho the macro for a second. We've got consumer spending under pressure. Walmart just announced, not great earning. Shouldn't be a surprise to anybody. We have Amazon meta and alphabet announcing this weekend. I think Microsoft. Yep. So everybody's on edge, you know, is this gonna ripple through now? The flip side of that is BEC because the economy yeah. Is, is maybe not in, not such great shape. People are saying maybe the fed is not gonna raise after September. Yeah. So that's, so that's why we come back to this half full half empty. How does that relate to cyber security? Well, people are prioritizing cybersecurity, but it's not an unlimited budget. So they may have to steal from other places. >>It's a double whammy. Dave, it's a double whammy on the spend side and also the macroeconomic. So, okay. We're gonna have a, a recession that's predicted the issue >>On, so that's bad on the one hand, but it's good from a standpoint of not raising interest rates, >>It's one of the double whammy. It was one, it's one of the double whammy and we're talking about here, but as we sit on the cube two weeks ago at <inaudible> summit in New York, and we did at re Mars, this is the first recession where the cloud computing hyperscale is, are pumping full cylinder, all cylinders. So there's a new economic engine called cloud computing that's in place. So unlike data center purchase in the past, that was CapEx. When, when spending was hit, they pause was a complete shutdown. Then a reboot cloud computer. You can pause spending for a little bit, make, might make the cycle longer in sales, but it's gonna be quickly fast turned on. So, so turning off spending with cloud is not that hard to do. You can hit pause and like check things out and then turn it back on again. So that's just general cloud economics with security though. I don't see the spending slowing down. Maybe the sales cycles might go longer, but there's no spending slow down in my mind that I see. And if there's any pause, it's more of refactoring, whether it's the crypto stuff or new things that Amazon has. >>So, so that's interesting. So a couple things there. I do think you're seeing a slight slow down in the, the, the ex the velocity of the spend. When you look at the leaders in spending velocity in ETR data, CrowdStrike, Okta, Zscaler, Palo Alto networks, they're all showing a slight deceleration in spending momentum, but still highly elevated. Yeah. Okay. So, so that's a, I think now to your other point, really interesting. What you're saying is cloud spending is discretionary. That's one of the advantages. I can dial it down, but track me if I'm wrong. But most of the cloud spending is with reserved instances. So ultimately you're buying those reserved instances and you have to spend over a period of time. So they're ultimately AWS is gonna see that revenue. They just might not see it for this one quarter. As people pull back a little bit, right. >>It might lag a little bit. So it might, you might not see it for a quarter or two, so it's impact, but it's not as severe. So the dialing up, that's a key indicator get, I think I'm gonna watch that because that's gonna be something that we've never seen before. So what's that reserve now the wild card and all this and the dark horse new services. So there's other services besides the classic AC two, but security and others. There's new things coming out. So to me, this is absolutely why we've been saying super cloud is a thing because what's going on right now in security and cloud native is there's net new functionality that needs to be in place to handle multiple clouds, multiple abstraction layers, and to do all these super cloudlike capabilities like Mike MongoDB, like these vendors, they need to up their gain. And that we're gonna see new cloud native services that haven't exist. Yeah. I'll use some hatchy Corp here. I'll use something over here. I got some VMware, I got this, but there's gaps. Dave, there'll be gaps that are gonna emerge. And I think that's gonna be a huge wild >>Cup. And now I wanna bring something up on the super cloud event. So you think about the layers I, as, uh, PAs and, and SAS, and we see super cloud permeating, all those somebody ask you, well, because we have Intuit coming on. Yep. If somebody asks, why Intuit in super cloud, here's why. So we talked about cloud being discretionary. You can dial it down. We saw that with snowflake sort of Mongo, you know, similarly you can, if you want dial it down, although transaction databases are to do, but SAS, the SAS model is you pay for it every month. Okay? So I've, I've contended that the SAS model is not customer friendly. It's not cloudlike and it's broken for customers. And I think it's in this decade, it's gonna get fixed. And people are gonna say, look, we're gonna move SAS into a consumption model. That's more customer friendly. And that's something that we're >>Gonna explore in the super cloud event. Yeah. And one more thing too, on the spend, the other wild card is okay. If we believe super cloud, which we just explained, um, if you don't come to the August 9th event, watch the debate happen. But as the spending gets paused, the only reason why spending will be paused in security is the replatforming of moving from tools to platforms. So one of the indicators that we're seeing with super cloud is a flight to best of breeds on platforms, meaning hyperscale. So on Amazon web services, there's a best of breed set of services from AWS and the ecosystem on Azure. They have a few goodies there and customers are making a choice to use Azure for certain things. If they, if they have teams or whatever or office, and they run all their dev on AWS. So that's kind of what's happened. So that's, multi-cloud by our definition is customers two clouds. That's not multi-cloud, as in things are moving around. Now, if you start getting data planes in there, these customers want platforms. If I'm a cybersecurity CSO, I'm moving to platforms, not just tools. So, so maybe CrowdStrike might have it dial down, but a little bit, but they're turning into a platform. Splunk trying to be a platform. Okta is platform. Everybody's scale is a platform. It's a platform war right now, Dave cyber, >>A right paying identity. They're all plat platform, beach products. We've talked about that a lot in the queue. >>Yeah. Well, great stuff, Dave, let's get going. We've got two days alive coverage. Here is a cubes at, in Boston for reinforc 22. I'm Shante. We're back with our guests coming on the queue at the short break.

>>Welcome everyone to this cube conversation featuring unit Q. I'm your host, Lisa Martin. And we are excited to be joined by Christian Vickle, the founder and CEO of unit Q Christian. Thank you so much for joining me today. >>Thank you so much, Lisa pleasure to be here. >>Let's talk a little bit about unit Q. You guys were founded in 2018, so pretty recent. What is it that unit Q does. And what were some of the gaps in the market that led you to founding the company? >>Yep. So me and my co-founder Nick, we're actually doing our second company now is the unit Q is number two, and our first company was called scout years ago. We were back ES wicks and it was very different from unit Q. It's a social network for meeting people. And it was really during that experience where we saw the impact that quality of the experience quality of the product can have on your growth trajectory and the challenges we faced. How do we test everything before we ship it? And in reality, a modern company will have, let's say, 20 languages supported you support Android, Iowas, web big screen, small screen, you have 20 plus integrations and you have lots of different devices out there that might run your binary a little differently. So who is the ultimate test group of all of these different permutation and that's the end user. >>And we, we saw the, the big gap in the market, sort of the dream platform for us was unit queue. So if, if this would've existed back in the day, we would've been a, a happy purchaser and customer, and it really comes down to how do we, how do we harness the power of user feedback? You know, the end user, that's testing your product every single day in all different configurations. And then they're telling you that, Hey, something didn't work for me. I got double build or the passive recent link didn't work, or I couldn't, you know, when music, when the ad is finished playing on, on my app, the music doesn't resume. So how do we capture those signals into something that the company and different teams can align on? So that's where, you know, unit Q the, the vision here is to build a quality company, to help other companies build higher quality products. >>So really empowering companies to take a data driven approach to product quality. I was looking on your website and noticed that Pandora is one of your customers, but talk to me a little bit about a customer example that you think really articulates the value of what Q unit he was delivering. >>Right? So maybe we should just go back one little step and talk about what is quality. And I think quality is something that is, is a bit subjective. It's something that we live and breathe every day. It's something that can be formed in an instant first impressions. Last it's something that can be built over time that, Hey, I'm using this product and it's just not working for me. Maybe it's missing features. Maybe there are performance related bots. Maybe there is there's even fulfillment related issues. Like we work with Uber and hello, fresh and, and other types of more hybrid type companies in addition to the Pandoras and, and Pinterest and, and Spotify, and these more digital, only products, but the, the end users I'm producing this data, the reporting, what is working and not working out there in many different channels. So they will leave app produce. >>They will write into support. They might engage with a chat support bot. They will post stuff on Reddit on Twitter. They will comment on Facebook ads. So like this data is dispersed everywhere. The end user is not gonna fill out a perfect bug report in a form somewhere that gets filed into gr like they're, they're producing this content everywhere in different languages. So the first value of what we do is to just ingest all of that data. So all the entire surface area of use of feedback, we ingest into a machine and then we clean the data. We normalize it, and then we translate everything into English. And it was actually a surprise to us when we started this company, that there are quite a few companies out there that they're only looking at feedback in English. So what about my Spanish speaking users? What about my French speaking users? >>And when, when, when that is done, like when all of that data is, is need to organized, we extract signals from that around what is impacting the user experience right now. So we break these, all of this data down into something called quality monitors. So quality monitor is basically a topic which can be again, passive reset, link noting, or really anything that that's impacting the end user. And the important part here is that we need to have specific actionable data. For instance, if I tell you, Hey, Lisa music stops playing is a growing trend that our users are reporting. You will tell me, well, what can I do with that? Like what specifically is breaking? So we deploy up to 1500 unique quality monitors per customer. So we can then alert different teams inside of the organization of like, Hey, something broke and you should take a look at it. >>So it's really breaking down data silos within the company. It aligns cross-functional teams to agree on what should be fixed next. Cause there's typically a lot of confusion, you know, marketing, they might say, Hey, we want this fixed engineering. They're like, well, I can't reproduce, or that's not a high priority for us. The support teams might also have stuff that they want to get fixed. And what we've seen is that these teams, they struggle to communicate. So how do we align them around the single source of truth? And I think that's for unit two is early identification of stuff. That's not working in production and it's also aligning the teams so they can quickly triage and say, yes, we gotta fix this right before it snowballs into something. We say, you know, we wanna, we wanna cap catch issues before you go into crisis PR mode, right? So we want to get this, we wanna address it early in the cycle. >>Talk to me about when you're in customer conversations, Christian, the MarTech landscape is competitive. There's nearly 10,000 different solutions out there, and it's growing really quickly quality monitors that you just described is that one of the key things that, that you talk to customers about, that's a differentiator for unit Q. >>Yeah. So I mean, it, it, it comes down to, as you're building your product, right, you, you have, you have a few different options. One is to build new features and we need to build new features and innovate and, and, and that's all great. We also need to make sure that the foundation of the product is working and that we keep improving quality and what, what we see with, with basically every customer that we work with, that, that when quality goes up, it's supercharges the growth machine. So quality goes up, you're gonna see less support tickets. You're gonna see less one star reviews, less one star reviews is of course good for making the store front convert better. You know, I, I want install a 4.5 star app, not a 3.9 star app. We also see that sentiment. So for those who are interested in getting that NPS score up for the next time we measure it, we see that quality is of course a very important piece of that. >>And maybe even more importantly, so sort of inside of the product machine, the different conversion steps, let's say sign up to activate it to coming back in second day, 30 day, 90 day, and so forth. We see a dramatic impact on how quality sort of moves that up and down the retention function, if you will. So it, it really, if you think about a modern company, like the product is sort of the center of the existence of the company, and if the product performs really well, then you can spend more money in marketing because it converts really good. You can hire more engineers, you can hire, you can hire more support people and so forth. So it's, it's really cool to see that when quality improves its supercharges, everything else I think for marketing it's how do you know if you're spending into a broken product or not? >>And I, and I, I feel like marketing has, they have their insights, but it's, it's not deep enough where they can go to engineering and say, Hey, these 10 issues are impacting my MPS score and they're impacting my conversion and I would love for you to fix it. And when you can bring tangible impact, when you can bring real data to, to engineering and product, they move on it cause they also wanna help build the company. And, and so I think that's, that's how we stand out from the more traditional MarTech, because we need to fix the core of, of sort of this growth engine, which is the quality of the product >>Quality of the product. And obviously that's directly related to the customer experience. And we know these days, one of the things I think that's been in short supply the last couple of years is patience. We know when customers are unhappy with the product or service, and you talked about it a minute ago, they're gonna go right to, to Reddit or other sources to complain about that. So being able to, for uniq, to help companies to improve the customer experience, isn't I think table stakes for businesses it's mission critical these days. Yeah, >>It is mission critical. So if you look at the, let's say that we were gonna start a, a music app. Okay. So how do we, how do we compete as a music app? Well, if you, if you were to analyze all different music apps out there, they have more or less the same features app. Like they, the feature differentiation is minimal. And, and if you launch a new cool feature than your competitor will probably copy that pretty quickly as well. So competing with features is really hard. What about content? Well, I'm gonna get the same content on Spotify as apple SD. So competing with content is also really hard. What about price? So it turns out you'll pay 9 99 a month for music, but there's no, there's no 1 99. It's gonna be 9 99. So quality of the experience is one of the like last vectors or areas where you can actually compete. >>And we see consistently that if you' beating your competition on quality, you will do better. Like the best companies out there also have the highest quality experience. So it's, it's been, you know, for us at our last company, measuring quality was something that was very hard. How do we talk about it? And when we started this company, I went out and talked to a bunch of CEOs and product leaders and board members. And I said, how do you talk about quality in a board meeting? And they were, they said, well, we don't, we don't have any metrics. So actually the first thing we did was to define a metrics. We have, we have this thing called this unit Q score, which is on our website as well, where we can base it's like the credit score. So you can see your score between zero and a hundred. >>And if your score is 100, it means that we're finding no quality issues in the public domain. If your score is 90, it means that 10% of the data we look at refers to a quality issue. And the definition of a quality issue is quite simple. It is when the user experience doesn't match the user expectation. There is a gap in between, and we've actually indexed the 5,000 largest apps out there. So we're then looking at all the public review. So on our website, you can go in and, and look up the unit Q score for the 5,000 largest products. And we republish these every night. So it's an operational metric that changes all the time. >>Hugely impactful. Christian, thank you so much for joining me today, talking to the audience about unit Q, how you're turning qualitative feedback into pretty significant product improvements for your customers. We appreciate your insights. >>Thank you, Lisa, have a great day. >>You as well, per Christian Lin, I'm Lisa Martin. You're watching a cube conversation.

>> Narrator: From the CUBE Studios in Palo Alto, in Boston, connecting with thought leaders all around the world, this is a cube conversation. >> Hi, Lisa Martin here with Caitlin Gordon, the VP of product marketing for Dell technologies, Caitlin, welcome back to the CUBE, we're excited to see you again. >> Caitlyn: I'm very excited to be here again. >> So data protection in the news what's going on? >> Yeah, it's been a busy year, we had obviously our Power Protect DD appliance launch last year. And then this year we've had announcements on the software side. We had announcements at VMworld, some more at Dell Technologies World. And now today we're announcing even more which is the new Power Protect the DP series appliances the new integrated appliances. And it's really exciting. So we now have our Power Protect DD, the next generation of data domain, and we have our power protect DP appliances integrated appliances. And that's all about combining both protection storage, protects and software in a single converge, all in one offering. That's really popular with our customers today, because of the simplicity the ability to really modernize your data protection in a very simple way, get up really up and running quickly. And in fact, it's really the fastest growing part of the backup appliance market. >> Yeah, I have read that the integrated appliances our market is growing twice as fast as the targeted market. So give us a picture of what customers can expect from the new DP series. >> Yeah, it's not that dissimilar to actually our DD series from last year, which is there's four models in the new DP series. And it's really all about getting better performance, better efficiency. We've got new hardware, assisted compression, denser drives, and all that gives us the ability to get faster backups faster recovery, In fact, you get 38% faster up backups, 45% faster recovery, more logical capacity, 30% more logical capacity, 65 to one deduplication which is just incredible and 60,000 IOPS for instant access. So really ups the game, both in performance and efficiency. >> Those are big numbers. You mentioned the DD launch last year, contrast it with what you're announcing now. What's the significance of the DP series? >> This is exciting for us because it does a couple of things. It expands our power protect appliance family, with the new DP series of integrated appliances. But at the same time, we're also announcing other important Power Protect enhancements on the software side. Power Protect data manager which we've been enhancing and continuing to talk about all year also has some new improvements the ability to deploy it in Azure and AWS gov cloud for in-cloud protection. The enhancements that we've done with VMware that we talked about, not that long ago at VM world about being able to integrate with based policy management really automating and simplifying VMware protection. And it's really all about kuberetes, right? And the ability to support kubernetes as well. So not only is this an exciting appliance launch for us but it's also the marketing of yet even more enhancements on the Power Protect data manager side and all that together, it means that with Power Protect, you really have a one-stop shop for all of your data protection needs no matter where the data lives, no matter what SLA, whether it's a physical virtual appliance, whether it's target or integrated, you've all got them in the Power Protect family now. >> Excellent. All right. Last question for you Caitlin, we know Dell technologies is focused on three big waves, it's cloud VMware and cyber recovery. Anything else you want to add here? >> Cyber resiliency, cyber recovery Ransomware has really risen to the top of the list. Unfortunately for many organizations and Power Protect cyber recovery is really an important enhancement that we also have with this announcement today. We've had this offering in market for a couple years with the exciting new enhancement here. So it is the first cyber recovery solution endorsed by sheltered Harbor. And if you're not familiar with Power Protect cyber recovery it provides an automated air gaped solution for data isolation, and then cyber sense provides the analytics and the forensics for discovering, diagnosing, and remediating those attacks. So it's really all about ransomware protecting from, recovering from those attacks, which unfortunately have become all too common for our customers today. >> Excellent news Caitlin. Thanks for sharing. What's new congratulations to you and the Dell team. >> Thank you so much, Lisa, >> For Caitlin Gordon, I'm Lisa Martin. You're watching the cube. (outro music)

>>from around the globe. It's the Cube with digital coverage of workplace next made possible by Hewlett Packard Enterprise. >>Okay. Hey, we're coming to the end of our session here at workplace next. This is a really exciting part where you get to meet the experts. Now, if you're watching live, you actually can go in and speak to the experts directly. If you're seeing this on demand, you'll be ableto see what was said. You won't be able to, of course, interact live. So again, we call this segment, meet the experts, and we're gonna allow you Thio. Speak directly with them. You could click on that link and go into those individual rooms. Very excited. First introduced Jonah S. Tebow, who is a solution engineering manager at Aruba. He's an expert in wireless Is this area is going to see massive changes in the coming years. Jonah, can you tell people what to expect in your meet the expert session? >>You sure today we'll talk about how you can deal with working remotely how you can connect from home and be connected and reach all your resources in the office. Like actually, if you were in the office eso put me on a resource from a point, Next office will be here on actually >>questions. Awesome. Okay, so if you wanna talk Tiuna directly, just click on his room link and go have at it. Next. I want to introduce you Toe Lin Neese. Now Lynn is an HP fellow and chief technologist for the i o. T advisory practice at HBs Point next services. Now I'm here to tell you an HP fellow has not only achieved this status by being a leading technologist, I might even say exceptional technologist. But these individuals are visionaries and the edge of the i o. T. Is one of these areas that has mind bending potential. Lynn, thanks for being here. What can people expect from your meet the expert session? Okay, so in our meet the expert session, we're gonna be talking about some of the critical issues that we're seeing with our customers Honestly, in this whole back to work scenario and how they're tangling with the major strategic issues associated with how long is covert gonna last? How do they deal with business continuity? So very importantly, we've had dozens of engagements and some of the issues that air profound are things like privacy. How do I How do I provide social distancing? How toe provide, contact tracing and use technology toe automate some of that while at the same time preserving privacy Extremely interesting, extremely compelling right now for many of our customers. That's great, then, and you think about things like business Resiliency totally changed our thinking on privacy as well. So if you wanna talkto Lynn, we set up these little cube rooms for you. So click on Lin's link and go into his room and chat away. Now I'd like to introduce Mark White. Mark is, ah, platforms architect, and he focuses on the critical elements of a digital workplace. Now, this has become increasingly important since the pandemic and the entire work from home Pivot Mark, please set up what you're going to talk about and discuss in your meat the experts breakout session. >>Yeah, thanks. Day. So today we're gonna talk about how technologies can help provide remote access to these critical and secure resources. But wherever your work needs to be done, so the pandemic has changed how people work and people have to work remotely, so we'll look at how these technologies can also satisfy the very specialized requirements of power. Uses all power applications in your organization. >>That's critical, right? I might have. Resource is into the office that I may not have access to. And now, you guys, we're gonna talk about how to provide those. That's fantastic. Okay, so you know the drill. By now, we've set up these these little drill down rooms, these cube rooms. So if you wanna talk to mark, click on that link and have a chat. Okay? Now I'm gonna introduce you to Peter Menzel. Peter leads the digital workplace practice within HP ES point next services. He's got an amazing perspective on how remote workers can not only stay productive. I mean, that's really important, but also some of the other really important factors that organizations need to think about and consider when taking care of their employees that are working remotely. Peter, would you kindly share what you'll be discussing today in your meet the expert session? >>Yes. So delighted to be reviewed today, Dave. Great. Great. Thanks for the intro. And I'll meet the expert sessions. We're going to cover a lot of subjects around remote work In fact, our focus will be how do we help people work from any location at any time? We're gonna take a look at some of the challenges or additional challenges that customers have faced in 2020 on the need to move towards a smart working environment. You hear from some of our experts. We'll talk through some of the solutions and offerings that we have in this space, and then we'll close at the session, focusing on how technology can have a really big impact on the way we drive productivity and innovation in our jobs on in our organizations today. >>That's great. Looking forward to that. Thank you, Peter. And thanks to our experts, you know, the timing of this workplace next event is actually really good, because in March we just had to react. Now we have some timeto sit back and think about how we really wanna architect the workforce for the future. But so now it's your turn. So jump in to the meet the expert sessions and ask your questions. Have a great rest of your day

>> Okay. Hey, we're coming to the end of our session here at Workplace Next. And this is a really exciting part where you get to meet the experts. Now, if you're watching live, you actually can go in and speak to the experts directly, if you're seeing this on demand, you'll be able to see what was said, you won't be able to, of course interact live. So again, we call this segment, Meet the Experts, and we're going to allow you to speak directly with them, you can click on that link and go into those individual rooms. We're very excited first to introduce Jone Ostebo, who is the solution engineering manager at Aruba. He's an expert in wireless and is this area is going to see massive changes in the coming years. Jone, can you tell people what to expect in your Meet the Expert Session? >> Sure, today we'll talk about how you can deal with working remotely, how you can connect from home and be connected and reach all your resources in the office, like actually, if you were in the office. So both me and a resource from a Pointnext services would be here and answer all your questions. >> Awesome. Okay, so if you want to talk to Jone directly, just click on his room link and go have at it. Next, I want to introduce you to Lin Nease. Now Lin is an HPE fellow and chief technologist for the IoT advisory practice at HPE Pointnext services. Now I'm here to tell you, an HPE fellow has not only achieved this status by being a leading technologist, I might even say exceptional technologist. But these individuals are visionaries, and the edge in the IOT is one of these areas that has mind-bending potential. Lin, thanks for being here. What can people expect from your Meet the Experts Session? >> Thank you, Dave. So in our Meet the Expert Session, we're going to be talking about some of the critical issues that we're seeing with our customers, honestly, in this whole back to work scenario and how they're tangling with the, the major strategic issues associated with how long is COVID going to last? How do they deal with business continuity? So very importantly, we've had dozens of engagements and some of the issues that are profound are things like privacy. How do I provide social distancing? How to provide contact tracing and use technology to automate some of that? While at the same time, preserving privacy extremely interesting and extremely compelling right now for many of our customers. >> That's great Lin, and when you think about, you know, things like business resiliency totally changed our thinking and privacy as well, so if you want to talk to Lin, we've set up these little cube rooms for you so click on Lin's link and go into his room and chat away. Now I'd like to introduce Mark Wayt. Mark is a platforms architect, and he focuses on the critical elements of a digital workplace. Now this has become increasingly important since the pandemic and the entire from home pivot. Mark, please set up what you're going to talk about and discuss in your, Meet the Experts Breakout Session. >> Yeah. Thanks Dave. So today we're going to talk about how technologies can help provide remote access to these critical and secure resources, but wherever your work needs to be done. So the pandemic has changed how people work and people have to work remotely. So we'll look at how these technologies can also satisfy the very specialized requirements of power users or power applications in your organization. >> That's critical, right? I might have resources into the office that I may not have access to. And now you guys are going to talk about how to provide those. That's fantastic. Okay. So look at, you know, the drill by now, we've set up these little drill down rooms, these cube rooms. So if you want to talk to Mark, click on that link and have a chat. Okay, now I'm going to introduce you to Peter Mansell. Peter leads the digital workplace practice within HPE Pointnext services. He's got an amazing perspective on how remote workers can not only stay productive. I mean, that's really important, but also some of the other really important factors that organizations need to think about and consider when taking care of their employees that are working remotely. Peter, would you kindly share what you'll be discussing today in your Meet the Expert Session? >> Yeah, so delighted to be with you today, Dave. Great, thanks for the intro. And I'll Meet the Expert Sessions. We're going to cover all the subjects around remote work. In fact, our focus will be how do we help people work, from any location at any time? We're going to take a look at some of the challenges or additional challenges that customers have faced in 2020, and the need to move towards a smart work environment. You hear from some of our experts, we'll talk through some of the solutions and offerings that we have in this space. And then we'll close out the session, focusing on how technology can have a really big impact on the way we drive productivity and innovation in our jobs, and in our organizations today. >> That's great. Looking forward to that. Thank you, Peter. And thanks to our experts. You know, the timing of this Workplace Next event is actually really good because in March, we just had to react. Now we have some time to sit back and think about how we really want to architect the workforce for the future but, so now it's your turn. So jump in to the Meet the Expert Sessions and ask your questions. Have a great rest of your day. (upbeat music)

>> Announcer: From theCUBE Studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is "theCUBE' conversation. >> Hi, Lisa Martin here with Caitlin Gordon, the VP of Product Marketing for Dell Technologies. Caitlin, welcome back to 'theCUBE' I'm excited to see you again. >> I'm very excited to be here again. >> So data protection in the news, what's going on? >> Yeah you know, it's been a busy year. We had obviously our power protect DD appliance launched last year and then this year, we've have announcements on the software side. We had announcements at the VMworld some more at Dell Technologies world. And now today we're announcing even more, which is the new PowerProtect PP series appliances, the new integrated appliances. And it's really exciting. So we now have our PowerProtect DD,xx the next generation of data domain, and we have our PowerProtect DP appliances, integrated appliances. And that's all about combining both protection storage, protecting software in a single converge, all in one offering. It's really popular with our customers today because of the simplicity, the ability to really modernize your data protection in a very simple way, get up really up and running quickly. And in fact, it's really the fastest growing part of the back of appliance market. >> I have read that the integrated appliances, our market is growing twice as fast as the targeted market. So give us a picture of what customers can expect from the new DP series. >> Yeah, and it's not that dissimilar to actually our DD series from last year which is there's in four models in the new DP series. There's a 4,400 which is actually now taking the PowerProtect brand and putting that on the existing DP 4,400 and then three new appliances: the 5,900, the 8,400 and then the 8,900. And it's really all about getting better performance, better efficiency. We've got new hardware, assisted compression, denser drives, and all that gives us the ability to get faster backups, faster recovery, in fact you get 38% faster backups, 45% faster recovery, more logical capacity, 30% more logical capacity, 65 to one theater application, which is just incredible and 60,000 IOPS for instant access. So really ups the game, both in performance and an efficiency. >> Those are big numbers, you mentioned the DD launch last year, contrast it with what you're announcing now. What's the significance of the DP series? >> And that this is exciting for us because it does a couple things. It expands our PowerProtect appliance family with the new DP series of integrated appliances. But at the same time, we're also announcing other important PowerProtect enhancements. On the software side, PowerProtect data manager, which we've enhancing and continuing to talk about all year also has some new improvements. The ability deploy it in Azure, in AWS GovCloud for in-cloud protection. The enhancements that we've done with VMware that we talked about, not that long ago at VMworld about being able to integrate with storage based policy management, really automating and simplifying VMware protection. And it's really all about Kubernetes right And the ability to support Kubernetes as well. So not only is this an exciting appliance launch for us, but it's also the marketing of yet even more enhancements on the PowerProtect data manager side. And all that together means that with PowerProtect, you really have a one-stop shop for all of your data protection needs no matter where the data lives, no matter what SLA, whether it's a physical, virtual appliance, whether it's target or integrated, you've all bought them in the PowerProtect family now. >> Excellent. All right. Last question for you, Caitlin we know Dell Technologies is focused on three big waves, it's cloud VMware and Cyber Recovery. Anything else you want to add here? Yeah, I'll pick up, especially on that last one, we talke%d a little bit about the enhancements we've done with cloud in cloud data protection, longterm recovery, disaster recovery, as well as what we've done on the VMware front, really important that we continue to have that automation at simplicity with VM-ware but cyber resiliency, cyber recovery ransomware has really risen to the top of the list. Unfortunately for many organizations and PowerProtect cyber recovery is really an important enhancement that we also have with this announcement today. We've had this offer in market for a couple of years, with the exciting new enhancement here. It is the first cyber recovery solution and endorsed by Sheltered Harbor. So it is the first Cyber Recovery solution endorsed by Sheltered Harbor. And if you're not familiar with PowerProtect data, PowerProtect, if you're not familiar with PowerProtect cyber recovery, it provides an automated air gapped solution for data isolation and then cyber sense provides the analytics and the forensics for discovering, diagnosing and remediating those attacks. So it's really all about ransomware protecting from protecting from or covering from those attacks, which unfortunately have become all too common for our customers today. >> Excellent news, Caitlin. Thanks for sharing what's new congratulations to you and the Dell team. >> Thank you so much, Lisa. >> For Cait%lin Gordon I'm Lisa Martin. You're watch%ing 'theCUBE'. (calm music)

>> Live from Barcelona, Spain, it's theCUBE. Covering KubeCon, CloudNativeCon, Europe 2019. Brought to you by Red Hat, the Cloud Native Computing Foundation and Ecosystem Partners. >> Welcome back to theCUBE here in Barcelona, Spain. This is KubeCon, CloudNativeCon 2019. I'm Stu Miniman, my co-host for two days of wall-to-wall coverage is Corey Quinn. Joining us on the program we have two gentleman from Red Hat. To my right is Josh Berkas who's the Kubernetes community manager and sitting to his right is Dejan Bosanac who's a senior software engineer and as I said, both with Red Hat. Gentlemen, thanks so much for joining us. >> Well thank you. >> Thank you. >> All right. So Josh, a community manager in the Kubernetes space, so what brings you here to KubeCon and maybe explain to us and give the clarification on the shirt so that we can be educated to properly call this city and residence by, how they should be. >> Oh, so many things, so. I mean obviously, I'm here because the community is here, right? A very large community. We had a contributor summit on Monday. They had a couple hundred people, three hundred people at it. The important thing, when we talk about community in Kubernetes there's the general ecosystem community and then there's the contributor community. >> Right. >> And the latter is more with what I'm concerned with. Because even the contributor community by itself is quite large. As for the t-shirt, speaking of community, so we like to actually do special t-shirts for the contributor summits. I designed this one. Despite my current career, my academic background is actually in art. This is obviously a Moreau pastiche, but one of things I actually learned by doing this was I did a different version first, It said Barca on it, and then one of the folks from here is like, "Well that's the football team." That when they abbreviate the city, it's actually Barna. >> It was news to me. I am today years old when I found that out. >> Yes. >> So thank you very much for that. >> Yes, that was an additional four hours of drawing for me. >> All right. Go ahead Corey. >> So a while back, I had a tweet that went out that I knew was going to be taken in two different ways and you were one of the first people to come back on that in the second way. Everyone first thought I was being a snarky jerk. >> Yeah. Which, let's be honest, fair. >> Yeah. >> But what I said was that in five years no one is going to care about Kubernetes. >> Right. >> And your response was yeah, that's a victory condition. If you don't have to think or care about this, >> Yeah. >> that means it won >> Right. >> in a similar way that a lot of things have slipped >> Yeah. >> beneath the level of awareness. And I'm curious as to what both of you think about the idea of Kubernetes not, I'm not saying it loses in the marketplace, I don't think that that is likely at all, but at what point do people not have to think about it any more and what does that future look like? >> Yeah, I mean one of our colleagues noticed yesterday that this conference particularly is not about Kubernetes any more. So, you hear more about all the ecosystem. A lot of projects around it. So it certainly grew up above the Kubernetes. And so you see all the talks about service meshes and things we try to do for the edge computing and things like that. So it's not just the Kubernetes any more. It's a whole ecosystem of the products and projects around it. I think, it's a big success. >> Yeah. And I mean I'll say, talking sort of a longer view is, I can remember compiling my own Linux kernels. I can remember doing it on a weekly basis. Because you honestly had to, right? If you wanted certain devices to work you had to actually compile your own kernel. Now on my various servers and stuff that I do for testing and demos and development, I can't even tell you what kernel version I'm running. Because I don't care, right? And for core Kubernetes, like I said, if we get to that point of not needing to care about it of only needing to care about it when we're developing something, then that looks like victory to me. >> Josh, is there anything in the core contributor team that they have milestones and say "Hey, by the time we get to 2.0 or 3.0, you know Kubernetes is invisible?" >> Yeah, well it's spoken of more in terms of GA and API stability >> Yeah. >> because really, if you're going to back off and you're going to say, "What is Kubernetes?" Well, Kubernetes is, what the definition of Kubernetes is, is a bag of APIs. A very large bag of APIs, we do a lot of APIs but a bag of APIs and the less those APIs change in the future the closer we're getting to maturity and stability, right? Because we want people building new stuff around the APIs, not modifying the APIs themselves. >> Yeah well, to that end, last night, here at Barcelona time, a blog post came out from AWS where they set out a formalized deprecation strategy for their EKS product to keep up with the releases of Kubernetes. Now, AWS generally does not turn things off ever, which means that 500 years from now, two trunkless legs of stone in a desert will be balanced by an ELB classic. And we're never going to be rid of anything they've ever built, but if nothing else, you've impacted them to formalize a deprecation strategy that follows upstream, which is awesome. It's great to start seeing a world where you don't have to support older versions of things as your user base and your community informs you. It's nice to see providers breaking from their model to respond to what the community has done. And I can't imagine, for you, that's anything other than an unqualified success. >> All right, so, Dejan. >> Yeah? >> When we talk about dispersion of technology, you know, there are few issues that get people as excited these days as edge computing. So, tell us a little bit about what you're doing and the community's doing in the IOTN edge space. >> Yeah. So, we noticed that more and more people want to try their workloads outside of the centralized, mon-centralized data clusters, so the big term for the last year was the hyper-cloud, but it's not just hyper-cloud. People coming also from the IOT user space wants to, you know, containerize their workloads, wants to put the processing closer and closer to the devices that they're actually producing and presuming those data in the users. And there's a lot of use cases which should be tackled in that way. And as you all said previously, like Kubernetes won developers' hearts and minds so APIs are stable, everybody's using them, it will be supported for decades so it's natural to try to bring all these tools and all these platforms that are already available to developers, try to tackle these new challenges. So that's why last year we formed Kubernetes IT edge working group, trying to, you know, start with simple questions because when people come to you and say edge, everybody thinks something different. For somebody it's an IOT gateway, for somebody it's a full blown, you know, Kubernetes cluster at some telco provider. So that's what they're trying to figure out, all these things, and try to form a community because as we saw in the previous sales for the IOT users space is that complex problems like this are never basically solved by a single company. You need open source, you need open standard, you need community around it so that people can pick and choose and build a solution to fit their needs. >> Yes, so as you said, right, there is that spectrum of offerings everything from that telco down to, you know, is this going to be something sitting on a tower somewhere or, you know, the vast proliferation of IOT which, you know, we spent lots of time. So are you looking at all of these or are you pointing "Okay, we already have a telco working group over here, and, you know, we're going to work on the IOT thing." You know, where are we? What are the answers and starting point for people today? >> Yes, so we have a single working group for now and we try to bring in to people that are interested in this topic in general. So it's, one of the guys said like "Edge is everything that's not running in the center crowd right, so, we have a couple of interesting things happening at a moment, so future way guys have a cubics project and there're presented at this conference. We have a couple of sessions on that. That's basically trying to tackle this device age kind of' space, how to, you know, put Kubernetes' workload on the constrained device and over to constrained network kind of' problem. And we have a people like coming from the rancher, which provide their own, again, resource-constrained Kubernetes deployments, and we see a lot of developments here, but it's still, I think, early age and that's why we have like a working group which is something that we can build our community and work over the time to shape things and find the appropriate reference, architectural blueprints for people that can follow in the future. >> Yeah, I think that there's been an awful lot of focus here on this show on Kubernetes, but it is KubeCon plus CloudNativeCon. I'm curious as far as what you're seeing with these conversations, something you eluded to as well is that there's now a bunch of other services that are factored in. I mean, it feels almost like this show is become, just from conversations, Kubernetes and friends; but, the level of attention that being paid to those friends is dramatically increasing. And I'm curious as to how you're seeing this evolve in the community particularly but also with customers and what you're seeing as this entire ecosystem continues to evolve. >> Yeah. Well, I mean part of it out of necessity, right, as when Kubernetes' move from Dev and experimental into production, you don't run Kubernetes by itself, right? And some of the things with Kubernetes is you can run with existing tooling, rank cloud providers, that sort of thing. But other things you discover that you want new tools. For example, one of the areas that we saw, expansion to start with, was the area of monitoring and telemetry because it turns out that monitoring telemetry that you build for a hundred servers does not work with twenty thousand pods. It's just a volume problem there. And so then we had new projects like Heapster and Prometheus and the new products from other companies like Sistic and that sort of thing, just looking at that space, right, in order to have that part of the tool because you can't be in production without monitoring and telemetry. One of my personal areas that I'm involved is storage, right, and so we've had the rook project here go from and pretty much a year and a half actually, go from being open sourced to being now a serious alternative solution if you don't want to be dependent on cloud provider storage. >> Please tell me you're giving that an award called Rookie of the Year. [laughs] >> I do not apologize for that one. One thing that does resonate with me though is the idea that you've taken, strategically, that instead of building all of this functionality into Kubernetes and turning it into, "You'll do it this way or you're going to be off in the wilderness somewhere," it's decoupled. I love that pattern. Was that always the design from day one or was this a contentious decision history? >> No, it wasn't. Kubernetes started out as kind of a monolith, right, because it was like the open source version of borg light, right, and, which was build as a monolith within Google 'cause there weren't options. They had to work with Google's stuff, right, if you're looking at borg, right, and so they're not worried about supporting all this other stuff, but from day one of Kubernetes being a project, it was a multi-company project, right, and if you look at, you know, open shift and open shift's users and open shift's stack, it's different from what Google uses for GKE. And, honestly, the easiest way to support sort of multiple stack layers is to decouple everything, right? And not how we started out, right? Cloud providers, like one of our problems cloud providers entry, storage entry, networking. Networking was the only thing that was separate from day one. You know but all this stuff was entry, and it didn't take very long for that to get unmaintainable, right? >> Well, I mean I think one of the, I've been following you and running into you in the conference circuit for years, and one of the talks I gave for a year and a half was Heresy in the Church of Docker where we don't know what your problem is but Docker, Docker, Docker, Docker, Docker, and I gave a list of twelve or thirteen different reasons and things that were not being handled by Docker. And now, I've sunset that talk largely because 1) no one talks about Docker and it feels a bit like punching down, but more importantly, Cooper Netties has largely solved almost all of those. There are still a few exceptions here and there 'cause it turns out "Sorry, nothing is perfect and we've not yet found containersation utopia. Surprise!" But it's really come a very long way in a very short period of time. >> Yeah, what a lot of it is is decoupling 'cause the thing is that you can take it two ways, right, one is that potentially as an ecosystem Kubernetes solves almost anything. Some things like IOT are, you know, a lot more alpha state than others. And then if you actually look at just core Kubernetes, it's like what you would get off the Kubernetes' Kubernetes repo if you compiled it yourself, Kubernetes solves almost nothing. Like by itself, you can't do much with it other than test your patches. >> Right, in isolation, the big problem it solves is "Room is limited to 'I want a buzz wort on my resume.'" >> Yes. >> There needs to be more to it than that. >> So, and I think that's true in general 'cause like, you know, if you look at "why did Linux become the default server OS, right?" It became the default server OS because it was adaptable, right, because you would compile in your own stuff because we define posics and kernel module API's to make it easy for people to build their own stuff without needing to commit to Lin EX Kernel. >> Alright, so I'd to get both your thoughts just on the storage piece there because, you know, 1) you know, storage is a complex, highly fragmented ecosystem out there. Red Hat has many options out there, and, boy, when I saw the key note this morning, I thought he did a really good job of laying out the options but, boy, there's, you know, it's a complex multi fragmented stack with a lot of different options out there, and edge computing, the storage industry as a whole without even Kubernetes is trying to figure out how that works, so Dejan, maybe we start with you, and yeah. >> So yeah. I don't have any particular answers for you for today in that area, but what I want, to emphasize what Josh said earlier is that these API's and these modelization that is done in Kubernetes, it's one of the big important things for edge's vow because people coming there and saying "We should do this. Should we invent things or should we just try to reuse what's a basically very good, very well designed system?" So that's a starting point, like why do we want to start using Kubernetes for the edge computing? But for the storage questions, I would hand over to Josh. >> So, your problem with storage is not anything to do with Kubernetes in particular, but the fact that, like you said, the storage sort of stack ecosystem is a mess. It's more vendor. Everything is vendor specific. Things don't work even semantically the same, let alone like the same by API. And so, all we can do in the world of Kubernetes is make enabling storage for Kubernetes not any harder than it would have been to do it in some other system. >> Right, and look, the storage industry'd say, "No no. It's not a mess. It's just that there's a prolifera of applications our there. There is not one solution to fit them all and that's why we have block, we have file, we have object, we have all these various ways of doing things, so you're saying storage is hard, but storage with Kubernetes is no harder today. We're getting to that point. >> I would say it's a little harder today. And we're working on making it not any harder. >> All right, excellent. Well, Josh and Dejan, thank you so much for the updates. >> Thank you guys. Always appreciative of the community contributions. Look forward to hearing more about the, of course, the contributors always and as the Edge and IOT groups mature. Look forward to hearing updates in the future. Thank you. >> Cool. >> Thank you guys. >> Alright, for Corey Quinn, I'm Stu Miniman back with lots more coverage hear from KubeCon CloudNativeCon 2019 in Barcelona, Spain. Thanks for watching theCube.

>> Ladies and gentlemen, please welcome Red Hat President Products and Technologies. Paul Cormier. Boring. >> Welcome back to Boston. Welcome back. And welcome back after a great night last night of our opening with with Jim and talking to certainly saw ten Jenny and and especially our customers. It was so great last night to hear our customers in how they set their their goals and how they met their goals. All possible because certainly with a little help from red hat, but all possible because of because of open source. And, you know, sometimes we have to all due that has set goals. And I'm going to talk this morning about what we as a company and with community, have set for our goals along the way. And sometimes you have to do that. You know, audacious goals. It can really change the perception of what's even possible. And, you know, if I look back, I can't think of anything, at least in my lifetime, that's more important. Or such a big golden John F. Kennedy setting the gold to the American people to go to the moon. I believe it or not, I was really, really only three years old when he said that, honestly. But as I grew up, I remember the passion around the whole country and the energy to make that goal a reality. So let's sort of talk about in compare and contrast, a little bit of where we are technically at that time, you know, tto win and to beat and winning the space race and even get into the space race. There was some really big technical challenges along the way. I mean, believe it or not. Not that long ago. But even But back then, math Malik mathematical calculations were being shifted from from brilliant people who we trusted, and you could look in the eye to A to a computer that was programmed with the results that were mostly printed out. This this is a time where the potential of computers was just really coming on the scene and, at the time, the space race at the time of space race it. It revolved around an IBM seventy ninety, which was one of the first transistor based computers. It could perform mathematical calculations faster than even the most brilliant mathematicians. But just like today, this also came with many, many challenges And while we had the goal of in the beginning of the technique and the technology to accomplish it, we needed people so dedicated to that goal that they would risk everything. And while it may seem commonplace to us today to trust, put our trust in machines, that wasn't the case. Back in nineteen sixty nine, the seven individuals that made up the Mercury Space crew were putting their their lives in the hands of those first computers. But on Sunday, July twentieth, nineteen sixty nine, these things all came together. The goal, the technology in the team and a human being walked on the moon. You know, if this was possible fifty years ago, just think about what Khun B. Accomplished today, where technology is part of our everyday lives. And with technology advances at an ever increasing rate, it's hard to comprehend the potential that sitting right at our fingertips every single day, everything you know about computing is continuing to change. Today, let's look a bit it back. A computing In nineteen sixty nine, the IBM seventy ninety could process one hundred thousand floating point operations per second, today's Xbox one that sitting in most of your living rooms probably can process six trillion flops. That's sixty million times more powerful than the original seventy ninety that helped put a human being on the moon. And at the same time that computing was, that was drastically changed. That this computing has drastically changed. So have the boundaries of where that computing sits and where it's been where it lives. At the time of the Apollo launch, the computing power was often a single machine. Then it moved to a single data center, and over time that grew to multiple data centers. Then with cloud, it extended all the way out to data centers that you didn't even own or have control of. But but computing now reaches far beyond any data center. This is also referred to as the edge. You hear a lot about that. The Apollo's, the Apollo's version of the Edge was the guidance system, a two megahertz computer that weighed seventy pounds embedded in the capsule. Today, today the edge is right here on my wrist. This apple watch weighs just a couple of ounces, and it's ten ten thousand times more powerful than that seventy ninety back in nineteen sixty nine But even more impactful than computing advances, combined with the pervasive availability of it, are the changes and who in what controls those that similar to social changes that have happened along the way. Shifting from mathematicians to computers, we're now facing the same type of changes with regards to operational control of our computing power. In its first forms. Operational control was your team, your team within your control? In some cases, a single person managed everything. But as complexity grows, our team's expanded, just like in the just like in the computing boundaries, system integrators and public cloud providers have become an extension of our team. But at the end of the day, it's still people that are still making all the decisions going forward with the progress of things like a I and software defined everything. It's quite likely that machines will be managing machines, and in many cases that's already happening today. But while the technology at our finger tips today is so impressive, the pace of changing complexity of the problems we aspire to solve our equally hard to comprehend and they are all intertwined with one another learning from each other, growing together faster and faster. We are tackling problems today on a global scale with unsinkable complexity beyond anyone beyond what any one single company or even one single country Khun solve alone. This is why open source is so important. This is why open source is so needed today in software. This is why open sources so needed today, even in the world, to solve other types of complex problems. And this is why open source has become the dominant development model which is driving the technology direction. Today is to bring two brother to bring together the best innovation from every corner of the planet. Toe fundamentally change how we solve problems. This approach and access the innovation is what has enabled open source To tackle The challenge is big challenges, like creating the hybrid cloud like building a truly open hybrid cloud. But even today it's really difficult to bridge the gap of the innovation. It's available in all in all of our fingertips by open source development, while providing the production level capabilities that are needed to really dip, ploy this in the enterprise and solve RIA world business problems. Red Hat has been committed to open source from the very, very beginning and bringing it to solve enterprise class problems for the last seventeen plus years. But when we built that model to bring open source to the enterprise, we absolutely knew we couldn't do it halfway tow harness the innovation. We had to fully embrace the model. We made a decision very early on. Give everything back and we live by that every single day. We didn't do crazy crazy things like you hear so many do out there. All this is open corps or everything below. The line is open and everything above the line is closed. We didn't do that, and we gave everything back Everything we learned in the process of becoming an enterprise class technology company. We gave it all of that back to the community to make better and better software. This is how it works. And we've seen the results of that. We've all seen the results of that and it could only have been possible within open source development model we've been building on the foundation of open source is most successful Project Lennox in the architecture of the future hybrid and bringing them to the Enterprise. This is what made Red Hat, the company that we are today and red hats journey. But we also had the set goals, and and many of them seemed insert insurmountable at the time, the first of which was making Lennox the Enterprise standard. And while this is so accepted today, let's take a look at what it took to get there. Our first launch into the Enterprise was rail two dot one. Yes, I know we two dot one, but we knew we couldn't release a one dato product. We knew that and and we didn't. But >> we didn't want to >> allow any reason why anyone of any customer anyone shouldn't should look past rail to solve their problems as an option. Back then, we had to fight every single flavor of Unix in every single account. But we were lucky to have a few initial partners and Big Eyes v partners that supported Rehl out of the gate. But while we had the determination, we knew we also had gaps in order to deliver on our on our priorities. In the early days of rail, I remember going to ask one of our engineers for a past rehl build because we were having a customer issue on it on an older release. And then I watched in horror as he rifled through his desk through a mess of CDs and magically came up and said, I found it here It is told me not to worry that the build this was he thinks this was the bill. This was the right one, and at that point I knew that despite the promise of Lennox, we had a lot of work ahead of us. The not only convinced the world that Lennox was secure, stable, an enterprise ready, but also to make that a reality. But we did. And today this is our reality. It's all of our reality. From the Enterprise Data Center standard to the fastest computers on the planet, Red Hat Enterprise, Lennox has continually risen to the challenge and has become the core foundation that many mission critical customers run and bet their business on. And an even bigger today Lennox is the foundation of which practically every single technology initiative is built upon. Lennox is not only standard toe build on today, it's the standard for innovation that builds around it. That's the innovation that's driving the future as well. We started our story with rail two dot one, and here we are today, seventeen years later, announcing rally as we did as we did last night. It's specifically designed for applications to run across the open hybrid. Clyde Cloud. Railed has become the best operating simp system for on premise all the way out to the cloud, providing that common operating model and workload foundation on which to build hybrid applications. Let's take it. Let's take a look at how far we've come and see this in action. >> Please welcome Red Hat Global director of developer experience, burst Sutter with Josh Boyer, Timothy Kramer, Lars Carl, it's Key and Brent Midwood. All right, we have some amazing things to show you. In just a few short moments, we actually have a lot of things to show you. And actually, Tim and Brandt will be with us momentarily. They're working out a few things in the back because we have a lot of this is gonna be a live demonstration, some incredible capabilities. Now you're going to see clear innovation inside the operating system where we worked incredibly hard to make it vast cities. You're free to manage many, many machines. I want you thinking about that as we go to this process. Now, also, keep in mind that this is the basis our core platform for everything we do here. Red hat. So it is an honor for me to be able to show it to you live on stage today. And so I recognize the many of you in the audience right now. Her hand's on systems administrators, systems, architect, citizens, engineers. And we know that you're under ever growing pressure to deliver needed infrastructure. Resource is ever faster, and that is a key element to what you're thinking about every day. Well, this has been a core theme, and our design decisions find red Odd Enterprise Lennox eight and intelligent operating system, which is making it fundamentally easier for you manage machines that scale. So hold what you're about to see next. Feels like a new superpower and and that redhead azure force multiplier. So first, let me introduce you to a large. He's totally my limits guru. >> I wouldn't call myself a girl, but I I guess you could say that I want to bring Lennox and light meant to more people. >> Okay, Well, let's let's dive in. And we're not about the clinic's eight. >> Sure. Let me go. And Morgan, >> wait a >> second. There's windows. >> Yeah, way Build the weft Consul into Really? That means that for the first time, you can log in from any device including your phone or this standard windows laptop. So you just go ahead and and to my Saturday lance credentials here. >> Okay, so now >> you're putting >> your limits password and over the web. >> Yeah, that might sound a bit scary at first, but of course, we're using the latest security tech by T. L s on dh csp on. Because that's the standard Lennox off site. You can use everything that you used to like a stage keys, OTP, tokens and stuff like this. >> Okay, so now I see the council right here. I love the dashboard overview of the system, but what else can you tell us about this council? >> Right? Like right here. You see the load of the system, some some of its properties. But you can also dive into logs everything that you're used to from the command line, right? Or lookit, services. This's all the services I've running, can start and stuff them and enable >> OK, I love that feature right there. So what about if I have to add a whole new application to this environment? >> Good that you're bringing that up. We build a new future into hell called application streams. Which the way for you to install different versions of your half stack that are supported I'LL show you with Youngmin a command line. But since Windows doesn't have a proper terminal, I'll just do it in the terminal that we built into the Web console Since the browser, I can even make this a bit bigger. Go to, for example, to see the application streams that we have for Poskus. Ijust do module list and I see you know we have ten and nine dot six Both supported tennis a default on defy enable ninety six Now the next time that I installed prescribes it will pull all their lady towards from them at six. >> Ok, so this is very cool. I see two verses of post Chris right here What tennis to default. That is fantastic and the application streams making that happen. But I'm really kind of curious, right? I loved using know js and Java. So what about multiple versions of those? >> Yeah, that's exactly the idea way. Want to keep up with the fast moving ecosystems off programming language? Isn't it a business? >> Okay, now, But I have another key question. I know some people were thinking it right now. What about Python? >> Yeah. In fact, in a minimum and still like this, python gives you command. Not fact. Just have to type it correctly. You can't just install which everyone you want two or three or whichever your application needs. >> Okay, Well, that is I've been burned on that one before. Okay, so no actual. Have a confession for all you guys. Right here. You guys keep this amongst yourselves. Don't let Paul No, I'm actually not a linnet systems administrator. I'm an application developer, an application architect, And I recently had to go figure out how to extend the file system. This is for real. And I'm going to the rat knowledge base and looking up things like, you know, PV create VD, extend resized to f s. And I have to admit, that's hard, >> right? I've opened the storage space for you right here, where you see an overview of your storage. And the council has made for people like you as well not only for people that I knew that when you two lunatics, right? It's if you're running, you're running some of the commands only, you know, some of the time you don't remember them. So, for example, I haven't felt twosome here. That's a little bit too small. Let me just throw it. It's like, you know, dragging this lighter. It calls all the command in the background for you. >> Oh, that is incredible. Is that simple? Just drag and drop. That is fantastic. Well, so I actually, you know, we'll have another question for you. It looks like now this linen systems administration is no longer a dark heart involving arcane commands typed into a black terminal. Like using when those funky ergonomic keyboards you know I'm talking about right? Do >> you know a lot of people, including me and people in the audience like that dark out right? And this is not taking any of that away. It's on additional tool to bring limits to more people. >> Okay, well, that is absolute fantastic. Thank you so much for that Large. And I really love him installing everything is so much easier, including a post gra seeker and, of course, the python that we saw right there. So now I want to change gears for a second because I actually have another situation that I'm always dealing with. And that is every time I want to build a new Lenox system, not only I don't want to have to install those commands again and again, it feels like I'm doing it over and over. So, Josh, how would I create a golden image? One VM image that can use and we have everything pre baked in? >> Yeah, absolutely. But >> we get that question all the time. So really includes image builder technology. Image builder technology is actually all of our hybrid cloud operating system image tools that we use to build our own images and rolled up in a nice, easy to integrate new system. So if I come here in the web console and I go to our image builder tab, it brings us to blueprints, right? Blueprints or what we used to actually control it goes into our golden image. Uh, and I heard you and Lars talking about post present python. So I went and started typing here. So it brings us to this page, but you could go to the selected components, and you can see here I've created a blueprint that has all the python and post press packages in it. Ah, and the interesting thing about this is it build on our existing kickstart technology. But you can use it to deploy that whatever cloud you want. And it's saved so that you don't actually have to know all the various incantations from Amazon toe azure to Google, whatever it's all baked in on. When you do this, you can actually see the dependencies that get brought in as well. Okay. Should we create one life? Yes, please. All right, cool. So if we go back to the blueprints page and we click create blueprint Let's, uh let's make a developer brute blueprint here. So we click great, and you can see here on the left hand side. I've got all of my content served up by Red Hat satellite. We have a lot of great stuff, and really, But we can go ahead and search. So we'LL look for post grows and you know, it's a developer image at the client for some local testing. Um, well, come in here and at the python bits. Probably the development package. We need a compiler if we're going to actually build anything. So look for GCC here and hey, what's your favorite editor? >> A Max, Of course, >> Max. All right. Hey, Lars, about you. I'm more of a person. You Maxim v I All right, Well, if you want to prevent a holy war in your system, you can actually use satellite to filter that out. But we're going to go ahead and Adam Ball, sweetie, I'm a fight on stage. So wait, just point and click. Let the graphical one. And then when we're all done, we just commit our changes, and our image is ready to build. >> Okay, So this VM image we just created right now from that blueprint this is now I can actually go out there and easily deploys of deploy this across multiple cloud providers. And as well as this on stage are where we have right now. >> Yeah, absolutely. We can to play on Amazon as your google any any infrastructure you're looking for so you can really hit your Clyburn hybrid cloud operating system images. >> Okay. All right, listen, we >> just go on, click, create image. Uh, we can select our different types here. I'm gonna go ahead and create a local VM because it's available image, and maybe they want to pass it around or whatever, and I just need a few moments for it to build. >> Okay? So while that's taking a few moments, I know there's another key question in the minds of the audience right now, and you're probably thinking I love what I see. What Right eye right hand Priceline say. But >> what does it >> take to upgrade from seven to eight? So large can you show us and walk us through an upgrade? >> Sure, this's my little Thomas Block that I set up. It's powered by what Chris and secrets over, but it's still running on seven six. So let's upgrade that jump over to my house fee on satellite on. You see all my relate machines here, including the one I showed you what Consul on before. And there is that one with my sun block and there's a couple others. Let me select those as well. This one on that one. Just go up here. Schedule remote job. And she was really great. And hit Submit. I made it so that it makes the booms national before. So if anything was wrong Kans throwback! >> Okay, okay, so now it's progressing. Here, >> it's progressing. Looks like it's running. Doing >> live upgrade on stage. Uh, >> seems like one is failing. What's going on here? Okay, we checked the tree of great Chuck. Oh, yeah, that's the one I was playing around with Butter fest backstage. What? Detective that and you know, it doesn't run the Afghan cause we don't support operating that. >> Okay, so what I'm hearing now? So the good news is, we were protected from possible failed upgrade there, So it sounds like these upgrades are perfectly safe. Aiken, basically, you know, schedule this during a maintenance window and still get some sleep. >> Totally. That's the idea. >> Okay, fantastic. All right. So it looks like upgrades are easy and perfectly safe. And I really love what you showed us there. It's good point. Click operation right from satellite. Ok, so Well, you know, we were checking out upgrades. I want to know Josh. How those v ems coming along. >> They went really well. So you were away for so long. I got a little bored and I took some liberties. >> What do you mean? >> Well, the image Bill And, you know, I decided I'm going to go ahead and deploy here to this Intel machine on stage Esso. I have that up and running in the web. Counsel. I built another one on the arm box, which is actually pretty fast, and that's up and running on this. Our machine on that went so well that I decided to spend up some an Amazon. So I've got a few instances here running an Amazon with the web console accessible there as well. On even more of our pre bill image is up and running an azure with the web console there. So the really cool thing about this bird is that all of these images were built with image builder in a single location, controlling all the content that you want in your golden images deployed across the hybrid cloud. >> Wow, that is fantastic. And you might think that so we actually have more to show you. So thank you so much for that large. And Josh, that is fantastic. Looks like provisioning bread. Enterprise Clinic Systems ate a redhead. Enterprise Enterprise. Rhetta Enterprise Lennox. Eight Systems is Asian ever before, but >> we have >> more to talk to you about. And there's one thing that many of the operations professionals in this room right now no, that provisioning of'em is easy, but it's really day two day three, it's down the road that those viens required day to day maintenance. As a matter of fact, several you folks right now in this audience to have to manage hundreds, if not thousands, of virtual machines I recently spoke to. Gentleman has to manage thirteen hundred servers. So how do you manage those machines? A great scale. So great that they have now joined us is that it looks like they worked things out. So now I'm curious, Tim. How will we manage hundreds, if not thousands, of computers? >> Welbourne, one human managing hundreds or even thousands of'em says, No problem, because we have Ansel automation. And by leveraging Ansel's integration into satellite, not only can we spin up those V em's really quickly, like Josh was just doing, but we can also make ongoing maintenance of them really simple. Come on up here. I'm going to show you here a satellite inventory and his red hat is publishing patches. Weaken with that danceable integration easily apply those patches across our entire fleet of machines. Okay, >> that is fantastic. So he's all the machines can get updated in one fell swoop. >> He sure can. And there's one thing that I want to bring your attention to today because it's brand new. And that's cloud that red hat dot com And here, a cloud that redhead dot com You can view and manage your entire inventory no matter where it sits. Of Redhead Enterprise Lennox like on Prem on stage. Private Cloud or Public Cloud. It's true Hybrid cloud management. >> OK, but one thing. One thing. I know that in the minds of the audience right now. And if you have to manage a large number servers this it comes up again and again. What happens when you have those critical vulnerabilities that next zero day CV could be tomorrow? >> Exactly. I've actually been waiting for a while patiently for you >> to get to the really good stuff. So >> there's one more thing that I wanted to let folks know about. Red Hat Enterprise. The >> next eight and some features that we have there. Oh, >> yeah? What is that? >> So, actually, one of the key design principles of relate is working with our customers over the last twenty years to integrate all the knowledge that we've gained and turn that into insights that we can use to keep our red hat Enterprise Lennox servers running securely, inefficiently. And so what we actually have here is a few things that we could take a look at show folks what that is. >> OK, so we basically have this new feature. We're going to show people right now. And so one thing I want to make sure it's absolutely included within the redhead enterprise in that state. >> Yes. Oh, that's Ah, that's an announcement that we're making this week is that this is a brand new feature that's integrated with Red Hat Enterprise clinics, and it's available to everybody that has a red hat enterprise like subscription. So >> I believe everyone in this room right now has a rail subscriptions, so it's available to all of them. >> Absolutely, absolutely. So let's take a quick look and try this out. So we actually have. Here is a list of about six hundred rules. They're configuration security and performance rules. And this is this list is growing every single day, so customers can actually opt in to the rules that are most that are most applicable to their enterprises. So what we're actually doing here is combining the experience and knowledge that we have with the data that our customers opt into sending us. So customers have opted in and are sending us more data every single night. Then they actually have in total over the last twenty years via any other mechanism. >> Now there's I see now there's some critical findings. That's what I was talking about. But it comes to CVS and things that nature. >> Yeah, I'm betting that those air probably some of the rail seven boxes that we haven't actually upgraded quite yet. So we get back to that. What? I'd really like to show everybody here because everybody has access to this is how easy it is to opt in and enable this feature for real. Okay, let's do that real quick, so I gotta hop back over to satellite here. This is the satellite that we saw before, and I'll grab one of the hosts and we can use the new Web console feature that's part of Railly, and via single sign on I could jump right from satellite over to the Web console. So it's really, really easy. And I'LL grab a terminal here and registering with insights is really, really easy. Is one command troops, and what's happening right now is the box is going to gather some data. It's going to send it up to the cloud, and within just a minute or two, we're gonna have some results that we can look at back on the Web interface. >> I love it so it's just a single command and you're ready to register this box right now. That is super easy. Well, that's fantastic, >> Brent. We started this whole series of demonstrations by telling the audience that Red Hat Enterprise Lennox eight was the easiest, most economical and smartest operating system on the planet, period. And well, I think it's cute how you can go ahead and captain on a single machine. I'm going to show you one more thing. This is Answerable Tower. You can use as a bell tower to managing govern your answerable playbook, usage across your entire organization and with this. What I could do is on every single VM that was spun up here today. Opt in and register insights with a single click of a button. >> Okay, I want to see that right now. I know everyone's waiting for it as well, But hey, you're VM is ready. Josh. Lars? >> Yeah. My clock is running a little late now. Yeah, insights is a really cool feature >> of rail. And I've got it in all my images already. All >> right, I'm doing it all right. And so as this playbook runs across the inventory, I can see the machines registering on cloud that redhead dot com ready to be managed. >> OK, so all those onstage PM's as well as the hybrid cloud VM should be popping in IRC Post Chris equals Well, fantastic. >> That's awesome. Thanks to him. Nothing better than a Red Hat Summit speaker in the first live demo going off script deal. Uh, let's go back and take a look at some of those critical issues affecting a few of our systems here. So you can see this is a particular deanna's mask issue. It's going to affect a couple of machines. We saw that in the overview, and I can actually go and get some more details about what this particular issue is. So if you take a look at the right side of the screen there, there's actually a critical likelihood an impact that's associated with this particular issue. And what that really translates to is that there's a high level of risk to our organization from this particular issue. But also there's a low risk of change. And so what that means is that it's really, really safe for us to go ahead and use answerable to mediate this so I can grab the machines will select those two and we're mediate with answerable. I can create a new playbook. It's our maintenance window, but we'LL do something along the lines of like stuff Tim broke and that'LL be our cause. We name it whatever we want. So we'Ll create that playbook and take a look at it, and it's actually going to give us some details about the machines. You know what, what type of reboots Efendi you're going to be needed and what we need here. So we'LL go ahead and execute the playbook and what you're going to see is the outputs goingto happen in real time. So this is happening from the cloud were affecting machines. No matter where they are, they could be on Prem. They could be in a hybrid cloud, a public cloud or in a private cloud. And these things are gonna be remediated very, very easily with answerable. So it's really, really awesome. Everybody here with a red hat. Enterprise licks Lennox subscription has access to this now, so I >> kind of want >> everybody to go try this like, we really need to get this thing going and try it out right now. But >> don't know, sent about the room just yet. You get stay here >> for okay, Mr. Excitability, I think after this keynote, come back to the red hat booth and there's an optimization section. You can come talk to our insights engineers. And even though it's really easy to get going on your own, they can help you out. Answer any questions you might have. So >> this is really the start of a new era with an intelligent operating system and beauty with intelligence you just saw right now what insights that troubles you. Fantastic. So we're enabling systems administrators to manage more red in private clinics, a greater scale than ever before. I know there's a lot more we could show you, but we're totally out of time at this point, and we kind of, you know, when a little bit sideways here moments. But we need to get off the stage. But there's one thing I want you guys to think about it. All right? Do come check out the in the booth. Like Tim just said also in our debs, Get hands on red and a prize winning state as well. But really, I want you to think about this one human and a multitude of servers. And if you remember that one thing asked you upfront. Do you feel like you get a new superpower and redhead? Is your force multiplier? All right, well, thank you so much. Josh and Lars, Tim and Brent. Thank you. And let's get Paul back on stage. >> I went brilliant. No, it's just as always, >> amazing. I mean, as you can tell from last night were really, really proud of relate in that coming out here at the summit. And what a great way to showcase it. Thanks so much to you. Birth. Thanks, Brent. Tim, Lars and Josh. Just thanks again. So you've just seen this team demonstrate how impactful rail Khun b on your data center. So hopefully hopefully many of you. If not all of you have experienced that as well. But it was super computers. We hear about that all the time, as I just told you a few minutes ago, Lennox isn't just the foundation for enterprise and cloud computing. It's also the foundation for the fastest super computers in the world. In our next guest is here to tell us a lot more about that. >> Please welcome Lawrence Livermore National Laboratory. HPC solution Architect Robin Goldstone. >> Thank you so much, Robin. >> So welcome. Welcome to the summit. Welcome to Boston. And thank thank you so much for coming for joining us. Can you tell us a bit about the goals of Lawrence Livermore National Lab and how high high performance computing really works at this level? >> Sure. So Lawrence Livermore National >> Lab was established during the Cold War to address urgent national security needs by advancing the state of nuclear weapons, science and technology and high performance computing has always been one of our core capabilities. In fact, our very first supercomputer, ah Univac one was ordered by Edward Teller before our lab even opened back in nineteen fifty two. Our mission has evolved since then to cover a broad range of national security challenges. But first and foremost, our job is to ensure the safety, security and reliability of the nation's nuclear weapons stockpile. Oh, since the US no longer performs underground nuclear testing, our ability to certify the stockpile depends heavily on science based science space methods. We rely on H P C to simulate the behavior of complex weapons systems to ensure that they can function as expected, well beyond their intended life spans. That's actually great. >> So are you really are still running on that on that Univac? >> No, Actually, we we've moved on since then. So Sierra is Lawrence Livermore. Its latest and greatest supercomputer is currently the Seconds spastic supercomputer in the world and for the geeks in the audience, I think there's a few of them out there. We put up some of the specs of Syrah on the screen behind me, a couple of things worth highlighting our Sierra's peak performance and its power utilisation. So one hundred twenty five Pata flops of performance is equivalent to about twenty thousand of those Xbox one excess that you mentioned earlier and eleven point six megawatts of power required Operate Sierra is enough to power around eleven thousand homes. Syria is a very large and complex system, but underneath it all, it starts out as a collection of servers running Lin IX and more specifically, rail. >> So did Lawrence. Did Lawrence Livermore National Lab National Lab used Yisrael before >> Sierra? Oh, yeah, most definitely. So we've been running rail for a very long time on what I'll call our mid range HPC systems. So these clusters, built from commodity components, are sort of the bread and butter of our computer center. And running rail on these systems provides us with a continuity of operations and a common user environment across multiple generations of hardware. Also between Lawrence Livermore in our sister labs, Los Alamos and Sandia. Alongside these commodity clusters, though, we've always had one sort of world class supercomputer like Sierra. Historically, these systems have been built for a sort of exotic proprietary hardware running entirely closed source operating systems. Anytime something broke, which was often the Vander would be on the hook to fix it. And you know, >> that sounds >> like a good model, except that what we found overtime is most the issues that we have on these systems were either due to the extreme scale or the complexity of our workloads. Vendors seldom had a system anywhere near the size of ours, and we couldn't give them our classified codes. So their ability to reproduce our problem was was pretty limited. In some cases, they've even sent an engineer on site to try to reproduce our problems. But even then, sometimes we wouldn't get a fix for months or else they would just tell us they weren't going to fix the problem because we were the only ones having it. >> So for many of us, for many of us, the challenges is one of driving reasons for open source, you know, for even open source existing. How has how did Sierra change? Things are on open source for >> you. Sure. So when we developed our technical requirements for Sierra, we had an explicit requirement that we want to run an open source operating system and a strong preference for rail. At the time, IBM was working with red hat toe add support Terrell for their new little Indian power architecture. So it was really just natural for them to bid a red. A rail bay system for Sierra running Raylan Cyril allows us to leverage the model that's worked so well for us for all this time on our commodity clusters any packages that we build for X eighty six, we can now build those packages for power as well as our market texture using our internal build infrastructure. And while we have a formal support relationship with IBM, we can also tap our in house colonel developers to help debug complex problems are sys. Admin is Khun now work on any of our systems, including Sierra, without having toe pull out their cheat sheet of obscure proprietary commands. Our users get a consistent software environment across all our systems. And if the security vulnerability comes out, we don't have to chase around getting fixes from Multan slo es fenders. >> You know, you've been able, you've been able to extend your foundation from all the way from X eighty six all all the way to the extract excess Excuse scale supercomputing. We talk about giving customers all we talked about it all the time. A standard operational foundation to build upon. This isn't This isn't exactly what we've envisioned. So So what's next for you >> guys? Right. So what's next? So Sierra's just now going into production. But even so, we're already working on the contract for our next supercomputer called El Capitan. That's scheduled to be delivered the Lawrence Livermore in the twenty twenty two twenty timeframe. El Capitan is expected to be about ten times the performance of Sierra. I can't share any more details about that system right now, but we are hoping that we're going to be able to continue to build on a solid foundation. That relish provided us for well over a decade. >> Well, thank you so much for your support of realm over the years, Robin. And And thank you so much for coming and tell us about it today. And we can't wait to hear more about El Capitan. Thank you. Thank you very much. So now you know why we're so proud of realm. And while you saw confetti cannons and T shirt cannons last night, um, so you know, as as burned the team talked about the demo rail is the force multiplier for servers. We've made Lennox one of the most powerful platforms in the history of platforms. But just as Lennox has become a viable platform with access for everyone, and rail has become viable, more viable every day in the enterprise open source projects began to flourish around the operating system. And we needed to bring those projects to our enterprise customers in the form of products with the same trust models as we did with Ralph seeing the incredible progress of software development occurring around Lennox. Let's let's lead us to the next goal that we said tow, tow ourselves. That goal was to make hybrid cloud the default enterprise for the architecture. How many? How many of you out here in the audience or are Cesar are? HC sees how many out there a lot. A lot. You are the people that our building the next generation of computing the hybrid cloud, you know, again with like just like our goals around Lennox. This goals might seem a little daunting in the beginning, but as a community we've proved it time and time again. We are unstoppable. Let's talk a bit about what got us to the point we're at right right now and in the work that, as always, we still have in front of us. We've been on a decade long mission on this. Believe it or not, this mission was to build the capabilities needed around the Lenox operating system to really build and make the hybrid cloud. When we saw well, first taking hold in the enterprise, we knew that was just taking the first step. Because for a platform to really succeed, you need applications running on it. And to get those applications on your platform, you have to enable developers with the tools and run times for them to build, to build upon. Over the years, we've closed a few, if not a lot of those gaps, starting with the acquisition of J. Boss many years ago, all the way to the new Cuban Eddie's native code ready workspaces we launched just a few months back. We realized very early on that building a developer friendly platform was critical to the success of Lennox and open source in the enterprise. Shortly after this, the public cloud stormed onto the scene while our first focus as a company was done on premise in customer data centers, the public cloud was really beginning to take hold. Rehl very quickly became the standard across public clouds, just as it was in the enterprise, giving customers that common operating platform to build their applications upon ensuring that those applications could move between locations without ever having to change their code or operating model. With this new model of the data center spread across so many multiple environments, management had to be completely re sought and re architected. And given the fact that environments spanned multiple locations, management, real solid management became even more important. Customers deploying in hybrid architectures had to understand where their applications were running in how they were running, regardless of which infrastructure provider they they were running on. We invested over the years with management right alongside the platform, from satellite in the early days to cloud forms to cloud forms, insights and now answerable. We focused on having management to support the platform wherever it lives. Next came data, which is very tightly linked toe applications. Enterprise class applications tend to create tons of data and to have a common operating platform foyer applications. You need a storage solutions. That's Justus, flexible as that platform able to run on premise. Just a CZ. Well, as in the cloud, even across multiple clouds. This let us tow acquisitions like bluster, SEF perma bitch in Nubia, complimenting our Pratt platform with red hat storage for us, even though this sounds very condensed, this was a decade's worth of investment, all in preparation for building the hybrid cloud. Expanding the portfolio to cover the areas that a customer would depend on to deploy riel hybrid cloud architectures, finding any finding an amplifying the right open source project and technologies, or filling the gaps with some of these acquisitions. When that necessarily wasn't available by twenty fourteen, our foundation had expanded, but one big challenge remained workload portability. Virtual machine formats were fragmented across the various deployments and higher level framework such as Java e still very much depended on a significant amount of operating system configuration and then containers happened containers, despite having a very long being in existence for a very long time. As a technology exploded on the scene in twenty fourteen, Cooper Netease followed shortly after in twenty fifteen, allowing containers to span multiple locations and in one fell swoop containers became the killer technology to really enable the hybrid cloud. And here we are. Hybrid is really the on ly practical reality in way for customers and a red hat. We've been investing in all aspects of this over the last eight plus years to make our customers and partners successful in this model. We've worked with you both our customers and our partners building critical realm in open shift deployments. We've been constantly learning about what has caused problems and what has worked well in many cases. And while we've and while we've amassed a pretty big amount of expertise to solve most any challenge in in any area that stack, it takes more than just our own learning's to build the next generation platform. Today we're also introducing open shit for which is the culmination of those learnings. This is the next generation of the application platform. This is truly a platform that has been built with our customers and not simply just with our customers in mind. This is something that could only be possible in an open source development model and just like relish the force multiplier for servers. Open shift is the force multiplier for data centers across the hybrid cloud, allowing customers to build thousands of containers and operate them its scale. And we've also announced open shift, and we've also announced azure open shift. Last night. Satya on this stage talked about that in depth. This is all about extending our goals of a common operating platform enabling applications across the hybrid cloud, regardless of whether you run it yourself or just consume it as a service. And with this flagship release, we are also introducing operators, which is the central, which is the central feature here. We talked about this work last year with the operator framework, and today we're not going to just show you today. We're not going to just show you open shift for we're going to show you operators running at scale operators that will do updates and patches for you, letting you focus more of your time and running your infrastructure and running running your business. We want to make all this easier and intuitive. So let's have a quick look at how we're doing. Just that >> painting. I know all of you have heard we're talking to pretend to new >> customers about the travel out. So new plan. Just open it up as a service been launched by this summer. Look, I know this is a big quest for not very big team. I'm open to any and all ideas. >> Please welcome back to the stage. Red Hat Global director of developer Experience burst Sutter with Jessica Forrester and Daniel McPherson. All right, we're ready to do some more now. Now. Earlier we showed you read Enterprise Clinic St running on lots of different hardware like this hardware you see right now And we're also running across multiple cloud providers. But now we're going to move to another world of Lennox Containers. This is where you see open shift four on how you can manage large clusters of applications from eggs limits containers across the hybrid cloud. We're going to see this is where suffer operators fundamentally empower human operators and especially make ups and Deb work efficiently, more efficiently and effectively there together than ever before. Rights. We have to focus on the stage right now. They're represent ops in death, and we're gonna go see how they reeled in application together. Okay, so let me introduce you to Dan. Dan is totally representing all our ops folks in the audience here today, and he's telling my ops, comfort person Let's go to call him Mr Ops. So Dan, >> thanks for with open before, we had a much easier time setting up in maintaining our clusters. In large part, that's because open shit for has extended management of the clusters down to the infrastructure, the diversity kinds of parent. When you take >> a look at the open ship console, >> you can now see the machines that make up the cluster where machine represents the infrastructure. Underneath that Cooper, Eddie's node open shit for now handles provisioning Andy provisioning of those machines. From there, you could dig into it open ship node and see how it's configured and monitor how it's behaving. So >> I'm curious, >> though it does this work on bare metal infrastructure as well as virtualized infrastructure. >> Yeah, that's right. Burn So Pa Journal nodes, no eternal machines and open shit for can now manage it all. Something else we found extremely useful about open ship for is that it now has the ability to update itself. We can see this cluster hasn't update available and at the press of a button. Upgrades are responsible for updating. The entire platform includes the nodes, the control plane and even the operating system and real core arrests. All of this is possible because the infrastructure components and their configuration is now controlled by technology called operators. Thes software operators are responsible for aligning the cluster to a desired state. And all of this makes operational management of unopened ship cluster much simpler than ever before. All right, I >> love the fact that all that's been on one console Now you can see the full stack right all way down to the bare metal right there in that one console. Fantastic. So I wanted to scare us for a moment, though. And now let's talk to Deva, right? So Jessica here represents our all our developers in the room as my facts. He manages a large team of developers here Red hat. But more importantly, she represents our vice president development and has a large team that she has to worry about on a regular basis of Jessica. What can you show us? We'LL burn My team has hundreds of developers and were constantly under pressure to deliver value to our business. And frankly, we can't really wait for Dan and his ops team to provisioned the infrastructure and the services that we need to do our job. So we've chosen open shift as our platform to run our applications on. But until recently, we really struggled to find a reliable source of Cooper Netease Technologies that have the operational characteristics that Dan's going to actually let us install through the cluster. But now, with operator, How bio, we're really seeing the V ecosystem be unlocked. And the technology's there. Things that my team needs, its databases and message cues tracing and monitoring. And these operators are actually responsible for complex applications like Prometheus here. Okay, they're written in a variety of languages, danceable, but that is awesome. So I do see a number of options there already, and preaches is a great example. But >> how do you >> know that one? These operators really is mature enough and robust enough for Dan and the outside of the house. Wilbert, Here we have the operator maturity model, and this is going to tell me and my team whether this particular operator is going to do a basic install if it's going to upgrade that application over time through different versions or all the way out to full auto pilot, where it's automatically scaling and tuning the application based on the current environment. And it's very cool. So coming over toothy open shift Consul, now we can actually see Dan has made the sequel server operator available to me and my team. That's the database that we're using. A sequel server. That's a great example. So cynics over running here in the cluster? But this is a great example for a developer. What if I want to create a new secret server instance? Sure, we're so it's as easy as provisioning any other service from the developer catalog. We come in and I can type for sequel server on what this is actually creating is, ah, native resource called Sequel Server, and you can think of that like a promise that a sequel server will get created. The operator is going to see that resource, install the application and then manage it over its life cycle, KAL, and from this install it operators view, I can see the operators running in my project and which resource is its managing Okay, but I'm >> kind of missing >> something here. I see this custom resource here, the sequel server. But where the community's resource is like pods. Yeah, I think it's cool that we get this native resource now called Sequel Server. But if I need to, I can still come in and see the native communities. Resource is like your staple set in service here. Okay, that is fantastic. Now, we did say earlier on, though, like many of our customers in the audience right now, you have a large team of engineers. Lost a large team of developers you gotta handle. You gotta have more than one secret server, right? We do one for every team as we're developing, and we use a lot of other technologies running on open shift as well, including Tomcat and our Jenkins pipelines and our dough js app that is gonna actually talk to that sequel server database. Okay, so this point we can kind of provisions, Some of these? Yes. Oh, since all of this is self service for me and my team's, I'm actually gonna go and create one of all of those things I just said on all of our projects, right Now, if you just give me a minute, Okay? Well, right. So basically, you're going to knock down No Jazz Jenkins sequel server. All right, now, that's like hundreds of bits of application level infrastructure right now. Live. So, Dan, are you not terrified? Well, I >> guess I should have done a little bit better >> job of managing guests this quota and historically just can. I might have had some conflict here because creating all these new applications would admit my team now had a massive back like tickets to work on. But now, because of software operators, my human operators were able to run our infrastructure at scale. So since I'm long into the cluster here as the cluster admin, I get this view of pods across all projects. And so I get an idea of what's happening across the entire cluster. And so I could see now we have four hundred ninety four pods already running, and there's a few more still starting up. And if I scroll to the list, we can see the different workloads Jessica just mentioned of Tomcats. And no Gs is And Jenkins is and and Siegel servers down here too, you know, I see continues >> creating and you have, like, close to five hundred pods running >> there. So, yeah, filters list down by secret server, so we could just see. Okay, But >> aren't you not >> running going around a cluster capacity at some point? >> Actually, yeah, we we definitely have a limited capacity in this cluster. And so, luckily, though, we already set up auto scale er's And so because the additional workload was launching, we see now those outer scholars have kicked in and some new machines are being created that don't yet have noticed. I'm because they're still starting up. And so there's another good view of this as well, so you can see machine sets. We have one machine set per availability zone, and you could see the each one is now scaling from ten to twelve machines. And the way they all those killers working is for each availability zone, they will. If capacities needed, they will add additional machines to that availability zone and then later effect fast. He's no longer needed. It will automatically take those machines away. >> That is incredible. So right now we're auto scaling across multiple available zones based on load. Okay, so looks like capacity planning and automation is fully, you know, handle this point. But I >> do have >> another question for year logged in. Is the cluster admin right now into the console? Can you show us your view of >> operator suffer operators? Actually, there's a couple of unique views here for operators, for Cluster admits. The first of those is operator Hub. This is where a cluster admin gets the ability to curate the experience of what operators are available to users of the cluster. And so obviously we already have the secret server operator installed, which which we've been using. The other unique view is operator management. This gives a cluster I've been the ability to maintain the operators they've already installed. And so if we dig in and see the secret server operator, well, see, we haven't set up for manual approval. And what that means is if a new update comes in for a single server, then a cluster and we would have the ability to approve or disapprove with that update before installs into the cluster, we'LL actually and there isn't upgrade that's available. Uh, I should probably wait to install this, though we're in the middle of scaling out this cluster. And I really don't want to disturb Jessica's application. Workflow. >> Yeah, so, actually, Dan, it's fine. My app is already up. It's running. Let me show it to you over here. So this is our products application that's talking to that sequel server instance. And for debugging purposes, we can see which version of sequel server we're currently talking to. Its two point two right now. And then which pod? Since this is a cluster, there's more than one secret server pod we could be connected to. Okay, I could see right there the bounder screeners they know to point to. That's the version we have right now. But, you know, >> this is kind of >> point of software operators at this point. So, you know, everyone in this room, you know, wants to see you hit that upgrade button. Let's do it. Live here on stage. Right, then. All >> right. All right. I could see where this is going. So whenever you updated operator, it's just like any other resource on communities. And so the first thing that happens is the operator pot itself gets updated so we actually see a new version of the operator is currently being created now, and what's that gets created, the overseer will be terminated. And that point, the new, softer operator will notice. It's now responsible for managing lots of existing Siegel servers already in the environment. And so it's then going Teo update each of those sickle servers to match to the new version of the single server operator and so we could see it's running. And so if we switch now to the all projects view and we filter that list down by sequel server, then we should be able to see us. So lots of these sickle servers are now being created and the old ones are being terminated. So is the rolling update across the cluster? Exactly a So the secret server operator Deploy single server and an H A configuration. And it's on ly updates a single instance of secret server at a time, which means single server always left in nature configuration, and Jessica doesn't really have to worry about downtime with their applications. >> Yeah, that's awesome dance. So glad the team doesn't have to worry about >> that anymore and just got I think enough of these might have run by Now, if you try your app again might be updated. >> Let's see Jessica's application up here. All right. On laptop three. >> Here we go. >> Fantastic. And yet look, we're We're into two before we're onto three. Now we're on to victory. Excellent on. >> You know, I actually works so well. I don't even see a reason for us to leave this on manual approval. So I'm going to switch this automatic approval. And then in the future, if a new single server comes in, then we don't have to do anything, and it'll be all automatically updated on the cluster. >> That is absolutely fantastic. And so I was glad you guys got a chance to see that rolling update across the cluster. That is so cool. The Secret Service database being automated and fully updated. That is fantastic. Alright, so I can see how a software operator doesn't able. You don't manage hundreds if not thousands of applications. I know a lot of folks or interest in the back in infrastructure. Could you give us an example of the infrastructure >> behind this console? Yeah, absolutely. So we all know that open shift is designed that run in lots of different environments. But our teams think that as your redhead over, Schiff provides one of the best experiences by deeply integrating the open chief Resource is into the azure console, and it's even integrated into the azure command line toll and the easy open ship man. And, as was announced yesterday, it's now available for everyone to try out. And there's actually one more thing we wanted to show Everyone related to open shit, for this is all so new with a penchant for which is we now have multi cluster management. This gives you the ability to keep track of all your open shift environments, regardless of where they're running as well as you can create new clusters from here. And I'll dig into the azure cluster that we were just taking a look at. >> Okay, but is this user and face something have to install them one of my existing clusters? >> No, actually, this is the host of service that's provided by Red hat is part of cloud that redhead that calm and so all you have to do is log in with your red hair credentials to get access. >> That is incredible. So one console, one user experience to see across the entire hybrid cloud we saw earlier with Red update. Right and red embers. Thank Satan. Now we see it for multi cluster management. But home shift so you can fundamentally see. Now the suffer operators do finally change the game when it comes to making human operators vastly more productive and, more importantly, making Devon ops work more efficiently together than ever before. So we saw the rich ice vehicle system of those software operators. We can manage them across the Khyber Cloud with any, um, shift instance. And more importantly, I want to say Dan and Jessica for helping us with this demonstration. Okay, fantastic stuff, guys. Thank you so much. Let's get Paul back out here >> once again. Thanks >> so much to burn his team. Jessica and Dan. So you've just seen how open shift operators can help you manage hundreds, even thousands of applications. Install, upgrade, remove nodes, control everything about your application environment, virtual physical, all the way out to the cloud making, making things happen when the business demands it even at scale, because that's where it's going to get. Our next guest has lots of experience with demand at scale. and they're using open source container management to do it. Their work, their their their work building a successful cloud, First platform and there, the twenty nineteen Innovation Award winner. >> Please welcome twenty nineteen Innovation Award winner. Cole's senior vice president of technology, Rich Hodak. >> How you doing? Thanks. >> Thanks so much for coming out. We really appreciate it. So I guess you guys set some big goals, too. So can you baby tell us about the bold goal? Helped you personally help set for Cole's. And what inspired you to take that on? Yes. So it was twenty seventeen and life was pretty good. I had no gray hair and our business was, well, our tech was working well, and but we knew we'd have to do better into the future if we wanted to compete. Retails being disrupted. Our customers are asking for new experiences, So we set out on a goal to become an open hybrid cloud platform, and we chose Red had to partner with us on a lot of that. We set off on a three year journey. We're currently in Year two, and so far all KP eyes are on track, so it's been a great journey thus far. That's awesome. That's awesome. So So you Obviously, Obviously you think open source is the way to do cloud computing. So way absolutely agree with you on that point. So So what? What is it that's convinced you even more along? Yeah, So I think first and foremost wait, do we have a lot of traditional IAS fees? But we found that the open source partners actually are outpacing them with innovation. So I think that's where it starts for us. Um, secondly, we think there's maybe some financial upside to going more open source. We think we can maybe take some cost out unwind from these big fellas were in and thirdly, a CZ. We go to universities. We started hearing. Is we interviewed? Hey, what is Cole's doing with open source and way? Wanted to use that as a lever to help recruit talent. So I'm kind of excited, you know, we partner with Red Hat on open shift in in Rail and Gloucester and active M Q and answerable and lots of things. But we've also now launched our first open source projects. So it's really great to see this journey. We've been on. That's awesome, Rich. So you're in. You're in a high touch beta with with open shift for So what? What features and components or capabilities are you most excited about and looking forward to what? The launch and you know, and what? You know what? What are the something maybe some new goals that you might be able to accomplish with with the new features. And yeah, So I will tell you we're off to a great start with open shift. We've been on the platform for over a year now. We want an innovation award. We have this great team of engineers out here that have done some outstanding work. But certainly there's room to continue to mature that platform. It calls, and we're excited about open shift, for I think there's probably three things that were really looking forward to. One is we're looking forward to, ah, better upgrade process. And I think we saw, you know, some of that in the last demo. So upgrades have been kind of painful up until now. So we think that that that will help us. Um, number two, A lot of our open shift workloads today or the workloads. We run an open shifts are the stateless apse. Right? And we're really looking forward to moving more of our state full lapse into the platform. And then thirdly, I think that we've done a great job of automating a lot of the day. One stuff, you know, the provisioning of, of things. There's great opportunity o out there to do mohr automation for day two things. So to integrate mohr with our messaging systems in our database systems and so forth. So we, uh we're excited. Teo, get on board with the version for wear too. So, you know, I hope you, Khun, we can help you get to the next goals and we're going to continue to do that. Thank you. Thank you so much rich, you know, all the way from from rail toe open shift. It's really exciting for us, frankly, to see our products helping you solve World War were problems. What's you know what? Which is. Really? Why way do this and and getting into both of our goals. So thank you. Thank you very much. And thanks for your support. We really appreciate it. Thanks. It has all been amazing so far and we're not done. A critical part of being successful in the hybrid cloud is being successful in your data center with your own infrastructure. We've been helping our customers do that in these environments. For almost twenty years now, we've been running the most complex work loads in the world. But you know, while the public cloud has opened up tremendous possibilities, it also brings in another type of another layer of infrastructure complexity. So what's our next goal? Extend your extend your data center all the way to the edge while being as effective as you have been over the last twenty twenty years, when it's all at your own fingertips. First from a practical sense, Enterprises air going to have to have their own data centers in their own environment for a very long time. But there are advantages of being able to manage your own infrastructure that expand even beyond the public cloud all the way out to the edge. In fact, we talked about that very early on how technology advances in computer networking is storage are changing the physical boundaries of the data center every single day. The need, the need to process data at the source is becoming more and more critical. New use cases Air coming up every day. Self driving cars need to make the decisions on the fly. In the car factory processes are using a I need to adapt in real time. The factory floor has become the new edge of the data center, working with things like video analysis of a of A car's paint job as it comes off the line, where a massive amount of data is on ly needed for seconds in order to make critical decisions in real time. If we had to wait for the video to go up to the cloud and back, it would be too late. The damage would have already been done. The enterprise is being stretched to be able to process on site, whether it's in a car, a factory, a store or in eight or nine PM, usually involving massive amounts of data that just can't easily be moved. Just like these use cases couldn't be solved in private cloud alone because of things like blatant see on data movement, toe address, real time and requirements. They also can't be solved in public cloud alone. This is why open hybrid is really the model that's needed in the only model forward. So how do you address this class of workload that requires all of the above running at the edge? With the latest technology all its scale, let me give you a bit of a preview of what we're working on. We are taking our open hybrid cloud technologies to the edge, Integrated with integrated with Aro AM Hardware Partners. This is a preview of a solution that will contain red had open shift self storage in K V M virtual ization with Red Hat Enterprise Lennox at the core, all running on pre configured hardware. The first hardware out of the out of the gate will be with our long time. Oh, am partner Del Technologies. So let's bring back burn the team to see what's right around the corner. >> Please welcome back to the stage. Red Hat. Global director of developer Experience burst Sutter with Kareema Sharma. Okay, We just how was your Foreign operators have redefined the capabilities and usability of the open hybrid cloud, and now we're going to show you a few more things. Okay, so just be ready for that. But I know many of our customers in this audience right now, as well as the customers who aren't even here today. You're running tens of thousands of applications on open chef clusters. We know that disappearing right now, but we also know that >> you're not >> actually in the business of running terminators clusters. You're in the business of oil and gas from the business retail. You're in a business transportation, you're in some other business and you don't really want to manage those things at all. We also know though you have lo latest requirements like Polish is talking about. And you also dated gravity concerns where you >> need to keep >> that on your premises. So what you're about to see right now in this demonstration is where we've taken open ship for and made a bare metal cluster right here on this stage. This is a fully automated platform. There is no underlying hyper visor below this platform. It's open ship running on bare metal. And this is your crew vanities. Native infrastructure, where we brought together via mes containers networking and storage with me right now is green mush arma. She's one of her engineering leaders responsible for infrastructure technologies. Please welcome to the stage, Karima. >> Thank you. My pleasure to be here, whether it had summit. So let's start a cloud. Rid her dot com and here we can see the classroom Dannon Jessica working on just a few moments ago From here we have a bird's eye view ofthe all of our open ship plasters across the hybrid cloud from multiple cloud providers to on premises and noticed the spare medal last year. Well, that's the one that my team built right here on this stage. So let's go ahead and open the admin console for that last year. Now, in this demo, we'LL take a look at three things. A multi plaster inventory for the open Harbor cloud at cloud redhead dot com. Second open shift container storage, providing convert storage for virtual machines and containers and the same functionality for cloud vert and bare metal. And third, everything we see here is scuba unit is native, so by plugging directly into communities, orchestration begin common storage. Let working on monitoring facilities now. Last year, we saw how continue native actualization and Q Bert allow you to run virtual machines on Cabinet is an open shift, allowing for a single converge platform to manage both containers and virtual machines. So here I have this dark net project now from last year behead of induced virtual machine running it S P darknet application, and we had started to modernize and continue. Arise it by moving. Parts of the application from the windows began to the next containers. So let's take a look at it here. I have it again. >> Oh, large shirt, you windows. Earlier on, I was playing this game back stage, so it's just playing a little solitaire. Sorry about that. >> So we don't really have time for that right now. Birds. But as I was saying, Over here, I have Visions Studio Now the window's virtual machine is just another container and open shift and the i d be service for the virtual machine. It's just another service in open shift open shifts. Running both containers and virtual machines together opens a whole new world of possibilities. But why stop there? So this here be broadened to come in. It is native infrastructure as our vision to redefine the operation's off on premises infrastructure, and this applies to all matters of workloads. Using open shift on metal running all the way from the data center to the edge. No by your desk, right to main benefits. Want to help reduce the operation casts And second, to help bring advance good when it is orchestration concept to your infrastructure. So next, let's take a look at storage. So open shift container storage is software defined storage, providing the same functionality for both the public and the private lads. By leveraging the operator framework, open shift container storage automatically detects the available hardware configuration to utilize the discs in the most optimal vein. So then adding my note, you don't have to think about how to balance the storage. Storage is just another service running an open shift. >> And I really love this dashboard quite honestly, because I love seeing all the storage right here. So I'm kind of curious, though. Karima. What kind of storage would you What, What kind of applications would you use with the storage? >> Yeah, so this is the persistent storage. To be used by a database is your files and any data from applications such as a Magic Africa. Now the A Patrick after operator uses school, been at this for scheduling and high availability, and it uses open shift containers. Shortest. Restore the messages now Here are on premises. System is running a caf co workload streaming sensor data on DH. We want toe sort it and act on it locally, right In a minute. A place where maybe we need low latency or maybe in a data lake like situation. So we don't want to send the starter to the cloud. Instead, we want to act on it locally, right? Let's look at the griffon a dashboard and see how our system is doing so with the incoming message rate of about four hundred messages for second, the system seems to be performing well, right? I want to emphasize this is a fully integrated system. We're doing the testing An optimization sze so that the system can Artoo tune itself based on the applications. >> Okay, I love the automated operations. Now I am a curious because I know other folks in the audience want to know this too. What? Can you tell us more about how there's truly integrated communities can give us an example of that? >> Yes. Again, You know, I want to emphasize everything here is managed poorly by communities on open shift. Right. So you can really use the latest coolest to manage them. All right. Next, let's take a look at how easy it is to use K native with azure functions to script alive Reaction to a live migration event. >> Okay, Native is a great example. If actually were part of my breakout session yesterday, you saw me demonstrate came native. And actually, if you want to get hands on with it tonight, you can come to our guru night at five PM and actually get hands on like a native. So I really have enjoyed using K. Dated myself as a software developer. And but I am curious about the azure functions component. >> Yeah, so as your functions is a function is a service engine developed by Microsoft fully open source, and it runs on top of communities. So it works really well with our on premises open shift here. Right now, I have a simple azure function that I already have here and this azure function, you know, Let's see if this will send out a tweet every time we live My greater Windows virtual machine. Right. So I have it integrated with open shift on DH. Let's move a note to maintenance to see what happens. So >> basically has that via moves. We're going to see the event triggered. They trigger the function. >> Yeah, important point I want to make again here. Windows virtue in machines are equal citizens inside of open shift. We're investing heavily in automation through the use of the operator framework and also providing integration with the hardware. Right, So next, Now let's move that note to maintain it. >> But let's be very clear here. I wanna make sure you understand one thing, and that is there is no underlying virtual ization software here. This is open ship running on bear. Meddle with these bare metal host. >> That is absolutely right. The system can automatically discover the bare metal hosts. All right, so here, let's move this note to maintenance. So I start them Internets now. But what will happen at this point is storage will heal itself, and communities will bring back the same level of service for the CAFTA application by launching a part on another note and the virtual machine belive my great right and this will create communities events. So we can see. You know, the events in the event stream changes have started to happen. And as a result of this migration, the key native function will send out a tweet to confirm that could win. It is native infrastructure has indeed done the migration for the live Ian. Right? >> See the events rolling through right there? >> Yeah. All right. And if we go to Twitter? >> All right, we got tweets. Fantastic. >> And here we can see the source Nord report. Migration has succeeded. It's a pretty cool stuff right here. No. So we want to bring you a cloud like experience, but this means is we're making operational ease a fuse as a top goal. We're investing heavily in encapsulating management knowledge and working to pre certify hardware configuration in working with their partners such as Dell, and they're dead already. Note program so that we can provide you guidance on specific benchmarks for specific work loads on our auto tuning system. >> All right, well, this is tow. I know right now, you're right thing, and I want to jump on the stage and check out the spare metal cluster. But you should not right. Wait After the keynote didn't. Come on, check it out. But also, I want you to go out there and think about visiting our partner Del and their booth where they have one. These clusters also. Okay, So this is where vmc networking and containers the storage all come together And a Kurban in his native infrastructure. You've seen right here on this stage, but an agreement. You have a bit more. >> Yes. So this is literally the cloud coming down from the heavens to us. >> Okay? Right here, Right now. >> Right here, right now. So, to close the loop, you can have your plaster connected to cloud redhead dot com for our insights inside reliability engineering services so that we can proactively provide you with the guidance through automated analyses of telemetry in logs and help flag a problem even before you notice you have it Beat software, hardware, performance, our security. And one more thing. I want to congratulate the engineers behind the school technology. >> Absolutely. There's a lot of engineers here that worked on this cluster and worked on the stack. Absolutely. Thank you. Really awesome stuff. And again do go check out our partner Dale. They're just out that door I can see them from here. They have one. These clusters get a chance to talk to them about how to run your open shift for on a bare metal cluster as well. Right, Kareema, Thank you so much. That was totally awesome. We're at a time, and we got to turn this back over to Paul. >> Thank you. Right. >> Okay. Okay. Thanks >> again. Burned, Kareema. Awesome. You know, So even with all the exciting capabilities that you're seeing, I want to take a moment to go back to the to the first platform tenant that we learned with rail, that the platform has to be developer friendly. Our next guest knows something about connecting a technology like open shift to their developers and part of their company. Wide transformation and their ability to shift the business that helped them helped them make take advantage of the innovation. Their Innovation award winner this year. Please, Let's welcome Ed to the stage. >> Please welcome. Twenty nineteen. Innovation Award winner. BP Vice President, Digital transformation. Ed Alford. >> Thanks, Ed. How your fake Good. So was full. Get right into it. What we go you guys trying to accomplish at BP and and How is the goal really important in mandatory within your organization? Support on everyone else were global energy >> business, with operations and over seventy countries. Andi. We've embraced what we call the jewel challenge, which is increasing the mind for energy that we have as individuals in the world. But we need to produce the energy with fuel emissions. It's part of that. One of our strategic priorities that we >> have is to modernize the whole group on. That means simplifying our processes and enhancing >> productivity through digital solutions. So we're using chlo based technologies >> on, more importantly, open source technologies to clear a community and say, the whole group that collaborates effectively and efficiently and uses our data and expertise to embrace the jewel challenge and actually try and help solve that problem. That's great. So So how did these heart of these new ways of working benefit your team and really the entire organ, maybe even the company as a whole? So we've been given the Innovation Award for Digital conveyor both in the way it was created and also in water is delivering a couple of guys in the audience poll costal and brewskies as he they they're in the team. Their teams developed that convey here, using our jail and Dev ops and some things. We talk about this stuff a lot, but actually the they did it in a truly our jail and develops we, um that enabled them to experiment and walking with different ways. And highlight in the skill set is that we, as a group required in order to transform using these approaches, we can no move things from ideation to scale and weeks and days sometimes rather than months. Andi, I think that if we can take what they've done on DH, use more open source technology, we contain that technology and apply across the whole group to tackle this Jill challenge. And I think that we use technologists and it's really cool. I think that we can no use technology and open source technology to solve some of these big challenges that we have and actually just preserve the planet in a better way. So So what's the next step for you guys at BP? So moving forward, we we are embracing ourselves, bracing a clothed, forced organization. We need to continue to live to deliver on our strategy, build >> over the technology across the entire group to address the jewel >> challenge and continue to make some of these bold changes and actually get into and really use. Our technology is, I said, too addresses you'LL challenge and make the future of our planet a better place for ourselves and our children and our children's children. That's that's a big goal. But thank you so much, Ed. Thanks for your support. And thanks for coming today. Thank you very much. Thank you. Now comes the part that, frankly, I think his best part of the best part of this presentation We're going to meet the type of person that makes all of these things a reality. This tip this type of person typically works for one of our customers or with one of with one of our customers as a partner to help them make the kinds of bold goals like you've heard about today and the ones you'll hear about Maura the way more in the >> week. I think the thing I like most about it is you feel that reward Just helping people I mean and helping people with stuff you enjoy right with computers. My dad was the math and science teacher at the local high school. And so in the early eighties, that kind of met here, the default person. So he's always bringing in a computer stuff, and I started a pretty young age. What Jason's been able to do here is Mohr evangelize a lot of the technologies between different teams. I think a lot of it comes from the training and his certifications that he's got. He's always concerned about their experience, how easy it is for them to get applications written, how easy it is for them to get them up and running at the end of the day. We're a loan company, you know. That's way we lean on accounting like red. That's where we get our support front. That's why we decided to go with a product like open shift. I really, really like to product. So I went down. The certification are out in the training ground to learn more about open shit itself. So my daughter's teacher, they were doing a day of coding, and so they asked me if I wanted to come and talk about what I do and then spend the day helping the kids do their coding class. The people that we have on our teams, like Jason, are what make us better than our competitors, right? Anybody could buy something off the shelf. It's people like him. They're able to take that and mold it into something that then it is a great offering for our partners and for >> customers. Please welcome Red Hat Certified Professional of the Year Jason Hyatt. >> Jason, Congratulations. Congratulations. What a what a big day, huh? What a really big day. You know, it's great. It's great to see such work, You know that you've done here. But you know what's really great and shows out in your video It's really especially rewarding. Tow us. And I'm sure to you as well to see how skills can open doors for for one for young women, like your daughters who already loves technology. So I'd liketo I'd like to present this to you right now. Take congratulations. Congratulations. Good. And we I know you're going to bring this passion. I know you bring this in, everything you do. So >> it's this Congratulations again. Thanks, Paul. It's been really exciting, and I was really excited to bring my family here to show the experience. It's it's >> really great. It's really great to see him all here as well going. Maybe we could you could You guys could stand up. So before we leave before we leave the stage, you know, I just wanted to ask, What's the most important skill that you'LL pass on from all your training to the future generations? >> So I think the most important thing is you have to be a continuous learner you can't really settle for. Ah, you can't be comfortable on learning, which I already know. You have to really drive a continuous Lerner. And of course, you got to use the I ninety. Maxwell. Quite. >> I don't even have to ask you the question. Of course. Right. Of course. That's awesome. That's awesome. And thank you. Thank you for everything, for everything that you're doing. So thanks again. Thank you. You know what makes open source work is passion and people that apply those considerable talents that passion like Jason here to making it worked and to contribute their idea there. There's back. And believe me, it's really an impressive group of people. You know you're family and especially Berkeley in the video. I hope you know that the redhead, the certified of the year is the best of the best. The cream of the crop and your dad is the best of the best of that. So you should be very, very happy for that. I also and I also can't wait. Teo, I also can't wait to come back here on this stage ten years from now and present that same award to you. Berkeley. So great. You should be proud. You know, everything you've heard about today is just a small representation of what's ahead of us. We've had us. We've had a set of goals and realize some bold goals over the last number of years that have gotten us to where we are today. Just to recap those bold goals First bait build a company based solely on open source software. It seems so logical now, but it had never been done before. Next building the operating system of the future that's going to run in power. The enterprise making the standard base platform in the op in the Enterprise Olympics based operating system. And after that making hybrid cloud the architecture of the future make hybrid the new data center, all leading to the largest software acquisition in history. Think about it around us around a company with one hundred percent open source DNA without. Throughout. Despite all the fun we encountered over those last seventeen years, I have to ask, Is there really any question that open source has won? Realizing our bold goals and changing the way software is developed in the commercial world was what we set out to do from the first day in the Red Hat was born. But we only got to that goal because of you. Many of you contributors, many of you knew toe open source software and willing to take the risk along side of us and many of partners on that journey, both inside and outside of Red Hat. Going forward with the reach of IBM, Red hat will accelerate. Even Mohr. This will bring open source general innovation to the next generation hybrid data center, continuing on our original mission and goal to bring open source technology toe every corner of the planet. What I what I just went through in the last hour Soul, while mind boggling to many of us in the room who have had a front row seat to this overto last seventeen plus years has only been red hats. First step. Think about it. We have brought open source development from a niche player to the dominant development model in software and beyond. Open Source is now the cornerstone of the multi billion dollar enterprise software world and even the next generation hybrid act. Architecture would not even be possible without Lennox at the core in the open innovation that it feeds to build around it. This is not just a step forward for software. It's a huge leap in the technology world beyond even what the original pioneers of open source ever could have imagined. We have. We have witnessed open source accomplished in the last seventeen years more than what most people will see in their career. Or maybe even a lifetime open source has forever changed the boundaries of what will be possible in technology in the future. And in the one last thing to say, it's everybody in this room and beyond. Everyone outside continue the mission. Thanks have a great sum. It's great to see it

>> live from Boston, Massachusetts. It's the you covering your red have some twenty nineteen. You >> buy bread >> and welcome back to Boston as we continue our coverage here on the Cube of the Red Hat Summit twenty nineteen, along with two minimum. I'm John Walls, and we're now joined by the V, P and C e o of Delta Airlines. Mr. Rahul Samad. Good to see you, sir. Good to see you too, Jamie, For joining us. And you have a little keynote appearance coming through with five. Forty five s. So we will not be well, we won't hold you back. >> But thank you for squeezing this, and we really do. We appreciate that. >> First off, let's talk about just Delta >> from the macro level in terms of the technology emphasis that you have tohave now, obviously running an airline. Extraordinarily complex, sophisticated systems. But how the view of technology has evolved. Maybe over the last five, ten years, where it is today. >> Yeah. I mean, you know, technology has always been core. I mean, we had a reservation systems going back to the sixties on IBM mainframes, but it's as as things have digitalized and the customer experience has become the key and empowering our employees with insights and tools so they can take better care. Even better care of the customers has become the other problem, so it's kind of a two pronged approach to digitalize ing. The company and technology has become central Now. Our culture is all about people, and our frontline teammates take great care off our customers. But then technology plays a great role in empowering them to do that even better. Sighting. It's Ah, within the company. We say, you know, we're transforming technology until competitive advantage for Delta, and so relevance is not a problem. We are extremely relevant to the company, have been forever. But I think it's getting Mohr and Maury even more so today, especially at the customer interaction. Touch point. >> So we're who we understand how important technology is. You know, in your field there talk a little bit about kind of the role of the CEO. How you know, what's the business asking for you? What? The stressors on that and a little bit of that dynamic. >> Yeah, I think. Look, >> you know, I'm an equal member of the CEOs executive team, but you still have to earn your right. And so things like reliability and stability, availability, security become table stakes. And so, in sixteen and seventeen, I started in two thousand sixteen and we needed to focus on that. So I came in, you know, starry eyed going. I'm gonna digitalize the airline experience. But what I needed to focus on was, you know, the table stakes and sort of earning my place at that table rightfully And then that gives you permission to really start collaborating with the business and bringing technology solutions to bear on business opportunity. So we're there now, so it's really exciting time we launched in the Enterprise. Why the digital transformation of the company in early two thousand eighteen, which is again both employees and customers focus. And so clearly we are central to the role ofthe Delta and the airline. >> You just can you share with us? What are some of those key goals of that digital transformation? Obviously, you know, we're all your end ultimate customers wait, value there, but, you know, is data at the core of that digital train. >> You said it. You took >> the words right out of my mouth. You know, I mean any legacy legacy is like a four letter word when it comes to technology everywhere else. We take great pride in our ninety plus year legacy, but not so much with our aging technology. So part of it was, of course, you know you got to modernize the technology, so we're doing that in the background. But data was strewn all over the company. We know a lot about our customers, but we hadn't brought it together. So now we have we have a three sixty degree view. We call it the single view of the customer. Along with that, we also have a single view of the operation. So those two data repositories are now real time and building a pea eye's on top of that and unlocking the power of that data. Two equipped Like I said, the frontline employees, they've now got tools there mobile enable, and they have insights that they can take to serving the customer and then directly guessing both off your customers and directly with you. We've mobile enable the experience and given you ah, whole lot more across the entire traveled ribbon. So >> what are you >> learning then or what have you learned about customers then, in terms of that data collection, I'm sure. I mean, there's there's pretty first level stuff when they buy tickets where the travel to that kind of thing. But then I guess going deeper and learning more about behaviors and impulsive sze impulsive reactions to certain use. Whatever. >> Yep. What do you get it out? We're just >> starting. You know, that's an interesting when, John, because we we do have it. It's a huge data repository, and we're just starting to get the use case is built on that and where we focus our attention is on service. Recovered because we >> do it with >> service would call recovery. So you know whether when weather goes bad and the airline, you know, goes into what we call an irregular operation or an IRA in airline terms, you gotta put that back together and you've got to recover the customers. They might be delayed. They might have suffered a canceled flight or miss bag in spite of all our best efforts. And that's where we're applying the single view of the customer because we know the history ofthe all your interactions with us. And so at the top of the house. The executives decided that that's where we wanted to go. We wanted to make sure that we could acknowledge to you we could recognize interruptions on your next travel with us. But while it's happening, we could actually help get you out of that and on your way again. So now we're moving from that two more revenue generation and targeted offers and targeted recognition. But where we started was really around service recovery because we think you know that that's where customers sometimes feel the pain azaz. Muchas way try for them not to. But you know, whether it's not our ally at times >> and making the business case for that, then are you able to then see how behavior is modified in terms of whether it's customer reaction or customer uptake on your services, whatever and how that's translating to either pretension or business growth or something >> along Absolutely. Even even with the early use cases that we've put forward, we're seeing that I mean the the expectations off airlines over time the customers have and that they're going to use data and technology. Ah, effectively is, I think, fairly low on DSO the when we go up and our folks walk down the aisle with the handheld device on board and they acknowledge someone for hitting a million mile milestone or for achieving diamond status >> in a way, customers are are impressed and, you know, and then you go >> the next level and you're able to take care of them on a on a delay or on a cancel and re accommodate. Before they even called the service center. They've been re accommodated and rebuild. Those are things that I mean, they engender so much loyalty. Andi, I think its technology equipping our our employees in a big way. So the employees are doing great. Now you've put another helping of technology on top of it. Customers are are paying us for that way. Have ah revenue premium on. >> So you talk about internal, Tell us a little bit about your team. How much has this been in a digital transfer? Information is retraining. So how much you trying to get people from the outside? You know, we go to shows like this. Companies like yours are heavy recruiting mode. Typical absent skill sets are tough. You know what you're looking for? And give a little >> Yes, we've had >> Ah, very seasoned, you know, t team an organization. As you would expect, an attrition very low at adult. What what I needed to do was bring in about fifteen to twenty percent of the total team. Strength is knew. That's what I brought in about six hundred people in the last thirty six months. And those were people who were hired for contemporary skills. I call them Been there, done that type people. So Cloud Engineers, FBI people, agile cyber expert, and blending that with the seasoned veterans that know a lot about Del Tighty and know a lot about the airline domain was really important. So you didn't create haves and have nots because that could have easily happened. And then that causes a rupture. So we spent a lot of time on integrating those those two halves and making sure that this was a sort of a shot of adrenaline into the bloodstream. But the blood stream is strong, and the combined force of those two groups has been terrific for us. So that that's the other thing I would say. And I'm not saying that because I'm sitting here in the Red Hat Summit is the use ofthe partners, not just for products but a set of strategic partners. Whether it's Red Hat or IBM or Microsoft, right, a small set of partners becomes a force multiplier from a talent perspective. So they become an accelerant to the transformation. >> Well, you brought it up. Talk a little bit of partnerships. How do you look at this? Is it? I want to have a primary one. Is it a handful? Talk about that depth of relationship and what you're looking for from that Federico >> system. Absolutely. And look, we've got about a dozen that I meet at the the CEO president type level on an annual basis where I would say, you know, ten to twelve that we really are tight with and that are inside the tent. They understand the pillars off our transformation, and they know where they can provide swift acceleration to our transformation. And of course, right at is one and the others that I named. But they're they're they're giving us not just the product and the service, but they're in there helping us with setting the strategy and making sure that they put the right team on the ground with us or training our people. So it runs the gamut from, you know, sort of the system integrator type all the way to open source product pipes >> for the Red Happy's. Can you highlight What are you using? And, you know, are they involved in some of that training and transformation? >> And I think you know, >> the behind the scenes sort of under the hood. The platform is a service that gives us tremendous interoperability. We are young in our journey to the cloud, and like any big company, we're going to be multi cloud and hybrid. So we built our private cloud. We've got the the red had open shift container platform hosted in our private cloud. And so we're moving a lot of application components into that >> prior to that. And that's only >> about a year that we've been doing that. But prior to that, we've been big Lennox users, you know, Red Hat Enterprise, Lin X J boss, a whole plethora of products. But I think the platform is the service is really helping us with our cloud journey, and we're we're totally jazzed about that. >> You talked about hiring and six hundred two employees in a very short period of time class door. It just stood up and said, Hey, Delta Airlines, one of the top of companies for hiring software engineers >> after it was a very nice distinction to get. What does that do? Does that mean terms of first off? How do you do >> that in such an environment where you know everybody's after the same market, if you >> will. I think, you know, how do you feel about something today? I'm I'm validate a little bit really proud of that. And it actually wasn't something that you self >> nominate or you even have, you know, some kind of a selection process. It just arrived, you know, we didn't know about it. And those are some of the best ones because it's also recognition from your employees >> because they're the >> ones who are voting with their their posts and their the ones that are telling glass Door that this is a terrific place to work and we're doing a lot of new things and we're doing them at speed and it's very relevant to the customer experience into our front line employees experience. So >> there's an impact >> story this is this is the great thing about working for an airline. There's no place to run or hide when you're in I t. Because if it's down within fifteen minutes were front page news right somewhere. And so we strive hard to make sure it's never down. And on top of that, we're building, you know, these great digital experiences. So it's been really gratifying, and I think it's going to help us even further with our recruiting efforts. >> Yeah, it's interesting, you know, without getting political. It's like you're doing this modernization. But I mean, you've got heavy regulations on, you know, just some of the basic infrastructure of your industry is a little bit antiquated, you know, and comments >> on that. Well, I think it's It's a dichotomy, and I don't think we're >> unique. And I came out of banking to insurance to airlines, And you think that the way the financial services guys spend money on it, there would be no aging technology and there'd be no you no, none of that. Webb off connectivity. It's not true. I think any company that's been around forty fifties, you know, years >> has all the generations of technology still existing. So our Endeavour >> is to make sure that we deprecate out of that technology as quickly as we can and where it's useful. I mean, >> we still use mainframes >> for a really good purpose, and someone asked me just couple of weeks ago would you get out of it? And I said, >> No, it's a half a billion dollars project >> and it's a high risk project and IBM serves me really well, And for that purpose, the mainframe is exactly what the doctor ordered. So this >> isn't about >> ideology, right? This is about purpose built and custom build. So if there's a technology that fits the purpose, I'm gonna leave well alone. And I'm going to train people and recruit people so that I don't have a talent issue in ten or twenty years when it comes to mainframe people. We've had no problem in getting apprentices and keeping our mainframe talent pipeline gold so they never get away from it. >> Can you give us just a little sneak peek on the keynote tonight? >> I mean, just a maybe a high >> level here, a couple of things just for John, and it's going to be a fireside with Jim you'LL have to come in and we'll be there and listen. But I think Jim Jim's probably got a few questions up his sleeve is also, you know, Jim's got a heritage with Delta. He was our >> chief operating officer until I think about ten years ago. And so it >> should be a fun. He hasn't told me what he's going to ask, so it's gonna be interesting as to which way he's going to come. But I would assume he >> wants to talk about, you know, digital transformation and and, of course, how right ATS helping I would, I would seem there's going to be a question or two about about red >> handed. My only warning, obi, is what >> I hear when I walk on a Delta flight. Let's fasten your seat belt. >> Yes, there. Thank you. Thanks for the time and looks forward to Aquino tonight. Thank you so much, guys. All right. Back with more here on the Cube were watching coverage right now. Right. Had summit >> and we're in Boston, Massachusetts

>> live from Boston, Massachusetts. It's the queue covering your red hat. Some twenty nineteen lots. You buy bread >> and good morning. Welcome to Beantown, Boston, Massachusetts to Mina Mons Hometown by the police Town of residents. John Wallis was stupid from here on the Q. Bert had summit and stew for you. Good to see you here. And a home game. >> Yeah, John, Thanks so much. Nice. You know, Boston, The Cube loves Boston. The B C E C is actually where the first cube event was way back in twenty ten. And we wish there were more conferences here in Boston. Gorgeous weather here in the spring. Ah, little chilly at night with the wind coming off the water, but really good. Here is the sixth year we've had the Cube here, right? Had some in my fifth year at the show. Great energy. And, you know, thirty four billion reasons why people are spending a lot of time keeping a close eye on. Let's just know. Yeah, >> jump right in thirty four billion dollar deal. I am red hatt gotta prove by doj uh, here in the States. But there's still some hurdles that they have to get over in order for that to come to fruition, Maybe later this year. That's the expectation. But just your thoughts right now about about that synergy about that opportunity that that we think is about to have. >> Yeah, so? So right, let's get this piece out of the way. Because here at the conference, we're talking about Red Hat. The acquisition has not completed. So while the CEO of IBM you know Jenny will be up on stage tonight along with, you know, Jim White Hirsi over at Hat and Sakina della, you know, flying in from Seattle, where you might get your name yesterday. So you know, at least two of those three your Cuba Lem's. So we'LL get Jenny on one of these days. But, you know, this is a big acquisition, the largest software acquisition ever, and third largest acquisition in tech history. Now we watched the first biggest tech acquisition in history, which was Del buying AMC just a couple of years ago. And this is not the normal. Okay? Hey, we announced it and you know, it closed quietly in a few months. So as you mentioned, DOJ approved it. There's a few more government agencies Europe needs to go through. You never know what China might ask to come in here, but, you know, really, at the core if you look at it, you know, IBM and Red Hat have worked together for decades. You know, we wrote a lot about this when the announcement happened. You know, IBM is no stranger to open source. IBM is no stranger to the clinics and the areas where Red Hat has been growing and expanded too. You see, IBM, they're so communities, you know, super hot space. If you look, you know, Red hat is they're they're open shift platform, which is what Red Hat does for cloud. Native Development has over a thousand customers. They're adding between one hundred one hundred fifty a quarter is what they talk about publicly. We're gonna have some of those customers on this week. So huge area. That multi cloud hybrid cloud world absolutely is where it's at. We did four days of broadcast from IBM. Think earlier this year in San Francisco. And, you know, once again, Jim white hairs and Jenny were on stage together. They're talking about where they've been working together for a long time. and just, you know, some things will change, but from IBM standpoint, they said, Look, you know, the day after this closes, you know, Red Hat doesn't go away. That had just announced new branding, and everybody's like, Well, why are they changing their branding? You know, when you know IBM is taking over and the answer was, Look, Red Hat's going to stay as a standalone entity. IBM says they're not going to have a single lay off, not even HR consolidation, at least in the beginning. We understand, you know, give me your stuff to work out some of these pieces, but there are ears. They will work together. I look at it. John is like the core. What is the biggest piece of IBM's business is services. That Army of services, both from IBM and all of their Esai partners and everybody they worked with Khun really supercharge and help scale some of the environment that red hats doing so really interesting. Expect them to talk a little bit about it. Red hat is way more transparent than your average company. They had an analyst event like a week or two after it happened, and I was really surprised how much they would tell us and that we could talk about publicly. As I said, just cause I've seen so many acquisitions happen, including some you know, mega ones in the past. And we know how little usually you talk about until it it's done and it's signed. And, you know, the bankers and lawyers have been paid all their fees. >> Let me ask you, you raise an interesting point. Um, you know that there are some different approaches, obviously, between IBM redhead, just in terms of their institutional legacies in terms of processes. Red hat. You mentioned very transparent organization. Open source. Right. So we're all about the rebrand. They come out, you know, the drop shadow, man, They got the hat. What's that cultural mix going to be like? Can they truly run independently? Yeah, they're a big piece. So And if your IBM can you let that run on its own? >> So, John, that is the question most of us have. So, you know, I've worked with Red Hat for coming up on twenty years now, you know, Remember when Lennox was just this mess of colonel dot organ. So much changes that red hat came and gave, you know, adult supervision to help move that forward on. The thing I I wrote about is what Red Hat is really, really good at. If you look at the core, there do is managing that chaos and change on the industry. If you look how many changes happen, toe Lennox, you know every you know, day, week, month and they package all that together and they test all that same thing in Kou Burnett is the same thing in so many different spaces where that open source world is just frenetic and changing. So they're really geared for today's industry. You talk what's the only constant in our industry? John is it is changed. IBM, on the other hand, is like, you know, over one hundred years old, and I tried and true, you know, Big Blue. You know, I ibm is this, you know, the big tanker, you know, it's not like they turn on a dime and you know, rapid pace of change. You think of IBM, you think of innovation. You think of, you know, trust. You think of all the innovations that have come out over the century. Plus do there and absolutely there is a little bit of impeded mismatch there and we'LL see So if ibm Khun truly let them do their own thing and not kind of merged suit groups and take over where the inertia of a larger group can slow things down I hope it will be successful But they're definitely our concerns And time will tell we'll see But you know analytics front You know, they just announced this morning Rehl eight Red hat enterprise linen, you know, just got announced and definitely something will be spent a lot of time So >> let's just jump in a relative Look again, We're gonna hear a little bit later on. We have several folks coming on board to talk aboutthe availability. Now what? What do you see from the outside? Looking at that. What is it going to allow you or us to do that? Seven Didn't know. Where did they improve? Is that on the automation side? Is it being maybe more attentive, Teo Hybrid environment or just What is it about? Really? That makes that special? >> Yes. So you know, first of all, you know these things take a while in the nice thing about being open sources. We've had transparency. If you wanted to know it was going to be in relate. You just look in the Colonel and and it's all out there. They've been working on this since twenty thirteen. Well, seven came out back in June of twenty fourteen. This has been a number of years in the mix. You know, security. The new, like crypto policy is a big piece that that's in their thie bullets that I got when I got the pre briefing on, It was, you know, faster and easier Deploy faster on boarding for non lennox users on, you know, seamless nondestructive migration from earlier versions of rail. So that's one of the things they really want to focus on is that it needs to be predictable, and I need to be able to move from one version the other. If you look at the cloud world, you know, when you don't go asking customers say, Hey, what version of Azure a ws are you running on your running on the latest and greatest? But if you look at traditional shrink wrap software, it was well, what virginity running? Well, I'm running in minus two and Why is that? Because I have to get it. I have to test it out. And then I, you know, find a time that I'm gonna roll that out, work it in my environment. So there is stability and understanding of the release cycle. My understanding is that they're going to do major releases every three years and minor releases every six months. So that cadence a little bit more like the cloud. And as I said, getting from one version a rail to the next should be easier and more non disruptive. Ah, a lot of people are going to want manage offerings where they don't really think about this. I have the latest version because that has not just the latest features but the latest security setting, which, of course, is a major piece of my infrastructure today to make sure that if there was some vulnerability released, I can't wait, You know, six or nine months for me to bake that in there. The limits community's always good have done a good job of getting fixes into it. But how fast can I roll that out into my environment is >> something I would assume that's that's a major factor in any consideration right now is is on the security front, because every day we hear about one more problem and these are just small little issues. These these air are could be multi billion dollar problems. But in terms of making products available today, how Muchmore important? How's that security shift? If you could put a percentage on it used to be, you know, axe and now it's X plus. I mean I mean, what kind of considerations are being given? >> You know what I'd say? Used to be that security got great lip service A. Said it was usually top of mind, but often towards bottom of budget. When you talk to administrators and you say, Oh, hey, where's your last security initiative? And that, like I've had that thing sitting on my desk for the last six months and I haven't had a chance to roll that out. I will get to it, but I want to again. If you go to that cloud operating model. If you talk about you know Dev, Ops movement is, I need to bake security into the process. If I'm doing C i D. It's not, I do something and then think about security afterwards. Security needs to be built in from the ground level. A CZ. You know, I I've heard people in the industry. Security is everyone's responsibility, and security must be baked in everywhere. So from the application all the way down to the chipset, we need to be thinking about security along the bar. Mind it is a board level discussion. Any user you talk too, you know, you don't say, Hey, where's the security sitting? Your priorities. You know, it's up there towards the top, if not vey top, because that's the thing that could put us out of business or, you know, definitely ruin careers. If if it doesn't go >> right, so there are there are probably a couple of platforms, every will or pillars. I think you like to call them that. You're looking forward to learning more about this week. I think in terms of red hats work one of those green hybrid cloud infrastructure, and we'LL get to the other to a little bit. But just your thoughts about how they're addressing that with the products that they offered the services they offer and where they're going in that >> Yeah, so look everything for red at start with rail. Everything is built on Lenox, and that's a good thing, because Lennox Endeavor is everywhere. If last year is that Microsoft ignite for the first time. And when you hear them talking a Microsoft talking about how Lennox is the majority of the environment, more than fifty percent of the environment are running linen goto a ws Same thing. All the cloud deployment Lennox is the preferred substrate underneath and Rehl doing very well to live in all those environment. So what we look at is, you know, some people say, is this olynyk show. It's like, well, at the core. Lin IX is the piece of it and relate the latest and greatest substantiation. But everywhere you go, there's going to be Lennox there from doing container ization. If a building on top of it with the the new cloud native models, it's there. And if you talk about how I get from my data center to a multi cloud environment, it's building things like Cooper Netease, which read that of course, uses open shift and you know those ties to eight of us and azure and you know, Google they're all there. So we mention Santina della's on stage tonight at Microsoft build. Yesterday there was announcement of this thing called Kita ke e d A, which has, like as your functions and ties in with open shift and spend a little time squinting it, trying to tease it apart. We've got some guests this week that'LL hopefully give some clarity, but it is. The answer is people today have multiple clouds and they have a lot of different ways they want. They want to do things, and Red has going to make sure that they help bridge the gap and simplify those environments across the board. Two years ago, when we were at the show big announcement about how open shift integrates with a W s so that if I'm using a ws But I want to have things in my environment still leverage some of those services. That was something that that Red had announced. I was, you know, quite impressed a time it was, you know, just last week being at the Del Show, it's V m. Where is the del strategy for how they get you know, A W, S, G, C, P and Azure and, you know, Red Hat does that themselves. Their software company. They live in all these cloud worlds, and therefore, open shift will help you extend from your data center through all of those public cloud environments on DH, you know? Yeah. So it's fascinating >> you've talked about Lennox to we're going to hear a little bit later on to about a fascinating the global economic study, that Red Hat Commission with the I. D. C. Of that talks about this ten trillion dollar impact of Lennox around the globe like to dive into that a little bit later on. >> Yeah, well, it's interesting, you know, it's the line I used is you say, and you say, Oh, well, how much impact is Lennox had? You know? You know, Red hats now, a three billion dollar company. That's good. But I was like, Okay, let's just take Google. You know, no slots of a company. Google underneath. It's not Red Hat Lennox, but Lennox is the foundation. I don't really think that Google could become the global search and advertising powerhouse they were. If it wasn't for Lennox to be able to help them get environment, there's a CZ we always talk with these technologies. You talk about Lennox, you talk about How do you talk about, you know, Cooper Netease? There are companies that will monetize it, but the real value is what business models and creation by. You know, all the enterprise is the service riders in the hyper scales that those technologies help enable. And that's where open source really shines is, you know, the order of magnitude network effect, that open source solutions have that its you say okay, three billion dollars? And is that what ten trillion dollars? It doesn't faze me, doesn't surprise me at all, but because my attention it look it. I'm not trying to trivialize. There's no But, you know, I've been watching clinics for twenty years, and I've seen the ripples of that effect. And if you dig down underneath your often finding it inside, >> I mentioned pillars that you were talking about cloud native development being another. But automation, let's just hit on that real quick before we head off on DH just again, with how that is being, I guess, highlighted. Or that's a central focus at and relate and and what automation? How that's playing in there I guess the new efficiencies they're trying to squeeze out. >> Yes. So? So what we always looked for it shows you're probably the last year is you know, you. How are they getting beyond the buzzwords? Aye, aye. When you talk about automation on area that that we've really enjoyed digging into is like robotic process automation. How do I take something that was manual? And maybe it was a fish injure? Not great. How can I make it perfectly efficient and use software robots to do that? So where are the places where I know that the amount of change and the scale and the growth that we have that I couldn't just put somebody to keyboard, you know, and have them typing or even a dashboard to be able to monitor and keep up with things? If I don't have the automation and intelligence in the system to manage things, I can't reach the scale and the growth that I need to. So where are you know, real solutions that are helping customers, you know, get over a little bit of the fear of Oh, my gosh, I'm losing a job. Or will this work or will this keep my business running and oh, my gosh, this will actually enabled me to be able to grow work on that security issue if I need to, rather than some of the other pieces and help really allow it agility to meet the requirements of what the business requires to help me move forward. So those are some of the things we kind of look across the shows. So, you know? Yeah. How much do we get? You know, buzzword, Bingo at the show. Where How much do we hear? You know, real customers with real solutions digging in and having, you know, new technologies that a couple of years ago would have had a saying, Wow, that's magic. >> But you say, Oh, my gosh. Yeah, and I don't want gosh right back with more. You're watching to serve the cube with the red had summit. We're in Boston, Massachusetts, that we'll be back with more coverage right after this