>>From around the globe. It's the cube with coverage of coop con and cloud native con North America, 2020 virtual brought to you by red hat, the cloud native computing foundation and ecosystem partners. >>Hey, welcome back, everybody Jeffrey here with the cube coming to you from our Palo Alto studios today with our ongoing coverage of coupon cloud native con North America, 2020. It's not really North America, it's virtual like everything else, but you know that the European show earlier in the summer, and this is the, this is the late fall show. So we're excited to welcome in our very next two guests. Uh, first joining us from Madrid. Spain is Miguel Perez, Kaleena. He is a principal product manager from red hat, Miguel. Great to see you. >>Good to see you happy to be in the cube. >>Yes. Great. Well welcome. And joining us from North Carolina is rich Sharples. He is a senior director, product management of red hat. Rich. Great to see you. >>Yeah, likewise, thanks for inviting me again. >>So we're talking about Java today and before we kind of jump into it, you know, in preparing for this rich, I saw an interview that you did, I think earlier about halfway through the year, uh, celebrating the 25th anniversary of Java and talking about the 25th anniversary Java. And before we kind of get into the future, I think it's worthwhile to take a look back at, you know, kind of where Java came from and how it's lasted for 25 years of such an important enterprise, you know, kind of application framework, because we always hear jokes about people looking for COBOL programmers or, you know, all these old language programmers, because they have some old system that's that needs a little assist. What's special about Java. Why are we 25 years into it? And you guys are still excited about Java yesterday, today and in the future. >>Yeah. And I should add that, um, in terms of languages, uh, twenty-five is actually still pretty young. Java's, uh, kind of middle aged, I guess. Um, you know, things like CC plus bus rrr you're 45, 50 years old Python, I think is about the same as Java in terms of years. So, you know, the languages do tend to move at a, um, at a, they do tend to stick around, uh, uh, a bit, well what's made Java really, really important for enterprises building business critical applications is it started off with a very large ecosystem of big vendors supporting it. Um, it was open in a sense from the very start and it's remained open as in open source and an open community as well. So that's really, really helped, um, you know, keep the language innovating and moving along and attracting new developers. And, um, it's, it's still a fairly modern language in terms of some of the new features it's advancing with the industry taking on new kinds of workloads and new kinds of per program paradigms as well. So, you know, it's, it's evolved very well and has a huge base out somewhere between 11 and 13 million developers still use it as a primary development language in professional settings. Yeah. >>What struck me about what you said though in that interview was kind of the evolution and how Java has been able to continue to adapt based on kind of what the new frameworks are. So whether it was early days in a machine, like you talked about being in a set top box, or, you know, kind of really lightweight kind of almost IOT applications then to be calming, you know, this really a great application to deliver enterprise applications via a web browser and that, you know, and it continues to morph and change and adapt over time. I thought that was pretty interesting given the vast change in the way applications are delivered today versus what they were 25 years ago. >>Yeah, absolutely. It's, you know, the very early days were around embedded devices, uh, intelligent toasters and, you know, whatever. Um, and, and then where it really, really took off was, but the building supporting big backend systems, big transactional workloads, whether you're a bank or an airline you're running both the scale, but also running really, really complex transactional systems that were business critical. And that's that's for the last, you know, 15 years has been, um, where it's, it's really shown building backend, um, systems. Now, as we kind of move forward, you know, the idea of, uh, um, like server side, uh, server side application versus a front end is kind of changed. You know, now we're talking microservices, we're talking about running in containers. So really the focus of where we run Java and the kinds of applications we're building with Java as this has radically changed. And as such the language has to change as well, which is, you know, one, I'm pretty excited to talk about caucus today. >>So let's, let's jump into it and talk about corcus cause the other big trend, you know, along with, with, with obviously, uh, uh, browsers being great enterprise applications, delivery vehicles is this thing called containers, right? And, and specifically more recently Kubernetes is the one that's grabbing all the attention and grabbing all the, all the momentum. Um, so I wonder Miguel, if you could talk about, you know, kind of as, as the popularity of containerized applications and containerized to everything right, containerized storage, or you even talked about containerizing networking, troll, how that's impacted, uh, what you guys are doing and the impact of Java, uh, and making it work with kind of a containerized Kubernetes world. >>Well, what we found is that the paradigm of development has teeth. So we have this top up, uh, uh, paradigm that the people are following to be able to do the best with containers, to the best with Kubernetes on the, this has worked quite fine in Greenfield on for, for many cases has been a way to develop applications faster, to be able to obtain variably salts. And the thing is that for many, uh, users, for many companies that we work with, uh, they also want to bring some of their stuff that the applications that are currently are running into this world. And, uh, I mean, we, we walk especially a lot in helping these customers be able to adopt those obligations, but we try to do it, uh, as we say, the N pixie dust, you know, we really dig into the code, we'll review the code with modernize. The application will help their customer with that application. We provide the tools are open for anyone to be able to review it and to be able to take it. So we are moving away from Greenfield into brownfield and not a way we are evolving together to say we more precise, you know, all these Greenfield applications keep coming, but also the current applications want to be more organized. >>Right. Right. So it's pretty interesting. Cause that's always the big conversation. There's, it's, it's all fine. And good if you're just building something new, uh, to use the latest tools. But as you mentioned, there's a whole lot of conversation about application modernization and this is really an opportunity to apply some of these techniques to do that. So quirky. So I wonder if you just give, let's just jump into it. What is it at the highest level? Uh, what's it all about? What should people know? >>Yeah. So, so Corker says I'm reading an attempt by red hat to ensure Java is a first-class citizen in containerized environments, but building reactive applications, uh, cloud native applications, uh, functions, Java is an incredible piece of engineering. It does some incredible things. It sudden can self optimize. As it's running in line code, it can do some really amazing things the longer it runs, but in a containerized environment, you're likely not going to be running huge amounts of code. You'd likely be running microservices and your, your services are likely to have a kind of limited life cycle as we you're able to deploy more frequently or in a function environment where, you know, you've been bought once and then you're done, um, you know, during all those long, um, kind of, um, those optimizations over time, don't really, um, make a lot of sense. So what we can do is remove a lot of the, um, the weights of Java, a lot of the complexity of Java, and we can optimize for an environment where your code is maybe just running for a few microseconds as in the case of the function or something running in native, cause you scale up and scale down. >>So we move a lot of the op side. We move a lot of the, um, the, the efforts within the application, uh, to compile time, we pre compile all of your, of your config and initialization, so that doesn't have to happen in your, um, your, your, your runtime or your production environment. Um, and then we can optimize the code week. We can, we can remove that code. We can remove, you know, whole, uh, trees and class libraries and really slimmed down the memory footprint and radically, um, slim, the Maddie memory footprint, um, increase the startup time as well. So, you know, you have less downtime in your applications. Um, and we've recently done a S a study with ADC that shows some pretty stunning results compared to, you know, some existing frameworks. And, you know, we get, um, you know, sort of like, you know, overall cost savings of, you know, 60, 64%. >>Um, we can get eight times better density. You're running more in a, in a, in a cluster and, um, you know, reduction in memory up to 90% as well. So it's, these are significant changes now. That's all good, you know, saving, saving 60, 60% on your operational costs is significant. But what we find is that most organizations, they come for the performance and the optimizations, but what actually stay for is the speed of development. So I think, I think caucus real silver bullets is, um, the developer productivity, you know, for organizations, the cost of development is still one of the major costs. I mean, the operational costs, the hosting costs a significant, but development costs, time to market will always be top of mind for organizations that are trying to move faster than the competition. And I think that's really where, um, um, caucus special and coupled in, uh, in, uh, OpenShift or Coobernetti's environment really, really does shine. Yeah, >>It's pretty interesting. So people can go to corcus.io and see a lot of the statistics that you just referenced in terms of memory usage and speed and, and whole bunch of stuff. But what struck me when I went to the site was that was this big, uh, uh, two words that jumped out developer joy. And it's funny that you talked on that just now about really, um, the benefits that come to the developer directly to make them happier. I mean, really calling out their joy. So they're more productive and ultimately that's what you said. That's where the great value is in terms of speed of deployment, happy developers, and productive developers. You know, Miguel, you get your, you get down into the weeds of this stuff. Again, the presentations on your LinkedIn, everyone needs to go look and you talk a lot about at migration and you lot talk a lot about app modernization. So without going through all 120 some odd slides that I think you have, which is good, phenomenal information, what are some of the top things that people need to think about and consider both for app modernization as well as at migration? >>Um, that's, that's, that's an interesting question. Uh, the thing is that, um, the tolling is important on the current code is, and the thing is that normally when, when we started migration project, we tried to find architects in the applications to be able to find patterns. You know, you find parents is much easier because, uh, once you solve one part on the same part on can be solved in a very similar way. So this is one of the parts of that. We focus a lot, but before getting to that point, it's very important how you stop, you know, so the assessment phase is, is very important to be able to review well, what is the status of the applications, the context of the applications. And with that, I mean, things like, for example, the requirements that they have, there's the maintenance that they take in their resiliency and so on. >>So you have to prepare very well, the project by starting with a good assessment, you have to check which applications makes more, make more sense to start with and see which, how to group them together by similarities. And then you can start with the project that saying, okay, let's go for these set of applications that make more sense that are more likely to be containerized because of the way we are developing them because of the dependencies that they have because of the resiliency that is already embedded into them and so on. So that, that the methodology is important. And we normally, for example, when we, when we help partners do a application migration, one of the things that we stress is that this is the methodology that we follow and in the website for my vision, totally for application, you can find also, um, methodology, uh, part that, uh, could help, uh, people understand, okay, these, these are the stages that we normally follow to be successful with migrating applications. >>Yeah. Let go. You don't, we're not friends. We don't hang out a lot, but if we did, you would know I never ever recommend PowerPoint for anything. So, so the fact that I'm calling out your PowerPoint actually means something. Cause I think it's the worst application ever built, but you got some tremendous, tremendous information in there and people do need to go in and look, and again, it's all from your LinkedIn work, but I wanted to shift gears a little bit, right? We're at CubeCon cloud native con. Um, obviously it's virtual is 2020. That's the way the world today. But I just curious to get your guys' take on, on what does this, uh, event mean for you obviously really active, open source community, you know, red hat has a long open-source history. Um, what does CubeCon cloud native con mean for you guys? What do you hope to get out of it? What should people hope to, uh, to learn from red hat? >>Yeah, we, um, yeah, we're, we're buying your DNA. We're very, very collaborative. Uh, we, we love to learn from our customers, users of the technologies, um, in the communities that we support. Um, speaking as a, you know, we're both product guys, there's nothing better than getting with, um, people that actually use the products, um, in anger, in real life, whether they're products are upstream technologies, learning, learning, what they're doing, understanding where, um, some of the gaps are there's. Um, yeah, we just couldn't do our jobs without engaging with developers, users in these kind of conferences. Yeah. A lot of the, um, love interest we've seen with coworkers is, is in the community, you know, um, like I'd been part of many, many successful open source projects, um, um, over red hat. And it's great when your customers, you know, like, uh, Vodafone, Greece or Carrefour in Spain are openly publicly talking about how good your technology is, what they're using it for. And that's really good. So it's just nothing, there's no alternative that, you know, whether it be virtual virtually or physically sitting down with, uh, with users of your technology, >>How about you, Miguel? What are you hoping to get out of, uh, out of the show this year? >>Um, we are working a lot with, on Kubernetes in red hat, on, uh, as part of the community, of course. And, um, I mean, there are so many new stuff that is coming around, Kubernetes that, uh, it's mostly about it, about all the capabilities that were arming, especially for example, several lists, you know, several lessons, there is an important topic with crackers, because for example, as you make the application stopped so much faster and react so much faster, you could have known of them running and just waiting for an event to happen, which saves a lot of resources and makes us super efficient. So this is one of the topics, for example, that we wanted to cover in this edition, you know, how we are implementing serverless with Kubernetes and OpenShift and many other things like pipelines. Like, I don't know, we just had quite a visit in the, uh, uh, video, uh, life of what is coming up. I see for the six. And I recommend people to take a look at it, to get everything that's new because there's a lot. Yeah, >>Yeah. You guys are technical people. You've been doing this for a long time. Why is Kubernetes so special? W Y Y you know, there's been containers in the past, right. And we've seen other kind of branded open source projects that got a lot of momentum, but Kubernetes just seems to be blowing everybody out of the out of its path. Why, what should people know about Kubernetes that aren't necessarily developers? >>Yeah, there's really nothing interesting about a single container or a single microservice, right? That's not, that's not the kind of environment that, um, real organizations live in. They live in organizations where they're going to have hundreds of services, um, who just containers and you need a technology to orchestrate and manage that in that complex environment. And Kubernete's has just quickly become the, the district per standard. Um, yeah, folks are red hat jumped on my very, very early, um, I mean, one of the advantages around her have is where we're embedded with developers and open source communities. We often have a pretty good, it gives us a pretty good crystal ball. So we're often quick to jump on the emerging technologies that are coming out of open source. And that's exactly what happened with Cubanetis. It was clear. It was, um, you're going to be sophisticated for our, you know, most, um, most sophisticated customers running at scale. Um, but, but also, you know, great for development environments as well. So it really a good fit for, uh, where we were headed and, you know, just very, very quickly became the fact that standard. And you, you just gotta go with the de facto standard. Right, right. >>Right. Well, the another thing that you mentioned rich in that other interview that I was watching is it came up the conversation in terms of managing open source projects. And at some point, you know, they kind of start, and then, you know, I think this one, if I go to corcus and look at the bottom of the page sponsored by red hat, but you talked about, you know, at some point, do you move it over to a foundation, um, you know, and kind of what are the things that kind of drive that process, that decision, um, and, you know, I would imagine that part of it has to do with popularity and scale, is that something, you know, potentially down the road, how do you think that you said you've been in lots of open source projects, when does it move from, you know, kind of single point of origin to more of a foundational support? >>Yeah. I mean, in fact the foundation's owner was necessary. Um, you know, when you have a, yeah. If you, if you have a, an open, very open project with, um, um, clear, clear rules for collaboration and kind of the encouragement or others to collaborate and be able to, you know, um, move the project and, you know, the foundation as low as necessarily what we've seen, I've been part of the no GS world where, you know, the, the community reached Belden to keep no GS moving forward. Um, we had to go from a, what we call a benevolent dictator for life, somebody who's well-intentioned, but, um, yeah, we're on stone, the technology, so a foundation, which is much more inclusive and, um, you know, greater collaboration and you can move even quicker. So, you know, um, I think what's required is, is open governance for open source projects and where that doesn't happen. You know, maybe a foundation is, is the right way forward. Right, right now with, with caucus, um, you know, the, the non red hat developers seem pretty happy with the way they can get, uh, get engaged and contribute. Um, but if we get to a point where the community is demanding a foundation and we'll absolutely consider it, that's the best project we'll do. >>So, so we're, we're coming to the end of our time. I want to give you each the last word, really with two questions, one again, you know, just kind of a summary of, of, uh, of CubeCon cloud, native con, you know, what should people be looking for, uh, find you, and, and, and I don't know if you guys are sponsoring any sessions, I'm sure there's a lot of great content. If you want to highlight one or two things. And then most importantly, as we turn the calendars, we come to the end of 2020, uh, thankfully, um, as you look ahead to 2021, you know, what are some of your priorities, uh, as, as we get ready to turn the turn, the calendar, and Miguel let's start with you. >>So, um, I mean, we have been working very hard this year on the migration, took it for applications to help her every user that is using Java to bring the two containers. You know, whether it is data IE or these crackers, but we're putting like a lot of effort in crackers. And now we are bringing in new rules. And, uh, by the, by December, we expect to have the new version of the migration looking for applications that is going to include the, all the bulls to help developers bring their, their code to the Java code, to, to carcass. And, uh, on this, this is the main goal for us right now. We are moving forward to the next year to include more, more capabilities in that project. Everything's up on site. You can go to the conveyor, uh, project and ticket on, uh, on the up capabilities for the assessment phase. So whenever any partner, any, any of our consultants are working on, on migration or anyone that would like to go and try it themselves on adopted, would like to do these migrations to the cloud native world, uh, will feel comfortable with, with this tool. So that is our main goal in, in my, in my team. >>All right. And how about you rich? >>Yeah, I think we're going to see this, um, um, kind of syllabus solidification kind of web of, um, microservices. Um, you know, if you like hate that, I'm sorry, but I'm just going to next generation microservice. There's going to be, as Miguel mentioned, is gonna be based around, um, uh, native, um, advancing, um, serverless functions. I think that's really the, the, the ideal architecture, the building March services, um, on, on Coobernetti's and caucus plays really, really well there. Um, I think there's, there's a, there's a kind of backlog of projects, um, within organizations that, um, you know, hopefully next year, everything really does start to crank up. And I think, um, yeah, I think a lot of the migration that Miguel has talked about is going to be, is going to rise in terms of importance. So app modernization, taking those existing applications, maybe taking aspects of those and, you know, doing some kind of decomposition in some microservices using caucus and a native, I think we'll see a lot of that. So I think we'll see a real drive around both the kind of Greenfield, um, applications, uh, you know, this next generation of microservices, as well as pulling those existing applications forward into these new environments, don't give an answers. So it's going to be excellent. >>Awesome. Well, thank you both for taking a few minutes with us and sharing the story of corcus, uh, and have a great show. Great to see you and a really good the conversation. All right. He's Miguel, he's rich. I'm Jeff. You're watching the cubes ongoing coverage of CubeCon cloud native con 2020 North America. Virtual. Thanks for watching. We'll see you next time.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners Welcome back to the Cube. Virtual coverage of KUB Con Cloud native 2020. It's virtual this year. We're not face to face. Were normally in person where we have great interviews. Everyone's kind of jamming in the hallways, having a good time talking tech, identifying the new projects and knew where So we're not. There were remote. I'm John for your host. We've got two great gas, both Cuba alumni's Chris. And is it chief technology officer of the C and C F Chris, Welcome back. Great to see you. Thanks for coming on. Appreciate it. >>Awesome. Glad to be here. >>And, of course, another Cube alumni who is in studio. But we haven't had him at a Show Jr store meant executive director of the Fin Ops Foundation. And that's the purpose of this session. A interesting data point we're going to dig into how cloud has been enabling Mawr communities, more networks of practitioners who are still working together, and it's also a success point Chris on the C N C F vision, which has been playing out beautifully. So we're looking forward to digging. Jr. Thanks for coming on. Great to see you. >>Yeah, great to be here. Thanks, John. >>So, first of all, I want to get the facts out there. I think this is really important story that people should pay attention to the Finn Ops Foundation. That J. R. That you're running is really an interesting success point because it's it's not the c n c f. Okay. It's a practitioner that builds on cloud. Your experience in community you had is doing specific things that they're I won't say narrow but specific toe a certain fintech things. But it's really about the success of Cloud. Can you explain and and layout for take a minute to explain What is the fin Ops foundation and has it relate to see NCF? >>Yeah, definitely. So you know, if you think about this, the shift that we've had to companies deploying primarily in cloud, whether it be containers a ciencia focuses on or traditional infrastructure. The thing that typically people focus on right is the technology and innovation and speed to market in all those areas. But invariably companies hit this. We'd like to call the spend panic moment where they realize they're They're initially spending much more than they expected. But more importantly, they don't really have the processes in place or the people or the tools to do things like fully, you know, understand where their costs are going to look at how to optimize those to operate that in their organizations. And so the foundation pinups foundation eyes really focused on, uh, the people in practitioners who are in organizations doing cloud financial management, which is, you know, being those who drive this accountability of this variable spin model that's existed. So we were partnering very closely with, uh, see NCF. And we're now actually part of the Linux Foundation as of a few months ago, Uh, and you know, just to kind of put into context how that you kind of Iraq together, whereas, you know, CNC s very focused on open source coordinative projects, you know, For example, Spotify just launched their backstage cloud called Management Tool into CFCF Spotify folks, in our end, are working on the best practices around the cloud financial management that standards to go along with that. So we're there to help, you know, define this sort of cultural transformation, which is a shift to now. Engineers happen to think about costs as they never did before. On finance, people happen to partner with technology teams at the speed of cloud, and, you know executives happen to make trade off decisions and really change the way that they operate the business. With this variable page ago, engineers have all the access to spend the money in Cloud Model. >>Hey, blank check for engineers who doesn't like that rain that in its like shift left for security. And now you've got to deal with the financial Finn ops. It's really important. It's super point, Chris. In all seriousness. Putting kidding aside, this is exactly the kind of thing you see with open sores. You're seeing things like shift left, where you wanna have security baked in. You know what Jr is done in a fabulous job with his community now part of Linux Foundation scaling up, there's important things to nail down that is specific to that domain that are related to cloud. What's your thoughts on this? Because you're seeing it play out. >>Yeah, no, I mean, you know, I talked to a lot of our end user members and companies that have been adopting Cloud Native and I have lots of friends that run, you know, cloud infrastructure at companies. And Justus Jr said, You know, eventually there's been a lot of success and cognitive and want to start using a lot of things. Your bills are a little bit more higher than you expect. You actually have trouble figuring out, you know, kind of who's using what because, you know, let's be honest. A lot of the clouds have built amazing services. But let's say the financial management and cost management accounting tools charge back is not really built in well. And so I kind of noticed this this issue where it's like, great everyone's using all these services. Everything is great, But costs are a little bit confusing, hard to manage and, you know, you know, scientifically, you know, I ran into, you know, Jr and his community out there because my community was having a need of like, you know, there's just not good tools, standards, no practices out there. And, you know, the Finau Foundation was working on these kind of great things. So we started definitely found a way to kind of work together and be under the same umbrella foundation, you know, under the under Linux Foundation. In my personal opinion, I see more and more standards and tools to be created in this space. You know, there's, you know, very few specifications or standards and trying to get cost, you know, data out of different clouds and tools out there, I predict, Ah, lot more work is going to be done. Um, in this space, whether it's done and defendants foundation itself, CNC f, I think will probably be, uh, collaboration amongst communities. Can I truly figure this out? So, uh, engineers have any easier understanding of, you know, if I spent up the service or experiment? How much is this actually going to potentially impact the cost of things and and for a while, You know, uh, engineers just don't think about this. When I was at Twitter, we spot up services all time without really care about cost on, and that's happening a lot of small companies now, which don't necessarily have as a big bucket. So I'm excited about the space. I think you're gonna see a huge amount of focus on cloud financial management drops in the near future. >>Chris, thanks for that great insight. I think you've got a great perspective. You know, in some cases, it's a fast and loose environment. Like Twitter. You mentioned you've got kind of a blank check and the rocket ships going. But, Jr, this brings up to kind of points. This kind of like the whole code side of it. The software piece where people are building code, but also this the human error. I mean, we were playing with clubs, so we have a big media cloud and Amazon and we left there. One of the buckets open on the switches and elemental. We're getting charged. Massive amounts for us cash were like, Wait a minute, not even using this thing. We used it once, and it left it open. It was like the water was flowing through the pipes and charging us. So you know, this human error is throwing the wrong switch. I mean, it was simply one configuration error, in some cases, just more about planning and thinking about prototypes. >>Yeah. I mean, so take what your experience there. Waas and multiply by 1000 development teams in a big organization who all have access to cloud. And then, you know, it's it's and this isn't really about a set of new technologies. It's about a new set of processes and a cultural change, as Chris mentioned, you know, engineers now thinking about cost and this being a whole new efficiency metric for them to manage, right? You know, finance teams now see this world where it's like tomorrow. The cost could go three x the next day they could go down. You've got, you know, things spending up by the second. So there's a whole set of cross functional, and that's the majority of the work that are members do is really around. How do we get these cross functional teams working together? How do we get you know, each team up leveled on what they need, understand with cloud? Because not only is it, you know, highly variable, but it's highly decentralized now, and we're seeing, you know, cloud hit. These sort of material spend levels where you know, the big, big cloud spenders out there spending, you know, high nine figures in some cases you know, in cloud and it's this material for their for their businesses. >>And let's just let's be honest. Here is like Clouds, for the most part, don't really have a huge incentive in offering limits and so on. It's just, you know, like, hey, the more usage that the better And hopefully getting a group of practitioners in real figures. Well, holy put pressure to build better tools and services in this area. I think actually it is happening. I think Jared could correct me if wrong. I think AWS recently announced a feature where I think it's finally like quotas, you know, enabled, you know, you have introducing quotas now for and building limits at some level, which, you know, I think it's 2020 Thank you know, >>just to push back a little bit in support of our friends, you ask Google this company, you know, for a long time doing this work, we were worried that the cloud would be like, What are you doing? Are you trying to get our trying to minimize commitments and you know the dirty secret of this type of work? And I were just talking a bunch of practitioners today is that cloud spend never really goes down. When you do this work, you actually end up spending more because you know you're more comfortable with the efficiency that you're getting, and your CEO is like, let's move more workloads over. But let's accelerate. Let's let's do Maurin Cloud goes out more data centers. And so the cloud providers air actually largely incentivized to say, Yeah, we want people to be officially don't understand this And so it's been a great collaboration with those companies. As you said, you know, aws, Google, that you're certainly really focused in this area and ship more features and more data for you. It's >>really about getting smart. I mean, you know, they no, >>you could >>do it. I mean, remember the old browser days you could switch the default search engine through 10 menus. You could certainly find the way if you really wanted to dig in and make policy a simple abstraction layer feature, which is really a no brainer thing. So I think getting smarter is the right message. I want to get into the synergy Chris, between this this trend, because I think this points to, um kind of what actually happened here if you look at it at least from my perspective and correct me if I'm wrong. But you had jr had a community of practitioners who was sharing information. Sounds like open source. They're talking and sharing, you know? Hey, don't throw that switch. Do This is the best practice. Um, that's what open communities do. But now you're getting into software. You have to embed cost management into everything, just like security I mentioned earlier. So this trend, I think if you kind of connect the dots is gonna happen in other areas on this is really the synergy. Um, I getting that right with CNC >>f eso The way I see it is, and I dream of a future where developers, as they develop software, will be able to have some insight almost immediately off how much potential, you know, cost or impact. They'll have, you know, on maybe a new service or spinning up or potentially earlier in the development cycle saying, Hey, maybe you're not doing this in a way that is efficient. Maybe you something else. Just having that feedback loop. Ah lot. You know, closer to Deb time than you know a couple weeks out. Something crazy happens all of a sudden you notice, You know, based on you know, your phase or financial folks reaching out to you saying, Hey, what's going on here? This is a little bit insane. So I think what we'll see is, as you know, practitioners and you know, Jr spinoffs, foundation community, you know, get together share practices. A lot of them, you know, just as we saw on sense. Yeah, kind of build their own tools, models, abstractions. And, you know, they're starting to share these things. And once you start sharing these things, you end up with a you know, a dozen tools. Eventually, you know, sharing, you know, knowledge sharing, code sharing, you know, specifications. Sharing happens Eventually, things kind of, you know, become de facto tools and standards. And I think we'll see that, you know, transition in the thin ops community over the next 12 to 4 months. You know, very soon in my thing. I think that's kind of where I see things going, >>Jr. This really kind of also puts a riel, you know, spotlight and illustrates the whole developer. First cliche. I mean, it's really not a cliche. It's It's happening. Developers first, when you start getting into the calculations of our oi, which is the number one C level question is Hey, what's the are aware of this problem Project or I won't say cover your ass. But I mean, if someone kind of does a project that it breaks the bank or causes a, you know, financial problem, you know, someone gets pulled out to the back would shed. So, you know, here you're you're balancing both ends of the spectrum, you know, risk management on one side, and you've got return on investment on the other. Is that coming out from the conversation where you guys just in the early stages, I could almost imagine that this is a beautiful tailwind for you? These thes trends, >>Yeah. I mean, if you think about the work that we're doing in our practice you're doing, it's not about saving money. It's about making money because you actually want empower those engineers to be the innovation engines in the organization to deliver faster to ship faster. At the same time, they now can have, you know, tangible financial roo impacts on the business. So it's a new up leveling skill for them. But then it's also, I think, to Christmas point of, you know, people seeing this stuff more quickly. You know what the model looks like when it's really great is that engineers get near real time visibility into the impact of their change is on the business, and they can start to have conversations with the business or with their finance partners about Okay, you know, if you want me to move fast, I could move fast, But it's gonna cost this if you want me to optimize the cost. I could do that or I can optimize performance. And there's actually, you know, deeper are like conversation the candidate up. >>Now I know a lot of people who watch the Cube always share with me privately and Chris, you got great vision on this. We talked many times about it. We're learning a lot, and the developers are on the front lines and, you know, a lot of them don't have MBAs and, you know they're not in the business, but they can learn quick. If you can code, you can learn business. So, you know, I want you to take a minute Jr and share some, um, educational knowledge to developers were out there who have to sit in these meetings and have to say, Hey, I got to justify this project. Buy versus build. I need to learn all that in business school when I had to see s degree and got my MBA, so I kind of blended it together. But could you share what the community is doing and saying, How does that engineer sit in the meeting and defend or justify, or you some of the best practices what's coming out of the foundation? >>Yeah, I mean, and we're looking at first what a core principles that the whole organization used to line around. And then for each persona, like engineers, what they need to know. So I mean, first and foremost, it's It's about collaboration, you know, with their partners andan starting to get to that world where you're thinking about your use of cloud from a business value driver, right? Like, what is the impact of this? The critical part of that? Those early decentralization where you know, now you've got everybody basically taking ownership for their cloud usage. So for engineers, it's yes, we get that information in front of us quickly. But now we have a new efficiency metric. And engineers don't like inefficiency, right? They want to write fishing code. They wanna have efficient outcomes. Um, at the same time, those engineers need to now, you know, have ah, we call it, call it a common lexicon. Or for Hitchhiker's Guide to the Galaxy, folks. Ah, Babel fish that needs to be developed between these teams. So a lot of the conversations with engineers right now is in the foundation is okay. What What financial terms do I need to understand? To have meaningful conversations about Op X and Capex? And what I'm going to make a commitment to a cloud provider like a committed use discount, Google or reserved instance or savings Planet AWS. You know, Is it okay for me to make that? What? How does that impact our, you know, cost of capital. And then and then once I make that, how do I ensure that I could work with those teams to get that allocated and accounted? The right area is not just for charge back purposes, but also so that my teams can see my portion of the estate, right? And they were having the flip side of that conversation with all the finance folks of like, You need to understand how the variable cloud, you know, model works. And you need to understand what these things mean and how they impact the business. And then all that's coming together. And to the point of like, how we're working with C and C f you know, into best practices White papers, you know, training Siri's etcetera, sets of KP eyes and capabilities. Onda. All these problems have been around for years, and I wouldn't say they're solved. But the knowledge is out there were pulling it together. The new level that we're trying to talk with the NCF is okay. In the old world of Cloud, you had 1 to 1 use of a resource. You're running a thing on an instance in the new world, you're running in containers and that, you know, cluster may have lots of pods and name spaces, things inside of it that may be doing lots of different workloads, and you can no longer allocate. I've got this easy to instance and this storage to this thing it's now split up and very ephemeral. And it is a whole new layer of virtualization on top of virtual ization that we didn't have to deal with before. >>And you've got multiple cloud. I'll throw that in there, just make another dimension on it. Chris, tie this together cause this is nice energy to scale up what he's built with the community now, part of the Linux Foundation. This fits nicely into your vision, you know, perfectly. >>Yeah, no, 100% like, you know, so little foundation. You know, as you're well, well aware, is just a federation of open source foundations of groups working together to share knowledge. So it definitely fits in kind of the little foundation mission of, you know, building the largest share technology investment for, you know, humankind. So definitely good there with my kind of C and C f c T o hat, you know, on is, you know, I want to make sure that you know, you know my community and and, you know, the community of cloud native has access and, you know, knowledge about modern. You know, cloud financial management practices out there. If you look at some of the new and upcoming projects in ciencia things like, you know, you know, backstage, which came out of Spotify. They're starting to add functionality that, you know, you know, originally backstage kind of started out as this, you know, everyone builds their own service catalog to go catalog, and you know who owns what and, you know and all that goodness and developers used it. And eventually what happened is they started to add cost, you know, metrics to each of these services and so on. So it surfaces things a little bit closer, you know, a depth time. So my whole goal is to, you know, take some of these great, you know, practices and potential tools that were being built by this wonderful spinoffs community and trying to bring it into the project. You know, front inside of CNC F. So having more projects either exposed, you know, useful. You know, Finn, ops related metrics or, you know, be able to, you know, uh, you know, tool themselves to quickly be able to get useful metrics that could be used by thin ox practitioners out there. That's my kind of goal. And, you know, I just love seeing two communities, uh, come together to improve, improve the state of the world. >>It's just a great vision, and it's needed so and again. It's not about saving money. Certainly does that if you play it right, but it's about growth and people. You need better instrumentation. You need better data. You've got cloud scale. Why not do something there, right? >>Absolutely. It's just maturity after the day because, you know, a lot of engineers, you know, they just love this whole like, you know, rental model just uses many Resource is they want, you know, without even thinking about just basic, you know, metrics in terms of, you know, how many idle instances do I have out there and so, like, people just don't think about that. They think about getting the work done, getting the job done. And if they anything we do to kind of make them think a little bit earlier about costs and impact efficiency, charge back, you know, I think the better the world isn't Honestly, you know, I do see this to me. It's It's almost like, you know, with my hippie hat on. It's like Stephen Green or for the more efficient we are. You know, the better the world off cloud is coming. Can you grow? But we need to be more efficient and careful about the resource is that we use in sentencing >>and certainly with the pandemic, people are virtually you wanted mental health, too. I mean, if people gonna be pulling their hair out, worrying about dollars and cents at scale, I mean, people are gonna be freaking out and you're in meetings justifying why you did things. I mean, that's a time waster, right? I mean, you know, talking about wasting time. >>I have a lot of friends who, you know, run infrastructure at companies. And there's a lot of you know, some companies have been, you know, blessed during this, you know, crazy time with usage. But there is a kind of laser focused on understanding costs and so on and you not be. Do not believe how difficult it is sometimes even just to get, you know, reporting out of these systems, especially if you're using, you know, multiple clouds and multiple services across them. It's not. It's non trivial. And, you know, Jared could speak to this, But, you know, a lot of this world runs in like terrible spreadsheets, right and in versus kind of, you know, nice automated tools with potential, a p I. So there's a lot of this stuff. It's just done sadly in spreadsheets. >>Yeah, salute the flag toe. One standard to rally around us. We see this all the time Jr and emerging inflection points. No de facto kind of things develop. Kubernetes took that track. That was great. What's your take on what he just said? I mean, this is a critical path item for people from all around. >>Yeah, and it's It's really like becoming this bigger and bigger data problem is well, because if you look at the way the clouds are building, they're building per seconds and and down to the very fine grain detail, you know, or functions and and service. And that's amazing for being able to have accountability. But also you get people with at the end of the month of 300 gigabyte billing files, with hundreds of millions of rows and columns attached. So, you know, that's where we do see you companies come together. So yeah, it is a spreadsheet problem, but you can now no longer open your bill in a spreadsheet because it's too big. Eso you know, there's the native tools are doing a lot of work, you know, as you mentioned, you know, AWS and Azure Google shipping a lot. There's there's great, you know, management platforms out there. They're doing work in this area, you know, there's there's people trying to build their own open source the things like Chris was talking about as well. But really, at the end of the day like this, this is This is not a technology. Changes is sort of a cultural shift internally, and it's It's a lot like the like, you know, move from data center to cloud or like waterfall to Dev ops. It's It's a shift in how we're managing, you know, the finances of the money in the business and bringing these groups together. So it it takes time and it takes involvement. I'm also amazed I look like the job titles of the people who are plugged into the Phenoms Foundation and they range from like principal engineers to tech procurement. Thio you know, product leaders to C. T. O. S. And these people are now coming together in the classic to get a seat at the table right toe, Have these conversations and talk about not How do we reduce, you know, cost in the old eighties world. But how do we work together to be more quickly to innovate, to take advantage of these cognitive technologies so that we could be more competitive? Especially now >>it's automation. I mean, all these things are at play. It's about software. I mean, software defined operations is clearly the trend we've been covering. You guys been riding the wave cloud Native actually is so important in all these modern APS, and it applies to almost every aspect of stacks, so makes total sense. Great vision. Um, Chris props to you for that, Jr. Congratulations on a great community, Jerry. I'll give you the final word. Put a plug in for the folks watching on the fin ops Foundation where you're at. What are you looking to do? You adding people, What's your objectives? Take a minute to give the plug? >>Yeah, definitely. We were in open source community, which means we thrive on people contributing inputs. You know, we've got now almost 3000 practitioner members, which is up from 1500 just this this summer on You know, we're looking for those who have either an interesting need to plug into are checked advisory council to help define standards as part of this event, The cognitive gone we're launching Ah, white paper on kubernetes. Uh, and how to do confidential management for it, which was a collaborative effort of a few dozen of our practitioners, as well as our vendor members from VM Ware and Google and APP Thio and a bunch of others who have come together to basically defined how to do this. Well, and, you know, we're looking for folks to plug into that, you know, because at the end of the day, this is about everybody sort of up leveling their skills and knowledge and, you know, the knowledge is out there, nobody's head, and we're focused on how toe drive. Ah, you know, a central collection of that be the central community for it. You enable the people doing this work to get better their jobs and, you know, contribute more of their companies. So I invite you to join us. You know, if your practitioner ITT's Frito, get in there and plug into all the bits and there's great slack interaction channels where people are talking about kubernetes or pinups kubernetes or I need to be asked Google or where we want to go. So I hope you consider joining in the community and join the conversation. >>Thanks for doing that, Chris. Good vision. Thanks for being part of the segment. And, as always, C N C F. This is an enablement model. You throw out the soil, but the 1000 flowers bloom. You don't know what's going to come out of it. You know, new standards, new communities, new vendors, new companies, some entrepreneur Mike jump in this thing and say, Hey, I'm gonna build a better tool. >>Love it. >>You never know. Right? So thanks so much for you guys for coming in. Thanks for the insight. Appreciate. >>Thanks so much, John. >>Thank you for having us. >>Okay. I'm John Furry, the host of the Cube covering Coop Con Cloud, Native Con 2020 with virtual This year, we wish we could be there face to face, but it's cute. Virtual. Thanks for watching

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America. 2020. Virtual Brought to You by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. Hey, welcome back, everybody. Jeffrey here with the Cube coming to you from our Palo Alto studios with our ongoing coverage of Q. Khan Cloud, Native Con 2020 North America. Of course, it's virtual like everything else is in 2020 but we're excited to be back. It's a terrific show, and we're excited our next guest. So let's introduce him. And we've got Sam Warner, the VP of offering manager and business line executive for storage for IBM. Sam. Great to see you. >>Great to be here. >>And also joining us is Brent Compton. He's a senior director of data services for Redhead. Great. See you, Brent. >>Thank you. >>So let's let's jump into it. Cloud Native. Everything's about cloud native. Everything's about containers. Everything is about kind of container ization and flexibility. But then there's this thing in the back and called storage. We actually have toe keep this stuff and record this stuff and have data protection for this stuff in business resiliency love to jump into it, so lets you know where does storage fit within a container world? And how is the growth of containers and the adoption containers really had you rethink the way that you think about storage and how clients you think about stories saying, Let's start with you >>e mean, it's a great question. And first off, I'm really excited about another cube con. Uh, we did Europe now, uh, doing North America so very excited to be, you know, seeing all the you know, all the news and all the people talking about the advancements around kubernetes. And we're very excited about it now. You asked a very good question. Important question. We're seeing an acceleration of digital transformation, and the people that are going through this digital transformation are using containers to now modernize the rest of their infrastructure. The interesting thing about it, though, is those initiatives are being driven out of the application teams. The business lines in an organization, and a lot of them don't understand that there's a lot of complexity to this storage piece here. So the storage teams I talked to are all of a sudden getting these initiatives thrown on them or a kind of halfway their strategy. And they're scratching their heads, trying to figure out now how they can support these applications with persistent storage. Because that's not where containers started. They started with micro services, and now now they're in a quandary. They have to deliver a certain S L. A to their customers, and they're trying to figure out how they do it in this new environment, which in a lot of cases, has been designed outside of their scope. So they're seeing issues with data protection. Some of the kind of core things that they've been dealing with for years are now. They're now having to solve all over again. So that's what we're working on helping them with reinventing how storage is deployed to help them deliver the same level of security, availability and everything they have in the past. Uh, in these new environments, >>right? So, yeah, e say you've been involved in this for a long time. You know, you've worked in hyper converge. You've worked in big data. You know, the evolution of big data continues to change, as ultimately we want to get people the information to make good decisions, but we've gone through a lot of integrations over the years. So how is it different? You know? Now how is it different with containers? What can we finally do you as a as an architect that we couldn't do before? >>Infrastructure is code. That's, I think, one of the fundamental differences of the storage admin of yesteryear versus storage admin of today today, Azaz Sam mentioned As people are developing and deploying applications, those applications need to dynamically provisioned the infrastructure dynamically provisioned what they need from compute dynamically provisioned what they need from storage dynamically provisioned network paths and so that that that element of infrastructure is code. A dynamically provisioned infrastructure is very different from well from yesterday, when applications or teams needed to. Well, when they needed storage, they would you know, they would file a ticket and typically wait. Now they make an a p A. Now they make an A p. I call and storage is dynamically provisioned and provided to their application. >>But what what I think hard to understand for the layman. And maybe it's just me, right? I It's very easy to understand dynamic infrastructure around, um compute right, I'm Pepsi. I'm running it out for the Super Bowl. I need I know how much people are gonna hit by hit my site and it's kind of easy to understand. Dynamic provisioning around networking again for the same example. What's less easy to understand its dynamic provisioning for storage? It's one thing to say, you know, there's a there's a pool of storage resource is that I'm going to dynamically provisioned for this particular after this particular moment. But one of the whole things about the dynamic is not only is it available when you need it, but I could make it big, and conversely, I could make it smaller go away. I get that for servers, and I kind of get that for networking, supporting an application and that example I just talked about. But we can't It doesn't go away a lot of the time for storage, right? That's important data that's maybe feeding another process. There's all kinds of rules and regulations, So when you talk about dynamic infrastructure for storage, it makes a lot of sense for grabbing some to provision for some new application. But it's >>hard to >>understand in terms of true dynamics in terms of either scaling down or scaling up or turning off when I don't particularly need that much capacity or even that application right now, how does it work within storage versus No, just servers or I'm grabbing them and then I'm putting it back in the pool. >>Let me start on this one, and then I'm gonna hand it off to Brent. Um, you know, let's not forget, by the way, that enterprises have very significant investments in infrastructure and they're able to deliver six nines of availability on their storage. And they have d are worked out in all of their security, encryption, everything. It's already in place, and they're sure that they can deliver on their SLS. So they want to start with that. You have to leverage that investment. So first of all, you have to figure out how to automate that into the environment, that existing sand, and that's where things like uh, a P I s the container storage interface CS I drivers come in. IBM provides that across your entire portfolio, allowing you to integrate your storage into a kubernetes environment into an open shipped environment so that it can be automated, but you have to go beyond that and be able to extend that environment, then into other infrastructure, for example, into a public cloud. So with the IBM flash system, family with our spectrum virtualized software were actually able to deploy that storage layer not only on Prem on our award winning a race, but we can also do it in the cloud. So we allow you to take your existing infrastructure investments and integrate that into your communities environment and using things like danceable, fully automated environment. I'll get into data protection before we're done talking. But I do want Brent to talk a bit about how container native storage comes into that next as well. On how you can start building out new environments for, uh, for your applications. >>Yeah, What the two of you are alluding to is effectively kubernetes services layer, which is not storage. It consumes storage from the infrastructure, Assam said. Just because people deploy Kubernetes cluster doesn't mean that they go out and get an entirely new infrastructure for that. If they're deploying their kubernetes cluster on premises, they have servers. If they're deploying their kubernetes cluster on AWS or an azure on G C P. They have infrastructure there. Uh, what the two of you are alluding to is that services layer, which is independent of storage that can dynamically provisioned, provide data protection services. As I mentioned, we have good stuff to talk about their relative to data protection services for kubernetes clusters. But that's it's the abstraction layer or data services layer that sits on top of storage, which is different. So the basics of storage underneath in the infrastructure, you know, remain the same, Jeff. But the how that storage is provisioned and this abstraction layer of services which sits on top of the storage storage might be IBM flash system array storage, maybe E m c sand storage, maybe a W S E B s. That's the storage infrastructure. But this abstraction layer that sits on top this data services layer is what allows for the dynamic interaction of applications with the underlying storage infrastructure. >>And then again, just for people that aren't completely tuned in, Then what's the benefit to the application developer provider distributor with that type of an infrastructure behind And what can they do that they just couldn't do before? >>Well, I mean Look, we're, uh, e I mean, we're trying to solve the same problem over and over again, right? It's always about helping application developers build applications more quickly helps them be more agile. I t is always trying to keep up with the application developer and always struggles to. In fact, that's where the emergency cloud really came from. Just trying to keep up with the developer eso by giving them that automation. It gives them the ability to provision storage in real time, of course, without having open a ticket like friends said. But really, the Holy Grail here is getting to a developed once and deploy anywhere model. That's what they're trying to get to. So having an automated storage layer allows them to do that and ensure that they have access to storage and data, no matter where their application gets it >>right, Right, that pesky little detail. When I have to develop that up, it does have to sit somewhere and and I don't think storage really has gotten enough of of the bright light, really in kind of this app centric, developer centric world, we talk all the time about having compute available and and software defined networking. But you know, having this software defined storage that lives comfortably in this container world is pretty is pretty interesting. In a great development, I want to shift gears a >>little bit. Just one thing. Go >>ahead, >>plus one to Sam's comments. There all the application developer wants, they want an A P I and they want the same a p I to provision the storage regardless of where their app is running. The rest of the details they usually don't care about. Sure. They wanted to perform what not give him an A p I and make it the same regardless of where they're running the app. >>Because not only do they want to perform, they probably just presume performance, right? I mean, that's the other thing is that the best in class quickly becomes presumed baseline in a very short short period of time. So you've got to just you just got to just deliver the goods, right? They're gonna get frustrated and not be productive. But I wanted to shift gears up a little bit and talk about some of the macro trends. Right? We're here towards the end of 2020. Obviously, Cove It had a huge impact on business and a lot of different ways. And it's really evolved from March, this light switch moment. Everybody work from home, too. Now, this kind of extended time, that's probably gonna go on for a while. I'm just curious some of the things that you've seen with your customers not so much at the beginning, because that was that was a special and short period of time. But mawr, as we've extended and and are looking to, um, probably extended this for a while, you know, What is the impact of this increased work from home increase attack surface? You know, some of these macro things that we're seeing that cove it has caused and any other kind of macro trends beyond just this container ization that you guys were seeing impacting your world. Start with you, Sam. >>You know, I don't think it's actually changed what people were going to do or the strategy. What I've seen it do is accelerate things and maybe changed the way they're getting their, uh and so they're actually a lot of enterprises were running into challenges more quickly than they thought they would. And so they're coming to us and asking us to help them. Saw them, for example, backing up their data and these container environments as you move mission critical applications that maybe we're gonna move more slowly. They're realizing that as they've moved them, they can't get the level of data protection they need. And that's why actually we just announced it at the end of October. Updates to our modern data protection portfolio. It now is containerized. It could be deployed very easily in an automated fashion, but on top of that, it integrates down into the A P. I layer down into CSE drivers and allows you to do container where snapshots of your applications so you could do operational recovery. If there's some sort of an event you can recover from that you can do D R. And you can even use it for data migration. So we're helping them accelerate. So the biggest I think requests I'm getting from our customers, and how can you help us accelerate? And how can you help us fix these problems that we went running into as we tried to accelerate our digital transformation? >>Brent, Anyone that you wanna highlight? >>Mm. Okay. Ironically, one of my team was just speaking with one of the cruise lines, um, two days ago. We all know what's happened them. So if we just use them as an example, I'm clearly our customers need to do things differently now. So plus one to Sam's statement about acceleration on I would add another word to that which is agility, you know, frankly, they're having to do things in ways they never envisioned 10 months ago. So there need to cut cycle times to deploy effectively new ways of how they transact business has resulted in accelerated poll for these types of infrastructure is code technologies. >>That's great. The one that jumped in my mind. Sam, is you were talking. We've we've had a lot of conversations. Obvious security always comes up on baking security and is is a theme. But ransomware as a specific type of security threat and the fact that these guys not only wanna lock up your data, but they want to go in and find the backup copies and and you know and really mess you up so it sounds like that's even more important to have the safe. And we're hearing, you know, all these conversations about air gaps and dynamic air gaps and, you know, can we get air gaps and some of these infrastructure set up so that we can, you know, put put those backups? Um, and recovery data sets in a safe place so that if we have a ransomware issue, getting back online is a really, really important thing, and it seems to just be increasing every day. We're seeing things, you know, if you can actually break the law sometimes if you if you pay the ransom because where these people operate, there's all kind of weird stuff that's coming out of. Ransomware is a very specific, you know, kind of type of security threat that even elevates, you know, kind of business continuity and resiliency on a whole nother level for this one particular risk factor. When if you're seeing some of that as well, >>it's a great point. In fact, it's clearly an industry that was resilient to a pandemic because we've seen it increase things. Is organized crime at this point, right? This isn't the old days of hackers, you know, playing around this is organized crime and it is accelerating. And that's one thing. I'm really glad you brought up. It's an area we've been really focused on across our whole portfolio. Of course, IBM tape offers the best most of the actual riel air gapping, physical air gapping We could take a cartridge offline. But beyond that we offer you the ability to dio you know, different types of logical air gaps, whether it's to a cloud we support. In fact, we just announced Now the spectrum protect. We have support for Google Cloud. We already supported AWS Azure IBM Cloud. So we give you the ability to do logical air gapping off to those different cloud environments. We give you the ability to use worm capability so you can put your backups in a vault that can't be changed. So we give you lots of different ways to do it. In our high end enterprise storage, we offer something called Safeguarded copy where we'll actually take data off line that could be recovered almost instantly. Something very unique to our storage that gives you, for the most mission critical applications. The fastest path recovery. One of things we've seen is some of our customers have done a great job creating a copy. But when the event actually happens, they find is gonna take too long to recover the data and they end up having to pay the ransom anyway. So you really have to think through an Indian strategy on we're able to help customers do a kind of health checks of their environment and figure out the right strategy. We have some offerings to help come in and do that for our customers. >>Shift gears a little bit, uh, were unanswerable fest earlier this year and a lot of talk about automation. Obviously, answer was part of the Red Hat family, which is part of the IBM family. But, you know, we're seeing Mawr and Mawr conversations about automation about, you know, moving the mundane and the air prone and all the things that we shouldn't be doing as people and letting people doom or high value stuff. When if you could talk a little bit about the role of automation, that the kind of development of automation and how you're seeing that, you know, impact your deployments, >>right? You want to take that one first? >>Yeah, sure. Um, s o the first is, um when you think about individual kubernetes clusters. There's a level of automation that's required there. I mean, that's the fundamental. I mean, back to the infrastructure is code that's inherently. That's automation. To effectively declare the state of what you want your application, your cluster to be, and that's the essence of kubernetes. You declare what the state is, and then you pass that declaration to kubernetes, and it makes it so. So there's the kubernetes level automation. But then there's, You know what happens for larger enterprises when you have, you know, tens or hundreds of kubernetes clusters. Eso That's an area of Jeff you mentioned answerable. Now that's an area of with, you know, the work, the red hats doing the community for multi cluster management, actually in the community and together with IBM for automating the management of multiple clusters. And last thing I'll touch on here is that's particularly important as you go to the edge. I mean, this is all well and good when you're talking about, you know, safe raised floor data center environments. But what happens when you're tens or hundreds or even thousands of kubernetes clusters are running in an oil field somewhere? Automation becomes not only nice to have, but it's fundamental to the operation. >>Yeah, but let me just add onto that real quick. You know, it's funny, because actually, in this cove it era, you're starting to see that same requirement in the data center in the core data center. In fact, I would say that because there's less bodies now in the data center, more people working remotely. The automation in need for automation is actually actually accelerating as well. So I think what you said is actually true for the core data center now as well, >>right? So I wanna give you guys the last word before before we close the segment. Um, I'm gonna start with you, Brent. Really, From a perspective of big data and you've been involved again in big data for a long time. As you look back, it kind of the data warehouse era. And then we had kind of this whole rage with the Hadoop era, and, you know, we just continue to get more and more sophisticated with big data processes and applications. But at the end of the day, still about getting the right data to the right person at the right time to do something about it. I wonder if if you can, you know, kind of reflect over that journey and where we are now in terms of this mission of getting, you know, the right data to the right person at the right time so they could make the right decision. >>I think I'll close with accessibility. Um, that Z these days, we you know, the data scientists and data engineers that we work with. The key problem that they have is is accessibility and sharing of data. I mean, this has been wonderfully manifest. In fact, we did some work with the province of Ontario. You could look that stop hashtag house my flattening eso the work with them to get a pool of data. Scientists in the community in the province of Ontario, Canada, toe work together toe understand how to track co vid cases s such so that government could make intelligent responses and policy based on based on the fax so that that need highlights the accessibility that's required from today's, you know, yesteryear. It was maybe, uh, smaller groups of individual data scientists working in silos. Now it's people across industry as manifest by that That need accessibility as well as agility. They need to be able to spin up an environment that will allow them to in this case, um, to develop and deploy inference models using shared data sets without going through years of design. So accessibility on back to the back to the the acceleration and agility that Sam talked about. So I'll close with those words >>That's great. And the consistent with the democratization of two is another word that we're here, you know, over and over again in terms of, you know, getting it out of the hands of the data scientists and getting it into the hands of the people who are making frontline business decisions every day. And Sam for you, for your clothes. I love for you Thio reflect on kind of the changing environment in terms of your requirements for the types of workloads that you now are, you know, looking to support. So it's not just taking care of the data center and relatively straightforward stuff. But you've got hybrid. You've got multi cloud, not to mention all the media, the developments in the media between tape and obviously flash, um, spinning, spinning drives. But you know, really, We've seen this huge thing with flash. But now, with cloud and the increased kind of autumn autonomy ization of of units to be able to apply big batches in small batches to particular workloads across all these different requirements. When if you could just share a little bit about how you guys are thinking about, you know, modernizing storage and moving storage forward. What are some of your what are some of your your priorities? What are you looking forward to, uh, to be able to deliver, You know, basically the stuff underneath all these other applications. I mean, applications basically is data whether you I and some in some computer on top. You guys something underneath the whole package? >>Yeah. Yeah. You know, first of all, you know, back toe what Brent was saying, Uh, data could be the most valuable asset of an enterprise. You could give an enterprising, incredible, uh, competitive advantage as an incumbent if you could take advantage of that data using modern analytics and a I. So it could be your greatest asset. And it can also be the biggest inhibitor to digital transformation. If you don't figure out how to build a new type of modern infrastructure to support access to that data and support these new deployment models of your application. So you have to think that through. And that's not just for your big data, which the big data, of course, is extremely important and growing at incredible pace. All this unstructured data, You also have to think about your mission critical applications. We see a lot of people going through their transformation and modernization of S a p with move toe s four Hana. They have to think about how that fits into a multi cloud environment. They need to think about the life cycle of their data is they go into these new modern environments. And, yes, tape is still a very vibrant part of that deployment. So what we're working on an IBM has always been a leader in software defined storage. We have an incredible portfolio of capabilities. We're working on modernizing that software to help you automate your infrastructure. And sure, you can deliver enterprise class sls. There's no nobody's going to alleviate the requirements of having, you know, near perfect availability. You don't because you're moving into a kubernetes environment. Get a break on your downtime. So we're able to give that riel enterprise class support for doing that. One of the things we just announced that the end of October was we've containerized our spectrum scale client, allowing you now toe automate the deployment of your cluster file system through communities. So you'll see more and more of that. We're offering you leading modern native protection for kubernetes will be the first to integrate with OCP and open ship container storage for data protection. And our flashes from family will continue to be on the leading edge of the curve around answerable automation and C s I integration with who are already so we'll continue to focus on that and ensure that you could take advantage of our world class storage products in your new modern environment. And, of course, giving you that portability between on from in any cloud that you choose to run in >>exciting times. No, no shortage of job security for you, gentlemen, that's for sure. All right, Well, Brent, Sam, thanks for taking a few minutes and, uh, is great to catch up. And again. Congratulations on the success. Thank you. Thank you. Thank you. Alrighty, Sammy's Brent. I'm Jeff, You're watching the cubes. Continuing coverage of Q. Khan Cloud, Native Con North America 2020. Thanks for watching. We'll see you next time.

