(upbeat sparkling music) >> Hello everyone and welcome back to our wall-to-wall coverage of AWS re:Invent. We are live from the show floor here in fabulous Las Vegas, Nevada. My name is Savannah Peterson, here with my cohost John Furrier on theCUBE. John, end of day three. You're smiling. >> Yeah. >> You're still radiating energy. Is it, is it the community that's keeping your, your level up? >> It's just all the action. We've got a great special guest joining us for the first time on theCUBE. It's going to be great and Serverless wave is hitting. More and more Serverless embedded into the like, things like analytics, are going to make things tightly integrated. You can see a lot more kind of tightly coupled but yet still cohesive elements together being kind of end-to-end, and again, the, the zero-ELT vision is soon to be here. That and security, major news here at Amazon. Of course, this next segment is going to be awesome, about the modernization journey. We're going to hear a lot about that. >> Yeah, we are, and our next guest is also an extraordinarily adventurous one. Please welcome Joe from Arc XP. Thank you so much for being here. >> Thanks for having me. >> Savannah: How this show going for you? >> It's been great and you know, it's the end of the day but there's so much great energy at the show this year. >> Savannah: There really is. >> It's great walking the halls, seeing the great engineers, the thought leaders, including this session. So, it's been really a stimulating time. >> What do you do at Arc, what do you, what's your role? >> So, I'm Vice President of Technology and Product Development. I recently joined Arc to lead all the product development teams. We're an experience platform, so, in that platform we have content tools, we have delivery tools, we have subscription tools. It's a really exciting time in all those spaces. >> John: And your customer base is? >> Our customers today started with publishers. So, Arc XP was built for the Washington Post's internal needs many years ago and word got out about how great it was, built on top of the AWS tech stack and other publishers came and started licensing the software. We've moved from there to B2C commerce as well as enterprise scenarios. >> I think that's really interesting and I want to touch on your background a little bit here. You just mentioned the Washington Post. You have a background in broadcast. What was it, since you, since you are fresh, what was it that attracted you to Arc? What made you say yes? >> Yeah, so I spent a little under 10 years building the Associated Press Broadcast Newsroom Tools, some of them that you have used for many years, and you know, one of the things that was really exciting about joining ARC, was they were cloud native and they were cloud native from the start and so that really gave them a leg up with how quickly they could innovate, and now we see developers here at re:Invent be able to do custom Lambdas and new extensibility points in a way that, really, no one else can do in the CMS space >> Which, which is very exciting. Let's talk a little bit about your team and the development cycle. We've touched a lot on the economic uncertainty right now. How are things internally? What's the culture pulse? >> Yeah, so the return to work has been a thing for us, just like- >> Savannah: Are you back in office? >> All of them. We actually have a globally distributed team, and so, if you happen to be lucky enough to be in Washington, DC or Chicago or some of our other centers, there's an opportunity to be in the office, but most of our engineers work remotely. One of the exciting things we did earlier this year was ARC week. We brought everyone to DC to see each other face-to-face, and that same energy you see at re:Invent, was there in person with our engineers. >> I believe that. So, I'm a marketer by trade. I love that you're all about the digital experience. Are you creating digital- I mean everyone needs some sort of digital experience. >> Joe: Yes. >> Every company is a technology company now. Do you work across verticals? You see more niche or industry specific? >> Yeah, so we began with a very large vertical of media and broadcast. >> Savannah: There's a couple companies in that category. >> There's a couple big ones out there. >> Savannah: Yeah, yeah, yeah. >> And actually their challenges are really high volume production of great digital storytelling, and so, solving their problems has enabled us to have a platform that works for anyone that needs to tell a story digitally, whether it's a commerce site, corporate HR department. >> Savannah: Which is everyone, right? >> Virtually everyone needs to get their story out today. >> Yeah. Yeah. >> And so we have gone to a bunch of other verticals and we've seen the benefits of having that strong, cloud-based platform offer the scale that all storytellers need. >> What are some of the challenges today that aren't, that weren't there a decade ago or even five years ago? We see a lot of media companies looking at the business model innovations, changing landscapes omnichannel distribution, different formats. What's some of the challenges that's going on in content? >> So, you know, content challenges include both production of content and delivery of that content through a great experience. So different parts of ARC focus on those problems and you got to monetize it as well, but what I'd say is unique to Arc and the challenge we talk to our customers about a lot is multi-format production. So, it's not just about one channel. >> Savannah: Right. It's about telling a story and having it go across multi-channels, multi-sites, and having the infrastructure both technically and in the workflow tools, is super critical for our customers and it is a challenge that we receive well. >> A lot of AI is coming into the conversation here. Data, AI, publishing, video, user generated content. It's all data. >> Absolutely, yep. >> It's all data. >> Joe: It's an immense amount of data. >> How do you look at the data plane or the data layer, the data aspect of the platform and what are some of the customers leaning into or are kicking the tires around? What are some of the trends, and what are some of the core issues you see? >> Yeah, so I've spent a lot of time in data ML and analytics looking at giant data sets, and you know, when you look at CMS systems and experience platforms, the first class that it's in, is really the, the documents themselves. What is the story you're saying? But where the rich data is that we can analyze is user behaviors, global distribution of content, how we optimize our CDN and really give a personal experience to the reader, but beyond that, we see a lot of advantages in our digital asset management platform, which is for video, audio, photos, all kinds of media formats, and applying AIML to do detection, suggest photos that might be appropriate based on what a journalist or a marketer is writing in their story. So, there's a lot of opportunities around that sort of data. >> What are some of the business model changes that you're seeing? 'Cause remember we're in digital, Page view advertising has gone down, subscription firewalls on blogs. You got things like Substack emerging. Journalists are kind of like changing. I've seen companies go out of business, some of the media companies or change, some of the small ones go out of business, the bigger ones are evolving. What are some of the business model enablements that you guys see coming, that a platform could deliver, so that a company can value their content, and their talent? >> For sure. I mean this is a perennial question in the media space, right? It's been going on for two decades. >> I was going to say we're- >> Right. >> So it's like- >> Joe: Right, and so we've seen that play out- >> John: Little softball for you. >> Really for almost every format. It's a softball, but- >> It's day three. >> How are we addressing that? You know what, first and foremost, you got to do great storytelling, so, we have tools for that, but then presenting that story, and a great experience no matter what device you're on, that's going to be critical no matter how you're monetizing it, and so, you know, we have customers that go very ad heavy. We also have a subscription platform that can do that built into our infrastructure. >> 50 million plus registered users, correct? >> Yeah, it's unbelievable to scale. Really, Arc is a growth story, and so we went from serving the Washington Post needs, to over 2000 sites today, across 25 countries. >> Very- >> How do we get to that? How do we get that audience if we want to? Can we join that network? Is it a network of people? >> I love that question. >> Of people that are using Arc XP? >> Yeah. >> Actually, we recently launched a new effort around our community, so I think they actually had a meeting yesterday, and so that's one way to get involved, but as you said, everyone needs to have a site and tell great stories. >> Yeah. >> So, we see a wide appeal for our platform, and what's unique about ARC, is it's truly a SaaS model. This is delivered via SaaS, where we take care of all of the services, over a hundred Amazon services, behind the scenes- >> Wow. >> Built into Arc. We manage all of that for our customers, including the CDN. So, it's not as though as our customers have to be making sure the site is up, we've got teams to take care of that 24/7 >> Great value proposition and a lot of need for this, people doing their own media systems themselves. What's the secret sauce to your success? If you had to kind of look at the technology? I see serverless is a big part of it on the EDB stack. What's the, what's the secret sauce? >> I think the secret sauce comes from the roots that Arc has in the Washington Post >> You understand it. >> And some of the most challenging content production workflows anywhere in the world, and I've spent a lot of time, in many newsrooms. So, I think that knowledge, the urgency of what it takes to get a story out, the zero tolerance for the site going down. That DNA really enables our engineers to do great solutions. >> Talk about understanding your user. I mean that that's, and drinking the Kool-Aid, but in a totally amazing way. One of the other things that stuck out to me in doing my research is not only are you a service used, now, by 50 million subscribers, but beyond that, you pride yourself on being a turnkey solution. Folks can get Arc up and running quite quickly. Correct? >> For sure. So, one of the things we built into Arc XP is something called Themes, which has a bunch of pre-built blocks, that our customers don't have to end up with a custom codebase when they've developed a new experience platform. That's not a good solution, of every site be a custom codebase. We're a product with extensibility hooks. >> Savannah: Right. >> That really enables someone to get started very quickly, and that also includes bringing in content from other platforms into Arc, itself. So that journey of migrating a site is really smooth with our toolset. >> What's the history of the company? Is it, did it come from the Washington Post or was that it's original customer? What's the DNA of the firm? >> Yeah, so it was originally built by the Washington Post for the Washington Post. So, designed by digital storytellers, for storytelling. >> Savannah: And one of the largest media outlets out there. >> So, that's that "DNA", the "special sauce". >> Yeah, yeah. >> So that's where that connection is. >> That really is where it comes through. >> John: Awesome. Congratulations on- >> Now today, you know, those roots are still apparent, but we've been very responsive to other needs in the markets around commerce. There's a whole other set of DNA we've brought in, experts in understanding different systems for inventory management, so we can do a great experience on top of some of those legacy platforms. >> My final question, before we go to the challenge- >> Savannah: To the challenge. >> Is, what's next? What's on the roadmap as you look at the technology and the teams that you're managing? What's some of the next milestone or priorities for your business? >> So, it is really about growth and that's the story of Arc XP, which has driven our technology decisions. So, our choice to go serverless was driven by growth and need to make sure we had exceptional experience but most importantly that our engineers could be focused on product development and responding to what the market needed. So, that's why I'd say next year is about, it's enabling our engineers to keep up with the scaling business but still provide great value on the roadmap. >> And it's not like there's ever going to be a shortage of content or stories that need to be told. So I suspect there's a lot of resilience in what you're doing. >> And we hope to be inspired with new ways of telling stories. >> Yeah. >> So if you're in the Washington Post or other media outlets. >> John: Or theCUBE. >> Joe: Or theCUBE. >> Savannah: I know, I was just- >> There's just great formats out there. >> Best dev meeting, let's chat after, for sure. >> Exactly, that's what I've been thinking the whole time. I'm sure the wheels are turning over on this side- >> So great to have you on. >> In a lot of different ways. So, we have a new tradition here at re:Invent, where we are providing you with an opportunity for quite a sizzle reel, Instagram video, 30 second, thought leadership soundbite. What is your hot take, key theme or most important thing that you are thinking about since we're here at this year's show? >> I would say it's the energy that's building in the industry, getting back together, the collaboration, and how that's resulting in us using new technologies. You know, the conversation's no longer about shifting to the cloud. We all have huge infrastructure, the conversation's about observability, how do we know what's going in? How do we make sure we're getting the most value for our customers with those, that technology set. So, I think the energy around that is super exciting. I've always loved building products. So, next year think it's going to be a great year with that, putting together these new technologies. >> I think you nailed it. The energy really is the story and the collaboration. Joe, thank you so much for being here and sharing your story. Arc is lucky to have you and we'll close with one personal anecdote. Favorite place to sail? >> Favorite place to sail. So, I lived in the Caribbean for many years, as we were talking about earlier >> None of us are jealous up here at all. >> And so my favorite place to sail would be in the British Virgin Islands, which was closed during Covid but is now back open, so, if any you've had a chance to go to the BVI, make some time, hop on Catamaran, there's some great spots. >> Well, I think you just gave us a catalyst for our next vacation, maybe a team off-site. >> Bucket list item, of course. >> Yeah, yeah. >> Yeah, Let's bring everyone together. >> Here we go. I love it. Well Joe, thanks so much again for being on the show. We hope to have you back on theCUBE again sometime soon, and thank all of you for tuning in to this scintillating coverage that we have here, live from the AWS re:Invent show floor in Las Vegas, Nevada with John Furrier. I'm Savannah Peterson. This is theCUBE, the leader in high tech coverage. (upbeat music)

>>Hey everyone. Welcome back to the cube. Lisa Martin, with Dave ante. We're here in Las Vegas with snowflake at the snowflake summit 22. This is the fourth annual there's close to 10,000 people here. Lots going on. Customers, partners, analysts, cross media, everyone talking about all of this news. We've got a couple of guests joining us. We're gonna unpack snow park. Torston grabs the director of product management at snowflake and Joe. No NTY AI and MDM architect at Allegis group. Guys. Welcome to the program. Thank >>You so much for having >>Us. Isn't it great to be back in person? It is. >>Oh, wonderful. Yes, it >>Is. Indeed. Joe, talk to us a little bit about Allegis group. What do you do? And then tell us a little bit about your role specifically. >>Well, Allegis group is a collection of OPCA operating companies that do staffing. We're one of the biggest staffing companies in north America. We have a presence in AMEA and in the APAC region. So we work to find people jobs, and we help get 'em staffed and we help companies find people and we help individuals find >>People incredibly important these days, excuse me, incredibly important. These days. It is >>Very, it very is right >>There. Tell me a little bit about your role. You are the AI and MDM architect. You wear a lot of hats. >>Okay. So I'm a architect and I support both of those verticals within the company. So I work, I have a set of engineers and data scientists that work with me on the AI side, and we build data science models and solutions that help support what the company wants to do, right? So we build it to make business business processes faster and more streamlined. And we really see snow park and Python helping us to accelerate that and accelerate that delivery. So we're very excited about it. >>Explain snow park for, for people. I mean, I look at it as this, this wonderful sandbox. You can bring your own developer tools in, but, but explain in your words what it >>Is. Yeah. So we got interested in, in snow park because increasingly the feedback was that everybody wants to interact with snowflake through SQL. There are other languages that they would prefer to use, including Java Scala and of course, Python. Right? So then this led down to the, our, our work into snow park where we're building an infrastructure that allows us to host other languages natively on the snowflake compute platform. And now here, what we're, what we just announced is snow park for Python in public preview. So now you have the ability to natively run Python code on snowflake and benefit from the thousands of packages and libraries that the open source community around Python has contributed over the years. And that's a huge benefit for data scientists. It is ML practitioners and data engineers, because those are the, the languages and packages that are popular with them. So yeah, we very much look forward to working with the likes of you and other data scientists and, and data engineers around the Python ecosystem. >>Yeah. And, and snow park helps reduce the architectural footprint and it makes the data pipelines a little easier and less complex. We have a, we had a pipeline and it works on DMV data. And we converted that entire pipeline from Python, running on a VM to directly running down on snowflake. Right. We were able to eliminate code because you don't have to worry about multi threading, right? Because we can just set the warehouse size through a task, no more multi threading, throw that code away. Don't need to do it anymore. Right. We get the same results, but the architecture to run that pipeline gets immensely easier because it's a store procedure that's already there. And implementing that calling to that store procedure is very easy. The architecture that we use today uses six different components just to be able to run that Python code on a VM within our ecosystem to make sure that it runs on time and is scheduled and all of that. Right. But with snowflake, with snowflake and snow park and snowflake Python, it's two components. It's the store procedure and our ETL tool calling it. >>Okay. So you've simplified that, that stack. Yes. And, and eliminated all the other stuff that you had to do that now Snowflake's doing, am I correct? That you're actually taking the application development stack and the analytics stack and bringing them together? Are they merging? >>I don't know. I think in a way I'm not real sure how I would answer that question to be quite honest. I think with stream lit, there's a little bit of application that's gonna be down there. So you could maybe start to say that I'd have to see how that carries out and what we do and what we produce to really give you an answer to that. But yeah, maybe in a >>Little bit. Well, the reason I asked you is because you talk, we always talk about injecting data into apps, injecting machine intelligence and ML and AI into apps, but there are two separate stacks today. Aren't they >>Certainly the two are getting closer >>To Python Python. It gets a little better. Explain that, >>Explain, explain how >>That I just like in the keynote, right? The other day was SRE. When she showed her sample application, you can start to see that cuz you can do some data pipelining and data building and then throw that into a training module within Python, right down inside a snowflake and have it sitting there. Then you can use something like stream lit to, to expose it to your users. Right? We were talking about that the other day, about how do you get an ML and AI, after you have it running in front of people, we have a model right now that is a Mo a predictive and prescriptive model of one of our top KPIs. Right. And right now we can show it to everybody in the company, but it's through a Jupyter notebook. How do I deliver it? How do I get it in the front of people? So they can use it well with what we saw was streamlet, right? It's a perfect match. And then we can compile it. It's right down there on snowflake. And it's completely easier time to delivery to production because since it's already part of snowflake, there's no architectural review, right. As long as the code passes code review, and it's not poorly written code and isn't using a library that's dangerous, right. It's a simple deployment to production. So because it's encapsulated inside of that snowflake environment, we have approval to just use it. However we see fit. >>It's very, so that code delivery, that code review has to occur irrespective of, you know, not always whatever you're running it on. Okay. So I get that. And, and, but you, it's a frictionless environment you're saying, right. What would you have had to do prior to snowflake that you don't have to do now? >>Well, one, it's a longer review process to allow me to push the solution into production, right. Because I have to explain to my InfoSec people, right? My other it's not >>Trusted. >>Well, well don't use that word. No. Right? It got, there are checks and balances in everything that we do, >>It has to be verified. And >>That's all, it's, it's part of the, the, what I like to call the good bureaucracy, right? Those processes are in place to help all of us stay protected. >>It's the checklist. Yeah. That you >>Gotta go to. >>That's all it is. It's like fly on a plane. You, >>But that checklist gets smaller. And sometimes it's just one box now with, with Python through snow park, running down on the snowflake platform. And that's, that's the real advantage because we can do things faster. Right? We can do things easier, right? We're doing some mathematical data science right now and we're doing it through SQL, but Python will open that up much easier and allow us to deliver faster and more accurate results and easier not to mention, we're gonna try to bolt on the hybrid tables to that afterwards. >>Oh, we had talk about that. So can you, and I don't, I don't need an exact metric, but when you say faster talking 10% faster, 20% faster, 50% path >>Faster, it really depends on the solution. >>Well, gimme a range of, of the worst case, best case. >>I, I really don't have that. I don't, I wish I did. I wish I had that for you, but I really don't have >>It. I mean, obviously it's meaningful. I mean, if >>It is meaningful, it >>Has a business impact. It'll >>Be FA I think what it will do is it will speed up our work inside of our iterations. So we can then, you know, look at the code sooner. Right. And evaluate it sooner, measure it sooner, measure it faster. >>So is it fair to say that as a result, you can do more. Yeah. That's to, >>We be able do more well, and it will enable more of our people because they're used to working in Python. >>Can you talk a little bit about, from an enablement perspective, let's go up the stack to the folks at Allegis who are on the front lines, helping people get jobs. What are some of the benefits that having snow park for Python under the hood, how does it facilitate them being able to get access to data, to deliver what they need to, to their clients? >>Well, I think what we would use snowflake for a Python for there is when we're building them tools to let them know whether or not a user or a piece of talent is already within our system. Right. Things like that. Right. That's how we would leverage that. But again, it's also new. We're still figuring out what solutions we would move to Python. We are, we have some targeted, like we're, I have developers that are waiting for this and they're, and they're in private preview. Now they're playing around with it. They're ready to start using it. They're ready to start doing some analytical work on it, to get some of our analytical work out of, out of GCP. Right. Because that's where it is right now. Right. But all the data's in snowflake and it just, but we need to move that down now and take the data outta the data wasn't in snowflake before. So there, so the dashboards are up in GCP, but now that we've moved all of that data down in, down in the snowflake, the team that did that, those analytical dashboards, they want to use Python because that's the way it's written right now. So it's an easier transformation, an easier migration off of GCP and get us into snow, doing everything in snowflake, which is what we want. >>So you're saying you're doing the visualization in GCP. Is that righting? >>It's just some dashboarding. That's all, >>Not even visualization. You won't even give for. You won't even give me that. Okay. Okay. But >>Cause it's not visualization. It's just some D boardings of numbers and percentages and things like that. It's no graphic >>And it doesn't make sense to run that in snowflake, in GCP, you could just move it into AWS or, or >>No, we, what we'll be able to do now is all that data before was in GCP and all that Python code was running in GCP. We've moved all that data outta GCP, and now it's in snowflake and now we're gonna work on taking those Python scripts that we thought we were gonna have to rewrite differently. Right. Because Python, wasn't available now that Python's available, we have an easier way of getting those dashboards back out to our people. >>Okay. But you're taking it outta GCP, putting it to snowflake where anywhere, >>Well, the, so we'll build the, we'll build those, those, those dashboards. And they'll actually be, they'll be displayed through Tableau, which is our enterprise >>Tool for that. Yeah. Sure. Okay. And then when you operationalize it it'll go. >>But the idea is it's an easier pathway for us to migrate our code, our existing code it's in Python, down into snowflake, have it run against snowflake. Right. And because all the data's there >>Because it's not a, not a going out and coming back in, it's all integrated. >>We want, we, we want our people working on the data in snowflake. We want, that's our data platform. That's where we want our analytics done. Right. We don't want, we don't want, 'em done in other places. We when get all that data down and we've, we've over our data cloud journey, we've worked really hard to move all of that data. We use out of existing systems on prem, and now we're attacking our, the data that's in GCP and making sure it's down. And it's not a lot of data. And we, we fixed it with one data. Pipeline exposes all that data down on, down in snowflake now. And we're just migrating our code down to work against the snowflake platform, which is what we want. >>Why are you excited about hybrid tables? What's what, what, what's the >>Potential hybrid tables I'm excited about? Because we, so some of the data science that we do inside of snowflake produces a set of results and there recommendations, well, we have to get those recommendations back to our people back into our, our talent management system. And there's just some delays. There's about an hour delay of delivering that data back to that team. Well, with hybrid tables, I can just write it to the hybrid table. And that hybrid table can be directly accessed from our talent management system, be for the recruiters and for the hiring managers, to be able to see those recommendations and near real time. And that that's the value. >>Yep. We learned that access to real time. Data it in recent years is no longer a nice to have. It's like a huge competitive differentiator for every industry, including yours guys. Thank you for joining David me on the program, talking about snow park for Python. What that announcement means, how Allegis is leveraging the technology. We look forward to hearing what comes when it's GA >>Yeah. We're looking forward to, to it. Nice >>Guys. Great. All right guys. Thank you for our guests and Dave ante. I'm Lisa Martin. You're watching the cubes coverage of snowflake summit 22 stick around. We'll be right back with our next guest.

welcome back to the cube coverage of aws re invent 2021 i'm john furrier your host of the cube this segment we're going to talk about red hat and the aws evolving partnership a great segment really talking about how hybrid and the enterprise are evolving certainly multi-cloud on the horizon but a lot of benefits in the cloud we've been covering on the cube and on siliconangle with red hat for the past year very relevant we've got gunner helixon gm of red hat enterprise linux and joe fernandez vp of and gm of the hybrid platforms both of red hat gentlemen thanks for coming on the cube yeah thanks for having us thanks for having us john so you know you know me i'm a fanboy of red hat so i always say you know you guys made all the right investments openshift all these things that you guys made decisions years ago playing out beautifully and i think you know with amazon's reinvent you're seeing the themes all play out modern application stack you're starting to see things at the top of the stack evolving you've got 5g in the edge workloads being redefined and expanded on the cloud with cloud scale so everything has been going down to hybrid and enterprise grade level discussions this is on the wheelhouse of red hat so one congratulations but what's your reaction what do you guys see this year at re invent what's the top story i can start first yeah sure i mean i mean clearly you know aws itself is huge but as you mentioned the world is hybrid right so customers are running uh still in their data center in the amazon public cloud across multiple public clouds and out to the edge and bringing more and more workloads right so it's not just the applications it's analytics it's ai it's machine learning and so yeah we just can expect to see more discussion around that more great examples of customer use cases and as you mentioned red hat's been right in the middle of this for some time john you guys also had some success with with the fully managed open shift service called rosa rosa which is red hat open shift service on advanced another acronym but really this is about the what the customers are looking for can you take us through an update on openshift on aws because the combination of managed services in the cloud refactoring applications but working on premises is a big deal take us through that why that's so important yeah so we've had customers running uh openshift on aws for a long time right so whether it's our software uh offerings where customers deploy openshift themselves or you know our fully managed cloud service we've had cloud services on aws for over five years uh what rosa brings a red hat open shift on aws is a jointly managed service right so we're working in partnership with uh with amazon with aws to make openshift available as a jointly managed service offering it's a native aws service offering you can get it right through the aws console you can leverage your aws committed spend but most importantly you know it's something that we're working on together bringing new customers to the table for both red hat and aws and we're really excited about it because it's really helping customers accelerate their move to the public cloud and and really helping them uh you know drive that hybrid strategy that we talked about gun early you know i want to get your thoughts on this because one of the things that i love about this market right now is open source continues to be amazing continues to drive more value and this new migration of talent coming in the numbers are just continuing to to grow and grow but the importance of red hat's history with aws is pretty significant i mean red hat pioneered open source uh and has been involved with aws from the early days can you take us through a little bit of the history for the folks that may not know red hat's partnership with aws yeah i mean we've been collaborating with aws since uh 2008 so for over a decade we've been working together and what's made the partnership work is uh that we have a common interest in making sure that uh customers have a consistent approachable experience whether they're going on-premise or in the cloud nobody wants to have to go through an entire retraining and retooling exercise just to take advantage of all the great all the great advantages of the cloud and so being able to use something like red hat enterprise linux as a consistent substrate on which you can build your application platforms is really attractive so that's where the partnership started and since then we've had the ability to better integrate with the native aws services and one thing i want to point out is that you know a lot of these a lot of these integrations are kind of technical well but these are also uh it's not just about technical consistency um across these platforms it's also about operational consistency and business concerns and when you're moving into an open hybrid cloud kind of a situation that's what becomes important right you don't want to have two completely different tool sets on two completely different platforms you want as much consistency as possible as you move from one to the other and i think you and i think a lot of customers see value in that both for the retta enterprise linux side of the business and also on the openshift side of the business well that's interesting i'd love to get your both perspective on this whole enterprise focus because you know the enterprises as you know guys you've been there from the beginning they have requirements and they're sometimes they're different by enterprise so as you see cloud i mean i remember the early days of amazon it's the 15th year of aws 10th year of reinvent as a conference i mean that seems like a lifetime ago but that's not not too far ago where you know there's like well amazon might not make it it's only for developers enterprises do their own thing now it's like it's all about the enterprise how are enterprise customers evolving with you guys because they're all seeing the benefit of re-platforming but as they refactor how has red hat evolved with that with that trend how have you helped amazon yeah so as we mentioned you know enterprises you know really across the globe are adopting a hybrid cloud strategy but hybrid actually isn't just about the infrastructure so certainly the infrastructure where these enterprises are running this application is increasingly becoming hybrid as you move from data center to multiple public clouds and out to the edge but the enterprises application portfolios are also hybrid right it's a hybrid mix of very traditional monolithic anterior type applications but also new cloud native services that have either been filled built from scratch or as you mentioned you know existing applications have been refactored and then they're moving beyond the applications as i mentioned to make better use of data also evolving their processes right for how they you know build deploy and manage you know leveraging ci cd and git ops and so forth so really for us it's how do you help enterprises bring all that together right manage this hybrid infrastructure that's supporting this you know hybrid portfolio of applications and really help them evolve their processes we've been uh you know working with enterprises on these types of challenges for a long time and and we're you know now partnering with amazon to do the same in terms of our joint product and service offerings talk about the rel evolution i mean because that's the bread and butter for red hat's been there for a long time open shift again making earlier i mentioned the bets you guys made with kubernetes for instance and has all been made all the right moves so i love rosa you got me sold on that rail though has been the the tr the tried and true steady uh workhorse how has that evolved uh with workloads yeah you know it's interesting it's uh uh i think when when customers were at the stage when they were wondering if uh well can i use aws for to solve my problem or where should i use aws to solve my problem our focus was largely on kind of technical enablement can we keep up with the pace of new hardware that amazon is rolling up you know can we can we ensure that consistency with on-premise and off-premise and i think now we're starting to shift focus into uh really differentiating rel on the aws platform again integrating natively with aws services making it easier to operate in aws um and a good example of this is using tools like red hat insights which we announced i guess about a year ago which is now included in every red hat enterprise linux subscription using tools like insights in order to give customers advice on maybe potential problems that are coming up helping customers solve them kelvin customers identify problems before they before they happen helping them with performance problems um and uh again having uh additional tools like that additional cloud-based tools um makes rel uh as easy to use on the on the cloud despite all the complexity of all the you know the redeploying refactoring microservices there's now a proliferation of infrastructure options um and to the extent that rail can be the thing that is consistent solid reliable secure uh just as customers are customers getting in um then then we can make customers successful you know joe we talked about this last time we were chatting i think red hat summit or ansible fest i forget which event it was but we were talking about how modern application developers at the top of the stack just want to code they want to write some code and now they want the infrastructure's code aka devops devsecops but as this trend of moving up the stack continues to be a big theme at reinvent um there requires automation that requires a lot of stuff to happen under the covers red hat's at the center of all this action from from historical perspective pre-existing enterprises before cloud now during cloud and soon to be cloud scale how do you see that evolving because how are customers shaping their architecture because i mean this is distributed computing in the cloud it's it's essentially we've seen this movie before but now at such a scale where data security these are all new elements how do you how do you talk about that yeah well first of all as as gunner linux is a given right linux is going to be available in every environment data center public cloud edge linux combined with linux containers and kubernetes that's the abstraction like separating abstracting the applications away from the infrastructure and now it's all about how do you build on top of that to bring that automation that you mentioned right so you know we're very focused on helping customers really build you know fully automated end-to-end deployment pipelines so they can build their applications more efficiently they can automate the the continuous integration and deployment of those applications into whatever cloud or edge footprint they choose and then they can promote across environments because again it's not just about developing the applications it's about moving them all the way through to production you know where you know work their customers are relying on you know on those services to do their work and so forth and so that's that's what we're doing is you know obviously uh i think linux is a given linux containers kubernetes you know those decisions you know have been made and now it's a matter of how can we put that together uh with the automation that allows them to accelerate those deployments out to production so customers can take advantage of them you know gunner we were always joking on the cube you know i was old enough remember when we used to install linux on a server back in the day you know now a lot of these young developers never actually act to install the software and do some of those configurations because it's all automated now again the commoditization and automation trend abstraction layers some say is a good thing um so how do you see the evolution of this devops movement with the partnership of aws going forward what types of things are you working on with amazon web services and what kind of offerings can customers look forward to yeah sure so i mean it used to be that uh as you say you know linux was something that you managed with a mouse and a keyboard and uh and i think it's been quite a few years since uh since any significant amount of linux has been managed for the mouse and keyboard a lot of it is uh whatever scripts automation tools configuration management tools things like this and the investments we've made both in rel and then specifically uh rel on aws is around enabling rail to be more manageable um and so including things like something we call system roles so these are ansible modules that kind of automate routine systems administration tasks um we've made investments in something called image builder and so this is a tool that allows customers to kind of compose the operating system that they need create a blueprint for it and then kind of stamp out uh the same image whether it's uh an iso image you know so you can install it on premise or in it or in mi so we can deploy it in aws so again helping customers it's the problem used to be helping customers package and manage dependencies and and that kind of old world three and a half inch floppy disk kind of linux problems um and now we've evolved towards making uh making linux easier to deploy and manage at a grand scale um both whether you're in aws or whether you're on premise joe take us through the hybrid story i know obviously success with openshift's managed service on aws uh what's the update there for you what what are customers expecting this re invent and what's the story for uh for you guys yeah so you know the openshift managed services business is the fastest growing segment of our business we're seeing uh lots of new customers and again you know bringing new customers i think for both uh red hat and and aws through this service um so we expect to to hear from from customers uh at re invent about what they're doing again and not not only with uh with openshift and our uh our red hat solutions but really with with what they're building on top of those uh service offerings of those solutions to to sort of bring more value to their customers so that to me that's always the best part of re invent is is really hearing from customers and you know when we all start going there in person again to actually be able to meet with them one-on-one uh whether it's in person or virtual so far so looking forward to that well great to have you guys on thecube congratulations on all the success the enterprise continues to adopt more and more cloud which benefits all the work you guys have done both on the rail side and as you guys modernized with all these great services and managed services continues to be the center of all the action thanks for coming on appreciate it thanks john okay red hat's partnership with aws evolving as cloud scale edge all happening all distributed computing all happening at large scale it's thecube with cube coverage of aws re invent 2021 i'm john furrier thanks for watching [Music] you

