(upbeat music) >> Hey everyone, welcome back to Chicago theCUBE is live on the floor at AnsibleFest 2022, the first in-person Ansible event that we've covered since 2019. Lisa Martin here with John Furrier. John, great to be here. There's about 1400 to 1500 people here in person, the partner ecosystem is growing and evolving, and that's going to be one of the themes of our next conversation. >> CloudScale is continuing to change the ecosystem, and this segment with AWS is going to be awesome. >> Exactly, we've got one of our alumni back with us, Stefanie Chiras joins us again, senior vice president, partner ecosystem success at Red Hat. and Manasi Jagannatha is also here Global Alliance Manager at AWS. Ladies, welcome to the program. >> Both: Thank you. >> Manasi: Nice to be here. >> Stefanie: Yeah. >> So some exciting news that came out. First of all was great to see you on stage. >> Thank you. >> In front of a live audience. The community is, you talked about this before we went live. The Ansible is nothing, if not the community. So I can only imagine how great that felt to be on stage in front of live bodies announcing the next step with Ansible and AWS. Tell us about that. >> I mean, you can't compete with the energy that comes from a live event. And I remember the first AnsibleFest I came to, it's just this electric feeling born out of the community, born out of collaboration and getting together feeds that collaboration in a way that like nothing else. >> Lisa: Can't do it by video alone. >> You cannot. And so it was so fun cuz today was big news. We announced that Ansible will be available through the AWS marketplace, the next step in our partnership journey. And we've been hearing like most of our announcements, we do these because customers ask for them. And that's really what is key. And the combination of what Red Hat brings to the table and what AWS brings to the table. That's what underpins this announcement this morning. >> Talk about it from a customer demand perspective and how you are not only meeting customers where they are, but you're speaking their language. >> Manasi: Yeah. >> Yeah, there's a couple of aspects and then I want to pass it to Manasi because nothing speaks better than a customer experience. But the specifics I think of what come together is this is where technology, procurement, experience, accessibility all come together. And it took both of us in order to do that. But we actually talked about a great example today, the TransUnion. >> So we have TransUnion, they are a credit reporting company and they're a giant customer. They use RHEL, they use AWS services. So while they were transitioning to the cloud, the first thing they wanted to know was compliance, right? Like, how do we have guardrails around compliance? That was a key feature for them. And then the other piece was how do we scale without increasing the complexity? And then the critical piece was being able to integrate with the depth of AWS services without having to do it over and over again. So what TransUnion did was they basically integrated Ansible automation platform with the AWS Cloud Control API that gave them the flexibility To basically integrate with what, 200 plus services? And it's amazing to see them grow over time. >> What's interesting is that Amazon, obviously cloud has been awesome. We've been covering it since the beginning. DevOps infrastructures code was the dream. Now it's app says code, you have configuration code before that. As cloud goes next level here, we're starting to see a lot more higher level services on AWS being adopted by customers. And so I want to get into how the marketplace deal works. So what's in it for the customer? Because as they bring Ansible across the enterprise and edge, now we're seeing that develop. If I'm the customer, am I buying it through the marketplace? What's the mechanics of the deal? Can I just tap into the bill, explain the marketplace workflow or how it works? >> Yeah, I'd love to do that. So customers come to the marketplace for three key benefits, right? Like one is the consumption based model, pay as you go, you can get hourly, annual, and spot instances. For some services you even get per second billing, right? Like, that's amazing, that's one. And then the other piece is John and Stefanie, as you know, customers would love to draw down on their EDPs, right? Like they want a single- >> EDPs, explain that with acronym. >> It's enterprise discount program. So they want a single bill where they can use third party services and AWS services and they don't have to go through the hustle of saying, "Hey, let me combine all these different pieces." So combining that, and of course the power of Ansible, right? Like customers love Ansible, they've built playbooks. The beauty of it is whatever you want to build on AWS, there is most likely a playbook or a module that already exists. So they can just tap into that and build into- >> Operationally it's a purchasing through marketplace. >> And you know, I mean, being an engineer myself, we always often get caught up in the technology aspect. Like what's the greatest technology? And everyone, as Manasi said, everyone loves the technology of Ansible, but the procurement aspect is also so important. And this is where I think this partnership really comes together. It is natively, Ansible is now, natively integrated into AWS billing. So one bill, you go and you log in. Now you have a Red Hat subscription, you get all the benefits from Red Hat that comes along with that subscription. But the like Ansible is all about simplicity. This brings simplicity to that procurement model and it allows you to scale within your AWS cloud environment that you have set up. And as Manasi mentioned, pull in those other native services from AWS. It's Great. >> It's interesting one of the things that buzzword Lisa and I were just talking as in the industry is the word multiplayer. I've heard people say that's multiplayer software, kind of a gaming analogy. But what you guys are doing is setting up, once they go with Ansible in the marketplace, they're just buying as things get more collaborative off the marketplace. So it kind of streamlines, if I get this right. >> Stefanie: Yep. >> The purchasing process. So they're already in, they just use it's on the bill. Is that kind of how it works? >> Yep. >> Absolutely done, yeah. >> So it the customer has a partnership with us more on the technology side and this particular case and with AWS and the procurement side, it brings that together. >> So multiplayer software, is it multiplayer software? >> We like to talk about multi-partner solutions and I think this provides a new grounding for other partners to come in and build upon that with their services capabilities, with their other technology capabilities. So well clearly in my world, we talk about multi-partner. (both laughs) >> Well, what you're doing is empowering the developers. I know that Red Hat is one of its goals is let's make things much more seamless, much smoother for the developers as the buyer's journey has changed. And John, you've talked about that quite a bit. You're empowering those buyers to actually have a much simpler, streamlined process and to be able to start seeing automation become democratized across organizations. >> Yeah, and one of the things I love about the announcement as well is it pulls in the other values of Ansible automation platform in that simplicity model that you mentioned with like things like certified collections, certified collections that have been built by partners. We have built certified collections, to go along with this offering as well as part of the AWS offering that pulls in these other partner engagements together. And as you said, democratizes not only what we've done together, but what we've done with other partners together. >> Lisa: Right. >> Yeah. >> Can you kind of talk kind of about the depths of the partnership, the co-engineering, and sort of the evolution and the customer involvement in the expansion of the partnership? >> Yeah, I'd love to walk you through that. So we've had a longstanding partnership coming up on 15 years now Stefanie, can you believe it? >> Stefanie: Yeah. (laughs) >> 15 years we've been building, to give you some historical context, right? In back in 2008 we launched RHEL and in 2015 we supported SAP workloads on RHEL. And then the list goes on, right? Like we've been launching Graviton instances, Arm instances, Nitro. The key to be noted here is that every new instance Launch, RHEL has always been supported on day one, right? Like that's been our motto. So that's one. And then in 2021, as you know, we launched Rosa Red Hat OpenShift service on AWS. And that's helped customers with their modernization journey to AWS. So that's been context historically around where we were and where we are today. And now with Ansible, it just gives customer another tool in their arsenal, right? And then the goal is to make sure we meet customers where they are, give them all the Red Hat products that they love using on their hybrid workloads. >> Sounds like a lot is coming maybe at re:Invent too, coming up. >> Yeah. >> What's next? >> This is the beginning, right? We'll continue to grow and based upon not only laying the building blocks for what customers can build with, and you mentioned Lisa, right? We follow this journey that Manasi talked about because of what customers ask for. So it's always a new adventure to determine what'll come next based upon what we hear from our joint customers. >> On that front though, Stefanie, talk about the impact of the broader ecosystem that this is just scratching the surface. >> One of the things, and we've been going through a whole transformation at Red Hat about how we engage with the ecosystem. We've done organizational shifts, we've done a complete revamp of how we engage with the ecosystem. One of our biggest focus is to make sure that the partnerships that we have with one partner bring value to the rest of our partners. No better example than something like this when we work with AWS to create accessibility and capability through a procurement model that we know is important to customers. But that then serves as a launch point for other partners to build certified collections around or now around validated content, which we talked about today at AnsibleFest, that allows other partners to engage. And we're seeing a huge amount in services partners, right? Automation is so pervasive now as customers want to go out and scale. We're seeing services partners really come in and help customers go from, it's always challenging when you have a broad set of IT. You have cloud native over here, you have bare metal over here, you have virtual, it's complex. >> John: Yeah. >> There's sometimes an energy activation barrier to get over that initial automation. We're seeing partners come in with really skilled services capabilities to help customers get over that hump to consolidate with an automation plan. It gets them better equipped to do day one automation and day two automation. And that's where Ansible automation platform is going. It's not just about configuration management, it's about day two management as well. >> Talk about those barriers a little bit more and how Ansible and AWS together are helping customers really knock those out of the park. Another baseball reference for you. We see that a lot of organizations, the skills gap, which we've talked about already on the conversation today, but Ansible as being a facilitator of helping organizations to attract talent, to retain talent, but also customers that maybe don't know where to start or don't know how to determine the ROI that automating processes will bring. How can this partnership help customers nock those out of the park? >> So I'll start and then I'll pass it to Manasi here. But I think one of the key things in this particular partnership is just plain old accessibility. Accessibility, which public cloud has taught the world a new way to get fast access that consumption based pricing. Right you can get your hands on it, you can test it out, you can have a team go in and test it out, and then you can see it's built for scale. So then you can scale it as far as you want to go forward. We clearly have an ecosystem of services partners, so does AWS to help people then sort of take it to the next level as they want to build upon it. But to me the first step is about accessibility, getting your hands dirty. You can build it into those committed spend programs that you may have with AWS as well to try new things. But it's a great test bed. >> Absolutely. And then to add to what Stefanie said, together Red Hat and AWS, we have about a hundred thousand partners combined, right? Like resellers, sis, GSI, distributors. So the reach the combined partnership has just amplifies. >> Yeah, it's huge news. I think it's a big deal because you operationalize the heavy lifting of procurement for all your joint customers and the scale piece is huge. So congratulations. I think it's going to make a lot of money for Ansible. So good call there. My question is, as we hear here, the next level's edge. So AWS has been doing a ton of hybrids since outpost announcement years ago. Now you got all kinds of regional expansions, you've got local zones, you've got all kinds of new edge activity. So are there dots connecting here with the edge with Red Hat Ansible? >> Do you want- >> Yeah, so I think we see two trends with our customers, right? Like mainly I'm specifically talking about our RHEL customer base on AWS. We have almost hundreds to thousands of customers using RHEL on AWS. These are 90% of fortune 500 companies use RHEL, right? So with that customer base, they are looking to expand your point into the edge. There's outposts, there are so many hybrid environments that they're trying to expand in. So just adding Ansible, RHEL, Rosa, OpenShift, that entire makes, just gives customers that the plethora of products they need to run their workloads everywhere, right? Like we have certifications outpost, we have certifications with OpenShift, right? So it just completes the puzzle, if you- >> So it's a nice fit. >> Yeah. >> It is a really nice fit. And I love Edge and Edge once you start going distributed, this automation aspect is key for all the reasons, for security reasons to make sure you do it the same way every single time. It's just pervasive in it. But things like the Cloud Control API allow it to bridge into things like Outpost. It allows a simple way, one clean way to do API and then you can expand it out and get the value. >> So this is why you are on stage and you said that Ansible's going to expand the scope to be more enterprise architecture. >> Stefanie: That's right. >> That's essentially what you're getting at. This is now a distributed computing fabric at cloud scale on AWS. >> Stefanie: That's right. >> Did I get that right? >> Yep, and it touches all the different deployments you may have, on-prem, virtual, cloud native, you name it. >> So how do the people turn into architects? Cuz this is, again, we had this earlier conversation with Tom, multi-tool players, a baseball analogy I used. It's like signifies the best player, your customers are becoming multiple tool players or operators. The new operator is now the top talent. They got to run Ansible, they got to automate, they got to provide services to the cloud native developers. So this new role is emerging, it's not a cloud architect but it's, if it's going to be system architecture wide, what's this new person look like that's going to run all this? >> I think it's an interesting question. We were talking yesterday, actually, Tom and I were talking with the partners. We had Partner Day, the first ever at AnsibleFest yesterday, which was great. We got a lot of insight. They talked a lot about this platform focus, right? Customers are looking to create that platform so that the developers can come in and build upon it without compromising what they want to do. So I do think there's a move in that direction to say how do you create these platforms at a company that no compromises, but it provides that consistency. I would say one thing in partnerships like this, I think customer expectations on the partner ecosystem to have it be trusted is increasing. They expect us as we've done to have our engineers roll up their sleeves together to come to the table together. That's going to show up in our curated content. It's going to show up in our validated content. Those are the places I think where we come up from the bottom through our partnership and we help bridge that gap. >> John: Awesome. >> And trust was brought up a number of times this morning during the keynote. We're almost out of time here, but I think it's one of those words that a lot of companies use. But I think what you're showing is really the value in it from Ansible's perspective from AWS's perspective and ultimately the value in it for the customer. >> Stefanie: Yes. >> So I got to ask you one final question. >> Stefanie: Absolutely. >> And maybe as as reinvent is around the corner, what's next for the partnership? Obviously big news today, Manasi, looking down down the pipe- >> Stefanie: Big news today. >> What are some of the things that you think are going to become next that you can share? >> I mean at this point, and I'll pass it to Manasi to close us out, but we are continuing to follow, to meet our customers where they want to be. We are looking across our portfolio for different ways that customers want to consume within AWS. We'll continue to look at the procurement models through the partner programs that Manasi and the team have had. And to me the next step is really bringing in the rest of the ecosystem. How do we use this as a grounding step? >> Yeah, absolutely. So we are always listening to customer feedback and they want more Red Hat products in the marketplace. So that's where we'll be. >> In the marketplace. >> Congratulations great deal. >> Yes great work there guys. And customers always want more. That's the thing. But that's what keeps us going. So we love it. >> Absolutely. >> Thank you so much for joining John and me on the program today. It's been great to have you. And congratulations again. >> It's a pleasure. >> Thank you. >> For our guests and for John Furrier, I'm Lisa Martin. You're watching theCUBE Live from Chicago at AnsibleFest 2022. This is only day one of our coverage. We'll be back after a short break for more. (upbeat music)