>>from around the globe. It's the Cube with coverage of Yukon and Cloud. Native Con North America 2020 Virtual brought to you by Red Hat The Cloud Native Computing Foundation and Ecosystem >>Partners Everyone welcome back to the cubes. Coverage of Coop con Cloud, native con North America 2020. Normally the Cuba's in person. But like the EU event, this is gonna be a remote virtual event. This is the Cube virtual. We are the Cube Virtual. This is a keynote and show review with our analysts and hosts Lisa Martin, GOP Scar and myself. Guys, welcome to the program. Lisa, Great to see you. You great to see you remotely. Thanks for coming on. >>Always great to be part of the Cuban acute virtual keeping us connected. >>So Coop Con Cloud Native cons November and I remember in 2016 the first Coop Con. That's when Hillary Clinton got defeated by Trump. And now this year the election's passed this time and, uh, Biden the winner. So, you know, election more good vibes this year in the community because everyone was kind of sad last time. So if you remember the first Cube con, it was in Seattle during that time, so that was important to kinda reminisce on. That other thing I want to bring up to you guys is the somber news of the passing of Dan Con who was the executive director of C N C F. He passed a few weeks ago on his home. It was illness and great legend. So we're gonna call that out, and there are thoughts and prayers. Go with the families. Condolences to his wife and kids. So what? I'm say, Dan. Godspeed. Funny dance story, Lisa. Yo, piece that I always always pronounce his name wrong on the queue was like, John, it's con, not Cohen. Okay. All right, Dan, Good to see you. Sorry, but a great guy friend to everyone And super great human being. So rest in peace. Okay. Que con, I >>think the big thing. >>This you wanna get your thoughts, you have to start with you, C and C F. What are they up to? Obviously remote. It's been a terrible year with the pandemic and all the disruptions on DCI change your thoughts on where they are now, this year. >>So you know, it's funny, even though it's remote. Even though reaching people, it's become harder. Uh, you know, we all have to deal with this from our you know, our living room, our office at home. But still, the C in C F is doing what it's been doing for a little while now. So instead of focusing on the technology part of RT world, there are focusing on you know, the community side of it. So they're fighting for inclusivity. They're fighting for diversity, for resilience in terms off their community. And they are really working on making the open source community more accessible, both for end user companies. A swell as offer developers thio enter the space, have their contribution and, you know, make sure that everyone can reap the full benefits off these open source products. >>You know, we talked to Priyanka Sharma and Stephen Augustus, and this was a big theme. There's there's been there's been a lot of engagement online, obviously, even though they have a remote platform, some people are thrilled with it. Some aren't. No one's ever happy these days. It's on the Web. It's always difficult, but the community been activated and a lot more diversity. I covered the big story around. You know, Master slave. The terminology now is gonna go main, you know, terminology and how that's gonna be safer. Also for diversity stem women in tech, This >>has been >>a big theme. I'd love to get your thoughts on that, because I think that's been a very positive thing. Uh, Lisa, you and I have been talking about this for years on the Cube around this diversity peace. What's your thoughts as well, like to get both your reactions on where this directions going. >>Yeah. You know, I think there's a number of things that have been catalyzed this year by the challenges that we've been through and the diversity pushed into the spotlight again. The spotlight is different, and it's really causing change for good. I think it's opening people's minds and perspective, as is, I think, this entire time, you know, it's for events like Yukon and all the other events that were normally getting a lot of airline miles for John and you were not getting. We're sitting at home with our in home studios, but at the same time, the engagement is increasing in every event, I imagine that the great Q. Khan and cognitive community that Dan Cohen has built is on Lee getting bigger and stronger, even though folks are physically separated. That's been just been my observation and something I felt from everything show I've covered every interview I've done that diversity is being raised now to a visibility level that we haven't seen in terms of a catalyzing action. >>You your reaction, Thio. >>No, I completely agree. And I want to add to that where you know, just like Lisa said. You know, we used to fly to these events. We were privileged and lucky to to be there to have the opportunity. But because everything is now digital and virtual, it opens the community up to so many other people who, for whatever reason, weren't able to join in person but are able to join virtually indigenously. So I think you know, even though there's a lot of downsides Thio to this pandemic, this is one of the, you know, the small nuggets of off seeing the sea NCF community opening up to a broader audience. >>Yeah, and that's a great point. You know, we aren't getting the airline miles we're getting Certainly the zoom and the cube mileage remote Lisa, because what's interesting you're saying is is that you know, we're getting more action with him coming in, doing some or hosting yourself, um, Eliana Gesu as well, Others. But we can get people more because remember, the people aren't we're not trying, but so aren't other people that were coming the big names, but also the fresh voices, the new names, names? We don't know yet. I think that's what we're seeing with the remote interviews is that it's one click away from being on the Cube now. So cute. Virtual is 24 73 65 we're gonna continue to do that. I think this is gonna change the makeup of the engagement in the conversation because you're gonna have mawr participation that's going to be highly accelerated. But also, these new voices are gonna bring a positive change. It might upset the hierarchy a little bit in the working groups at the top you, But you know they're open. I mean, I talked with Stephen Augustus. He's totally cool with this Chris, and I check is the same way he's like, Hey, bring on more people. This is the >>This is >>the vibe of the of the Lennox foundations always been. >>It's always been that way. And, you know, going back Teoh to the early open source events in Europe that I went to you. I started doing that as a teenager 15 years ago, and the vibe, you know, hasn't necessarily changed. The makeup of the audience certainly has changed right from it, being dominated by white males. It's totally opened up. And, you know, if we see that happening with the C N C F now as well, I think that's for you know, for the better. I think, um, our community, the i t community in the open source community need that resilience. Need all of those different perspectives from all of you know, different kinds of people from different walks of life with different histories. And I think that only makes the community stronger and more viable in the long run. I >>agree it's that >>open source needs. >>Sorry, it's not thought diversity that I think we're seeing even more now again. Just my perspective is just that the light that this challenging time is shining on, exposing things that are really opportunities and it's I think it's imperative to look at it in that way. But that thought diversity just opens up so many more opportunities that folks that are maybe a little bit more tunnel visioned aren't thinking of. But for businesses, thio and people Thio thrive and move forward and learn from this we need to be able Thio, take into consideration other concepts, other perspectives as we learn and grow. >>Yeah, that's a good point. You know, It was giving a a shout out to Dan Conn. And when I heard the news, I put a clip. One of my favorite clips over the interviews was really me kind of congratulating him on the success of C and C. I think it was, like two years ago or maybe last year. I forget, Um, but I >>was a >>critic of it ever initially, and I was publicly on the record on the Cube. Lisa, you remember, uh, with Stew, who's now having a great new career? Red hat Still and I were arguing, and I was saying, Stew, I think this is gonna fail, because if c. N. C F doesn't balance the end user peace with the logos that we're coming because remember, you about four years ago. It was like a NASCAR logo. Farmers like you know, it's like, you know, everything was like sponsored by Google this and then Amazon came in. You look at the sponsor list. It was like It's the who's who and cloud and now cloud native. It was the industry the entire industry was like, stacked up against reinvent. This is before Amazon made their move. I mean, uh, as your maid, they're moving for Google. Cloud kind of got their footing. So is essentially coop con against a W s. And I said, That's gonna fail, and I had to eat my words, and I did. It was rightfully so, But the balance, the balance between end user projects and vendor was very successful. And that's still plays out today. Lisa. This is important now because you said pandemic de ecosystem still needs to thrive, but there's no face to face anymore. >>What's the >>challenge? What's the opportunity there? I wanna put you on the spot. >>Sure. No, I think I think it's both challenging and opportunistic. I tend to look at it more from an opportunistic view. I think that it forced a lot of us, Even people like myself who worked from home a lot before, when I wasn't traveling for my marketing company or the Cube. You can really have very personal interactions. The people on Zoom and I found that it's connecting people in a deeper way than you even would get in the office. That's something that I actually really appreciate, how it has been an opportunity to really kind of expand relationships or toe open new doors that wouldn't be there if we were able to be studying together physically in person. And it's obviously changing. You know, all the vendors that we work with. It's very different to engage an audience when you are on Lee on camera, and it's something that, as we know, is we work with folks who haven't done it before. That's one of the things that I think a lot of the C suite I talked to Mrs is that opportunity Thio. You know, be on a stage and and be able to show your body language and your energy with your customers and your partners and your employees. But I actually do think that there is what we're doing through Zoom and and all these virtual platforms like the Cube virtual is well, we're opening up doors for a more intimate way that I think the conversations are more authentic. You know, people are have, like, three year old Discover occurs and they're running in the room when they're screaming behind that. That's how things are today. We're learning toe work with that, but we're also seeing people in a more human >>way. Containers Mitch, mainstream and shifting, left the role of security this year. What's your >>take? So I mean, if we're talking about security and nothing else, I think we're at a point where you know, the C N C. F has become mainstream. Its most popular products have become mainstream. Um, because if we're talking about security, there's, you know, not a lot left. And I say that with, you know, a little bit of sarcasm. I don't mean to offend anyone, but if I did, uh, I do apologize, but, you know, security. Even though it is super important again, it means that we have, you know, moved on from talking about kubernetes and and container Management, or we've moved on from storage. Um, it means that the technology part of the C N. C. F. Like the hard work has been done for 80%. We're now into the 20% where we're kind of, you know, dotting the I's and and making sure that we cover all of the bases. And so one of the news sandbox sandbox projects that has been accepted, I think, today even eyes certain Manager Thio to manage certificates Uh, you know, at scale, um, in an automated fashion. And I think that's, you know, 11 prime example of how security is becoming the theme and kind of the conversation at Yukon this year where, you know, we're again seeing that maturity come into play with even with sandbox projects now being able to help customers help end users with, you know, certificates which is, you know, in in the the macro picture a very specific, a very niche thing to be able to solve with open source software. But for every company, this is one of those vital, you know, kind of boilerplate security measures so that the, um the customer and all of their infrastructure remains safe. >>I think you what You're kind of really articulate, and there is the evolution of CNC off much to John Surprises. You said you thought in the very beginning that this wasn't gonna take off. It has. Clearly, Dan Cohen's left a great legacy there. But we're seeing the evolution of that. I do know John. Wanna ask because you did a lot of the interviews here. We've been talking for, what, nine months now on the Cube Virtual about the acceleration of transformation, of every business to go from that. Okay, how do we do this work in this in this weird environment? Keep the lights on. How do we actually be successful and actually become a thriving business? As things go forward, what are some of the things that you heard from the guests regarding? Kobe has an accelerator. >>Well, I think I think a couple of things. Good. Good question. I think it ranges. Right. So the new They had some news that they're trying to announce. Obviously, new survey certifications, K a security certification, new new tech radar support, diversity stats. You know, the normal stuff they do in the event, they gotta get the word out. So that was one thing I heard, but on the overall macro trend. You know, we saw the covert impact, and no >>one's >>afraid of it there. I mean, I think, you know, part of the legacy of these tech communities is they've been online. They're they're used to being online. So it's not a new thing. So I don't think that the work environment has been that much of a disruption to the people in the in the core community. Linux Foundation, for instance, had a great shot with Chris and a sticker on this. He's the CTO. He's been the CEO, brought a senior roles. Um, in fact, they're they're creating a template around C N C f. And then they're announced The Finn Finn Ops Foundation. Uh, Jr store meant, um, is an executive director. That's part of the new foundation. It's a practitioner community. So I think, um, teasing out the conversation is you're gonna see a template model of the C N. C f. Where you're going to see how groups work together. I think what cove? It has definitely shown in some of the things that you guys were saying around how people are gonna be more engaged, more diversity, more access. I >>think you're >>gonna start to see new social constructs emerge around distinct user groups. And I think this Finn ops Foundation is a tell sign around how groups of people going to start together, whether they're cube host coming together on Cube fans and cube alumni. I mean, let me think about the alumni that have been on the Cube. Lisa, you know Tim Hopkins, Sarah Novotny. Chelsie Hightower. Um, Dan Burns, Craig MK Lucky. I mean, we've had everybody on that's now Captain of the industry. So, um, way had capital one we've had, uh, you know, lift on. I mean, it's becoming a really tight knit. Everyone knows each other, and I think now they realize that they have a lot of, uh, power to infect change. And so when you're trying to affect change, um, that's a good thing, and people are pumped about. So I think the big focus was, um, CNC have a successful again. It's there's there's a somber note around Dan cons passing, but I think he had already moved on to a new position. So he was already passed the baton to management, But he did leave a mark, but I think there's Priyanka Sharma. She's doing a great job. People are upbeat and I think the theme is kubernetes. It happened. It's went next level, then it's going next level again and I think that's kind of what people really aren't saying is kind of the public secret, which is okay, this thing's going mainstream. Now you're gonna start to see it in, in, In commercial deployments. You're gonna start to see it scale into organizations. And that's not the cool kids or the Emerging Dev ops crowd. That's I t. So you know you know it's gonna happen is like, Hey, you know, I'm a nice guy, our developer. What is this? It has toe work. Well, that's the big I think I think people weren't talking about That's the most important story. >>I think another element to that John is the cultural shift. You know, we were talking when we talk about Dev ops who was think about speed and I talked to some folks who said, You know, it's it has to be the I T. Cultures on the business cultures coming together in a meaningful way to collaborate in a very new way. Thankfully, we have the technology to enable us to collaborate. But I think that's been another underlying thing that I've heard a lot through recent times. Is that that facilitator of of cultural change, which is always hard to dio? And there's a bit of a catalyst here for organizations to not just keep the lights on. But to be successful, going forward and and and find new ways of delighting their customers, >>we'll get the final word. I just want to say my big take away to the show is and we'll go down the line. I'll start Lisa in Europe, you could go is the usage of cloud and multi cloud is here. Everyone sees that. I think there's a financial aspect going on with security. You're gonna be tied in. I think you see new sets of services coming built on the foundation of the C N C F. But cloud and multi cloud is here. Multi cloud meeting edges. Well, that is definitely on everyone's radar. That was a big theme throughout the interview, so we'll see more of that. Lisa, your takeaways. >>Yeah, I would agree with that. And I think one of the biggest things that I hear consistently is the opportunities that have been uncovered, the the collaboration becoming tighter and folks having the opportunity to engage more with events like Coop Con and C and C F. Because of this virtual shift, I think there's only ah lot of positive things that we're going to stay to come. >>Yep. Yeah, my point of view is I mean, open source is validated completely right? It's a viable model to build around software. On the one hand, on the other hand, the C and C s role in making that open source community broadly accessible and inclusive is, I think, the biggest win Thio look back at at the last year. >>Well, I'm super excited for moving on to the next event. It's been great pleasure. Lisa. You you guys are great co host Virtual Cube. Thanks for participating. And we'll see you next time. Thank you. Okay, that's the cubes. Coverage of Coop con 2020 cloud Native con Virtual This the cube Virtual. We are the cube. Virtual. Thanks for watching

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