(upbeat music) >> Welcome back to theCUBE coverage of AWS re:Invent 2021. I'm John Furrier, your host for theCUBE. In this segment, we're going to be talking about Red Hat and the AWS evolving partnership. A great segment, really talking about how Hybrid and the Enterprise are evolving, certainly multicloud and the horizon. But a lot of benefits in the cloud, we've been covering on theCUBE and on SiliconANGLE with Red Hat for the past year. Very relevant. We've got Gunnar Hellekson, GM of Red Hat Enterprise Linux, And Joe Fernandes, VP and GM of the Hybrid Platforms, both of Red Hat. Gentlemen, thanks for coming on theCUBE. >> Yeah, thanks for having us. >> Thanks for having us John. >> So, you know, me, I'm a fan boy of Red Hat. So I always say, you guys made all the right investments, OpenShift, all these things that you guys made decisions years ago playing out beautifully. And I think, you know, with Amazon's re:Invent, you're seeing the themes all play out. Modern application stack, you're starting to see things at the top of the stack evolve, you've got 5G in the Edge, workloads being redefined and expanded on the cloud with Cloud Scale. So everything has been going down to Hybrid and Enterprise grade level discussions. This is in the Wheelhouse of Red Hat. So I want to congratulate you. But what's your reaction? What do you guys see this year at re:Invent? What's the top story? >> I can start. >> Who wants to start with first? >> Sure, I mean, clearly, AWS itself is huge. But as you mentioned, the world is Hybrid, right, so customers are running still in their data center, in the Amazon Public Cloud across multiple Public Clouds and out to the Edge and bring in more and more workloads. So it's not just the applications, analytics. It's AI, it's machine learning. And so, yeah, we can expect to see more discussion around that, more great examples of customer use cases. And as you mentioned, Red Hat has been right in the middle of this for some time John. >> You guys also had some success with the fully managed OpenShift service called ROSA, R-O-S-A, which is Red Hat OpenShift Service on AWS, another acronym, but really this is about what the customers are looking for. Can you take us through an update on OpenShift on AWS, because the combination of managed services in the cloud, refactoring applications, but working on-premises is a big deal. Take us through why that's so important. >> Yeah, so, we've had customers running OpenShift on AWS for a long time, right? So whether it's our software-based offerings where customers deploy OpenShift themselves, or our fully managed cloud service. We've had cloud services on AWS for over five years. What ROSA brings or Red Hat OpenShift on AWS is a jointly managed service, right? So we're working in partnership with Amazon, with AWS to make OpenShift available as a jointly-managed service offering. It's a native AWS service offering. You can get it right through the AWS console. You can leverage your AWS committed spend. But, most importantly, you know, it's something that we're working on together. Bringing new customers to the table for both Red Hat and AWS. And we're really excited about it because it's really helping customers accelerate their move to the public cloud and really helping them drive that Hybrid strategy that we talked about. >> Gunnar, you know what I want to get your thoughts on this, because one of the things that I love about this market right now is open-source continues to be amazing, continues to drive more value, and there's new migration of talent coming in. The numbers are just continuing to grow and grow. But the importance of Red Hat's history with AWS is pretty significant. I mean, Red Hat pioneered Open-source and it's been involved with AWS from the early days. Can you take us through a little bit of history for the folks that may not know Red Hat's partnership with AWS? >> Yeah. I mean, we've been collaborating with AWS since 2008. So for over a decade we've been working together, and what's made the partnership work is that we have a common interest in making sure that customers have a consistent approachable experience. Whether they're going on-premise or in the cloud. Nobody wants to have to go through an entire retraining and retooling exercise just to take advantage of all the great advantages of the cloud. And, so being able to use something like Red Hat Enterprise Linux as a consistent substrate on which you can build your application platforms is really attractive. So, that's where the partnership started. And since then we've had the ability to better integrate with native AWS services. And one thing I want to point out is that, a lot of these integrations are kind of technical. It's not just about technical consistency across these platforms, it's also about operational consistency and business concerns. And when you're moving into an Open Hybrid Cloud kind of a situation, that's what becomes important, right? You don't want to have two completely different tool sets on two completely different platforms. You want as much consistency as possible as you move from one to the other. And I think a lot of customers see value in that, both for the Red Hat Enterprise Linux side of the business, and also on the OpenShift side of the business. >> Well that's interesting. I'd love to get your both perspective on this whole Enterprise focus, because the Enterprise is, as you know, guys you've been there from the beginning, they have requirements. And there're sometimes, they're different by Enterprise. So as you see cloud, and I remember early days of Amazon, it's the 15th year of AWS, 10th year of re:Invent as a conference. I mean, that seems like a lifetime ago. But that's not, not too far ago where, you know, it was like, well, Amazon might not make it, its only for developers. Enterprisers do their own thing. Now it's like, it's all about the Enterprise. How are Enterprise customers evolving with you guys? Because they're all seeing the benefit of replatforming. But as they refactor, how has Red Hat evolved with that trend and how have you helped Amazon? >> Yeah, so as we mentioned, Enterprisers really across the globe are adopting a Hybrid Cloud Strategy. But, Hybrid actually isn't just about the infrastructure. So, its certainly the infrastructure where these Enterprisers are running these applications is increasingly becoming Hybrid as you move from data center to multiple public clouds and out to the Edge. But the Enterprisers application portfolios are also Hybrid, right? It's a Hybrid mix of very traditional monolithic and tier type applications. But also new cloud native services that have either been built from scratch, or as you mentioned, existing applications have been refactored. And then they're moving beyond the applications, as I mentioned to make better use of data. Also evolving their processes for how they build, deploy, and manage, leveraging, CI/CD and GitOps and so forth. So really for us it's, how do you help Enterprises bring all that together, right? Manage this Hybrid infrastructure that's supporting this Hybrid portfolio of applications that really help them evolve their processes. We've been working with Enterprises on these types of challenges for a long time. And we're now partnering with Amazon to do the same in terms of our joint product and service offerings. >> Talking about the RHEL evolution. I mean, because that's the bread and butter for Red Hat. It has been there for a long time. OpenShift again, making argument earlier, I mentioned the bets you guys made with Kubernetes, for instance, and it's all been made with all the right moves. So I love ROSA. You got me sold on that. RHEL though has been the tried and true steady workhorse. How has that evolved with workloads? >> Yeah, you know, it's interesting. I think when customers were at the stage, when they were wondering, if well, can I use AWS to solve my problem, or should I use AWS to solve my problem? Our focus was largely on kind of technical enablement. Can we keep up with the pace of new hardware that Amazon is rolling up? Can we ensure that consistency with the on-premise and off-premise? And I think now we're starting to shift focus into really differentiating RHEL on the AWS platform. Again, integrating natively with AWS services, making it easier to operate in AWS. And a good example of this is using tools like Red Hat Insights, which we announced, I guess, about a year ago. Which is now included in every Red Hat Enterprise Linux subscription. Using tools like Insights in order to give customers advice on maybe potential problems that are coming up, helping customer solve them. Can the customers identify problems before they happen? Helping them with performance problems. And again, having additional tools like that, additional cloud-based tools, makes RHEL as easy to use on the Cloud despite all the complexity of all the redeploying, refactoring, microservices, there is now a proliferation of infrastructure options, and to the extent that RHEL can be the thing that is consistent, solid, reliable, secure, just as customers are getting in, then we can make customer successful. >> You know, Joe, we talked about this last time we were chatting, I think Red Hat Summit or Ansible Fest, I forget which event it was, but we were talking about how modern application developers at the top of the stack just want to code. They want to write some code, and now they want the infrastructure's code, AKA DevOps, DevSecOps, but as this trend of moving up the stack continues to be a big theme at re:Invent, that requires automation. That requires a lot of stuff that happened under the covers. Red Hat is at the center of all this action from historical perspective, pre-existing Enterprises before Cloud now, during Cloud, and soon to be Cloud Scale, how do you see that evolving? Because how are customers shaping their architecture? Cause this is distributed computing in the cloud. It's essentially, we've seen this moving before, but now at such a scale where data, security, these are all new elements. How do you talk about that? >> Yeah, well, first of all, got to mention, Linux is a given right. Linux is going to be available in every environment, data center, Public Cloud, Edge. Linux combined with Linux containers and Kubernetes, that's the abstraction like abstracting the applications away from the infrastructure. And now it's all about how do you build on top of that to bring that automation that you mentioned. So, we're very focused on helping customers really build fully automated end to end deployment pipelines, so they can build their applications more efficiently. They can automate the continuous integration and deployment of those applications into whatever Cloud or Edge footprint they choose. And that they can promote across environments. Because again, it's not just about developing the applications, it's about moving them all the way through to production where their customers are relying on those services to do their work and so forth. And so that's what we're doing is, you know, obviously I think, Linux is a given, Linux, Containers, Kubernetes. Those decisions have been made and now it's a matter of how can we put that together with the automation that allows them to accelerate those deployments out to production so customers can take advantage of them? >> You know, Gunnar, we were joking in theCUBE. I was old enough to remember we used to install Linux on a server back in the day. Now a lot of these young developers never actually have to install the software and do some of those configurations 'cause it's all automated now. Again, the commoditization and automation trend, abstraction layers, some say, is a good thing. So how do you see the evolution of this DevOps movement with the partnership with AWS going forward? What types of things are you working on with Amazon Web Services and what kind of offerings can customers look forward to? >> Yeah, sure. So, I mean, it used to be that as you say, Linux was something that you managed with a mouse and keyboard. And I think it's been quite a few years since any significant amount of Linux has been managed with a mouse and a keyboard. A lot of it is scripts, automation tools, configuration management tools, things like this. And the investments we've made both in RHEL and in specifically RHEL on AWS is around enabling RHEL to be more manageable. And so, including things like something we call System Roles. So these are Ansible modules that kind of automate routine system's administration tasks. We've made investments in something called Image Builder. And so this is a tool that allows customers to kind of compose the operating system that they need, create a blueprint for it, and then kind of stamp out the same image, whether it's an ISO image, so you can install it on-premise or an AMI so we can deploy it in AWS. So again, the problem used to be helping customers package and manage dependencies and that kind of old world, three and a half-inch floppy disc kind of Linux problems. And now we've evolved towards making Linux easier to deploy and manage at a grand scale whether you're in AWS or whether you're On premise. >> Joe, take us through the Hybrid story. I know obviously success with OpenShifts Managed Service on AWS. What's the update there for you? What are customers expecting this re:Invent and what's the story for you guys? >> Yeah, so, you know, the OpenShift Managed Services business this is the fastest growing segment of our business. We're seeing lots of new customers. And again, bringing new customers, I think for both Red Hat and AWS through this service. So, we expected to hear from customers at re:Invent about what they're doing. Again, not only with OpenShift and our Red Hat solutions, but really with what they're building on top of those service offerings, of those solutions to sort of bring more value to their customers. To me, that's always the best part of re:Invent is really hearing from customers. And when we all start going there in person again, to actually be able to meet with them one-on-one, whether it's in person or virtual and so forth. So, looking forward to that. >> Well, great to have you guys on theCUBE. Congratulations on all success. The Enterprise continues to adopt more and more Cloud which benefits all the work you guys have done both on the RHEL side, and as you guys modernize with all these great services and managed services continues to be the center of all the action. Thanks for coming on. Appreciate it. >> Thanks John. >> Thank you. >> Okay, Red Hat's partnership with AWS evolving as Cloud scale Edge, all distributed computing, all happening at large scale. This is theCUBE with CUBE coverage of AWS re:Invent 2021. I'm John Furrier. Thanks for watching. (upbeat music)

(cheerful music) >> Hello everyone, welcome to theCUBE's coverage of AnsibleFest 2021, with Red Hat. Topic of this power panel is the future of automation, we've got a great lineup of CUBE alumni, Joe Fitzgerald, vice president, general manager of the Red Hat business unit, thanks for coming on, Tom Anderson, vice president, product manager of Red Hat, and Alessandro Perilli, the senior director of product market at Red, all good CUBE alumni. Distinct power panel, Joe we'll start out with you, what have you seen in automation game right now, 'cause it continues to evolve. I mean you can't go to an event, a virtual event, or read anything online without hearing AI automation, automation hybrid, automation hybrid hybrid hybrid hybrid, I mean automation is the top conversation in almost all verticals. What do you see happening right now? >> Yeah, it's sort of amazing, you know? Automation is quite fashionable these days, as you pointed out. Automation's always been on the radar of a lot of enterprises, and I think it was always perceived as sort of like that, an efficiency, a task model thing, that people did. Now automation is, if you believe some of the analysts, it's up to a board room imperative in some cases. So we are seeing with our customers that the level of complexity they're dealing with, particularly exaggerated by what's gone past year and a half in the world, is putting a tremendous amount of pressure, attention and importance on automation. So automation's definitely one of the busiest places to be right now. >> What's the big change this year, though? I mean we love the automation conversation, we had it last year a lot too, as well. What's the change, what's the trend right now that's driving this next level automation conversation with customers? >> Well, I'll ask my colleagues to comment on that in a second, but, the challenges here with automation, is people are constrained now, they can't access facilities as easy as they used to be able to. They still need to go fast, some businesses have had to expand dramatically, and introduce new services to handle all sorts of new scenarios, they've had to deploy things faster. Security, not a week goes by you don't read about something going on regarding security and breaches and hacking and things like that, so they're trying to secure things as fast as possible, right, and deploy critical fixes and patches and things like that. So there's just tremendous amount of activity, that's really been exaggerated by what's gone on over the past year. >> And all of this is being compounded with a nature of increasing complexity, that we're seeing in the architecture, explosion microservices, the adoption en masse of containers, and the adoption of multiple clouds for most customers around the world. So really, the extension of the IT environment, especially for large enterprises, enormous for any team, no matter how big it is, so how scale it is, to really go after and look for all the systems, and then the complexity of the architectures, is enormous within that IT environment. It is impossible to scale the applications and to scale the infrastructure, and not scale the IT operations. And so automation becomes really a way to scale IT operations, rather than just keep repeating the same steps over and over, in an attempt to simplify, or to reduce costs. It's well beyond that at this point. >> That's a great point. Tom, what's your reaction to this, because Alessandro brings up a good point, developers are going faster than ever before. The changes of speed and complexity have gone up, so the demand for the IT and/or security groups, or anyone, to be faster, not weeks, minutes. We're talking about a complete time shift here. >> Yeah, so I talk to a lot of customers, and what I keep hearing again and again from them is kind of two things, which is, a need for skills, and reskilling existing staff. When Alessandro talks about the complexity and the scale, think about all the different new tools, new environments, new platforms that these employees and these associates are being exposed to and expected to be able to handle. So, a real, not a skill shortage, but a stress on the skills of the organization. And then secondly, really, our customers are talking to us about the culture in the environment itself, the culture of collaboration, the culture of automation, and the kind of impact that has in our organization, the way teams are now expected to work together, to share information, to share automation, to push, you know, we talk about shifting left in a lot of things now in IT, automation is now shifting left, pushing automation and access to subsystems, IT subsystems and resources, into the hands of people who traditionally haven't had direct access to those resources. So really kind of shift in skills, and a shift in culture I see. >> Ah, the culture. (indistinct), I want to come back to that culture thing, but I want to ask you specifically on that point, do you think automation users still view automation as just repeating and simplifying processes that they already are doing? You've heard the term, "Done it three times, automate it." Is that definition changing and evolving, what's your thoughts? >> Yeah, IT is really changing, going from the traditional, "I'm a network engineer and I use a command line to update my devices I'm responsible for, the config devices, and then I decide to write a playbook using a really cool product like Ansible to drive automation into my daily tasks." And then it comes up to exposing, again, exposing that subsystem I'm responsible for, whatever it is, storage, network, compute, whatever it is, exposing that op so other people can consume it without me being involved, right? So that's a real change in a mindset, and tooling, and approach, that I'm going to expose that op to a set of workflows, business workflows, that drive automation throughout an organization. So that's a real kind of evolution of automation, (indistinct) first, and that's usually focused mostly on day zero, provisioning of a new service. Now we see a lot more focus, or a lot of additional focus on day two operations. How do I automate my day two operations to make them a lot more efficient, as my scale and complexity grows? How do I take the human element out of operating this on a day to day basis? >> So you're saying basically, if I understand you correctly, the system's architecture view, or mindset, around automation, it moves from "Hey, I'm going to use," and Ansible by the way is great for "Hey, I want to automate something, I'm doing a lot," that's cool. But you're looking at it differently. If I understand you correctly, you're saying the automation has to be a system view, meaning you create the rules of the road so that automation can happen at the front lines of the CICD pipeline. You mentioned shift left, is that the difference, is that kind of what's happening here, that's beyond just doing automation, because you can automate it, so you've done that, this is like the next level, is that what you're getting at? >> It is, and we joke about it a little bit, crushing silos, right? Breaking down silos, and again, I keep talking about culture, it really is important, tools are important and technology's important, but the culture's super important, and trying to think of that thing from a systems mindset, of sort of workflows and orchestration of a business process that touches IT components, and how do I automate that and expose that to that workflow, without a human having to touch it, right? Yet still enforce my security protocols, my performance expectations, my compliance stuff, all of that stuff still needs to be enforced, and that's where repeatable automation comes in, of being able to expose this stuff up into these system-level workflows. >> And then there is another element to this (indistinct), I think it's really important to attach to this, the element of speed. We talk about complexity, we talk about scale, but then there is this emerging third dimension, as I call it, that is the speed. And the speed has a number of different articulation, it's the speed when you're thinking about how quickly you need to deliver the application. If you're in a very competitive environment, think about web scale startups for example, or companies in an emerging market, and then you have the speed in terms of reacting to a cybersecurity attack, which Tom just mentioned. And then you have the third kind of speed I'm thinking about right now, which is the increasing amount of artificial intelligence, so an algorithmic kind of operation that is taking place in the organization. For now it's still very limited, but it's not unthinkable that going forward, the operations will be driven, or at least assisted by artificial intelligence. This speed, just like the scale and the complexity we mentioned before, are impossible to be addressed by a single team, and so automation becomes indispensable. >> Yeah, that's a great point, I want to just double click on that, I mean both Tom and Joe were just talking about system, they used the word system. In a subsystem, if one is going faster than the other, to your point, there's a bottleneck there. So if the IT group or security groups are going to take time to approve things, they're not putting rules to the road together to automate and help developers be faster, because look, it's clear, we've been reporting on this in theCUBE, cloud developers are fast. They're moving really fast with code. And so what happens is, if they're going to shift left, that means they're going to be at the point of coding to set policies on security. So, that's going to put pressure on the other subsystems to go faster, so they have to then expose rules of the road, or I'm just making that up, but policy base, or have some systems thinking. They can't just be the old way of saying "No, slow it down." So this is a cultural thing, I think Joe, you brought up culture, Alessandro, you brought up culture. Is that still there? That speed, fast team here and a slow team here? Is that still around, or people getting faster on both sides? And I'm kind of talking about IT, generally speaking, they tend to be slower than the developers. >> Well, just a couple comments, first of all, you heard silos, you heard complexity, you heard speed, talked about shift left. Let me sort of maybe tie those together, right? What's happened to date is every silo has their own set of tooling, right? And so one silo might move very fast, with a very private set of tools, or network management, or security, or whatever, right? And if you think about it, one of the number one skills gaps right now is for automation people. But if an automation person has to learn 17 different tools, 'cause I'm running on three public clouds, I'm on-premise, edge, and I'm doing things to move network storage, compute, security, all sorts of different systems, the tooling is so complicated, right, that I end up with a bunch of specialists. Which can only do one or two things, because they don't know the other domains and they don't know the skills. One of the things we've seen from our customers, I think this is a fundamental shift in automation, is that what we've done with Ansible in particular is, we actually adopted Ansible because of its simplicity. It's actually human-readable, you don't have to be a hardcore programmer to write automation. So that allows the emergence of citizen creators of automation. There's not like a group in some ivory tower that now can make automation and they do it for the masses. Individuals can now use Ansible to create automation. Going cross-domain, Ansible automation touches networks, security, storage, compute, cloud, edge, Linux, Windows, containers, traditional, ITSM, it touches so many systems, that basically what you have is you have a set of power tooling, in Ansible, that allows you now to share automation across teams, 'cause they speak the same language, right? And that's how you go faster. If every silo is fast, but when you have to go inter-silo you slow down, or have to open a ticket, or have some (indistinct) mismatch, it causes delays, errors, and exposures. >> I think that is a very key point, I mean that delay of opening up tickets, not being responsive, Alessandro, you put up machine learning and AI, I mean if you think about what that could do from an automation standpoint, if you can publish the HIPAA rules for your healthcare, you can just traverse that with a bot, right? I mean this is the new... This just saves so much time, why even open up a ticket? So if you can shift left and do the security, and there's kind of rules there, this is a trend, how do you make that happen, how do you bust the silos, and I guess that's the question I'd love to get everyone to react to, because that implies some sort of horizontally scalable control plane. How does someone do that in an architectural way, that doesn't really kind of, maybe break everything, or make the (indistinct) go into a cultural sideways situation? >> Maybe I can jump in, and grab this one, and then maybe ask Alessandro to weigh in afterwards, but, what we've seen and what you'll see some of the speakers at AnsibleFest this year talk about, from a cultural perspective is bringing teams together across automation guilds, JPMC calls it a community of practice, where they're bringing hundreds and thousands of individuals in the organization together virtually, into these teams that share best practices, and processes and automation that they've created. Secondly, and this is a little bit of a shameless plug for Ansible, which is having a common language, a common automation language across these teams, so that sharing becomes obviously a lot easier when you're using the same language. And then thirdly, what we see a lot now is people treating automation as code. Storing that, and get version managing and version controlling and checking in, checking out, really thinking of automation differently from an individual writing a script, to this being infrastructure or whatever my subsystem is, managed it and automated it as code, and thinking of themselves as people responsible for code. >> These are all great points. I think that on top of all these things, there is an additional element which is change management. You cannot count on technology alone to change something that is purely cultural, as we kept saying during this video right now. So, I believe that a key element to win, to succeed in an automation project, is to couple the technology, great technology, easy to understand, able to become the common language as Tom just said, with an effort in change management that starts from the top. It's something you don't see very often because a technology vendor rarely works with a more consulting firm, but it's definitely an area that I think would be very interesting to explore for our customers. >> That's a great point on the change management, but let me ask you, what do you think it needs to make automation more frictionless for users, what do you see that needs to happen, Alessandro? >> I think there are at least a couple of elements that need to change. The first one is that, the effort that we're seeing right now in the industry, to further democratize the capability to automate has to go one notch further. And by that I mean, implementing cell service provisioning portals and ways for automatically execute an automation workflow that already exists, so that an end user, somebody that works in the line of business, and doesn't understand necessarily what the automation workflow, the script is doing, still able to use it, to consume it when it, she or he needs to use it. This is the first element, and then the second element that is definitely more ambitious, is about the language, about how do I actually write the automation workflow? This is a key problem. It's true that some automation engines and some workflows have done, historically speaking, a better job than others, in simplifying the way we write automation workflows, and definitely this is much simpler than writing code with a programming language, and it's simpler than writing automation compared to a tool that we use 10, 15 years ago. But still, there is a certain amount of complexity, because you need to understand how to write in a way that the automation framework understands, and you need even before that, you need to express what you want to achieve, and in a way that the automation engine understands. So, I'm thinking that going forward we'll start to see artificial intelligence being applied to this problem, in a way that's very similar to what OpenAI Microsoft are doing with Codex, the capability that is a model that allows a person to write in plain English through a comment in code, to translate that comment into actual code, taken from GitHub or through the machine learning process that's been done. I'm really thinking that going forward, we will start to see some effort in the same direction, but applied to automation. What if the AI could assist us, not replace us, in writing the automation workflow so that more people are capable to translating what they want to achieve, in a way that is automatable? >> So you're saying the language, making it easy to program, or write, or create. Being a creator of automation. And then having that be available as code, with other code, so there's kind of this new paradigm of automating the automation. >> In a sense, this is absolutely true, yes. >> In addition to that, John, I think there's another dimension here which is often overlooked, which we do spend a lot of time on. It's one thing to have things like Alessandro mentioned, that are front edge in terms of helping you write code, but you want to know something? In big organizations, a lot of times what we find is, someone's already written the code that you need. You know what the problem is? You don't know about it, you can't find it, you can't share it and you can't collaborate on it, so the best code is something that somebody's already invested the time to write, test, burn in, certify, what if they could share it, and what if people could find it, and then reuse it? Right, everybody's talking about low code, no code, well, reuse is the best, right? Because you've already invested expertise into doing it. So we've spent a lot of time working with our customers based on their feedback, on building the tools necessary for them to share automation, to collaborate on it, certify it, and also to create that supply chain from partners who create integrations and interfaces to their systems, and to be able to share that content through the supply chain out to our customers and have them be able to share automation across very large globally distributed organizations. Very powerful. >> That's a powerful point, I mean reuse, leverage there, is phenomenal. Discovery engine's got to be built. You got to know, I mean someone's got to build a search engine for the code. "Hey code, who's written some code?" But just a whole 'nother mindset, so this brings up my next question for you guys, 'cause this is really, we're teasing out the biggest things coming next in automation. These are all great points, they're all about the future, where will the puck be, let's skate to where the puck will be, but it's computer science and automation that's being democratized and opened up more, so it's, what do you guys think is the biggest thing coming next for automation? >> Joe, you want to go next? >> Sure. Sure. Yeah, I'll take it. So we're getting a glimpse of that with a number of customers right now that we're working with that are doing things around concepts like self-healing infrastructures. Well what the heck is that? Basically, it's tying event systems, and AI, which is looking at what's going on in an environment, and deciding that something is broken, sub-optimal, spending too much, there's some issue that needs to be dealt with. In the old days, it was, that system would stop with opening a ticket, dispatch some people who were either manually or semi-automated go fix their whatever. Now people are connecting these systems and saying "Wait a minute. I've got all this rich data coming through my eventing systems. I can make some sense out of it with AI or machine learning. Then I can drive automation, I just eliminated a whole bunch of people, time, exposure, cost, everything else." So I think that, sort of a ventureman automation is going to be huge. I'm going to argue that every single system in the world that uses AI, the result of that's going to be, I want to go do something, I want to change, optimize my move, secure, stop, start, relocate, how's that going to get done? It's going to get done with automation. >> And what Joe just said is really highly successful in the consumer space. If you think about solutions like If This Then That, or Zapier for example, those are examples of event-driven automation. They've been in the consumer space for a long time, and they are wildly popular to the point that there are dozens of clones and competitors. The enterprise space, it didn't adopt the same approach so far, but we start to see event bridges, and event hubs that can really help with this. And this really connects to the previous point, at this point I'm a broken record, which is about the speed and the complexity. If the environment is so spread out, so complex, and it goes all the way to the edge, and all these events take place at a neck-breaking pace, the only way for you is to tie the automation workflows that you have written, to a trigger, an event that takes place at some point, according to your logic. >> Tom, what are your thoughts? >> Yeah, last but not least on that kind of thread, which is sort of the architectures as we get out to the edge, what does it take to automate things at the edge? We thought there was a big jump from data center to cloud, and now when you start extending that out to the edge, am I going to need a new automation platform to handle those edge devices? Will I need a new language, will I need a new team, or can I connect these things together using a common platform to develop the automate at the edge? And I think that's where we see some of our customers moving now, which is automating those edge environments which have become critical to their business. >> Awesome, I want to ask one final question while I've got you guys here in this power panel, great insights here. Operational complexity was mentioned, skills gap was mentioned earlier, I want to ask you guys about the organizational behavior and dynamic going on with this change. Automation, hybrid, multi-cloud, all happening. When you start getting into speed of application development for the modern app, opensource where things are opening up and things are going to be democratized with automation and code and writing automation, and scaling that, you're going to have a cultural battle that's happening, and we're kind of seeing it play out in real time. DevOps has kind of gone and been successful, and we're seeing cloud-native bring new innovation, people are refactoring their business models with cloud technologies, now the edge is here, so this idea of speed, shifting left, from a developer standpoint, is putting pressure on the old, incumbent systems, like the security group, or the IT group that's still holding onto their ticketing system, and they're slower, they're getting requests, and the developer's like "Okay, go faster, I want this done faster." So we're seeing departments reorganizing. What do you guys see, 'cause Red Hat, you guys have been in there, all these big accounts for the generation of this modern era. What's the cultural dynamics happening, and what can companies do to be successful, to get to the next level? >> So I think for us, John, we certainly see it and we experience it, across thousands of customers, and what we've done as an organization is put together adoption journeys, a consulting engagement for our customers around an automation adoption journey, and that isn't just about the technology, it's all throughout that technology, it's about those cultural things, thinking differently about the way I automate and the way I share, and the way I do these tasks. So it's as much about cultural and process as it is about technology. And our customers are asking us for that help. Red Hat, you have thousands of customers that are using this product, surely you can come and tell us how we can achieve more with automation, how can we break down these silos, how can we move faster, and so we've put together these offerings, both directly as well as with our partners, to try and help these customers kind of get over that cultural hump. >> Awesome. Anyone else want to react to the cultural shift and dynamics and how it can play out in a positive way? >> Yeah, I think that it's a huge issue. We always talk about people, processes, and technology. Well the people issue's a really big deal here. We're seeing customers, huge organizations, with really capable teams building apps and services and infrastructures, saying "Help me think about automation in a new way." The old days, it was "Hey, I'm thinking about it as a cost savings thing." Yeah, there's still cost savings in there. To your point, John, now they're talking about speed, and security, and things like that. How fast, zero day exploits, now it's like zero hour exploits. How fast can I think about securing something? You know, time to heal, time to secure, time to optimize, so people are asking us, "What are the best practices? What is the best way to look at what I've got, my automation deficits," used to have tech deficits, now you got automation deficits, right? "What do I need to do culturally?" It's very similar to what happened with DevOps, right? Getting teams to get together and think about it differently and holistically, that same sort of transition is happening, and we're helping customers do that, 'cause we're talking to a lot of them where you've got the scholars have been through it. >> Awesome. Alessandro, your thoughts on this issue. >> I think that what Tom and Joe just said is going to further aggravate, it's going to happen more and more going forward, and there is a reason for that. And this connects back with the skill problem, that we discussed before. In the last 10 years, I've seen growing demand for developers to become experts in a lot of areas that have nothing to do with development, code development. They had to become experts in cloud infrastructures, they had to become experts in security because, you've probably heard this many times, security's everybody's responsibility. Now they've been asked to become experts in artificial intelligence, transforming their title into something like ML engineer. The amount of skills and disciplines that they need to master, alone, by themself, would require a lifetime of work. And we're asking human beings to get better and better at all of these things, and all of the best practice. It's absolutely impossible. And so the only way for them, yeah, five jobs in one, six jobs in one, right? Probably for the same seller, and the only way that these people can execute the best practice, enforce the best practice, if the best practices are encoded in automation workflow, not necessarily written by them, but by somebody else, and execute them at the right time, the right context, and for the right reason. >> It's like the five tool player in baseball, you got to do five different things, I mean this is, you got to do AI, you got to do machine learning, you got to have access to all the data, you got to do all these different things. This is the future of automation, and automation's critical. I've never heard that term, automation deficit or automation debt, we used to talk about tech debt, but I think automation is so important because the only way to go fast is to have automation, kind of at the center of it. This is a huge, huge topic. Thank you very much for coming on, power panel on the future of automation, Joe, Tom, Alessandro from Red Hat, thanks for coming on, everyone, really appreciate the insight, great conversation. >> Thanks, John. >> 'Kay, this is theCUBE's coverage of AnsibleFest 2021 virtual. This is theCUBE, I'm John Furrier, your host, thanks for watching. (calm music)