>> From the theCUBE studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vellante. >> Welcome to this week's Wikibon, theCUBE's insights powered by ETR. As we exited the isolation economy last year, supercloud is a term that we introduced to describe something new that was happening in the world of cloud. In this Breaking Analysis, we address the 10 most frequently asked questions we get around supercloud. Okay, let's review these frequently asked questions on supercloud that we're going to try to answer today. Look at an industry that's full of hype and buzzwords. Why the hell does anyone need a new term? Aren't hyperscalers building out superclouds? We'll try to answer why the term supercloud connotes something different from hyperscale clouds. And we'll talk about the problems that superclouds solve specifically. And we'll further define the critical aspects of a supercloud architecture. We often get asked, isn't this just multi-cloud? Well, we don't think so, and we'll explain why in this Breaking Analysis. Now in an earlier episode, we introduced the notion of super PaaS. Well, isn't a plain vanilla PaaS already a super PaaS? Again, we don't think so, and we'll explain why. Who will actually build and who are the players currently building superclouds? What workloads and services will run on superclouds? And 8-A or number nine, what are some examples that we can share of supercloud? And finally, we'll answer what you can expect next from us on supercloud? Okay, let's get started. Why do we need another buzzword? Well, late last year, ahead of re:Invent, we were inspired by a post from Jerry Chen called "Castles in the Cloud." Now in that blog post, he introduced the idea that there were sub-markets emerging in cloud that presented opportunities for investors and entrepreneurs that the cloud wasn't going to suck the hyperscalers. Weren't going to suck all the value out of the industry. And so we introduced this notion of supercloud to describe what we saw as a value layer emerging above the hyperscalers CAPEX gift, we sometimes call it. Now it turns out, that we weren't the only ones using the term as both Cornell and MIT have used the phrase in somewhat similar, but different contexts. The point is something new was happening in the AWS and other ecosystems. It was more than IaaS and PaaS, and wasn't just SaaS running in the cloud. It was a new architecture that integrates infrastructure, platform and software as services to solve new problems that the cloud vendors in our view, weren't addressing by themselves. It seemed to us that the ecosystem was pursuing opportunities across clouds that went beyond conventional implementations of multi-cloud. And we felt there was a structural change going on at the industry level, the supercloud, metaphorically was highlighting. So that's the background on why we felt a new catch phrase was warranted, love it or hate it. It's memorable and it's what we chose. Now to that last point about structural industry transformation. Andy Rappaport is sometimes and often credited with identifying the shift from the vertically integrated IBM mainframe era to the fragmented PC microprocesor-based era in his HBR article in 1991. In fact, it was David Moschella, who at the time was an IDC Analyst who first introduced the concept in 1987, four years before Rappaport's article was published. Moschella saw that it was clear that Intel, Microsoft, Seagate and others would replace the system vendors, and put that forth in a graphic that looked similar to the first two on this chart. We don't have to review the shift from IBM as the center of the industry to Wintel, that's well understood. What isn't as well known or accepted is what Moschella put out in his 2018 book called "Seeing Digital" which introduced the idea of "The Matrix" that's shown on the right hand side of this chart. Moschella posited that new services were emerging built on top of the internet and hyperscale clouds that would integrate other innovations and would define the next era of computing. He used the term Matrix because the conceptual depiction included not only horizontal technology rose like the cloud and the internet, but for the first time included connected industry verticals, the columns in this chart. Moschella pointed out that whereas historically, industry verticals had a closed value chain or stack and ecosystem of R&D, and production, and manufacturing, and distribution. And if you were in that industry, the expertise within that vertical generally stayed within that vertical and was critical to success. But because of digital and data, for the first time, companies were able to traverse industries, jump across industries and compete because data enabled them to do that. Examples, Amazon and content, payments, groceries, Apple, and payments, and content, and so forth. There are many examples. Data was now this unifying enabler and this marked a change in the structure of the technology landscape. And supercloud is meant to imply more than running in hyperscale clouds, rather it's the combination of multiple technologies enabled by CloudScale with new industry participants from those verticals, financial services and healthcare, manufacturing, energy, media, and virtually all in any industry. Kind of an extension of every company is a software company. Basically, every company now has the opportunity to build their own cloud or supercloud. And we'll come back to that. Let's first address what's different about superclouds relative to hyperscale clouds? You know, this one's pretty straightforward and obvious, I think. Hyperscale clouds, they're walled gardens where they want your data in their cloud and they want to keep you there. Sure, every cloud player realizes that not all data will go to their particular cloud so they're meeting customers where their data lives with initiatives like Amazon Outposts and Azure Arc, and Google Anthos. But at the end of the day, the more homogeneous they can make their environments, the better control, security, cost, and performance they can deliver. The more complex the environment, the more difficult it is to deliver on their brand promises. And of course, the lesser margin that's left for them to capture. Will the hyperscalers get more serious about cross-cloud services? Maybe, but they have plenty of work to do within their own clouds and within enabling their own ecosystems. They had a long way to go a lot of runway. So let's talk about specifically, what problems superclouds solve? We've all seen the stats from IDC or Gartner, or whomever the customers on average use more than one cloud. You know, two clouds, three clouds, five clouds, 20 clouds. And we know these clouds operate in disconnected silos for the most part. And that's a problem because each cloud requires different skills because the development environment is different as is the operating environment. They have different APIs, different primitives, and different management tools that are optimized for each respective hyperscale cloud. Their functions and value props don't extend to their competitors' clouds for the most part. Why would they? As a result, there's friction when moving between different clouds. It's hard to share data, it's hard to move work. It's hard to secure and govern data. It's hard to enforce organizational edicts and policies across these clouds, and on-prem. Supercloud is an architecture designed to create a single environment that enables management of workloads and data across clouds in an effort to take out complexity, accelerate application development, streamline operations and share data safely, irrespective of location. It's pretty straightforward, but non-trivial, which is why I always ask a company's CEO and executives if stock buybacks and dividends will yield as much return as building out superclouds that solve really specific and hard problems, and create differential value. Okay, let's dig a bit more into the architectural aspects of supercloud. In other words, what are the salient attributes of supercloud? So first and foremost, a supercloud runs a set of specific services designed to solve a unique problem and it can do so in more than one cloud. Superclouds leverage the underlying cloud native tooling of a hyperscale cloud, but they're optimized for a specific objective that aligns with the problem that they're trying to solve. For example, supercloud might be optimized for lowest cost or lowest latency, or sharing data, or governing, or securing that data, or higher performance for networking, for example. But the point is, the collection of services that is being delivered is focused on a unique value proposition that is not being delivered by the hyperscalers across clouds. A supercloud abstracts the underlying and siloed primitives of the native PaaS layer from the hyperscale cloud and then using its own specific platform as a service tooling, creates a common experience across clouds for developers and users. And it does so in a most efficient manner, meaning it has the metadata knowledge and management capabilities that can optimize for latency, bandwidth, or recovery, or data sovereignty, or whatever unique value that supercloud is delivering for the specific use case in their domain. And a supercloud comprises a super PaaS capability that allows ecosystem partners through APIs to add incremental value on top of the supercloud platform to fill gaps, accelerate features, and of course innovate. The services can be infrastructure-related, they could be application services, they could be data services, security services, user services, et cetera, designed and packaged to bring unique value to customers. Again, that hyperscalers are not delivering across clouds or on-premises. Okay, so another common question we get is, isn't that just multi-cloud? And what we'd say to that is yes, but no. You can call it multi-cloud 2.0, if you want, if you want to use it, it's kind of a commonly used rubric. But as Dell's Chuck Whitten proclaimed at Dell Technologies World this year, multi-cloud by design, is different than multi-cloud by default. Meaning to date, multi-cloud has largely been a symptom of what we've called multi-vendor or of M&A, you buy a company and they happen to use Google Cloud, and so you bring it in. And when you look at most so-called, multi-cloud implementations, you see things like an on-prem stack, which is wrapped in a container and hosted on a specific cloud or increasingly a technology vendor has done the work of building a cloud native version of their stack and running it on a specific cloud. But historically, it's been a unique experience within each cloud with virtually no connection between the cloud silos. Supercloud sets out to build incremental value across clouds and above hyperscale CAPEX that goes beyond cloud compatibility within each cloud. So if you want to call it multi-cloud 2.0, that's fine, but we chose to call it supercloud. Okay, so at this point you may be asking, well isn't PaaS already a version of supercloud? And again, we would say no, that supercloud and its corresponding superPaaS layer which is a prerequisite, gives the freedom to store, process and manage, and secure, and connect islands of data across a continuum with a common experience across clouds. And the services offered are specific to that supercloud and will vary by each offering. Your OpenShift, for example, can be used to construct a superPaaS, but in and of itself, isn't a superPaaS, it's generic. A superPaaS might be developed to support, for instance, ultra low latency database work. It would unlikely again, taking the OpenShift example, it's unlikely that off-the-shelf OpenShift would be used to develop such a low latency superPaaS layer for ultra low latency database work. The point is supercloud and its inherent superPaaS will be optimized to solve specific problems like that low latency example for distributed databases or fast backup and recovery for data protection, and ransomware, or data sharing, or data governance. Highly specific use cases that the supercloud is designed to solve for. Okay, another question we often get is who has a supercloud today and who's building a supercloud, and who are the contenders? Well, most companies that consider themselves cloud players will, we believe, be building or are building superclouds. Here's a common ETR graphic that we like to show with Net Score or spending momentum on the Y axis and overlap or pervasiveness in the ETR surveys on the X axis. And we've randomly chosen a number of players that we think are in the supercloud mix, and we've included the hyperscalers because they are enablers. Now remember, this is a spectrum of maturity it's a maturity model and we've added some of those industry players that we see building superclouds like CapitalOne, Goldman Sachs, Walmart. This is in deference to Moschella's observation around The Matrix and the industry structural changes that are going on. This goes back to every company, being a software company and rather than pattern match an outdated SaaS model, we see new industry structures emerging where software and data, and tools, specific to an industry will lead the next wave of innovation and bring in new value that traditional technology companies aren't going to solve, and the hyperscalers aren't going to solve. You know, we've talked a lot about Snowflake's data cloud as an example of supercloud. After being at Snowflake Summit, we're more convinced than ever that they're headed in this direction. VMware is clearly going after cross-cloud services you know, perhaps creating a new category. Basically, every large company we see either pursuing supercloud initiatives or thinking about it. Dell showed project Alpine at Dell Tech World, that's a supercloud. Snowflake introducing a new application development capability based on their superPaaS, our term of course, they don't use the phrase. Mongo, Couchbase, Nutanix, Pure Storage, Veeam, CrowdStrike, Okta, Zscaler. Yeah, all of those guys. Yes, Cisco and HPE. Even though on theCUBE at HPE Discover, Fidelma Russo said on theCUBE, she wasn't a fan of cloaking mechanisms, but then we talked to HPE's Head of Storage Services, Omer Asad is clearly headed in the direction that we would consider supercloud. Again, those cross-cloud services, of course, their emphasis is connecting as well on-prem. That single experience, which traditionally has not existed with multi-cloud or hybrid. And we're seeing the emergence of companies, smaller companies like Aviatrix and Starburst, and Clumio and others that are building versions of superclouds that solve for a specific problem for their customers. Even ISVs like Adobe, ADP, we've talked to UiPath. They seem to be looking at new ways to go beyond the SaaS model and add value within their cloud ecosystem specifically, around data as part of their and their customers digital transformations. So yeah, pretty much every tech vendor with any size or momentum and new industry players are coming out of hiding, and competing. Building superclouds that look a lot like Moschella's Matrix, with machine intelligence and blockchains, and virtual realities, and gaming, all enabled by the internet and hyperscale cloud CAPEX. So it's moving fast and it's the future in our opinion. So don't get too caught up in the past or you'll be left behind. Okay, what about examples? We've given a number in the past, but let's try to be a little bit more specific. Here are a few we've selected and we're going to answer the two questions in one section here. What workloads and services will run in superclouds and what are some examples? Let's start with analytics. Our favorite example is Snowflake, it's one of the furthest along with its data cloud, in our view. It's a supercloud optimized for data sharing and governance, query performance, and security, and ecosystem enablement. When you do things inside of that data cloud, what we call a super data cloud. Again, our term, not theirs. You can do things that you could not do in a single cloud. You can't do this with Redshift, You can't do this with SQL server and they're bringing new data types now with merging analytics or at least accommodate analytics and transaction type data, and bringing open source tooling with things like Apache Iceberg. And so it ticks the boxes we laid out earlier. I would say that a company like Databricks is also in that mix doing it, coming at it from a data science perspective, trying to create that consistent experience for data scientists and data engineering across clouds. Converge databases, running transaction and analytic workloads is another example. Take a look at what Couchbase is doing with Capella and how it's enabling stretching the cloud to the edge with ARM-based platforms and optimizing for low latency across clouds, and even out to the edge. Document database workloads, look at MongoDB, a very developer-friendly platform that with the Atlas is moving toward a supercloud model running document databases very, very efficiently. How about general purpose workloads? This is where VMware comes into to play. Very clearly, there's a need to create a common operating environment across clouds and on-prem, and out to the edge. And I say VMware is hard at work on that. Managing and moving workloads, and balancing workloads, and being able to recover very quickly across clouds for everyday applications. Network routing, take a look at what Aviatrix is doing across clouds, industry workloads. We see CapitalOne, it announced its cost optimization platform for Snowflake, piggybacking on Snowflake supercloud or super data cloud. And in our view, it's very clearly going to go after other markets is going to test it out with Snowflake, running, optimizing on AWS and it's going to expand to other clouds as Snowflake's business and those other clouds grows. Walmart working with Microsoft to create an on-premed Azure experience that's seamless. Yes, that counts, on-prem counts. If you can create that seamless and continuous experience, identical experience from on-prem to a hyperscale cloud, we would include that as a supercloud. You know, we've written about what Goldman is doing. Again, connecting its on-prem data and software tooling, and other capabilities to AWS for scale. And we can bet dollars to donuts that Oracle will be building a supercloud in healthcare with its Cerner acquisition. Supercloud is everywhere you look. So I'm sorry, naysayers it's happening all around us. So what's next? Well, with all the industry buzz and debate about the future, John Furrier and I, have decided to host an event in Palo Alto, we're motivated and inspired to further this conversation. And we welcome all points of view, positive, negative, multi-cloud, supercloud, hypercloud, all welcome. So theCUBE on Supercloud is coming on August 9th, out of our Palo Alto studios, we'll be running a live program on the topic. We've reached out to a number of industry participants, VMware, Snowflake, Confluent, Sky High Security, Gee Rittenhouse's new company, HashiCorp, CloudFlare. We've hit up Red Hat and we expect many of these folks will be in our studios on August 9th. And we've invited a number of industry participants as well that we're excited to have on. From industry, from financial services, from healthcare, from retail, we're inviting analysts, thought leaders, investors. We're going to have more detail in the coming weeks, but for now, if you're interested, please reach out to me or John with how you think you can advance the discussion and we'll see if we can fit you in. So mark your calendars, stay tuned for more information. Okay, that's it for today. Thanks to Alex Myerson who handles production and manages the podcast for Breaking Analysis. And I want to thank Kristen Martin and Cheryl Knight, they help get the word out on social and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE, who does a lot of editing and appreciate you posting on SiliconANGLE, Rob. Thanks to all of you. Remember, all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. It publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me @DVellante, or comment on my LinkedIn post. And please do check out ETR.ai for the best survey data. And the enterprise tech business will be at AWS NYC Summit next Tuesday, July 12th. So if you're there, please do stop by and say hello to theCUBE, it's at the Javits Center. This is Dave Vellante for theCUBE insights powered by ETR. Thanks for watching. And we'll see you next time on "Breaking Analysis." (bright music)

