>>Mhm. Hey, welcome to the cubes coverage of HP discover 2021. I'm lisa martin. I have two guests with me here today. We're gonna be talking to the walt. Disney company. Jason Abrahamson is here. The Director of infrastructure engineering. Jason. Welcome to the program. >>Hi, how you doing >>doing well. And James Irvine is here as well. Account chief technologist at H P. D. James. Welcome to the program. >>Yeah, I like to thank you. >>Okay, so we're gonna be talking about all things the HP supporting Disney relationship. But you know, things have been changing so much in technology, things have been very different for technologists in the last few years, Jason talked to us about how Disney has adapted as business needs have evolved. >>Uh you know, I think not just Disney but in general, as we've we've had to evolve, evolve as technologists. Right. And one of the ways we've done that is to focus a lot on automation and self service, enabling developers to move faster to meet the shift in business demand, business moves at the speed of light. Uh anybody that's been this business long enough knows. Uh There were years ago you could have email servers down for three hours and nobody would notice. Now if email went down for more than, you know, 35 seconds, everybody notices. Right? So in order to meet the change in demand, we've had to focus heavily on automation and self service, which has been a key strategy, is keep a key driver for as as part of private cloud. >>So Jason with infrastructure as such, a large part of your responsibilities and your job title, how has Disney been thinking about private cloud in the last few years? >>So I would say that we were probably one of the uh I don't wanna see bleeding edge, but certainly out in front when it came to private cloud, we had embarked on a cloud first strategy overall across the enterprise, uh, the goal there was to figure out how we could do more with less and be more agile and be able to flex for application developers and meet our shifts in demand. However, there are, you know, systems that for whatever reasons, business purpose or otherwise need to either span hybrid cloud or multi cloud or stay on premise. So in order to uh get a cloud like environment for application developers and whatnot, we decided to build out a robust, private cloud environment that allowed all of our application developers to be able to just bring their code or get a server and try to get as much of the public cloud functionality on premise as we possibly could >>James. Let's bring you into the conversation, talk to us about the H P E WAlt Disney company relationship and how HP is supporting walt. Disney. >>Yeah, HP and Disney have had a long standing relationship dating all the way back to HP and Disney as far as the audio oscillators concerned. So we've had an extraordinarily long history, the technology and co innovation partnership that we've worked on together through the years. And as Jason mentioned, you know, the journey around private cloud and working together in that technology relationship is just has been fantastic. And we've supported them with all the innovation and technology is needed for them to meet their bulls. >>Excellent. All right, Jason, let's go back to you. I want to dig into this private cloud strategy a little bit more. You mentioned this a minute ago, but as we look at and here so many discussions and strategies revolving around public, multi cloud, Why is private cloud so important to Disney? >>Well, we have a tremendous amount of applications. We are application portfolio as massive as you can imagine. And we find ourselves in unique situations because of all of the different uh, business challenges that we have that are unique to Disney, that we have to develop applications from the ground up far more often than we probably like to admit. So, uh, private cloud allows us to uh take advantage of the public cloud, like services and technology scalability and flexibility and agility, right? And bring those on premise and be close to the business where it's absolutely critical to our business. I don't want to comment on what specific, because their services that we have to run close to the business. But you can imagine with the uh, expansive footprint of our business and how we have to interact with guests, um whether it's from a movie or at a theme park, we do have to have some services that are close to our business. And so by having private cloud, we complement our public cloud strategy uh, and and allow us to keep those most critical services very close to the business. >>Got it. You just mentioned a number of the elements of Disney. There's been a lot going on, so much going on. It's actually kind of easy to forget how new Disney Plus is, but sitting in the center of a company that's doing so much digitally, how does the shared services play a part in the overall digital transformation of the business? >>Uh, that's a great question. So obviously technology is key to our business. If you look at all the different lines of business we have and you look at all the different technology that we have. It's absolutely critical in order for us to continue to invest in technology to meet all of our business demands. Were shared services comes in is we enable the business to focus on what is critical to their business. Right? We allow resorts and even the immediate media partners to just focus solely on the technology that is critical to driving those businesses to enabling the guest experience and keeping it great. We are focused on uh everything else that is not critical for their business. The underlying infrastructure, the underpinning infrastructure right? Such as the global network, global servers, emails and so on and so forth. So it's a great compliment where it freezes the business up to focus on what's really critical for them and we can get economies of scale and synergy across our entire enterprise by delivering core services at a much more efficient costs throughout the company >>and James. I want to ask you a question. You've been working as a with the walt Disney company for a long time. We've we've seen the evolution of h p e and we've seen the evolution of Disney. Can we ask you anything about kind of, give us your perspectives on how both companies have evolved in this relationship together? >>I would say that it's been it's been a great relationship. I would say that the uh, we have continued to lean on HP from an investment perspective for our servers in certain areas storage, but mostly servers, what are the big investments we've made recently was hB synergy which is composed all infrastructure, which has allowed us to continue to uh invest in our automation strategy and allows us deliver physical servers much, much faster James. Did you want to add anything there? >>Yeah, of course, Jason. Uh it's been great to partner with with Jason and the team walt. Disney company in particular and and through this experience of them trying to achieve their private cloud goals, we've been able to bring the right technology, the right set of services to achieve these technology outcomes that they've been after and the use of automation to improve life cycle management day to operations, all the goals and aspirations that they need to really automate infrastructure and make it intelligent and started achieving the goal of the intelligent data center. So it's it's been a great technology partners of relationship we've had there, >>Jason back to you. Let's, we've talked about Disney's private cloud strategy. I'm gonna talk a little bit more about how that integrates with the rest of Disney's cloud strategy. What can you share with us? >>Well, uh >>like, like anything you want the right tool for the right job And uh, certainly the multi cloud strategy in the public cloud strategy is a huge part of our overall strategic roadmap. Where again, we use the private cloud is to complement that for applications that need to either span or stay on premise. You know, one of the things that we're just getting into now is hybrid cloud while you have application teams that are like, hey, we really just need to focus on premises where we need to be close to the business, but we have workloads that need to burst to the public cloud or need to scale out to the public cloud, uh, and you really take advantage of that. So again, we don't look at it as it used to be, not just within Disney, but in general, and most cloud strategies, it was, it's kind of like an either or now we look at it as the right tool for the right job. What's the right fit for your application? And as we continue to look at how the application stack modernizes, right used to be. How do you get servers faster? Well, now I don't want to serve. I want a container. Now. It's, I just want to bring my coat and I don't even know if I need a container. Right. The application developers really want sort of this, They really want to just focus on application development and they want to focus more on what makes their applications great. Right. We want to focus more on commoditization and blurring the lines between public and private. Really, where does the workload run best? Where is it most efficient? And where is the best for the business? And so when we look at how we build out our private cloud environment, it was really to complement our existing public cloud strategy. >>Let's talk about people now, Jason for a second. I know, I love that. Disney calls there folks, Cast members, I see the pin on your lapel there. How are the cast members at the center of this technology strategy and how does the private cloud strategy play into that? >>Well, it's one of those things where our cast members are the most important aspect of our, of our brand. If you, if you were to look at what is r one of the most valuable asset, it would certainly be our cast members right there. The front line, whether it's helping a guest, whether it's working on a movie and our overall technology strategy is all about enabling cast members to do their job as most efficiently and effectively as possible. Um, uh, when it comes to how private cloud fits into that, it's again creating an environment where the application developers and our business partners can accelerate their application growth and the delivery of their services to support our back of house operations for our cast members. So that way it doesn't impact the guest experience. There's nothing more frustrating for a cast member is when they're impeded or have issues trying to get to a resource or unable to efficiently do their job. And so by having the private cloud, by having access to resources on premise. At times it gives them the ability to deliver those and consume those applications even faster, >>which I'm sure the guests love. One of the things that you mentioned, Jason and I want to James at your opinion on this too. It's a, it's a statement that we hear very often you need to do more with less in that situation. How does Disney navigate that? And a strategy that is cost effective while you're growing your public, your private cloud strategy? >>Uh huh automation, Right? Automate automation and self service. It really it's always comes back to, I know it's a buzzword, I know people go automate this, automate that you know, what are you automating if you look at just the investments we're making right now in the HP synergy line and having proposal infrastructure combined with pockets of three tier architecture as well as hyper converge. You are we're bringing a delivery model to application teams and business teams that they haven't that is just like public cloud, Right? But that they haven't seen before. So in order to manage massive scale, uh you you need to automate more and you need to automate more in order to make sure that you have self healing, right? So you can see you can look at things and understand things and see where you're having problems and try to predict them before they happen and increase your uptime and availability. I mean it all comes back to again, automation automation, automation uh >>James. Do you have the similar opinion when you talk with customers similar to the walt Disney company that are told we've got to do more but we've got less to work with is automation one of your key go to recommendations. >>Automation is at the center of everything that we're trying to achieve today, both on premise and in the public cloud. And hyper automation is really kind of where everybody is driving to the ability to be incredibly they are incredibly efficient um using infrastructure as code api driven and using all the tools to really automate that and make the seamless delivery of new products and services just that much quicker. And, and we've been focused on that, both not only from a technology and infrastructure standpoint, but also from a consulting and delivery standpoint. So we're able to really kind of meat all the different needs as it relates to automation, both in a private cloud, hybrid cloud or multi cloud scenario with all of the partnerships that we have across all the hyper scale hours. >>James sticking with you with that. Looking through that consultant lens, I want to get some thought leadership from you. What are some of the principles that you'd recommend for businesses that really are working hard to make their private cloud investment work as efficiently as possible for them? >>A lot of that comes down >>to >>consulting and understanding. So really kind of driving to what we referred to as the right mix, what is that right mix of hybrid cloud, private cloud um applications that have gravity that need to remain on premise and there's just no reason to move them. So, working with somebody and partnering with somebody that has the ability to be able to advise and consult in that capacity across the continuum of private public as well as Edge um is vitally important for people to consider as a part of their strategy. >>Jason Edge is absolutely in critical we're hearing about it more and more, especially as so much more data and machine data is generated there. I want to get your advice for the audience the same question that I asked James, what principles would you recommend for making the private cloud investment work as hard as possible? As efficiently as possible. >>I would say that, you know, it's gonna be a unique journey for every single company, but the number one advice is remember, right tool for the right job. Right, What is your application stack? What are the types of in that? What is the type of needs of the application owners? And when you start thinking about it, you start dissecting, Are you going to be investing more microservices? Can you go with more of a serverless, container based type of environment? Are you using shrink wrap software? You're gonna need more. I as right. It all comes down to the right tool for the right job. My father was an auto mechanic and I remember as a kid, he had 8000 tools and they say no, dad, why do you have five screwdrivers? To me? They all look the same right in the heart of mechanic because no, no, no, Jason you don't understand. It's the right tool for the right job. That was always his mantra. That would be my advice. >>I like that. I think my dad would have said the same thing, right tool for the right job. Absolutely critically important. So when we think about Disney, we know, generate a ton of data, how does the growth of the private cloud, Jason support that massive data growth? >>Well, as you can imagine, we have ebbs and flows in our data. There's times where we're taking a tremendous amount of data in and there's times where we're purging a tremendous amount of data for various different reasons. Right? So one of the beauties of private cloud and how it complements the public cloud is when you go to you think about data ingestion, right? And then storage and being able to efficiently can get it on premise and what not having the private cloud there to do those types of things to use more of those B I type of work clothes there, you're just Truncheon a bunch of data. Uh it's really nice to have the private cloud. So that way the application, he can add nodes at collectors of, you know, other other log aggregation type tools, right? Whatever the tool is, you know, being able to have the flexibility to add notes very quickly, just like they can in public cloud, public cloud but have it on premise so that you can do cost control and get the data in a more timely, more efficient manner. Again though, it comes down to the type of workload and what was best for that business. I would I would be remiss if I tried to sit here and tell you that all of our big data stuff were to only reside or only use on premise technology is of course it spans like I said, we've got hybrid cloud and multi cloud, so >>it kind of goes with the right tool for the right job. One more question for both of you and I want to go back to that thought leadership angle Jason when you are talking with peers of yours, what do you recommend that technology leaders look for when they're going to be partnering with a company on any type of cloud, initiative management or implementation project? >>I was a understand you understand the problem, trying to solve, understand the technology that you want to use and understand again, your application portfolio and perhaps because I'm insured services, a large company, I have a unique perspective of having to deal with very different problems at any given day on any given week. And you know, sometimes we forget about those, especially as technologists, we tend to forget that the decisions we make have wide and far reaching impact within our application stacks and within the individual businesses. And I think if if you uh look at what is my application stack, what are the types of technologies? How how is it going to be if you are doing just shrink wrap, then you probably shouldn't be investing in cloud technologies that are heavily focused on container ization. Right. If your custom developing applications, then your entire strategy should probably be focused on how do you build container farms? And if you're doing big data, you probably should bring deep use into the conversation with something nobody's talking about really yet. So, you know, Mhm >>Sounds like collaboration is really key. James the same question. Last question of our conversation. I'd love to get your perspective on what technology leaders should look for when you're talking with prospective customers when they're looking to partner for cloud implementation, growth management. What are some of those things that you say the technology leaders look for this? >>You really need to be working with people who understand your business that are passionate about your success and really having access to not only the advisory capabilities but the technology portfolio to help you realize all of your business and technology outcomes. And I think those are super important attributes that we HP can provide, you know, across the entire portfolio of technologies and services that most customers need to do. And I think that the business outcome, the business transformation is really key to what what the future holds for us. And having the visionary perspective of not only the customer but US in joint partnership allows for these great goals to be achieved. >>Its great goals in this business outcomes. Well, gentlemen, thank you for joining me on the program today. Talking to me about what Disney is doing with technology. How HP is supporting the Disney relationship. Jason and James. I appreciate your time. Thank >>you. Thank you lisa >>For Jason, Abrahamson and James Irvine. I'm Lisa Martin. You're watching the cubes coverage of HP Discover 2021. Uh huh. >>Yeah.