(joyful music) >> According to storage guru, Fred Moore, 60 to 80% of all stored data is archival data, leading to the need for what he calls the infinite archive. And in this world, digital customers require inexpensive access to archive data that's protected, it's got to be available, durable, it's got to be able to scale and also has to support the governance and compliance edicts of the organizations. Welcome to this next session of the AWS Storage Day with theCUBE. I'm your host, Dave Vellante. We're going to dig into the topic of archiving and digitally preserving data and we're joined by Joe Fitzgerald, who's the general manager of Amazon S3 Glacier. Joe, welcome to the program. >> Hey, Dave. It's great to be here. Thanks for having me. >> Okay, I remember early last decade, AWS announced Glacier, it got a lot of buzz. And since then you've evolved your archival storage services, strategy and offerings. First question: why should customers archive their data in AWS? >> That's a great question. I think Amazon S3 Glacier is a great place for customers to archive data. And I think the preface that you gave, I think, covers a lot of the reasons why customers are looking to archive data on the cloud. We're finding a lot of customers have a lot of data. And if you think about it, most of the world's data is cold by nature. It's not data that you're accessing all the time. So if you don't have an archival story as part of your data strategy, I think you're missing out on a cost savings opportunity. So one of the reasons we're finding customers looking to move data to S3 Glacier is because of cost. With Glacier Deep Archive, we have an industry-leading price point of a dollar per terabyte per month. I think another reason that we're finding customers wanting to move data to the cloud, into Glacier, is because of the security, durability and availability that we offer. Instead of having to worry about some of the most valuable data that your company has and worrying about that being in a tape library that doesn't get access very often on premises or offsite in a data locker that you don't really have access to, and we offer the best story in terms of the durability and security and availability of that data. And I think the other reason that we're finding customers wanting to move data to S3 Glacier is just the flexibility and agility that having your data in the cloud offers. A lot of the data, you can put it in Deep Archive and have it sit there and not access it but then if you have some sort of event that you want to access that data, you can get that back very quickly, as well as put the power the rest of the AWS offerings, whether that's our compute offerings, our machine learning and analytics offerings. So you just have unmatched flexibility, cost, and durability of your data. So we're finding a lot of customers looking to optimize their business by moving their archive data to the cloud. >> So let's stick on the business case for a minute. You nailed the cost side of the equation. Clearly, you mentioned several of the benefits, but for those customers that may not be leaning in to archive data, how do they think about the cost-benefit analysis when you talk to customers, what are you hearing from them, the ones that have used your services to archive data, what are the benefits that they're getting? >> It's a great question. I think we find customers fall into a few different camps and use cases and one thing that we recommend as a starting point is if you have a lot of data and you're not really familiar with your access patterns, like what part of the data is warm, what part is cold? We offer a storage class called S3 intelligent tiering. And what that storage class does is it optimizes the placement of that data and the cost of that data based on the access patterns. So if it's data that is accessed very regularly, it'll sit in one of the warmer storage tiers. If it's accessed infrequently, it'll move down into the infrequent access tier or to the archive or deep archive access tiers. So it's a great way for customers who are struggling to think about archive, because it's not something that every customer thinks about everyday, to get automatic cost savings. And then for customers who have either larger amounts of data or better understand the access patterns, like some of the industries that we're seeing, like autonomous vehicles, they might generate tons of training data from running the autonomous vehicles. And they know, okay, this data, we're not actively using it, but it's also very valuable. They don't want to throw it away. They'll choose to move that data into an archive tier. So a lot of it comes down to the degree to which you're able to easily understand the access pattern of the data to figure out which storage class and which archive storage class maps best to your use case. >> I get it, so if you add that deep archive tier, you automagically get the benefit, thanks to the intelligent tiering. What about industry patterns? I mean, obviously, highly regulated industries have compliance issues and you have data intensive industries are going to potentially have this because they want to lower costs, but do you see any patterns emerging? I mean every industry needs this, but are there any industries that are getting more bang from the buck that you see? >> I would say every industry definitely has archived data. So we have customers in every vertical segment. I think some of the ones that we're definitely seeing more activity from would be media and entertainment customers are a great fit for archive. If you think about even digital native studios who are generating very high definition footage and they take all that footage, they produce the movie, but they have a lot of original data that they might reuse, that you remaster, director's cut, to use later, they're finding archive is a great fit for that. So they're able to use S3 Standard for their active production, but when they're done finishing a movie or production, they can save all that valuable original footage and move it in deep archive and just know that it's going to be there whenever they might need to use it. Another use case, we're staying in media, entertainment, similar to that and this is a good use case for S3 Glacier is if you have sports footage from like the '60s and then there's some sort of breaking news event about some athlete that you want to be able to cut a shot for the six o'clock news, with S3 Glacier and expedited retrievals, you're able to get that data back in a couple of minutes and that way you have the benefit of very low cost archive storage, but being able to get the immediacy of having some of that data back when you need it. So that's just some of the examples that we're seeing in terms of how customers are using archives. >> I love that example because the prevailing wisdom is the older data is, the less valuable it is, but if you can pull a clip up of Babe Ruth at the right time, even though it's a little grainy, wow, that's huge value for the-- >> We're finding like lots of customers that they've retained this data, they haven't known why they're going to need it, they just intrinsically know this data is really valuable, we might need it. And then as they look for new opportunities and they're like, hey, we're going to remaster this. And they've gone through a lot of digital transformation. So we're seeing companies have decades of original material moving into the cloud. We're also seeing fairly nascent startups who are also just generating lots of archive data. So it's just one of the many use cases we see from our customers love Glacier. >> Data hoarders heaven. I love it. Okay, Joe. Let's wrap up. Give us your closing thoughts, how you see the future of this business, where you want to take your business for your customers. >> Mostly, we just really want to help customers optimize their storage and realize the potential of their data. So for a lot of customers, that really just comes down to knowing that S3 glacier is a great and trusted place for their data, and that they're able to meet their compliance and regulatory needs, but for a lot of other customers, they're looking to transform their business and reinvent themselves as they move to the cloud. And I think we're just excited by a lot of emerging use cases and being able to find that flexibility of having very low cost storage, as well as being able to get access to that data and hook it up into the other AWS services and really realize the potential of their data. >> 100%, we've seen it over the decades, cost drops and use cases explode. Thank you, Joe. Thanks so much for coming on theCUBE. >> Thanks a lot, Dave. It's been great being here. >> All right, keep it right there for more storage and data insights. You're watching AWS Storage Day on theCUBE. (tranquil music)

(upbeat music) >> According to storage guru, Fred Moore, 60 to 80% of all stored data is archival data leading to the need for what he calls the infinite archive, In this world digital customers require inexpensive access to archive data that's protected it's got to be available, durable, it's got to be able to scale and also has to support the governance and compliance edicts of the organizations. Welcome to this next session of the AWS storage day with The Cube. I'm your host, Dave Vellante. We're going to dig into the topic of archiving and digitally preserving data and we're joined by Joe Fitzgerald, who is the general manager of Amazon S3 Glacier, Joe. Welcome to the program. >> Hey Dave, it's great to be here. Thanks for having me. >> Yeah, I remember early last decade, AWS announced Glacier, it got a lot of buzz, and since then you've evolved your archival storage services, strategy and offerings. First question. Why should customers archive their data in AWS? >> That's a great question. I think Amazon S3 Glacier is a great place for customers to archive data and I think the preface that you gave, I think covers a lot of the reasons why customers are looking to archive data on the cloud. We're finding a lot of customers have a lot of data. And if you think about it, most of the world's data is cold by nature. It's not data that you're accessing all the time. So if you don't have an archival story as part of your data strategy, I think you're missing out on a cost savings opportunity. So one of the reasons we're finding customers looking to move data S3 glacier is because of cost with Glacier Deep archive we have an industry leading price point of a dollar per terabyte per month. I think another reason that we're finding customers wanting to move data to the cloud into glacier is because of the security, durability, and availability that we offer. Instead of having to worry about some of the most valuable data that your company has and worrying about that being in a tape library that doesn't get accessed very often on premises or offsite in a, in a data locker that you don't really have access to. And we offer the best story in terms of the durability and security and availability of that data. And I think the other reason that we're finding customers wanting to move data to S3 Glacier is just the flexibility and agility that having your data in the cloud offers. A lot of the data, you can put it in deep archive and have it sit there and not access it, but then if you have, you know, some sort of event that you want to access that data, you can get that back very quickly, as well as put to power the rest of the AWS offerings, whether that's our compute offerings, or our machine learning and analytics offerings. So you just have like unmatched, you know, flexibility, cost, and durability of your data. So we're finding a lot of customers looking to optimize their business by moving their archive data to the cloud. >> Let's stick on the business case for a minute. I mean, you kind of nailed the cost side of the equation. Clearly you mentioned several of the benefits, but, but for those customers that may not be leaning in to, to, to archive data, how do they think about the cost benefit analysis when you talk to customers, what are you hearing from them? The ones that have used your services to archive data, what are the benefits that they're getting? >> It's a great question. I think we find customers fall into a few different, you know, camps in use cases. And one thing that we recommend as a starting point is if you have a lot of data and you're not really familiar with your access patterns, like which what, what part of the data is warm, what part is cold, we offer a storage class called S3 intelligent tiering. And what that storage class does is it optimizes the placement of that data and the cost of that data based on the access patterns. So if, if it's data that is accessed very regularly, it'll sit in one of the warmer storage tiers. If it's, accessed infrequently, it'll move down into the infrequent access tier or into the archive or deep archive access tiers. So it's a great way for customers who are struggling to think about archive, because it's not something that every customer thinks about every day to get on automatic cost savings. And then for customers who have, you know, either larger amounts of data or, or better understand the access patterns, like, you know, some of the industries that we're seeing like in, you know, autonomous vehicles, you know, they, they might have, they might generate like tons of training data from, from, you know, from running the autonomous vehicles. And they kind of know, okay, this data it's, it's, we're not actively using it, but it's also very valuable. They don't want to throw it away, they'll choose to move that data into an archive tier. So a lot of it kind of comes down to the degree to which you're able to easily understand the access pattern of the data to figure out which storage class and which archive storage class match best to your use case. >> I get it, so if you add that deep archive tier, you auto-magically get the benefit thanks to the intelligent tiering. What about industry patterns? I mean, obviously highly regulated industries have compliance issues. You know,, data intensive industries are going to potentially have this because they want to lower lower costs, but do you see any patterns emerging? I mean, every industry kind of needs this, but, but are there any industries that are getting more bang from the buck that, that you see? >> I would say every industry definitely has archived data. So we have, we have customers in every vertical segment. I think some of the ones that we're definitely seeing more activity from would be, you know, media and entertainment customers are a great fit for archive. If you think about, you know, even like digital native studios who are, you know, generate, you know, very high definition footage and, you know, they take all that footage, they produce the movie, but they have a lot of original data that they, you know, they, they might reuse. You know, remaster director's cut or, you know, to use later. They're finding archive is a great fit for that. So they're able to use S3 standard for their active production, but when they're done finishing a movie or production, they can save all that valuable original footage and move it into deep archive and just know that it's going to be there whenever they might need to use it. Another use case for staying in media entertainment, you know, kind of similar to that. And this is a good use case for S3 Glacier is if, if you have like sports footage from like the '60s, and then, you know, there's like some sort of breaking news event about some athlete that you want to be able to cut a shot for the six o'clock news, with S3 Glacier and expedited retrievals, you're able to kind of get like that, you know, that data back in a couple of minutes and that way you have the benefit of like very low cost archive storage, but being able to get the immediacy of having some of that data back when you need it. So, that's just some of the examples that we're seeing in terms of how customers are using archives. >> I love that example because, you know, the, the prevailing wisdom is the older, you know, data is the less valuable it is, but if you can pull a clip up of, you know, Babe Ruth at the right time, even though it's a little grainy, wow. That's huge value for the-- >> Yeah, I mean, we're, we're finding like lots of customers that, you know, they've retained this data, they haven't known why they're going to need it. They just sort of intrinsically know this data is really valuable and, you know, we might need it. And then as they, you know, they look for new opportunities and they're like, hey, you know, we're, we're going to remaster this and they they've gone through a lot of digital transformation. So we're seeing companies have, you know, decades of original material moving to the cloud where we're also seeing, you know, fairly new startups who are also just generating lots of archive data. So it's just, you know, one of the many use cases we see from our customers who love Glacier. >> Data hoarder's heaven, I love it. Okay, Joe, let's wrap up, give us your closing thoughts, how you see the future of this business, where you want to take, take your, your business for your customers. >> I think mostly we, we just really want to help customers optimize their storage and realize the potential of their data. So for a lot of customers that really just comes down to knowing that S3 Glacier is a great and trusted place for their data, and that they're able to kind of meet their compliance and regulatory needs, but for, you know, a lot of other customers, they're, they're looking to kind of transform their business and reinvent themselves as they move to the cloud, and I think we're just excited by a lot of emerging use cases, and, you know, being able to find that flexibility of having like very low cost storage, as well as being able to get access to that data and, hook it up into the other AWS services and really realize the potential of their data. >> 100%, I mean, we've seen it over the decades, cost drops and use cases explode. Thank you, Joe. Thanks so much for coming on The Cube. >> Thanks a lot, Dave, it's been great being here. >> All right keep it right there for more storage and data insights. You're watching AWS Storage Day on The Cube. (upbeat music)

(joyful music) >> According to storage guru, Fred Moore, 60 to 80% of all stored data is archival data, leading to the need for what he calls the infinite archive. And in this world, digital customers require inexpensive access to archive data that's protected, it's got to be available, durable, it's got to be able to scale and also has to support the governance and compliance edicts of the organizations. Welcome to this next session of the AWS Storage Day with theCUBE. I'm your host, Dave Vellante. We're going to dig into the topic of archiving and digitally preserving data and we're joined by Joe Fitzgerald, who's the general manager of Amazon S3 Glacier. Joe, welcome to the program. >> Hey, Dave. It's great to be here. Thanks for having me. >> Okay, I remember early last decade, AWS announced Glacier, it got a lot of buzz. And since then you've evolved your archival storage services, strategy and offerings. First question: why should customers archive their data in AWS? >> That's a great question. I think Amazon S3 Glacier is a great place for customers to archive data. And I think the preface that you gave, I think, covers a lot of the reasons why customers are looking to archive data on the cloud. We're finding a lot of customers have a lot of data. And if you think about it, most of the world's data is cold by nature. It's not data that you're accessing all the time. So if you don't have an archival story as part of your data strategy, I think you're missing out on a cost savings opportunity. So one of the reasons we're finding customers looking to move data to S3 Glacier is because of cost. With Glacier Deep Archive, we have an industry-leading price point of a dollar per terabyte per month. I think another reason that we're finding customers wanting to move data to the cloud, into Glacier, is because of the security, durability and availability that we offer. Instead of having to worry about some of the most valuable data that your company has and worrying about that being in a tape library that doesn't get access very often on premises or offsite in a data locker that you don't really have access to, and we offer the best story in terms of the durability and security and availability of that data. And I think the other reason that we're finding customers wanting to move data to S3 Glacier is just the flexibility and agility that having your data in the cloud offers. A lot of the data, you can put it in Deep Archive and have it sit there and not access it but then if you have some sort of event that you want to access that data, you can get that back very quickly, as well as put the power the rest of the AWS offerings, whether that's our compute offerings, our machine learning and analytics offerings. So you just have unmatched flexibility, cost, and durability of your data. So we're finding a lot of customers looking to optimize their business by moving their archive data to the cloud. >> So let's stick on the business case for a minute. You nailed the cost side of the equation. Clearly, you mentioned several of the benefits, but for those customers that may not be leaning in to archive data, how do they think about the cost-benefit analysis when you talk to customers, what are you hearing from them, the ones that have used your services to archive data, what are the benefits that they're getting? >> It's a great question. I think we find customers fall into a few different camps and use cases and one thing that we recommend as a starting point is if you have a lot of data and you're not really familiar with your access patterns, like what part of the data is warm, what part is cold? We offer a storage class called S3 intelligent tiering. And what that storage class does is it optimizes the placement of that data and the cost of that data based on the access patterns. So if it's data that is accessed very regularly, it'll sit in one of the warmer storage tiers. If it's accessed infrequently, it'll move down into the infrequent access tier or to the archive or deep archive access tiers. So it's a great way for customers who are struggling to think about archive, because it's not something that every customer thinks about everyday, to get automatic cost savings. And then for customers who have either larger amounts of data or better understand the access patterns, like some of the industries that we're seeing, like autonomous vehicles, they might generate tons of training data from running the autonomous vehicles. And they know, okay, this data, we're not actively using it, but it's also very valuable. They don't want to throw it away. They'll choose to move that data into an archive tier. So a lot of it comes down to the degree to which you're able to easily understand the access pattern of the data to figure out which storage class and which archive storage class maps best to your use case. >> I get it, so if you add that deep archive tier, you automagically get the benefit, thanks to the intelligent tiering. What about industry patterns? I mean, obviously, highly regulated industries have compliance issues and you have data intensive industries are going to potentially have this because they want to lower costs, but do you see any patterns emerging? I mean every industry needs this, but are there any industries that are getting more bang from the buck that you see? >> I would say every industry definitely has archived data. So we have customers in every vertical segment. I think some of the ones that we're definitely seeing more activity from would be media and entertainment customers are a great fit for archive. If you think about even digital native studios who are generating very high definition footage and they take all that footage, they produce the movie, but they have a lot of original data that they might reuse, that you remaster, director's cut, to use later, they're finding archive is a great fit for that. So they're able to use S3 Standard for their active production, but when they're done finishing a movie or production, they can save all that valuable original footage and move it in deep archive and just know that it's going to be there whenever they might need to use it. Another use case, we're staying in media, entertainment, similar to that and this is a good use case for S3 Glacier is if you have sports footage from like the '60s and then there's some sort of breaking news event about some athlete that you want to be able to cut a shot for the six o'clock news, with S3 Glacier and expedited retrievals, you're able to get that data back in a couple of minutes and that way you have the benefit of very low cost archive storage, but being able to get the immediacy of having some of that data back when you need it. So that's just some of the examples that we're seeing in terms of how customers are using archives. >> I love that example because the prevailing wisdom is the older data is, the less valuable it is, but if you can pull a clip up of Babe Ruth at the right time, even though it's a little grainy, wow, that's huge value for the-- >> We're finding like lots of customers that they've retained this data, they haven't known why they're going to need it, they just intrinsically know this data is really valuable, we might need it. And then as they look for new opportunities and they're like, hey, we're going to remaster this. And they've gone through a lot of digital transformation. So we're seeing companies have decades of original material moving into the cloud. We're also seeing fairly nascent startups who are also just generating lots of archive data. So it's just one of the many use cases we see from our customers love Glacier. >> Data hoarders heaven. I love it. Okay, Joe. Let's wrap up. Give us your closing thoughts, how you see the future of this business, where you want to take your business for your customers. >> Mostly, we just really want to help customers optimize their storage and realize the potential of their data. So for a lot of customers, that really just comes down to knowing that S3 glacier is a great and trusted place for their data, and that they're able to meet their compliance and regulatory needs, but for a lot of other customers, they're looking to transform their business and reinvent themselves as they move to the cloud. And I think we're just excited by a lot of emerging use cases and being able to find that flexibility of having very low cost storage, as well as being able to get access to that data and hook it up into the other AWS services and really realize the potential of their data. >> 100%, we've seen it over the decades, cost drops and use cases explode. Thank you, Joe. Thanks so much for coming on theCUBE. >> Thanks a lot, Dave. It's been great being here. >> All right, keep it right there for more storage and data insights. You're watching AWS Storage Day on theCUBE. (tranquil music)