(upbeat music) >> Hello, and welcome back to AWS Startup Showcase, I'm John Furrier, your host. This is the Hero panel, the AWS Heroes. These are folks that have a lot of experience in Open Source, having fun building great projects and commercializing the value and best practices of Open Source innovation. We've got some great guests here. Liz Rice, Chief Open Source Officer, Isovalent. CUBE alumni, great to see you. Brian LeRoux, who is the Co-founder and CTO of begin.com. Erica Windisch who's an Architect for Developer Experience. AWS Hero, also CUBE alumni. Casey Lee, CTO Gaggle. Doing some great stuff in ed tech. Great collection of experts and experienced folks doing some fun stuff, welcome to this conversation this CUBE panel. >> Hi. >> Thanks for having us. >> Hello. >> Let's go down the line. >> I don't normally do this, but since we're remote and we have such great guests, go down the line and talk about why Open Source is important to you guys. What projects are you currently working on? And what's the coolest thing going on there? Liz we'll start with you. >> Okay, so I am very involved in the world of Cloud Native. I'm the chair of the technical oversight committee for the Cloud Native Computing Foundation. So that means I get to see a lot of what's going on across a very broad range of Cloud Native projects. More specifically, Isovalent. I focus on Cilium, which is it's based on a technology called EBPF. That is to me, probably the most exciting technology right now. And then finally, I'm also involved in an organization called OpenUK, which is really pushing for more use of open technologies here in the United Kingdom. So spread around lots of different projects. And I'm in a really fortunate position, I think, to see what's happening with lots of projects and also the commercialization of lots of projects. >> Awesome, Brian what project are you working on? >> Working project these days called Architect. It's a Open Source project built on top of AWSM. It adds a lot of sugar and terseness to the SM experience and just makes it a lot easier to work with and get started. AWS can be a little bit intimidating to people at times. And the Open Source community is stepping up to make some of that bond ramp a little bit easier. And I'm also an Apache member. And so I keep a hairy eyeball on what's going on in that reality all the time. And I've been doing this open-source thing for quite a while, and yeah, I love it. It's a great thing. It's real science. We get to verify each other's work and we get to expand and build on human knowledge. So that's a huge honor to just even be able to do that and I feel stoked to be here so thanks for having me. >> Awesome, yeah, and totally great. Erica, what's your current situation going on here? What's happening? >> Sure, so I am currently working on developer experience of a number of Open Source STKS and CLI components from my current employer. And previously, recently I left New Relic where I was working on integrating with OpenTelemetry, as well as a number of other things. Before that I was a maintainer of Docker and of OpenStack. So I've been in this game for a while as well. And I tend to just put my fingers in a lot of little pies anywhere from DVD players 20 years ago to a lot of this open telemetry and monitoring and various STKs and developer tools is where like Docker and OpenStack and the STKs that I work on now, all very much focusing on developer as the user. >> Yeah, you're always on the wave, Erica great stuff. Casey, what's going on? Do you got some great ed techs happening? What's happening with you? >> Yeah, sure. The primary Open Source project that I'm contributing to right now is ACT. This is a tool I created a couple of years back when GitHub Actions first came out, and my motivation there was I'm just impatient. And that whole commit, push, wait time where you're testing out your pipelines is painful. And so I wanted to build a tool that allowed developers to test out their GitHub Actions workflows locally. And so this tool uses Docker containers to emulate, to get up action environment and gives you fast feedback on those workflows that you're building. Lot of innovation happening at GitHub. And so we're just trying to keep up and continue to replicate those new features functionalities in the local runner. And the biggest challenge I've had with this project is just keeping up with the community. We just passed 20,000 stars, and it'd be it's a normal week to get like 10 PRs. So super excited to announce just yesterday, actually I invited four of the most active contributors to help me with maintaining the project. And so this is like a big deal for me, letting the project go and bringing other people in to help lead it. So, yeah, huge shout out to those folks that have been helping with driving that project. So looking forward to what's next for it. >> Great, we'll make sure the SiliconANGLE riders catch that quote there. Great call out. Let's start, Brian, you made me realize when you mentioned Apache and then you've been watching all the stuff going on, it brings up the question of the evolution of Open Source, and the commercialization trends have been very interesting these days. You're seeing CloudScale really impact also with the growth of code. And Liz, if you remember, the Linux Foundation keeps making projections and they keep blowing past them every year on more and more code and more and more entrance coming in, not just individuals, corporations. So you starting to see Netflix donates something, you got Lyft donate some stuff, becomes a project company forms around it. There's a lot of entrepreneurial activity that's creating this new abstraction layers, new platforms, not just tools. So you start to see a new kickup trajectory with Open Source. You guys want to comment on this because this is going to impact how fast the enterprise will see value here. >> I think a really great example of that is a project called Backstage that's just come out of Spotify. And it's going through the incubation process at the CNCF. And that's why it's front of mind for me right now, 'cause I've been working on the due diligence for that. And the reason why I thought it was interesting in relation to your question is it's spun out of Spotify. It's fully Open Source. They have a ton of different enterprises using it as this developer portal, but they're starting to see some startups emerging offering like a hosted managed version of Backstage or offering services around Backstage or offering commercial plugins into Backstage. And I think it's really fascinating to see those ecosystems building up around a project and different ways that people can. I'm a big believer. You cannot sell the Open Source code, but you can sell other things that create value around Open Source projects. So that's really exciting to see. >> Great point. Anyone else want to weigh in and react to that? Because it's the new model. It's not the old way. I mean, I remember when I was in college, we had the Pirate software. Open Source wasn't around. So you had to deal under the table. Now it's free. But I mean the old way was you had to convince the enterprise, like you've got a hard knit, it builds the community and the community manage the quality of the code. And then you had to build the company to make sure they could support it. Now the companies are actually involved in it, right? And then new startups are forming faster. And the proof points are shorter and highly accelerated for that. I mean, it's a whole new- >> It's a Cambrian explosion, and it's great. It's one of those things that it's challenging for the new developers because they come in and they're like, "Whoa, what is all this stuff that I'm supposed to figure out?" And there's no right answer and there's no wrong answer. There's just tons of it. And I think that there's a desire for us to have one sort of well-known trot and happy path, that audience we're a lot better with a more diverse community, with lots of options, with lots of ways to approach these problems. And I think it's just great. A challenge that we have with all these options and all these Cambrian explosion of projects and all these competing ideas, right now, the sustainability, it's a bit of a tricky question to answer. We know that there's a commercialization aspect that helps us fund these projects, but how we compose the open versus the commercial source is still a bit of a tricky question and a tough one for a lot of folks. >> Erica, would you chime in on that for a second. I want to get your angle on that, this experience and all this code, and I'm a new person, I'm an existing person. Do I get like a blue check mark and verify? I mean, these are questions like, well, how do you navigate? >> Yeah, I think this has been something happening for a while. I mean, back in the early OpenStack days, 2010, for instance, Rackspace Open Sourcing, OpenStack and ANSU Labs and so forth, and then trying, having all these companies forming in creating startups around this. I started at a company called Cloudccaling back in late 2010, and we had some competitors such as Piston and so forth where a lot of the ANSUL Labs people went. But then, the real winners, I think from OpenStack ended up being the enterprises that jumped in. We had Red Hat in particular, as well as HP and IBM jumping in and investing in OpenStack, and really proving out a lot of... not that it was the first time, but this is when we started seeing billions of dollars pouring into Open Source projects and Open Source Foundations, such as the OpenStack Foundation, which proceeded a lot of the things that we now see with the Linux Foundation, which was then created a little bit later. And at the same time, I'm also reflecting a little bit what Brian said because there are projects that don't get funded, that don't get the same attention, but they're also getting used quite significantly. Things like Log4j really bringing this to the spotlight in terms of projects that are used everywhere by everything with significant outsized impacts on the industry that are not getting funded, that aren't flashy enough, that aren't exciting enough because it's just logging, but a vulnerability in it brings every everything and everybody down and has possibly billions of dollars of impact to our industry because nobody wanted to fund this project. >> I think that brings up the commercialization point about maybe bringing a venture capital model in saying, "Hey, that boring little logging thing could be a key ingredient for say solving some observability problems so I think let's put some cash." Again then we'd never seen that before. Now you're starting to see that kind of a real smart investment thesis going into Open Source projects. I mean, Promethease, Crafter, these are projects that turned off companies. This is turning up companies. >> A decade ago, there was no money in Dev tools that I think that's been fully debunked now. They used to be a concept that the venture community believed, but there's just too much evidence to the contrary, the companies like Cash Court, Datadog, the list goes on and on. I think the challenge for the Open Source (indistinct) comes back to foundations and working (indistinct) these developers make this code safe and secure. >> Casey, what's your reaction to all of this? You've got, so a project has gained some traction, got some momentum. There's a lot of mission critical. I won't say white spaces, but the opportunities in the big cloud game happening. And there's a lot of, I won't say too many entrepreneurial, but there's a lot of community action happening that's precommercialization that's getting traction. How does this all develop naturally and then vector in quickly when it hits? >> Yeah, I want to go back to the Log4j topic real quick. I think that it's a great example of an area that we need to do better at. And there was a cool article that Rob Pike wrote describing how to quantify the criticality. I think that's sort of quantifying criticality was the article he wrote on how to use metrics, to determine how valuable, how important a piece of Open Source is to the community. And we really need to highlight that more. We need a way to make it more clear how important this software is, how many people depend on it and how many people are contributing to it. And because right now we all do that. Like if I'm going to evaluate an Open Source software, sure, I'll look at how many stars it has and how many contributors it has. But I got to go through and do all that work myself and come up with. It would be really great if we had an agreed upon method for ranking the criticality of software, but then also the risk, hey, that this is used by a ton of people, but nobody's contributing to it anymore. That's a concern. And that would be great to potential users of that to signal whether or not it makes sense. The Open Source Security Foundation, just getting off the ground, they're doing some work in this space, and I'm really excited to see where they go with that looking at ways to stop score critically. >> Well, this brings up a good point while we've got everyone here, let's take a plug and plug a project you think that's not getting the visibility it needs. Let's go through each of you, point out a project that you think people should be looking at and talking about that might get some free visibility here. Anyone want to highlight projects they think should be focused more on, or that needs a little bit of love? >> I think, I mean, particularly if we're talking about these sort of vulnerability issues, there's a ton of work going on, like in the Secure Software Foundation, other foundations, I think there's work going on in Apache somewhere as well around the bill of material, the software bill of materials, the Secure Software supply chain security, even enumerating your dependencies is not trivial today. So I think there's going to be a ton of people doing really good work on that, as well as the criticality aspect. It's all like that. There's a really great xkcd cartoon with your software project and some really big monolithic lumps. And then, this tiny little piece in a very important point that's maintained by somebody in his bedroom in Montana or something and if you called it out. >> Yeah, you just opened where the next lightening and a bottle comes from. And this is I think the beauty of Open Source is that you get a little collaboration, you get three feet in a cloud of dust going and you get some momentum, and if it's relevant, it rises to the top. I think that's the collective intelligence of Open Source. The question I want to ask that the panel here is when you go into an enterprise, and now that the game is changing with a much more collaborative and involved, what's the story if they say, hey, what's in it for me, how do I manage the Open Source? What's the current best practice? Because there's no doubt I can't ignore it. It's in everything we do. How do I organize around it? How do I build around it to be more efficient and more productive and reduce the risk on vulnerabilities to managing staff, making sure the right teams in place, the right agility and all those things? >> You called it, they got to get skin in the game. They need to be active and involved and donating to a sustainable Open Source project is a great way to start. But if you really want to be active, then you should be committing. You should have a goal for your organization to be contributing back to that project. Maybe not committing code, it could be committing resources into the darks or in the tests, or even tweeting about an Open Source project is contributing to it. And I think a lot of these enterprises could benefit a lot from getting more active with the Open Source Foundations that are out there. >> Liz, you've been actively involved. I know we've talked personally when the CNCF started, which had a great commercial uptake from companies. What do you think the current state-of-the-art kind of equation is has it changed a little bit? Or is it the game still the same? >> Yeah, and in the early days of the CNCF, it was very much dominated by vendors behind the project. And now we're seeing more and more membership from end-user companies, the kind of enterprises that are building their businesses on Cloud Native, but their business is not in itself. That's not there. The infrastructure is not their business. And I think seeing those companies, putting money in, putting time in, as Brian says contributing resources quite often, there's enough money, but finding the talent to do the work and finding people who are prepared to actually chop the wood and carry the water, >> Exactly. >> that it's hard. >> And if enterprises can find peoples to spend time on Open Source projects, help with those chores, it's hugely valuable. And it's one of those the rising tide floats all the boats. We can raise security, we can reduce the amount of dependency on maintain projects collectively. >> I think the business models there, I think one of the things I'll react to and then get your guys' comments is remember which CubeCon it was, it was one of the early ones. And I remember seeing Apple having a booth, but nobody was manning. It was just an Apple booth. They weren't doing anything, but they were recruiting. And I think you saw the transition of a business model where the worry about a big vendor taking over a project and having undue influence over it goes away because I think this idea of participation is also talent, but also committing that talent back into the communities as a model, as a business model, like, okay, hire some great people, but listen, don't screw up the Open Source piece of it 'cause that's a critical. >> Also hire a channel, right? They can use those contributions to source that talent and build the reputation in the communities that they depend on. And so there's really a lot of benefit to the larger organizations that can do this. They'll have a huge pipeline of really qualified engineers right out the gate without having to resort to cheesy whiteboard interviews, which is pretty great. >> Yeah, I agree with a lot of this. One of my concerns is that a lot of these corporations tend to focus very narrowly on certain projects, which they feel that they depend greatly, they'll invest in OpenStack, they'll invest in Docker, they'll invest in some of the CNCF projects. And then these other projects get ignored. Something that I've been a proponent of for a little bit for a while is observability of your dependencies. And I don't think there's quite enough projects and solutions to this. And it sounds maybe from lists, there are some projects that I don't know about, but I also know that there's some startups like Snyk and so forth that help with a little bit of this problem, but I think we need more focus on some of these edges. And I think companies need to do better, both in providing, having some sort of solution for observability of the dependencies, as well as understanding those dependencies and managing them. I've seen companies for instance, depending on software that they actively don't want to use based on a certain criteria that they already set projects, like they'll set a requirement that any project that they use has a code of conduct, but they'll then use projects that don't have codes of conduct. And if they don't have a code of conduct, then employees are prohibited from working on those projects. So you've locked yourself into a place where you're depending on software that you have instructed, your employees are not allowed to contribute to, for certain legal and other reasons. So you need to draw a line in the sand and then recognize that those projects are ones that you don't want to consume, and then not use them, and have observability around these things. >> That's a great point. I think we have 10 minutes left. I want to just shift to a topic that I think is relevant. And that is as Open Source software, software, people develop software, you see under the hood kind of software, SREs developing very quickly in the CloudScale, but also you've got your classic software developers who were writing code. So you have supply chain, software supply chain challenges. You mentioned developer experience around how to code. You have now automation in place. So you've got the development of all these things that are happening. Like I just want to write software. Some people want to get and do infrastructure as code so DevSecOps is here. So how does that look like going forward? How has the future of Open Source going to make the developers just want to code quickly? And the folks who want to tweak the infrastructure a bit more efficient, any views on that? >> At Gaggle, we're using AWS' CDK, exclusively for our infrastructure as code. And it's a great transition for developers instead of writing Yammel or Jason, or even HCL for their infrastructure code, now they're writing code in the language that they're used to Python or JavaScript, and what that's providing is an easier transition for developers into that Infrastructure as code at Gaggle here, but it's also providing an opportunity to provide reusable constructs that some Devs can build on. So if we've got a very opinionated way to deploy a serverless app in a database and do auto-scaling behind and all stuff, we can present that to a developer as a library, and they can just consume it as it is. Maybe that's as deep as they want to go and they're happy with that. But then they want to go deeper into it, they can either use some of the lower level constructs or create PRs to the platform team to have those constructs changed to fit their needs. So it provides a nice on-ramp developers to use the tools and languages they're used to, and then also go deeper as they need. >> That's awesome. Does that mean they're not full stack developers anymore that they're half stack developers they're taking care of for them? >> I don't know either. >> We'll in. >> No, only kidding. Anyway, any other reactions to this whole? I just want to code, make it easy for me, and some people want to get down and dirty under the hood. >> So I think that for me, Docker was always a key part of this. I don't know when DevSecOps was coined exactly, but I was talking with people about it back in 2012. And when I joined Docker, it was a part of that vision for me, was that Docker was applying these security principles by default for your application. It wasn't, I mean, yes, everybody adopted because of the portability and the acceleration of development, but it was for me, the fact that it was limiting what you could do from a security angle by default, and then giving you these tuna balls that you can control it further. You asked about a project that may not get enough recognition is something called DockerSlim, which is designed to optimize your containers and will make them smaller, but it also constraints the security footprint, and we'll remove capabilities from the container. It will help you build security profiles for app armor and the Red Hat one. SELinux. >> SELinux. >> Yeah, and this is something that I think a lot of developers, it's kind of outside of the realm of things that they're really thinking about. So the more that we can automate those processes and make it easier out of the box for users or for... when I say users, I mean, developers, so that it's straightforward and automatic and also giving them the capability of refining it and tuning it as needed, or simply choosing platforms like serverless offerings, which have these security constraints built in out of the box and sometimes maybe less tuneable, but very strong by default. And I think that's a good place for us to be is where we just enforced these things and make you do things in a secure way. >> Yeah, I'm a huge fan of Kubernetes, but it's not the right hammer for every nail. And there are absolutely tons of applications that are better served by something like Lambda where a lot more of that security surface is taken care of for the developer. And I think we will see better tooling around security profiling and making it easier to shrink wrap your applications that there are plenty of products out there that can help you with this in a cloud native environment. But I think for the smaller developer let's say, or an earlier stage company, yeah, it needs to be so much more straightforward. Really does. >> Really an interesting time, 10 years ago, when I was working at Adobe, we used to requisition all these analysts to tell us how many developers there were for the market. And we thought there was about 20 million developers. If GitHub's to be believed, we think there is now around 80 million developers. So both these groups are probably wrong in their numbers, but the takeaway here for me is that we've got a lot of new developers and a lot of these new developers are really struck by a paradox of choice. And they're typically starting on the front end. And so there's a lot of movement in the stack moved towards the front end. We saw that at re:Invent when Amazon was really pushing Amplify 'cause they're seeing this too. It's interesting because this is where folks start. And so a lot of the obstructions are moving in that direction, but maybe not always necessarily totally appropriate. And so finding the right balance for folks is still a work in progress. Like Lambda is a great example. It lets me focus totally on just business logic. I don't have to think about infrastructure pretty much at all. And if I'm newer to the industry, that makes a lot of sense to me. As use cases expand, all of a sudden, reality intervenes, and it might not be appropriate for everything. And so figuring out what those edges are, is still the challenge, I think. >> All right, thank you very much for coming on the CUBE here panel. AWS Heroes, thanks everyone for coming. I really appreciate it, thank you. >> Thank you. >> Thank you. >> Okay. >> Thanks for having me. >> Okay, that's a wrap here back to the program and the awesome startups. Thanks for watching. (upbeat music)