(upbeat music) >> Hey, welcome to the Cube's coverage of HPE Discover 2021. I'm Lisa Martin. I have two guests with me here today. We're going to be talking to the Walt Disney company. Jason Abraham sent us here, the director of infrastructure engineering. Jason, welcome to the program. >> Hi, how are you doing? >> Doing well and James Irvine is here as well. Account chief technologist at HPE. James, welcome to the program. >> Yeah hi Lisa, thank you. >> Good, so we're going to be talking about all things the HPE supporting Disney relationship, but you know things have been changing so much in technology. Things have been very different for technologists in the last few years. Jason talk to us about how Disney has adapted as business needs have evolved. >> You know, I think not just Disney, but in general, as we've, we've had to evolve, evolve as technologists, right? And one of the ways we've done that is to focus a lot on automation and self-service, enabling developers to move faster to meet the shift in business demand. Business moves at the speed of light. Anybody that's been in this business long enough knows there were years ago, you could have email servers down for three hours and nobody would notice. Now if email went down for more than, you know, 35 seconds, everybody notices, right? So in order to meet the change in demand we've had to focus heavily on automation and self-service which has been a key strategy, a key driver for us as part of private cloud. >> So Jason, with infrastructure as such a large part of your responsibilities and your job title, how has Disney been thinking about private cloud in the last few years? >> So I would say that we were probably one of the, I don't want to say bleeding edge, but certainly out in front when it came to private cloud. We had embarked on a cloud first strategy overall across the enterprise. The goal there was to figure out how we could do more with less and be more agile and be able to flex for our application developers and meet our shifts in demand. However, there are, you know systems that for whatever reasons, business purpose or otherwise need to either span a hybrid cloud or multi-cloud or stay on premise. So in order to get a cloud-like environment for our application developers and whatnot, we decided to build out a robust private cloud environment that allowed all of our application developers to be able to just bring their code or get a server and try to get as much of the public cloud functionality on premise as we possibly could. >> James, let's bring you into the conversation. Talk to us about the HPE Walt Disney company relationship and how HPE is supporting Walt Disney. >> Yeah. The HPE and Disney have had a longstanding relationship dating all the way back to HPE and Disney as far as the audio oscillator is concerned. So we've had an extraordinarily long history in technology and co-innovation partnership that we've worked on together through the years. And as Jason mentioned, you know, the journey around private cloud and working together in that technology relationship is just, has been fantastic and we've supported them with all the innovation and technologies needed for them to meet their goals. >> Excellent. All right, Jason, let's go back to you. I want to dig into this private cloud strategy a little bit more. You mentioned this a minute ago, but as we look at and hear so many discussions and strategies revolving around public multi-cloud, why is private cloud so important to Disney? >> Well, we have a tremendous amount of applications. We, our application portfolio is massive as you can imagine. We find ourselves in unique situations because of all of the different business challenges that we have that are unique to Disney, that we have to develop applications from the ground up far more often than we'd probably like to admit. So- private cloud allows us to take advantage of the public cloud-like services and technology scalability and flexibility and agility, right? And bring those on premise and be close to the business where it's absolutely critical to our business. I don't want to comment on what specific things or services that we have to run close to the business but you can imagine with the expansive footprint of our business and how we have to interact with guests, whether it's from a movie or at a theme park, we do have to have some services that are close to our business. And so, by having private cloud we compliment our public cloud strategy and allow us to keep those, those critical services very close to the business. >> Got it. You just mentioned a number of the elements of Disney. There's been a lot going on, so much going on. It's actually kind of easy to forget how new Disney Plus is, but sitting in the center of a company that's doing so much digitally, how does that shared services play a part in the overall digital transformation of the business? >> That's a great question. So obviously technology is key to our business. If you look at all the different lines of businesses we have and you look at all the different technology that we have, it's absolutely critical in order for us to continue to invest in technology to meet all of our business demands. Where shared services comes in is we enable the business to focus on what is critical to their business, right? We allow resorts and even the immediate media partners to just focus solely on the technology that is critical to driving those businesses, to enabling the guest experience and keeping it great. We are focused on everything else that is not critical for their business, the underlying infrastructure, the underpinning infrastructure, right, such as the global network, global servers, emails and so on and so forth. So it's a great compliment where it frees the business up to focus on what's really critical for them. And we can get economies of scale and synergy across our entire enterprise by delivering core services at a much more efficient cost throughout the company. >> And James, I want to ask you a question and we'll see if this gets approved. I just would love to understand, you've been working as a, with the Walt Disney company for a long time. We've, we've seen the evolution of HPE and we've seen the evolution of Disney. Can we ask you anything about, kind of give us your perspectives on how both companies have evolved in this relationship together? >> I- (laughter) I would, I would say that it's been it's been a great relationship. I would say that the, the, we have continued to lean on HPE from an investment perspective for our servers in certain areas, storage, but mostly servers. One are the big investments we've made recently was HP synergy, which is a composable infrastructure which has allowed us to continue to- invest in our automation strategy and allows us to deliver physical servers much faster, much faster. James, did you want to add anything there? >> Yeah of course Jason, it's been great to partner with Jason and the team, Walt Disney company in particular. And through this experience of them trying to achieve their private cloud goals, we've been able to bring the right technology, the right set of services to achieve these technology outcomes that they've been after and the use of automation to improve life cycle management, day two operations, all the goals and aspirations that they need to really automate infrastructure and make it intelligent and start achieving the goal of the intelligent data center. So it's been a great technology partnership and relationship we've had there. >> Jason back to you, let's, we've talked about Disney's private cloud strategy. I want to talk a little bit more about how that integrates with the rest of Disney's cloud strategy. What can you share with us? >> Well, like anything you'd want the right tool for the right job. And certainly the multi-cloud strategy and the public cloud strategy is a huge part of our overall strategic roadmap, where again we use the private cloud is to compliment that for applications that need to either span or stay on premise. You know, one of the things that we're just getting into now is hybrid cloud, where you have application teams that are like, hey, we really just need to focus on premise. It's where we need to be close to the business, but we have workloads that need to burst to the public cloud or need to scale out to the public cloud. And you really take advantage of that. So again, we don't look at it as, it used to be, not just within Disney, but in general in most cloud strategies, it was, is kind of like an either or. Now we look at it as the right tool for the right job. What's the right bid for your application? And as we continue to look at how the application stack modernizes right? Used to be how do you get servers faster? Well, now it's I don't want a server, I want a container. Now it's I just want to bring my code. I don't even know if I need a container, right? The application developers really want servers that compute. They really want to just focus on application development and they want to focus more on what makes their applications great, right? We want to focus more on commoditization and blurring the lines between public and private. Really, where does the workload run best? Where is it most efficient and where is it best for the business? And so when we look at how we built out our, our private cloud environment, it was really to compliment our existing public cloud strategy. >> Let's talk about people now, Jason, for a second. I know I love that Disney calls their folks, the cast members. I see the pin on your lapel there. How are the cast members at the center of this technology strategy and the how does the private cloud strategy play into that? >> Well, it's one of those things where our cast members are the most important aspect of our, of our brand. If you, if you were to look at what is our what is our most valuable asset? It would certainly be our cast members, right? They are the frontline, whether it's helping a guest, whether it's working on a movie, and our overall technology strategy is all about enabling cast members to do their job as most efficiently and effectively as possible. When it comes to how private cloud fits into that, it's again creating an environment where the application developers and our business partners can accelerate their application growth and the delivery of their services to support our back of house operations for our cast members. So that way it doesn't impact the guest experience. There's nothing more frustrating for a cast member is when they're impeded or have issues trying to get to a resource or unable to efficiently do their job. And so by having the private cloud, by having access to resources on premise, at times it gives them the ability to deliver those and consume those applications even faster. >> Which I'm sure that the guests love. One of the things that you mentioned, Jason, and I want to, James, get your opinion on this too. It's a, it's a statement that we hear very often. You need to do more with less. In that situation, how does Disney navigate that and, and a strategy that is cost-effective while you're growing your public, your private cloud strategy? >> Automation. Right? Automate automation and self-service. It, it really, it's always comes back to, I know it's a buzzword. I know people go, oh, automate this, automate that, you know, what are you, what are you automating? If you look at just the investments we're making right now in the HP synergy line and having composable infrastructure combined with pockets of three-tier architecture as well as hyperconverge, you are, we're bringing a delivery model to application teams and business teams that they haven't that is just like public cloud, right? But that they haven't seen before. So in order to manage massive scale, you need to automate more and you need to automate more in order to make sure that you have self healing, right? So you can, so you can look at things and understand things and see where you're having problems and try to predict them before they happen and increase your uptime and availability. I mean, it all comes back to, again, automation, automation, automation. >> James, do you have the similar opinion when you talk with customers similar to the Walt Disney company that are told we've got to do more but we've got less to work with? Is automation one of your key go-to recommendations? >> Yeah. Automation is at the center of everything that we're trying to achieve today both on-premise and in the public cloud and hyper automation is really kind of where everybody is driving to. The ability to be incredibly big, incredibly efficient using infrastructure as code API driven and using all the tools to really automate that and make the seamless delivery of new products and services just that much quicker. And we've been focused on that both not only from a technology and infrastructure standpoint, but also from a consulting and delivery standpoint. So we're able to really kind of meet all the different needs as it relates to automation, both in a private cloud hybrid cloud or multi-cloud scenario with all of the partnerships that we have across all the hyperscalers. >> James, sticking with you. With that, looking through that consultant lens I want to get some thought leadership from you. What are some of the principles that you'd recommend for businesses that really are working hard to make their private cloud investment work as efficiently as possible for them? >> A lot of that comes down to consulting and understanding. So really kind of driving to what we've referred to as the right mix. What is that right mix of hybrid cloud, private cloud applications that have gravity that needs to remain on premise. And there's just no reason to move them. So working with somebody and partnering with somebody that has the ability to be able to advise and consult in that capacity across the continuum of private public as well as edge is vitally important for people to consider as a part of their strategy. >> Jason, edge is absolutely incredible. We're hearing about it more and more, especially as it's so much more data and machine data is generated there. I want to get your advice for the audience. Same question that I asked James. What principles would you recommend for making the private cloud investment work as hard as possible, as efficiently as possible? >> I would say that, you know it's going to be a unique journey for every single company, but the number one advice is remember, right tool for the right job, right? What is your application stack? What are the types of in that, what is the type of needs of the application owners? And when you start thinking about it, you start dissecting it, are going to be investing more in microservices? Can you go with a more of a server-less container based type of environment or are you using shrink wrap software and you're going to need more eyes, right? It all comes down to, the right tool for the right job. My father was an auto mechanic and I remember as a kid, he had 8,000 tools. And I used to say to him, dad why do you have five screwdrivers? To me they all looked the same, right? I'm not a mechanic, but he goes, no, no, no, Jason, you don't understand. It's the right tool for the right job. You know, that was always his mantra. That would be my advice. >> I like that. I think my dad would have said the same thing, right tool for the right job. Absolutely critically important. So when we think about Disney, we know you generate a ton of data. How does the, the growth of the private cloud, Jason, support that massive data growth? >> Well, as you can imagine, we have ebbs and flows in our data. There's times where we're taking a tremendous amount of data in, and there's times where we're purging a tremendous amount of data for various different reasons, right? So one of the beauties of private cloud and how it compliments the public cloud is when you, you go to, you think about data ingestion, right? And then storage and being able to efficiently get it on premise and whatnot. Having the private cloud there to do those types of things, to use more of those BI type of workloads. They're, you're, you're just trunching a bunch of data. It's really nice to have the private cloud. So that way the application team can add nodes, add collectors if it's, you know, other log aggregation type tools, right? Whatever the tool is, you know, being able to have the flexibility to add nodes very quickly, just like they can in a public cloud, public cloud, but have it on premise so that you can do cost control and get the data in a more timely, more efficient manner. Again though, it comes down to the type of workload and what was best for that business. I would, I would be amiss if I tried to sit here and tell you that all of our big data stuff, were to only reside or only use on-premise technologies. Of course it spans like I said, we've got hybrid cloud and multi-cloud so. >> Well, it kind of goes with the right tool for the right job. One more question for both of you. And I want to go back to that thought leadership angle. Jason, when you are talking with peers of yours, what do you recommend that technology leaders look for when they're going to be partnering with a company on any type of cloud initiative management or implementation project? >> I would say understand your, understand the problem you're trying to solve, understand the technologies that you want to use and understand again your application portfolio and perhaps because I'm in shared services, a large company, I have a unique perspective of having to deal with very different problems at any given day on any given week. And I, you know, sometimes we forget about those, especially as technologists, we tend to forget that the decisions we make have wide and far reaching impact within our application stacks and within the individual businesses. And I think if, if you look at what is my application stack, what are the types of technologies? How, how is it going to be? If you were doing just shrink wrap, then you probably shouldn't be investing in cloud technologies that are heavily focused on containerization, right? If you're custom developing applications, then your entire strategy should probably be focused on how do you build container farms? And if you're doing big data, you probably should bring GPU's into the conversation with something that nobody's talking about really yet. So, you know. >> Sounds like collaboration is really key. James, same question. Last question of our conversation. I'd love to get your perspective on what technology leaders should look for when you're talking with prospective customers. When they're looking to partner for cloud implementation, growth management, what are some of those things that you say, the technology leaders look for this? >> You really need to be working with people who understand your business, that are passionate about your success and really having access to not only the advisory capabilities, but the technology portfolio to help you realize all of your business and technology outcomes. And I think those are super important attributes that we HPE can provide, you know, across the entire portfolio of technologies and services that most customers need to do. And I, and I think that the business outcome, the business transformation is really key to what the future holds for us and having the visionary perspective of not only the customer, but us in joint partnership allows for these great goals to be achieved. >> Great goals and those business outcomes. Well, gentlemen, thank you for joining me on the program today. Talking to me about what Disney's doing with technology, how HPE is supporting that Disney relationship. Jason and James, I appreciate your time. >> Thank you. >> Thank you, Lisa. For Jason Abrahamson and James Irvine, I'm Lisa Martin. You're watching the Cube's coverage of HPE discover 2021. (upbeat music)