>> Okay. We want to pick up on a couple of themes that Mick discussed, you know, supercharging your business with AI, for example, and this notion of getting hybrid right. So right now we're going to turn the program over to Rob Bearden, the CEO of Cloudera and Manuvir Das who's the head of enterprise computing at NVIDIA. And before I hand it off to Rob, I just want to say for those of you who follow me at the Cube, we've extensively covered the transformation of the semiconductor industry. We are entering an entirely new era of computing in the enterprise and it's being driven by the emergence of data intensive applications and workloads. No longer will conventional methods of processing data suffice to handle this work. Rather, we need new thinking around architectures and ecosystems. And one of the keys to success in this new era is collaboration between software companies like Cloudera and semiconductor designers like NVIDIA. So let's learn more about this collaboration and what it means to your data business. Rob, take it away. >> Thanks Mick and Dave. That was a great conversation on how speed and agility is everything in a hyper competitive hybrid world. You touched on AI as essential to a data first strategy in accelerating the path to value and hybrid environments. And I want to drill down on this aspect. Today, every business is facing accelerating change. Everything from face-to-face meetings to buying groceries has gone digital. As a result, businesses are generating more data than ever. There are more digital transactions to track and monitor now. Every engagement with coworkers, customers and partners is virtual. From website metrics to customer service records and even onsite sensors. Enterprises are accumulating tremendous amounts of data and unlocking insights from it is key to our enterprises success. And with data flooding every enterprise, what should the businesses do? At Cloudera, we believe this onslaught of data offers an opportunity to make better business decisions faster and we want to make that easier for everyone, whether it's fraud detection, demand forecasting, preventative maintenance, or customer churn. Whether the goal is to save money or produce income, every day that companies don't gain deep insight from their data is money they've lost. And the reason we're talking about speed and why speed is everything in a hybrid world and in a hyper competitive climate, is that the faster we get insights from all of our data, the faster we grow and the more competitive we are. So those faster insights are also combined with the scalability and cost benefit that cloud provides. And with security and edge to AI data intimacy, that's why the partnership between Cloudera and NVIDIA together means so much. And it starts with a shared vision, making data-driven decision-making a reality for every business. And our customers will now be able to leverage virtually unlimited quantities and varieties of data to power an order of magnitude faster decision-making. And together we turbo charged the enterprise data cloud to enable our customers to work faster and better, and to make integration of AI approaches a reality for companies of all sizes in the cloud. We're joined today by NVIDIA's Manduvir Das, and to talk more about how our technologies will deliver the speed companies need for innovation in our hyper competitive environment. Okay, Manuvir, thank you for joining us. Over to you now. >> Thank you Rob, for having me. It's a pleasure to be here on behalf of NVIDIA. We're so excited about this partnership with Cloudera. You know, when, when NVIDIA started many years ago, we started as a chip company focused on graphics. But as you know, over the last decade, we've really become a full stack, accelerated computing company where we've been using the power of GPU hardware and software to accelerate a variety of workloads, AI being a prime example. And when we think about Cloudera, and your company, your great company, there's three things we see Rob. The first one is that for the companies that were already transforming themselves by the use of data, Cloudera has been a trusted partner for them. The second thing we've seen is that when it comes to using your data, you want to use it in a variety of ways with a powerful platform, which of course you have built over time. And finally, as we've heard already, you believe in the power of hybrid, that data exists in different places and the compute needs to follow the data. Now, if you think about NVIDIA's mission going forward to democratize accelerated computing for all companies, our mission actually aligns very well with exactly those three things. Firstly, you know, we've really worked with a variety of companies to date who have been the early adopters using the power acceleration by changing their technology and their stacks. But more and more we see the opportunity of meeting customers where they are with tools that they're familiar with, with partners that they trust. And of course, Cloudera being a great example of that. The second part of NVIDIA's mission is we focused a lot in the beginning on deep learning where the power of GPU is really shown through. But as we've gone forward, we found that GPU's can accelerate a variety of different workloads from machine learning to inference. And so again, the power of your platform is very appealing. And finally, we know that AI is all about data, more and more data. We believe very strongly in the idea that customers put their data, where they need to put it. And the compute, the AI compute, the machine learning compute, needs to meet the customer where their data is. And so that matches really well with your philosophy, right? And, and Rob, that's why we were so excited to do this partnership with you. It's come to fruition. We have a great combined stack now for the customer and we already see people using it. I think the IRS is a fantastic example where, literally, they took the workflow they had, they took the servers they had, they added GPUs into those servers. They did not change anything. And they got an eight times performance improvement for their fraud detection workflows, right? And that's the kind of success we're looking forward to with all customers. So the team has actually put together a great video to show us what the IRS is doing with this technology. Let's take a look. >> How you doing? My name's Joe Ansaldi. I'm the branch chief of the technical branch in RAS. It's actually the research division, research and statistical division of the IRS. Basically, the mission that RAS has is we do statistical and research on all things related to taxes, compliance issues, fraud issues, you know, anything that you can think of basically, we do research on that. We're running into issues now that we have a lot of ideas to actually do data mining on our big troves of data, but we don't necessarily have the infrastructure or horsepower to do it. So our biggest challenge is definitely the, the infrastructure to support all the ideas that the subject matter experts are coming up with in terms of all the algorithms they would like to create. And the diving deeper within the algorithm space, the actual training of those algorithms, the number of parameters each of those algorithms have. So that's, that's really been our challenge now. The expectation was that with NVIDIA and Cloudera's help and with the cluster, we actually build out to test this on the actual fraud detection algorithm. Our expectation was we were definitely going to see some speed up in computational processing times. And just to give you context, the size of the data set that we were, the SME was actually working her algorithm against was around four terabytes. If I recall correctly, we had a 22 to 48 times speed up after we started tweaking the original algorithm. My expectations, quite honestly, in that sphere, in terms of the timeframe to get results, was it that you guys actually exceeded them. It was really, really quick. The definite now term, short term, what's next is going to be the subject matter expert is actually going to take our algorithm run with that. So that's definitely the now term thing we want to do. Going down, go looking forward, maybe out a couple of months, we're also looking at procuring some A-100 cards to actually test those out. As you guys can guess, our datasets are just getting bigger and bigger and bigger, and it demands to actually do something when we get more value added out of those data sets is just putting more and more demands on our infrastructure. So, you know, with the pilot, now we have an idea with the infrastructure, the infrastructure we need going forward and then also just our in terms of thinking of the algorithms and how we can approach these problems to actually code out solutions to them. Now we're kind of like the shackles are off and we can just run a, you know, run to our heart's desire, wherever our imaginations takes our SMEs to actually develop solutions. Now have the platforms to run them on. Just kind of to close out, we really would be remiss, I've worked with a lot of companies through the year and most of them been spectacular. And you guys are definitely in that category, the whole partnership, as I said, a little bit early, it was really, really well, very responsive. I would be remiss if I didn't thank you guys. So thank you for the opportunity. Doing fantastic. and I'd have to also, I want to thank my guys. my staff, Raul, David worked on this, Richie worked on this, Lex and Tony just, they did a fantastic job and I want to publicly thank them for all the work they did with you guys and Chev, obviously also is fantastic. So thank you everyone. >> Okay. That's a real great example of speed and action. Now let's get into some follow up questions guys, if I may, Rob, can you talk about the specific nature of the relationship between Cloudera and NVIDIA? Is it primarily go to market or are you doing engineering work? What's the story there? >> It's really both. It's both go to market and engineering The engineering focus is to optimize and take advantage of NVIDIA's platform to drive better price performance, lower cost, faster speeds, and better support for today's emerging data intensive applications. So it's really both. >> Great. Thank you. Manuvir, maybe you could talk a little bit more about why can't we just use existing general purpose platforms that are, that are running all this ERP and CRM and HCM and you know, all the, all the Microsoft apps that are out there. What, what do NVIDIA and Cloudera bring to the table that goes beyond the conventional systems that we've known for many years? >> Yeah. I think Dave, as we've talked about the asset that the customer has is really the data, right? And the same data can be utilized in many different ways. Some machine learning, some AI, some traditional data analytics. So, the first step here was really to take a general platform for data processing, Cloudera data platform, and integrate with that. Now NVIDIA has a software stack called rapids, which has all of the primitives that make different kinds of data processing go fast on GPU's. And so the integration here has really been taking rapids and integrating it into a Cloudera data platform so that regardless of the technique the customer is using to get insight from the data, the acceleration will apply in all cases. And that's why it was important to start with a platform like Cloudera rather than a specific application. >> So, I think this is really important because if you think about, you know, the software defined data center brought in, you know, some great efficiencies, but at the same time, a lot of the compute power is now going towards doing things like networking and storage and security offloads. So the good news, the reason this is important is because when you think about these data intensive workloads, we can now put more processing power to work for those, you know, AI intensive things. And so that's what I want to talk about a little bit, maybe a question for both of you, maybe Rob, you could start. You think about AI that's done today in the enterprise. A lot of it is modeling in the cloud, but when we look at a lot of the exciting use cases, bringing real-time systems together, transaction systems and analytics systems, and real-time AI inference, at least even at the edge, huge potential for business value. In a consumer, you're seeing a lot of applications with AI biometrics and voice recognition and autonomous vehicles and the liking. So you're putting AI into these data intensive apps within the enterprise. The potential there is enormous. So what can we learn from sort of where we've come from, maybe these consumer examples and Rob, how are you thinking about enterprise AI in the coming years? >> Yeah, you're right. The opportunity is huge here, but you know, 90% of the cost of AI applications is the inference. And it's been a blocker in terms of adoption because it's just been too expensive and difficult from a performance standpoint. And new platforms like these being developed by Cloudera and NVIDIA will dramatically lower the cost of enabling this type of workload to be done. And what we're going to see the most improvements will be in the speed and accuracy for existing enterprise AI apps like fraud detection, recommendation engine, supply chain management, drug province. And increasingly the consumer led technologies will be bleeding into the enterprise in the form of autonomous factory operations. An example of that would be robots. That AR, VR and manufacturing so driving better quality. The power grid management, automated retail, IOT, you know, the intelligent call centers, all of these will be powered by AI, but really the list of potential use cases now are going to be virtually endless. >> I mean, Manufir, this is like your wheelhouse. Maybe you could add something to that. >> Yeah. I mean, I agree with Rob. I mean he listed some really good use cases, you know, The way we see this at NVIDIA, this journey is in three phases or three steps, right? The first phase was for the early adopters. You know, the builders who assembled use cases, particular use cases like a chat bot from the ground up with the hardware and the software. Almost like going to your local hardware store and buying piece parts and constructing a table yourself right now. Now, I think we are in the first phase of the democratization. For example, the work we do with Cloudera, which is for a broader base of customers, still building for a particular use case, but starting from a much higher baseline. So think about, for example, going to Ikea now and buying a table in a box, right. And you still come home and assemble it, but all the parts are there, the instructions are there, there's a recipe you just follow and it's easy to do, right? So that's sort of the phase we're in now. And then going forward, the opportunity we really look forward to for the democratization, you talked about applications like CRM, et cetera. I think the next wave of democratization is when customers just adopt and deploy the next version of an application they already have. And what's happening is that under the covers, the application is infused by AI and it's become more intelligent because of AI and the customer just thinks they went to the store and bought a table and it showed up and somebody placed it in the right spot. Right? And they didn't really have to learn how to do AI. So these are the phases. And I think we're very excited to be going there. >> You know, Rob, the great thing about, for your customers is they don't have to build out the AI. They can, they can buy it. And just in thinking about this, it seems like there are a lot of really great and even sometimes narrow use cases. So I want to ask you, you know, staying with AI for a minute, one of the frustrations, and Mick I talked about this, the GIGO problem that we've all, you know, studied in college, you know, garbage in, garbage out. But, but the frustrations that users have had is really getting fast access to quality data that they can use to drive business results. So do you see, and how do you see AI maybe changing the game in that regard, Rob, over the next several years? >> So yeah, the combination of massive amounts of data that had been gathered across the enterprise in the past 10 years with an open APIs are dramatically lowering the processing costs that perform at much greater speed and efficiency. And that's allowing us as an industry to democratize the data access while at the same time delivering the federated governance and security models. And hybrid technologies are playing a key role in making this a reality and enabling data access to be quote, hybridized, meaning access and treated in a substantially similar way, irrespective of the physical location of where that data actually resides. >> And that's great. That is really the value layer that you guys are building out on top of all this great infrastructure that the hyperscalers have have given us. You know, a hundred billion dollars a year that you can build value on top of, for your customers. Last question, and maybe Rob, you could, you could go first and then Manuvir, you could bring us home. Where do you guys want to see the relationship go between Cloudera and NVIDIA? In other words, how should we as outside observers be, be thinking about and measuring your project, specifically in the industry's progress generally? >> Yes. I think we're very aligned on this and for Cloudera, it's all about helping companies move forward, leverage every bit of their data and all the places that it may be hosted and partnering with our customers, working closely with our technology ecosystem of partners, means innovation in every industry and that's inspiring for us. And that's what keeps us moving forward. >> Yeah and I agree with Rob and for us at NVIDIA, you know, we, this partnership started with data analytics. As you know, Spark is a very powerful technology for data analytics. People who use Spark rely on Cloudera for that. And the first thing we did together was to really accelerate Spark in a seamless manner. But we're accelerating machine learning. We're accelerating artificial intelligence together. And I think for NVIDIA it's about democratization. We've seen what machine learning and AI have done for the early adopters and help them make their businesses, their products, their customer experience better. And we'd like every company to have the same opportunity.

(upbeat music) >> Hello and welcome back to theCUBES coverage of Red Hat summit 21 virtual. I'm John Furry, host of theCUBE. We've two great guests here, returning back CUBE alumni here to give us their perspective. Dave Linquist GM VP of engineering hybrid cloud management at Red Hat. Joe Fitzgerald, general manager VP of the management business unit Red Hat. Guys, welcome back to theCUBE. Congratulations, Red Hat summits, ongoing virtual. Great to see you. >> Thank you, John. >> Thanks John. >> So I'd love to get the low down. A lot going on the productivity this year. Looking back from last year, a lot's been done and we've been in the pandemic now, now circling back a full year. A lot's happened- a lot of productivity, a lot of clear visibility on, on what's working, what's not, you guys got some great news. Let's just jump right into it. What's the big announcement? >> So one of the things that we announced here at Summit, John, is an expansion of our Red Hat insights brand. Basically we announced Red Hat insights for our RHEL platform back in 2015. Over the years, we've increased the amount of data and visibility into those systems. Here at summit, we've now announced Red Hat insights for both OpenShift, and for the Red Hat Ansible platform. So it's a pretty significant increase in the visibility that we have to the platforms. >> Oh, so can you repeat that one more time? So the expansion is through which platform style specifically? >> So Red Hat insights is a way that we connect up to different platforms that Red Hat provides. Historically it was for Red Hat enterprise Linux realm. We've now expanded it to the Red Hat, OpenShift family, the platforms as well as the Red Hat Ansible automation platform as well. >> So a nice broad expansion and people want that data. What's what was the motivation behind it? Was it customer demand? Was it more access to the data? Just, was it on the roadmap? What's the motivation- where where's this going? What's what's the purpose of all this? >> Well, I don't think customers say, Hey, please, you know take more data. I think it's customers say, can you keep me more secure? Can you keep my systems more optimized? Can you help me set more things to automatic? And that requires that you get data from these systems that you can auto tune on, auto- secure, auto optimize. Right? So it's really all those benefits that we get by connecting to these systems, bringing the telemetry data that config different kinds of information, and using that on customer behalf to optimize secure to the systems. >> You know, one of the biggest trends I think now for multiple years has been observability with cloud native, more services are being turned on and off enterprises are are getting a lot of pressure to be modern in their in their application development processes. Why is data more important than ever now? Can you guys take a minute to expand on that? Because this idea of telemetry across the platform is a very interesting announcement because you're turning that data into value, but can you guys expand where's that value coming, turning into? What is the value proposition? Where are people seeing the, the, the key key value points? >> Well, a couple of points, John, as you started out is in a hybrid cloud environment with cloud native applications and a lot of application modernization and the current progressiveness of DevOps and SRE teams, you're seeing a lot of dynamics and workloads and continuous delivery and deployments that are in public environments and private environments, distributed models. And so consequently, there's a lot of change in dynamics in the environment. So to sustain these high levels of service levels to sustain the security and the compliance, the ability to gather data from all these different points, to be able to get visibility into that data. It'd be able the ability to process that with various analytics and understand what when something's gone wrong or when an update is needed or when a configuration has drifted is increasingly critical in that in a hybrid cloud environment. >> So on the telemetry piece is that in open shift as well that that's supporting that as in there has that work. >> It's it's in OpenShift, as Joe mentioned, it's in braille it's in V2 Ansible and the OpenShift space we'd have an offering advanced cluster management that understands fleets of deployments, clusters, wherever they're deployed however they're running infrastructure public private hybrid environments. And it also collects in the context of the workloads that are deployed on those on those clusters to multi-question burn. >> I want to ask you guys a question. I get this all the time on theCUBE. Hey, you know, I need more data. I have multiple systems. I need to pull that data into one kind of control plane but I'm being pushed more and more to keep scaling operations. And this becomes a huge question mark for the enterprises because they, they have to turn up more, more scale. So this is becomes a data problem. Does this solve it here? How do you guys answer that? And what was the, what would be your response to that trend? >> Well, I think the, the thirst for data, right? There's a lot of things you can do with more data. There is a point where you can't ship all the data everywhere, right? If you think about logs and metrics and all the data it's too heavyweight to move everything everywhere. Right? So part of it is, you know, selecting the kind of data that you're going to get from these systems and the purpose you're going to use it for. And in the case of Red Hat, we take data from these different systems, regardless of whether they're deployed bring it in, and then we did predictive analytics against that data. And we use that telemetry that can take that health data right to do everything from optimize for performance or security costs, things like that. But we're not moving, you know, huge quantities of data from every system to Red Hat in order to, you know, pour through it. We are very selectively moving certain kinds of data for very specific purposes. >> Dave, what's your take on that because you know you got to engineer these systems. What's the optimized path for data? Do you keep it in the silo? Do you bring it together? What's the customer's view on, on how to deal with the data? >> Yeah. It is a complex problem. No doubt. You don't want it to be pulling all the data and trying to transmit all that data back into your analytics system. So you ended up curating some data, some of it you afford on often it's done under it will be done under control of policies. So that data that is sensitive, that should stay within the environment that it's in, will stay, but curated or alerts or information that's particularly relevant say to configurations, updates, any any of that type of information will go up into the analytics, into the insights. And then in turn, the alerts will come back down in a manner that are presented to the user. So they understand what actions need to be taken place whether there's automated actions or or they have to get approvals to maybe make an update to a certain environment. >> All right, you got telemetry, data power, the the advanced cluster management ACM. What's the overlap of the visibility and automation here. Can you guys talk about that? >> Well, let's say it's a great question, John what we'd like to do is we'd like to sort of separate the different areas. There's the seeing, right. And what's going on in these environment. Right. So getting the data analyzing it and determining what needs to be done. And then the, you know the recommendation of the automation. As Dave said, in a lot of environments, there's a process of either approvals or checkpoints or, you know evaluation of the changes being made to the system. Right. So separating the data and the analysis from the what do you want to do at this and making that configurable I think is really powerful. >> Yeah. I mean, that's, I mean I think that's the number one thing is like, you know everyone always asks, what do you optimize for do you optimize for the automation or the visibility? And I think, you know, there's always a trade-off and that's always interesting question David- love to get your thoughts. If someone asks you, Hey, I'm a I'm I have a team of people. What do I optimize for? The visibility or the automation or both? Is or is there a rule of thumb or is there a playbook? What w how would you answer that question? >> Well, there's a couple of things. I first, I think the, the ability to pull the data together to get visibility across the environment is critical. And then what becomes often complex is how the different disciplines, how the different parts of the system are able to work together on common understanding of the resources common understanding the applications. That's usually where systems start falling down. And so it's too siloed. So one of the key things we have with with our systems, particularly with OpenShift and row and with ACM and Ansible is the ability to have the common back lane and the ability to have a common understanding of the resources and the applications. And then you can start integrating the data around that common, those common data models and take appropriate actions on that. So that's how you ended up getting the visibility integrated with the automation. >> When you think about this, Joe about the security aspect of it and the edge of the network which has been a big theme this year and going into next year, a lot more discussion just the industrial edge, you know, that's important. You got to take all this into account. How do you, how would you talk about folks who are thinking about embedding security and thinking about now the distributed edge specifically? >> Right. So we thought it was complicated before, right? It goes up a notch here, right? As you have, you know, more and more edge applications I think at the edge, you're going to want automated policies and automated configurations in force so that when a device connects up to a network or is, you know analyzed that there's a set of policies and some configurations and versions that need to be applied to that device, these devices, aren't always connected. There's not always high bandwidth. So you basically want a high degree of automation in that case. And to get back to your early point there are certain things you can set like policies about security or configuration. You say, I always want it to be like this and make it so and there's other things where they're more you know, complicated, right. To, to address or have regulatory requirements or oversight issues. And those things you want to tell somebody I think this should be done. Is this the right thing to do? Is it okay? Do it, but at the edge you're going to have a lot more sort of lights out automation to keep these things secure, to configure. Right. >> It's funny. I was, some of the Ansible guys are talking about, you know code for code, changing code all the time and dynamic nature of some of the emerging tech coming out of the Red Hat teams. It's pretty interesting. You guys have going on there, but you know, you can bring it down to the average enterprise and main street, you know enterprise out there, you know, they're looking at, okay I got some public loud. Now I got hybrid. I'm going a hundred percent hybrid. That's pretty much the general consensus of all the enterprises. Okay. So now you say, okay, if I understand this correctly you got insights on REL, OpenShift and Ansible platform. So I'm, am I set up for an open hybrid cloud? That's the question I want to ask you guys does that give me the foundation to allow me to start the cloud adoption with an, a true distributed open way >> I'll I'll offer to go first. I think there's a couple of things you need in order to run across hybrid clouds. And I think Red Hat from a platform point of view the fact that Red Hat platforms run across all those different environments from the public cloud to on-premise and physical vert to edge devices. Now you have consistency of those platforms whether it's your traditional on REL, your container based workloads on shift or automation that's being turned in by Ansible. Those are consistent across all these different hybrid cloud environments. So reduces the complexity by standardizing those platforms across any and all of those different substrates. Then, when you can take the data from those systems bring them centrally and use it to manage those things to a higher degree of automation. Now you take an, another sort of chunk of complexity out of the problem, right? Consistency of getting data from all those different systems being able to set policies and enforce things across all those distributed environments is huge. >> Yeah. And then, you know, it fills in the gaps when you start thinking about the siloed teams, you know, the, the, I think one of the messages that I've been hearing out of Red Hat Summit in the industry that's consistent is the unification trend that's going on. Unifying development teams in a way that creates more of an exponential value curve rather than just linear progressions in, in traditional IT. Are you guys seeing that as well? I mean, what's your take on this? That's that piece of the story? >> Well, I think the shift that we've seen for the last few years actually quite a few years with DevOps and SRE is started to bring a lot of the disciplines together that you mentioned that are traditionally silos. And you're finding the effectiveness of that is really around many of the areas that we've been discussing here which is open platforms that can run consistently across a hybrid environment, the ability to get data and visibility out of this platform. So you can see across the distributed environment across the hybrid environment and then the ability to take actions in Bourse or update environments through automation is, is is really what's critical to bring things to to bring it all together. >> Yeah. I think that's such an important point, Joe. You know, I was talking with Chris right around and we we've covered this in the past red hats success with academics in the young people coming into in the universities with computer science. It's not just computer science anymore. Now you have engineering degrees kind of cross-disciplinary with SRS is SRE movement because you're looking at cloud operations at scale. That's not an IT problem anymore. It's actually an IT next gen problem. And this is kind of what, there's no real degree. There's no real credential for, you know large scale hybrid cloud environment. You guys have the mass open cloud initiative. I saw that going on. That's some really pretty big things. This is a, a change and, and talent. What's your, what's your view on this? Because I think people want to learn what what do I need to be in the future? What position? >> So John it's a great question. I think Ansible actually addresses a number of the issues you brought up, which is, you know historically there've been different tools for each of the different groups. So, you know, developers had their favorite set of tools and different, IT areas their favorite set of tools and technologies. And it was sort of like a tower of Babel. People did not share the same, you know sort of languages and tools. Ansible crosses both your your development test and operational teams. So creates a common language, now that can be used across different teams. It's easy to understand. So it sort of democratizes automation. You don't have to be deeply skilled in some, you know misspoke language or technology in order to be able to do some level of automation. So I think sort of sharing the same technology and tools I'd like an answer, more democratizing it so that more people can get involved in automating sharing that automation across teams and unifying those worlds is huge, right? So I think that's a game changer as well in terms of getting these teams work holistically integrated. >> Yeah. And there's also a better together panel on the Ansible and advanced cluster management session. Folks watching should check it out on on the virtual event platform on that point while I got you here on that point, let's let's talk about the portfolio updates for advanced cluster management for Kubernetes, what's new since the Ansible Fest, Ansible Fest announcements >> There's quite a bit that's been new since Ansible Fest. Ansible Fest well actually going back to Summit last year we introduced advanced cluster management. For years, we've been seeing the growth of Kubernetes with cloud native and clusters. And what ACM really allows enterprises to do is is scale out their deployments of OpenShift. Well, one of the things we found is that as you're deploying workloads or clusters or trying to take care of the compliance, the importance of integrating that environment with the breadth of capabilities that Ansible has in automation. So that's what we announced that at Ansible Fest following last year's summit what we've done is put a lot more focus on that integration with Ansible. So when you bring up, provision a cluster maybe you need to make some storage or security configurations on behalf of that cluster or if you're taking care of the compliance how do you remediate any issues with Ansible or one of the things that get shown a lot, demonstrate a lot with customers like is when you're deploying applications into production, how do you configure the network? Do the network configurations like a load balancer maybe a ticket into your service management system along with say a threat detection on your security. So a lot of advances with ACM and the integration with a broader ecosystem of IT, in particular with, with Ansible >> What's the ecosystem update for partners? And this has comes up all the time. I want to make sure I get this in there. I want it, I missed it. Last time we chatted, you know, the partner impact to this. You mentioned the ecosystem and you've got native Coobernetti's, non-native what's native to open. You guys have a lot of native things and sometimes it's just support for other clouds. So you start to get into the integration questions. Partners are very interested in what you guys are doing. Can you share the partner update on how they play and what impacts them the most here? >> Yeah. On the events, cluster management ACM front first with this integration with Ansible that actually allows us to integrate with the wealth of partner ecosystem the Ansible apps, which is huge. So that's, that's one, one space. And then the way ACM works, this policy desirous state model is we've been able to integrate with a large number of partners around particularly the security space model the service management space, where they, where we can enforce the use of certain security tools on the on the clusters themselves. So it's really opened up how quickly partner offerings can be integrated into the OpenShift environment at scale across all the clusters that you want, that you need to support it on what the appropriate configurations and policies >> I got to ask you on the insight side you mentioned the expansion across the platform. Now, if you go out and take out to the ecosystem, you know there's guard rails around governance how far can partners push their data in terms of sharing? That's something that might come up when you comment on that. >> Sure. So Red Hat, you know, takes, you know our customer data very seriously. We're a trusted partner to our customers. So the data that we get from systems we make sure that we are following all of the governance and oversight necessary to protect that data. So far, we have basically been collecting that data and using that data at Red Hat. Our plan really is to allow partners with the right degree of governance and control to be able to use some of that data in the future, under the right conditions whether it's anonymized or aggregated, things like that to be able to take that data and to add value to customers if they can enrich customers or or help customers by getting some access to that data without every vendor or partner, having to go out to systems and having to connect and pull data back. That's a pretty tough situation for customers to live with. But I think that fact that we're ahead is trusted. We've been doing this for awhile. We know how to handle the data. We know how to provide the governance. But our plan really is to enable partners to use that data ecosystem. I will say that initially what they had said about ACM and partners, Ansible has been working with partners on the automation side at a very large scale, right? So if you look at the amount of partners that are doing automation, work with us we have some pretty strong, you know, depth there. But in terms of working with partners, our plan is to take the data ecosystem, expand that as well. >> It's really a nice mix between the Ansible OpenShift and then REL, do you guys have great insights across now? I think the open innovation just continues to be every year. I say the same thing. It's almost like a broken record but every year it just gets better and better. You know, innovation out in the open you guys doing a great job and continuing and now certainly as the pandemic looks like it's coming to an end soon, post-pandemic, a lot more projects are being worked on a lot more productivity, as we said at the top. So to end the segment out I'd love to get you guys to weigh in on what happens next. As we come out of the pandemic, the table has been set. The foundation's there, cloud native is continuing to accelerate rapidly in the open OpenSource, going through them on another level. What's next what's, what's going to what's next for customers. Are they going to continue to double down on those? The winds they're going to shut down certain projects. What happens after this pandemic? How do people grow, Dave? We'll start with you. >> Well, I think, yes we all see the light at the end of the tunnel, John. It's great. And I think if a positive, is it really throughout this? We've been accelerated in the digitization and at modernization cross the board across industries. Okay. And that is really teaching all of us a lot about the importance of how do you start managing and running this at scale and securing this at scale. So I think what we'll see coming out of this is just that much more effort, open ecosystems. How you really bring together data across insights? How do you bring in increasing the amount of analytics AI to now do something turn that data into information that you can respond with and that in turn, close it, closing the loop with automation against or against your hybrid cloud environment? We're just going to see acceleration of that occurring. >> Awesome, great insights there. Open data insights, automation, all kind of coming together. AI. You don't have AI in your, your plans. Someone was Wall Street was joking. That's going to be the future stable stakes get listed on Wall Street. You got to have some sort of AI piece. They have great insight, Joe, your take on what's next? What, what what's going to what's going to happen as we come out of the pandemic? >> Yeah. We've definitely seen people, you know advance their digital transformation. And I don't think it's going to stop. Right? So the speed scale and complexity or just put more pressure on teams, right? To be able to support these environments that are evolving at light speed. So I think Red Hat is really well positioned and is a great partner for folks who are trying to get more digital, faster trying to leverage these technologies from the hybrid cloud to the edge. They're going to need lots of help. Red Hat is in a great position. >> Okay. >> You guys doing great work, Dave Linquist, Joe Fitzgerald. Great to have you back on again. Open, always wins. And as end users become much more participants in the open source ecosystem and user contributions and user interactions software at scale, it's now a new come next generation commercial environment, You guys are doing a great job. Thank you for sharing. Appreciate it. >> Thank you John. >> Thanks John. >> Okay. Red Hat Summit 21 CUBE coverage. I'm John Furrier getting all the action from the experts who've been there, done that living through it, being more productive and have bringing benefits to you being open source. Thanks for watching.