(energetic music) >> Hello, welcome to the CUBE's coverage of Boomi's Out of This World event. I'm John Furrier, host of theCUBE. We've got two great guests here, Chris McNabb, CEO of Boomi, and Ed Macosky, SVP and Head of Products, talking about hyper automation and the future of connectivity. Gentlemen, thank you for coming on theCUBE, great to see you. >> John, it is great to see you again as well. Looking forward to the next in-person one. >> I miss the in-person events, you guys have had great events and a lot of action happening. Love the big news of going out on your own direction, big financing, change of control, all that good stuff happening, industries growing. Chris, this is a big move. You know, the industry is changing. Can you give us some context to, you know, what's going on in automation and connectivity, because iPaaS, which you guys have pioneered, have been a big part of Cloud and CloudScale, and now we're seeing next-generation things happening. Data, automation, edge, modern application development, all happening. Set some context, what's going on? >> Yeah John, listen, it's a great time to be in our space at this point in time. Our customers, at the end of the day, are looking to create what we announced at last year's thing, called Integrated Experiences, which is the combination of user engagement, more awesome connectivity, and making sure high quality data goes through that experience, and providing 21st century experiences. And we're right at the heart of that work. Our platform really drives all the services that are needed there. But what our customers really need and what we're here to focus on today, that this world is to make sure that we have the world's best cut connectivity capabilities, and process automation engagement of constituents to really do what they want to do, where they want to do it. >> So a lot of big moves happening, what's the story? Take us through the story. I mean, you guys have a transaction with big sum financing, setting up this intelligence connectivity and automation approach. Take us through the story, what happened? >> Yeah. So, you know, the lead business was sold outside of Dell and that deal closed. We are now owned by two top tier private equity firms, FP and TPG. That sale is completed and now we are ready to unleash the Boomi business on this market. I think it's a great, it's a great transaction for Dell, and it's a great transaction for FP, PTG but most specifically, it's really a world-class transaction for the Boomi business, the Boomi customer base, as well as the Boomi employee. So I really looked at this as a win-win-win and sets us up for really going after this one. >> Yeah, and there's a huge wave coming and you're seeing like the, the big wave coming. It's just like, no need to debate it. It's here. It's cloud 2.0, whatever you want to call it, it's scale. IT has completely figured out, that not only is replatforming the cloud, but you got to be in the cloud refactoring. This is driving the innovation. And, this is really I see where you guys are leading. So share with me what is hyper automation? What is that actually mean? >> So what hyper automation really is, is intelligent connectivity automation. So our customers have been doing this. It's very specifically related to taking workflows, taking automation within the business. That's been around for a long time anyway, but adding AI and ML to it. So, as you continue to automate your business, you're getting more and more steam, and you get more and more productivity out of the (mumbles) organization or productivity from the (mumbles). >> So Chris, tell us more about this hyper automation, because you guys have a large install base. Take us through some of the numbers of the customer base, and where the dots are connecting as they look at the new IT landscape as it transforms. >> Yeah. John, great question. You know, when I talk to, you know as many of our 18,000 customers worldwide as I can get to, you know, what they are saying very clearly is their IT news feed is getting more complicated, more distributed, more siloed, and it has more data. And as you work through that problem, what they're trying to accomplish, is they're trying to engage their constituents in a 21st century web, however they want, whether it be mobile web, portals, chat bots, old fashioned telephones. And in doing that, that complicated area is extraordinarily difficult. So that's the pervasive problem that Boomi is purpose-built to help solve. And our customers start out sometimes with just great connectivity. Hyper automation is where the real value comes in. That's where your constituents see a complete difference in how I inter-operate with (mumbles). >> So, first of all, I love the word hyper automation because it reminds me of hyper scale, which, you know, look at the Amazons and the cloud players. You know, that kind of game has kind of evolved. I mean, the old joke is what inning are we in, right? And, and I, to use a baseball metaphor, I think it's a doubleheader and game one is won by the cloud. Right? So, Amazon wins game one, game two is all about data. You guys, this is core to Boomi and I want to get your thoughts on this because data is the competitive advantage. But if you look at the pandemic and the stories that we're reporting on, and this reinvent specifically, that'll be a big story. The refactoring in the cloud is a big strategic effort, not just replatforming, refactoring in the cloud. So this is really where you guys are, I think, skating where the puck is. Am I getting it right, can you just share that vision? >> Yeah, John. From a vision perspective, I think the pandemic has really accelerated people's expectations. You know what we need to be more nimble, more flexible. And because they had a fair amount in the Cloud they have to understand what is the next tier, what is the next generation offerings that we put together tie together and connect. That is not only connecting systems, apps, databases, and clouds. You're connecting people, processes and devices. So we're going to have a great story here and out of this world about how we connect bio centric vest to a video system who a network monitoring hub to protect the officer's safety in Amsterdam in real-time. We can deploy officers to location all automatic. All decisions are automatic, all locations, cameras (mumbles) all automatically. And that's only possible, when we think about next generation technology that Boomi provides. Next generation capabilities by the other providers in that solution. >> Ed, before we get to the product announcements for the even, we'll get your reaction to that. I see in the cloud you can refactor, you got data, you got latency issues. These are all kind of go away when you start thinking about integrating it altogether. What's your reaction to refactoring as the next step? >> Yeah. So my regular, I mean, exactly what Chris said, but as our customers are moving to the cloud, they're not choosing any more, just one cloud. It is a multi-cloud it's multidimensional (mumbles), you got multi-cloud, you got hybrid cloud, you have edge devices, et cetera. And our technology just naturally puts this in the space to do that. And based on what we see with our customers, we actually have, we've connected over 189,000 different devices, application points, data endpoints, et cetera to people. And we're seeing that growth of 44% year on year. So, we're seeing that explosion in helping customers, and we just want to accelerate that, and help them react to these changes as quickly as they possibly can. And a lot of it doesn't require, you know, massive upload project technology. We've been lucky enough to be visionaries that with our deployment technology, being able to embrace this new environment that's coming up or we're right at the forefront of this (mumbles). >> Yeah. I love the intelligence saying, I love hyper automation. Okay, let's get into the product announcements of Out of This World event. What are some of the announcements, and share with us the key highlights. >> Yeah. So first and foremost, we've announced a vision in our tactic. So I talked about the 189,000 applications that we did data endpoints, et cetera, that our customers are picking today. And they're moving very, very rapidly with that and it's no longer about name, connections, and having these fixed auxiliary that connects to applications you need to be able to react intelligently, pick the next endpoint and connect very quickly and bring that into your ecosystem. So we've got this vision towards the connectivity service that we're working on that will basically normalize that connectivity across all of the applications that are plugging into Boomi's iPaaS ecosystem and allow customers to get up and running very quickly. So I'm really excited about that. The other thing we announced is Boomi event streams. So in order to complete this, we can't just, we've been on this EDA journey Event-Driven Architecture for the last couple of years, and embracing an open ecosystem. But we found that in order to go faster for our customers, it's very, very important that we bring this into Boomi's iPaaS platform. Our partnerships in this area are still very important for us. But there is an avenue that our customers are demanding that, "hey, bring us into your platform." And we need to move faster with this, and our new Boomi event streams will allow them to do that. We also recently just announced the Boomi Discover Catalog. So this is the, this is an ongoing vision us. We're, building up into a marketplace where customers and partners can all participate, whether it's inside of a customer's ecosystem or partners, or Boomi, et cetera, offering these quick onboarding solutions for their customers. So we will learn intelligently as people have these solutions to help customers onboard, and build, and connect to these systems faster. So that's kind of how they all come together for us In a hyper automation scenario the last thing too, is we are working on RPA as a last mile connectivity that's where we start RPAs today, you know, gone are going to be the days of having RPA at a desktop perspective where you have to have someone manually run that. Although its RPA our runtime technology extends the desktops anyway. So we are going to bring RPA technology into the IPaaS platform as we move forward here so that our customers can enjoy the benefits of that as well. >> That's real quick. It was going to ask about the fence stream. I love this RPA angle. Tell me more about how that impacts is that's that's what I think, pretty big what's the impact of when you bring robotic processes on our RPA into iPaaS, what's the, what's the impact of the customer? >> The impact of the customer is that we believe that customers can really enjoy true cloud when it comes to RPA technology today, most of the RPA technologies, like I said, are deployed at a desktop and they are, they are manually run by some folks. It helps speed up the business user and adds some value there. But our technology will surely bring it to the cloud and allow that connectivity of what an arm robotic process automation solution will be doing and can tap into the iPaaS ecosystem and extend and connect that data up into the cloud or even other operating systems that the customer (mumbles). >> Okay. So on the event streams that you did, you guys announced, obviously it's the best part of the embedded event driven architecture, You guys have been part of. What is, why is it important for customers? Can you just take a minute to explain why event streams and why event driven approaches are important. >> Because customers need access to the data real time. So, so there's two reasons why it's very important to the customers one is Event Driven Architectures are on the rise, in order to truly scale up an environment. If you're talking tens of millions of transactions, you need to have an Event Driven Architecture in place in order to manage that state. So you don't have any message loss or any of those types of things. So it's important that we continue to invest as we continue to scale on our customers and they scale up their environments with us. The other reason it is very important for us to bring it into our ecosystem, within our platform is that our customers enjoy the luxury of having an integrated experience themselves as they're building, you know, intelligent connectivity and automation solutions within our platform. So to ask a customer, to go work with a third party technology versus enjoying it in an integrated experience itself is why we want to bring it in and have them get their (mumbles) much faster. >> I really think you guys are onto something because it's a partnership world. Ecosystems are now everywhere. There's ecosystems, because everything's a platform now that's evolving from tools to platforms and it's not a one platform rules the world. This is the benefit of how the clouds emerging, almost a whole nother set of cloud capabilities. I love this vision and you start to see that, and you guys did talk about this thing called conductivity marketplace. And what is that? Is that a, is that a place where people are sharing instead of partnershipping? I know there's a lot of partners are connected with each other and they want to have it all automated. How does this all play in? Can you just quickly explain that? >> Yeah, so in the last year we launched and we actually launched open source community around connectors and that sort of thing we invested pretty heavily in RSDK. We see quite a big uptake in the ecosystem of them building specific connectors, as well as solution. And our partners were very excited about partnering with us and (mumbles) to markets and those sorts of things that they can offer solutions to their customers on a marketplace. So, so we are reacting to the popular demand that we have from our partners and customers where they say, Hey, we'd love to participate in this marketplace. We'd love to be able to work with you and publish solutions that we're delivering more customers. So, so we're, we're fulfilling that mission on behalf of our customers and partners. >> You know, Chris, when you look at the cloud native ecosystem at the high level, you're seeing opensource driving a big part of it, large enterprises, large customers are moving to that next level of modern application development. They're partnering, right? They're going to out, outsource and partner some, some edge components, maybe bring someone else over here, have a supplier everything's confide now in the cloud, AKA dev ops meets, you know, business logic. So this seems to be validated. How do you see this evolving? How does this iPaaS kind of environment just become the environment? I mean, it seems to me that that's what's happening. What's your reaction to the, to that trend? >> I think as iPaaS evolves we've extended the breadth of our iPaaS dramatically. We're not an integration platform. We're, we take the broadest definition of the word integration I guess I'll say it that way. You'll be integrating people. Connecting people is just as important as connecting cloud applications So, you know, that that's part one in terms of the vision of what it is two is going to be the importance of speed and productivity. It's critically important that people can figure out how to reconnect because endpoints are exploding. You have to connect these extraordinarily quickly infractions of the amount of time that it ever took and coding, code is just not the way that that works. You have to have it abstracted and you have to make it simpler, low-code, no-code environments, configuration based environments, make it simpler for more people outside of IT to actually use the solutions. So that's where these platforms become much more pervasive than the enterprise, solve a much bigger problem, and they solve it at speeds. So, you know, the vision for this is just to continue to accelerate that, you know, when we got started here, things used to take months and months, you know, it came down to weeks, it came down to days, it's in to hours. We're looking at seconds to define connectivity in an easy button, those get connected and get working. That's our vision for intelligent connectivity. >> Okay, so we're talking about hyper automation in the future context. That's the segment here? What is a feature conductivity? Take me through that. How does that evolve? I can see marketplace. I can see an ecosystem. I see people connecting with partners and applications and data. What is the future of connectivity? >> The vision, right? For connectivity, and they talk about our connectivity as a service, but you know, you have to think about it as connectivity instead of connectors, like an NBO, a thing that talks to it, and what we look at is like, you should be able to point to an endpoint, pick a cloud app, any cloud application.  You have an API. I should be able to automatically programmatically and dynamically, anytime I want go interrogate that, browse it in the button and I've established connectivity, and the amount of take, in the amount of time it's taken me to explain it, you should almost be able to work through it and be connected to that and talking to that endpoint, we're going to bring that kind of connectivity, that dynamic generated, automatic connectivity, in to our platform, and that's the vision >> And people connect to user from a product standpoint and this should be literally plug and play, so to speak, old, old term, but really seamlessly, automated play, automate and play kind of just connect. >> Yes, absolutely. And what Chris was talking, I was thinking about a customer to be named, but one of the, during one of the interviews coming up at Out of this World, the customer was describing to us today, already the capabilities that we have, where he is, a CTO was able to get an integration up and running before this team was able to write the requirements for the integration. So, so those are the types of things we're looking to continue add to, to add to. And we're also, you know, not asking our customers to make a choice. You can scale up and scale down. It's very important for our customers to realize whether the problem's really big or really small our platforms there to get it done fast and in a secure way. >> I see a lot of people integrating in the cloud with each other and themselves other apps, seeing huge benefits while still working on premise across multiple environments. So this kind of new operating models evolving, some people call it refactoring, whatever term you want to use. It's a change of, of a value creation, creates new value. So as you guys go out, Chris, take us through your vision on next steps. Okay. You're, you're going to be independent. You got the financing behind you. Dell got a nice deal. You guys are going forward. What's next for boomi? >> Well, listen John, we, we, you know, we couldn't be more excited having the opportunity to truly unleash, you know, this business out on the market and you know, our employees are super excited. Our customers are going to benefit. Our customers are going to get a lot more product innovation every single day, we are ready to put out 11 releases a year. There's literally a hundred different features we put in that product. We're looking to double down on that and really accelerate our path towards those things what we were talking about today. Engagement with our customers gets to get much better, you know, doubling down on customer success. People support people, PSL in the field gets us engaging our customers in so many different ways. There's so much more folks that when we partner with our customers, we care about their overall success, and this investment really gives us so many avenues now to double down on and making sure that their journey with us and their journey towards their success as a business and how we can help them. Some of them, we help them get there. >> You guys got a lot of trajectory and experience and knowledge in this industry I think. It's really kind of a great position to be in. And as you guys take on this next wave, Chris McNabb, CEO Boomi, Ed Macosky, SVP, head of projects, thanks for coming on the cube, and this is the cube coverage of Boomi's Out of This World. I'm John Furrier, your host. Thanks for watching. (upbeat music)