(intro music) >> Hi, everybody, we're back. Dave Vellante and Dave Nicholson. We're covering Fal.Con 22. This is CrowdStrike's big user conference. CrowdStrike is a very hot company, as you probably know started on endpoint security, expanding into another, a number of other areas trying to build the next great generational company in cybersecurity. Michael Sherwood is here. He's the chief innovation and technology officer for the city of Las Vegas. >> Got to love that. >> Thanks so much for coming to theCUBE. >> Welcome! >> Yeah, we got to love that. I mean, if it weren't for Las Vegas, I'm not sure where we would have our CUBE events, but so thank you for hosting us. >> Thank you for being here. This is awesome. It's a great day and a lot of people, and it's exciting to see everything that's going on here. >> Yeah, the city is booming. Obviously the convention, the conference business is booming. Tech is a big part of that but there's so many other industries that come to Las Vegas. Talk about your role, really interesting, chief innovation, technology officer, CTO. Tell us about what you do day to day. >> Kind of all over the place. But a lot of it has to do with day to day technology within the organization. So managing all the different technology components. When you start looking at any city, it's a lot of different companies inside of it. Think of fire service as a different company. They all have different missions. And so our technology needs are expansive. So while we have operational IT, we also have our innovation unit. Innovation unit works on next generation technology. So Las Vegas was one of the first cities in the United States to have a autonomous vehicle drive in mix-flow traffic, meaning it was out there with, driving along cars. We're also the first city to have an accident in a autonomous vehicle. That happened on day two. (Vellante laughing) So, there's always a lot of firsts in Las Vegas, but. >> Despite the grid. >> Despite the grid, you know. But even today, so that was in 2017, when we first started working with autonomous vehicles. Up until today, where you have the ability, anybody in Las Vegas, including yourselves right after the show can go ahead and use Lyft, go outside and hail an autonomous taxi to come pick you up and drive you up and down the strip. Those vehicles actually communicate with our infrastructure. So the innovation is, how do cities work with private companies to start building next generation amenities, next generation technologies? And so that happens a lot of times. People don't realize. They come to Las Vegas for entertainment, and now we're known for sports but we do have a lot of technology here that permeates through the entire community. >> So I'm from Boston. We're trying to get the smart traffic lights, we're not quite there yet. But I was at a session, Dave you'll appreciate it, it was John Rose, who was the CTO. He was the CTO of, he's a CTO of Dell Technologies now. And the mayor of Boston, we were talking about the vision for a smart city. But Boston and I mean talk about, a challenge for building a smart city. So when I come out here, it's like amazing to me to see the technology that's there. So as a CTO and innovation officer, you've got a playground where... Now, of course you have legacy infrastructure, you've got technical debt, but you also have, in certain cases, an opportunity and more latitude to get creative. So what are some of the cool things that you're working on that you're really excited about? >> There's a lot of things I'm excited about. It's just great being in this city. But a lot of the things that we're excited about here in the next year to two years, we have an innovation district. So not a lot of cities have this but Downtown around the Fremont Street Experience, there's a corridor there that covers government, covers entertainment, medical. And so this innovation district is where we test out new technologies. So some of the things we're testing out, computer vision. So we're, our smart parks program is how do we provide better security and enjoyment of those amenities without providing physical labor to constantly patrol. And so we're using cameras and vision and different types of AI algorithms to kind of manage the park. And while we're doing that, we're also getting data back on how often is the park used? Are the facilities, are the sprinklers going on during the day? Water's a big deal here. And so those type of projects. Again, autonomy is still huge, vehicle autonomy, still working on driving those next generation changes where you'll actually have a driverless vehicle. Right now, there's a safety driver in a lot of the autonomous vehicles. Even the one I talked about earlier, you have the, while the vehicles driving itself, for safety reasons, there's still a human driver in the seat. But as we go forward in the next year to two, that >> That's soon. >> is getting ready to change. I believe that's soon. You can quote it here, you heard it here first. >> Wow. >> But that would be coming up. You got drones as well. We've already started looking at a few types of drone delivery systems. It may not be too far away. Your pizza or maybe some other item that you want is delivered in the general area. Probably not in the hotel corridor but in the outside areas of the city. I just think there's a lot of, again, we're building amenities for the future. We really want people to understand that Las Vegas is not just a place to come visit, but it's a place to live and have fun and be part of a community. >> So from an academic perspective, what you just described is a highly ambidextrous organization, right? >> Yes. >> Because you're not just worried about keeping the lights on, but you're also looking at innovation. How did your organization get to this place? What you're describing is sort of the gold standard that any organization public or private would seek to implement. How did you get there? >> Baby steps, small steps. It all started back when there was the Smart Cities Challenge. So we were not selected as the finalist. We were in the, I think top 15 at the time but we didn't give up on it. And we continued to move forward. The pandemic helped us do things. When you ask, what do I do? Well, my normal job is running the day to day infrastructure. I also see my role as economic development to help bring companies here and bring new ideas. We have a great community, diverse and ready to do things. But when you take, talk about the innovation and the technology and what we're doing. Like I said, during a pandemic, we came up with the idea of, Hey, we don't want to send our building inspectors or our inspectors in the people's homes, one for the inspector's health and one for the citizen's health. So we used normal tools. We took an iPhone and made it a virtual inspector. So now if you get a new water heater, you can actually do your inspection via like a FaceTime. And you hold your phone up around the water heater. We can view it, we record the video, save it, and boom give you an inspection remotely. And so you build on it. So how do you get, I wouldn't quite say we're the gold. I appreciate, we're moving there, that's the bar. You've laid out the bar for us, but we're moving in that direction. But it's building on one win and not all of our things that we've deployed. We can talk about those as well. Some of the things like trash can sensors, we looked at doing, which would monitor when the trash can was full or empty, just didn't pan out. So a lot of the times I talk about the wins a lot not as much about the things that didn't pan out. >> So what're the big challenges, generally of building out a smart city and then specifically around cyber? >> So there's, community acceptance number one. Las Vegas, I'm very lucky cameras are everywhere. So there's not as much resistance to using video technology. But a lot of times it's just getting the constituents, getting people to understand the value of what we're trying to do. Not everybody is interested in autonomous vehicles or believes they're ready for that. But when you start looking at the increments, more than any other city I know, the community here is so robust and so supportive of bringing on these technologies. Look, what other city do you know that builds new buildings and knocks them down five years later to build something new again? Or, who has a volcano in the middle of their downtown? So different things like that. But when you start looking at all the advancements we're making, you brought up one of the biggest concerns. When people ask me, what keeps you up at night? It's not the autonomous vehicle not performing, its the cyber, it's the cyber issues that go along with becoming more advanced. And as you bring innovation in, you start bleeding the lines of what's government, what's private. And then how do you continue to have the data transmission between these multiple entities? How do you keep the endpoint secure? And that is something that you learn as you go, but it's always out there. And endpoint security and security in general is a huge, huge area. >> And how about the data? You were talking before about you can get actually approval for an inspection. That's data, it's video data. How have you changed the way in which you're using data? What are you doing with that data? How do you leverage it? How do you secure it? >> It's all great questions. One of the things we've undertaken is called an open data initiative. So we have an open data portal. It's opendata.lasvegasnevada.gov, where we publish a lot of the data sets that we collect. If it's air quality, if it's ambulance runs, and we make that data available. A lot of that is, one for the public for transparency, two though, it's, we hope enables the private sector to build apps off of the data that we have. A lot of times, you either you have the data but you don't have the app or you have the app, but no data. So in our way, it's trying to help the community build up new ideas. Our push has been moving to the cloud a lot. So we're pushing a lot more data into the cloud where before I think a lot of governments keep a lot of that internal, but obviously look, the cloud's here to stay and it's not going anywhere. And so now it's more about as we migrate, using our partners, our relationship with CrowdStrike, to start securing not only our endpoints but start looking at the cloud space as well. And then we have this new technology. It's not really new, but edge compute. You've heard a lot of, there's different people talking about it. When you start talking about autonomous vehicles, autonomous delivery, drones. We own a large private wireless network. A lot of data now is computed at the edge and we're only taking the metadata and sending it up to the cloud. So it becomes rather complicated with security being at the forefront. >> Yeah, so that very small portion of the actual amount of data that's created goes back but it's such a massive amount of data. It's not to trivialize it, it's still a lot. And some of it is probably ephemeral. Do you persist at all? Or probably not. >> Not always, I mean. A lot of it, what we're learning is, it's a learning process as you go through this smart city or what we call just basically emerging into, 'cause I believe all cities are smart. Not one city smarter than another necessarily. So I'm not really a fan of the term smart city. It's more in line with me as we're building amenities for the future and building amenities for people. And a lot of that is built upon data and then built upon providing things that citizens want. And we all know, we all live somewhere and we live there because it's safe community, it has good education, good infrastructure whatever it might be. And so we're trying to build out that smart community to be as many things as we can to as many people. >> Yeah, that's fair. And there's automation, there's certainly machine intelligence that's heavily involved. Of course, you talking autonomous. Now I understand your work transcends the city of Las Vegas into the broader state of Nevada helping make Nevada a safer state. What's that all about? >> So we have a great partnership. One of the great things, I come from California, so a rather large state. Here in Nevada, it's a very close knit state. So we have a lot of communications with the state. We get to work with them very closely. One of the initiatives we've been working on is how do we, a lot of organizations spend a lot of time doing cybersecurity for just their organization. So it's focused internal on the employees that might work in that organization. We're kind of now looking outwards and saying, how do we not only do that for our internal government employees but how do we involve the entire community? One of the things is, is Las Vegas over 40,000 conventions per year. You're here a lot. What happens in Vegas stays in Vegas and a lot of people bring malware with them and it stays here. We're trying to educate people. We do a lot in government to help people with police and fire and services. What is local government doing to help the community prepare for the next generation of cyber threats and issues? So our initiative is really working with the community, bringing in CrowdStrike and other partners to help us not only work with small business, but work with those entrepreneurs as well as the midsize businesses. >> So what do you do with Crowd? You got the cool little CrowdStrike, not CrowdStrike, but you got the red splash in your lapel. Very cool cuff links, I noticed that you have there. I love the red. >> Little poker chips there. >> They're Very nice, very nice. >> They're very cool. So what do you do with CrowdStrike? >> So CrowdStrike is one of our major components in our security posture. We use them as endpoint protection. I can tell you a quick story. I know my CISO's listening probably was going to cringe now when I tell this story, but our journey with CrowdStrike has been amazing. We deployed the product and when that first week of deployment, we had a malicious actor and CrowdStrike was able to catch it. I would probably would not be here today with you two gentlemen if it wasn't for CrowdStrike. That's not an endorsement it's just a, that's a fact of how things rolled out. But we depend on CrowdStrike and their capabilities to ensure the safety of our digital assets. >> You wouldn't be here 'cause we, it used to be failure means fire. Is that what you mean? >> That's what I mean. I'm not going to, I don't like to use that word in my terminology, but basically failure is not an option in my job. It's just not there. >> Well, it's funny, we had Kevin Mandy on early, he was like, look I started my company in 2004 with the assumption that breaches will happen, you are going to get breached. >> Yes >> So that's why I say, I think there was a day when, if you got breached, oh, you're fired. Well that, then everybody got breached. So I think that that sentiment changing 'cause CrowdStrike saying that the unstoppable breach is a myth. Well, we're not there yet, but. >> I'd say damage control now. At least we have a little bit more control but, again, look, government is about trust. And so when you have that trust level, from my perspective, I keep a high standard and try to prevent any loss of data or any type of malicious activity from happening. I hope the mayor's listening and she doesn't fire me if anything would happen, but you know. >> You got a fun job. How'd you get into this? >> It was a great opportunity. I worked in law enforcement prior to here. I was a Deputy Police Chief in city of Irvine. I oversaw technology as part of that role. I've always loved Las Vegas, always liked the energy of the city and I had a great opportunity to apply and I applied and was lucky enough to be selected. I have a great team that supports me. >> Deputy Police Chief, it sounds like, what you just described, the technology role. You had an operations role essentially, is that right? >> Correct. And so kind of gave me a lot of insights and really helped me, as you progress in government, having different roles in your portfolio makes you a little bit more adaptive and it's kind of, it helps in, especially now with so much video and cameras prevalent in cities, having that law enforcement role, understanding a little of the legal aspects and understanding some of the, what law enforcement wants kind of makes that bridge from technology to the actual end user. >> A really interesting story, Michael. Thanks so much for sharing on theCUBE, appreciate it. >> Thank you for having me here. >> You're very welcome. All right, keep it right there. Dave Nicholson and Dave Vellante will be back from Las Vegas at the Aria from Fal.Con 22. You're watching theCUBE. (outro music)