>>from around the globe. It's the >>Cube with digital >>coverage of AWS reinvent 2020 sponsored by Intel, >>AWS and >>our community partners. >>Welcome back to the cubes ongoing coverage of this year's AWS reinvent. You know, normally we'd be in the middle of the San Sands Convention Center. We have two sets and 50,000 of our closest friends. We'd be deking out on cloud. Seems like a long time ago, but the show must go on. And it does. Joe Duffy is here. He's the co founder and CEO of Gloomy, and Justin Fits you is the vice president engineering for Cloud Engineering for snowflake. Welcome, gentlemen. Good to see you. >>It's good to be here, >>Joe. I love what you guys are doing. You know, leading your customers to the cloud and really attacking that I t labor problem that we've dealt with for years and years by playing a role in transforming what I would say is I t ops into cloud ups with programmable infra infrastructure practices. So take >>a >>moment to tell us. Why did you and your co founder start the company how you got it off the ground? People are always interested in how you got it funded. You got a couple of Seattle VCs, Madrona and Tola involved. Any a just got involved. So congrats on that. What's the story of your company? >>Yeah. So my background and my co founder Eric's background. You know, we spent multiple decades at Microsoft just really obsessing over developer platforms and productivity and trying to make you know developers lives as as as as productive as possible. You know, help them harness the power of software >>toe create, >>you know, innovative new applications and really spent time on technologies like Visual Studio and Ahmed. And and, you know, it really struck us that the cloud is changing everything about how we develop software. And yet from our perspective, coming from developer landed had almost changed nothing. You know, most of our customers were still, you know, developing software like they did 15 years ago, where it was a typical enter your application, they'd kind of write the code and then go to their I t team and say, Hey, we need to run this somewhere. Can you provisioned a few virtual machines? Can you prevision You know, maybe a database or two and and And so And then we went and talked Thio, you know, infrastructure teams and found out Hey, you know, folks were really toiling away with tools that air a pale in comparison when it comes to the productivity that we we were accustomed Thio on the developer side. And then frequently we heard from leaders that there were silos between the organizations. They couldn't build things quickly enough. They couldn't move quickly enough in cloud Native and the new public cloud capabilities just really were pushed pushing on that, really, you know. But the most innovative companies we kept hearing were the ones who figured this out, who really figured out how to move faster in the cloud. Companies like Snowflake really are leveraging the cloud toe transform entire businesses. You look at uber lyft Airbnb, these companies that really harnessed the cloud toe not just from a technical productivity standpoint, but really transform the business. Eh? So that was the opportunity that we saw Kalemie was Let's take a step back. We call this cloud engineering. Let's imagine a world where every developers, a cloud developer and infrastructure teams are enabling that new way of building. >>Great. So you mentioned cloud engineering. Now, Justin, you've done a bit a bit of cloud engineering yourself in your day. You know, the Cube has been following Snowflake very closely since it launched really mid last decade. And we've we've covered your novel, architectural approach and your cloud only mantra. Talk about that. And have there been any changes in how you're thinking about cloud adoption and how that's as that's increased and you've seen new use cases emerged. >>Yeah, so I think, you know, obviously Snowflake was was built on the foundation of cloud first, and in fact, cloud Onley are only platform and only infrastructure is is based on the cloud. But, you know, for us, it was absolutely key on. How do you develop a platform and a product that's completely elastic? Lee, scalable on drily, really allows for kind of the paper use and paper consumption model. We didn't really it would be very difficult for us to offer this and Thio offer a product in this way. On def, you start to think about kind of from a cloud engineering perspective. Um, we don't have the typical network engineers. A typical data center engineers that you that you might have seen previously. Instead, we're shifting our model in our what we do include engineering away from kind of an operations model or even devotes model towards the software engineering model. E. I think that's the That's the big shift to cloud engineering is that we're looking to hire and we're building a team of software engineers to build systems and platforms and and tooling Thio have the system self managed as much as possible, and it changes to our infrastructure that we look at any changes in our platform are all through, commits and and deployed via pipelines, as opposed to having Operator's log on and make these changes. And so that's the shift that I think we're seeing. And that's to kind of match the overall stuff like Model of Cloud, first and on and where the product is like just going. >>Like you said in cloud only, Justin, you use Pollux me in your own engineering and also in your product externally. Is that correct? And how so? >>Yeah, we actually use it in, specifically and, um, in our platform, in order to kind of deployed to manage and, uh, just operate a kind of our overall cloud infrastructure. We specifically use it more focused on the good days and and continue ization side of things. But that use cases kind of rapidly expanding across the organization. >>So I'm curious of what do you guys we're seeing in the market place? Joe, you know, thinking about cloud broadly, What's the impact that you're seeing on businesses? Who are the big players that you see out there? Maybe you could talk about some of the differentiation that you've noticed. >>Yeah, I think this notion of plot engineering, you know, even 3.5 years ago when we got started was in its infancy. You know, we definitely saw that. Hey, you know, the world is moving and shifting left, you know, it's just was saying and really, people are looking for new ways to empower developers, but that empowerment has to come with guard rails, right? And so what we're seeing is oftentimes, teams are now modernizing their entire platform infrastructure platform, and they're looking to technologies like kubernetes to do that. But increasingly, you know, aws, Azure gp. You know, when we started, um, there weren't any great managed kubernetes clusters. And now today, fast forward. You know Onley 3.5 years and and many of our customers are using flew me to help them get up and running with the chaos in AWS, for example, you look at a lot of folks transforming on Prem as well again many times, adopting kubernetes is sort of a if they intend to stay on Prem. You know, Thio, at least modernize their approach to application infrastructure delivery. That's where Pollux me really can help. It could be a bridge. Thio hate from on Prem to the public cloud. There's certainly a lot of folks doing great work in the space, you know, I think VM Ware has really kind of emerged as sort of vanguard thought leader in this in this space, especially with, you know, hep dio and now kind of pivotal joining the story. We see other, you know, great companies like hash in court, for we're doing good work in this space. Um, certainly we integrate with a lot of their technologies on you. Combine those with the public cloud providers. There's also a lot of just smaller startups in the space which you know, strikes in my heart. I love I love supporting the startup ecosystem. You know, whether that's for cell or net lif I or server list. You know, really trying to help developers harness more of the cloud. I think that's an emerging trend that we're gonna see accelerating in the coming years. >>Yeah. Thank you. You've mentioned a number of interesting emerging tools companies in the ecosystem. I mean, Justin talked about kubernetes. Are there other tooling that you're using that that might be, you know, some of your customers might like toe to know about. >>Yeah, I think so. So one thing I wanted to actually follow up with what Joe said here is is around kind of the multi cloud nature of what we do is is the tools, like gloomy are critical for us to be able to abstract away specific cloud provider AP ice and such and so given Snowflake operates on all three major public clouds and offers a seamless experience amongst all three of them. We have to have something that abstracts some of that complexity and some of those technical details away. Andi, that's why I kind of blew me, made sense in in this case and has helped us kind of achieved that cloud neutrality piece. Um, in terms of other tools that that you're thinking that we're talking about, I think Bellamy is doing a great job kind of on some of these on some of the kind of that interaction and infrastructure and sensation. But we're looking for tooling to kind of look for the overall workflow automation piece on orchestration. So what sits on top of say, you're using intervals using terra form? You may be using Polonia's well, but what kind of orchestrates all these pieces together? Onda, How do you kind of build workflow automation? And I think there's a lot of companies and technology providers that air starting up in this area to kind of stitch all these pieces together so that you kind of have a seamless kind of work flow across across your infrastructure. >>Got it. So, Joe, I'm kind of curious you talked a little bit about your background at Microsoft, and you're even a TMC where you're helping, you know, people manage Luns. It was a sort of skill set that is not in high demand today. Early. Shouldn't be people really need to transform? I've said that a lot in the queue, but But, you know, maybe talk a little bit about the experiences that you've had in the past that informed the direction that Pollux me is taking and where you see it going specifically. I mean, I've been talking a lot about the next decade of cloud is not gonna be the same as the last decade of the cloud. How did you How do you see it? >>Yeah, I think I recognize a clear trend, you know, in with cloud computing. Uh, you know, back I can't remember 13 years ago, maybe 15 years ago, When, when When the Azure project started. You know Dave Cutler, who actually founded the anti project at Microsoft, Actually, was was one of the first engineers that started Azure. And he called it a cloud operating system. And, you know, I think that vision of hey, the cloud is the new operating system is something that we're still just chipping away at. And that was that was a clear trend, you know, having seen these transformations in the past, you know the shift from, you know, dos to windows from windows to mobile Thio, client server thio now the cloud every step of the way. We always transform the way we build applications. And I think where we're at now is horse, really in the midst of a transition that I think we'll look back. You never know when it's happening right? But you can always look back in hindsight and see that it did happen. And I think the trend that we're going through now with service meshes and just, you know, micro services and service list is really we're building distributed applications. These clouds made of applications, they're distributed applications. And that was the trend that I, I recognized, also recognizes another trend, which is, you know, we spent 30 years building great tools. You know, I d s test frameworks sharing and reuse package managers. We figured out static analysis and how to fix security problems in this in in programming languages that we've got today. Let's not go rebuild all that. Let's leverage that, and and so that's what Eric and I said they want, you know, Let's stand on the shoulders of giants. Let's leverage all this good work that has come before us. Let's just apply that to the infrastructure domain and really try toe smooth things out. Give us a new sort of level playing field to build on. From here is we go forward and I'm excited that Parliament gives us that foundation that we can now build on top of >>Great and Justin, of course, were covered. Aws reinvent you guys. It was kind of your your first platform. It's your largest, the largest component of your business. And I have been saying, Ah lot that, you know the early days of cloud was about infrastructure last 32 throw in some database. But really, there's a new workload that's emerging. And you guys are at the heart of that where people are putting governed data giving access to that data, making it secure, uh, sharing that data across an ecosystem so that new workload is really driving new innovation. I wonder how you see that what you see the next half a decade or decades looking like in terms of innovation? >>Yeah, I think I think it za valid point, which is, um, it's less about infrastructure and more about the services that you're providing with that infrastructure. And what what value are you able to add and So I think that's it, Snowflake. The thing that we're really focused on, which is abstract away, all these tunes and all these knobs and such, and the how much remember you have on a specific and a piece of infrastructure or describes or anything like that. So what's the business value? And how can we present that business value in a uniform way, regardless of kind of the underlying service provider on baby to a different class of business users, someone who wants a low data and just two analysts against that they really don't want to understand what's happening underneath. And I think that's that's where this club engineering piece comes in. Um, and what my team is doing is really focused on How do we abstract away that kind of lower level infrastructure and scalability pieces and allow the application developers to develop this application that is providing business value in a transparent and seamless way and in elastic way such that we can scale up and down we can. We have the ability, obviously, to replicate both within regions and clouds, but also across different clouds. So from a business resiliency and and up time point of view. That's that's something that's been really important. Um, and I think also how do we security is? Becoming is obviously a huge, huge importance, given the classifications type of day that people are putting within our platform. So how are we able Thio ensure that there is a pipeline where developers have reviews and commits of any kind of changes going into the system and their arm's length away, and could be fully audited for various clients and regular regulatory needs? And that's something that kind of this suffer engineering cloud engineering concept has really helped develop and allowed us Thio obviously be successful with various different types of industries. >>Joe, we're almost out of time. I wonder if you could bring us home. I mean, some of the things Justin was talking about I mean, I definitely see a lot of potential disruption coming from the world of developers. Uh, he was talking. He was talking about consumption models different than many of the SAS pricing models. And how do you How do you see it? Developers air kind of the really the new source of innovation. Your final thoughts. >>Yeah. I think we're democratizing access to the cloud for everybody. I think you know it's not just about developers, but it's It's really all engineers of all backgrounds, its developers, its infrastructure engineers, its operations engineers, its security engineers. You know, Justin's mentioning compliance and security. These air really critical elements of how we deliver software into the cloud. So I think you know what you're going to see is you're gonna see a lot of new, compelling experiences built thanks to cloud capabilities. You know, the fact that you've got a I and M l and all these infinitely scalable data services like snowflake and, you know, just an arm's length away that you can use as building blocks in your applications. You know, application developers love that. You know, if we can just empower them to run fast, they will run fast, and we'll build great applications. And infrastructure teams and security engineers will be central to enabling that that new future. I think you also see that you know infrastructure and cloud services will become accessible to an entirely new audience. You know, kids graduating from college, they understand Java script. They understand python now they can really just harness the cloud to build amazing new experiences. So I think we're still, you know, still early days on the transition to the cloud. I know where many years on the journey, but we've got many, many years, you know, in our future. And it's very exciting. >>Well, thank you, guys, Joe and Justin. I really appreciate it. Congratulations on your respective success. I know is Joe said you got a lot more work to do, but I really appreciate you coming on the Cube. >>Awesome. Thank you. You're >>welcome. All right, so we're here covering reinvent 2020. The virtual edition. Keep it right there for more great content. Were unpacking the cloud and looking to the future. You're watching the cube?

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

>> Voiceover: From around the globe, it's theCUBE with digital coverage of Dell Technologies World Digital Experience brought to you by Dell Technologies. >> Welcome to theCUBE's coverage of Dell Technologies World 2020, the Digital Experience this year. I'm Lisa Martin, pleased to be joined by two CUBE alumni from Dell EMC. Please welcome Joe Caradonna, the VP of Cloud Storage CTO. Joe, good to see you again, even though quite socially distant. >> Yeah, thank you, it's great to be here. >> And Devon Reed is also joining us, the Senior Director of Product Management. Devon, how are you? >> I'm good, how are you doing? >> Good. >> Nice to be here, thank you. >> Nice to be chatting with you guys, although very, very socially distant, following rules. It wouldn't be a Dell Technologies World without having you guys on theCUBE, so we appreciate you joining us. So let's dig in. So much has happened in the world since we last spoke with you. But one of the things that happened last year, around a year ago, was the Dell On Demand program was launched. And now here we are nearly a year later when Michael Dell was just talking about, "Hey, Dell's plan is to go "and deliver everything as a service." We've heard some of your competitors kind of going the same route, some kind of spurned by COVID. Talk to us, Devon, we'll start with you, about what this direction is shift to as-a-service means and what it means specifically for storage. >> Yeah, certainly. So first and foremost, what we talked about last year with respect to On Demand, Dell Technologies On Demand, we've had great success with that program. But before I get into what we're doing with as-a-service, I really want to talk about why we're doing the as-a-service. And when we talk to customers and partners, and when we look at the trends in the market, what we're seeing is that customers are more and more wanting to consume technology infrastructure as a service in an OPEX manner. And analysts are revising those estimates up almost daily. And what we're seeing is one of the things that's driving that is actually why we're here in this remote session as opposed to being in Vegas, doing this. And it's really the global uncertainty around the pandemic. So it's driving the need to free up cash and consume these infrastructure more as a service. Now, as Michael said... Yeah, as Michael said, we have the broadest set of infrastructure offerings in the market and we are number one in most categories. And we're in the process of building out an offer structure that cuts across all the different infrastructure components. But to get real specific on what we're doing with a storage as a service, we are in the process of building out the first true storage or as a service offering for our infrastructure starting with storage. It'll be a private preview as of Q4, by the end of this fiscal year and generally available in the first half of next year. And what we're doing is taking the infrastructure, the Dell Technology's storage and where we're flipping the business model as opposed to buying it outright, the customers actually just consume it as a service. So they have a very simple consumption model where they just pick their outcome, they pick their restored service, they pick their performance, they pick their capacity, and we deliver that service to their on-premise site. >> Let me unpack outcomes of it, 'cause I saw that in some of the information online, outcome driven. What do you mean by that, and can you give us some examples of those outcomes that customers are looking to achieve? >> Yeah, so in today's world, the way people mostly consume infrastructure is, or at least storage, is that they say, "I need a storage product." And what the customers do is they work with our sales representatives and say, "I need a XYZ product. "Maybe it's a PowerStore and I need this much capacity. "I can pick all of the components, "I can pick the number of drives, "the type of drives there are." And that's really from a product perspective. And what we're doing with the, as-a-service, is we're trying to flip the model and really drive to what the business outcome is. So the business outcome here is really, I need block storage, I need this performance level, I need this much capacity. And then we basically ship the infrastructure, we think, that better suits those outcomes. And we're making changes across our entire infrastructure value chain to really deliver these service. So we try to deliver these much quicker for the customer. We actually manage the infrastructure. So it enables customers to spend less time managing their infrastructure and more time actually operating the service, paying attention to their business outcomes. >> Got it, and that's what every customer wants more of is more time to actually deliver this business outcomes and make those course corrections as they need to. Joe, let's talk to you for a bit. Let's talk, what's going on with cloud? The last time we saw you, a lot of change as we talked about, but give us a picture of Dell's cloud strategy. From what you guys are doing on-prem to what you are doing with cloud partners. What is this multi-pronged cloud strategy actually mean? >> Yeah, sure, I mean, our customers want hybrid cloud solutions and we believe that to be the model going forward. And so actually what we're doing is, if you think about it, we're taking the best of public cloud and bringing it on-prem, and we're also taking the best of on-prem and bringing it to the public cloud. So, you know, Devon just talked to you about how we're bringing that public cloud operation model to the data center. But what we've also done is bring our storage arrays to the cloud as a service. And we've done that with PowerStore, we've done that with PowerMax, and we've done that with PowerScale. And in the case of PowerScale for Google cloud, I mean, you get the same performance and capacity scale out in the cloud as you do on-prem. And the systems inter-operate between on-prem and cloud so it makes it easy for fluid data mobility across these environments. And for the first time it enables our customers to get their data to the cloud in a way that they can bring their high performance file workloads to the cloud. >> So talk to me a little bit about, you mentioned PowerScale for Google cloud service, is that a Dell hardware based solution? How does that work? >> Yeah, the adoptions have been great. I mean, we launched back in May and since then we brought on customers in oil and gas and eCommerce and in health as well. And we're growing out the regions, we're going to be announcing a new region in North America soon and we're going to be building out in APJ and EMEA as well. So, customer response has been fantastic, looking forward to growing up. >> Excellent, Devon back to you, let's talk about some of the things that are going on with PowerProtect DD, some new cloud services there too. Can you unpack that for us? >> So Joe, was talking about how we were taking our storage systems and putting them in the cloud. So I just back up in, and kind of introduce real quickly or reintroduce our Dell Technologies Cloud Storage Services. And that's really, we have our primary storage systems from Unity XT, the PowerStore, to PowerScale, to ECS, and that's housed in a co-locations facility right next to hyperscalers. And then that enables us to provide a fully managed service offering to our customers to a multi-cloud. So what we're doing is we're extending the Dell Technologies Cloud Storage Services to include PowerProtect DD. So we're bringing PowerProtect DD into this managed services offering so customers can use it for cloud, longterm retention, backup, archiving, and direct backup from a multicloud environment. So extending what we've already done with the Dell Technologies Cloud Storage Services. >> So is that almost kind of like a cloud based data protection solution for those workloads that are running in the cloud VMs, SaaS applications, physical servers, spiral data, things like that? >> Yeah, there's several use cases. So you could have a primary block storage system on your premises and you could actually be providing direct backup into the cloud. You could have backups that you have on-premise that you could be then replicating with PowerProtect data, data domain replication to cloud. And you could also have data in AWS, or Azure, or Google that you could be backing up directly to the PowerProtect domain into this service. So there's multiple use cases. >> Got it, all right. Joe, let's talk about some of the extensions of cloud you guys have both been talking about the last few minutes. One of the recent announcements was about PowerMax being cloud enabled and that's a big deal to cloudify something like that. Help us understand the nature of that, the impetus, and what that means now and what customers are able to actually use today. >> Yeah sure, I mean, we've launched the PowerMax as a cloud service about a year and a half ago with our partner, Faction. And that's for those customers that want that tier zero enterprise grade data capabilities in the cloud. And not just a cloud, it also offers multicloud capabilities for both file and block. Now, in addition, the Dell Tech World, we're launching additional cloud mobility capabilities for PowerMax, where let's say you have a PowerMax on-prem, you could actually do snapshot shipping to an object repository. And that could be in AWS, that can be in Azure, or it could be locally to our local ECS object store. In addition, in the case of Amazon we go a step further where if you do snapshot shipping into Amazon S3, you can then rehydrate those snapshots directly into EBS. And that way you can do processing on that data in the cloud as well. >> Give us an idea, Joe, the last few months or so what some of your customer conversations have been like? I know you're normally in front of customers all the time. Dell Tech World is a great example. I think last year there was about 14,000 folks there, was huge. And we're all so used to that three dimensional engagement, more challenging to do remotely, but talk to me about some of the customer conversations that you've had, and how they've helped influence some of the recent announcements. >> Yeah sure, customers... It might sound a little cliche, but cloud is a journey. It's a journey for our customers. It's a journey for us too, as we build out our capabilities to best serve them. But their questions are, "I want to take advantage "of that elastic compute in the cloud." But maybe the data storage doesn't keep up with it. In the case of when we go to PowerScale for Google, the reason why we brought that platform to the cloud is 'cause you can get hundreds of gigabytes per second of throughput through that. And for our customers that are doing things like processing genomic sequencing data, they need that level of throughput, and they want to move those workloads into the cloud. The computer's there but the storage systems to keep up with it, were not. So by us bringing a solution like this to the cloud, now they can do that. So we see that with PowerScale, we see a lot of that with file in the cloud because the file services in the cloud aren't as mature as some of the other ones like with block and object. So we're helping filling some of those gaps and getting them to those higher performance tiers. And as I was mentioning, with things like PowerMax and PowerStore, it's extending their on-prem presence into the public cloud. So they can start to make decisions not based on a capability, but more based on the requirements for where they want to run their workloads. >> And let's switch gears to talking about partners now. Dell has a huge partner ecosystem. We always talk with those folks on theCUBE as well, every year. Devon, from a product management perspective, tell me about some of the things that are interesting to partners and what the advantages are for partners with this shift in what, how Dell is going to be delivering, from PCs, to storage, to HCI, for example. >> Yeah exactly, so, Joe mentioned that it's really a journey and Joe talked a lot about how customers aren't maybe not (indistinct) completely going to a hyperscale or to a complete public cloud. And what we're hearing is there's a lot of customers that are actually wanting the cloud-like experience, but wanting it on-prem. And we're hearing from our partners almost on a daily basis. I have a lot of partner customer conversations where they want to be involved in delivering this as a service. Through their customers, they want to maintain that relationship, derive that value, and in some cases even provide the services for them. And that's what we're looking do as the largest infrastructure provider with the broadest base of partnership we have an advantage there. >> Is there any specific partner certification programs that partners can get into to help start rolling this out? >> At this point, we are trying to build it, but at this point we had nothing to announce here but that's something that we're actively working on and stay tuned for that. >> I imagine there will be a lot of virtual conversations at the digital tech world this year, between the partner community when all of these things are announced. And you get those brains collectively together although obviously virtually, to start iterating on ideas and developing things that might be great to programmatize down the road. And, Joe, last question for you, second to last question actually, is this, this year as we talked about a number of times, everyone's remote, everyone's virtual. It's challenging to get that level of engagement. We're all so used to being in-person and all of the hallway conversations even that you have when you're walking around the massive show floor for example, what can participants and attendees expect from your perspective this year at Dell Technologies World? Will they be able to get the education and that engagement that Dell really wants to deliver? >> Yeah, well, clearly we had to scale things back quite, there's no way around that. But we have a lot of sessions that were designed to inform them with a new capabilities we've been building out. And not just for cloud, but across the portfolio. So I hope they get a lot out of that. We have some interactive sessions in there as well, for some interactive Q and A. And you're right, I mean, a challenge for us is connecting with the customer in this virtual reality. We're all at home, right? The customers are at home. So we've been on Zoom, like never before, reaching out to customers to better understand where they want to go, what their challenges are and how we can help them. So I would say we are connecting, it's a little different and requires a little more effort on everyone's part. We just can't all do it in the same day anymore. It is just a little more spread out. >> Well, then it kind of shows the opportunity to consume things on demand. And as consumers, we sort of have this expectation that we can get anything we want on demand. But you mentioned, Joe, in the second to last question, this is the last one. But you mentioned, everybody's at home. You have to tell us about that fantastic guitar behind you. What's the story? >> Every guitar has a story. I'll just say for today, look, this is my tribute to Eddie Van Halen. We're going to miss him for sure. >> And I'll have the audience know, I did ask Joe to play us out. He declined, but I'm going to hold them to that for next time, 'cause we're not sure when we're going to get to see you guys in person again. Joe and Devon, thank you so much for joining me on the program today. It's been great talking to you. Lots of things coming, lots of iterations, lots of influence from the customers, influence from COVID and we're excited to see what is to come. Thanks for your time. >> Both: Thank you so much. >> From my guests, Joe Caradonna and Devon Reed, I'm Lisa Martin. You're watching theCUBE's coverage of Dell Technologies World 2020, the Digital Experience. (soft music)