>> Narrator: From around the globe, it's theCUBE with digital coverage of AWS re:Invent 2020 sponsored by Intel, AWS and our community partners. >> Hello, welcome back to theCUBE's Virtual Coverage of AWS re:Invent 2020 virtual. Normally we're in person. This year because of the pandemic, we're doing it remote. We're Cube Virtual covering AWS re:Invent Virtual. I'm John for your host. We are theCUBE Virtual, two great guests here Linda Tong a general manager, AppDynamics and Dave McCann vice-president of AWS migration, marketplace and control services. Welcome to theCUBE. >> Thanks so much for having us. >> Good to see you again John. >> Linda we were talking to some AppDynamics folks and some of your customers, obviously we've been following the growth of the marketplace for many years. The confluence of the tailwinds of the innovation going on with COVID and post COVID strategies is about helping customers where they are and they're not in the office anymore. They got to get the job done. This is really important on this cloud migration of getting software in the hands of people to write these modern apps. It's a big theme. What's your perspective on this right now, because you guys are partnered with Amazon, share your vision. >> Yeah, absolutely. And you nailed it. It's with COVID-19 our customers like IT organizations are finding this need to accelerate their migration to the cloud. And what's more important is they're finding that more and more of their customers are engaging through digital experiences and with the influx of people leaning on those digital experiences during COVID, performance issues are becoming more and more apparent. And so we're helping our customers as they migrate to the cloud. And specifically to AWS, it's a big partnership for us because we need to understand how our customers and how they manage performance through these transitions can stay flawless so that they can manage those experiences for their end users. >> Yeah, Dave, I've been watching this discovery observation space, observability, service meshes, Kubernetes, cloud native higher level services have really gotten popularity have gone mainstream. So there's more and more demand for I won't call it point products. That's an old term, but in the cloud, these are just higher level services that people are adopting more of. You're seeing huge pickup in the marketplace of companies who are selling through there and engaging but it's not just selling, you're integrating. What's your vision for all of this? >> So, John, you're absolutely right. Our customers as they migrate more and more applications to the cloud and in some regulated industries they still have applications running on premise. They're really actually standing up a new operating model where they not only want observability of what's going on but I feel what we would call service management framework or a set of tools to manage the application portfolio. And companies around the world are putting together new common instance of AWS native services, such as CloudWatch CloudTrail, Service Catalog, AWS Config, Control Tower with best in class vendors like Cisco AppDynamics. And each company is building their own collection of tools into management framework that allows them to optimally modernize and manage their application portfolio. And it's a rising topic around the world. >> Linda, I want to get back to you on AppDynamics you're the leader of the team as general manager, congratulations. You know a little bit about software in the cloud and CloudScale and your career going back to Google now at AppDynamics you've seen a lot of the changes. What specifically value do you see AppDynamics and Amazon bringing to the market today? Because the world's changed. It's still large scale, there's faster speed but you can't just buy things like anymore, I've got to go in send a ticket request, go to procurement, developers want to integrate immediately. They need to integrate when they see a problem they got to integrate technology. This seems to be a trend. What's your, where is AppDynamics bringing the value of AWS to the market? >> Absolutely I think it's threefold. One it's for a lot of these developers, as they start to migrate their applications and modernize them with AWS and all the great services that are available we can partner to help them with that modernization effort while giving them visibility into the performance of those applications to make sure that they don't miss a beat as they deploy those on these new sets of services over AWS. The second thing is, for those customers that are leveraging AWS for that migration, we have a seamless integration between AppDynamics and AWS. So you can buy our service directly through AWS marketplace. So that becomes a really easy procurement. And then on top of that, as, a lot of developers have to manage hybrid employments, so new modern applications has done AWS as well as some of their traditional applications that are talking to each other. They can get that full end to end visibility leveraging AppDynamics so that they can understand what's going on across the entirety of their business as they start to lead these transformations across our organization. >> Dave, just comment on if you can, 'cause I know a little bit about some of the things you put in place, the enterprise I forget development or sales program where at the prices can be more friendly. I think this is kind of a use case where this is proving enterprises can get what they need in the marketplace that not only is it successful but you have traction with this. What's you take on... >> There's a number of motions that we're doing there John, to help large companies around the world who may have, dozens, hundreds and in comes cases with fortune 100 they're thousands of applications. And so you actually have to solve multiple challenges that the company has. On the procurement side, we're obviously working with AppDynamics to publish as a service right in AWS marketplace. And we have over 300,000 customers worldwide only AWS marketplace who are subscribing to software and provisioning out to hundreds and thousands of developers, all of whom are using their own AWS accounts. So on that provisioning and subscription experience we work deeply with the AppDynamics team to meet that a really seamless experience from discovery to provision to meter and billing. On the interoperability front, as Linda mentioned, our customers want these best in class tools like AppDynamics to work well with the other AWS services so that they can really have a very modern DevOps pipeline for those applications that are moving to more of a CICD model. And for people who are still running in a bit more of an Intel, ITSM model, they've still got to manage and monitor applications that haven't quite got there in the full modernization stack. So this is actually happening not just with the customer, the enterprise or with the ISV AppDynamics, this transitions' also working with all the consulting firms. And a lot of the large software resellers around the world, the computer centers of Europe the right spaces, the presidios of North America. The DXEs of Asia Pacific. These consulting partners are also using tools such as AppDynamics so to become a managed service provider. And in some cases on that journey to the cloud no join the customer saying I'm really busy I'm modernizing applications. Hey consulting partner, can you manage some part of my infrastructure, some part of my stack? And tools like AppDynamics and Kubernetes and AWS become really central tool kits to the new emerging managed service providers that are all around the world. >> Yeah, and I talked about this years ago with Andy Jassy and I think we were riffing on this run this new set of category creations of services and companies. Linda this appears to be one of those cases where, there's a category with existing spend and existing customers. So what he just said is interesting. And I want to get your thoughts because these are these points of these new areas where AppDynamics can potentially help enterprises. What are some of the areas that you see AppDynamics helping enterprises in their cloud adoption journey 'cause they want some cloud native we see Hybrid and all the announcements, Outpost, now Edge it's a distributed computer. You need to have software at every piece of the puzzle. So what's your, what areas can you share specifically? >> Absolutely and so, like Dave was just saying it's, as these organizations start to make these major cloud migrations, one, their applications are getting actually significantly more complex than they've ever been. And they're now spanning a much broader ecosystem than they've ever spanned before. So that the kind of coverage that IT organizations and DevOps needs to cover not only is seeing this explosion of data but it's also now spanning areas of control that some of these folks have never had to think about before. And so the value of AppDynamics is our ability to be able to ingest data from your cloud native applications your traditional applications, all different sources of domain data that you want to get including things like security data. So we can start to correlate that in a meaningful way and then tie that back to business insights. And so the way that AppDynamics is actually bringing value to the table is not only helping our customers get visibility across the entire stack, but actually only surfacing the most meaningful insights to help them act on that those performance issues that they might see and more meaningfully manage their businesses. >> Linda I think you guys are onto something really big not just on the wave and just the positioning but one of the trends that we're reporting and we're going to be teasing out all week three weeks here is automation is great but that's just baseline. Everything is a service really speaks to some of the things that you guys have to put in place 'cause the mandate is everything should be a service. Now, I mean, I'm overgeneralizing but that's generally the ivory tower C suite message. Make it as a service cloud scale is beautiful, but then you when you pass it down to the teams, that's like that's not easy boss. It's not easy to do. That's really kind of what you're getting at here. It's not just automation and DevOps. It's the business model. >> Absolutely it's the intelligence it's once you create thousands and thousands of services, how do you manage them effectively and know what matters and what doesn't? >> Dave your final word here on on this point is when you think about that if you believe that to be true, then I'm just going to be downloading services whenever I need them. So it's almost like quasi self service managed services kind of coming together in real time or with my off base there. What's your take on that? >> No, we're actually working together with that dynamic and so all these kinds of things. So as we proliferate services, John and, AWS has got over 175 services and application is made up of many components. So how do you actually correlate an associate all the resources that make up that application? And if you think about dynamics name is the application and dynamics what's going on with the application. So we actually just launched today service catalog application registry, which is a new API surface for the AWS service catalog that allows you to define NGS on all the AWS resources from a cloud formation stack set all the way down into an easy to instance and associate that's an application known. And so the higher level of abstraction is what we talked about is management of the application. And what customers want to do, CIO's want to manage the application all the resources associated through the application whether the application is running well, is it secure? Is it on budget? Whether it's actually running? So application management is kind of where people are going even though their application is made up of dozens of associated services. So this is the next frontier. >> Well you guys are just great to have on world-class partnership two leaders, AppDynamics, story history they continue to do well. And even now with the world going on, Dave congratulations on your success. Final question for both of you is, where's the partnership go from here? I think it's a great success story. What's in the store for the future? >> Linda. >> Yeah to the moon. It's look AWS is an amazing partner. And Dave is a great guy to work with and where we are going is to help our customers build world-class applications and be able to manage them and modernize those effectively. And there's no way we could do that without partners at AWS. So it's a, there's a long-term relationship here. >> Well, congratulations, Linda Tong general manager AppDynamics. Thanks for coming on, and virtually at least we'll see you on the Interwebs during the next couple of weeks here, Virtual re:Invent Dave McCann. Of course, we'll see you again and great to watch you continue to grow. Is there any new title is going to add to your thing marketplace now it's migration, control services come on. >> With innovation culture we keep innovating. >> Great to have you guys on. Thanks for, thanks for sharing, appreciate it. >> John, Linda thank you very much. >> Thanks. >> Thanks for that great insight. Really appreciate it. I'm John from theCUBE you're watching coverage of re:Invent 2020. This is theCUBE virtual. (upbeat music)

>> Announcer: From San Francisco, it's theCUBE, covering GitLab Commit 2020. Brought to you by GitLab. >> Hi and welcome to CUBE's coverage of GitLab Commit 2020. We're here in San Francisco, actually, the first CUBE event of the year, and I'm Stu Miniman here with John Furrier, the founder of SiliconANGLE, one of our main CUBE hosts. John, always great to kick off the year with you, and of course, we're digging in on the developer world, cloud native. Nothing better than, you know, the opening keynote talks about, you know, there's a line we've been talking for years, software's eating the world and what are the ripples that are happening on. So, Tom, great to see you, and how come it's so cold here in San Francisco? I mean, I could be back in Boston. >> Coldest winter. I've spent summers here years ago, but it's not summer anymore. But Stu, it's football playoffs. Patriots aren't in, so sorry to hear that our Pats didn't make it. But great to see you. I think one of the things this year in 2020, a new decade, 10 years of theCUBE, looking back, we have been on all the major developer waves since 2010. We jumped on the Hadoop wave with Cloudera. We saw the beginning of that wave of OpenStack to cloud, Kubernetes, containers, the whole nine yards. We've been in the developer community. But this year, cloud native not only is going to continue that expansion of developer CUBE action, but the cross-connect with mainstream, and this is to me the biggest trend of the next 20 years is going to be the open systems model of cloud, just like the open systems interconnect in the '80s created a whole new computer industry, changed the landscape, changed the value proposition, this year, I think we're going to start to see real visibility of value creation where the developers are not just the cliche of the value proposition. That's the cliche. Oh yeah, developers (mumbles). No, no, this is a whole nother game change. With CloudScale, with data, with AI, you're seeing again the importance of this. I think cloud native represents to me that next generation, because with multicloud, there are new criterias out there for success, new requirements. Same game, writing software. Whole new dynamic. Networking, Stu. >> Yeah. >> Compute. >> Yeah, John, and I love actually, I think this was a great show to help us kick it off because you talked about those mega waves out there. We've been watching the growth of some of the huge platforms. AWS was on the keynote stage this morning, Google is doing the closing keynote, and of course one of the major acquisitions, you know, in the relatively recent past was Microsoft buying GitHub. And so we know that developers are so important, but the message we heard from GitLab is it's not about silos anymore. They said not only the dev, the sec, and the ops, but finance and marketing. Everyone needs to get on the same page. GitLab's vision, of course, is that everyone should be using the same tools. That was something that I heard, that we both heard last year at AnsibleFest, that if you're in the same tools, sharing the same information, in the same communication channels, you're going to be able to move fast, and that is what companies need to do. They need to be able to react fast. The business should be able to move. Those software cycles need to be shortened. And that's the mission and the big goal that GitLab has, and I think it's representative of the wave we've been seeing. >> Let's get into the keynote analysis, but before we get to that, I want to, you brought up a point about GitHub. I think there's a real dynamic of GitHub being acquired by Microsoft for many reasons. One is Microsoft's got this cloud called Azure, and not the only cloud in town. Amazon has AWS. And so multicloud is going to be a theme we're going to see more and more of. And so this idea of open and transparent community in open source is interesting in a world where everyone's siloing. I mean, let's face it, GitHub is owned by Microsoft. LinkedIn was acquired by Microsoft. You're starting to see the walled garden world come back again where data is really valuable. And so what's interesting to see is you're seeing a company with GitLab, really one of the first ones to say, "Hey, you know what? "We're going to be anti-walled garden. "We're going to be open. "We're going to be transparent." And again, integrated platform. The cloud is demanding companies have integration requirements that are well above what we saw years ago, and this is now a new table stake. This to me is the real walkaway. What's your thoughts on the GitLab keynote and those industry dynamics? >> Yeah, some great points there, John. Right, first of all, open, fully open. You know, the CEO and the CMO, some of the things they were talking about is sometimes the team doesn't know who's doing the contribution because they're getting regular contribution. They said, "Hey, I didn't see them in the group." Oh wait, that's a customer, that's a partner, someone from the outside doing it. Fully open and transparent and remote. They now have over 1100 employees. Four years ago there were nine of them. And it is fully remote. Actually, do a little compare and contrast. Talk about Amazon. John, how many people do we know that have joined Amazon, and the first thing you do is you move to Seattle, because that's just where they have. Now, of course they've got multiple locations. They've got thousands of employees down in DC, in Massachusetts, in New York City, all over the place, but the core decision-making, even though they are very distributed, Seattle is where everything happens. That's where most of the people live. So GitLab, not only is the company remote, but that's the tooling that they've built really is to enable people to work wherever they are. From GitLab's standpoint, they said hey, we have, one of our software people, she lives in New Zealand, and she has her own power. She's completely off the grid except for her internet. As long as she has internet, she can contribute to the team and participate in the building of GitLab. So it's fascinating. You know, we've talked for years ago the future of work and how that happens. So the tooling as enablement not only to allow everybody to work together, but work together wherever they are and that remote capability, and it is very challenging. You know, we watched Zoom IPO last year, and they're trying to help with that whole wave, but we know that there's a challenging dynamic of being able to work wherever you are. >> So they brought up some stats, interesting. Scale and integration are a big theme. Looks like GitLab's getting it. They made some good calls. Have integration, very friendly integration, very open. And they're essentially consolidating a lot of the different tool chains out there. You look at Jenkins and other things out there, from continuous integration and variety through now mainstream. They got 1100 employees, okay. They got a valuation of $2 billion. They just raised $436 million. They have cash on hand of 350 million and they're going to do revenue. So you have essentially scale in GitLab with an integration story which the cloud guys are being forced. That's my opinion. Do you agree with that and do you think that GitLab can continue the pace of growth given where they're at? >> Well, John, they have something that everybody wants. It's that recurring revenue. So in February 2020, they will have passed the 100 million of ARR, and they've announced that they're going to IPO later this year. We're going to have the CEO on later. I'm a little surprised how fast they are looking to IPO, John. We've seen so many companies that not only do they do big raises, but it's not $100 million, it's two or $300 million. You know, when do you have profitability? When do you go public? So I'm a little curious why there's almost a race for GitLab to go IPO. But absolutely they are catching a lot of these waves. When GitHub was taken off the table, boy did I see Google moving fast to work closer with them. It's no coincidence that Amazon is here, because there's been a little bit of concern from GitHub as to, oh, if I'm doing GitHub, does that mean that I'm kind of being pushed closer to Microsoft Azure, as you said, that cloud. I've read recently GitHub's trying to make sure that they stay independent. We know the GitHub team. And the other big thing we saw is GitLab, about three years ago, they really differentiated themself. They are not just a GitHub alternative. You talked about Jenkins. The CICD is a huge piece of what they're doing. The source code management and CICD, putting those together are the core of what they're doing, but they're trying to be a single tool chain. Boy, when I look at the, you know, the mesh of tooling that GitLab kind of is poking at a little bit, we know a lot of these companies. Some of them are public. Some of them are unicorns. You know, to say that, oh, well, we're going to all of your security chaining. We know how deep and gnarly the security world is. But GitLab, being open, they're going to partner with all of these environments. It's not that you can only use the GitLab pieces. But the audacious goal to say that they are going to be kind of the one tool chain to rule them all is a good goal. I'm hugely supportive my entire career of trying to get rid of silos. But we know that you're still going to have corner cases and use cases that I'm going to need to go deeper. I'm still going to use those best of breeds. And that's one of the things that we're going to look at this year, John, that platform, just like I could go all in on AWS, but I'm still going to use lots of tools on Amazon and I'm going to use other clouds. >> What's your take on, great analysis, by the way. What's your take on as cloud native becomes multicloud where you got edge developing, we got outposts. You're seeing Azure with their stuff. Outposts is Amazon. You now have more pressure on speed and agility than ever before. How does GitLab's story play well into that, and as enterprises have to be faster. Not just enterprises, service providers. There's other new companies doing more cloud and on-premises and edge, AKA multicloud, too. >> Yeah, so I actually, I loved the problem statement that they nailed with talking about the tool chain that's out there is they said more than 50% of devops time is wasted on logistics and repetitive tasks. And John, if you talk about multicloud, it's not just simple to say, "Oh, hey, I threw in a Kubernetes layer "and therefore I can move from my Auzre "to my GCP to my AWS." That's not how it works. I have all the underlying things. I have the interface. That tool and user interface knowledge is challenging to overcome. There are some tools like GitLab, of course, that help me span across those environments. HashiCorp is here at the show, a partner of GitLab. I was just meeting with them recently. And of course, they're going to spread across the multiple cloud environments. But that is really where the meat on the bone is, John, if you talk about multicloud and cloud native. Where are these pieces that can help customers make sure that I'm not too deeply locked into one environment and still being able to leverage the various services that I might want to use across multiple clouds. >> Yeah, I mean, to me, the big takeaway, Stu, on the keynote I made in my notes here is that what I was impressed with is, obviously the transparency that they have is, I love the openness. You know, I mean, this whole silo thing's definitely real. You're seeing more and more. So open and transparent's key. But when you look at what they really have here is the integration story, and cloud is forcing that, in my opinion. But they announced what they call a complete devops platform delivered as a single application, from manage, plan, create, verify, package, secure, release, configure, monitor, and defend. The spectrum of a devops platform. So that to me, I think, is the step that needs to be taken. The question I have is how real is it, in your opinion? Is that what a lot of other people are saying that they have? What's your analysis of that story, reality, legit, and what's their prospects? >> Yeah, well, definitely GitLab has great adoption. The two pieces is the SCM and the CI are the core of what they're doing, and they know that's where people usually kind of walk in the door. Then they kind of land and they look to expand from that. GitLab's made a number of acquisitions, and from 2020, they are going to really double down on making sure that they dig deeper into some of those environments, especially security, planning, and ops were the three priorities that they had there. So, you know, John, we know when you talk about you're trying to be all things to all people, there are going to be things that you will do well and things that you can do great, but, so it is an audacious goal, and with a broad community supporting it. >> Well, we know, you've reported on this and we've told stories about it is that if there's too many tools in an enterprise, you have this tool shed effect where there's no real platform around it, and I call it a tool shed, but if you have too many tools laying around, they're not cohesively integrated, that's a problem that becomes tool sprawl. So this has become an issue. We saw it in the big data world. We saw unification as a strategy for that. Databricks, for example, is a great example of one company that's taken advantage of that trend. Is there a tool problem in the dev space that GitLab's taken advantage of? >> Absolutely, John. And I think something we're going to dig in deep today, we've got a couple of practitioners on, we've got the partners, we've got the executive team from GitLab. John, thank you so much for helping me kick off GitLab Commit 2020 and a massive schedule of theCUBE coverage throughout the entire cloud native multicloud ecosystem. All right, be sure to check out thecube.net for all of the shows that we will be out in 2020 as well as a tremendous back catalog that you can search. For John Furrier, I'm Stu Miniman. Thank you for watching theCUBE. (electronic music)