>> Man: from around the globe, it's "theCUBE" with coverage of "Kubecon" and "CloudNativeCon Europe 2020", virtual. Brought to you by Red Hat, the cloud native computing foundation and ecosystem partners. >> Welcome back, I'm Stu Miniman, and this is "theCUBE's" coverage of KubeCon CloudNativeCon Europe 2020, the virtual edition of course, it, this ecosystem has been bustling, a lot of activity in the five years that we've been covering it with "theCUBE" we've watched very much the maturation of what's going on. Remember, in the early days, it was open source projects, companies pulling all the pieces together. Now, there's a lot more things to choose from lots of projects, not just Kubernetes, but all the other pieces, and still lots of new innovations and new startups coming into the space. So happy to welcome to the program, have two first time guests from Spectro Cloud, first of all, we have the co founder and CEO Tenry Fu, and also Tina Notle who's the Vice President of product, Tina and Tenry, thank you so much for joining us. >> Thank you for having us. >> Likewise. >> All right, so Tenry, as one of the co founders, I want to understand, you know, why Spectro Cloud? Why now, you know, many outsiders, would they have said for a while, you know, Kubernetes, it's just getting baked into all of the environment. They looked at all the platforms, whether you're talking, you know, Google and AWS or VMware, they all have their platforms, they all have their managed services offering. So help us understand, what your team does and how you differentiate from what's already existing. >> Absolutely yeah, so I actually used to work at VMware, I, and then, I saw clouds taking off right and then I left VMware, to start my first startup called CliQr Technologies, which focus on multicloud management. But at that time, really, multicloud management through a single pane of glass is obviously right, and then clicker later acquired by Cisco. So at Cisco, I kind of witness The Container and Kubernetes taking off, right? And it makes a lot of sense, right for the first time both the application workloads and infrastructure became truly portable across multiple environments, but also very interestingly at Cisco I observed there are many developer teams, right? That is adopting Kubernetes and everyone is doing a little bit different things, that because different teams, they have a different stack constructor requirements, like some for AI/ML, some, they need a different base OS, some they just don't want to have a different version, and a lot of existing solutions doesn't really provide this kind of flexibility to satisfy all the different needs, right? one size fit all, typically is a one size fit for nothing. So we asked ourselves, why can't we try to create a platform that will give people the flexibility, but not turning it into a DIY project, right, still have a full manageability, so that user don't need to worry about the upgrade, Day Two operations, governance so and so forth. >> Yeah to Tina, I know when I've looked at your product, it's discussed as layers, which my background's in networking. So I love seeing things visually and understanding the pieces as they lay out the stack. So maybe help us understand a little bit as to, you know, that the flexibility that you give and how it's not just the Paradox of Choice, just too many options out there and you know, developers left to create their own mess that they can't then support. (laughing) >> Yeah, so you know, as Tenry mentioned, offering folks flexibility without turning into a do it yourself, you know, hot mess is what we're what we're helping People do at Spectrol Cloud, the core of our solution, the core of the differentiation within our solution is around this concept of a cluster profile, and as you mentioned, cluster profile basically allows people to define in a layered fashion, what's part of their Kubernetes infrastructure stack? So at the bottom, you're talking, what's the base operating system? What's the version of Kubernetes, that's going to be part of clusters that uses profile? What's your networking and storage interface look like? And then on top of that, you have a number of optional layers. So again, you know, back to flexibility manageability, we give people options around what those other layers look like on top. They include everything from security, logging, monitoring, etc, just anything that you want to go ahead and kind of bake into a definition, a profile of what a cluster should look like in one of your deployed environments. >> All right, well, Want to make sure I understand when you talk about Kubernetes in there, can it be, you know, say VMware with Vsphere7, now has Kubernetes support. Red Hat open shift is an option, all of the cloud players have their, you know, AKS, EKS. And they're like, can I bake that Kubernetes in or are you taking a different approach? >> We're going with upstream vanilla Kubernetes today, that allows us to go ahead and provide what's newest within the ecosystem, and let people go ahead and have a really open, really open solution that's replying. >> Okay, so when I talk to, when you look out there, a lot of companies are saying how can I manage multiple clusters? So if you look at what Google, Microsoft and VMware, they're talking about, we can manage our clusters and we can also help you with those other clusters. How does that impact Tenry, your Solution, doesn't it need to be, it's just the upstream solution that I put into that cluster profile, or can I connect to, say a managed cloud solution? >> Yeah, so I think in terms the multi class management or the consistency is really the key, right. So through this class profile concept, not only it can be used as the initial template to deploy a cluster, but it can also use as a single source for choose, to drive the cluster Lifecycle Management income upgrade. So right now, as Tina mentioned, we primarily focus on upstream, so that we want to provide the maximum flexibility in terms of our end to end Kubernetes stack. But we do also have a plan, that down the road that we go into in Brownfield existing clusters. So that enterprise, existing investment to their Kubernete infrastructure can be under managed by us. >> Well there always reaches a time when the brand new technology gets called Brownfield. I think that's the first time I've heard something like, you know, EKS or the like, you know, referred to as Brownfield. Tina, you know, when I think back to my history with integrated solutions, obviously, if I have the various pieces, it should be easier for me to stay on the latest make upgrades, roll things forward or roll things back, but you know, what, give us if you could some of the, the key values of, you know, building these cluster profiles, what that enables for your customers. >> So the key around cluster profiles, we offer this policy based management, so you describe as an administrator, what it is that those clusters need to look like, right? And we've got, we adopt a declarative desired state, you know, management approach along what Kubernetes does itself, and so what you're able to get through adopting, utilize cluster profiles, is this guarantee that from deployment and then into day two as well, what you've described in this profile, winds up maintaining itself, it remains true of the clusters that have been deployed. So what it is that you require as far as the operating system, what is required as far as some configuration options, etc. So the profile itself winds up being ground source of truth and around what it is that you've got running at all these various locations, across clouds, across different clusters, etc. >> All right. Tenry, you mentioned that having things more standardized is going to help customers, absolutely, we saw that in data centers for a long time, and standardized, how do you help customers make sure that the configuration that they build are going to work, are going to be stable, if they make changes that they're not going to get things out of sync. Is there you know, interoperability matrix or some other ways that we're trying to make sure that customers, you know, stay on the rails, if you will. >> Absolutely right, So through our system, right, all the integration points, we carry the additional metadata, right to basically give the hint about compatibility, resource constraints, right, and also the upgradability, in terms of moving from one version to another. So this way, we can kind of give you some guidance, when they initially construct a class profile, what will work together nicely and then what will not, right. And then on top of that, when upgrading from one existing cluster to a new version of a class profile definition, then we can look at the environment, right to understand, right, if there's something that potentially incompatible will popping up right, so we call that pre pilot integration, check right and also post deployment, we also allow user to run additional conformance tests. So that make sure the cluster everything is actually is still acting as as it's supposed to be. >> Another way to explain that is that you know, the cluster profile concept has a lot of flexibility attached with to it, right? That's a lot of power, it can get you into trouble if you don't have the right safety nets and safety harnesses underneath you. So we have a multi layered approach to helping make sure that people are getting benefit out of that flexibility. >> Wonderful and I'm wondering did, when you've had more customers using this, is their shared information, and if there're community guidelines that help, you know, understand when it's going to be okay, hey, 1.19's out, we're looking at 1.20. You might want to do this or hey, if you're using this piece of networking, you might want to wait a little bit before you go to the next version. >> That's definitely the idea over time, folks that are engaging with us, are very interested in the fact that, because of the fact that we're SaaS management platform, SaaS space management platform today, that it offers them the opportunity to learn from their peers, if you will, right, and their peers experiences. On top of that, we also have the ability to watch just what's been going on in other deployments in the Kubernetes ecosystem and we can make sure that all that's available, as Tenry mentioned, you know, in the form of the metadata that's on top of those packs. >> All right, how about how do you price this solution? When I look out there, I talked about Kubernetes baked into all the platforms, oftentimes, it can be baked into ELA, It's part of, you know, my just general cloud spend from that platform. So how do you do the pricing and, you know, are you plugged into any of the cloud marketplaces yet? >> Yeah, so flexibility is really part of our DNA. So even for pricing, we want to provide the maximum flexibility to our customer. So unlike some traditional solution typically is priced based on number of pause, right, a year, or even number of nodes, right. So we actually price based on number of CPU cores of all workers node under management by hour. So what we call those, core hour under management, right, and then every thousand core hours at one unit, we call kilo core hours. So kind of similar to how electricity is consumed, right, so this way, based on these core hour consumption, we allow user to either pay as you go as amongst the on demand plan, or you can do an annual commitment. >> And we are in process on the marketplaces. >> Yeah. >> All right, how about, we talked about Kubernetes, I think service mesh are part of it. What in this Kube, kubecon cloud native con ecosystem, which projects are the most tied into what you're doing anything that specter cloud is particularly contributing to that you can share? >> Yeah, so our system is built on top of Kubernetes cluster API project. So we are one of the contributor to class API, we are actively adding additional functionality to enhance class API, especially by in some other VMware environment for some custom use case, such as static IP or some special placement behaviors, and also adding additional contribute on different cloud support. >> Yeah, and as far as things that we're watching, and clearly we're, we've seen a dramatic increase in the number of people on our customer front that are interested in actual deployment, of service mesh now. So that's something that you know, we're going to be more engaged in over time. And another one that we're hoping to see, check out more talks around Kubecon is AI ML, right? A lot of interest on the part of customers around AIML use cases. >> Yeah, absolutely edge and AI and ML. Definitely very hot topics to conversation this year at the, at the Europe show, expect that to continue. Tina, I'm wondering, do you have any customer examples, maybe even anonymized that could kind of just explain the key values that your customers are seeing using your solution? >> Yeah, sure, so we've got one of our earliest customers is a Canadian financial, who came to us because, they were looking to figure out how to manage consistently at scale, and they have the problem that Tenry described earlier, around, I've got different development teams, they have different needs, and you know, how do you satisfy all those guys without going crazy, right? They've got an AIML use case, that's a special snowflake they've got two separate teams in different groups that would like to be under an IT management umbrella. That's a convergence use case that they're looking at, so kind of a typical example of somebody that we think of is, you know, a really good set of people for us to be having conversations with. We've also been working with a telecom provider that it's in a similar, similar vein actually, there's an AIML, there are multiple teams of different infrastructure, and they want to be able to consistently manage it's a story that we're seeing over and over again, thankfully. >> Yeah, we also see right from I think, at individual group or team level, right. There are a lot of, kind of a product owner or data scientists that they really want to have a kind of an easy button to quickly be able to provision Kubernetes clusters that suit for their need, right. And a lot of these groups, their primary focus is really the application, right? It's not their interest to spend a lot of time and resource on Kubernete management, in terms of deploying update, or secure an operation. So through us, they can very easily spin up a Kubernetes cluster, whether it's for AIML or for developing experiment, they can very quickly do that But with the flexibility, because a lot of existing solution, they may limit the version of Kubernetes clusters, they may limit the what kind of integration they can do. >> Yeah, Tenry you, we talked a little bit earlier about, you know, potential integration down the road. I'm curious, just there's so many companies creating innovations out there, you know, say for example, one that I hear a lot of feedback on is AWS now has far gate support for their EKS offering. Is that Something down the line you should look at or do you have some guidance as to how customers should be thinking about that, and if they want that kind of functionality, how they would get that with a solution like yours? >> Yeah, actually, we really share the same vision as AWS, right. So we believe, ultimately is the infrastructure really should be transparent to application developers, right, and it should be boundary-less. So our goal is not only manage Kubernetes, across multiple environment, but eventually we will be able to link all these cluster together, to make them acting as a single infrastructure. So developers, they can still use their familiar Kubernetes interface to deploy and manage their application, but without worrying about the how infrastructure underneath is operated or managed, right. So this in a way will eventually become kind of a phallic model, but across multiple cluster and multiple clouds. >> Alright, Tina, if maybe if you could give us the final takeaway, people attending Kubecon, cloud native con, what's the one thing that if you know they have a problem, they should be coming to Spectro cloud to hear more about? >> Yeah, sure so what Spectrol cloud aims to do is help enterprises not have to trade off between flexibility and control of their infrastructure, and manageability of use that stuff's that's the main, the main thing that we would like people to remember. >> All right, well Tenry and Tina, thank you so much for sharing with our community a little bit about Specter Cloud great talking to you and look forward to hearing more in the future. >> Thanks so much. >> Thank you too. >> All right, and stay tuned more coverage from Kubecon Cloud Native Con 2020. I'm Stu MiniMan and thank you, for watching "theCUBE." (light music)