>>Individuals create developers, translate ideas to code, to create great applications and great applications. Touch everyone. A Docker. We know that collaboration is key to your innovation sharing ideas, working together. Launching the most secure applications. Docker is with you wherever your team innovates, whether it be robots or autonomous cars, we're doing research to save lives during a pandemic, revolutionizing, how to buy and sell goods online, or even going into the unknown frontiers of space. Docker is launching innovation everywhere. Join us on the journey to build, share, run the future. >>Hello and welcome to Docker con 2021. We're incredibly excited to have more than 80,000 of you join us today from all over the world. As it was last year, this year at DockerCon is 100% virtual and 100% free. So as to enable as many community members as possible to join us now, 100%. Virtual is also an acknowledgement of the continuing global pandemic in particular, the ongoing tragedies in India and Brazil, the Docker community is a global one. And on behalf of all Dr. Khan attendees, we are donating $10,000 to UNICEF support efforts to fight the virus in those countries. Now, even in those regions of the world where the pandemic is being brought under control, virtual first is the new normal. It's been a challenging transition. This includes our team here at Docker. And we know from talking with many of you that you and your developer teams are challenged by this as well. So to help application development teams better collaborate and ship faster, we've been working on some powerful new features and we thought it would be fun to start off with a demo of those. How about it? Want to have a look? All right. Then no further delay. I'd like to introduce Youi Cal and Ben, gosh, over to you and Ben >>Morning, Ben, thanks for jumping on real quick. >>Have you seen the email from Scott? The one about updates and the docs landing page Smith, the doc combat and more prominence. >>Yeah. I've got something working on my local machine. I haven't committed anything yet. I was thinking we could try, um, that new Docker dev environments feature. >>Yeah, that's cool. So if you hit the share button, what I should do is it will take all of your code and the dependencies and the image you're basing it on and wrap that up as one image for me. And I can then just monitor all my machines that have been one click, like, and then have it side by side, along with the changes I've been looking at as well, because I was also having a bit of a look and then I can really see how it differs to what I'm doing. Maybe I can combine it to do the best of both worlds. >>Sounds good. Uh, let me get that over to you, >>Wilson. Yeah. If you pay with the image name, I'll get that started up. >>All right. Sen send it over >>Cheesy. Okay, great. Let's have a quick look at what you he was doing then. So I've been messing around similar to do with the batter. I've got movie at the top here and I think it looks pretty cool. Let's just grab that image from you. Pick out that started on a dev environment. What this is doing. It's just going to grab the image down, which you can take all of the code, the dependencies only get brunches working on and I'll get that opened up in my idea. Ready to use. It's a here close. We can see our environment as my Molly image, just coming down there and I've got my new idea. >>We'll load this up and it'll just connect to my dev environment. There we go. It's connected to the container. So we're working all in the container here and now give it a moment. What we'll do is we'll see what changes you've been making as well on the code. So it's like she's been working on a landing page as well, and it looks like she's been changing the banner as well. So let's get this running. Let's see what she's actually doing and how it looks. We'll set up our checklist and then we'll see how that works. >>Great. So that's now rolling. So let's just have a look at what you use doing what changes she had made. Compare those to mine just jumped back into my dev container UI, see that I've got both of those running side by side with my changes and news changes. Okay. So she's put Molly up there rather than mobi or somebody had the same idea. So I think in a way I can make us both happy. So if we just jumped back into what we'll do, just add Molly and Moby and here I'll save that. And what we can see is, cause I'm just working within the container rather than having to do sort of rebuild of everything or serve, or just reload my content. No, that's straight the page. So what I can then do is I can come up with my browser here. Once that's all refreshed, refresh the page once hopefully, maybe twice, we should then be able to see your refresh it or should be able to see that we get Malia mobi come up. So there we go, got Molly mobi. So what we'll do now is we'll describe that state. It sends us our image and then we'll just create one of those to share with URI or share. And we'll get a link for that. I guess we'll send that back over to you. >>So I've had a look at what you were doing and I'm actually going to change. I think that might work for both of us. I wondered if you could take a look at it. If I send it over. >>Sounds good. Let me grab the link. >>Yeah, it's a dev environment link again. So if you just open that back in the doc dashboard, it should be able to open up the code that I've changed and then just run it in the same way you normally do. And that shouldn't interrupt what you're already working on because there'll be able to run side by side with your other brunch. You already got, >>Got it. Got it. Loading here. Well, that's great. It's Molly and movie together. I love it. I think we should ship it. >>Awesome. I guess it's chip it and get on with the rest of.com. Wasn't that cool. Thank you Joey. Thanks Ben. Everyone we'll have more of this later in the keynote. So stay tuned. Let's say earlier, we've all been challenged by this past year, whether the COVID pandemic, the complete evaporation of customer demand in many industries, unemployment or business bankruptcies, we all been touched in some way. And yet, even to miss these tragedies last year, we saw multiple sources of hope and inspiration. For example, in response to COVID we saw global communities, including the tech community rapidly innovate solutions for analyzing the spread of the virus, sequencing its genes and visualizing infection rates. In fact, if all in teams collaborating on solutions for COVID have created more than 1,400 publicly shareable images on Docker hub. As another example, we all witnessed the historic landing and exploration of Mars by the perseverance Rover and its ingenuity drone. >>Now what's common in these examples, these innovative and ambitious accomplishments were made possible not by any single individual, but by teams of individuals collaborating together. The power of teams is why we've made development teams central to Docker's mission to build tools and content development teams love to help them get their ideas from code to cloud as quickly as possible. One of the frictions we've seen that can slow down to them in teams is that the path from code to cloud can be a confusing one, riddle with multiple point products, tools, and images that need to be integrated and maintained an automated pipeline in order for teams to be productive. That's why a year and a half ago we refocused Docker on helping development teams make sense of all this specifically, our goal is to provide development teams with the trusted content, the sharing capabilities and the pipeline integrations with best of breed third-party tools to help teams ship faster in short, to provide a collaborative application development platform. >>Everything a team needs to build. Sharon run create applications. Now, as I noted earlier, it's been a challenging year for everyone on our planet and has been similar for us here at Docker. Our team had to adapt to working from home local lockdowns caused by the pandemic and other challenges. And despite all this together with our community and ecosystem partners, we accomplished many exciting milestones. For example, in open source together with the community and our partners, we open sourced or made major contributions to many projects, including OCI distribution and the composed plugins building on these open source projects. We had powerful new capabilities to the Docker product, both free and subscription. For example, support for WSL two and apple, Silicon and Docker, desktop and vulnerability scanning audit logs and image management and Docker hub. >>And finally delivering an easy to use well-integrated development experience with best of breed tools and content is only possible through close collaboration with our ecosystem partners. For example, this last year we had over 100 commercialized fees, join our Docker verified publisher program and over 200 open source projects, join our Docker sponsored open source program. As a result of these efforts, we've seen some exciting growth in the Docker community in the 12 months since last year's Docker con for example, the number of registered developers grew 80% to over 8 million. These developers created many new images increasing the total by 56% to almost 11 million. And the images in all these repositories were pulled by more than 13 million monthly active IP addresses totaling 13 billion pulls a month. Now while the growth is exciting by Docker, we're even more excited about the stories we hear from you and your development teams about how you're using Docker and its impact on your businesses. For example, cancer researchers and their bioinformatics development team at the Washington university school of medicine needed a way to quickly analyze their clinical trial results and then share the models, the data and the analysis with other researchers they use Docker because it gives them the ease of use choice of pipeline tools and speed of sharing so critical to their research. And most importantly to the lives of their patients stay tuned for another powerful customer story later in the keynote from Matt fall, VP of engineering at Oracle insights. >>So with this last year behind us, what's next for Docker, but challenge you this last year of force changes in how development teams work, but we felt for years to come. And what we've learned in our discussions with you will have long lasting impact on our product roadmap. One of the biggest takeaways from those discussions that you and your development team want to be quicker to adapt, to changes in your environment so you can ship faster. So what is DACA doing to help with this first trusted content to own the teams that can focus their energies on what is unique to their businesses and spend as little time as possible on undifferentiated work are able to adapt more quickly and ship faster in order to do so. They need to be able to trust other components that make up their app together with our partners. >>Docker is doubling down and providing development teams with trusted content and the tools they need to use it in their applications. Second, remote collaboration on a development team, asking a coworker to take a look at your code used to be as easy as swiveling their chair around, but given what's happened in the last year, that's no longer the case. So as you even been hinted in the demo at the beginning, you'll see us deliver more capabilities for remote collaboration within a development team. And we're enabling development team to quickly adapt to any team configuration all on prem hybrid, all work from home, helping them remain productive and focused on shipping third ecosystem integrations, those development teams that can quickly take advantage of innovations throughout the ecosystem. Instead of getting locked into a single monolithic pipeline, there'll be the ones able to deliver amps, which impact their businesses faster. >>So together with our ecosystem partners, we are investing in more integrations with best of breed tools, right? Integrated automated app pipelines. Furthermore, we'll be writing more public API APIs and SDKs to enable ecosystem partners and development teams to roll their own integrations. We'll be sharing more details about remote collaboration and ecosystem integrations. Later in the keynote, I'd like to take a moment to share with Docker and our partners are doing for trusted content, providing development teams, access to content. They can trust, allows them to focus their coding efforts on what's unique and differentiated to that end Docker and our partners are bringing more and more trusted content to Docker hub Docker official images are 160 images of popular upstream open source projects that serve as foundational building blocks for any application. These include operating systems, programming, languages, databases, and more. Furthermore, these are updated patch scan and certified frequently. So I said, no image is older than 30 days. >>Docker verified publisher images are published by more than 100 commercialized feeds. The image Rebos are explicitly designated verify. So the developers searching for components for their app know that the ISV is actively maintaining the image. Docker sponsored open source projects announced late last year features images for more than 200 open source communities. Docker sponsors these communities through providing free storage and networking resources and offering their community members unrestricted access repos for businesses allow businesses to update and share their apps privately within their organizations using role-based access control and user authentication. No, and finally, public repos for communities enable community projects to be freely shared with anonymous and authenticated users alike. >>And for all these different types of content, we provide services for both development teams and ISP, for example, vulnerability scanning and digital signing for enhanced security search and filtering for discoverability packaging and updating services and analytics about how these products are being used. All this trusted content, we make available to develop teams for them directly to discover poll and integrate into their applications. Our goal is to meet development teams where they live. So for those organizations that prefer to manage their internal distribution of trusted content, we've collaborated with leading container registry partners. We announced our partnership with J frog late last year. And today we're very pleased to announce our partnerships with Amazon and Miranda's for providing an integrated seamless experience for joint for our joint customers. Lastly, the container images themselves and this end to end flow are built on open industry standards, which provided all the teams with flexibility and choice trusted content enables development teams to rapidly build. >>As I let them focus on their unique differentiated features and use trusted building blocks for the rest. We'll be talking more about trusted content as well as remote collaboration and ecosystem integrations later in the keynote. Now ecosystem partners are not only integral to the Docker experience for development teams. They're also integral to a great DockerCon experience, but please join me in thanking our Dr. Kent on sponsors and checking out their talks throughout the day. I also want to thank some others first up Docker team. Like all of you this last year has been extremely challenging for us, but the Docker team rose to the challenge and worked together to continue shipping great product, the Docker community of captains, community leaders, and contributors with your welcoming newcomers, enthusiasm for Docker and open exchanges of best practices and ideas talker, wouldn't be Docker without you. And finally, our development team customers. >>You trust us to help you build apps. Your businesses rely on. We don't take that trust for granted. Thank you. In closing, we often hear about the tenant's developer capable of great individual feeds that can transform project. But I wonder if we, as an industry have perhaps gotten this wrong by putting so much emphasis on weight, on the individual as discussed at the beginning, great accomplishments like innovative responses to COVID-19 like landing on Mars are more often the results of individuals collaborating together as a team, which is why our mission here at Docker is delivered tools and content developers love to help their team succeed and become 10 X teams. Thanks again for joining us, we look forward to having a great DockerCon with you today, as well as a great year ahead of us. Thanks and be well. >>Hi, I'm Dana Lawson, VP of engineering here at get hub. And my job is to enable this rich interconnected community of builders and makers to build even more and hopefully have a great time doing it in order to enable the best platform for developers, which I know is something we are all passionate about. We need to partner across the ecosystem to ensure that developers can have a great experience across get hub and all the tools that they want to use. No matter what they are. My team works to build the tools and relationships to make that possible. I am so excited to join Scott on this virtual stage to talk about increasing developer velocity. So let's dive in now, I know this may be hard for some of you to believe, but as a former CIS admin, some 21 years ago, working on sense spark workstations, we've come such a long way for random scripts and desperate systems that we've stitched together to this whole inclusive developer workflow experience being a CIS admin. >>Then you were just one piece of the siloed experience, but I didn't want to just push code to production. So I created scripts that did it for me. I taught myself how to code. I was the model lazy CIS admin that got dangerous and having pushed a little too far. I realized that working in production and building features is really a team sport that we had the opportunity, all of us to be customer obsessed today. As developers, we can go beyond the traditional dev ops mindset. We can really focus on adding value to the customer experience by ensuring that we have work that contributes to increasing uptime via and SLS all while being agile and productive. We get there. When we move from a pass the Baton system to now having an interconnected developer workflow that increases velocity in every part of the cycle, we get to work better and smarter. >>And honestly, in a way that is so much more enjoyable because we automate away all the mundane and manual and boring tasks. So we get to focus on what really matters shipping, the things that humans get to use and love. Docker has been a big part of enabling this transformation. 10, 20 years ago, we had Tomcat containers, which are not Docker containers. And for y'all hearing this the first time go Google it. But that was the way we built our applications. We had to segment them on the server and give them resources. Today. We have Docker containers, these little mini Oasys and Docker images. You can do it multiple times in an orchestrated manner with the power of actions enabled and Docker. It's just so incredible what you can do. And by the way, I'm showing you actions in Docker, which I hope you use because both are great and free for open source. >>But the key takeaway is really the workflow and the automation, which you certainly can do with other tools. Okay, I'm going to show you just how easy this is, because believe me, if this is something I can learn and do anybody out there can, and in this demo, I'll show you about the basic components needed to create and use a package, Docker container actions. And like I said, you won't believe how awesome the combination of Docker and actions is because you can enable your workflow to do no matter what you're trying to do in this super baby example. We're so small. You could take like 10 seconds. Like I am here creating an action due to a simple task, like pushing a message to your logs. And the cool thing is you can use it on any the bit on this one. Like I said, we're going to use push. >>You can do, uh, even to order a pizza every time you roll into production, if you wanted, but at get hub, that'd be a lot of pizzas. And the funny thing is somebody out there is actually tried this and written that action. If you haven't used Docker and actions together, check out the docs on either get hub or Docker to get you started. And a huge shout out to all those doc writers out there. I built this demo today using those instructions. And if I can do it, I know you can too, but enough yapping let's get started to save some time. And since a lot of us are Docker and get hub nerds, I've already created a repo with a Docker file. So we're going to skip that step. Next. I'm going to create an action's Yammel file. And if you don't Yammer, you know, actions, the metadata defines my important log stuff to capture and the input and my time out per parameter to pass and puts to the Docker container, get up a build image from your Docker file and run the commands in a new container. >>Using the Sigma image. The cool thing is, is you can use any Docker image in any language for your actions. It doesn't matter if it's go or whatever in today's I'm going to use a shell script and an input variable to print my important log stuff to file. And like I said, you know me, I love me some. So let's see this action in a workflow. When an action is in a private repo, like the one I demonstrating today, the action can only be used in workflows in the same repository, but public actions can be used by workflows in any repository. So unfortunately you won't get access to the super awesome action, but don't worry in the Guild marketplace, there are over 8,000 actions available, especially the most important one, that pizza action. So go try it out. Now you can do this in a couple of ways, whether you're doing it in your preferred ID or for today's demo, I'm just going to use the gooey. I'm going to navigate to my actions tab as I've done here. And I'm going to in my workflow, select new work, hello, probably load some workflows to Claire to get you started, but I'm using the one I've copied. Like I said, the lazy developer I am in. I'm going to replace it with my action. >>That's it. So now we're going to go and we're going to start our commitment new file. Now, if we go over to our actions tab, we can see the workflow in progress in my repository. I just click the actions tab. And because they wrote the actions on push, we can watch the visualization under jobs and click the job to see the important stuff we're logging in the input stamp in the printed log. And we'll just wait for this to run. Hello, Mona and boom. Just like that. It runs automatically within our action. We told it to go run as soon as the files updated because we're doing it on push merge. That's right. Folks in just a few minutes, I built an action that writes an entry to a log file every time I push. So I don't have to do it manually. In essence, with automation, you can be kind to your future self and save time and effort to focus on what really matters. >>Imagine what I could do with even a little more time, probably order all y'all pieces. That is the power of the interconnected workflow. And it's amazing. And I hope you all go try it out, but why do we care about all of that? Just like in the demo, I took a manual task with both tape, which both takes time and it's easy to forget and automated it. So I don't have to think about it. And it's executed every time consistently. That means less time for me to worry about my human errors and mistakes, and more time to focus on actually building the cool stuff that people want. Obviously, automation, developer productivity, but what is even more important to me is the developer happiness tools like BS, code actions, Docker, Heroku, and many others reduce manual work, which allows us to focus on building things that are awesome. >>And to get into that wonderful state that we call flow. According to research by UC Irvine in Humboldt university in Germany, it takes an average of 23 minutes to enter optimal creative state. What we call the flow or to reenter it after distraction like your dog on your office store. So staying in flow is so critical to developer productivity and as a developer, it just feels good to be cranking away at something with deep focus. I certainly know that I love that feeling intuitive collaboration and automation features we built in to get hub help developer, Sam flow, allowing you and your team to do so much more, to bring the benefits of automation into perspective in our annual October's report by Dr. Nicole, Forsgren. One of my buddies here at get hub, took a look at the developer productivity in the stork year. You know what we found? >>We found that public GitHub repositories that use the Automational pull requests, merge those pull requests. 1.2 times faster. And the number of pooled merged pull requests increased by 1.3 times, that is 34% more poor requests merged. And other words, automation can con can dramatically increase, but the speed and quantity of work completed in any role, just like an open source development, you'll work more efficiently with greater impact when you invest the bulk of your time in the work that adds the most value and eliminate or outsource the rest because you don't need to do it, make the machines by elaborate by leveraging automation in their workflows teams, minimize manual work and reclaim that time for innovation and maintain that state of flow with development and collaboration. More importantly, their work is more enjoyable because they're not wasting the time doing the things that the machines or robots can do for them. >>And I remember what I said at the beginning. Many of us want to be efficient, heck even lazy. So why would I spend my time doing something I can automate? Now you can read more about this research behind the art behind this at October set, get hub.com, which also includes a lot of other cool info about the open source ecosystem and how it's evolving. Speaking of the open source ecosystem we at get hub are so honored to be the home of more than 65 million developers who build software together for everywhere across the globe. Today, we're seeing software development taking shape as the world's largest team sport, where development teams collaborate, build and ship products. It's no longer a solo effort like it was for me. You don't have to take my word for it. Check out this globe. This globe shows real data. Every speck of light you see here represents a contribution to an open source project, somewhere on earth. >>These arts reach across continents, cultures, and other divides. It's distributed collaboration at its finest. 20 years ago, we had no concept of dev ops, SecOps and lots, or the new ops that are going to be happening. But today's development and ops teams are connected like ever before. This is only going to continue to evolve at a rapid pace, especially as we continue to empower the next hundred million developers, automation helps us focus on what's important and to greatly accelerate innovation. Just this past year, we saw some of the most groundbreaking technological advancements and achievements I'll say ever, including critical COVID-19 vaccine trials, as well as the first power flight on Mars. This past month, these breakthroughs were only possible because of the interconnected collaborative open source communities on get hub and the amazing tools and workflows that empower us all to create and innovate. Let's continue building, integrating, and automating. So we collectively can give developers the experience. They deserve all of the automation and beautiful eye UIs that we can muster so they can continue to build the things that truly do change the world. Thank you again for having me today, Dr. Khan, it has been a pleasure to be here with all you nerds. >>Hello. I'm Justin. Komack lovely to see you here. Talking to developers, their world is getting much more complex. Developers are being asked to do everything security ops on goal data analysis, all being put on the rockers. Software's eating the world. Of course, and this all make sense in that view, but they need help. One team. I told you it's shifted all our.net apps to run on Linux from windows, but their developers found the complexity of Docker files based on the Linux shell scripts really difficult has helped make these things easier for your teams. Your ones collaborate more in a virtual world, but you've asked us to make this simpler and more lightweight. You, the developers have asked for a paved road experience. You want things to just work with a simple options to be there, but it's not just the paved road. You also want to be able to go off-road and do interesting and different things. >>Use different components, experiments, innovate as well. We'll always offer you both those choices at different times. Different developers want different things. It may shift for ones the other paved road or off road. Sometimes you want reliability, dependability in the zone for day to day work, but sometimes you have to do something new, incorporate new things in your pipeline, build applications for new places. Then you knew those off-road abilities too. So you can really get under the hood and go and build something weird and wonderful and amazing. That gives you new options. Talk as an independent choice. We don't own the roads. We're not pushing you into any technology choices because we own them. We're really supporting and driving open standards, such as ISEI working opensource with the CNCF. We want to help you get your applications from your laptops, the clouds, and beyond, even into space. >>Let's talk about the key focus areas, that frame, what DACA is doing going forward. These are simplicity, sharing, flexibility, trusted content and care supply chain compared to building where the underlying kernel primitives like namespaces and Seagraves the original Docker CLI was just amazing Docker engine. It's a magical experience for everyone. It really brought those innovations and put them in a world where anyone would use that, but that's not enough. We need to continue to innovate. And it was trying to get more done faster all the time. And there's a lot more we can do. We're here to take complexity away from deeply complicated underlying things and give developers tools that are just amazing and magical. One of the area we haven't done enough and make things magical enough that we're really planning around now is that, you know, Docker images, uh, they're the key parts of your application, but you know, how do I do something with an image? How do I, where do I attach volumes with this image? What's the API. Whereas the SDK for this image, how do I find an example or docs in an API driven world? Every bit of software should have an API and an API description. And our vision is that every container should have this API description and the ability for you to understand how to use it. And it's all a seamless thing from, you know, from your code to the cloud local and remote, you can, you can use containers in this amazing and exciting way. >>One thing I really noticed in the last year is that companies that started off remote fast have constant collaboration. They have zoom calls, apron all day terminals, shattering that always working together. Other teams are really trying to learn how to do this style because they didn't start like that. We used to walk around to other people's desks or share services on the local office network. And it's very difficult to do that anymore. You want sharing to be really simple, lightweight, and informal. Let me try your container or just maybe let's collaborate on this together. Um, you know, fast collaboration on the analysts, fast iteration, fast working together, and he wants to share more. You want to share how to develop environments, not just an image. And we all work by seeing something someone else in our team is doing saying, how can I do that too? I can, I want to make that sharing really, really easy. Ben's going to talk about this more in the interest of one minute. >>We know how you're excited by apple. Silicon and gravis are not excited because there's a new architecture, but excited because it's faster, cooler, cheaper, better, and offers new possibilities. The M one support was the most asked for thing on our public roadmap, EFA, and we listened and share that we see really exciting possibilities, usership arm applications, all the way from desktop to production. We know that you all use different clouds and different bases have deployed to, um, you know, we work with AWS and Azure and Google and more, um, and we want to help you ship on prime as well. And we know that you use huge number of languages and the containers help build applications that use different languages for different parts of the application or for different applications, right? You can choose the best tool. You have JavaScript hat or everywhere go. And re-ask Python for data and ML, perhaps getting excited about WebAssembly after hearing about a cube con, you know, there's all sorts of things. >>So we need to make that as easier. We've been running the whole month of Python on the blog, and we're doing a month of JavaScript because we had one specific support about how do I best put this language into production of that language into production. That detail is important for you. GPS have been difficult to use. We've added GPS suppose in desktop for windows, but we know there's a lot more to do to make the, how multi architecture, multi hardware, multi accelerator world work better and also securely. Um, so there's a lot more work to do to support you in all these things you want to do. >>How do we start building a tenor has applications, but it turns out we're using existing images as components. I couldn't assist survey earlier this year, almost half of container image usage was public images rather than private images. And this is growing rapidly. Almost all software has open source components and maybe 85% of the average application is open source code. And what you're doing is taking whole container images as modules in your application. And this was always the model with Docker compose. And it's a model that you're already et cetera, writing you trust Docker, official images. We know that they might go to 25% of poles on Docker hub and Docker hub provides you the widest choice and the best support that trusted content. We're talking to people about how to make this more helpful. We know, for example, that winter 69 four is just showing us as support, but the image doesn't yet tell you that we're working with canonical to improve messaging from specific images about left lifecycle and support. >>We know that you need more images, regularly updated free of vulnerabilities, easy to use and discover, and Donnie and Marie neuro, going to talk about that more this last year, the solar winds attack has been in the, in the news. A lot, the software you're using and trusting could be compromised and might be all over your organization. We need to reduce the risk of using vital open-source components. We're seeing more software supply chain attacks being targeted as the supply chain, because it's often an easier place to attack and production software. We need to be able to use this external code safely. We need to, everyone needs to start from trusted sources like photography images. They need to scan for known vulnerabilities using Docker scan that we built in partnership with sneak and lost DockerCon last year, we need just keep updating base images and dependencies, and we'll, we're going to help you have the control and understanding about your images that you need to do this. >>And there's more, we're also working on the nursery V2 project in the CNCF to revamp container signings, or you can tell way or software comes from we're working on tooling to make updates easier, and to help you understand and manage all the principals carrier you're using security is a growing concern for all of us. It's really important. And we're going to help you work with security. We can't achieve all our dreams, whether that's space travel or amazing developer products ever see without deep partnerships with our community to cloud is RA and the cloud providers aware most of you ship your occasion production and simple routes that take your work and deploy it easily. Reliably and securely are really important. Just get into production simply and easily and securely. And we've done a bunch of work on that. And, um, but we know there's more to do. >>The CNCF on the open source cloud native community are an amazing ecosystem of creators and lovely people creating an amazing strong community and supporting a huge amount of innovation has its roots in the container ecosystem and his dreams beyond that much of the innovation is focused around operate experience so far, but developer experience is really a growing concern in that community as well. And we're really excited to work on that. We also uses appraiser tool. Then we know you do, and we know that you want it to be easier to use in your environment. We just shifted Docker hub to work on, um, Kubernetes fully. And, um, we're also using many of the other projects are Argo from atheists. We're spending a lot of time working with Microsoft, Amazon right now on getting natural UV to ready to ship in the next few. That's a really detailed piece of collaboration we've been working on for a long term. Long time is really important for our community as the scarcity of the container containers and, um, getting content for you, working together makes us stronger. Our community is made up of all of you have. Um, it's always amazing to be reminded of that as a huge open source community that we already proud to work with. It's an amazing amount of innovation that you're all creating and where perhaps it, what with you and share with you as well. Thank you very much. And thank you for being here. >>Really excited to talk to you today and share more about what Docker is doing to help make you faster, make your team faster and turn your application delivery into something that makes you a 10 X team. What we're hearing from you, the developers using Docker everyday fits across three common themes that we hear consistently over and over. We hear that your time is super important. It's critical, and you want to move faster. You want your tools to get out of your way, and instead to enable you to accelerate and focus on the things you want to be doing. And part of that is that finding great content, great application components that you can incorporate into your apps to move faster is really hard. It's hard to discover. It's hard to find high quality content that you can trust that, you know, passes your test and your configuration needs. >>And it's hard to create good content as well. And you're looking for more safety, more guardrails to help guide you along that way so that you can focus on creating value for your company. Secondly, you're telling us that it's a really far to collaborate effectively with your team and you want to do more, to work more effectively together to help your tools become more and more seamless to help you stay in sync, both with yourself across all of your development environments, as well as with your teammates so that you can more effectively collaborate together. Review each other's work, maintain things and keep them in sync. And finally, you want your applications to run consistently in every single environment, whether that's your local development environment, a cloud-based development environment, your CGI pipeline, or the cloud for production, and you want that micro service to provide that consistent experience everywhere you go so that you have similar tools, similar environments, and you don't need to worry about things getting in your way, but instead things make it easy for you to focus on what you wanna do and what Docker is doing to help solve all of these problems for you and your colleagues is creating a collaborative app dev platform. >>And this collaborative application development platform consists of multiple different pieces. I'm not going to walk through all of them today, but the overall view is that we're providing all the tooling you need from the development environment, to the container images, to the collaboration services, to the pipelines and integrations that enable you to focus on making your applications amazing and changing the world. If we start zooming on a one of those aspects, collaboration we hear from developers regularly is that they're challenged in synchronizing their own setups across environments. They want to be able to duplicate the setup of their teammates. Look, then they can easily get up and running with the same applications, the same tooling, the same version of the same libraries, the same frameworks. And they want to know if their applications are good before they're ready to share them in an official space. >>They want to collaborate on things before they're done, rather than feeling like they have to officially published something before they can effectively share it with others to work on it, to solve this. We're thrilled today to announce Docker, dev environments, Docker, dev environments, transform how your team collaborates. They make creating, sharing standardized development environments. As simple as a Docker poll, they make it easy to review your colleagues work without affecting your own work. And they increase the reproducibility of your own work and decreased production issues in doing so because you've got consistent environments all the way through. Now, I'm going to pass it off to our principal product manager, Ben Gotch to walk you through more detail on Docker dev environments. >>Hi, I'm Ben. I work as a principal program manager at DACA. One of the areas that doc has been looking at to see what's hard today for developers is sharing changes that you make from the inner loop where the inner loop is a better development, where you write code, test it, build it, run it, and ultimately get feedback on those changes before you merge them and try and actually ship them out to production. Most amount of us build this flow and get there still leaves a lot of challenges. People need to jump between branches to look at each other's work. Independence. Dependencies can be different when you're doing that and doing this in this new hybrid wall of work. Isn't any easier either the ability to just save someone, Hey, come and check this out. It's become much harder. People can't come and sit down at your desk or take your laptop away for 10 minutes to just grab and look at what you're doing. >>A lot of the reason that development is hard when you're remote, is that looking at changes and what's going on requires more than just code requires all the dependencies and everything you've got set up and that complete context of your development environment, to understand what you're doing and solving this in a remote first world is hard. We wanted to look at how we could make this better. Let's do that in a way that let you keep working the way you do today. Didn't want you to have to use a browser. We didn't want you to have to use a new idea. And we wanted to do this in a way that was application centric. We wanted to let you work with all the rest of the application already using C for all the services and all those dependencies you need as part of that. And with that, we're excited to talk more about docket developer environments, dev environments are new part of the Docker experience that makes it easier you to get started with your whole inner leap, working inside a container, then able to share and collaborate more than just the code. >>We want it to enable you to share your whole modern development environment, your whole setup from DACA, with your team on any operating system, we'll be launching a limited beta of dev environments in the coming month. And a GA dev environments will be ID agnostic and supporting composts. This means you'll be able to use an extend your existing composed files to create your own development environment in whatever idea, working in dev environments designed to be local. First, they work with Docker desktop and say your existing ID, and let you share that whole inner loop, that whole development context, all of your teammates in just one collect. This means if you want to get feedback on the working progress change or the PR it's as simple as opening another idea instance, and looking at what your team is working on because we're using compose. You can just extend your existing oppose file when you're already working with, to actually create this whole application and have it all working in the context of the rest of the services. >>So it's actually the whole environment you're working with module one service that doesn't really understand what it's doing alone. And with that, let's jump into a quick demo. So you can see here, two dev environments up and running. First one here is the same container dev environment. So if I want to go into that, let's see what's going on in the various code button here. If that one open, I can get straight into my application to start making changes inside that dev container. And I've got all my dependencies in here, so I can just run that straight in that second application I have here is one that's opened up in compose, and I can see that I've also got my backend, my front end and my database. So I've got all my services running here. So if I want, I can open one or more of these in a dev environment, meaning that that container has the context that dev environment has the context of the whole application. >>So I can get back into and connect to all the other services that I need to test this application properly, all of them, one unit. And then when I've made my changes and I'm ready to share, I can hit my share button type in the refund them on to share that too. And then give that image to someone to get going, pick that up and just start working with that code and all my dependencies, simple as putting an image, looking ahead, we're going to be expanding development environments, more of your dependencies for the whole developer worst space. We want to look at backing up and letting you share your volumes to make data science and database setups more repeatable and going. I'm still all of this under a single workspace for your team containing images, your dev environments, your volumes, and more we've really want to allow you to create a fully portable Linux development environment. >>So everyone you're working with on any operating system, as I said, our MVP we're coming next month. And that was for vs code using their dev container primitive and more support for other ideas. We'll follow to find out more about what's happening and what's coming up next in the future of this. And to actually get a bit of a deeper dive in the experience. Can we check out the talk I'm doing with Georgie and girl later on today? Thank you, Ben, amazing story about how Docker is helping to make developer teams more collaborative. Now I'd like to talk more about applications while the dev environment is like the workbench around what you're building. The application itself has all the different components, libraries, and frameworks, and other code that make up the application itself. And we hear developers saying all the time things like, how do they know if their images are good? >>How do they know if they're secure? How do they know if they're minimal? How do they make great images and great Docker files and how do they keep their images secure? And up-to-date on every one of those ties into how do I create more trust? How do I know that I'm building high quality applications to enable you to do this even more effectively than today? We are pleased to announce the DACA verified polisher program. This broadens trusted content by extending beyond Docker official images, to give you more and more trusted building blocks that you can incorporate into your applications. It gives you confidence that you're getting what you expect because Docker verifies every single one of these publishers to make sure they are who they say they are. This improves our secure supply chain story. And finally it simplifies your discovery of the best building blocks by making it easy for you to find things that you know, you can trust so that you can incorporate them into your applications and move on and on the right. You can see some examples of the publishers that are involved in Docker, official images and our Docker verified publisher program. Now I'm pleased to introduce you to marina. Kubicki our senior product manager who will walk you through more about what we're doing to create a better experience for you around trust. >>Thank you, Dani, >>Mario Andretti, who is a famous Italian sports car driver. One said that if everything feels under control, you're just not driving. You're not driving fast enough. Maya Andretti is not a software developer and a software developers. We know that no matter how fast we need to go in order to drive the innovation that we're working on, we can never allow our applications to spin out of control and a Docker. As we continue talking to our, to the developers, what we're realizing is that in order to reach that speed, the developers are the, the, the development community is looking for the building blocks and the tools that will, they will enable them to drive at the speed that they need to go and have the trust in those building blocks. And in those tools that they will be able to maintain control over their applications. So as we think about some of the things that we can do to, to address those concerns, uh, we're realizing that we can pursue them in a number of different venues, including creating reliable content, including creating partnerships that expands the options for the reliable content. >>Um, in order to, in a we're looking at creating integrations, no link security tools, talk about the reliable content. The first thing that comes to mind are the Docker official images, which is a program that we launched several years ago. And this is a set of curated, actively maintained, open source images that, uh, include, uh, operating systems and databases and programming languages. And it would become immensely popular for, for, for creating the base layers of, of the images of, of the different images, images, and applications. And would we realizing that, uh, many developers are, instead of creating something from scratch, basically start with one of the official images for their basis, and then build on top of that. And this program has become so popular that it now makes up a quarter of all of the, uh, Docker poles, which essentially ends up being several billion pulse every single month. >>As we look beyond what we can do for the open source. Uh, we're very ability on the open source, uh, spectrum. We are very excited to announce that we're launching the Docker verified publishers program, which is continuing providing the trust around the content, but now working with, uh, some of the industry leaders, uh, in multiple, in multiple verticals across the entire technology technical spec, it costs entire, uh, high tech in order to provide you with more options of the images that you can use for building your applications. And it still comes back to trust that when you are searching for content in Docker hub, and you see the verified publisher badge, you know, that this is, this is the content that, that is part of the, that comes from one of our partners. And you're not running the risk of pulling the malicious image from an employee master source. >>As we look beyond what we can do for, for providing the reliable content, we're also looking at some of the tools and the infrastructure that we can do, uh, to create a security around the content that you're creating. So last year at the last ad, the last year's DockerCon, we announced partnership with sneak. And later on last year, we launched our DACA, desktop and Docker hub vulnerability scans that allow you the options of writing scans in them along multiple points in your dev cycle. And in addition to providing you with information on the vulnerability on, on the vulnerabilities, in, in your code, uh, it also provides you with a guidance on how to re remediate those vulnerabilities. But as we look beyond the vulnerability scans, we're also looking at some of the other things that we can do, you know, to, to, to, uh, further ensure that the integrity and the security around your images, your images, and with that, uh, later on this year, we're looking to, uh, launch the scope, personal access tokens, and instead of talking about them, I will simply show you what they look like. >>So if you can see here, this is my page in Docker hub, where I've created a four, uh, tokens, uh, read-write delete, read, write, read only in public read in public creeper read only. So, uh, earlier today I went in and I, I logged in, uh, with my read only token. And when you see, when I'm going to pull an image, it's going to allow me to pull an image, not a problem success. And then when I do the next step, I'm going to ask to push an image into the same repo. Uh, would you see is that it's going to give me an error message saying that they access is denied, uh, because there is an additional authentication required. So these are the things that we're looking to add to our roadmap. As we continue thinking about the things that we can do to provide, um, to provide additional building blocks, content, building blocks, uh, and, and, and tools to build the trust so that our DACA developer and skinned code faster than Mario Andretti could ever imagine. Uh, thank you to >>Thank you, marina. It's amazing what you can do to improve the trusted content so that you can accelerate your development more and move more quickly, move more collaboratively and build upon the great work of others. Finally, we hear over and over as that developers are working on their applications that they're looking for, environments that are consistent, that are the same as production, and that they want their applications to really run anywhere, any environment, any architecture, any cloud one great example is the recent announcement of apple Silicon. We heard from developers on uproar that they needed Docker to be available for that architecture before they could add those to it and be successful. And we listened. And based on that, we are pleased to share with you Docker, desktop on apple Silicon. This enables you to run your apps consistently anywhere, whether that's developing on your team's latest dev hardware, deploying an ARM-based cloud environments and having a consistent architecture across your development and production or using multi-year architecture support, which enables your whole team to collaborate on its application, using private repositories on Docker hub, and thrilled to introduce you to Hughie cower, senior director for product management, who will walk you through more of what we're doing to create a great developer experience. >>Senior director of product management at Docker. And I'd like to jump straight into a demo. This is the Mac mini with the apple Silicon processor. And I want to show you how you can now do an end-to-end arm workflow from my M one Mac mini to raspberry PI. As you can see, we have vs code and Docker desktop installed on a, my, the Mac mini. I have a small example here, and I have a raspberry PI three with an led strip, and I want to turn those LEDs into a moving rainbow. This Dockerfile here, builds the application. We build the image with the Docker, build X command to make the image compatible for all raspberry pies with the arm. 64. Part of this build is built with the native power of the M one chip. I also add the push option to easily share the image with my team so they can give it a try to now Dr. >>Creates the local image with the application and uploads it to Docker hub after we've built and pushed the image. We can go to Docker hub and see the new image on Docker hub. You can also explore a variety of images that are compatible with arm processors. Now let's go to the raspberry PI. I have Docker already installed and it's running Ubuntu 64 bit with the Docker run command. I can run the application and let's see what will happen from there. You can see Docker is downloading the image automatically from Docker hub and when it's running, if it's works right, there are some nice colors. And with that, if we have an end-to-end workflow for arm, where continuing to invest into providing you a great developer experience, that's easy to install. Easy to get started with. As you saw in the demo, if you're interested in the new Mac, mini are interested in developing for our platforms in general, we've got you covered with the same experience you've come to expect from Docker with over 95,000 arm images on hub, including many Docker official images. >>We think you'll find what you're looking for. Thank you again to the community that helped us to test the tech previews. We're so delighted to hear when folks say that the new Docker desktop for apple Silicon, it just works for them, but that's not all we've been working on. As Dani mentioned, consistency of developer experience across environments is so important. We're introducing composed V2 that makes compose a first-class citizen in the Docker CLI you no longer need to install a separate composed biter in order to use composed, deploying to production is simpler than ever with the new compose integration that enables you to deploy directly to Amazon ECS or Azure ACI with the same methods you use to run your application locally. If you're interested in running slightly different services, when you're debugging versus testing or, um, just general development, you can manage that all in one place with the new composed service to hear more about what's new and Docker desktop, please join me in the three 15 breakout session this afternoon. >>And now I'd love to tell you a bit more about bill decks and convince you to try it. If you haven't already it's our next gen build command, and it's no longer experimental as shown in the demo with built X, you'll be able to do multi architecture builds, share those builds with your team and the community on Docker hub. With build X, you can speed up your build processes with remote caches or build all the targets in your composed file in parallel with build X bake. And there's so much more if you're using Docker, desktop or Docker, CE you can use build X checkout tonus is talk this afternoon at three 45 to learn more about build X. And with that, I hope everyone has a great Dr. Khan and back over to you, Donnie. >>Thank you UA. It's amazing to hear about what we're doing to create a better developer experience and make sure that Docker works everywhere you need to work. Finally, I'd like to wrap up by showing you everything that we've announced today and everything that we've done recently to make your lives better and give you more and more for the single price of your Docker subscription. We've announced the Docker verified publisher program we've announced scoped personal access tokens to make it easier for you to have a secure CCI pipeline. We've announced Docker dev environments to improve your collaboration with your team. Uh, we shared with you Docker, desktop and apple Silicon, to make sure that, you know, Docker runs everywhere. You need it to run. And we've announced Docker compose version two, finally making it a first-class citizen amongst all the other great Docker tools. And we've done so much more recently as well from audit logs to advanced image management, to compose service profiles, to improve where you can run Docker more easily. >>Finally, as we look forward, where we're headed in the upcoming year is continuing to invest in these themes of helping you build, share, and run modern apps more effectively. We're going to be doing more to help you create a secure supply chain with which only grows more and more important as time goes on. We're going to be optimizing your update experience to make sure that you can easily understand the current state of your application, all its components and keep them all current without worrying about breaking everything as you're doing. So we're going to make it easier for you to synchronize your work. Using cloud sync features. We're going to improve collaboration through dev environments and beyond, and we're going to do make it easy for you to run your microservice in your environments without worrying about things like architecture or differences between those environments. Thank you so much. I'm thrilled about what we're able to do to help make your lives better. And now you're going to be hearing from one of our customers about what they're doing to launch their business with Docker >>I'm Matt Falk, I'm the head of engineering and orbital insight. And today I want to talk to you a little bit about data from space. So who am I like many of you, I'm a software developer and a software developer about seven companies so far, and now I'm a head of engineering. So I spend most of my time doing meetings, but occasionally I'll still spend time doing design discussions, doing code reviews. And in my free time, I still like to dabble on things like project oiler. So who's Oberlin site. What do we do? Portal insight is a large data supplier and analytics provider where we take data geospatial data anywhere on the planet, any overhead sensor, and translate that into insights for the end customer. So specifically we have a suite of high performance, artificial intelligence and machine learning analytics that run on this geospatial data. >>And we build them to specifically determine natural and human service level activity anywhere on the planet. What that really means is we take any type of data associated with a latitude and longitude and we identify patterns so that we can, so we can detect anomalies. And that's everything that we do is all about identifying those patterns to detect anomalies. So more specifically, what type of problems do we solve? So supply chain intelligence, this is one of the use cases that we we'd like to talk about a lot. It's one of our main primary verticals that we go after right now. And as Scott mentioned earlier, this had a huge impact last year when COVID hit. So specifically supply chain intelligence is all about identifying movement patterns to and from operating facilities to identify changes in those supply chains. How do we do this? So for us, we can do things where we track the movement of trucks. >>So identifying trucks, moving from one location to another in aggregate, same thing we can do with foot traffic. We can do the same thing for looking at aggregate groups of people moving from one location to another and analyzing their patterns of life. We can look at two different locations to determine how people are moving from one location to another, or going back and forth. All of this is extremely valuable for detecting how a supply chain operates and then identifying the changes to that supply chain. As I said last year with COVID, everything changed in particular supply chains changed incredibly, and it was hugely important for customers to know where their goods or their products are coming from and where they were going, where there were disruptions in their supply chain and how that's affecting their overall supply and demand. So to use our platform, our suite of tools, you can start to gain a much better picture of where your suppliers or your distributors are going from coming from or going to. >>So what's our team look like? So my team is currently about 50 engineers. Um, we're spread into four different teams and the teams are structured like this. So the first team that we have is infrastructure engineering and this team largely deals with deploying our Dockers using Kubernetes. So this team is all about taking Dockers, built by other teams, sometimes building the Dockers themselves and putting them into our production system, our platform engineering team, they produce these microservices. So they produce microservice, Docker images. They develop and test with them locally. Their entire environments are dockerized. They produce these doctors, hand them over to him for infrastructure engineering to be deployed. Similarly, our product engineering team does the same thing. They develop and test with Dr. Locally. They also produce a suite of Docker images that the infrastructure team can then deploy. And lastly, we have our R and D team, and this team specifically produces machine learning algorithms using Nvidia Docker collectively, we've actually built 381 Docker repositories and 14 million. >>We've had 14 million Docker pools over the lifetime of the company, just a few stats about us. Um, but what I'm really getting to here is you can see actually doctors becoming almost a form of communication between these teams. So one of the paradigms in software engineering that you're probably familiar with encapsulation, it's really helpful for a lot of software engineering problems to break the problem down, isolate the different pieces of it and start building interfaces between the code. This allows you to scale different pieces of the platform or different pieces of your code in different ways that allows you to scale up certain pieces and keep others at a smaller level so that you can meet customer demands. And for us, one of the things that we can largely do now is use Dockers as that interface. So instead of having an entire platform where all teams are talking to each other, and everything's kind of, mishmashed in a monolithic application, we can now say this team is only able to talk to this team by passing over a particular Docker image that defines the interface of what needs to be built before it passes to the team and really allows us to scalp our development and be much more efficient. >>Also, I'd like to say we are hiring. Um, so we have a number of open roles. We have about 30 open roles in our engineering team that we're looking to fill by the end of this year. So if any of this sounds really interesting to you, please reach out after the presentation. >>So what does our platform do? Really? Our platform allows you to answer any geospatial question, and we do this at three different inputs. So first off, where do you want to look? So we did this as what we call an AOI or an area of interest larger. You can think of this as a polygon drawn on the map. So we have a curated data set of almost 4 million AOIs, which you can go and you can search and use for your analysis, but you're also free to build your own. Second question is what you want to look for. We do this with the more interesting part of our platform of our machine learning and AI capabilities. So we have a suite of algorithms that automatically allow you to identify trucks, buildings, hundreds of different types of aircraft, different types of land use, how many people are moving from one location to another different locations that people in a particular area are moving to or coming from all of these different analyses or all these different analytics are available at the click of a button, and then determine what you want to look for. >>Lastly, you determine when you want to find what you're looking for. So that's just, uh, you know, do you want to look for the next three hours? Do you want to look for the last week? Do you want to look every month for the past two, whatever the time cadence is, you decide that you hit go and out pops a time series, and that time series tells you specifically where you want it to look what you want it to look for and how many, or what percentage of the thing you're looking for appears in that area. Again, we do all of this to work towards patterns. So we use all this data to produce a time series from there. We can look at it, determine the patterns, and then specifically identify the anomalies. As I mentioned with supply chain, this is extremely valuable to identify where things change. So we can answer these questions, looking at a particular operating facility, looking at particular, what is happening with the level of activity is at that operating facility where people are coming from, where they're going to, after visiting that particular facility and identify when and where that changes here, you can just see it's a picture of our platform. It's actually showing all the devices in Manhattan, um, over a period of time. And it's more of a heat map view. So you can actually see the hotspots in the area. >>So really the, and this is the heart of the talk, but what happened in 2020? So for men, you know, like many of you, 2020 was a difficult year COVID hit. And that changed a lot of what we're doing, not from an engineering perspective, but also from an entire company perspective for us, the motivation really became to make sure that we were lowering our costs and increasing innovation simultaneously. Now those two things often compete with each other. A lot of times you want to increase innovation, that's going to increase your costs, but the challenge last year was how to do both simultaneously. So here's a few stats for you from our team. In Q1 of last year, we were spending almost $600,000 per month on compute costs prior to COVID happening. That wasn't hugely a concern for us. It was a lot of money, but it wasn't as critical as it was last year when we really needed to be much more efficient. >>Second one is flexibility for us. We were deployed on a single cloud environment while we were cloud thought ready, and that was great. We want it to be more flexible. We want it to be on more cloud environments so that we could reach more customers. And also eventually get onto class side networks, extending the base of our customers as well from a custom analytics perspective. This is where we get into our traction. So last year, over the entire year, we computed 54,000 custom analytics for different users. We wanted to make sure that this number was steadily increasing despite us trying to lower our costs. So we didn't want the lowering cost to come as the sacrifice of our user base. Lastly, of particular percentage here that I'll say definitely needs to be improved is 75% of our projects never fail. So this is where we start to get into a bit of stability of our platform. >>Now I'm not saying that 25% of our projects fail the way we measure this is if you have a particular project or computation that runs every day and any one of those runs sale account, that is a failure because from an end-user perspective, that's an issue. So this is something that we know we needed to improve on and we needed to grow and make our platform more stable. I'm going to something that we really focused on last year. So where are we now? So now coming out of the COVID valley, we are starting to soar again. Um, we had, uh, back in April of last year, we had the entire engineering team. We actually paused all development for about four weeks. You had everyone focused on reducing our compute costs in the cloud. We got it down to 200 K over the period of a few months. >>And for the next 12 months, we hit that number every month. This is huge for us. This is extremely important. Like I said, in the COVID time period where costs and operating efficiency was everything. So for us to do that, that was a huge accomplishment last year and something we'll keep going forward. One thing I would actually like to really highlight here, two is what allowed us to do that. So first off, being in the cloud, being able to migrate things like that, that was one thing. And we were able to use there's different cloud services in a more particular, in a more efficient way. We had a very detailed tracking of how we were spending things. We increased our data retention policies. We optimized our processing. However, one additional piece was switching to new technologies on, in particular, we migrated to get lab CICB. >>Um, and this is something that the costs we use Docker was extremely, extremely easy. We didn't have to go build new new code containers or repositories or change our code in order to do this. We were simply able to migrate the containers over and start using a new CIC so much. In fact, that we were able to do that migration with three engineers in just two weeks from a cloud environment and flexibility standpoint, we're now operating in two different clouds. We were able to last night, I've over the last nine months to operate in the second cloud environment. And again, this is something that Docker helped with incredibly. Um, we didn't have to go and build all new interfaces to all new, different services or all different tools in the next cloud provider. All we had to do was build a base cloud infrastructure that ups agnostic the way, all the different details of the cloud provider. >>And then our doctors just worked. We can move them to another environment up and running, and our platform was ready to go from a traction perspective. We're about a third of the way through the year. At this point, we've already exceeded the amount of customer analytics we produce last year. And this is thanks to a ton more albums, that whole suite of new analytics that we've been able to build over the past 12 months and we'll continue to build going forward. So this is really, really great outcome for us because we were able to show that our costs are staying down, but our analytics and our customer traction, honestly, from a stability perspective, we improved from 75% to 86%, not quite yet 99 or three nines or four nines, but we are getting there. Um, and this is actually thanks to really containerizing and modularizing different pieces of our platform so that we could scale up in different areas. This allowed us to increase that stability. This piece of the code works over here, toxin an interface to the rest of the system. We can scale this piece up separately from the rest of the system, and that allows us much more easily identify issues in the system, fix those and then correct the system overall. So basically this is a summary of where we were last year, where we are now and how much more successful we are now because of the issues that we went through last year and largely brought on by COVID. >>But that this is just a screenshot of the, our, our solution actually working on supply chain. So this is in particular, it is showing traceability of a distribution warehouse in salt lake city. It's right in the center of the screen here. You can see the nice kind of orange red center. That's a distribution warehouse and all the lines outside of that, all the dots outside of that are showing where people are, where trucks are moving from that location. So this is really helpful for supply chain companies because they can start to identify where their suppliers are, are coming from or where their distributors are going to. So with that, I want to say, thanks again for following along and enjoy the rest of DockerCon.