(upbeat techno music) >> Narrator: From New York, it's theCUBE, Covering Escape/19. >> Okay, welcome back to theCUBE coverage here in New York City for the first inaugural Multi-Cloud Conference called Escape/2019 as in gathering of industry thought leaders, experts, entrepreneurs, engineers, really having substantive conversations around what multi-cloud is, what it's going to look like, what are some of the thing, technical and business opportunities around that, really small intimate conference. Again first inaugural conference. I'm here with my next guest to talk about that Chris Smith, Vice President of Engineering, on Data Science at Ticketmaster. Chris, thanks for coming on. >> Thank you very much Don. >> Appreciate taking the time. >> Glad to talk to you. >> Practitioner out there, you know, we all go scar tissue. >> Yes we do. >> If you don't have scar tissue, if you're not breaking things and then the learning from it then you're not advancing. But sometimes you don't want to step too far forward right? >> Yep, yep. >> Can you get back it's like you know. So you guys have a great experience. Legacy business, I remember buying tickets when I was going to conference back in the day when I was in, you know, in college. >> Yep. >> Buy it at Ticketmaster. >> That's right, that was Ticketmaster then, Ticketmaster now. >> Now it's lot of online provisioning of all direct to consumer. So you guys are a journey, tell the story. >> Well certainly, the company Ticketmaster, has had an incredibly long journey, starting back our first concert was Electric Light Orchestra which kind of like puts that in in context. >> (laughs) I was in eighth grade, '79. >> Yeah, yeah that was back at ASU. And even then we were a very innovative technology company we were making ticketing platforms that performed better, got more capacity out of the hardware than anybody else could do, anything close to that. We were really pioneered that idea of the what was at the time called the electronic ticket. Which was the idea that, you know, you could go to any store that was selling tickets for an event and the same inventory would be available at each store instead of the old model of a bunch of tickets getting sent out to each place >> That was bad-ass back in the day. >> That was really cutting edge and we've been evolving ever since then for 40 years. We were also very early onto the web scene. We were selling tickets online before anybody else was and before most people were selling anything online really to a degree. So we've been pioneers in a lot of areas, we see ourselves as the technology partner for the live events business. That's really what we are. And as a consequence, we're always sitting on that edge right? Trying to innovate and move to new opportunities but at the same time trying to provide that quality of experience at scale. >> Yeah. >> That is so critical to the business. >> And there's a big business so it's not like it's your nimble start up but you got to be agile. What are the learnings? Take us through the cloud learnings as you guys pioneered and started to go into that pioneering mode which was okay, you don't have to be a rocket scientist to figure out what a cloud's going to do. So you guys probably said hey, we got to go look at this, let's go pioneer our impact, take us through that what happened? >> Yeah absolutely, and I think there's two interesting contexts that started that conversation right? One was we're one of the few online businesses that launches a denial of services attack against itself on a regular basis, basically every day, right? And so we have traffic patterns that are unusual even for a typical e-commerce site where we might see loads that are a hundred x, you know beginning of a Taylor Swift on sale. There's going to be traffic like no one's business. And then when all her tickets are sold, there's not going to be nearly as much traffic right? And so that is the nature of our business and cloud is very attractive for its elastic capacity. When we were running on prim, we have to provide all that capacity all the time, just to have it for that one peak moment that might literally be the highest traffic level we see all year, right? So that drew a lot of the interest in looking at the cloud in the first place. And then the other aspect was we'd been working on, you know we'd been running on prim for nearly 40 years at the time and there is a lot of technical debt that had accumulated in the system at that point. And so, there was an interest in maybe potentially being able to leverage cloud vendors' infrastructure, and migrate systems onto that and then sort of declare bankruptcy on some of that technical debt rather than trying to pay it off. And so that, those were the two thoughts that were driving that conversation. I think we got really excited by the possibility and we committed really heavily to the idea of a strategy of just moving aggressively into the cloud as fast as we possibly could. And we knew that in the process, that we would be breaking some things, we'd be you know discovering some challenges et cetera, and that's definitely what happened, right? >> (laughs) What was the big learning? >> I think the biggest learning was that, you know, we had been developing systems for decades literally, with our on prim environment and so the systems were actually very well tuned for that on prim environment and that on prim environment was very well tuned for them. >> Yeah, yeah exactly. >> And it clouds use-- >> On all levels, hardware, software. >> Yeah, all the way through 'cause it's a fully integrated, vertically integrated solution. We build a lot of this stuff custom ourselves. >> John: Yeah, and we would decompose all that. >> And so it was very difficult to migrate some parts of that to the cloud and more importantly we're pretty smart guys, we can figure out how to move stuff into the cloud. But then to do it in a cost effective manner. Required in a lot of cases, really dramatically changing the design and architecture even of the software at a pretty fundamental level that you just can't do overnight. And so ironically, you know, the technical debt that we had in our infrastructure didn't seem quite so huge once you start thinking about the technical debt of the entire stack, right? And so then we realized that we could be much more strategic about how we went after our cloud strategy and that's kind of where we are now. Where we are being smart about, there's a lot of new products that are being developed, that, you know, we can build from the get go with the idea of them being designed for the cloud. >> Cloud native. >> Exactly, so we have a lot of stuff like that, that's just being built, in fact, the bulk of our website now when you go to visit it as a consumer, the bulk of that is running in the cloud right now. But, there are some really critical systems that are core to that experience, that are still running on prim. >> So you guys had to essentially re-architect the operating environment to take into account hybrid operating. >> Yes. >> Decoupling the critical systems that can't be tampered with, maybe put some containers of Kubernetes move some services around. But for the most part treat Cloud Native as Cloud Native, Greenfield apps and nurture-- >> Yeah but there's also refactoring opportunities. So there's a lot of opportunities where you need to go in and change the product anyway and that can be an opportunity to make things a lot more cloud friendly and better take advantage of the capabilities that the cloud has, so it's actually a mix of both. >> Give an example of a good opportunity to refactory, 'cause this comes up a lot in my CUBE interviews. Like okay, 'cause it's all opportunity, opportunistic, but what are the characteristics for a great refactoring opportunity the tune up? >> So a lot of times when you want to refactor really what you want to do is take a set of capabilities that you may have in a much larger system and pull 'em out and manipulate them and play around with them and do things differently. So, our ticket purchasing process we're constantly looking at tweaking the process. Now the core pieces of it remain the same right? But we might want to change the experience and provide something more innovative that's different from what people used to do. And so one of the areas we're working on for this as an example is reserve-less checkout. Where you just buy the ticket without ever actually reserving the seat. That's a very small minor change in the flow, but to make that really work you have to pull out the pieces of the system anyway right? And grab, say I want these four pieces to rearrange differently, so that's a great refactoring opportunity. You can make all those pieces, what we actually did is we've made those pieces into lambdas that are sitting in AWS, they're basically not running most of the time which is great. >> Yeah. (laughs) >> Really cheap when it's not running right? >> Yeah, exactly. >> Very efficient. But then when we need them they run very efficiently and more importantly we can now manipulate the order of operations for this stuff. So breaking things out into those composable parts whenever you know you need to do that anyway, it's a great opportunity to change it. >> So great for work flow refactoring there. >> Absolutely. >> Final question for you, I know we got to break for lunch, but, then really appreciate you coming and sharing your insight. >> Absolutely. >> As a pioneer in data science and data you got machine learning certainly is the engine of AI. AI gets math and cognition are kind of coming into it. Learning machines, deep learning, bla bla bla, what's your, in your opinion, what are some pioneering areas that are ripe pioneering grounds to dig into in data science and data? When you think about CloudScale, Hybrid and just, in general what are the ripe opportunities for people to pioneer in daily. What's the next frontier in your mind? >> So I think the trend right now that's maybe not the frontier, but it's now where the main shift is, is to moving into what I would call real time learning, right? Where you're doing refactor, reinforcement learning, or online learning of some form. Where you're literally, the data's arriving in real time, transforming your model in real time, learning in real time, that's key to our strategy and it's very very common. But I think in terms of where the frontiers are it's actually kind of everywhere, in the sense that the name of the game is the cost of doing that work is getting lower and lower. You know, data's getting cheaper, computes' getting cheaper, and also the products for doing it are getting more productized, so you need less expertise and you can deploy them more quickly. So what you want to look at is businesses that are traditionally been too low margin right? To apply machine learning to but have large scale, right? Which is like the commodity, everything in that's commoditized, right? Now there's an opportunity to, there's the cost have gone so low-- >> To squeeze insight out of those areas. >> That you can now optimize that small margin and get value from it with you know, otherwise like 10 years ago it would have been so costly to build a machine learning infrastructure for it. You would've lost more money than you would've gained. >> So you could, what your saying is, these areas that were not attractive because of cost in the past, that have large scale, there's penetration opportunities to create value and insight that could-- >> Absolutely. >> Bring in new franchises and new capabilities. >> And that's why I think you know the Andreessen's software's eating the world thing, that's what that's really about is as those costs get lower, as the ability to deploy gets easier, suddenly businesses that before didn't make any sense to invest in this way, they totally make sense and in fact there's huge opportunities to completely transform the landscape by getting in. >> Chris you're a man of our world, we love you, thank you for coming on theCUBE. >> Thank you so much. >> That's great insight. >> Look at this we're getting insider on the future of data, which I believe everything that he just said is totally relevant. You're an entrepreneur out there, you can attack big markets and get in there with a position with great IP, great intellectual property, again this is the modern world of computer science. >> It is. >> Don't ya think? >> It absolutely is. >> This is the benefit of scale and cloud. >> Absolutely. >> I wish I was 20 something years old again. (laughs) We've been through the ringer. >> Yes. >> Chris, thanks for coming on. Keep coverage here in New York for the first inaugural conference, Escape/2019, I'm John Furrier here, thanks for watching. (upbeat techno music)