>> Narrator: From around the globe, it's theCUBE with digital coverage of AnsibleFest 2020, brought to you by Red Hat. >> The ascendancy of massive clouds underscored the limits of human labor. People, they simply don't scale at the pace of today's technology. And this trend created an automation mandate for IT which has been further accentuated by the pandemic. The world is witnessing the build-out of a massively distributed system that comprises on-prem apps, public clouds and edge computing. The challenge we face is how to go from managing things you can see and touch to cost effectively managing, securing and scaling these vast systems. It requires an automation first mindset. Hello, everyone. This is Dave Vellante and welcome back to AnsibleFest 2020. We have a great panel to wrap up this show. With me are our three excellent guests and CUBE alums. Ashesh Badani is the Senior Vice President of Cloud Platforms at Red Hat. Ashesh, good to see you again. Thanks for coming on. >> Yeah, likewise. Thanks for having me on again, Dave. >> Stefanie Chiras is Vice President and General Manager of the RHEL Business Unit and my sports buddy. Stefanie, glad to see you back in the New England area. I knew you'd be back. >> Yeah, good to see you, Dave. Thanks for having us today. >> You're very welcome. And then finally, Joe Fitzgerald, longtime CUBE alum, Vice President and General Manager of the Management Business Unit at Red Hat. Joe, good to see you. >> Hey, Dave, good to be here with you. >> Ashesh, I'm going to start with you. Lay out the big picture for us. So how do you see this evolution to what we sometimes talk about as hybrid cloud, but really truly a hybrid cloud environment across these three platforms that I just talked about? >> Yeah, let me start off by echoing something that most of your viewers have probably heard in the past. There's always this notion about developers, developers, developers. And you know, that still holds true. We aren't going away from that anymore. Developers are the new kingmakers. But increasingly, as the scope and complexity of applications and services that are deployed in this heterogeneous environment increases, it's more and more about automation, automation, automation. In the times we live in today, even, you know, before dealing with the crises that, you know, we have, just the sheer magnitude of requirements that are being placed on enterprises and expectations from customers require us to be more and more focused on automating tasks which humans just can't keep up with. So you know, as we look forward, this conversation here today, you know, what Ansible's doing, you know, is squarely aimed at dealing with this complexity that we all face. >> So Stefanie, I wonder if you could talk about what it's going to take to implement what I call this true hybrid cloud, this connection and management of this environment. RHEL is obviously a key piece of that. That's going to be your business unit, but take us through your thoughts there. >> Yeah, so I'm kind of building on what Ashesh said. When we look at this hybrid cloud world, right, which now hybrid is much more than it was considered five years ago. It used to be hybrid was on-prem versus off-prem. Now, hybrid translates to many layers in the stack. It can be VMs hybrid with containers. It can be on-prem with off-prem and clearly with edge involved, as well. Whenever you start to require the ability to bridge across these, that's where we focus on having a platform that allows you to access sort of all of those and be able to deploy your applications in a simple way. When I look at what customers require, it's all about speed of deploying applications, right, build, deploy and run your applications. It's about stability, which is clearly where we're focused on RHEL being able to provide that stability across multiple types of hybrid deployment models. And third is all about scale. It is absolutely all about scale and that's across multiple ranges in hybrid, be it on-prem, off-prem, edge and that's where all of this automation comes in, so to me, it's really about where do you make those strategic decisions that allow you to choose, right, for the flexibility that you need and still be able to deploy applications with speed, have that stability, resiliency, and be able to scale. >> So Joe, let's talk about your swim lane and it's weird to even use that term, right? 'Cause as Stefanie just said, we're kind of breaking down all these silos that we talk in terms of platform, but how do you see this evolving, and specifically, what's the contribution from a management perspective? >> Right, so Stefanie and Ashesh talked about sort of speed, scale and complexity. Right, people are trying to deploy things faster or larger scale, and oh, by the way, keep everything highly available and secure. That's a challenge, right? And so, you know, interestingly enough, Red Hat, about five years ago, we recognized that automation was going to be a problem as people were moving into open hybrid clouds, which we've been working with our customers for years on. And so we acquired this small company called Ansible, which had some really early emerging technology, all open source, right, to do automation. And what we've done over the past five years is we've really amplified that automation and amplified the innovation in that community to be able to provide automation across a wide array of domains that you need to automate, right, and to be able to plug that in to all the different processes that people need in order to be able to go faster, but to track, manage, secure and govern these kind of environments. So we made this bet years ago and it's paying off for Red Hat in very big ways. >> I mean, no doubt about it. I mean, when you guys bought Ansible, so it wasn't clear that it was going to be the clear leader. It is now. I mean, it's pulled ahead of Chef, Puppet. You saw, you know, VMware bought Salt, but I mean, Ansible very clearly has, based on our surveys, the greatest market momentum. We're going to talk about that. I know some of the other analysts have chimed in on this, but let me come back to this notion of on-prem and cloud and edge and this is complicated. I mean, the edge, it's kind of its own island, isn't it? I mean, you got the IT and the OT schism, so maybe you could talk a little bit about how you see those worlds coming together, the cloud, the on-prem, the edge. Maybe Stefanie, you can start. >> Yeah, I think the magic, Dave, is going to happen when it's not its own island, right, as we start to see this world driven by data cause the spread of a data center to be really dis-aggregated and allow that compute to move out closer to the data, the magic happens when it doesn't feel like an island, right, that's the beauty and the promise of hybrid. So when you start to look at what can you provide that is consistent that serves as a single language that you can talk to from on-prem, off-prem and edge, you know, it all comes down to, for us, having a platform that you can build once and deploy across all of those, but the real delicacy with edge is there are some different deployment models. I think that comes into deployment space and we're clearly getting feedback from customers. We're working on some capabilities where edge requires some different deployment models in the ways you update, et cetera, and thanks to all of you out there who are working with us upstream in order to deliver that. And I think the second place where it's unique is in this ability to manage and automate out at the edge, but our goal is certainly at our platform levels, whether it be on RHEL, whether it be on OpenShift to provide that consistent platform that allows you that ease of deployment, then you got to manage and automate it and that's where the whole Ansible and the ecosystem really plays in. You need that ecosystem and that's always what I love about AnsibleFest is this community comes together and it's a vibrant community, for sure. >> Well, I mean, Ashesh, you guys are betting big on this and I often think of the cloud is just this one big cloud. You got the on-prem cloud, you got the public clouds. Edge becomes just an extension of that cloud. Is that how you think about it and what is it actually going to take to make that edge not an island? >> Yeah, great point, Dave, and that's exactly how we think about it. We've always thought about our vision of the cloud as being a platform and abstraction that spans all the underlying infrastructure that the user can take advantage of, so if it happens to reside in a data center, some in a private cloud running off a data center, more increasingly in the public cloud setting, and as Stefanie called out, we're also starting to see edge deployments come in. We're seeing, you know, big build-outs in the work we're doing with telecom providers from a 5G perspective that's helping drive that. We're seeing, if you will, IOT-like opportunities with, let's say, the automotive sector or some in the retail sector, as well. And so this fabric, if you will, needs to span this entire set of deployment that a customer will take advantage of. And Joe started touching on this a little bit, right, with this notion of the speed, scale and complexity, so we see this platform needing to expand to all these footprints that customers are using. At the same time, the requirements that they have, even when they're going out the edge, is the same with regard to what they see in the data center and the public cloud, so putting all that together really is our sweet spot. That's our focus. And to the point you're making, Dave, that's where we're making a huge bet across all of Red Hat. >> So I mentioned, you know, some of our research and I do these breaking analysis segments every week and recently I was digging into cloud and specifically was interested in hybrid and multi. And you know, hybrid been I think pretty well understood for awhile. Multi I think was a lot of, you know, a lot of talk, but it's becoming real and the data really shows that. It shows OpenShift and Ansible have momentum. I mentioned that before. Yeah, you know, obviously VMware is there, but clearly Red Hat is well positioned specifically in multicloud and hybrid. And I know some of the other analyst firms have picked up on this. What are you guys seeing in the market? Maybe Joe, you can chime in and Ashesh, you can maybe add some color. >> Yeah, so you know, there's a lot of fashion, right, around hybrid and multicloud today, so every vendor is jumping on with multicloud storing. And you know, a lot of the vendors' strategies are, pick my solution and vertically use my stuff in the public cloud on-premise, maybe even at the edge, right, and you'll be fine. And you know, obviously customers don't like lock-in. They like to be able to take advantage of the best services, availability, security, different things that are available in each of these different clouds, right? So there is a strong preference for hybrid and multicloud. Red Hat is sort of the Switzerland of hybrid and multicloud because we enable you to run your workloads across all these different substrates, whether it's in public clouds, multiple, right, into the data center and physical, virtual, bare metal, out to the edge and edge is not a single homogeneous, you know, set of hardware or even implementation. It varies a lot by vertical, so you have a lot of diversity, right? And so Red Hat is really good at helping provide the platforms like OpenShift and RHEL that are going to provide that consistency across those different environments or also in the case of Ansible to provide automation that's going to match the physics of management and automation that are required across each of those different environments. Trust me, managing or automating something at the edge and with very small footprint of some device across the constraint network is very, very different than managing things in a public cloud or in a data center and that's where I think Red Hat is really focused and that's our sweet spot, helping people manage those environments. >> And Ashesh, you guys have obviously put a lot of effort there. If you could maybe comment. >> Yeah, I was just going to say, Dave, I'll add just really quickly to what Joe said. He said it well. But the thing I will add is the way for us to succeed here is to follow the user, follow the customer. Right, instead of us just coming out with regard to what we believe the path to be, you know, we're really kind of working closely with the actual customers that we have. So for example, recently been working with a large water utility in Italy, but they're thinking about, you know, the world that they live in and how can they go off and, you know, have kiosks that are spread throughout Italy, able to provide reports with regard to the quality of the water that's available, as well as other services to all their citizens. But it's really interesting use case for us to go off and pursue because in some sense, you can ask yourself, well, is that public cloud? Are they going to take advantage of those services? Is that, you know, private cloud? Is that data center, is that IOT, is that edge? At a certain point in time, what you've got to think about is, well, we've got to provide integrated end-to-end solution that spans all of these different worlds, and so as long as I think we keep that focus, as long as we make sure our North Star is really what the user's trying to do, what problem they're trying to solve, I think we'll come out just fine on the other side of this. >> So I'd love to get all your thoughts, all three of you, on just what's going on in containers, generally, Kubernetes, specifically. I mean, everybody knows it's a hot space and the data shows that it is maturing, but it's amazing to me how much momentum it still has. I mean, it's like the new shiny toy, but it's everywhere and so it's able to sort of maintain that velocity and it's really becoming the go-to cloud native development platform, so the question is how is Red Hat, you know, helping your customers connect OpenShift to the rest of their IT infrastructure, platforms, their processes, the tools. I mean, who wants to start? I'd love to hear from all three of you. Ashesh, why don't you kick it off and then we'll just go left to right. >> So Dave, we've spoken to you and to folks the CUBE, as well, other for many years on this. We've made a huge investment in the Kubernetes market and been one of the earliest to do that and we continue to believe in the promise that it delivers to users, this notion of being able to have an environment that customers can use regardless of the underlying choices that they make. Here's an extremely powerful one, it's truly an open source, right? This is key to, you know, what we do. Increasingly, what we're working on is to ensure that one, if you make a commitment to Kubernetes and increasingly we see lots of customers around the world doing that, that we ensure that we're working closely, that our entire portfolio helps support that. So if you're going to make a choice with regard to Kubernetes base deployment, we help support you running it yourself wherever it is that you choose to run it, we help support you whether you choose to have us manage on your behalf and then also make sure we're providing an entire portfolio of services, both within Red Hat as well as from third parties so that you have the most productive, integrated experience possible. >> Okay, and Stefanie, loved your point of view on this, and Joe, I'd love to understand how you're bridging kind of the Ansible and Kubernetes communities, but Stefanie, why don't you chime in first? >> Yeah, I'll quickly add to what Ashesh said and talked about well on really the promise and the value of containers, but particularly from a RHEL perspective, we have taken all our capabilities and knowledge in the Linux space and we have taken that to apply it to OpenShift, right, because Kubernetes and containers is just another way to deploy Linux, so making sure that that underpinning is stable, secure and resilient and tied to an ecosystem, right? An ecosystem of various architectures, an ecosystem of ISVs and tooling, right? We've pulled that together and everything we've done in Linux for, you know, over decades now at Red Hat and we've put that into that customer experience around OpenShift to deploy containers, so we've really built, it has been a portfolio-wide effort, as Ashesh alluded to, and of course, it passes over to Ansible as well with Joe's portfolio. >> Yeah, we talked about this upfront, Joe. The communities are so crucial, so how are you bridging those Ansible and Kubernetes communities? What's your thought on that? >> Well, a quick note about those communities. So you know, OpenShift is built on Kubernetes and a number of other projects. Kubernetes is number seven in the top 10 open source projects based on the number of contributors. Turns out Ansible is number nine, right? So if you think about it, these are two incredibly robust communities, right? On the one hand, building the container platform in Kubernetes and in the other around Ansible and automation. It turns out that as the need for this digital acceleration and building these container-based applications comes along, there's a lot of other things that have to be done when you deploy container-based applications, whether it's infrastructure automation, right, to expand and manage and automate the infrastructure that you're running your container-based applications on, creating more clusters, you know, configuring storage, network, you know, counts, things like that, but also connecting to other systems in the environment that need to be integrated with around, you know, ITSM or systems of record, change management, inventory, cost, things like that, so what we've done is we've integrated Ansible, right, in a very powerful way with OpenShift through our advanced cluster management capability, which allows us to provide an easy way to instrument Ansible during critical points, whether it's you're deploying new clusters out there or you're deploying a new version of an application or a new application for the first time, whether you're checking policy, right, to ensure that, you know, the thing is secure and that, you know, you can govern these environments, right, that you're relying on. So we've really now tied together two sort of de facto standards, OpenShift built on Kubernetes and a number of other projects and then Ansible, or Red Hat, has taken this innovation in the community and created these certified content collections, platforms and capabilities that people can actually build and rely on and know that it's going to work. >> Ashesh, I mean, Red Hat has earned the right, really, to play in both the cloud native world and of course the traditional infrastructure world, but I'm interested in what you're seeing there, how you're bringing those two worlds together. Are they still, you know, largely separate? Are you seeing traditional IT? I mean, you're certainly seeing them lean in to more and more cloud native, but what are you guys doing specifically to kind of bring those worlds together? >> Yeah, increasingly it's really hard to be able to separate out those worlds, right? So in the past, we used to call it shadow IT. There really is no shadow IT anymore, right? This is IT. So we've embraced that completely. You know, our take on that is to say there are certain applications that are going to be appropriate for being run in a data center a certain way. There are certain other workloads that'll find their way appropriate for the public cloud. We want to make sure we're meeting them across, but what we want to do is constantly introduce technologies to help support the choices customers make. What do I mean by that? Let me give a couple examples. One is, you know, we can say customers have VMs that are based out in specific environments and they can only run as VMs. That code can't be containerized for a variety of reasons, right? You know, hard to re-architect that, don't have the funds, you know, have certain security compliance reasons. Well, what if we could take those VMs and then have them be run in containers in a native fashion? Wouldn't that be extremely powerful value proposition to run containers and then VMs as containers sort of side by side with Kubernetes orchestrating them all. So that's a capability we call open source virtualization. We've introduced that and made that generally available within our platform. Another one, which I think Joe starting to touch on a little bit here, is both around this notion of Ansible, as well as advanced cluster management. And say, once technologies like Ansible are familiar to our customers, how about if we find ways to introduce things like the operator framework to help support people's use of Ansible and introduce technologies like advanced cluster management, which allows for us to say, well, regardless of where you run your clusters, whether you run your Kubernetes clusters on premise, you run them in the cloud, right, we can imagine a consistent fashion and manage, you know, health and policy and compliance of applications across that entire state. So David, question's extremely good one, right, but what we are trying to do is try to be able to say, you know, we are going to just span those two worlds and provide as many tools as possible to ensure that customers feel like, you know, the shift, if you will, or the move between traditional enterprise software application development and the more modern cloud native can be bridged as seamlessly as possible. >> Yeah, Joe, we heard a lot of this at AnsibleFest, so the ACM as a key component of your innovation, and frankly, your competitive posture. Anything you would add to what Ashesh just shared? >> Well, I think that one of the things that Red Hat is really good at is we take management and automation as sort of an intrinsic part of what needs to go on. It's not an afterthought. You just don't go build something, go, "Oh I need management," go out and, you know, go get something, right, so we've been working on, sort of automation and management for many, many years, right, so we build it in concert with these platforms, right, and we understand the physics of these different environments, so we're very focused on that from inception, as opposed to an afterthought when people sort of paint themselves into a corner or have management challenges they can't deal with. >> There's a lot of analogs in our business, isn't there? Management is a bolt-on and security is a bolt-on. It just doesn't work that well and certainly doesn't scale. Stefanie, I want to come back to you and I want to come back to the edge. We hear a lot of people talking about extending their deployments to the edge in the future. I mean, you look at what IBM's doing. They're essentially betting its business on RHEL and OpenShift and betting that its customers are going to do the same as well are you. Maybe talk about, you know, what you're doing to specifically extend RHEL to the edge. >> Yeah, Dave, so we've been looking at this space consistent with our strategy, as Ashesh talked about, right? Our goal is to make sure that it all looks and feels the same and provides one single Linux experience. We've been building on a number of those aspects for quite some time, things like being able to deal with heterogeneous architectures, as an example, being able to deal with, you know, having Arm components and x86 components and power components and being able to leverage all of that from multiple vendors and being able to deploy. Those are things we've been focused on for a long time and now when you move into the space of the edge, certainly we're seeing, you know, essentially data center level hardware move out to be dis-aggregated and dispersed as they move it closer to the data and where that's coming in and where the analysis needs to be done, but some of those foundational things that we've been working on for years starts to pay off because the edge tends to be more heterogeneous all the way from an architecture level to an application level, so now we're seeing some asks. We've been working upstream in order to pull in some features that drive capabilities around specifically updating, deploying those updates, doing rollbacks and things like that, so we're focused on that. But really, it's about pulling together the capabilities of having multiple architectures, dealing with heterogeneous infrastructure out there at the edge, being able to reliably deploy it even when, for example, we have customers who they deploy their hardware and they can't touch it for years. How do they make sure that that's out there in a stable environment that they can count on? And then, you know, adding in things like containerization. We talked about the magic of that, being able to deploy an application consistently and being able to deploy a single container out there to the edge. We're thinking about it all the way from the architecture up to how the application gets deployed and it's going to take the whole portfolio to do that as you need to manage it, as you need to deploy containers, so it's a focus across the company for how we deal with that. >> And as we were talking about before, you know, it takes a village. You know that bromide, but it does, requires an ecosystem of jobs. I mean, there's some real technical challenges in R&D that has to happen. I mean, you've got to be, you know, you're talking about cloud native in all three different clouds, and you know, and not just the big three, but other clouds and then bringing that to the edge, so there's some clear technical challenges, but there's also some business challenges out there. So you know, what are you seeing in that regard? You know, what are some of those things that you hope to solve by bridging that gap? >> Well, I think one of the things we're trying to do and I'm focused on the management and automation side is to provide a common set of management tooling of automation, right, and I think Ansible fits that quite well. So for the past five years since Ansible's been part of Red Hat, we've expanded from, you know, they started off initially doing configuration management, right? We've expanded to include, you know, network and storage and security, now edge. At AnsibleFest, we demonstrated things like serverless event-driven automation, right, building an OpenShift serverless in Knative. We're trying to expand the use cases for Ansible so that there's a simplicity, there's a tool reduction, right, across all these environments and you don't have to go deal with nine vendors, and you know, 17 different tools to try to manage each element here to be able to provide a common set. It reduces complexity, cost and allows skills to be able to be reused across these different areas. It's going to all be about digital acceleration, right, and reducing that complexity. And one last comment. One of the reasons we bought Ansible years ago is the architecture, it's agent-less. Many of our competitors that you hear, the first thing they want to do is go deploy an agent somewhere and that creates its own ongoing burden of, do I have the latest version of the agent? Is it secure? Does it fit on the device? As Stefanie mentioned, is there a version that fits on the architecture the device is running on? It starts getting really, really complicated. So Ansible is just simple, elegant, agent-less. We've expanded the domains we can automate with it and we've expanded sort of the modality. How can I call it? User, driven by an event, as part of some life cycle management, app deployment, Ansible plugs right in. >> Well, Joe, you can tell you're a management guy, right? Agents, another thing that has to be managed. You just laundry list of stuff. (laughs) I want to come back to this notion Joe just touched on, this digital transformation. They say, "If it ain't broke, don't fix it." Well, COVID broke everything. And I got to say, I mean, all the talk about digital transformation over the last, you know, several years, yes, it was certainly happening, but there was also a lot of lip service going on and now if you're not digital, you're out of business. And so, you know, given everything that we've seen in the last, you know, whatever, 150, 200 days or so, what's the impact that you're seeing on customers' digital transformation initiatives, and you know, what is Red Hat doing to respond? Maybe Ashesh, you could start and we can get feedback from the others. >> Yeah, David, it's an unfortunate thing to say, right, but there's that meme going around with regard to who's responsible for digital transformation and it's a little bit of I guess gallows humor to call it COVID, but we're increasingly seeing that customers and the journey that they're on is one that they haven't really gotten off, even with this, if you will, change of environment that's come about. So projects that we've seen in play, you know, are still underway. We've seen acceleration, actually, in some places with regard to making services more easily accessible. Anyone who's invested in hybrid cloud or public cloud is seeing huge value with regard to being able to consume services remotely, being able to do this on demand and that's a big part of the value proposition, you know, that comes forward. And increasingly what we're trying to do is try to say, how can we engage and assist you in these times, right? So our services team, for example, has transformed to be able to help customers remotely. Our support team has gone off and work more and more with customers. For a company like Red Hat, that hasn't been completely, if you will, difficult thing to do mostly because we've been so used to working in a distributed fashion, working remotely with our customers, so that's not a challenge in itself, but making sure customers understand that this is really a critical journey for them to go on and how we can kind of help them, you know, walk through that has been good and we're finding that that message really resonates. Right, so both Stefanie and Joe talked a little bit about, you know, how essentially our entire portfolio is now built around, you know, ensuring that if you'd like to consume on demand, we can help support you, if you'd like to consume in a traditional fashion, we can help you. That amount of flexibility that we provide to customers is really coming to bear at this point in time. >> So maybe we could wrap with, we haven't really dropped any customer names. Stefanie and Joe and Ashesh, I wonder if you have any stories you can share or, you know, customer examples that we could close on that are exciting to you this year. >> So I can start, if that's okay. >> Please. >> So an area that I find super interesting from a customer perspective that we're increasingly seeing more and more customers go down is sheer interest in, if you will, kind of diversity of use cases that we're seeing, right? So we see this, for example, in automotive, right? So whether it's a BMW or a Volkswagen, we see this now in health care with the ACA, in we'll say a little bit more traditional industries like energy with Exxon or Schlumberger around increasingly embrace of AIML, right? So artificial machine learning, if you will, advanced analytics being much more proactive with regard to how they can take data that's coming in, adjust it, be able to make sense of the patterns and then be able to, you know, have some action that has real business impact. So this whole trend towards, you know, AIML workloads that they can run is extremely powerful. We work very closely with Nvidia, as well, and we're seeing a lot of interest, for example, in being able to run a Kubernetes-based platform, support Nvidia GPUs for specific class workloads. There's a whole bunch of customers, people in financial services that, you know, this is a rich area of interest. You know, we've seen great use cases for example around grid with Deutsche Bank. And so, to me, I'm personally really excited to see kind of that embrace the PC from our customers regard to saying there's a whole lot of data that's out there. You know, how can we essentially use all of these tools that we have in place? You know, we talk about containers, microservices, DevOps, you know, all of this and then put it to bear to really put to work and get business value. >> Great, thank you for that, Ashesh. Stefanie, Joe, Stefanie, anything you want to add or final thoughts? >> Yeah, just one thing to add and I think Ashesh talked to a whole number across industry verticals and customers. But I think the one thing that I've seen through COVID is that if nothing else, it's taught us that change is the only constant and I think, you know, our whole vision of open hybrid cloud is how to enable customers to be flexible and do what they need to do when they need to do it, wherever they want to deploy, however they want to build. We provide them some consistency, right, across that as they make those changes and I think as I've worked with customers here through since the beginning of COVID, it's been amazing to me the diversity of how they've had to respond. Some have doubled down in the data center, some have doubled down on going public cloud and to me, this is the proof of the strategy that we're on, right, that open hybrid cloud is about delivering flexibility, and boy, nothing's taught us the need for flexibility like COVID has recently, so I think there's a lot more to do. I think pulling together the platforms and the automation is what is going to enable the ability to do that in a simple fashion. >> So Joe, you get the final word. I mean, AnsibleFest 2020, I mean, it's weird, right? But that's the way these events are, all virtual. Hopefully, next year we got a shot at being face to face, but bring us home, please. >> Yeah, I got to tell ya, having, you know, 20,000 or so of your closest friends get together to talk about automation for a couple of days is just amazing. That just shows you sort of the power of it. You know, we have a lot of customers this week at AnsibleFest telling you their story, you know, CarMax and ExxonMobil, you know, BlueCross BlueShield. I mean, there's a number across all different verticals, globally, Cepsa from Europe. I mean, just an incredibly, you know, diverse array of customers and use cases. I would encourage people to look at some of the customer presentations that were on at AnsibleFest, listen to the customer telling you what they're doing with Ansible, deploying their networks, deploying their apps, managing their infrastructure, container apps, traditional apps, connecting it, moving faster. They have amazing stories. I encourage people to go look. >> Well, guys, thanks so much for helping us wrap up AnsibleFest 2020. It was really a great discussion. You guys have always been awesome CUBE guests. Really appreciate the partnership and so thank you. >> Thanks a lot, Dave. Appreciate it. >> Yeah, thanks, Dave. >> Thanks for having us. >> All right, and thank you for watching, everybody. This is Dave Vellante for theCUBE and we'll see you next time. (calm music)

>>From around the globe. It's the cube presenting, accelerating automation with dev net brought to you by Cisco and welcome back to the cubes coverage. Just to keep virtuals coverage of dev net create virtual. We're not face to face the cubes been there with dev net and dev net create. Since the beginning, dev net create was really a part of the dev net community. Looking out at the external market outside of Cisco, which essentially is the cloud native world, which is going mainstream. We've got a great guest here. Who's who's been the company's been on the cube. Many times. We've been talking to them recently acquired by Cisco thousand eyes. We have Joe Vaccaro, his beast vice president of product, Joe, welcome to the cube. Thanks for coming on. Great. And thanks for having me. You have the keys to the kingdom. You are the vice president of product, which means you get to look inside and you get to look outside, figure it all out, uh, make everything run on thousand eyes. >>You guys have been finding common language across multiple layers of network intelligence, external services. This is the heart of what we're seeing in innovation with multi-cloud microservices, cloud native. This is really a hot area it's converged in multiple theaters and technology super important. So I want to get into that with you. But first thousand eyes was recently acquired by Cisco, um, big acquisition, uh, super important, the new CEO of Cisco, very clear API, everything we're seeing that come out. That's a big theme at dev net create the ecosystem of Cisco is going outside their own, you know, their, their walls outside of the Cisco network operators, network engineers. We're talking to developers talking programmability. This is the big theme. What's it like at Cisco? Tell us, honestly, the COVID hits. You get acquired by Cisco. Tell us what's happening. >>Yeah, surely been an exciting six months, 4,000 eyes on the entire team and our customers as we all kind of shifted to the new normal of working from home. And I think, you know, that change alone really kind of amplified. Even some of the fundamental beliefs that we have as a company that you know, cloud is becoming the new data center or customers that Indra internet has become the new network and the new enterprise network backbone. And that SAS has really become the new application stack. And as you think about these last six months, those fundamental truths have never been more evident as we rely upon the cloud to be able to, to work as we rely upon our own home networks and the internet in order to be productive. And as we access more sized applications on a daily basis. And as you think about those fundamental truths, what's common across all of them is that you rely upon them now more than ever, not only to run your business, but to enable your employees to be productive, but you don't own them. And if you don't own them, then you lack the ability in a traditional way to be able to understand that digital experience. And I think that's ultimately what, what thousand eyes is trying to solve for. And I think it's really being amplified in really these last six months. >>Talk about the COVID dynamic because I think it highlighted and certainly accelerated digital transformation, but specifically exposes opportunities, challenges, weaknesses, I've talked to many CXOs CSOs. Uh, sec security is huge. Um, the home of the conference and book talk track we'll get to in a second, but it exposes what's worth doubling down on what to abandoned from a project standpoint, as people start to look at their priorities, they're going, Hey, we got to have a connected experience. We got to have security. People are working at home. No one has VPNs at home VPNs or passe. Maybe it's SD when maybe it's something else they're on a backbone. They're connecting to the internet, a lot of different diversity in connections. At the same time, you got a ton of modern apps running off for these networks. This is a huge issue. COVID is exposed this at scale. What's your view on this? And what does thousand nights thinking about this? >>You know, if you think about the kind of legacy application delivery, it went from largely users in an office connected over, say a dedicated corporate network, largely to traditional say internal hosted applications. And that was a early, simple, uh, connectivity bath. And as you mentioned, we've seen amplifications in terms of the diversity from the users. So users are not in the office. Now they're connected in distributed disparate locations that are dynamically changing. And you think that how they're getting to that application, they're going across a really complex service chain of different network services that are working together across as public internet backbone. We'll totally to land them on an application. And then those applications themselves are becoming now, as you mentioned, distributed largely based upon a microservices architecture and increasing barrel independence upon third party sample size applications to fulfill say key functions of that application. >>Those three things together ultimately are creating that level of complex service chain. It really makes it difficult to understand the digital experience and ultimately the it organization it's really chartered with not just delivering the infrastructure, but delivering the right experience. And yet then have a way to be able to see, to gain that visibility, that experience, you know, to measure it and understand, and to provide that intelligence and then ultimately to act on it and be able to ensure that your employees, as well as your customers are getting the right overall, um, approach to being able to leverage those assets. >>It's funny, you know, as you're getting to some of these high-scale environments, a lot of these concepts are converging. You know, we had terms like automation self-healing networks. Um, you mentioned microservices earlier, you mentioned data out of the clouds, the new data center, uh, or when's the new land. However, we're going to look at it. It's a whole different architecture. So I want to get your thoughts on, on the automation piece of networking and internet outages, for instance, um, because when you, you know, there's so many outages going up and down, it is like, uh, catching, looking for a needle in a haystack, right. So, um, we've had this conversation with you guys on cube before. How does automation occur when you guys look at those kinds of things what's important to look at? Can you comment on and react to, you know, the internet outages and how you find resolve those? >>Yeah. It's um, it was really great. And as you mentioned, automation really in a place that a key, when you think about the, just a broad problem that it is trying to drive and, you know, from our lens, we look at it in really three ways. Your first off is you have to be able to gain the level of visibility from where it matters and be able to, to test and be able to provide that level of active measurements across the, the type of ways you want to be able to inspect the network. But then also from the right vantage points, you want to inspect it. But what we talked about right aside, you know, data, um, alone, doesn't solve that problem. As you mentioned, that needle in the haystack, you know, data just provides the raw metrics that are screaming across the screen, and you have to then enable that data to provide meeting. >>You need to enable that data to become intelligent. And that intelligence comes through the automation of being able to process that data very quickly. They'll allow you to be able to see the unseen, allow you to be able to quickly understand the issues that are happening across this digital supply chain to identify issues that are even happening outside of your own control across the public internet. And then the last step of automation really comes in the form of the action, right? How do you enable that intelligence to be put, to use? How do you enable that intelligence to then drive across the rest of your it workflow as well as be able to be used as a signaling engine, to be able to then make the fundamental changes back to the network fabric, whether that is a dressing you're modifying your BGB pairing, that we see happen within our customers using thousand eyes data, be able to route around major internet outages that we've seen over the past six months, or to be able to then use that data, to be able to optimize the ultimate experience that they're delivering to both our customers, as well as our employees, >>Classic policy based activities take into a whole nother level. I got to get your thoughts on the employees working at home. Okay. Because, um, you know, most it people like, Oh yeah, we're going to forecast in cases of disruption or a hurricane or a flood or arcane Sandy, but now with COVID, everyone's working at home. So who would have forecasted a hundred percent, um, you know, work from home, which puts a lot of pressure on him, everything. So I got to ask you, now that employees are working at home, how do you tie network visibility to the actual user experience? >>Yeah, that's a great question. As you know, we saw it within our own customer base, you know, when COVID head and we saw this rise of work from home, it teams were really scrambling and said, okay, I have to light up this, say VPN infrastructure, or I need to now be able to support my users in a work from home situation where I don't control the corporate network. In essence, now you have naturally thousands. Every employee is acting across their own corporate network and people were then using thousand eyes in different ways to be able to monitor their CTP and infrastructure across, uh, back into the corporate network, as well as in using our thousand eyes endpoint point agents that runs on a local, a user's laptop or machine in their home to help you to be able to gain that visibility down to that last mile of connectivity. >>Because when a user calls up support and says, I'm having trouble say accessing my application, whether that's Salesforce or something else, what ultimately might be causing that issue might not necessarily be a Salesforce issue, right? It could be the device in the device performance in terms of CPU, memory utilization. It could be the wifi and the signal quality within your wifi network. It could be your access point. It could be your raw, local home router. It can be your local ISP. It could be the path that you're taking ultimately to your corporate network or that application. There's so many places that could go wrong that are now difficult to be able to see, unless you have the ability to see comprehensively from the user to the application, and to be able to understand that full end to end path, >>You know, it teams have also been disrupted. They've been on offsite prop off property as well, but you got the cloud. How is your technology help the it teams? Can you give some examples there? Um, >>Yeah, a great way is, you know, how people use thousand eyes as part of that data sharing ecosystem. Again, that notion of how do you go from visibility to intelligence to action and where in the past you might be able as an it administrator to walk over to their network team and say, Hey, can you take a look at what I'm seeing now? That's no longer available. So how do you be able to work efficiently as the Nike organization? You know, we think a thousand eyes and how our customers are using us a thousand times becomes a common operating language and allows them to be able to analyze across from the application down into the underlying infrastructure, through those different layers of the network what's happening. And where do you need to focus your attention? And then furthermore, within thousand eyes in terms of a need, enabling that data sharing ecosystem, leveraging our Sherlyn capability really gives them the ability to say, you know, what, here's what I'm seeing and be able to send that to anybody within the it organization. But it goes even further and many times in recent times, as well as over the course of people using thousand eyes, they take those share links and actually send them to their external providers because they're not just looking to resolve issues within their own it organization. They're having worked collaboratively with the different ESPs that they're pairing with, with their cloud providers that they're appearing, uh, they're leveraging, or the SAS applications that are part of that core dependency of how they deliver their experience. >>I've got to ask you the question we think about levels of visibility and making the lives easier for it. Teams. Um, you see a lot of benefits with thousand eyes. You pointed out a few of them. It's got to ask you the question. So if I'm an it person I'm in the trenches, are you guys have, uh, an aspirin or a vitamin or both? Can you give an example because it does a lot of pain point out there. So yeah. Give me a, a cup, a couple Advils and aspirins, but also you're an enabler. The new things are evolving. You pointed out some use case. Talk about the difference between where you're helping people pain points and also enabling them be successful for it teams. >>Yeah, that's a great analogy. You're thinking it, like you said, it definitely sits on both sides of that spectrum, you know, thousand eyes is the trusted tool, the source of truth for it. Organizations when issues are happening as their alarm bells are ringing, as they are generating the, um, the different, uh, on call, uh, to be able to jump into a worm situation thousand eyes is that trusted source of truth. Allow them to focus, to be able to resolve the issue in the heat of the moment. But that was a nice also when we think about baselining, your experience, what's important is not understanding that experience at that moment in time, but also how that's deviated over time. And so by leveraging thousand eyes on a continuous basis, it gives you the ability to see the history of that experience, to understand how your network is changing is as you mentioned, networks are constantly evolving, right? >>The internet itself is constantly changing. It's an organic system, and you need to be able to understand not only what are the metrics that are moving out of your bounds, but then what is potentially the cause of that as a network has evolved. And then furthermore, you can be begin to use that, as you mentioned, in terms of your vitamin type event analogy, you'll be able to understand the health of your system over time on a baseline basis so that you can begin to, uh, be able to ensure its success in a great way to really kind of bring that to light as people using say, thousand eyes, as part of saying se land base for allow where you're looking to say benchmark and gain confidence as you look to scale out and either, you know, benchmarking different ESPs within that, I feel like connectivity for as you look to ensure a level of success with a single branch to give you that competence, to then scale out to the rest of your organization. >>That's great insights. The classic financial model ROI got baseline and upside, right? You got handle the baseline as you pointed out, and the upside music experience connectivity, you know, application performance, which drives revenue, et cetera. So great point. Great insight, Joe. Thank you so much for that insight. It's got a final question for you. I want to just riff a little bit with you on the industry. A lot of us have been having debates about automation. I mean, who doesn't, who doesn't love automation, automation's awesome, right? Automate things. But as the trend starts going on, as everything is a service or X, a S as it's called, certainly Cisco's going down that road. Talk about your view about the difference between automation and everything is a service because at the end of the day, everything will be a service, but without automation, you really can't have services, right? So, you know, automation, automation, automation, great, great drum to bang all day long, but then also you got the same business side saying as a service, as a service, pushing that into the products, it means not trivial. Talk about, talk about how you look at automation and everything as a, and the relationship and interplay between those two concepts. >>Yeah. Ultimately I think about in terms of what is the problem that the business is trying to solve in ultimately, what is the value that they're trying to face? And in many ways, right, they're being exploded with increase of data that needs, they need to be able to not only process and gather, but then be able to then make use of, and then from that, as we mentioned, once you've processed that data and you'd say, gather the insights from it. You need to be able to then act on that data. And automation plays a key role of allowing you to be able to then put that through your workflow. Because again, as that, it experience becomes even more complex as more and more services get put into that digital supply chain. As you adopt say increased complexity within your infrastructure, by moving to a multicloud architecture where you look to increase the number of say, network services that you're leveraging across that digital experience. >>Ultimately you need the level of automation. You'd be able to see outside of your own vantage point. You need to be able to look at the problem from as broad of a, a broad of a way as possible. And, you know, data and automation allows you to be able to do what is fundamentally difficult to do from a very narrow point of view, in terms of the visibility you gather intelligence you generate, and then ultimately, how do you act on that data as quick as possible to be able to provide the value of what you're looking, salt >>Feature it's under the hood, the feature of everything, because the service is automation, data, machine learning, all the goodness and the software. I mean, that's really kind of what we're talking about here. Isn't it a final question for you as we wrap up, uh, dev net create really, again, is going beyond Cisco's dev net community going into the industry ecosystem where developers are there. Um, these are folks that want infrastructure as code. They want network as code. So network programmability, huge topic. We've been having that conversation, uh, with Cisco and others throughout the industry for the past three years. What's your message to developers out there that are watching this who say, Hey, I just want to develop code. Like I want, you know, you guys got that. That was nice. Thanks so much. You know, you take care of that. I just want to write code. What's your message to those folks out there who want to tap some of these new services, these new automation, these new capabilities, what's your message. >>And ultimately, I think, you know, when you look at thousand eyes, um, you know, from a product perspective, we, you know, we try to build our product in an API first model to allow you to be able to then shift left of how you think about that overall experience. And from a developer standpoint, you know, what I'd say is, is that while you're developing in your silo, you're going to be part of a larger ultimate system. In your experience you deliver within your application is now going to be dependent upon not only the infrastructure it's running upon, but the network it's connected to. And then ultimately the user in the sense of that user and by leveraging a thousand eyes, being able to then integrate thousand 18 to how you think closely on that experience, that's going to help ensure that ultimately the application experience that the developers looking to deliver meets that objective. And I think what I would say is, you know, while you need to focus on your, uh, your role as a developer, having the understanding of how you fit into the larger ecosystem and what the reality of how your users will access that application is critical. >>Awesome, Joe, thank you so much. Again, trust is everything letting people understand that what's going on underneath is going to be viable and capable. You guys got a great product and congratulations on the acquisition that Cisco made of your company. And we've been following you guys for a long time and a great technology chops, great market traction, congratulations to everyone, 1,009. Thanks for coming on sharing. I appreciate it. Thanks for having me. Do you have a car, a vice president of product here with thousand eyes. Now, part of Cisco I'm John farrier, host of the cube cube virtual for dev net. Create virtual. Thanks for watching.