>>from around the globe. It's the queue with digital coverage of Docker Con Live 2020 brought to you by Docker and its ecosystem partners. Welcome to the Special Cube coverage of Docker Con 2020. It's a virtual digital event co produced by Docker and the Cube. Thanks for joining us. We have great segment here. Precision cancer medicine really is evolving where the personalization of the data are really going to be important to personalize those treatments based upon unique characteristics of the tumors. This is something that's been a really hot topic, talking point and focus area in the industry. And technology is here to help with two great guests who are using technology. Docker Docker containers a variety of other things to help the process go further along. And we got here spring and who's the bioinformatics research assistant and Camille took Who's a student and in turn, you guys done some compelling work. Thanks for joining this docker con virtualized. Thanks for coming on. >>Thanks for having me. >>So first tell us about yourself and what you guys doing at the Children's Cancer Institute? That's where you're located. What's going on there? Tell us what you guys are doing there? >>Sure, So I built into Cancer Institute. As it sounds, we do a lot of research when it comes to specifically the Children's cancer, though Children a unique in the sense that a lot of the typical treatment we use for adult may or may not work or will have adverse side effects. So what we do is we do all kinds of research. But what lab and I love, which we call a dry love What we do research in silica, using computers at the develop pipelines in order to improve outcomes for Children. >>And what are some of the things you get some to deal with us on the tech side, but also there's the workflow of the patients survival rates, capacity, those constraints that you guys are dealing with. And what are some of the some of the things going on there that you have to deal with and you're trying to improve the outcomes? What specific outcomes were you trying to work through? >>Well, at the moment off of the past decade and all the work you've done in the past decade, we've made a substantial impact on the supply of ability off several high risk cancers in Pediatrics on and we've Got a certain Program, which spent I'll talk about in more depth called the Zero Childhood Cancer Program and essentially that aims to reduce childhood cancer in Children uh, zero. So that, in other words, with the previous five ability 100% on hopefully, no lives will be lost. But that's >>and what do you guys doing specifically? What's your your job? What's your focus? >>Yes, so part of our lab Old computational biology. Uh, we run a processing pipeline, the whole genome and our next guest that, given the sequencing information for the kids, though, we sequence the healthy cells and we sequence there. Two missiles. We analyze them together, and what we do is we find mutations that are causing the cancel that help us determine what treatment. So what? Clinical trials might be most effective for the kids and so specifically Allah books on that pipeline where we run a whole bunch of bioinformatics tools, that area buying thematic basically biology, informatics, and we use the data generated sequel thing in order to extract those mutations that will be the cancer driving mutations that hopefully we can target in order to treat the kids. >>You know, you hear about an attack and you hear Facebook personalization recommendation engines. What the click on you guys are really doing Really? Mawr personalization around treatment recommendations. These kinds of things come into it. Can you share a little bit about what goes on there and and tell us what's happening? >>Well, as you mentioned when you first, some brought us into this, which we're looking at, the the profile of the team itself and that allows us to specialize the medication on the young treatment for that patient on. Essentially, that lets us improve the efficiency and the effectiveness off the treatment, which in turn has an impact on this probability off. >>What are some of the technical things? How did you guys get involved with Docker with Docker fit into all this? >>Yeah, I'm sure Camille will have plenty to bring up on this as well. But, um, yes, it's been quite a project to the the pipeline that we have. Um, we have built on a specific platforms and is looking great. But as with most tools in a lot of things that you develop when your engineers eyes pretty easy for them to become platform specific. And then that kind of stuck there. And you have to re engineer the whole thing kind of of a black hole. That's such a pain to there. So, um, the project that Mikhail in my field working on was actually taking it to the individual's pools we used in the pipeline and Docker rising them individually containing them with the dependencies they need so that we could hook them up anyway. We want So we can configure the pipeline, not just customized based off of the data like we're on the same pipeline and every it even being able to change the pipeline of different things to different kids. Be able to do that easily, um, to be able to run it on different platforms. You know, the fact that we have the choice not only means that we could save money, but if there's a cloud instance that will run an app costal. If there's a platform that you know wanted to collaborate with us and they say, Oh, we have this wholesome data we'd love for you to analyze. It's over hell, like a lot of you know, >>use my tool. It's really great. >>Yeah. And so having portability is a big thing as well. And so I'm sure people can go on about, uh, some of the pain point you having to do authorize all of the different, But, you know, even though they Austin challenges associated with doing it, I think the payoff is massive. >>Dig into this because this is one of the things where you've got a problem statement. You got a real world example. Cancer patients, life or death gets a serious things going on here. You're a tech. You get in here. What's going on? You're like, Okay, this is going to be easy. Just wrangle the data. I throw some compute at it. It's over, right? You know what? How did you take us through the life? They're, you know, living >>right. So a supreme I mentioned before, first and foremost well, in the scale of several 100 terabytes worth of data for every single patient. So obviously we can start to understand just how beneficial it is to move the pipeline to the data, rather the other way around. Um, so much time would be saved. The money costs as well, in terms of actually Docker rising the but the programs that analyze the data, it was quite difficult. And I think Sabrina would agree mate would agree with me on this point. The primary issue was that almost all of the apps we encountered within the pipeline we're very, very heavily dependent on very specific versions off some dependencies, but that they were just build upon so many other different APS on and they were very heavily fined tuned. So docker rising. It was quite difficult because we have to preserve every single version of every single dependency in one instance just to ensure that that was working. And these apps get updated quite Simpson my regularly. So we have to ensure that our doctors would survive. >>So what does it really take? The doc arise your pipeline. >>I mean, it was a whole project. Well, um, myself, Camille, we had a whole bunch of, um, automatic guns doing us over the summer, which was fantastic as well. And we basically have a whole team of lost words like, Okay, here's another automatic pull in the pipeline. You get enterprise, you get to go for a special you get enterprise, they each who individually and then you've been days awake on it, depending on the app. Easier than others. Um, but particularly when it comes to things a lot by a dramatic pools, some of them are very memory hungry. Some of them are very finicky. Some of the, um ah, little stable than others. And so you could spend one day characterizing a tool. And it's done, you know, in a handful of Allah's old. Sometimes it could make a week, and he's just getting this one tool done. And the idea behind the whole team working on it was eventually use. Look through this process, and then you have, um, a docker file set up. Well, anyone to run it on any system. And we know we have an identical set up, which was not sure before, because I remember when I started and I was trying to get the pipeline running on my own machine. Ah, lot of things just didn't look like Oh, you don't have the very specific version of ah that this developer has. 00 that's not working because you don't have this specific girl file that actually has a bug fixes in it. Just for us like, Well, >>he had a lot of limitations before the doctor and doctor analyzing docker container izing it. It was tough. What was it like before and after? >>And we'll probably speak more people full. It was basically, uh, yeah, days or weeks trying to set up on in. Stole everything needed around the whole pipeline. Yeah, it took a long time. And even then, a lot of things, But how you got to set up this? You know, I think speculation of pipeline, all the units, these are the three of the different programs. Will you need this version of obligation? This new upgrade of the tools that work with that version of Oz The old, all kinds of issues that you run into when they schools depend on entirely different things and to install, like, four different versions of python. Three different versions of our or different versions of job on the one machine, you know, just to run it is a bit of >>what has. It's a hassle. Basically, it's a nightmare. And now, after you're >>probably familiar with that, >>Yeah. So what's it like after >>it's a zoo? It supports ridiculously efficient. Like it. It's It's incredible what Michael mentioned before, as soon as we did in stone. Those at the versions of the dependencies. Dhaka keeps them naturally, and we can specify the versions within a docker container. So we can. We can absolutely guarantee that that application will run successfully and effectively every single time. >>Share with me how complicated these pipelines are. Sounds like that's a key piece here for you guys. And you had all the hassles that you do. Your get Docker rised up and things work smoothly. Got that? But tell >>me about >>the pipelines. What's what's so complicated about them? >>Honestly, the biggest complication is all of the connection. It's not a simple as, um, run a from the sea, and then you don't That would be nice, but that know how these things work if you have a network of programs with the output of this, input for another, and you have to run this program before this little this one. But some of the output become input for multiple programs, and by the time you hook the whole thing up, it looks like a gigantic web of applications. The way all the connections, so it's a massive Well, it almost looks like a massive met when you look at it. But having each of the individual tools contained and working means that we can look them all up. And even though it looks complicated, it would be far more complicated if we had that entire pipeline. You know, in a single program like having to code, that whole thing in a single group would be an absolute nightmare. Where is being able to have each of the tools as individual doctors means we just have the link, the input on that book, which is the top. But once you've done that, it means that you know each of the individual pools will run. And if an individual fails, or whatever raised in memory or other issues run into, you can rerun that one individual school re hooks the output into whatever the next program is going without having one massive you know, program will file what it fails midway through, and there's nothing you can do. >>Yeah, you unpack. It really says, Basically, you get the goodness to the work up front, and a lot of goodness come out of it. So this lets comes to the future of health. What are the key takeaways that you guys have from this process? And how does it apply to things that might be helpful to you right around the corner? Or today, like deep learning as you get more tools out there with machine learning and deep learning? Um, we hope there's gonna be some cool things coming out. What do you guys see here? And the insights? >>Well, we have a section of how the computational biologist team that is looking into doing more predictive talks working out, um, basically the risk of people developing can't the risks of kids developing cancel. And that's something you can do when you have all of this data. But that requires a lot of analysis as well. And so one of the benefits of you know being able to have these very moveable pipelines and tools makes it easier to run them on. The cloud makes it easier to shale. You're processing with about researches to the hospitals, just making collaboration easier. Mainz that data sharing becomes a possibility or is before if you have three different organizations. But the daughter in three different places. Um, how do you share that with moving the daughter really feasible. Pascal, can you analyze it in a way that practical and so I don't want one of the benefits of Docker? Is all of these advanced tools coming out? You know, if there's some amazing predicted that comes out that uses some kind of regression little deep learning, whatever. If we wanted to add that being able to dock arise a complex school into a single docker ice makes it less complicated that highlighted the pipeline in the future, if that's something we'd like to do, >>Camille, any thoughts on your end on this? >>Actually, I was Sabrina in my mind for the last point. I was just thinking about scalability definitely is very. It's a huge point because the part about the girls as a technology does any kind of technology that we've got to inspect into the pipeline. As of now, it be significantly easier with the use of Docker. You could just docker rise that technology and then implant that straight into the pipeline. Minimal stress. >>So productivity agility doesn't come home for you guys. Is that resonate? >>Yeah, definitely. >>And you got the collaboration. So there's business benefits, the outcomes. Are there any proof points you could share on some results that you guys are seeing some fruit from the tree, if you will, from all this Goodness. >>Well, one of the things we've been working on is actually a collaboration with those Bio Commons and Katica. They built a platform, specifically the development pipelines. We wanted to go out, and they have support for Docker containers built into the platform, which makes it very easy to push a lot of containers of the platform, look them up and be able to collaborate with them not only to try a new platform without that, but also help them look like a platform to be able to shoot action access data that's been uploaded there as well. But a lot of people we wouldn't have been able to do that if we hadn't. Guys, they're up. It just wouldn't have. Actually, it wouldn't be possible. And now that we have, we've been able to collaborate with them in terms of improving the platform. But also to be able to share and run our pipelines on other data will just pretty good, >>awesome. Well, It's great to have you on the Cube here on Docker Con 2020 from down under. Great Internet connections get great Internet down. They're keeping us remote were sheltering in place here. Stay safe and you guys final question. Could you eat? Share in your own words from a developer? From a tech standpoint, as you're in this core role, super important role, the outcomes are significant and have real impact. What has the technology? What is docker ization done for you guys and for your work environment and for the business share in your own words what it means. A lot of other developers are watching What's your opinion? >>But yeah, I mean, the really practical point is we've massively increased capacity of the pipeline. One thing that been quite fantastic years. We've got a lot of increased. The Port zero child who can program, which means going into the schedule will actually be able to open a program. Every child in Australia that, uh, has cancel will be ableto add them to the program. Where is currently we're only able to enroll kids who are low survivability, right? So about 30% the lowest 30% of the viability we're able to roll over program currently, but having a pipeline where we can just double the memory like that double the amount of battle. Uh, and the fact that we can change the instance is really to just double the capacity trip. The capacity means that now that we have the support to be able to enroll potentially every kid, Mr Leo, um, once we've upgraded the whole pipeline, it means will actually be a code with the amount of Children being enrolled, whereas on the existing pipeline, we're currently that capacity. So doing the upgrade in a really practical way means that we're actually going to be a triple the number of kids in Australia. We can add onto the program which wouldn't have been possible otherwise >>unleashing the limitations and making it totally scalable. Your thoughts as developers watching you're in there, Your hand in your hands, dirty. You built it. It's showing some traction. What's what's your what's your take? What's your view? >>Well, I mean first and foremost locks events. It just feels fantastic knowing that what we're doing is as a substantial and quantify who impact on the on a subset of the population and we're literally saving lives. Analyze with the work that we're doing in terms off developing with With that technology, such a breeze especially compared Teoh I've had minimal contact with what it was like without docker and from the horror stories I've heard, it's It's It's a godsend. It's It's it's really improved The quality of developing. >>Well, you guys have a great mission. And congratulations on the success. Really impact right there. You guys are doing great work and it must feel great. I'm happy for you and great to connect with you guys and continue, you know, using technology to get the outcomes, not just using technology. So Fantastic story. Thank you for sharing. Appreciate >>you having me. >>Thank you. >>Okay, I'm John for we here for Docker Con 2020 Docker con virtual docker con digital. It's a digital event This year we were all shale three in place that we're in the Palo Alto studios for Docker con 2020. I'm John furrier. Stay with us for more coverage digitally go to docker con dot com from or check out all these different sessions And of course, stay with us for this feat. Thank you very much. Yeah, yeah, yeah, yeah, yeah, yeah