>> From theCUBE studios in Palo Alto, in Boston bringing you data-driven insights from theCUBE and ETR. This is breaking analysis with Dave Vellante. >> SaaS companies have been some of the strongest performers in this COVID era. They finally took a bit of a breather this month, but they remain generally well-positioned for the next several years with their predictable models and cloud platforms. Meanwhile, the demise of on-prem legacy players from COVID shock, seems to have been overstated, in part because of the return of the laptop and in the case of Oracle with some see as a cloud play, Hmm. Then there's Bitcoin which is seeing public companies use their balance sheet liquidity to invest in the cryptocurrency. (chuckles) Wow. What does that all mean? I'll leave that for another day. Hello everyone and welcome to this week on Cube insights powered by ETR. On this breaking analysis, we'll pick out some of the more recent themes from this month and share our thoughts in some major enterprise software players, the future of on-prem, a review of our take on cloud and what cloud will look like in the 2020s. Wow. It's true, trees really don't grow to the moon. As predicted, the stock market has been a little bit crazy this month. February saw some leading SaaS names like Workday, Salesforce, and ServiceNow take a bit of a breather in the second half of the month. Workday and Salesforce announced earnings on the 25th. Workday had its first billion dollar subscription revenue quarter at 16% revenue growth a revenue and earnings beat. And of course the stock closed down Friday, more than 2%. Salesforce had a nearly $6 billion revenue quarter 20% growth, a revenue and earnings beat. And the day after it announced earnings the stock was down more than 6%. The market is worried about rising interest rates, and maybe concerned that an inflation fears are going to kill the stimulus bill. And so any whiff of caution by company managements is met with dampened enthusiasm. Meanwhile, it's looking like some of the big on-prem legacy firms, notably Dell, HPQ and HPE are making it through COVID, and might even come out in the other side stronger maybe. Dell handily beat expectations on the 25th on the strength of 17% growth in its client business. That's PCs. It's the gift that keeps on giving. HPQ had a strong beat as well, and we're anticipating a solid quarter from HPE next week on March 2nd. And then there's Oracle. Barron's had a big article on February 19th, entitled, "Oracle is turning into a cloud giant and why it's stock is a buy". It moved the market. And many investors rotated out of growth stocks, tech growth tech stocks into Oracle, others who had owned Oracle for a while scooped up some profits. Is Oracle a cloud giant? Hmm. We'll discuss that in a moment. And then there's all this Bitcoin mania. You know, our interest there is much more beyond the price fluctuations rather we're interested in the innovations in crypto. Look, we're going to table this for another day, but it's an interesting side note of this February madness. Let's take a look closer look at the February chill for SaaS companies. Here's a chart showing the relative performance of some of the big SaaS names in the latter half of this month. Now despite the strong earnings for Workday and Salesforce you can see the market's negative response on the 26th. Snowflake and ServiceNow they had epic runs last year, and they've been softening although on Friday morning ServiceNow shut down quickly on the open on sympathy with Workday and ServiceNow and then investors, you know, came back in. Very weird action in the market these days, again, not surprising. And look at the reaction investors had to the Barron's article on the 19th. They anointed Oracle as a cloud giant. Kudos to the Oracle PR team for that one. Now, let's take a look at these companies and put them in context. Even though they're not direct competitors it's instructive to model some of the top enterprise software players in positions, and line them up against each other. This chart here shows two dimensions from the ETR data. On the vertical axis is net score or customer spending momentum. And the horizontal axis is market share or pervasiveness in the survey. The table inset shows the net score measurement in the shared end. That's the metric that plots the dots. In both cases bigger is better. Note, that red dotted-line there is the 40% line. 40% to us is the magic number. Anything above that line is considered elevated. So we have ServiceNow and Salesforce they're up to the right. They're both big companies. They have significant market presence amongst the CIO and both have elevated spending velocity in the 50% range. And I've said for years, these two companies are on a collision course and I stand by that. It started happening and McDermott Bill McDermott, new CEO he's going to accelerate that in our view. We put a cloud around Snowflake tongue in cheek, because they are literally in the clouds on this chart. They stand alone, with a solid market presence that continues to grow in an off the charts net score of 83.3% now. For context you can see Oracle Fusion, NetSuite and Taleo. In addition, we put Slack and Coupa on the graphic, two names that have been on the radar lately and SAP, which continues to show decent spending momentum despite its challenges. All right, let me make a few comments on some of these companies. Snowflake, we've talked about a lot. I said earlier that their IPO, that if you really wanted to own it and couldn't wait for a better price, which I thought you'd get. And by the way you did, but then if you really wanted to own it on day one hold your nose and buy it and then wait a few years. So, you know, good luck. And I think you'll, it'll turn out okay for you. Now, the data really continues to show strong demand for Snowflake. There's no signs of them slowing down. So they announced earnings on March 3rd. We didn't have more data there. So we would expect confirmation of our analysis but you never know. Now Workday, here's our take. In our view the market is catching up to Workday. They had about a three-year lead at least in human capital management and the cloud and that whole model. And they had the best product. It was really simple and it was quite disruptive. But now you got Oracle, ADP, Ceridian they're catching up. Workday's expansion into financial management has been much more challenging and as it gets bigger, things get tougher. It's still though an enduring name. Salesforce, we see a bit differently. Salesforce is so big now, it's really hard for it to move the needle. And so it's been on an acquisition binge, and to grow that's likely going to continue. It could work well for the company. I mean, similar to the ways in which Oracle consolidated software names and picked up a lot of customers. Salesforce is a great name, and we think is going to continue to grow. ServiceNow is interesting. It's entering a new chapter under CEO, Bill McDermott, new CEO. He wants to double the company's revenue. And I think he's got a reasonable chance at that through a combination of great go-to-market and expanding the platform and in McDermott style doing acquisitions. SAP's market value tripled under his watch, and he knows the customers. And he's a magnet for attracting talent. Now ServiceNow is not without its challenges. Its customers often complain that ServiceNow is pricing is really high and it's becoming the Oracle of service management. But as McDermott aims more at SAP and Oracle customers, they create a nice umbrella for ServiceNow to work with. And technically, we think ServiceNow has other challenges around its multi-instance. We call it, if you can't fix it feature it architecture. That may present some issues down the road at scale. We don't have time to go into that in detail but suffice it to say that ServiceNow runs on its own cloud. So it's not running on a hyper scale cloud. Yeah. Good news it doesn't have to pay it through that. The bad news is, has got to manage all that infrastructure. It's basically be a cloud supply supplier but it doesn't do multi-tenant which means fundamentally, it has a more expensive cost structure. Okay. Let's turn our attention to what's happening on-prem with some of the big legacy names. Here's the same X Y chart with some of the big names that have a presence on-prem. First you can see VMware and Cisco, Oracle, Dell, IBM and HP. Look at them on the horizontal scale. They've got a large market share of presence in the ETR dataset. Unlike the larger SaaS companies however, none is above that magic 40% net scoreline. Pure, Dell's laptop business, Red Hat, OpenShift. They're above the line with Nutanix just about there at the line. The other major laptop players, Lenovo and HPQ showing momentum from the whole remote work trend. And for context, we put in NetApp so you can get a sense of where they're at. Pure beat its earnings last week but only grew 2% last quarter. Now remember the ETR survey, this is a forward-looking survey. So this potentially bodes well for the companies that are above that 40% line. Okay. So most so sorry of the companies on this chart only IBM and Oracle, those two own a public cloud. And we'll dig further into that in a moment, but virtually every name shown here, even Oracle has a mandate to redefine cloud. Meaning it has to put forth in our view in North star vision and execute on it. That will unify the experience between on-prem, hybrid cloud, public clouds, cross clouds and the edge. Now I say even Oracle, because in my view, Oracle is in a stronger position than the others, because of it's more coherent software architecture. Now the other companies on this chart, they have to architect a platform that abstracts the underlying complexity of clouds, leverage cloud native tooling in the respective public clouds. Connect on-prem infrastructure and build a layer, that stretches out and accommodates edge workloads. I think Oracle will follow suit and is actually ahead of most in a narrower context, i.e hybrid. But it doesn't have to race toward this vision. It can sit back as it often does, watch everyone else fumble around and make mistakes. And then Oracle will keep investing in R&D, watch the market, you know make its own experimental mistakes, and then enter the market and act like we invented it. Now, Cisco will come at this from a strong networking and security perspective. And it has a nice story on programmable infrastructure with Cisco DevNet. But unfortunately it does not own VMware as does Dell, but Dell is in the middle of a fairly remarkable journey. And it will be interesting to see what happens with the VMware spin-out and the cozy commercial relationship that Dell is structuring with VMware as you know, and as we've reported, Dell has used VMware's cash for a lot of this restructuring. And so we'll see, as it exits the current phase and enters a new phase, how it will be able to pursue that vision. It's going to be, whatever it does it's going to be much different than that vertically integrated Oracle approach, which of course brings me to IBM. Potentially Red Hat with OpenShift is the most powerful card in the deck right now. OpenShift I mean, it's open it's everywhere. It has momentum as we showed. And I like their position. My concern is IBM, IBM is still unwinding and restructuring its business. And it's taking a long time as we've seen, with its outsourcing business. And now the Watson health assets, Irvine is continuing that downsizing trend that we saw under Ginny, shedding non-strategic businesses that don't fit, Irvine has a lot to deal with. And I want to point out that this idea of an abstraction layer across clouds is not trivial. First, all of these companies have to stop being so defensive about the public cloud. To a large extent, VMware and Red Hat have found a happy place. But in my view, they all should be thanking AWS, Azure, and Google for building out this great global distributed system, that they can leverage and build on top of. And second, this is going to be expensive. And Cisco, Dell VMware, IBM, they're all really stretched thin from an R&D perspective. They a lot of mouths to feed across the portfolio. So is HPE stretched thin, and it doesn't have the R&D budget at less than $2 billion annually. So my concern is that we're going to have lots of complexity across these obstructions layers by vendor. Now maybe the good news for companies. This may be good news for companies like Hashi or specialists with a vision to do this within a domain like a clumial, or a vast data, but this is big, and they are small. So it's going to take the better part of a decade to play out. Now, let's take a quick look at the cloud players. OMG when I saw that article in Barron's last weekend my mouth dropped. What a headline and it had this illustration of a stout Larry Ellison rising above the clouds. Here's a picture of the ETR data for the cloud players. It's the same X, Y plotting or net score and market share. If you follow this program, you know we believe there are four and only four hyper scale cloud players, with the resources to compete and differentiate as horizontal infrastructure players, which really is how we view the origination of modern cloud computing. AWS created it with S3 and EC2 with 2006. Those four are AWS and Azure, which have a large lead over the pack. Google cloud and Alibaba. And you can see we've circled the on-prem pack which comprises Oracle and IBM along with Dell VMware. And we snuck Google just stuck them at the edge of that circle because the differentiate they're cozying up to companies with strong enterprise sales teams and Google's, they're smart, they're patient. And so we, by no means, count them out. They're spending like mad and they have a lot of cash. They've done some really interesting open source things with containers. And so, you know, no doubt they're a player, but they are behind. Now in that on-prem pack, IBM and Oracle they actually own their own public clouds. IBM, they acquired soft layer which was a bare metal hosting company at the time to get IBM into the game. They retooled the platform over several years. Now here's the thing, try and unpack IBM's cloud business looking at its financial or in earnings reports. It's just a mess. I hope Irvine cuts the nonsense and actually develops and reports a set of metrics that are meaningful to cloud observers and IBM observers, because the way IBM reports its cloud business today is opaque and it's nonsense. It's frankly embarrassing to the company. It needs to end sooner rather than later is fundamentally meaningless to any observers. Now observers of cloud. If you care about the big chunk of whatever then maybe it has meaning. Now Oracle for its part, they announced the public cloud years ago, its version of one datto cloud was crap. And the company, they hired a bunch of really smart cloud engineers and they spent a lot of money to fix that. Now neither IBM nor Oracle have the CapEx resources of the big four, not even close, yet they'll build out data centers and yes they'll have a play, but they're different and that's okay. Now in the Barron's article on Oracle, the author was quite positive on Oracle, noting that quote, "On a recent earnings call CEO Safra Catz said that Oracle cloud infrastructure revenue was up 139% for the quarter". So, (laughs) we have really no sense or a stake in the ground is to up from what? Anyway, noting further the author said, quote, "Alas! Oracle doesn't break out OCI sales and comps can be messy". Hmm, indeed. Oracle is hiding the ball on OCI, that's because if they did break it out, which by the way they used to report, AIS revenue explicitly, but if they did break it out, they would only be highlighting that they are a minor player in AIS. Further, the article continues, quote, "Catz says that hers is the only tech company that has both a global cloud and a full set of enterprise applications". Unquote, bingo. There it is. That's why Oracle is in a better position than many of or most of the on-prem players listed in this chart. By the way, I would argue that Microsoft has a pretty impressive set of enterprise applications in a fairly global cloud. But what Safra is talking about is applications that support the world's most mission critical work. And when it comes to that, Oracle is number one. Don't fool yourself and get caught up in the Oracle lock-in and high pricing narrative, thinking that they're going to get crushed. They're not. Oracle is the best in the mission critical workload game. There is no one better, period. But guys, come on. The big four last year grew 41% and accounted for $86 billion in AIS revenue, AKA real cloud revenue. And they're going to surpass $115 billion this year combined. Real cloud companies don't grow in the single digits today. So talk to me when we reach equilibrium on that front. Okay. So let's wrap by looking at what does a cloud company look like in the 2020s? Now, I'm not saying that the rest of the pack shouldn't redefine cloud they should. But I hope we can all agree by now that modern day cloud computing was defined in business terms by AWS. They are number one in cloud computing, make no mistake. However, AWS is bringing the cloud into the wheelhouse of the on-prem players, cleverly saying that it's bringing AWS to the edge and it looks at the data centers. Just another edge node is great positioning but that is not trivial. Just look it out posts and how AWS has had to evolve its pricing strategy in terms, can't just turn it off like you can, the public cloud. I have an entire rant on all the, SaaS service transformations. It's really interesting to watch as AWS goes out, and the on-prem players come in and go hybrid. I got a lot of thought on what's happening there both in terms of SaaS, which I think is an outdated pricing model, and the infrastructure as a service players that are really getting into this game, we would love to do a session on that sometime. And it's a real disruption I think coming. Anyway, AWS competitors should absolutely try to redefine cloud. By AWS moving to the edge, it's opened up the door to that possibility. Microsoft is obviously in the best position I think by far here. They've earned the right and I'll never accuse them of cloud washing. Google, they got some work to do in this regard, but they probably have the largest physical cloud infrastructure in the world. As I've said, they just need to pull their heads out of their ads and quadruple down on cloud. But this idea of abstracting away the underlying complexity of the cloud, leveraging cloud native capabilities and building on top of the shoulders of the cloud giants such as David Floyer has expressed in this chart, moving from stateless to state full, integrating across clouds, advancing automation not only through the stack, but across domains and ultimately using metadata to govern where workloads should live or be moved, be disintegrated and recombined with low latency and be highly secured. I look at this, I think about this and I say one there is this technically feasible and smart techies tell me yes, so I keep trying to dig here for signs and I definitely see some movement in this direction. And two, I don't think any one vendor is going to do this themselves. They're not going to, it's not going to be owned by one company. I think what's going to happen is you'll get successes within layers of the stack. I mean, think about Snowflakes data cloud. We're going to see that for storage. See it for backup, data management, security maybe security within different domains. You see endpoint and identity access management. Maybe that cloud comes together as cloud security. You see it in applications, but without clear standards, it's going to be a challenge. And with respect to my friends at Snowflake, we might even see it in database sometime LOL, but look you all have a lot of work to do. And to my CIO friends, you know the drill much better than I, technology is going to keep relentlessly coming at you and you can deal with that. It's the people and the change management in the culture. Those are your bigger challenges, but don't screw up the tech. Okay. Thanks for watching. Remember, these episodes are all available as podcasts wherever you listen, just search breaking analysis podcasts, and please subscribe to the series, we appreciate that. Check out ETR's website at ETR.plus sorry, ETR.plus. We also publish a full report every week on wikibon.com and siliconangle.com. You can email me at David.Vellante@siliconangle.com or DM me on Twitter at DVellante that's @DVellante or comment, excuse me on my LinkedIn posts. This is Dave Vellante for theCUBE Insights powered by ETR. Stay safe, be well, get the jab if you have an opportunity. And we'll see you next time. (soft music)