>> Announcer: From around the globe, it's theCUBE! With digital coverage of AnsibleFest 2020, brought to you by Red Hat. >> Hello, everyone, welcome back to theCUBE's coverage of AnsibleFest 2020. We're not face-to-face this year, we're in virtual remote mode. This is theCUBE virtual and obviously it's AnsibleFest 2020 virtual. We've got a great panel of experts and leaders at Red Hat and Ansible. I want to introduce them. Dave Lindquist, general manager and vice president of engineering of hybrid cloud management at Red Hat. Joe Fernandes, vice president and general manager of the Core Cloud platforms at Red Hat. And Tom Anderson, vice President at Red Hat, Ansible Automation Platform, the big news and feature of this event. Tom, great to see you, Joe and David, thanks for coming on. >> Great to be here. >> Every year I love talking about Red Hat because I remember going back a few years ago, Arvind from IBM was on at Red Hat Summit in San Francisco, and you can see the twinkle in his eye. This was three, four years ago. Cloud native was really gearing up and now it's kind of mainstream. Last year at AnsibleFest, all the buzz was collaboration, collections, and you can start to see that integration piece kicking in, and this year at the event, the big story is the same. More collections, more integrations, a lot of collaboration around code. Content equals code. So it really points to the trend with Kubernetes of multi-cloud, multi-cluster. So the first question for you guys is, why would anyone want to deploy multiple clusters simultaneously and why is multi-cluster such a big deal? Tom, we'll start with you. >> Great, okay, yeah. So why is multi-cluster such a big deal? Basically, Kubernetes and our OpenShift container platform have now become a strategic part of our customers' environments, of their infrastructure for building and deploying cloud native applications on. And as becoming a strategic part of that, when you're deploying production applications you're going to need all kinds of things like scale out, redundancy, cloud location for access to different cloud provider locations for application requirements and whatnot. So there are a bunch of requirements for why customers would deploy OpenShift in a multi-cluster way. And maybe I'll turn it over to Joe Fernandes a little bit 'cause he's got a lot of background on the OpenShift side of this. >> Joe, what's your thoughts? >> Yeah, thanks, Tom. Yeah, so I mean, as Tom mentions, a number of reasons why customers may deploy or need to deploy more than one Kubernetes cluster. So within a cluster, you can certainly have multiple applications, multiple developers, multiple teams work, but as you start to scale your usage you may want additional clusters. It could be because you want to separate your production environments from your dev and test environments. It could be for capacity, right? You have more development teams or more production environments than you want to sort of tie to a single cluster. Then you start expanding out into locations, right? Maybe you started in the data center, then you started doing deployments to one public cloud, then to other public clouds, and then that's only going to grow. We see more and more customers deploying multi-cloud strategies. And then the new thing right now that everybody wants to talk to us about is edge, and as you get into edge deployments, now those, the number of clusters could really explode into the hundreds or thousands. And so it all points back to you need a sane way to manage across all these clusters regardless of where they run and regardless of how many you have, and that's really what we've been working on with the Advanced Cluster Management for Kubernetes. >> What's the big draw? What's drawing the customers in with multi-cluster and multi-cloud? Obviously, the multi-cloud makes a lot of sense, you have multiple clouds. Sounds easier just saying it than doing it. But what is it about multi-cluster and multi-cloud that's drawing customers and people into this concept? >> Yes, I can start. I think what's drawing customers in is the need, the desire to have sort of a common abstraction for the applications that's consistent regardless of where they happen to run, right? So making sure that the developers don't have to worry about what infrastructure the applications are landing on, and they have that consistent experience that it's, abstracts their applications away from that infrastructure. So that gives the developers more flexibility, but it's also about flexibility and agility for those infrastructure owners, right, because they too want to make decisions on where stuff runs. Not because they're particularly tied to an infrastructure, but based on things like cost or security or other concerns. And so these are all drivers for multi-cluster and multi-cloud strategies and I think our hybrid cloud strategy at Red Hat really hits the mark to address those needs. >> Well, you guys had great performance. We've been following the past few years just the OpenShift and beyond, kind of the whole Red Hat, and Ansible specifically too, is doing real well in the marketplace so congratulations. David, I want to ask you about the management piece. This comes up over and over again. It's all good having the abstraction layer, you got all kinds of new sets of services, but multi-cluster management is not, (laughs) is not trivial. There's challenges for ops and automation teams. Could you share your perspective on how you guys are looking at the multi-cluster management? >> Sure, sure. The first thing we saw, and this kind of follows on the points that Joe and Tom are making, is that as customers start embracing the development with containers and leveraging Kubernetes, you start finding that they're putting up clusters across their data centers, across cloud, to support different parts of the life cycle of development, or supporting their own production environment or distributed workloads across clouds, across the data centers. And so the challenges that operations and management run into, and security in particular, is how do you start managing the clusters, their life cycle. It's easy to put 'em up, to provision 'em quickly, but how do you update and upgrade those? How do you make sure they're compliant with your various regulatory compliance like PCI, HIPAA, or the various federal standards? How do you make sure that compliance is adhered to across, and security across those clusters, as well as the applications themselves? How do you manage the applications through their life cycle? How do you have deployment policies? So the challenges for ops and automation and security are to have a consistent policy-driven way to take care of the clusters across these hybrid environments, and making sure they adhere to the compliance and security of the enterprise. >> Tom, multi-cluster deployments is a big part of this integration. We heard a little bit, obviously, compliance and governance is huge. IT's been living this world of policies and governance, but when we start moving fast into these new cutting edge services that are providing a lot of value, integration into existing IT infrastructure is important with clusters. How do you view that because this is where I think maybe collections are other things are, is this an indicator of what's happening? Can you give your thoughts on the customers out there who want to do multiple clusters for all the benefits, but then go, "Oh, I got to integrate it into existing IT infrastructure"? >> Yeah, absolutely. So that's what's happening right now. As Kubernetes and as OpenShift has become a strategic platform for our customers, the idea of, I'm going to say, kind of normalizing the operations of that platform as part of a greater IT ecosystem has become a challenge for them. And for the most part, they've already automated security, network, provisioning, app deployment, application updates, using the Ansible Automation Platform, and so it only makes sense that as Kubernetes and as OpenShift becomes a strategic platform for them, they want to use that same language, that same tool set, that same automation fabric, if you will, to integrate the applications that are running on OpenShift with the rest of the environment. So, for example, when I add a new node to a cluster or more capacity to a cluster or to clusters, I probably want to update my systems of record, right? My CMDBs or my ITSM systems. When I deploy a new app or make an update to an app on a cluster or across clusters, I'm probably going to want to update my load balancer to be able to direct traffic correctly to that, and that load balancer probably isn't running, my enterprise load balancer is kind of platform independent, so I'd need to be able to update that load balancer to properly direct traffic. Well, IT has already automated that function using Ansible. So by creating the collections that we have created for OpenShift and for Kubernetes, it makes it much easier for our customers to be able to just plug that in and adapt that to their existing automation infrastructure. So now it just becomes part of their overall IT environment. >> So just a follow-up real quick, if you don't mind. What are some of the challenges you're hearing from your customers around containerization and that growing space? I just talked to the IDC research analyst earlier at another virtual CUBE session where she says, roughly their estimate is 5 to 10% of enterprises are containerized, which is huge growth opportunities. The headroom in containers is massive, so what are some of the challenges? Is it easy to get started? This seems to be a nice opportunity for you guys. What's your take on that? >> Yeah, I think that the way of looking at it with all that growth space, it's also the speed at which Kubernetes adoption and containerized application adoption is happening. And so, IT organizations are having to respond faster than they ever have before as this environment grows, and it is a multi-cloud environment. They have Kubernetes, OpenShift running on-prem, in the cloud, multiple data centers, as both Joe and Dave have said, and it becomes critical that they automate that correctly and accurately to ensure security, consistency, performance, availability. All of the other things that drive the requirement for automation standardization, all of those things that drive the requirements for automation are applicable to Kubernetes environments and containerized environments as well except they're moving and expanding faster, so teams have to respond quicker to the need. >> Joe, what's your take on this? I mean, to me, I'm the glass half full. I think I've seen containers be great and that maybe I'm looking at the early adopters, but those numbers seem a little bit low to me. What does that mean to you? More people are now getting up to speed. Is it a tipping point? It just seems a little bit low, and David, if you want to comment too, I think this an important number there. Joe, what's your take? >> Yeah, I mean, I think the rate represents an opportunity, but I see the growth as having been tremendous even in just the first few years. But to get to that broader market we did continue making it easier for customers to bring their applications to this new environment, to ride on existing infrastructure, and ultimately for our customers that means an evolution, right? An evolution of how they are going to manage those applications, how they're going to build and deploy them. And so with the integration of OpenShift and our advanced container management platforms with Ansible we can bring that automation to the mix to sort of tie those together, right? So to tie in the existing compute infrastructure, to tie in storage and networking and configure those as needed. And then as Tom mentioned, all those other systems, whether it's an IT service management system, something like a ServiceNow or other ticketing systems or other enterprise systems that exist that you just can't ignore. Because the more you try to go against the grain and do something different, the even harder it'll be. So we need to help customers evolve to take advantage of cloud and cloud native approaches, and the solutions that we're bringing to market are all about enterprise Kubernetes, enterprise container platforms. The combination of those technologies with something like Ansible really helps pave the path for the next phase of growth that we're expecting. >> So, ready for prime time right now. >> Right. >> David, your thoughts real quick on this. Containerization upside. >> Yeah, real quick, the development organizations, development teams, have picked up on containers very rapidly. Everybody is leveraging containers when they develop new applications or modernize the existing applications. So what we found is that a lot of the folks that pushed out very quickly, some greenfield apps, that's the 5, 10, 15, 20% that you're seeing occur. What started getting complex is how you really scale this to your enterprise. How do you really run this at scale from management operations and security perspective? OpenShift is critical, that gives a consistent platform across the hybrid cloud environments. What we're doing with ACM and the Advanced Cluster Management brings in the security and compliance. And what you'll see through AnsibleFest, what we're doing with Ansible is then, how do we then hook these environments right into all the existing IT environments? That's, to me, what's critical to really bring this to scale to the enterprise. >> Yeah, I think this, to me, the number points to exactly what you guys said. Ready for prime time, scale's there, and the demand's there. And I think, Tom and Joe, I want to ask you specifically the relationship between OpenShift and Ansible, but before that, I remember, forget what year it was, we were doing a CUBE event at, I think it might've been OpenStack, going back to the day, but I remember OpenShift and it was a moment where OpenShift adopted containers and then next year Kubernetes. And I remember talking to the team, them saying, "This is going to be a big bet for OpenShift." Looks like it was a good bet. (laughs) It paid out real well, congratulations. And it was good, you guys stayed the course. But you made it easier, and one of the things was is that the complaint at the time was they didn't want Kubernetes to be the next Hadoop. Easy to use but gets out of control. Not that I meant they're comparable, but Hadoop had that problem of it was easy open source but then it was hard to manage. So OpenShift really took advantage of that. You guys, I think, did a good job on that. But now you got Ansible winning the game on developers, on easy to deploy, so as that scales up, automation's there. So I'd like to hear you guys talk about the connection between OpenShift and Ansible and how that expands the scope of what both products can do for customers. >> Yeah, maybe I'll give it a shot first and then let Joe go after me, which is, look, here's what we have, is we have lots and lots and lots of customers, Red Hat customers that are OpenShift users and that are Ansible users, right? So we have this two large pools. They also represent two very large and vibrant open source community projects. The Ansible project and the Kubernetes project are two hugely popular, vibrant communities, and so it just made sense to kind of be a catalyst in those communities, to bring those two things together, to work together, to the benefit of our customers and to kind of capture the innovation that's going on upstream in the communities. So we decided to get really kind of serious about the integration of these two platforms and integrated Ansible in a native way on Kubernetes so that OpenShift and Kubernetes operators, as well as application developers, could take advantage of that integration without having to learn something new or foreign in order to be able to do it. So it was a native integration using operators, which is the right way to integrate with the Kubernetes platform, with OpenShift in particular. And so that's the way we kind of brought it together to the benefit of our customers. Our customers are, like I said, normalizing the operations of OpenShift as a strategic part of their infrastructure, deploying production applications, and want to be able to tie that into their other systems and other parts of their infrastructure, both from an app deployment process as well as from an infrastructure deployment and management process. So it only made sense that it actually, our customers have been asking us for this and talking to us about this, so it only kind of made perfect sense to kind of get out there and do that, get the communities together innovating, and then take that innovation out for our customer. >> Joe. >> Yeah, the only thing I'd add to that, there's really two specific personas at play here, right? When you think of, there's the IT operations and infrastructure teams. They own those clusters, the provisioning, the configuration, the management of those clusters. And with ACM, with Advanced Cluster Management for Kubernetes, we have now an interface that they can use to see and manage the life cycle of all their clusters. So through that we can integrate Ansible as another automation tool in their portfolio to do things that need to happen when those clusters first get configured or when those clusters get updated and so forth. So if they need to update an ITSM system or configure a network or do whatever it needs to, you have Ansible automation scripts that can be plugged in at the appropriate time in that cluster's life cycle to do that. On the other side, you have the developer and DevOps teams that are consumers of these platforms, right? And what they care about is the applications that they're building, but there's a lot that goes into building it, right? There's the source code management systems, there's the CI systems, the CD systems, there's the test environments and stage and prod. And so there's a lot of moving parts, and again, and then there's the services themselves that they're configuring so you have, or building, not configuring, you have Ansible again ready to sort of take on some of those tasks, automation tasks that go beyond what Kubernetes is focused on or what you're trying to do with OpenShift. And again, doing it at the appropriate time in the life cycle, all tied in through Advanced Cluster Management which can actually see out to all those clusters and be in that sort of application deployment workflow across those clusters. So those are sort of some of the specific areas and how they pertain to those specific personas that are driving the activity. >> What's interesting, this automation piece really is key across multiple environments, and we've heard that from some of your customers. 'Cause you got now private clouds out there, you got large scale. But, Dave, I want to ask you, what makes Advanced Cluster Management a natural fit with OpenShift and Ansible? What's your take? >> Yeah, good question, John. First, ACM is purpose-built for the Kubernetes environment. It's a cloud native management system, and as we said earlier, we really focused on managing the cluster life cycles, managing the security compliance, and managing applications deployed into these environments. So it was a very natural extension of OpenShift, to be able to manage OpenShift, multiple clusters of OpenShift in hybrid environments. Within your data center, across data centers, across clouds, and the combination. So, very natural fit with OpenShift. As we've been all talking about, as we looked at how did we then bring OpenShift and these resources closer through automation to many of the other parts of your IT environment, that made it natural from ACM to call out into the playbooks of Ansible. So just a simple example, and I think we circled around this a few times. You're deploying a cluster or you're deploying, say, an application to that cluster. You need to configure that into a firewall. Maybe configure it into a load balancer. Maybe register it with a service management system. That, all those calls, they come out through policy from ACM over into Ansible to take advantage of the wealth of playbooks that are available in Ansible to perform those operations. Whether it's security, network, service management, storage, et cetera. >> Real quick follow-up for you is, how has bringing your ACM team and product into Red Hat changed the scope and approach of what you're trying to do? >> Yeah, well, let me say first of all it's been a great experience bringing the team into Red Hat. The environment, the open culture, it's really been invigorating for the whole team. Also, getting much, much closer into the open communities and open sourcing ACM and doing development in the open has really brought us closer really to users, the ecosystem, the communities, accelerating our delivery quality, as well as really getting much more closer insights, getting insights into what's happening in the community, what's happening with the users. So it's really, it's been a great experience all the way around. >> Joe and Tom, quick comment, what do you think people should pay attention to this year at AnsibleFest 2020? What's the big story? Obviously we're in a pandemic. We're going to come out of the pandemic. People want to have a growth strategy that has the right projects on the right rails. They want to either maybe downplay some of the projects that maybe not be a fit, that were exposed during the pandemic. Best practices that are emerging, shifting left for security is one. You're seeing remote workers. People have kind of had a wake-up call on cloud native being relevant for the modern app. Now they're running as fast as they can to build the infrastructure, and guess what? People are not actually in the workplaces. The workforce, the workplace has all changed. Can you guys share your expertise over the years on what is the best practice and approach to take? Because the clock's ticking. >> Yeah, from my perspective and from an Ansible perspective here, we had always been about kind of automate everything, right? Automate every task that is automatable, right? A repeatable task, automate it. Repeatable task, automate it. And over the past couple of years we've really been focused on automation across teams by using Ansible content, the actual automation code, if you will, itself to bring teams together and to cross teams and cross functions. So not just focused on what a network operations person or a network engineer needs to do in their day-to-day job, but connect that to what a security operations person is doing day-to-day in their job in terms of threat detection and intrusion response, or intrusion detection and threat response, and connecting those two teams together via automation to make both of them more responsive and more effective. So we've been on this bandwagon for the past couple of years around Ansible content, and now Ansible collections and Automation Hub, to try and accelerate the way these teams can collaborate together. The pandemic and the pressures that put on the system with remote users and having to do things in a different way only exacerbated, it only kind of enhanced the requirement for that collaboration, that automation across teams. So in a lot of ways, the past six, seven months, both for our Ansible business as well as for the way our customers have been using the technology, has really been an accelerator for that kind of cross-team collaboration, our subscription business, and our Ansible consumption. >> Yeah, well, I said it last year in-person when we were in Atlanta for AnsibleFest 2019, a platform approach is a great way to go. You start out as a tool, you become a platform. You guys are doin' the work over there. I really appreciate it and I want to call that out 'cause I think it's worth calling out. Joe, cloud platforms. Cloud is certainly an enabler. Red Hat and OpenShift has been a great success and can, only has got more work to do. People still got to build out these platforms, and you're seeing private cloud not going away. I mean, we just had a conversation at OpenStack and you guys got customers with a lot of private cloud everywhere. (laughs) So you got private, you got hybrid, you got multi, and you got public. It's pretty crazy. What's your thoughts on what people should take away from AnsibleFest and then going forward post-pandemic? >> Yeah, so, first Tom hit on a number of key points there, right? COVID-19 and everything going on in the world has really just accelerated a lot of these transformations that were already in the works at many of our enterprise customer accounts, right? And now when we're all working remotely, we're all meeting virtually, we're educating our children remotely, it just exacerbates the need to scale our networks, to extend security out to remote workforces, and to do all of these things at much larger scales than we ever envisioned before, and you can't do that without automation. And I would argue, without taking advantage of some of these modern cloud native platforms and cloud native development approaches. And we always say Red Hat's been a big proponent of hybrid cloud, of our open hybrid cloud strategy. We've been talking about that for years, and what we always say is even if that's a strategy that you aren't specifically looking for, it's something that, everybody ends up there, right? Because nobody's running everything in the data center anymore, but as they move out to public cloud they're not completely shutting those data centers off either. As they expand their consumption of public cloud, they tend to start exploring multi-cloud strategies, and now that hybrid cloud is extending out to the edge. So the hybrid cloud is sort of where everybody is, right? And the ability to sort of manage consistently, to run consistently across all those environments, to be able to secure all those environments and scale those environments, and that's what we're all about here at Red Hat and that's sort of the key to our open hybrid cloud strategy and what we're really trying to do with our entire portfolio. >> Awesome, David, final word. We're in a systems world now. The cloud is one big distributed computer. We got the edge, we heard that. Developers just want to code, they want infrastructure as code, you guys got to help 'em get there. What's your take on the importance of AnsibleFest and this systems world we live in? >> Well, there's probably not a more critical time. We've all been saying this and seeing this the last 10 months now. The transformation digitally that's been going on for years, the development transformations, it's all hit a fever pitch. It's been accelerated through COVID. In particular, how quickly can I adjust to a digital transformation? How quickly can I adjust my business processes? How quickly can I really become a very agile DevOps SRE organization? That is so critical. So at AnsibleFest what we're doing is bringing together platforms with automation with the ability to manage it at scale with security. That's what's going on from Red Hat in a open environment, open world, with communities and huge ecosystems. That, to me, is the critical rallying points, and really necessary to drive this accelerated transformation. >> Yeah, and again, open source continues to power it. One thing I'm impressed with is this concept of content, not content as in a video, but content as code. It's collaboration. It's what people are sharing their playbooks and they're sharing their, are opening things up. I think there's going to be a whole 'nother level of developer collaboration that's going to emerge and you guys are on the front end of all of this. I think it's going to be pretty powerful. I don't think yet clearly understood yet by most folks, but when you start seeing the automation benefits, Tom, I'm sure your team will be like, "Yeah, see, automation platform." Thank you so much for coming on, appreciate it. >> Thank you. >> Thanks a lot. >> Thanks. >> I'm John Furrier with theCUBE, hosting theCUBE virtual for AnsibleFest 2020 virtual. Thanks for watching. (relaxing music)