>> Live from Seattle, Washington, it's theCUBE, covering KubeCon, and CloudNativeCon North America 2018. Brought to you by Red Hat, the CloudNative Computing Foundation, and the Antigo System Partners. >> Hey, welcome back everyone live here in Seattle for the theCUBE's coverage of KubeCon and CloundNativeCon 2018. I'm John Furrier, theCUBE with Stu Miniman, breaking down all the action. Three days of coverage, we're in day two. A lot of action at Open-source. 8,000 attendees, up from 4,000 North America, they were in China, they were all over Europe. The community's growing in a massive way. We had two great guests from Red Hat, all making it happen, part of the community. We've got Diane Mueller, whose theCUBE alumni director of community development, many times on theCUBE, good to see you, and Rob Szumski, principal product manager, both at Red Hat. Guys, thanks for coming on. Great to see you again. >> Yeah, glad to be here. - Great to be here. >> So the world's changing a lot, and there was some news recently around Red Hat. I can't remember what it was. Recently, something big news, but you guys have been big players in Open-source for years. We always cover it, we always wax on about the origination of it and how the evolution, but the CloudNative piece has gotten so real, and your role in it particularly, we've had many conversations, going maybe back to the OpenStack days of how OpenShift was developing, then the bet on Kubernetes that you made, Core OS acquisition, those two things I think, to me, at least from my perspective, really catalyzed a lot of things at the right time, right? So, from there, just a lot of things has just been happening really in a good way. Big tail wind for you guys, CloudNative app developers are using Open-source, CI/CD pipeline, and then also policy based up under the hood, completely big shift in moving the game down the field. So big congratulations first of all. But what's new? What's the update? >> The update is Operators. I think the next big thing that we are really focusing on, and that's a game changer for all the second day operations type things, and we'll make Rob talk about it in detail, is the rise of Kubernetes' Operators. It's not a scary thing, it's not like terminator day, or anything like that, but it is really the thing that helps us make the service catalogs, the Kubernetes marketplaces really accessible to all of the data bases as a service, and all of the other things, and takes out some of the complexity of delivering applications and database  as a Service to anybody running Kubernetes anywhere. >> Take a minute to explain Operator, real quick, and then we can jump into it, because I think this is a fundamental trend, that we're seeing. Developer trend is pretty obvious, it's been that word for awhile, CloudScale, ML, machine learning, and all the goodness around application development, but the Operator side of it has been an IT thing. But now you guys have a different, a new approach that's winning. What is it? What is Operator? >> Well, it's Kubernetes that has the approach, and I'll let you-- >> Yeah, so it's basically like the rise of containers was great, because you could take a single container and package an application and give to somebody, and know that they can run it successfully. And Operator does that for a distributed system in the exact same way. So you're using all the Kubernetes primitives, so you're not reinventing service discovery, and seeker management, and all that. And you can give somebody an entire Kafka stack, or a machine learning stack, or whatever it is, these very complex distributed systems, and have them run it without having to be an expert. They need to know Kafka at a high level, but not exactly all the underpinnings of it, because that's all baked in the software. >> And the benefit and the impact of the organization is what? >> And just to clarify, so this was added in, I believe Kubernetes is like 1.7, it's something that's in there, it's not something Red Hat specific- >> Yeah, it's like-- >> So you're extending Kubernetes so that you have a custom resource definition, which is an extensible mechanism for saying, hey, I've got a deployment or a staple set, but what if I want to have a new object called a MongoDB? That knows how to deploy, and manage, and upgrade MongoDB. So that's the extension mechanism that we're using. >> Yeah, so you got to think, there's certain applications that this is going to make, just a lot easier how I manage them, deploy them, things like that. Any specific examples you want to share as to-- >> All the clustered data bases. >> There's a lot of the application side in this model have been very excited about this. >> So its all the vendors and partners that want a hybrid Cloud story, just targeting Kubernetes, and we're using Kubernetes under the hood, and then everybody wants to run like a staple data base tier, whether that's Mongo and Couchbase, and Cassandra, whatever. And these are all distributed systems. >> Alright, so I want you to just perch, you said a hybrid Cloud. Explain that model, because there's just something in general discussion that is hybrid or multi means I'm running multiple places, I'm not necessarily stretching an application, but I have instances there, just want to make sure we're on the same page. >> So this would be more the compatibility that you're programming against when you're building an operator, is Kubernetes. It's not a Cloud offering, it's not OpenShift, so you're just targeting Kubernetes, and so you can run MongoDB on prem, in the Cloud, and have it function the exact same, by standing up one of these Operators. And then if that Operator has higher level constructs for how to do multi-cluster aware data rebalancing, you can take advantage of that too. >> And the Open-source status of this product is what? >> It's all Open-source, it's all in the github repos, there's a Google group for Operator framework, that anyone can come and participate in. We hold SIG meetings on the third Friday of every month, 9 a.m. Pacific Time, and it's a completely Open-source project. There's a whole framework around it, so there's the Operator SDK, the Operator Lifecycle Management, and Operator metering, all the tooling there to help people build and manage these Operators, and it's all being built out there in the open with the community's support and feedback loops. >> What's the feedback? What's the top feedback you guys are getting right now? Seeing right now? >> I have to say, this is really, like I've been hanging out with you guys like for the past three, four months on this topic, trying to get my head around it and everything, and we came here and we had two sessions, an intro session and a deep dive session, intro yesterday, deep dive today. Today's deep dive, the room was about 250 people, and they're were people outside of it-- >> Security guards blocking people from coming in. >> Nobody could come in and it's like, it's insane. It's like, everybody needs these things, and everybody wants to figure out that, and when you ask people in the room whose building one, half the room raises their hands. It's just crazy. This thing crept up on us really, maybe not on Core OS, okay, it crept up on me very quickly, and it's very rapid adoption. We have a Kubernetes Operators workshop on Friday, so not only do we have pre-conference days of like OpenShift Cons that are huge now, but now we're starting to book end, CNCF events and put on other things, just because, and that, we had 100 seats that we were hoping we would fill, and it sold out in like minutes once it got in there, and there's a waiting list of like 300 people. It is like one of, aside from Knative, and all the other wonderful hot things too, it is one of the most interesting developments I think right now. >> Thirst for the content. Would it impact? >> Yeah, and you can get all of the documentation is out there now, and people are already building them. We have a list of 50 community Operators. It's just, it's phenomenal how quickly it's growing. >> You know, Diane and Rob, it's funny because you know, we do so many of these theCUBE interviews, and this is our 10th year doing theCUBE coming up, and I remember the conversations going back in the OpenStack days, we would ask questions like, if you had a magic wand, what would you like, hope to have happened, right? And you know, those are parts of the evolution, where it's like, it's aspirational, things are being built. It seems now with Kubernetes, it's almost like, wait a minute, it's actually, this is like the goodness is so compelling, above and below Kubernetes that it's almost like uncomprehendible. You think about, oh this is actually happening. Finally the kinds of steady state kind of operational things that have been a pain in the butt for years-- >> Yeah, the toil, it's gone, for the most part. >> Yeah. >> So Rob, I've been having a lot of just thinking back to, you're employee number two at Core OS, when I first talked to Core OS, it was, we're going to build all of these individual tools, and we're going to Open-source them, and it's going to be good. We watched this just rising ecosystem and the CNCF, and it feels like what's nice and what's different that I see, compared to some previous things, is it's not one product or even a small group of companies. It's, I have this tool kit, and some of them work together, but many of them are independently used. We've talked to your peers earlier about it, etCD. etCD is totally stand alone, doesn't need to be Kubernetes. What have you seen, if you go back to that original vision, would Core OS just been, part of this whole ecosystem, and done it, if this was available, and has this delivering on a promise that your team had hoped to work on? >> Yeah, so we've always filled in where we see gaps, and so something like etCD, the concept is not new, and it comes from Google, and they have a system internally, and as Brandon got up on stage and said, we needed that coordinate, reboot, to grow out, to cluster of machines. It didn't exist so we had to build it. Same thing with how we wanted to manage Linux. There was no distro that even resembled what we were doing. Wanted to do automatic upgrades, people thought that was crazy, so we had to go build it. And so, but we always adopted the best of breed technology, when it existed. In our early bet Kubernetes, we just saw, this is the thing, and went for it. I don't even remember what version, but it was months and months before it was zero point oh, or one point oh, so it was, we've been doing it forever. And you just see the right thing, and it's the little nugget that you need, and if you don't see it, then you build it. >> What are you surprised about Rob, in terms of the ecosystem now, you mentioned some goodness is happening, still a lot more to do, visibility around value creation, you're starting to see spots where value can be created in the ecosystem, which is great. Still more work areas, but what's surprising you? What do you see as opportunities, challenges? Your thoughts, because this vision of ease of use and programmability, is happening, right? So there's still more work to do. What's your vision there? What's your thoughts? >> I mean, I think self service is key, so this is like the rise of the Cloud comes from self service for developers, and Kubernetes gives you the right abstraction, where self service for VM's, like OpenStack, which is not quite at the level of what you want. You don't want a VM, you actually wanted a place to deploy an application, you wanted load balancing, you wanted service discovery, you didn't want like a bare Ubuntu VM, and so Kubernetes raises you up to where you're productive, and then it's about building stuff on top. But what's interesting, in the space is, we're still kind of competing on Kubernetes installers, and stuff like that, so we're not even really into like the phase where people are being super productive on the platform, other than these leading companies. So I think we'll democratize that, and we'll have a whole new landscape. >> And so 2019 you see as what being a key theme for Kubernetes? >> I think it'll be Core stuff built on top, like all the serverless frameworks, a bunch of container natives storage solutions, solving some of these problems that folks are reaching out to external machine learning, but bringing that onto the cluster, GPU support, that type of stuff. It's all about the workloads. >> And tradition end users, you have a huge install base, with Red Hat, well documented, as the end users start coming in and looking at CloudNative, and doing a reimagine of their environment, whether it's IT span, IT investments, to have a run their coding and the deployments. It's going to change. 2019's going to have an impact on what I call mainstream enterprise, for lack of a better description. What's the impact of those guys, 'cause now, they now have head room, they can do more, what's the main stream enterprise look like right now with the impact of Kubernetes? >> I think they're going to start deploying applications and get like lower the time to business value, much, much lower. And I was just talking to a customer, and they ordered bare metal machines like a year ago, and they're still not racked and in the data center. And so people are still getting over that type of stuff, but once you have like a shared Kubernetes layer, you can onboard teams like crazy. I mean, name spaces are free, quote, unquote, and you can get 35 engineering teams on a Kubernetes cluster super easy. >> So they can ramp up in development teams basically, as they bring value in-house, versus outsourcing everything. They start getting development teams, this is where the action is. >> I think you're also going to see the rise of those end users contributing back things, to the Kubernetes community and as Lyft, and Uber, and everybody are great examples of that. Uber with Jaeger, and Lyft is, we were just in the Operators thing, and they raised their hand that they are about to Open-source it, a few Operators that they're building and stuff, and you're just going to see people that you didn't normally see. Often these large foundation driven things are vendor driven, but I think what you see here, is the end user community is now embracing the Open-source, is getting the legal teams there, allowing them to share their things, because one, they get more people to maintain them, and more people working on them, but it's really I think the rise of the end user we'll see, as they start participating more and more in here. And that's the promise of Open-source. >> And that's where CNCF really made it's bones. It wasn't really vendor led per se, it was really end users, the guys building out their stuff for the first time. You see Lyft for instance, great example, you guys did a Core OS, this is like the new generational model. Final question before we break. I want to get this out there. Get a plug in for Red Hat. What are you guys, what's the focus for the show? What's the news? What's the big story for Red Hat here at KubeCon this year? >> I think it's Operators, that's what we're here talking about. It's a really big push to once again get smarter workloads onto the cluster. We've got a really great hybrid story, we've got a really great over the air upgrade story that we're bringing from some of the Core OS technology, and then the next thing is, once it's easy to run 35 clusters, we need a bunch of workloads to put on there. And so we want to save folks from the toil of running all those workloads as well, just like we did at the cluster level. >> Awesome. >> Well put. I couldn't add more. One of the things that Core OS did, you hit the nail on the head earlier, is when there was something missing, they helped us build it, and with the Operator SDK, and the Lifecycle Management, and the metering, and whatever else the tooling is, they have really been inspirational inside of Red Hat. And so they filled a number of gaps, and it's just been all Operators all the time right now. >> It's great when a plan comes together. You guys got a great tail wind. Congratulations on all the success, and it's just the beginning of the wave. It's theCUBE, covering the wave of innovation here at KubeCon CloudNativeCon 2018, we'll be back with more live coverage. Day two of Three days of Kube Coverage. We'll be right back. (upbeat music)

(upbeat music) >> Live from Washington, D.C., it's theCUBE, covering Inforum D.C. 2018, brought to you by Infor. >> Well, back here on theCUBE, we are at Inforum '18. We're in Washington, D.C. here in the Walter Washington Convention Center. Not far from the White House. It's about a mile that way, and Capitol Hill's about a mile that way, I think. I know we're right in here, but I know we are smack dab in the middle of it. Dave Vellante and John Walls and Kevin Curry, who's the SVP of the global public sector at Infor. Good to have you with us. Good to see you, sir. >> Great to be here. Thanks for your time. >> So public sector, you're in the heart of it here, and you were telling us before we went on the air that you've got more than 700 clients here at the show this week? >> We do, we do. It's the best attendance we've had yet for Inforum, and I joined about six and a half years ago. And we built this business pretty much from the ground up. So it's been a great experience, and now we're starting to get a lot of adoption within the government, across the government, from federal to state to locals. >> What's the process been like, especially across those three, because I assume they're all different? You know, local, state, federal, everybody has different pain points and there's different tolerances. >> They do, they do. I mean, there's different micro-verticals within each of those statements. As an example, if you look at local governments, it could be anything from transit agencies to K-12 schools, to public works, to police, to fire. They all have all different requirements. State's the same thing, whether it's Department of Transportation or Department of Health and Human Services. And then when you get the federal side of it, then it's from the intelligence community to Department of Defense, healthcare within Defense, like the VA and DoD and Defense agencies as well. So it's a pretty wide swatch of use cases and business cases that you need to be able to sell to. >> Charles said something interesting in the keynote today. I want to ask you about it. He said, "We made a strategic decision to go to the cloud. "We didn't want to compete with Google "and Amazon and Microsoft for CloudScale. "That didn't make any sense for us." And he said, "When we were an on-prem software vendor, "we weren't managing servers for our customers." Now what struck me there is if you look back at the software company back in the day, they really didn't care about the server, right? It was just sort of infrastructure. It was kind of irrelevant to them. The cloud feels different. It seems like a more strategic relationship with Amazon. You know, we talk about Teresa Carlson and what a force she is in the government. AWS in the GovCloud has been a huge force. They had a giant lead. So have you been able to draft off that or is it just another sort of infrastructure platform? >> No, they're a major strategic partnership there with AWS and NN4. At the company level, and especially for me, with the government, they've made the right investments at the right time, I mean, and they actually have cloud environments that are very specific to different segments of the government and to different geographies. So as an example, in the federal government they have an intelligence cloud called C2S, which we work with them on. There's a very large procurement out right now for the Department of Defense called Jedi, which Amazon's going after, as well as the other larger cloud providers, so we're obviously riding that horse with AWS. And also for local governments, and they've done all of the compliancy for the government, whether it be FedRAMP, whether it be CJIS for those departments that are worried about the justice type of requirements. And as you get outside of the U.S., they're putting clouds and we're a global company as well, putting clouds in all the right places. They have a G-Cloud offering in the U.K. and as we talked about earlier when we sat down, they're opening a cloud in the Middle East right now too, in Bahrain that I think traces on oil over there as we speak. >> Right, right. The first Middle East country to claim cloud first. But it just seems like there's a strategic advantage there. And even with the other cloud suppliers. I mean, you know, Google's got its niche, big niche, you know, Microsoft, with its software state, but it seems like Amazon, they talk about that flywheel effect, brings certain technologies that, you know, when you talk to Soma, you guys have been able to take advantage of. It just feels a lot different than the old traditional server manufacturer. Oh, it's a Unix box and there's no difference between vendor A, B and C. >> Absolutely correct. And for us, we've taken advantage of the tools that Amazon has and obviously, we're doing all the compliancy on our applications and they've got whole the infrastructure piece of it, so the two work very well together. >> And that has allowed you to focus on your knitting, if you will. >> Yes. >> The things that you do best, which is a micro-verticals, suite across the application portfolio, bringing AI to the equation, automation, we heard a lot about robotic process automation, which is probably a hot topic in the government. >> Yes. I mean, Charles famously, he may have had a quote. I'm sure you heard it. It's friends don't let friends build data centers. >> Great quote. >> You know, that's not a business we're in. We're a software company. >> Right. >> So the public sector, obviously a different animal than the private sector. Very different needs, different constituents, you got tax payers, you got all that. When you bring the technology into the public sector, what does that do for it or how does that have to be, I don't know, re-conformed or adapted? And ultimately, what's the payoff, right? What's the return on that investment? >> So it was actually pretty shocking how quickly the government has adopted and moved towards the cloud. Typically, they're laggards. Everything happens in the commercial market and then government's a little bit of a late adopter, right? But we're seeing them very quickly go to the cloud and there's a lot of reasons for that. One being, you have an aging workforce. Okay, so the baby boomers are all retiring so a lot of that intellectual knowledge is going out the door. Two, is there's some economies of scale to be realized by doing that because once you're in the cloud, I mean, it's up to the vendor who's maintaining it to maintain that for you. So, you know, the people behind the scenes, they have to do it. You know, when you upgrade your software to go from one release to the other, it's automatically done for you. I mean, so there's real cost savings to be had, you know, from a care and feeding perspective there as well. Also a lot of the, on the ERP side of the things, a lot of the systems that are out in the marketplace today that governments have bought, like the Oracles or the SAPs, a lot of these systems are at end-of-life and the companies are no longer supporting them. So it's a re-implementation for them. You know, and so now they're looking, okay, if we have to re-implement and we have to look at our new options, we're going to do it in a cloud. >> So when you've been around as long as I have, Kevin, >> Right. >> you've seen the pendulum swing. You don't have to agree so vehemently. (laughing) But from mainframe to client server and so you're back to the cloud, and now with IoT, it seems like the pendulum is swinging back to a distributed environment. So help us understand where IoT fits to the cloud and even your on-prem business. >> Okay, so like I say, cloud is a pretty broad topic, okay? We have multiple applications that would run in that environment. So when I look at IoT, I think of things like our asset management platform. We have a very strong enterprise asset management platform that runs in the cloud or runs on-prem. And if you think about infrastructure as an example, which government has a lot of, okay. Think about the ability to have sensors on different pieces of equipment and being able to read that information. Think about using drone technology, okay, to be able to do physical inspections under bridges, so you're not having people having to climb around underneath there. I mean, so being able to do live feeds of data and be able to streamline the way you do business and have that automatically captured within an application. So yes, that is one area where we see it. I mean, I think you're going to see more and more of robotics and artificial intelligence and all the things come into play. I think you heard a lot about that here and it's here. I mean, they were things we saw in movies before but now the technology's here today. >> Well, the other thing we heard this morning that Charles has always talked a lot about the data. You guys always talked about your data lake. I like to think of it as a data ocean. You think about all the data out of GT Nexus and, you know, your customers that are providing data to inform. The data model starts to really expand and you guys have seemed to really take advantage of that. Talk about the data, the importance of data, the importance of securing data to the government. >> Well, think about that. I mean, there's islands of information that governments have that if they were able to consolidate that data and put some intelligence into it, be able to make business decisions versus, you know, one system sitting over here, one system sitting over here and none of them ever communicating or talking to each other. You know, the ability to, You could do from anything from, just think about crime statistics, okay? The ability to deploy resources where the crime is and then as it moves, be able to further deploy resources. You know, New York, years ago, did things like that with CompStat when they were cleaning up Times Square and so forth. But just think of that as a concept, realtime being able to manage data. >> So you've got, here at the show, we were talking about earlier, 700 and some odd clients, 725. You've got the federal forum for the first time. Why now? And what are you getting out of that or what do you hope to get out of that at the end of the week? >> So the whole executive team and our board of directors have made significant investments in this marketplace because they understand that government is a very large beast, if you will, and there's a lot of opportunity for deployment of our solutions and there's a real need to solve problems for constituents here as well. So they've made very significant investments in things for security like FedRAMP, compliancy. You know, some companies are doing it on some of their solutions. We're doing it across the board on all the products that we take to the government marketplace. So we're invested in it. You've probably heard today, Charles talked about the fact that we're going to have a federal cloud suite, which we are. So that means federal financials, okay? Actually being able to solve all the problems for the federal government and comply to all their needs and all the things that are part of mandated accounting for the federal government. They made all the right investments and human capital management would be another area. If you think about, we've got an application called Talent Science. The ability to hire the right people for the right job and retain those people. Just think about, ICE is a good example. You heard that they have to hire thousands of people to deploy on the borders, right? How do you quickly ramp and hire these right people if you don't have the right tools to do it? >> You were quoted in TIME magazine, Marc Benioff's new publication, about America's crumbling infrastructure. What role do you see technology playing generally and specifically in for software and helping with that problem? >> So we do a lot today around infrastructure. As an example, we have a very strong presence in transit agencies here in the U.S. New York City runs us, amounts to about a trillion dollars worth of assets there. So anything moving in, out or around the city, so subways, buses, trains, tunnels, bridges, Metro-North, Long Island Rail Road. L.A. runs us, San Francisco runs us, Chicago runs us, Dallas runs us and many others. So we're managing all of that infrastructure. So you hear a lot about infrastructure bills coming out of the federal government. And they're right. I mean, a lot of these tunnel, a lot of these bridges and tunnels and even roadways were built back during World War II, right? And they're aged, you know, they are starting to crumble and there's going to be a lot of money spent to do that and when it comes to rebuilding those types of things, there's a lot of assets that are going to need to be managed, you know, to do that. So we think there's a real opportunity for software such as what we bring to the marketplace to help with that process. >> How about talent retention? I mean, obviously, as administrations come and go, you know, people move, but there's been a lot of brain drain. I mean, take the Patent Office, people in commercial industry stealing some of the best and brightest out of government. Can software play a role in helping better retain, train, you know, evolve growth paths and careers? >> Yes. I guess, in a couple different ways. I mean, number one, I think the applications of today versus the applications of yesterday have changed so much. I mean, you look at, you know, the applications you have on your mobile phone. The ability to have that look and feel, I mean, our kids today are going to go into the workforce and they won't settle for anything less. They're going to want to have that look and feel. They're going to want to have those intuitive type of applications that help them do their job. And that's the kind of offering we're bringing to the marketplace. Then from just actually bringing the right people and we have an application called Talent Science, as an example, where actually there's multiple different areas of your personality that it can determine and map it back to your top performers in your company. And determine the right people for the right job where they'll fit into that environment and then they would thrive hopefully. And it should increase retention on the staff. In government, we've actually sold it to Department of Health and Human Services for hiring case workers. Okay? Or to police departments for hiring of law enforcement. So there's a real opportunity to take those types of applications and do some pretty creative things. >> What's, I hate to say, the pain side of it. But dealing with the government obviously contracts is an issue, right? And a challenge sometimes maybe for you. I'm curious, in a quickly evolving space such as yours, how do you help them keep up with you and their regulatory oversight and whatever mandated restrictions they have? All those things, you know, that come with government. It just doesn't square up with what you do. >> It is, it's a very, again, to your point, it's a different, it's a different industry with different requirements. And everything here is very open and above board. It's open procurements. Everything is competitively bid. There are contractual vehicles that you competitively bid for that'll allow you to be able to do business a lot easier in the future. I mean, in the feds you have things like the GSA 70 Schedule. U.K., you have something called the G-Cloud contract. A lot of states have vehicles where you can bid for it, so all states and local can buy off of those contracts without having to go to a competitive offering. So there's ways that the business can get done without having to go through a lot. >> Every hoop and every, yeah, right. >> The major pain process. But then there's also competitive RFPs, which, you know, well, they'll put a bid out, it'll be very detailed. You have to answer 3,000 requirements. And then after that you'll end up going into an orals and a demo process and, you know, nine months later, they're going to pick a winner. (laughs lightly) Then you go through, but then you have to go through a very painful contract negotiation process. >> That's the process I was talking about. (laughing) Exactly what I was talking about, right. >> Right. >> Yeah, yeah. Well, Kevin, thanks for being with us. We appreciate the time. >> It's my pleasure. >> And it sounds impressive, right, with the turnout you had, so I'm sure you're very, very pleased with the response you've had here on the show for so far. >> I am and I thank you for your time and >> You bet. >> have a good show. >> Look forward to seeing you down the road. Alright, sir, thank you. Back with more here live on theCUBE. We're at Inforum '18 and we are in Washington, D.C. >> I'm quite sure they got me pinned up back here, but I can't-- (upbeat music)