>>from around the globe. It's the queue with digital coverage of Docker Con Live 2020 brought to you by Docker and its ecosystem partners. Everyone welcome back to Docker Con 2020 Docker Con 20. I'm John Furrier, host of the Cube. We're here for virtual event docker con docker, con dot com, and check out all the great footage. And also great guests were talking to all the major thought leaders and people in the industry making it happen as we have this new reality, a great guest and a great segment here from Engine. It's now part of F five, Robb said. Who's the vice president? Product management Sydney, thanks for coming on this segment. Appreciate you taking the time to chat with us. >>No problem. Happy to be here >>so and UNIX Everyone that does development knows about you. Guys have been very popular product with developers. Number one in the Docker hub will get to that later on this segment. So it's known really in the industry is really easy, easy to use and very reliable component of cloud native and cloud, if you will Anything that working So So I got I got to ask you with the new reality we're living with Covert 19 we now see the new reality that's now apparent to everyone in the world that with new work style, working at home VPNs are under provision now. People working from home, more service area with security. The at scale problems are surface for the executives and business, saying, We need to figure this new reality out because this is not going to change. It's going to move to hybrid when it comes back. But ultimately it exposes and highlights the opportunities around cloud native and kind of shows the operating model of how applications are going to be using. So I think this is going to be mainstream trend for what used to be an inside baseball kind of industry. Conversation around micro services, containers, docker containers, kubernetes. This is all now a tailwind for what will be a massive surge in new APS. I want to get your thoughts and reaction to that as you guys are in the middle of it with your product and the developers would have to build new value on top of it. What's your reaction? >>Yeah, I think you're absolutely right. We're also dealing with our own version of this new way of working right. We're also working from home and working remotely and seeing how that impacts us. But as we think about our customers and the folks that leverage in genetics, we started with scaling applications. We have 10 X solution that made it easier to deploy an application, have it scale in a very efficient way. And so it's folks are moving online more and more, relying more on staying connected, no matter where they're working from. Providing that capability is something that's going to continue to be core and will increase in importance. And these folks are looking to build more modern applications or modernize what they already have. Leveraging our technologies is just a natural extension. It's the technology they're already familiar with. They've been relying on it for many years and, you know, as they look to the future, has the capabilities they need to continue to rely on it going forward. >>What are some of the new things that you're working on? You can share with the audience because you're known for tried and true, very reliable. Okay, now you got micro services, which is emerging and very dynamic, literally, figuratively. So what's the new stuff? What do you guys focused on? Can you share some insights into how you're thinking about it and some things that you're doing? >>Yeah, a big part of what we're focusing on is really taking with headaches that come with scaling up applications, especially in the modern world. Now, those headaches are all about understanding the complexity of these new applications, being in the confidence needed to be able to deploy them at scale and understand not only what they're doing, but make sure that if something were to go wrong, they could figure out what was happening. And so, as we think about the investments we're making at the help folks modernize versus just making it easier to employ at modern applications of scale, which is one category of things, second is making sure that you have a really strong understanding of how the application is really working, so that, you know, with if it breaks, it could be fixed quickly. But there opportunities to improve it. We can quickly see the impact of it, and, you know, there's a lot of capabilities we're building in on those two dimensions. And in the third dimension, I would say is around security. I think there's a lot of new surface area. It's being exposed as folks start to build more micro services based applications. And you know, with the technology we have way allow people to buy both rich security capabilities as well as very surgical capabilities, depending on where they need the right functionality. >>And the container business has been really great ride to watch the rise of containers that really someone who has been in software engineering since I was 17. You know, the old way of systems thinking is modernized with containers, and you saw that the beginning of a surge of a sea change Now, actually, with micro services, you just pointed out it's gonna create a whole nother level level of head room. But containers really brought in this notion of making systems work better together, and I think that's really been a great boon for developers. So I got to ask you, you know, Docker containers and now kubernetes on this trend, you guys have been very popular, if not the most popular downloaded container in the hub, and so you've been super popular developers. So what happens next? First? Well, why is that the case and talk to the developers? Why will you continue to be popular? What do you guys have got to keep that that satisfaction going. Why so popular? And how are you going to keep that rolling? >>Yeah, I think. Why so popular? I think we've been fortunate to ride the wave of trusted solutions, right? So folks were already leveraging us for their critical applications. I've been very critical location. It's natural to look to that same text technology as you move to new environments. And, yeah, we've been very fortunate. Teoh have folks continue to trust us with their applications as they move to new environments as a containerized things. And we appreciate that. And we continue to invest in making sure that our feature set is just as capable in those environments as it is anywhere else. And in addition to that, we do invest heavily in making sure that our capabilities and those in the container, space and micro services space specifically, are you staying ahead of where there's a lot of work we're doing to support the next generation capabilities that folks want to be able to leverage but aren't necessarily yet. And that scales from kind of near term things like like G rpc all the way out to HDP three. That's on the horizon. So as we look at the space, we're privileged to have the footprint already. But at the same time, we're not resting on our laurels. We're absolutely investing and making sure that we allow folks to continue to deliver that high quality, high performance application experience no matter what environment they choose to use. >>You know, you know, this whole covert crisis brings up the glass is half full or half empty, depending on your view is you know that due to the two worlds are certainly getting more collision oriented when it come together. The CSO level size of sides of the business and the developer side. We've always said for years other developers on the front lines and it's true, have been cloud native and cloud has been great for developers, but now more than ever, the conversation having on the business side would CSO CIO, CIO, CSO, or whatever have been Hey, my house is on fire after I don't have worry about I don't need to worry about the appliances and what's going on in my kitchen. I need to save my business. And so they're then gonna call the developers to the table. And you're seeing this this kind of formation of critical path thinking around OK, we need to come out of this crisis on a reinvention growth trajectory, which brings the developers into the mix even faster. So I want to get your thoughts on that because, you know, what does that actually mean? Are they gonna be called in for projects? I mean, what's the media's look like? Because you have a zoom meeting or whatever this is going to be now a new dynamic, A new psychology of the business models of these companies with developers are going to be very active leaders in that new role. Because the virtualized world, now that we live in, is going to be different. The applications have more demands and more more needs more capabilities. So take us through your thinking on this and what what should developers expect when they get called to those meetings? >>Yeah, I think you know the trend that we're seeing that's going to accelerate. I believe as a result of this is the internal transformation. So there's a lot of technologies that developers already leverage be able to deliver that absent. There's technologies that they'd like to be able to leverage more and more, especially if they're using more modern environments. And that tends to come into sharp relief against the legacy infrastructure that exists in the legend legacy tooling that oftentimes exists in large organizations. And so, as organizations start to see, not only about the in the world has changed prior to code, and they need to modernize and transform. I think you know this. This crisis will also spur folks toe really put more thought into how they operate. We're already looking at from the remote work perspective, but also the agility that businesses really want to be able to have but traditionally have been prevented from having. And so I think that the developers are really gonna have an opportunity here to really drive that agile change they want to see in an organization so they can get the capabilities they want help to market quickly. That's going to require new tools, new processes within the organization and those types of things that we're fully supported about. We work in legacy environments, work in modern environments. We allow companies to be as agile as they like to be. I think developers have a really good opportunity here to really be leaders of that change. >>That's awesome. Great insight. So let's talk about the developer side. I'll put my developer hat on for a second here. Sydney. OK, The business guys came to me. We're gonna We're gonna do more cool stuff. I get that. That's totally relevant. Very good insight there. But now in the developer and I have been working with engineers, and I know of Engine X. What's in it for me? What's in it for me? The developer? What do I need to know about Engine X now for me, as a developer, going forward? >>Look, I mean, way come from a really strong, open source tradition. And you know the main reason folks use our solutions. Because if we take headaches away right, I mean, we're a tool that allows folks to deliver their applications, deploy their applications without having to worry about the mechanics. And so for the developers, you know what's in it for you is you build, the application will take care of. The rest will make sure it gets delivered with the controls that are required with security and authentication is required. We operate as an extension of your application. We provide a lot of nice things in the front door. All the way back to you know, into the bedroom is technically a spark, as the application infrastructure is concerned. But, you know, we take care of that common infrastructure. They keep infrastructure set of capabilities needed. That application. Developers can simply focus on building the best applications they can, and we'll make sure that they were >>awesome. Now let's get into the F five acquisition combination with Engine X. What does that do for you guys? As a change of capabilities as it increased more head room for solutions? Is there a new joint tech take us through some of the impacts of that combination? >>Yeah, so it's been a good right. It's been just over a year since the deal closed, and we've been aggressively investing in scaling up the vision that we had previously have. We really want to bring applications to life. You make it so that your application not only scalable and highly available, but it's able to adapt over time. And that, of course, would require input from operations teams, of course, but you know, we're trying to make sure that folks have the ability to operate their applications under any circumstances, whether they're being attacked, whether they're under high demand, whether people are moving all over the place, and we're really trying to make it so that the application is essentially bullet proof. So with that five, we have the ability to invest more in that road map in that vision, in addition to bringing on some pretty cool, complimentary capabilities. One of the things that we're really happy to see is the rich security capabilities that five have has that we're now able todo leverage with the Internet solutions side by side, providing no again new ways to get really advanced security capabilities into the right places in your application greeting. Yeah, >>great insights. I really appreciate that That commentary love to get your thoughts on just something that's always been near and dear to my heart, being cloud world since the early days and trying stuff. Now it's fully enterprise ready and doing all sorts of new things that multi cloud hybrid. But remember the days back when Dev Ops was kind of debated? All that is the day of is it ops? And it always had that Dev ops kind of. I'm an operations person or a devil developer. That's kind of generally been resolved in the sense that infrastructure is code is kind of resolve that. But now, with the Covad crisis, you're seeing operations clearly front and center again, right? So you got security ops now coming online, networking up. So I think the new reality and the edge exploding people are home. That's technically an edge. Perimeter security is now the edge point. More and more edge is more and more network traffic is getting more and more complicated. This >>is >>put bring up a lot of conversation around. What is the new formula As you navigate this, how do you attack the problem? Space is how do you create solutions? Is there a playbook? Is there anything that you could share in terms of this new thinking? Because it's gonna be a new trajectory. I think this is an inflection point came from explosions coming of APS. I believe we've been reporting on that. But the thinking has to change. It's going to be pretty crazy. What's your what's your thoughts on this? >>Yeah, I think folks are getting more and more experience with this new way of working on infrastructure of code is absolutely here. Um, automation is absolutely your orchestrations. Absolutely here. And so I see no more and more of these capabilities will get stitched together. And as I said earlier, you know this this organizational transformation It's all about taking the human more and more out of the loop for certain things to be ableto benefit or to the benefit of being able to move more quickly, but in a predictable way. So you're living failures that come with moving quickly. But you're getting that elasticity that you really want. And so, yeah, I think there's more, more adoption of practices. It's not gonna be overnight for folks. But I do think again, this this crisis is gonna give folks an opportunity to really take a deeper look at how they've been operating and where they want to get to, and it's gonna provide an opportunity to accelerate that move, >>you know, from a developer's perspective. The tried and true form of making something complex, easy with us through abstractions making highly performing and highly available. Always a good formula, right? I mean, as the world gets more complex, you still got to move packets around. You still got to run applications. It's just gonna be that tried and true formula of reduce the complexity, make things easier but makes things run faster, make things runs higher scale. This seems to be the play book. What's your thoughts? >>Yeah, absolutely. You know, things that once were hard to becoming easy. And I think we look back three years. Five years from now, we'll see a world that's that's even more automated, moving much more quickly. And some of the things that look difficult now are gonna become commoditized, right? So, you know, as I talked about bringing applications of life and making applications more resilience, more able to protect themselves more ableto, he'll defend all that kind of stuff. The things that the advanced things that we're doing now that folks are playing with will become the easy things, and we'll have new challenges to focus on, especially as we look at things like Ai. We're really starting to get a sense for some of the capabilities we can apply Teoh impact application behaviors and performance. But once you get to the point where you build up a good library of capabilities now, you really have a nice playbook that can become a foundation for even more advanced things. >>Yeah, build that foundation. Scale it up. It's beautiful scales and new competitive Advantage. Lovett Final question. Just take a minute to give the plug for Engine X. Really appreciate your insights here in this segment on this new reality, this new new developer environments going to be huge. Give the plug for engines. What are you guys working on? What should people know about share? What's happened? >>Yeah, so Internet spent, you know, the last decade plus making applications work at scale. I'm really focused now on making applications easy and bringing them to life. And so, you know, the laser focus we have is on taking away the headaches that folks might have, you know, as they try to scale up on their applications. So we're focused on that space we're focused on taking with headaches that folks have is they're trying to make sure that the applications more secure we're taking away the headaches of folks have is they're dealing with complexity of applications. Um, and 80 eyes. You know, that's that's the hottest thing. Right now, people are talking about applications, but they're actually talking about AP eyes that needs to be leveraged, to be able to make their applications really saying so, you know, in all of those spaces, our focus is on making modernization much easier And taking where the headaches associated with doing so. >>Sidney, wrap side with VP of product management at engine X now part of F five. Great conversation. Um, him up on Twitter. He's out there. Great conversation with the community. Really appreciate you taking the time. Thank you. >>Thank you. >>Okay. Him up on Twitter? If any questions jump into the event, this is Docker con 2020. I'm John Furrier here in the Palo Alto studios. Getting all the moat interviews as fast as we can get them to you. Here is Docker con segment. Thanks for watching. Yeah, yeah, yeah, yeah, yeah