>> Narrator: From around the globe it's "TheCUBE" presenting accelerating automation with DevNet brought to you by Cisco. >> Hello and welcome back to theCUBE's coverage theCUBE virtual's coverage of DevNet Create Virtual, we're not face to face, theCUBE's been there with DevNet and DevNet Create, since the beginning DevNet Create was really a part of the DevNet community looking out at the external market outside of Cisco which essentially is the cloud native world which is going mainstream. We've got a great guest here who's been on theCUBE many times, we've been talking to them, recently acquired by Cisco ThousandEyes we have Joe Vaccaro with us Vice President of Product. Joe, welcome to theCUBE. Thanks for coming on. >> Great and thanks for having me. >> You have the keys to the kingdom you're the Vice President of the Product which means you get to look inside and you get to look outside figure it all out make everything run on ThousandEyes, You guys have been running common language across multiple layers of network intelligence, external services. This is the heart of what we're seeing in innovation with multi-cloud microservices, cloud-native. This is really a hard area, it's converging multiple theaters and technology, a super important I want to get into that with you but first ThousandEyes is recently acquired by Cisco big acquisition, super important. The new CEO of Cisco, very clear API everything we're seeing that come out. That's a big theme at DevNet Create. The ecosystem of Cisco is going outside their own their walls, outside of the Cisco network operators, network engineers. We're talking to developers, talking programmability. This is the big theme. What's it like at Cisco? Tell us as the COVID hits you get acquired by Cisco. Tell us what's happening. >> Yeah, surely been an exciting six months for a ThousandEyes and the entire team and our customers as we all kind of shifted to the new normal of working from home. And I think that change alone really kind of amplified even some of the fundamental beliefs that we have as a company that you know cloud is becoming the new data center or customers that internet has become the new network and the new enterprise network backbone. And SaaS has really become the new application stack. And as you think about these last six months those fundamental truths have never been more evident as we rely upon the cloud to be able to work as we rely upon our own home networks and the internet in order to be productive. And as we access more sized applications on a daily basis. And as you think about those fundamental truths what's common across all of them is that you rely upon them now more than ever not only to run your business but to enable your employees to be productive but you don't own them. And if you don't own them then you lack the ability in a traditional way to be able to understand that digital experience. And I think that's ultimately what ThousandEyes is trying to solve for. And I think it's really being amplified in really these last six months. >> Talk about the COVID dynamic because I think it highlighted and certainly accelerated digital transformation, but specifically exposes opportunities, challenges, weaknesses. I've talked to many CXOs, CSOs, chief security is huge. Talk track we'll get to in a second. But it exposes what's worth doubling down on what to abandon from a project standpoint as people start to look at their priorities and on hey, we going to have a connected experience. We going to have security. People are working at home. No one has VPNs at home VPNs are passe, maybe it's SD-WAN maybe it's something else, they're on a backbone, they're connecting to the internet. A lot of different diversity in connections. At the same time, you got a ton of modern apps running for these networks. This is a huge issue, COVID is exposed us at scale. What's your view on this? And what is ThousandEyes thinking about this? >> If you think about the kind of legacy application delivery it went from largely users internet office connected over say a dedicated corporate network largely to traditional say internal hosted applications. And that was a fairly simple connectivity bath. And as you mentioned, we've seen amplifications in terms of the diversity from the users. So users are not in the office. Now they're connected in distributed disparate locations that are dynamically changing. And you think that how they're getting to that application they're going across a really complex service chain of different network services that are working together across as public internet backbone will totally to land them on an application. And then those applications themselves are becoming now as you mentioned distributed largely based upon a microservices architecture and increasing their own dependence upon third party sample size applications to fulfill say key functions of that application. Those three things together, ultimately are creating that level of complex service chain. It really makes it difficult to understand the digital experience and ultimately the IT organization is really chartered with not just delivering the infrastructure but delivering the right experience. And yet then have a way to be able to see to gain that visibility that experience to measure it and understand and to provide that intelligence and then ultimately to act on it to be able to ensure that your employees as well as your customers are getting the right overall approach to being able to elaborate those assets. >> It's funny you know I was getting to some of these high scale environments a lot of these concepts are converging. We had terms like automation, self healing networks. You mentioned microservices earlier, you earlier mentioned the clouds of the new data center or when's the new land. Have you ever look at it, it's a whole different architecture. So I want to get your thoughts on the automation piece of networking and internet outages for instance. Because there's so many outages going up and down it is like catching looking for a needle in a haystack, right? So we've had this conversation with you guys on theCUBE before. How does automation occur when you guys look at those kinds of things? What's important to look at? Can you comment on and react to the internet outages and how you find resolve those? >> Yeah, it was really great and as you mentioned automation really in a place that a key when you think about the just a broad problem that IT is trying to drive you know from our lens we look at it in really three ways. First off is you have to be able to gain the level of visibility from where it matters and be able to test and be able to provide that level of active measurements across the type of ways you want to be able to inspect the network. But then also from the right vantage points you want to inspect them. But what we talked about RightSide Data alone doesn't solve that problem as you mentioned that needle in the haystack. Data just provides the raw metrics that are streaming across the screen you have to then enable that data to provide meeting. You need to enable that data to become intelligent. And that intelligence comes through the automation of being able to process that data very quickly to allow you to be able to see the unseen. To allow you to be able to quickly understand the issues that are happening across this digital supply chain to identify issues that are even happening outside of your own control across the public internet. And then the last step of automation really comes in the form of the action, right? How do you enable that intelligence to be put to use? How do you enable that intelligence to then drive across the rest of your IT workflow as well as to be able to be used as a signaling engine to be able to then make the fundamental changes back the network fabric whether that is dressing your modifying your BGP peering that we see happen within our customers using ThousandEyes data built around major internet outages that we've seen over the past six months or to be able to then use that data to be able to optimize the ultimate experience that they're delivering to both our customers as well as our employees. >> Classic policy-based activities taken to a whole another level. I going to get your thoughts on the employees working at home. Okay, because most IT people like Oh yeah, we're going to forecast in cases of disruption or a hurricane or a flood or hurricane sandy but now with COVID everyone's working at home. So who would have forecasted a hundred percent work from home which puts a lot of pressure on everything. So I got to ask you now that employees are working at home how do you tie network visibility to the actual user experience? >> Yeah, that's a great question. As you we saw within our own customer base when COVID hit and we saw this rise of work from home IT teams were really scrambling and said, okay I have to light up this say VPN infrastructure or I need to now be able to support my users in a work from home situation where I don't control the corporate network. In essence now you have essentially thousands. Every employee is acting across their own corporate network. And people were then using ThousandEyes in different ways to be able to monitor their CPP and infrastructure across back into the corporate network as well as in using our ThousandEyes end point agents that runs on a local user's laptop or machine in their home to help you to be able to gain that visibility down to that last mile of connectivity. Because when a user calls up support and says I'm having trouble say accessing my application whether that's Salesforce or something else what ultimately might be causing that issue might not necessarily be a Salesforce issue, right? It could be the device in the device performance in terms of CPU memory utilization. It could be the WiFi and the signal quality within your WiFi network. It could be your access point. It could be your local home router. It can be your local ISP. It could be the path that you're taking ultimately to your corporate network or that application. There's so many places that can go wrong that are now difficult to be able to see unless you have the ability to see comprehensively from the user to the application and to be able to understand that full end to end path. >> IT teams have also been disrupted. They've been on offsite prop off property as well but you've got the Cloud. How has your technology help the IT teams? Can you give some examples there? >> Yeah great way is how people use ThousandEyes as part of that data sharing ecosystem again that notion of how do you go from visibility to intelligence action. And where in the past you might be able as an IT administrator to walk over to their network team say hey, can you take a look at what I'm seeing? Now that's no longer available. So how do you be able to work efficiently as an IT organization? We think a ThousandEyes and how our customers are using a ThousandEyes becomes a common operating language. It allows them to be able to analyze across from the application down into the underlying infrastructure through those different layers of the network. What's happening and where do you need to focus your attention? And then furthermore within ThousandEyes in terms of enabling that data sharing ecosystem leveraging our share link capability really gives them the ability to say you know what here's what I'm seeing and be able to send that to anybody within the IT organization. But it goes even further and many times in recent times as well as over the course of people using ThousandEyes. They take those share links that actually send them to their external providers. Because they're not just looking to resolve issues within their own IT organization they're having worked collaboratively with the different ESPs that they're pairing with, with their cloud providers that they're leveraging or the SaaS applications that are part of that core dependency of how they deliver their experience. >> So I got to ask you the question what you think about levels of visibility and making the lives easier for IT teams, you see a lot of benefits with ThousandEyes. You pointed out a few of them. So I got to ask you the question. So if I'm an IT person in the trenches are you guys have an aspirin or a vitamin or both? Can you give an example because there's a lot of pain point out there. So yeah, give me a couple Advils and aspirins but also >> Yeah. you're an enabler too. The new things are evolving. You pointed out some use case. Talk about the difference between where you're helping people pain points and also enabling them be successful for IT teams. >> Yeah, that's a great analogy you're thinking like you said, it definitely sits on both sides of that spectrum ThousandEyes is the trusted tool the source of truth for IT organizations when issues are happening as their alarm bells are ringing as they are generating the different on call to be able to jump into a war room situation. ThousandEyes is that trusted source of truth that allow them to focus to be able to resolve that issue in the heat of the moment. But ThousandEyes is also when you think about baselining your experience what's important is not understanding that experience at that moment in time but also how that's deviated over time. And so by leveraging ThousandEyes on a continuous basis it gives you that ability to see the history of that experience to understand how your network is changing cause as you mentioned networks are constantly evolving, right? The internet itself is constantly changing. It's an organic system and you need to be able to understand not only what are the metrics that are moving out of your bounds but then what is potentially the cause of that as a network has evolved. And then furthermore you can be begin to use that as you mentioned in terms of your vitamin type of an analogy you'd be able to understand the health of your system over time on a baseline basis so that you can begin to be able to ensure its success in a great way to really kind of bring that to light as people using say ThousandEyes as part of say SD-WAN roll out. Where you're looking to say benchmark and again confidence as you look to scale out either benchmarking different ISP within that I feel like connectivity where as you look to ensure a level of success with a single branch to give you that competence to then scale out to the rest of your organization. >> That's great insights classic financial model ROI you got baseline and upside, right? You got handle the baseline as you pointed out and the upside music experience connectivity, application performance which drives revenue, etc. So great point great insight Joe, thank you so much for that insight. It's got a final question for you I want to just riff a little bit with you on the industry. A lot of us have been having debates about automation. Who doesn't love automation. Automation is awesome, right? Automate things, but as the trend starts going on as everything is a service or SaaS as it's called certainly Cisco is going down that road. Talk about your view about the difference between automation and everything is a service. Because at the end of the day everything will be a service but without automation you really can't have services, right? So, automation, automation, automation great drum to bang all day long but then also you've got the same business side saying as a service pushing that into the products. Means it's not trivial. Talk about how you look at automation and everything as service and the relationship and interplay between those two concepts. >> Yeah, ultimately I think about in terms of what is the problem that the business is trying to solve and ultimately, what is the deal that they're trying to face? And in many ways right, they're being exploded with increase of data they need to be able to not only process and gather but then be able to then make use of. Then from that as we mentioned once you've processed that data and you still gather the insights from it you need to be able to then act on that data. And automation plays a key role of allowing you to be able to then put that through your workflow. Because again, as that IT experience becomes even more complex as more, more services get put into that digital supply chain. As you adopt say increased complexity within your infrastructure by moving to a multicloud architecture where you look to increase the number of say network services that you're leveraging across that digital experience. Ultimately you need with the level of automation you'd be able to see outside of your own vantage point. You need to be able to look at the problem from as a broad of a way as possible. And data and automation allows you to be able to do what is fundamentally difficult to do from a very narrow point of view in terms of the visibility you gather intelligence you generate and then ultimately how do you act on that data as quick as possible to be able to provide the value of what you're looking to solve. >> Its like a feature (laughs). It's under the hood. The feature of everything comes to the surface is automation, data, machine learning all the goodness in the software. That's really kind of what we're talking about here, isn't it? >> Hmm. >> Final question for you as we wrap up DevNet Create really again is going beyond Cisco's DevNet community going into the industry ecosystem where developers are there. These are folks that want infrastructure as code. They want network as code. So network programmability, huge topic. We've been having that conversation with Cisco and others throughout the industry for the past three years. What's your message to developers out there that are watching this who say hey, I just want to develop code. Like I want you know, you guys got that. That was nice thanks so much. You take care of that I just want to write code. What's your message to those folks out there who want to tap some of these new services these new automation, these new capabilities what's your message? >> Ultimately I think when you look at ThousandEyes from a product perspective we try to build our product in an API first model to allow you to be able to then shift left of how you think about that overall experience and from a developer standpoint what I'd say is that, while you're developing in your silo you're going to be part of a larger ultimate system. And your experience you deliver within your application is now going to be dependent upon not only the infrastructure it's running upon but the network its connected to and then ultimately the user and the sense of that user. If I leveraging a ThousandEyes and being able to then integrate ThousandEyes into how you think closely on that experience that's going to help ensure that ultimately the application experience that the developers looking to deliver meets that objective. And I think what I would say is while you need to focus on your role as a developer having the understanding of how you fit into the larger ecosystem and what the reality of how your users will access that application is critical. >> Awesome Joe, thank you so much again. Trust is everything letting people understand that what's going on underneath is going to be viable and capable. You guys got a great product and congratulations on the acquisition that Cisco made of your company. And we've been following you guys for a long time and a great technology chops, great market traction. Congratulations to everyone at ThousandEyes. Thanks for coming on sharing. >> I appreciate it thanks for having me. >> Joe Vaccaro vice president of Product here with ThousandEyes is now part of Cisco. I'm John Furrier host of theCUBE Virtual for DevNet Create Virtual. Thanks for watching. (upbeat music)

>> From around the globe it's theCUBE with digital coverage of AnsibleFest 2020, brought to you by Red Hat. >> Hi, I'm Stu Miniman and this is a preview for Red Hat's AnsibleFest 2020, second year that theCUBE's been at the event. Happy to welcome back to the program one of our CUBE alumni, Joe Fitzgerald, he's the vice president and general manager of the division that includes Ansible. Joe, thank you and welcome back to the program. >> Thanks for having me back, Stu, excited to be here. >> So Joe, you know, boy, I think since last year, you know, the overarching trend of automation adoption has only increased, of course, with conversation you and I have had back at Red Hat Summit, as well as all the conversations we're having across the industry. It's been five years now since Red Hat bought Ansible. Remember, you know, big activities at Summit and throughout the industry. A lot has changed. The players that we talked about five years ago definitely have shifted. So why don't you bring us in is to, you know, 2020 you know, the state of your Ansible business and let's give the audience a preview of what we're going to see at the show. >> Sure. So it's been an exciting five years. I can't believe how fast it flew. You know, five years ago when Red Hat acquired this little company called Ansible, they were basically, you know, selling to IT admins in a particular space around config management. They, you know, frequently got lumped in with a, you know, a couple of other companies that were in that segment. Over the past five years the stats are just amazing. Over the past four years it's been in the top 10 open source projects in the world, right? I think Kubernetes is number seven, Ansell's number nine and has been in the top 10 for past five years. The number of contributors, the number of folks with Ansible in their skills, the titles, I mean, the numbers are just amazing. And of course we've had, you know, analyst validation and thousands of customers vote with their subscriptions to Ansible. So it's an amazing five years growth. >> Yeah. Okay. Congratulations. Of course the concern always is, you know, oh, when an acquisition happens, what will happen to the culture, what will happen to the community? Red Hat, everyone knows open sources is in its DNA there. And therefore the community has flourished. I definitely see Ansible at many of the cloud and cloud native type discussions. You talked to, you mentioned Kubernetes, Joe, help draw the dots, connect the dots for us as to, you know, what should we be expecting to see when it comes to things like, you know, Kubernetes, cloud computing, edge computing and the like. >> So it's pretty interesting because, you know, OpenShift has been our flagship offering around Kubernetes at Red Hat, right? And market leader just incredible validation, right? And so, you know, automation connected up to that environment becomes really, really important because even though people are modernizing their apps and running container based apps, there's a lot of other things that those things need to be connected up to. Traditional applications, other systems of record, your CMDBs or change management, things like that. So there's a lot of automation that has to happen around, you know, building, deploying, managing container based apps in those environments. So sort of a teaser for what's coming up here is you're going to see us pushing Ansible even further into areas like Kubernetes and OpenShift at AnsibleFest. >> Yeah, Joe, when I look at the entire landscape, one of the big challenges out there is there's so many tools out there, you know, developers have all the little pieces that they're dealing with. If you talk about Kubernetes, it's "Okay, which cluster am I doing? How do we wrap our arms around managing environments?" I've talked to you about the ACM solution came out of IBM, now part of Red Hat. What I really love that the top learning I had from AnsibleFest last year is various people in the organization can get their view into really that pipeline of development from the product people through the developer. You know, we always hope that software can be a unifying, you know, tool inside an organization. And it definitely felt like Ansible's doing that. So, do we expect that when we talk about Kubernetes, that's the kind of expansion we have is that, you know, not just that I can do more as an individual person, but inside the organization, we can break through some of those silos. >> Yeah. So I think this plays to Ansible's strength. So Ansible, as I mentioned, five years ago was sort of IT admins focused on config. Over the years, we've expanded the number of domains dramatically into network storage, cloud security. We've also expanded the people who use Ansible automation. So Ansible is extremely popular with developers. It's a favorite in tool chains, right, around automation and config and things like that. So bringing together sort of the automation that crosses all those domains and the different personas that use Ansible, right, now bringing that and connecting that up to the Kubernetes environment, right, is extremely powerful in so many ways and covers a lot of the areas where the automation in those Kubernetes environments sort of ends and you have to have that connection to the other teams and to the other technologies that are outside of that to make the thing work. >> All right. So what specifically, should we be expecting to see, you know, what'll be the same, what'll be the different of the virtual environment versus what everybody's come to expect for the in person AnsibleFest? >> Well, first of all, the numbers are amazing, right? We've run a number of events over the course of the year. You know, training webinars, you know, all sorts of Ansible events. Every one of them has exceeded our expectations by a lot. AnsibleFest is no different. We're currently over 15,000 people registered for AnsibleFest. It would not surprise me to see it go much higher than that. Our last in-person Ansible event was 12,000 people. The level of interest globally, right, across personas for AnsibleFest is just amazing. So we think we're going to see a tremendous amount of interest and in typical Red Hat fashion at Fest, we're going to bring out additional Ansible capabilities around Kubernetes environment, obviously, but talking about where Ansible's going with Edge, right, and a number of areas that people are pushing out on Ansible automation. I believe Ansible's becoming sort of the de facto standard in automation, regardless of what domain, regardless of what persona. And I think AnsibleFest is going to show again why it is. >> Awesome. Well, Joe bold statement. Absolutely phenomenal to see the momentum there. I'll let you have the final word as to if they haven't already, why should people sign up and any other kind of, you know, cool customers or things that people should dive into once they have a chance to look at the agenda? >> Well, if somebody is familiar with Ansible, then they're going to love the expansion of the domains and the capabilities necessary to really expand usage of Ansible. If you're new to Ansible, Ansible, you know, if you look at the number of LinkedIn jobs that talk about Ansible, it's, you know, it's in the tens of thousands, right? Indeed top 10 skill that people are looking for in hiring. So automation is more important than ever given the sort of the world backdrop. So I would encourage people to really look at Ansible, right, to expand the professional, you know, skills and things like that. And people that are already in the know that are using Ansible, wait till you see how you can use it for Kubernetes Edge and really expand it beyond where you are today with it. >> All right. Well, Joe Fitzgerald, thank you so much. And to our audience, you know, go check out the website, really easy to find, register online. theCUBE will have a full lineup. John Furrier is going to be the lead host for the event in our second year of coverage. Joe, have a great event and as always, thanks for having theCUBE. >> Thanks, Stu. Appreciate it. >> All right, check out theCUBE.net for all the upcoming events, as well as you can look at the back catalog. Of course, we've done seven years of Red Hat Summit as well as the AnsibleFest last year. So lots of good customer studies, as well as deep dives on all the product. Thank you for joining. I'm Stu Miniman. Thanks as always for watching. (upbeat music)

>>from around the globe. >>It's the Cube with >>coverage of Coop Khan and Cloud Native Con Europe 2020 Virtual brought to you by Red Hat Cloud, >>Native Computing Foundation and >>Ecosystem Partners. Hi. And welcome back. I'm stew Minuteman. And this is the cube coverage of que con cognitive con 2020. The Europe virtual addition Course kubernetes won the container wars as we went from managing a few containers that managing clusters, too many customers managing multiple clusters and that and get more complicated. So to help understand those challenges and how solutions are being put out to solve them, having a welcome back to the from one of our cube alumni do if it Gerald is the vice president and general manager of the management business unit at Red Hat. Joe, good to see you again. Thanks so much for joining us >>two. Thanks for having me back. >>All right, so at Red Hat Summit, one of the interesting conversation do you and I add, was talking about advanced cluster management or a CME course. That was some people and some technology that came over to Red hat from IBM post acquisition. So it was tech preview give us the update. What's the news? And, you know, just level set for the audience. You know what cluster management is? >>Sure, So advanced Cluster manager or a CMS, We actually falling, basically, is a way to manage multiple clusters. Ross, even different environments, right? As people have adopted communities and you know, we have at several 1000 customers running open shift on their starting to push it in some very, very big ways. And so what they run into is a stay scale. They need better ways to manage. It would make those environments, and a CMS is a huge way to help manage those environments. It was early availability back at Summit end of April, and in just a few months now it's generally available. We're super excited about that. >>Well, that that Congratulations on moving that from technical preview to general availability so fast. What can you tell us? How many customers have you had used this? What have you learned in talking to them about this solution? >>So, first of all, we're really pleasantly surprised by the amount of people that were interested in the tech preview. Integrity is not a product that's ready to use in production yet so a lot of times accounts are not interested in. They want to wait for the production version. We had over 100 customers in our tech review across. Not only geography is all over the world Asia, America, Europe, us across all different verticals. There's a tremendous amount of interest in it. I think that just shows you know, how applicable it is to these environments of people trying to manage. So tremendous had update. We got great feedback from that. And in just a few months, we incorporate that feedback into the now generally available product. So great uptick during the tech created >>Excellent Bring assigned side a little bit, you know, When would I use this solution? If I just have a single cluster, Does it make sense for May eyes? Is it only for multi clusters? You know, what's the applicability of the offering? Yes, sir, even for >>single clusters that the things that ACM really does fall into three major areas right allows closer lifecycle management. Of course, that would mean that you have more than one cluster ondas people grow. They do for a number of reasons. Also, policy based management the ability to enforced and fig policies and enforce compliance across even your single cluster to make sure that stays perfect in terms of settings and configuration and things like that. Any other application. Lifecycle management The ability to deploy applications in more advanced way, even if you're on a single cluster, gets even better for multi cluster. But you can deploy your APS to just the clusters that are tagged a certainly, but lots of capabilities, even for application, even a single cluster. So we find even people that are running a single cluster need it askew, deployed more more clusters. You're definitely >>that's great. Any you mentioned you had feedback from customers. What are the things that I guess would be the biggest pain points that this solves for them that they were struggling with in the past? Well, >>first of being able to sort of Federated Management multiple clusters, right, as opposed to having to manage each cluster individually, but the ability to do policy based configuration management to just express the way you want things to stay, have them stay that way to adopt a more of a getups ethnology in terms of how they're managing their your open ships environments. There's lots more feedback, but those were some of the ones that seem to be fairly common, repetitive across the country. >>Yeah, and you know, Joe, you've also gotten automation in the management suite. How do I think about this? How does this fit into the broader management automation that customers were using? Well, >>I think as people in employees environments. And it was a long conversation about platform right? But there's a lot of things that have to go with the platform and red hats actually in very good about that, in terms of providing all the things you necessary that you would find necessary to make the five form successful in your environment. Right? So I was seen by four. We need storage, then development environments management, the automation ability to train on it. We have our open innovation labs. There's lots of things that are beyond the platform that people acquire in order to be successful. In the case of management automation, ACM was a huge advancement. Terms had managed these environments, but we're not done. We're gonna continue to ADM or automation integration with things like answerable mawr, integration with observe ability and analytics so far from done. But we want to make sure that open ship stays the best managed environment that's out there. I also do want to make a call out to the fact that you know, this team has been working on this technology for the past couple of years. And so, you know, it's only been a red hat for five months. This technology is actually very mature, but it is quite an accomplishment for any company to take a new team in a new technology. And in five months, do what Red Hat does to it in terms of making it consumable for the enterprise. So then kudos continue. Really not >>well. And I know a piece of that is, you know, moving that along to be open source. So, you know, where are we with the solution? Now that is be a How does that fit in tow being open? Source. >>Eso supports that are open source Already. When the process of open sourcing the rest of it, as you've seen over time read, it has a perfect record here of acquiring technologies that were either completely closed Source Open core in some cases where part it was open. It was closed. But that was the case with Ansell a few years ago. But basically our strategy is everything has to be open source. That takes time in the process of going through all of the processes necessary to open source parts of ACM on. We think that will find lots of interest in the community around the different projects inside of >>Yeah. How about what? One of the bigger concerns talking to customers in general about kubernetes even Mawr in 2020 is. What about security? How does a CME help customers make sure that their environment to secure? >>Yeah, so you know, configuration policies and forcing you can actually sent with ACM that you want things to be a certain way that somebody changes them that automatically either warn you about them or enforcement would set them back. So it's got some very strong security chops in terms of keeping the configurations just the way you want. That gets harder as you get more and more clusters. Imagine trying to keep everything but the same levels, settings, software, all the parts and pieces so affected you have ACM that can do this across any and all of your clusters really took the burden off people trying to maintain secure environments, >>okay, and so generally available. Now, anything you can share about how this solution is priced, how it fits in tow. The broader open shift offerings, >>Yes. Oh, so it's an add on for open shift is priced very similarly to open shift in terms of the, you know, core pricing. One thing I do want to mention about ACM, which maybe doesn't come out just by a description product is the fact that a scene was built from scratch for communities, environments and optimize for open shift. We're seeing a lot of competition out there that's taking products that were built for other environments, trying to sort of been member coerce them into managing kubernetes environments. We don't think people are going to be successful at that. Haven't been successful to date. So one things that we find as sort of a competitive differentiator for ACM and market is the fact that it was built from scratch designed for communities environments. So it is really well designed for the environment it's trying to manage, and we think that's gonna keep your competitive edge? >>Well, always. Joe. When you have a new architecture, you advantage of things. Any examples that you have is what, what a new architecture like this can do that that an older architecture might struggle with or not believe. Be able to do even though when you look at the product sheet, the words sound similar. But when you get underneath the covers, it's just not a good architect well fit. >>Yeah, so it's very similar sort of the shift from physical to virtual. You can't have a paradigm shift in the infrastructure and not have a sort of a corresponding paradigm shift in management tool. So the way you monitor these environments, where you secure them the way they scale and expand, we do resource management, security. All those things are vastly different in this environment compared to, let's say, a virtual more physical environment. So this has improved many times in the past. You know, paradigm shift in the infrastructure or the application environment will drive a commensurate paradigm shift in management. That's what you're seeing here. So that's why we thought it was super important to have management that was built for these environments. by design. So it's not trying to do sort of unnatural things north manage the environment. >>Yeah, I wondered. I love to hear just a little bit your philosophy as to what's needed in this space. You know, I look back to previous generations, look at virtualization. You know, Microsoft did very well at managing their environment, the M where did the same for their environments. But, you know, we've had generations of times where solutions have tried to be management of everything, and that could be challenging. So, you know, what's Red Hat in a CM's position and what do we need in the community space, you know, today and for the next couple of years. >>So kubernetes itself is the automation platform you talked about, you know, early on in the second. So you know, Cooper navies itself provides, you know, a lot of automation around container management. What a CME does is build a top it out and then capture, you know, data and events and configuration items in the environment and then allows you to define policies. People want to move away from manual processes. Certainly, but they wanna be able to get to a more state full expression of the way things should be. You want to be able to use more about, you know, sort of get up, you know, kind of philosophy where they say, this is how I want things today. Check the version in, keep it at that level. If it changes, put it back. Tell me about it. But sort of the era of chasing. You know, management with people is changing. You're seeing a huge premium now on probation. So automation at all levels. And I think this is where a cm's automation on top of open shift automation on down the road, combined with things like ansell, will provide the most automated environment you can have for these container platforms. Um, so it's definitely changing your seeing observe ability, ai ops getups type of philosophies Coming in these air very different manager in the past helps you seeing innovation across the whole management landscape in the communities environment because they are so different. The physics of them are different than the previous environments. We think with ACM answerable or insights product and some over analytics that we've got the right thing for this environment >>and can give us a little bit of a look forward, you know? How often should we expect to see updates on this? Of course. You mentioned getting feedback from the community from the technical preview to G A. So give us a little bit. Look, you know, what should we be expecting to see from a CME down the right the So >>the ACM team is far from done, right? So they're going to continue to rev, you know, just like we read open shift, that very, very fast base we're gonna be reading ACM and fast face. Also, you see a lot of integration between ACM. A lot of the partners were already working with in the application monitoring space and the analytics space security automation I would expect to see in the uncivil fest time frame, which is mid October, will cease, um, integration with danceable on ACM around things. That insult does very well combined with what ACM does. A sand will continue to push out on Mawr cluster management, more policy based management and certainly advancing the application life cycles that people are very interested in ruined faster. They want to move faster with a higher degree of certainty in their application. Employments on ACM is right there. >>It just final question for you, Joe, is, you know, just in the broader space, looking at management in this kind of cube con cloud, native con ecosystem final words, you want customers to understand where we are today and where we need to go down the road. >>So I think the you know, the market and industry has decided communities is the platform of future right? And certainly we were one of the earliest to invest in container management platforms with open shift were one of the first to invest in communities. We have thousands of customers running open shift back Russell Industries on geography is so we bet on that a long time ago. Now we're betting on the management automation of those environments and bringing them to scale. And the other thing I think that redhead is unique on is that we think that people gonna want to run their kubernetes environments across all different kinds of environments, whether it's on premise visible in virtual multiple public clouds, where we have offerings as well as at the edge. Right. So this is gonna be an environment that's going to be very, very ubiquitous. Pervasive, deported scale. And so the management of a nation has become a necessity. And so but had investing in the right areas to make sure that enterprises continues communities particularly open shift in all the environments that they want at the scale. >>All right. Excellent. Well, Joe, I know we'll be catching up with you and your team for answerable fest. Ah, coming in the fall. Thanks so much for the update. Congratulations to you in the team on the rapid progression of ACM now being G A. >>Thanks to appreciate it, we'll see you soon. >>All right, Stay tuned for more coverage from que con club native con 2020 in Europe, the virtual addition on still minimum and thanks, as always, for watching the Cube.