>> Good Live from Las Vegas. It's the cute covering knowledge sixteen Brought to you by service. Now carry your host David, Dante and Jeffrey. >> Oh, >> welcome back to knowledge. Sixteen everybody, this is the cubicle wall to wall coverage. We got the events. We extract the signal from the noise. This is Day one for us will be going Three days of knowledge extraction from knowledge. Sixteen. Ray Wong is here. He's the founder and principal analyst and chairman of Consolation Research. Up and coming Smoking Hot research company. Ray, Always a pleasure to see you. Thanks for coming >> on. Excited to be here, man. It's been a world one week of events, so >> I'LL say So you were You were down. It's Sapphire, right? You were over it on Tampa Amplify And >> I'm Austin s Wait after this race, a >> normal week for you >> It's a normal week for all of us. >> So impressed You were telling us off camera that you were at one of the earlier knowledge events down in San Diego. So you've got a lot of experience with this company, >> you know, it was in a tent. It was outside they had detected. I think it's like a park. I'm not even sure what it was. I just But remember, there's one one hundred fifty people next. There's like five hundred people. Three years later, it's pretty wild. >> So they've come out of the blue and really, you know, escalated a lot of momentum. The latest billion dollar software company with a plan to get to four billion. So stepping back a second just looking at the software landscape, one has to be impressed with the progress that service now is made. What's your take on the industry and service now in particular? >> Well, I think what people don't understand this service now is a platform, right? There's a business model platform or the way that we used to look at paga or the way we used to look at a lot of those companies that were actually sit in the middle. That orchestration what's changes? Because everything's in the cloud. What we now have the ability to abstract orchestrating doing away that we've never seen before, right so you can take specific business problems. Take the heart of what's actually happened on the idle piece. Use it to not just manage the process, but also do the analytics and the monitoring. So when we get the things like Coyote coyotes really about having a set of smart services and being well. To put that in the construct is a lot of the opportunity that we see going forward >> so high. So I said three years ago in the Cube after I saw the platform capabilities and said, Wow, this is a collision course with sales force Investor's Business Daily wrote a article today. Collision course of sales for so glad they caught up with Theo. But But, I mean, it's you could kind of see it coming together. And now you Frank lays out this vision this morning. Have you got the AARP estate, the C R M estate and tea or a service management Rather kind of bridging those two. How do you see it? >> No, we definitely see this as a platform play. Now here's what's interesting is the lots of the developments, and you see this all the time has been happening in the APP to have side of the House package. APS have kind of been at a standstill for innovation compared to what's going on on the customs side. And so every so often we see that flip on platforms. This is the beginning of that flip, more than one person said. I it is going to be the end of the affair, right, because we're going to put all the intelligence into the interaction. You don't have to go to the specific app. No. And the fact is, what becomes important is the ability, the orchestration, the intelligence, the recommendation and what you want to build to get to the part where I'm making the right set of recommendations to augment the next set of processes. That's what gets really powerful and these platforms that are emerging on, What's the next set of clouds? That's going to be where we're going to see a lot of this advancement. >> So the FBI essentially becomes the product. Is that kind of? >> It's the orchestration of the AP eyes, the way the context was delivered against those AP eyes and more importantly, how we actually pulled together those journeys, like a couple things that we talk about time mass personalization of scale, lots of context, right, so rolls relationship, identity weather, location, time, all important, Then choose your own adventure journeys the ability to actually abstract different processes from different places and bring them together, and the more importantly, we call intention driven design, which is. I'm gonna give you three or four choices. Learn over time. Take that machine learning. Then apply that the next set of recommendations and then start building against that. And that power sits on the network. That power sits in these new platforms. >> So you're here speaking to the service now customers about customer experience, right? It's something we hear a lot about. Your an expert in that in that space. What did you say? What was the reaction? What was the feedback? >> Well, I think the important thing is we're seeing new business models and you hear me say this before it's we're in a post sale on demand, attention, economy. And what that means is everything after the sale is what's happening right now. That's the service. That's the experience. Peace. The on demand pieces were accessing smaller, smaller slices of a product. Maybe not even a product, a service, maybe not even a service, and incite maybe not even insight and experience. And then, more importantly, it's an attention to come. If you're not capturing my time and attention, which is mind share, or if you're not saving me time and money, I don't care. And That's what we're in. We're in. These business moms are built around. This is interesting. Came out of the Oracle Marketing cloud shows Well, same thing. Just smaller and smaller slices of attention based on the way you interact with all the other applications you have. You don't have time to give somebody the big story. You've got to get him when you can. They could be standing in line. They look at their phones, are in the middle of their kids, switching innings at the baseball game. And you got to get in that little tiny video that in between time is so important because you don't close there. You lose him, right? And it's not for something really big. It's move them along the needle down. The journal. Correct. >> What do you make of this, Dave? Dave Wright was just not talking about the new state of work. IBM has been talking about a new way to work in. He is kind of running the collaboration, you know, group. Now you you talk about millennials and how they work. What are you seeing in state of work? >> Well, a lot of the research we're looking on the future of work is by one of my colleagues, Alain Le Pastilles, and what he's been really looking as this shift in terms of conversations as a service. He's been looking at the shift in terms of intelligent collaboration. Right, and all this stuff is actually leading the point where we're actually using technology to augment ability. Teo do decisions had a lot more automation than we had him before. But then cognitive assistance pop up right and they help make a smarter. And they learned from our different our actions and all that's starting to come into the workplace, which is exciting and a little bit creepy and scary at the same time. >> So what's the What's the What's new with Constellation? You guys are growing. Bring it on. New analyst Cranking out Want to research? Your event keeps growing? Give us the update on Constellation. >> You know, I think the big thing is this digital transformation story we've been talking about for the last five to six years is huge. The next set is really not about transformation. It's about finding growth in times where there is no growth. That's where we're going to talk about the next five years at our conference. Really? Talking about what are those factors, right? We gotta jump start growth. Global GDP is growing two to three percent at best. Every company has a target of like five to ten. Someone's gonna lose, and it's gonna be very interesting. >> So you think that growth is going to come through productivity improvements or investments in technology? Actually, Dr sort of new productivity levels were taking away from >> someone else. I think we're taking me for someone else. That's what I'm really scared about, that they're smart growth that's sustainable and helps people with the jobs and the job transitions. And there's what we've been doing, which a lot of destructive Cross, which is actually limiting all of the jobs and actually making it harder to grow in the long run. >> Well, so yeah, we've talked about this on the Cuba lot machines replacing humans, which they've always replaced humans. But it seems to be now happening at the cognitive level. That's scary. I know you guys to the valley, wags. You know the seasonal nervous right now, You guys, you more sanguine? Then the VCs air >> well with these three big areas where we see a lot of investment. Deep learning happens to be one of them, right? We see a lot of medicine going off. Some of the smartest people I know are all focused and on deep learning. Very interesting thing. If you look at that university, California, Irvine there's a whole department around. This artificial intelligence that just lifted itself up became a private corporation. So there's very unfeeling things there. There's nanotech, which is also some erasers, things on the material science piece that's also playing a big role. And then, of course, there's stem cells in the biotech piece. Those three things are converging, and you know it's more than just building out the Star Trek roadmap that Apple's been doing. It's a lot bigger than that. There's some big societal shift that are happening. >> What, what's next for you? You say you're heading Teo. That's sweet, but we're So we work. We find Ray Juan. I'm >> off this sweet world, Max. There's a monetary it next week. There's a whole bunch of other events picking up in June as well as you. You're going to be at them, but I think we do our retreat every year at the end of the year. May June, we're going to be at Stanford, the faculty club. All the constellation folks get together on. Then we go back out into the field and it's a crazy summer as well. I don't know when this stops making, so yeah, you could always find him on Twitter That that's but I looked for you guys when I'm where you're at is where the events are. >> Well, hopefully our past will continue to cross. We love having you in the Cube was a great guests. Really appreciate your time. Thanks for coming on. >> You know, Thanks for having have a >> great conference. All right. They've travelled, right, everybody. We'LL be back after this short break. This's the Cube or live from knowledge. Sixteen, right? >> Service now is the