>>From around the globe. It's the queue with digital coverage of DockerCon live 2020 brought to you by Docker and its ecosystem partners. >>Hello everyone. Welcome to Docker con 2020 I'm John furrier with the cube. I'm in our Palo Alto studios with our quarantine crew. We have a great lineup here for DockerCon con 2020 virtual event. Normally it was in person face to face. I'll be with you throughout the day from an amazing lineup of content over 50 different sessions, cube tracks, keynotes, and we've got two great co-hosts here with Docker, Jenny Marcio and Brett Fisher. We'll be with you all day, all day today, taking you through the program, helping you navigate the sessions. I'm so excited, Jenny. This is a virtual event. We talk about this. Can you believe it? We're, you know, may the internet gods be with us today and hope everyone's having an easy time getting in. Jenny, Brett, thank you for being here. Hey, >>Yeah. Hi everyone. Uh, so great to see everyone chatting and telling us where they're from. Welcome to the Docker community. We have a great day planned for you >>Guys. Great job. I'm getting this all together. I know how hard it is. These virtual events are hard to pull off. I'm blown away by the community at Docker. The amount of sessions that are coming in the sponsor support has been amazing. Just the overall excitement around the brand and the, and the opportunities given this tough times where we're in. Um, it's super exciting. Again, made the internet gods be with us throughout the day, but there's plenty of content. Uh, Brett's got an amazing all day marathon group of people coming in and chatting. Jenny, this has been an amazing journey and it's a great opportunity. Tell us about the virtual event. Why DockerCon virtual. Obviously everyone's cancelling their events, but this is special to you guys. Talk about Docker con virtual this year. >>Yeah. You know, the Docker community shows up at DockerCon every year and even though we didn't have the opportunity to do an in person event this year, we didn't want to lose the time that we all come together at DockerCon. The conversations, the amazing content and learning opportunities. So we decided back in December to make Docker con a virtual event. And of course when we did that, there was no quarantine. Um, we didn't expect, you know, I certainly didn't expect to be delivering it from my living room, but we were just, I mean we were completely blown away. There's nearly 70,000 people across the globe that have registered for Docker con today. And when you look at backer cons of past right live events, really and more learning are just the tip of the iceberg. And so thrilled to be able to deliver a more inclusive vocal event today. And we have so much planned. Uh, I think Brett, you want to tell us some of the things that you have planned? >>Well, I'm sure I'm going to forget something cause there's a lot going on. But, uh, we've obviously got interviews all day today on this channel with John the crew. Um, Jenny has put together an amazing set of all these speakers all day long in the sessions. And then you have a captain's on deck, which is essentially the YouTube live hangout where we just basically talk shop. Oh, it's all engineers, all day long, captains and special guests. And we're going to be in chat talking to you about answering your questions. Maybe we'll dig into some stuff based on the problems you're having or the questions you have. Maybe there'll be some random demos, but it's basically, uh, not scripted. It's an all day long unscripted event, so I'm sure it's going to be a lot of fun hanging out in there. >>Well guys, I want to just say it's been amazing how you structured this so everyone has a chance to ask questions, whether it's informal laid back in the captain's channel or in the sessions where the speakers will be there with their, with their presentations. But Jenny, I want to get your thoughts because we have a site out there that's structured a certain way for the folks watching. If you're on your desktop, there's a main stage hero. There's then tracks and Brett's running the captain's tracks. You can click on that link and jump into his session all day long. He's got an amazing set of line of sleet, leaning back, having a good time. And then each of the tracks, you can jump into those sessions. It's on a clock. It'll be available on demand. All that content is available if you're on your desktop, if you're on your mobile, it's the same thing. >>Look at the calendar, find the session that you want. If you're interested in it, you could watch it live and chat with the participants in real time or watch it on demand. So there's plenty of content to navigate through. We do have it on a clock and we'll be streaming sessions as they happen. So you're in the moment and that's a great time to chat in real time. But there's more, Jenny, you're getting more out of this event. We, you guys try to bring together the stimulation of community. How does the participants get more out of the the event besides just consuming some of the content all day today? >>Yeah. So first set up your profile, put your picture next to your chat handle and then chat. We have like, uh, John said we have various setups today to help you get the most out of your experience are breakout sessions. The content is prerecorded so you get quality content and the speakers and chat. So you can ask questions the whole time. Um, if you're looking for the hallway track, then definitely check out the captain's on deck channel. Uh, and then we have some great interviews all day on the queue so that up your profile, join the conversation and be kind, right. This is a community event. Code of conduct is linked on every page at the top and just have a great day. >>And Brett, you guys have an amazing lineup on the captain, so you have a great YouTube channel that you have your stream on. So the folks who were familiar with that can get that either on YouTube or on the site. The chat is integrated in, so you're set up, what do you got going on? Give us the highlights. What are you excited about throughout your day? Take us through your program on the captains. That's going to be probably pretty dynamic in the chat too. >>Yeah. Yeah. So, uh, I'm sure we're going to have less, uh, lots of, lots of stuff going on in chat. So no concerns there about, uh, having crickets in the, in the chat. But we're going to, uh, basically starting the day with two of my good Docker captain friends, uh, Nirmal Mehta and Laura taco. And we're going to basically start you out and at the end of this keynote, at the end of this hour, and we're going to get you going. And then you can maybe jump out and go to take some sessions. Maybe there's some cool stuff you want to check out in other sessions that are, you want to chat and talk with the, the instructors, the speakers there, and then you're going to come back to us, right? Or go over, check out the interview. So the idea is you're hopping back and forth and throughout the day we're basically changing out every hour. >>We're not just changing out the, uh, the guests basically, but we're also changing out the topics that we can cover because different guests will have different expertise. We're going to have some special guests in from Microsoft, talk about some of the cool stuff going on there. And basically it's captains all day long. And, uh, you know, if you've been on my YouTube live show you, you've watched that, you've seen a lot of the guests we have on there. I'm lucky to just hang out with all these really awesome people around the world, so it's going to be fun. >>Awesome. And the content again has been preserved. You guys had a great session on call for paper sessions. Jenny, this is good stuff. What are the things can people do to make it interesting? Obviously we're looking for suggestions. Feel free to, to chirp on Twitter about ideas that can be new. But you guys got some surprises. There's some selfies. What else? What's going on? Any secret, uh, surprises throughout the day. >>There are secret surprises throughout the day. You'll need to pay attention to the keynotes. Brett will have giveaways. I know our wonderful sponsors have giveaways planned as well in their sessions. Uh, hopefully right you, you feel conflicted about what you're going to attend. So do know that everything is recorded and will be available on demand afterwards so you can catch anything that you miss. Most of them will be available right after they stream the initial time. >>All right, great stuff. So they've got the Docker selfie. So the Docker selfies, the hashtag is just Docker con hashtag Docker con. If you feel like you want to add some of the hashtag no problem, check out the sessions. You can pop in and out of the captains is kind of the cool, cool. Kids are going to be hanging out with Brett and then all they'll knowledge and learning. Don't miss the keynote. The keynote should be solid. We got changed governor from red monk delivering a keynote. I'll be interviewing him live after his keynote. So stay with us and again, check out the interactive calendar. All you gotta do is look at the calendar and click on the session you want. You'll jump right in. Hop around, give us feedback. We're doing our best. Um, Brett, any final thoughts on what you want to share to the community around, uh, what you got going on the virtual event? Just random thoughts. >>Yeah. Uh, so sorry, we can't all be together in the same physical place. But the coolest thing about as business online is that we actually get to involve everyone. So as long as you have a computer and internet, you can actually attend DockerCon if you've never been to one before. So we're trying to recreate that experience online. Um, like Jenny said, the code of conduct is important. So, you know, we're all in this together with the chat, so try to try to be nice in there. These are all real humans that, uh, have feelings just like me. So let's, let's try to keep it cool and, uh, over in the Catherine's channel be taking your questions and maybe playing some music, playing some games, giving away some free stuff. Um, while you're, you know, in between sessions learning. Oh yeah. >>And I gotta say props to your rig. You've got an amazing setup there, Brett. I love what your show you do. It's really bad ass and kick ass. So great stuff. Jenny sponsors ecosystem response to this event has been phenomenal. The attendance 67,000. We're seeing a surge of people hitting the site now. So, um, if you're not getting in, just, you know, just wait going, we're going to crank through the queue, but the sponsors on the ecosystem really delivered on the content side and also the sport. You want to share a few shout outs on the sponsors who really kind of helped make this happen. >>Yeah, so definitely make sure you check out the sponsor pages and you go, each page is the actual content that they will be delivering. So they are delivering great content to you. Um, so you can learn and a huge thank you to our platinum and gold authors. >>Awesome. Well I got to say, I'm super impressed. I'm looking forward to the Microsoft Amazon sessions, which are going to be good. And there's a couple of great customer sessions there and you know, I tweeted this out last night and let them get you guys' reaction to this because you know, there's been a lot of talk around the covert crisis that we're in, but there's also a positive upshot to this is Cambridge and explosion of developers that are going to be building new apps. And I said, you know, apps apps aren't going to just change the world. They're gonna save the world. So a lot of the theme years, the impact that developers are having right now in the current situation, you know, if we get the goodness of compose and all the things going on in Docker and the relationships, this real impact happening with the developer community. And it's pretty evident in the program and some of the talks and some of the examples how containers and microservices are certainly changing the world and helping save the world. Your thoughts. >>Yeah. So if you, I think we have a, like you said, a number of sessions and interviews in the program today that really dive into that. And even particularly around coven, um, Clemente is sharing his company's experience, uh, from being able to continue operations in Italy when they were completely shut down. Uh, beginning of March, we have also in the cube channel several interviews about from the national Institute of health and precision cancer medicine at the end of the day. And you just can really see how containerization and, uh, developers are moving in industry and, and really humanity forward because of what they're able to build and create, uh, with advances in technology. Yeah. >>And first responders and these days is developers. Brett compose is getting a lot of traction on Twitter. I can see some buzz already building up. There's huge traction with compose, just the ease of use and almost a call for arms for integrating into all the system language libraries. I mean, what's going on with compose? I mean, what's the captain say about this? I mean, it seems to be really tracking in terms of demand and interest. >>Yeah, it's, it's a, I think we're over 700,000 composed files on GitHub. Um, so it's definitely beyond just the standard Docker run commands. It's definitely the next tool that people use to run containers. Um, just by having that we just by, and that's not even counting. I mean, that's just counting the files that are named Docker compose Yammel so I'm sure a lot of you out there have created a gamma file to manage your local containers or even on a server with Docker compose. And the nice thing is, is Docker is doubling down on that. So we've gotten some news recently, um, from them about what they want to do with opening the spec up, getting more companies involved, because compose is already gathered so much interest from the community. You know, AWS has importers, there's Kubernetes importers for it. So there's more stuff coming and we might just see something here in a few minutes. >>Well, let's get into the keynote. Guys, jump into the keynote. If you missed anything, come back to the stream, check out the sessions, check out the calendar. Let's go. Let's have a great time. Have some fun. Thanks for enjoy the rest of the day. We'll see you soon..