>> Live from San Francisco, it's theCUBE! Covering, Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back everyone. We're here live in San Francisco for Red Hat Summit 2018, I'm John Furrier, my co-host John Troyer. Next guest is CUBE alumni, been on so many times. I can't remember. I think you're a VIP CUBE alumni, Doug Balog, general manager, IBM Storage Client Success and IBM's partners executive leading the Red Hat relationship. Welcome back to theCUBE, great to see you. >> It's always great to be on it again. I think that's a new category you just invented, a VIP alumni, as to something. >> On theCUBE.net site we actually have badges for CUBE VIPs that says VIP. Great to see you. Again, we have a little history. Your role at IBM, you've been there for a lot of time. You've seen their history. Power's been your wheelhouse, you built that from scratch. An open community with the Power Systems at IBM, but you launched OpenPOWER, an open consortium, very much open source model. And you know that's very successful, congratulations on that. >> Thank you. >> Now your role with Red Hat, you're the lead executive. You're the guy to call with any problems, or anything, opportunities. What's going on? Give us the update. >> Yeah, so I think it was mentioned by Matt on stage today where we're actually celebrating 20 years of partnering together with Red Hat. I think a lot of folks take pause at that not realizing how far back this relationship goes. Hate to say I was there in 1998 when we struck this agreement. I think at that time a lot of folks inside IBM were scratching their heads saying, who's Red Hat, and what is Linux, and why are we doing this? At the end of the day, we have had a longstanding belief in open collaboration, drives innovation, drives value to clients. That was the fundamental reason we jumped in when it was just an operating system discussion back in the early 2000s. We brought that across at that time. Our Intel server base, then our mainframe, and then in 2013 our Power platform. We brought our software along as well back then too. Running on that operating system. Then it became a virtualization discussion and brought Rev onto the platforms, our software supported that. Now here with some exciting announcements today around the partnership around cloud with a common container strategy. Which I think for enterprise clients will help build a larger ecosystem, give clients choice of how they want to bring that value to clients. So it's been a long, deep relationship and one that I think the two companies are more aligned than not in many ways. >> And you guys are humble, I'll say. And you guys were a catalyst moment. Linux, the Linux coming together at that time became an industry standard literally overnight, because the industry rallied around it. You guys supported it with a big contribution and since then. But that was back in the day, that was when it was tier two citizen in the world. Now open source is tier one, it's powering everything you see and open source software and storage and networking, software-defined data center, now CloudScale, this is a big deal. >> It's a big deal. >> For the world. Now, the cloud story's interesting to me. So you got the Red Hat powering a lot of the enterprise. Hybrid cloud's number one thing on the agenda, multi-cloud's kind of being discussed, but that's with the end in mind. Hybrid cloud is a number one work area, which essentially cloudifying, creating cloud operations for the enterprise. How is this partnership with Red Hat impact IBM's customers and what's in it for the Red Hat customers? >> I think as, and I know you just had Arvin on here a moment ago. It was literally just about six months ago, that Arvin and I and Paul Cormier and Jim Whitehurst sat down and said, you know what, I think the next big thing for us to partner around is containers. There is so much advantage for speed of software deployment, this hybrid cloud structure you talked about and the fact that, listen, I think we're much more mature in the industry talking about cloud. There were moments a year or two ago where the answer was everything's going to the public cloud, on-prem's dead. I think it's a much more mature conversation now in terms of the role of hybrid. Which means clients are still going to have plenty of their data. Especially if they're a regulated industry. That data's going to stay on-prem, but that still doesn't mean there are parts of their infrastructure, parts of their applications that they're going to want to run on a public cloud, like the IBM cloud. So that ability to have a common container approach, a common container management structure, like IBM cloud private, with OpenShift as the partner, I think it brings tremendous freedom of choice to clients, so where they run what with a common development platform. >> It's interesting, the definition's changed, and we're always squinting through the noise, but the bottom line is if everything's cloudified if you will, using that word, on-prem and public cloud doesn't really make a difference where you locate it because it's cloud operations and Wikibon had the True Private Cloud rapport which basically stated that True Private Cloud is essentially on-premise activity, just operating in a cloud framework meaning same code bases, more operational dashboard. Especially cloud operations not traditional IT. So I think there is the distinction, so it's still on-prem. >> Still on-prem. >> But now you've got the edge of the network as well. Software Base2, so you've got IoT Edge, public cloud, hybrid, all coming together. >> You know we used to, when the world was just on-prem for the most part, we used to talk about different architectures being fit for purpose. What's the right workload to run what kind of applications. I was just up with a large financial institution in your neck of the woods on Friday and we were having this fit for purpose conversation around the cloud based on what kind of workload it is, how sensitive is the data, is it redacted of your and my names and social security numbers, right? All that stuff that's important. Where should that cloud workload run? What cloud should it run in? Or should it run on-prem or across both? So listen, a lot of what's old is always new, but of course it keeps evolving here now to this world of multi-cloud and hybrid cloud as you said. >> What's going on with customers at IBM? Tell us what's happening in your world. Obviously the industry's replatforming as the entire business. It's not just companies. It's an entire infrastructure's changing. You call it cloud infrastructure, data insfrastructure, AI, you're doing the Power stuff being successful. It's a global rearchitecture. >> That's right. >> This is not a one company. >> No. >> This is a complete standard. >> Everybody's transforming and I don't think there's ever an end to transformation. I think transformation is a train ride you decide to get on and you better get on, and you're going to stay on it once you get on. There's milestones along the way that demonstrate progress. But there's no resting anymore in terms of being comfortable in today's world. So transformation is going on forever. In the systems business we're constantly transforming. We brought out a new mainframe last year, we call it the z14. And now recently kind of a sum of our little skinny Zs, the ZR1s. Which are really designed for the modern data center because they fit in a standard, an industry standard rack. So we're bringing that robust security to not only our traditional Z clients, but to brand new Z clients, running Linux by the way. >> Arvin nailed it in his description and then I think this is true. You've got TCP/IP, HTTP, these are seminal moments and now you've got this glue layer with containers and say Kubernetes. This is going to change how software's being built and software being run, and how businesses will be running. So that's an industry wide dynamic shift over. At the infrastructure level. Instrumentation, and all the software behind it. Okay, that's happening. We're agreeing with that and totally agree with that. Now the impact to the customer. What do they have to do? Because they have to now adapt to this new world. Which means they got to put the legacy in. Plugging into the legacy they have to have microservices. So what does that software-defined infrastructure look like for the customer? You've seen the systems side through storage. What does software-defined mean in this new architecture? >> It certainly, part of the objective of ICP, IBM Cloud Private, was to create that on-prem cloud experience. Because again, so many clients were looking for not just having their traditional IT, which they're going to continue to have, but continue to modernize. But also move to a new environment that was much more self-service, all the things and the benefits of the public cloud, but still being careful around their data in many ways, and their core applications. So they're transforming and modernizing from legacy IT to on-prem IT, and then branching out with the fit for purpose discussion to the multi-cloud, to the hybrid cloud world. >> I love that that in the fit for purpose you can it that in so many parts of the stack. We, I think open source, one of its characteristics is it develops in public. And 20 years ago the question was, not is it fit for purpose, but when is Linux going to be ready? When's it going to be ready? Is it going to be ready? I think that answer is pretty clear now, and I think the same thing has been going through with containers and with Kubernetes. On theCUBE you're tracking Kubernetes, the growth of Kubernetes. Is this a real moment where IBM says, okay now, Kubernetes and OpenShift is now ready for the enterprise? >> Absolutely. Absolutely. If I think about kind of big moments in IT that provide a ubiquitous access to developers, you had, we talked about Linux as an operating environment, once all the platforms, the different architectures ran Linux, the ability for application portability while still bringing out the value of the platform, became very much true. Java, from an application programming model was another one. If you wrote in Java, you had the ability then to move that Java workload around without recompilation in many cases, to different architectures getting the value out of where you chose. Containers are the next one. So now we're containerizing workload. And again you have sort of freedom of choice of where you run it. And if you run it in this cloud or that cloud. Or this system or that system. You get different values out of it. >> And we're not just containerizing microservices. Now we're talking about containerizing WebSphere. >> WebSphere and databases and message queuing, and kind of that robust runtime that somebody in the audience joked, gosh I haven't seen those queues in a long time. Not that they haven't been there, they've always been there. But again, this is back to how do you take what you have from a legacy IT and modernize it for this cloud era? Much more than cloud washing. This is really transforming the IT. >> It preserves the adjustment. The bottom line, if I'm a CIO or I'm an executive looking at this market, I say okay, I've got a purchase decision I've made in the past, and I have a stall base of stuff and my choice used to be I've got to replace that, hire new people, move everything over, to now your approach is a little bit different. Great, just containerize it. And then when you're ready, you deal with it on its lifecycle. So you don't really have, so it's an ROI thing and it's also preservation of preexisting conditions. >> Now the other big, of course, client transformation going on is there's not a single client on the planet who's not trying to figure out artificial intelligence and what it means to their business to bring more insights around their clients into their workflows. So that's why in addition to Watson and all the work we do around Watson, of course in our cloud, we've gone down to the system level with our Power platform and really optimized Power9 with flash storage attached to it as the best combination of a platform for this AI era. In fact, I was sharing just before we went live here, is actually a big announce day for our systems business too. We're announcing new models of our AI platform, what we call the AC922 now with six GPUs with our partnership with NVIDIA. We've got new Linux systems, kind of the fall on with Power9, that I started back, they're much better by the way, that I started back in 2013. So here we are at the Linux Summit, we've got a common cloud partnership being announced at the same time we're announcing all the way down to the metal, systems and chips that are optimized to run the Linux and open source platforms. >> The thing that I like about those environments, the level of granularity is getting down to the point where you can have your applications or down to the level, to a service level, and manage it on that based on PowerAI would be a great example of what people can tap into. >> It actually it connects it all together, right? I mean PowerAI, which again, new content there. We've just announced PowerAI on Power9 and on Red Hat for the first time. Back to new news here at the Summit. It'll be containerized later this year. So now you've got PowerAI in a container on IBM Cloud Private, running on OpenShift optimized for Power9. Starts to make your brain hurt a little bit. But that's closer to the level of the thoughtfulness of our strategy and how all the pieces work together from the software and the applications down to the systems and the chip. >> You guys do a good job keeping in the open, too. I really like how that went with Power, certainly great stuff. PowerAI for the folks watching, check it out it's from IBM. Interesting product. I think it's got a lot of capability. Your perspective as an industry participant. You've seen many waves. What's this wave like in your opinion? There's so much going on with this new infrastructure. How do you talk about it when someone says hey Doug, what's going on? All this stuff. You've got blockchain over here. You've got this going on over there. >> I think that, at least from a systems perspective, the way think about it, myself and my peers think about it is, we've gone through so many generations where it was more manufacturing process driven innovation. How do you pack more on a chip? How do you pack more on a chip? How do you pack more on a chip? And it was kind of all about that. We're now in an era where homogeneity is no longer going to cut it. You're going to really need a number of GPUs, a number of processors, different kind of architectures, to fit the kind of workload that's coming so fast at us these days. You really don't have time to step back and say, let me replumb my old data center with that next one chip. It's going to be a diversity of infrastructure. >> Its hard to provision. You need it available immediately. >> So this wave we're in really is about bringing that diversity, that heterogeneity back into the data center, and bringing that value though, back in a simplified deployment way, 'cause heterogeneity means complexity in some ways. And that's where the layering of software packages like PowerAI, like software-defined storage, like ICP and OpenShift with our partnership with Red Hat kind of help bring that diversity and bring it back to a common level of application development. That's kind of the end goal. Common application development, the platform brings out the value. The app doesn't have to worry about it, but you've got that diversity of choice underneath. >> Great, Doug, great stuff. Great to have you on theCUBE. Just to end the segment, briefly summarize for people watching, what's this relationship with Red Hat all about? Obviously you have history, but what's the value? Talk about it right now. What's the impact to the customer watching? The relationship that's announced today with the private cloud initiative with Red Hat. >> I think if we summarize the relationship without getting into the technology, it really is about bringing innovation to enterprise clients. At the end of the day that's what Red Hat's focused on, that's what we're focused on, and that's what we're focused on together. They have great minds in the industry, we have great minds in the industry. The power of those minds coming together to create some of the innovation that we just talked about here in this segment, I mean it's mind blowing for what it means to enterprise clients to help them propel themselves forward and transform. That's what it means. >> These are the kind of partnerships we're going to see now that people are rallying behind Kubernetes and containers and this new software-defined infrastructure that's going on. We expect more of it. Right? We'll see more? >> Absolutely, software-defined is the name of the game these days. Not that there isn't value in the systems by the way. It's got to run someplace. >> They're under the hood. >> They're under the hood. >> Programmable. >> And they're differentiated for sure. >> Yeah infrastructure as code, you still need servers to run this stuff on. >> It does matter. It does matter a lot. >> Doug, great to see you. >> Good to see you as always, John. John, good to see you. >> Absolutely. >> theCUBE bringing all the action here, here in San Francisco. Live coverage, I'm John Furrier, John Troyer, day one, we'll be right back with more after this short break. (electronic music)