>>Good evening, brilliant humans. My name is Savannah Peterson and very delighted to be streaming to you. Live from the Cube Studios here in Motor City, Michigan. I've got John Furrier on my left. John, this is our last interview of the day. Energy just seems to keep oozing. How >>You doing? Take two, Three days of coverage, the queue love segments. This one's great cuz we have a practitioner who's implementing all the hard core talks to be awesome. Can't wait to get into it. >>Yeah, I'm very excited for this one. If it's not very clear, we are a community focused community is a huge theme here at the show at Cape Con. And our next guests are actually a provider and a customer. Turning it over to you. Lisa and Jake, welcome to the show. >>Thank you so much for having us. >>It's great to be here. It is our pleasure. Lisa, you're with Cockroach. Just in case the audience isn't familiar, give us a quick little sound bite. >>We're a distributed sequel database. Highly scalable, reliable. The database you can't kill, right? We will survive the apocalypse. So very resilient. Our customers, mostly retail, FinTech game meet online gambling. They, they, they need that resiliency, they need that scalability. So the indestructible database is the elevator pitch >>And the success has been very well documented. Valuation obviously is a scorp guard, but huge customers. We were at the Escape 19. Just for the record, the first ever multi-cloud conference hasn't come back baby. Love it. It'll come back soon. >>Yeah, well we did a similar version of it just a month ago and I was, that was before Cockroach. I was a different company there talking a lot about multi-cloud. So, but I'm, I've been a car a couple of years now and I run community, I run developer relations. I'm still also a CNCF ambassador, so I lead community as well. I still run a really large user group in the San Francisco Bay area. So we've just >>Been in >>Community, take through the use case. Jake's story set us up. >>Well I would like Jake to take him through the use case and Cockroach is a part of it, but what they've built is amazing. And also Jake's history is amazing. So you can start Jake, >>Wherever you take >>Your Yeah, sure. I'm Jake, I'm CEO and co-founder of Offset. Oted is the commercial entity behind Spice Dvy and Spice Dvy is a permission service. Cool. So a permission service is something that lets developers and let's platform teams really unlock the full potential of their applications. So a lot of people get stuck on My R back isn't flexible enough. How do I do these fine grain things? How do I do these complex sharing workflows that my product manager thinks is so important? And so our service enables those platform teams and developers to do those kinds of things. >>What's your, what's your infrastructure? What's your setup look like? What, how are you guys looking like on the back end? >>Sure. Yeah. So we're obviously built on top of Kubernetes as well. One of the reasons that we're here. So we use Kubernetes, we use Kubernetes operators to orchestrate everything. And then we use, use Cockroach TV as our production data store, our production backend data store. >>So I'm curious, cause I love when these little matchmakers come together. You said you've now been presenting on a little bit of a road show, which is very exciting. Lisa, how are you and the team surfacing stories like Jakes, >>Well, I mean any, any place we can obviously all the social medias, all the blogs, How >>Are you finding it though? >>How, how did you Oh, like from our customers? Yeah, we have an open source version so people start to use us a long time before we even sometimes know about them. And then they'll come to us and they'll be like, I love Cockroach, and like, tell me about it. Like, tell me what you build and if it's interesting, you know, we'll we'll try to give it some light. And it's always interesting to me what people do with it because it's an interesting technology. I like what they've done with it. I mean the, the fact that it's globally distributed, right? That was like a really important thing to you. Totally. >>Yeah. We're also long term fans of Cockroach, so we actually all work together out of Workbench, which was a co-working space and investor in New York City. So yeah, we go way back. We knew the founders. I, I'm constantly saying like if I could have invested early in cockroach, that would've been the easiest check I could have ever signed. >>Yeah, that's awesome. And then we've been following that too and you guys are now using them, but folks that are out there looking to have the, the same challenges, what are the big challenges on selecting the database? I mean, as you know, the history of Cockroach and you're originating the story, folks out there might not know and they're also gonna choose a database. What's the, what's the big challenge that they can solve that that kind of comes together? What, what would you describe that? >>Sure. So we're, as I said, we're a permission service and per the data that you store in a permission service is incredibly sensitive. You need it to be around, right? You need it to be available. If the permission service goes down, almost everything else goes down because it's all calling into the permission service. Is this user allowed to do this? Are they allowed to do that? And if we can't answer those questions, then our customer is down, right? So when we're looking at a database, we're looking for reliability, we're looking for durability, disaster recovery, and then permission services are one of the only services that you usually don't shard geographically. So if you look at like AWS's iam, that's a global service, even though the individual things that they run are actually sharded by region. So we also needed a globally distributed database with all of those other properties. So that's what led us >>To, this is a huge topic. So man, we've been talking about all week the cloud is essentially distributed database at this point and it's distributed system. So distributed database is a hot topic, totally not really well reported. A lot of people talking about it, but how would you describe this distributed trend that's going on? What are the key reasons that they're driving it? What's making this more important than ever in your mind, in your opinion? >>I mean, for our use case, it was just a hard requirement, right? We had to be able to have this global service. But I think just for general use cases, a distributed database, distributed database has that like shared nothing architecture that allows you to kind of keep it running and horizontally scale it. And as your requirements and as your applications needs change, you can just keep adding on capacity and keep adding on reliability and availability. >>I'd love to get both of your opinion. You've been talking about the, the, the, the phases of customers, the advanced got Kubernetes going crazy distributed, super alpha geek. Then you got the, the people who are building now, then you got the lagers who are coming online. Where do you guys see the market now in terms of, I know the Alphas are all building all the great stuff and you guys had great success with all the top logos and they're all doing hardcore stuff. As the mainstream enterprise comes in, where's their psychology, what's on their mind? What's, you share any insight into your perspective on that? Because we're seeing a lot more of it folks becoming like real cloud players. >>Yeah, I feel like in mainstream enterprise hasn't been lagging as much as people think. You know, certainly there's been pockets in big enterprises that have been looking at this and as distributed sequel, it gives you that scalability that it's absolutely essential for big enterprises. But also it gives you the, the multi-region, you know, the, you have to be globally distributed. And for us, for enterprises, you know, you need your data near where the users are. I know this is hugely important to you as well. So you have to be able to have a multi-region functionality and that's one thing that distributed SQL lets you build and that what we built into our product. And I know that's one of the things you like too. >>Yeah, well we're a brand new product. I mean we only founded the company two years ago, but we're actually getting inbound interest from big enterprises because we solve the kinds of challenges that they have and whether, I mean, most of them already do have a cockroach footprint, but whether they did or didn't, once they need to bring in our product, they're going to be adopting cockroach transitively anyway. >>So, So you're built on top of Cockroach, right? And Spice dv, is that open source or? >>It >>Is, yep. Okay. And explain the role of open source and your business model. Can you take a minute to talk about the relevance of that? >>Yeah, open source is key. My background is, before this I was at Red Hat. Before that we were at CoreOS, so CoreOS acquisition and before that, >>One of the best acquisitions that ever happened for the value. That was a great, great team. Yeah, >>We, we, we had fun and before that we built Qua. So my co-founders and I, we built Quay, which is a, a first private docker registry. So CoreOS and, and all of those things are all open source or deeply open source. So it's just in our dna. We also see it as part of our go-to market motion. So if you are a database, a lot of people won't even consider what you're doing without being open source. Cuz they say, I don't want to take a, I don't want to, I don't want to end up in an Oracle situation >>Again. Yeah, Oracle meaning they go, you get you locked in, get you in a headlock, Increase prices. >>Yeah. Oh yeah, >>Can, can >>I got triggered. >>You need to talk about your PTSD there >>Or what. >>I mean we have 20,000 stars on GitHub because we've been open and transparent from the beginning. >>Yeah. And it >>Well, and both of your projects were started based on Google Papers, >>Right? >>That is true. Yep. And that's actually, so we're based off of the Google Zans of our paper. And as you know, Cockroach is based off of the Google Span paper and in the the Zanzibar paper, they have this globally distributed database that they're built on top of. And so when I said we're gonna go and we're gonna make a company around the Zabar paper, people would go, Well, what are you gonna do for Span? And I was like, Easy cockroach, they've got us covered. >>Yeah, I know the guys and my friends. Yeah. So the question is why didn't you get into the first round of Cockroach? She said don't answer that. >>The question he did answer though was one of those age old arguments in our community about pronunciation. We used to argue about Quay, I always called it Key of course. And the co-founder obviously knows how it's pronounced, you know, it's the et cd argument, it's the co cuddl versus the control versus coo, CTL Quay from the co-founder. That is end of argument. You heard it here first >>And we're keeping it going with Osted. So awesome. A lot of people will say Zeed or, you know, so we, we just like to have a little ambiguity >>In the, you gotta have some semantic arguments, arm wrestling here. I mean, it keeps, it keeps everyone entertained, especially on the over the weekend. What's, what's next? You got obviously Kubernetes in there. Can you explain the relationship between Kubernetes, how you're handling Spice dv? What, what does the Kubernetes piece fit in and where, where is that going to be going? >>Yeah, great question. Our flagship product right now is a dedicated, and in a dedicated, what we're doing is we're spinning up a single tenant Kubernetes cluster. We're installing all of our operator suite, and then we're installing the application and running it in a single tenant fashion for our customers in the same region, in the same data center where they're running their applications to minimize latency. Because of this, as an authorization service, latency gets passed on directly to the end user. So everybody's trying to squeeze the latency down as far as they can. And our strategy is to just run these single tenant stacks for people with the minimal latency that we can and give them a VPC dedicated link very similar to what Cockroach does in their dedicated >>Product. And the distributed architecture makes that possible because it's lighter way, it's not as heavy. Is that one of the reasons? >>Yep. And Kubernetes really gives us sort of like a, a level playing field where we can say, we're going going to take the provider, the cloud providers Kubernetes offering, normalize it, lay down our operators, and then use that as the base for delivering >>Our application. You know, Jake, you made me think of something I wanted to bring up with other guests, but now since you're here, you're an expert, I wanna bring that up, but talk about Super Cloud. We, we coined that term, but it's kind of multi-cloud, is that having workloads on multiple clouds is hard. I mean there are, they are, there are workloads on, on clouds, but the complexity of one clouds, let's take aws, they got availability zones, they got regions, you got now data issues in each one being global, not that easy on one cloud, nevermind all clouds. Can you share your thoughts on how you see that progression? Because when you start getting, as its distributed database, a lot of good things might come up that could fit into solving the complexity of global workloads. Could you share your thoughts on or scoping that problem space of, of geography? Yeah, because you mentioned latency, like that's huge. What are some of the other challenges that other people have with mobile? >>Yeah, absolutely. When you have a service like ours where the data is small, but very critical, you can get a vendor like Cockroach to step in and to fill that gap and to give you that globally distributed database that you can call into and retrieve the data. I think the trickier issues come up when you have larger data, you have huge binary blobs. So back when we were doing Quay, we wanted to be a global service as well, but we had, you know, terabytes, petabytes of data that we were like, how do we get this replicated everywhere and not go broke? Yeah. So I think those are kind of the interesting issues moving forward is what do you do with like those huge data lakes, the huge amount of data, but for the, the smaller bits, like the things that we can keep in a relational database. Yeah, we're, we're happy that that's quickly becoming a solved >>Problem. And by the way, that that data problem also is compounded when the architecture goes to the edge. >>Totally. >>I mean this is a big issue. >>Exactly. Yeah. Edge is something that we're thinking a lot about too. Yeah, we're lucky that right now the applications that are consuming us are in a data center already. But as they start to move to the edge, we're going to have to move to the edge with them. And it's a story that we're gonna have to figure out. >>All right, so you're a customer cockroach, what's the testimonial if I put you on the spot, say, hey, what's it like working with these guys? You know, what, what's the, what's the, you know, the founders, so you know, you give a good description, little biased, but we'll, we'll we'll hold you on it. >>Yeah. Working with Cockroach has been great. We've had a couple things that we've run into along the way and we've gotten great support from our account managers. They've brought in the right technical expertise when we need it. Cuz what we're doing with Cockroach is not you, you couldn't do it on Postgres, right? So it's not just a simple rip and replace for us, we're using all of the features of Cockroach, right? We're doing as of system time queries, we're doing global replication. We're, you know, we're, we're consuming it all. And so we do need help from them sometimes and they've been great. Yeah. >>And that's natural as they grow their service. I mean the world's changing. >>Well I think one of the important points that you mentioned with multi-cloud, we want you to have the choice. You know, you can run it in in clouds, you can run it hybrid, you can run it OnPrem, you can do whatever you want and it's just, it's one application that you can run in these different data centers. And so really it's up to you how do you want to build your infrastructure? >>And one of the things we've been talking about, the super cloud concept that we've been issue getting a lot of contrary, but, but people are leaning into it is that it's the refactoring and taking advantage of the services. Like what you mentioned about cockroach. People are doing that now on cloud going the lift and shift market kind of had it time now it's like hey, I can start taking advantage of these higher level services or capability of someone else's stack and refactoring it. So I think that's a dynamic that I'm seeing a lot more of. And it sounds like it's working out great in this situation. >>I just came from a talk and I asked them, you know, what don't you wanna put in the cloud and what don't you wanna run in Kubernetes or on containers and good Yeah. And the customers that I was on stage with, one of the guys made a joke and he said I would put my dog in a container room. I could, he was like in the category, which is his right, which he is in the category of like, I'll put everything in containers and these are, you know, including like mis critical apps, heritage apps, since they don't wanna see legacy anymore. Heritage apps, these are huge enterprises and they wanna put everything in the cloud. Everything >>You so want your dog that gets stuck on the airplane when it's on the tarmac. >>Oh >>God, that's, she was the, don't take that analogy. Literally don't think about that. Well that's, >>That's let's not containerize. >>There's always supply chain concern. >>It. So I mean going macro and especially given where we are cncf, it's all about open source. Do y'all think that open source builds a better future? >>Yeah and a better past. I mean this is, so much of this software is founded on open source. I, we wouldn't be here really. I've been in open source community for many, many years so I wouldn't say I'm biased. I would say this is how we build software. I came from like in a high school we're all like, oh let's build a really cool application. Oh you know what? I built this cuz I needed it, but maybe somebody else needs it too. And you put it out there and that is the ethos of Silicon Valley, right? That's where we grew up. So I've always had that mindset, you know, and social coding and why I have three people, right? Working on the same thing when one person you could share it's so inefficient. All of that. Yeah. So I think it's great that people work on what they're really good at. You know, we all, now you need some standardization, you need some kind of control around this whole thing. Sometimes some foundations to, you know, herd the cats. Yeah. But it's, it's great. Which is why I'm a c CF ambassador and I spend a lot of time, you know, in my free time talking about open source. Yeah, yeah. >>It's clear how passionate you are about it. Jake, >>This is my second company that we founded now and I don't think either of them could have existed without the base of open source, right? Like when you look at I have this cool idea for an app or a company and I want to go try it out, the last thing I want to do is go and negotiate with a vendor to get like the core data component. Yeah. To even be able to get to the >>Prototypes. NK too, by the way. Yeah. >>Hey >>Nk >>Or hire, you know, a bunch of PhDs to go and build that core component for me. So yeah, I mean nobody can argue that >>It truly is, I gotta say a best time if you're a developer right now, it's awesome to be a developer right now. It's only gonna get better. As we were riff from the last session about productivity, we believe that if you follow the digital transformation to its conclusion, developers and it aren't a department serving the business, they are the business. And that means they're running the show, which means that now their entire workflow is gonna change. It's gonna be have to be leveraging services partnering. So yeah, open source just fills that. So the more code coming up, it's just no doubt in our mind that that's go, that's happening and will accelerate. So yeah, >>You know, no one company is gonna be able to compete with a community. 50,000 users contributing versus you riding it yourself in your garage with >>Your dogs. Well it's people driven too. It's humans not container. It's humans working together. And here you'll see, I won't say horse training, that's a bad term, but like as projects start to get traction, hey, why don't we come together as, as the world starts to settle and the projects have traction, you start to see visibility into use cases, functionality. Some projects might not be, they have to kind of see more kind >>Of, not every feature is gonna be development. Oh. So I mean, you know, this is why you connect with truly brilliant people who can architect and distribute sequel database. Like who thought of that? It's amazing. It's as, as our friend >>You say, Well let me ask you a question before we wrap up, both by time, what is the secret of Kubernetes success? What made Kubernetes specifically successful? Was it timing? Was it the, the unambitious nature of it, the unification of it? Was it, what was the reason why is Kubernetes successful, right? And why nothing else? >>Well, you know what I'm gonna say? So I'm gonna let Dave >>First don't Jake, you go first. >>Oh boy. If we look at what was happening when Kubernetes first came out, it was, Mesosphere was kind of like the, the big player in the space. I think Kubernetes really, it had the backing from the right companies. It had the, you know, it had the credibility, it was sort of loosely based on Borg, but with the story of like, we've fixed everything that was broken in Borg. Yeah. And it's better now. Yeah. So I think it was just kind and, and obviously people were looking for a solution to this problem as they were going through their containerization journey. And I, yeah, I think it was just right >>Place, the timing consensus of hey, if we just let this happen, something good might come together for everybody. That's the way I felt. I >>Think it was right place, right time, right solution. And then it just kind of exploded when we were at Cores. Alex Povi, our ceo, he heard about Kubernetes and he was like, you know, we, we had a thing called Fleet D or we had a tool called Fleet. And he's like, Nope, we're all in on Kubernetes now. And that was an amazing Yeah, >>I remember that interview. >>I, amazing decision. >>Yeah, >>It's clear we can feel the shift. It's something that's come up a lot this week is is the commitment. Everybody's all in. People are ready for their transformation and Kubernetes is definitely gonna be the orchestrator that we're >>Leveraging. Yeah. And it's an amazing community. But it was, we got lucky that the, the foundational technology, I mean, you know, coming out of Google based on Go conferences, based on Go, it's no to coincidence that this sort of nature of, you know, pods horizontally, scalable, it's all fits together. I does make sense. Yeah. I mean, no offense to Python and some of the other technologies that were built in other languages, but Go is an awesome language. It's so, so innovative. Innovative things you could do with it. >>Awesome. Oh definitely. Jake, I'm very curious since we learned on the way and you are a Detroit native? >>I am. Yep. I grew up in the in Warren, which is just a suburb right outside of Detroit. >>So what does it mean to you as a Michigan born bloke to be here, see your entire community invade? >>It is, I grew up coming to the Detroit Auto Show in this very room >>That brought me to Detroit the first time. Love n a I a s. Been there with our friends at Ford just behind us. >>And it's just so interesting to me to see the accumulation, the accumulation of tech coming to Detroit cuz it's really not something that historically has been a huge presence. And I just love it. I love to see the activity out on the streets. I love to see all the restaurants and coffee shops full of people. Just, I might tear up. >>Well, I was wondering if it would give you a little bit of that hometown pride and also the joy of bringing your community together. I mean, this is merging your two probably most core communities. Yeah, >>Yeah. Your >>Youth and your, and your career. It doesn't get more personal than that really. Right. >>It's just been, it's been really exciting to see the energy. >>Well thanks for going on the queue. Thanks for sharing. Appreciate it. Thanks >>For having us. Yeah, thank you both so much. Lisa, you were a joy of ball of energy right when you walked up. Jake, what a compelling story. Really appreciate you sharing it with us. John, thanks for the banter and the fabulous questions. I'm >>Glad I could help out. >>Yeah, you do. A lot more than help out sweetheart. And to all of you watching the Cube today, thank you so much for joining us live from Detroit, the Cube Studios. My name is Savannah Peterson and we'll see you for our event wrap up next.

>>From around the globe. It's the cube with digital coverage of IBM. Think 20, 21 brought to you by IBM, >>Everybody welcome back to IBM. Think 2021. My name is Dave Vellante and you're watching the cubes continuous coverage of this event. We go out to the events, we extract the signal from the noise, but doing that virtually for the better part of a 14 months. Now we're going to get deeper into application modernization. Marie ASHRAE is here. She's the director of marketing at mainline information systems and David burrows. Burrows is an account executive at mainline folks. Welcome to the cube. Great to have you on today. >>Thank you. Nice to be here >>To start with with mainline. Uh, people might not be familiar with, with mainline, but you've transformed over the past five years. I wonder if you could describe that for our audience? >>Yes, we have. Indeed. We have, um, mainline, um, you know, it's a 30 plus year company and, um, and for 30 odd years we had really been focused a lot in hardware, right? Hardware reselling. That's what the market needed. That's what we did a lot of. But then in the past, I would say five to eight years, maybe even 10 years, we started on this transformation project, um, for the business where we started transforming ourselves into really systems integrators versus just hardware reseller. So now we can go to a client and we can say, Hey, now what are you struggling with? Right? What are your business challenges? And then from there, we can integrate a solution that might be hardware. It might be software, it might be some services, it could be managed services. It could be staffing services, um, could be a number of different things and put all that together and then deliver a complete solution that helps them with their, their business requirements. Okay, >>David, that, that must've been an interesting transition because what Marie just described is it used to be every opportunity was a nail and whatever box you were selling was the hammer. And, and that, that has changed dramatically. Of course. So you, you, I wonder what that discussion was like with, with, with clients. You must have heard that early on and said, Oh, this cloud thing is happening. The world is changing. We've got to change too. I wonder if you could chime in on that transformation. >>Yes. That's our, uh, as our clients have been changing, what we've been doing is, uh, you know, making sure that we fully understand what's available not only in the marketplace, but the competition and what, what each industry segment, for example, baking versus insurance versus a utility maybe facing, uh, during this this time. And so, you know, being able to transform as a, as an accounting dedicated, we've been able to, uh, indicate and so provide solutions as Marie indicated. Um, the large focus over the last five years has been networking and security as we move, uh, more compute to the edge, close to the edge. Security has been predominant. Uh, and so, you know, hardware is really almost commoditized through and through and with the exception of, you know, IBM, Z and, and power. Uh, and so, you know, we've had to really, uh, sellers, you know, focus on what customers are dealing with and how they transition. Uh, and as we, uh, you know, through COVID, it's actually been a bigger challenge, a bigger focus on security. And I think we'll talk about that a little bit later in more detail >>Let's, let's, let's do that now. So, so Marie, maybe at a high level, you could talk about those challenges that your clients are facing. And then we can sort of double click on how that was exacerbated by, by COVID. And I'm really interested in your perspectives on sort of the post isolation economy and how those challenges are going to shift, but, but maybe, maybe kick us off at the high level if you could. >>Sure. So, um, so, you know, people, companies were moving toward, um, uh, th the whole digital transformation, right? Probably for the past three to four years, we started seeing more and more that's constantly, everybody sees those buzz words all the time. Um, so clients were shifting in that direction and we were shifting to try to satisfy them with their needs with those solutions, but then came COVID and all of a sudden, right. What people were, were planning on doing for the next, let's say five years. I mean, most of the iOS were saying, yeah, we're going to get there in five years. Well, that had to happen. Right. It had to have brakes went on and it had to happen instantaneously. So that put a big change in focus, a big change in direction for not only our clients. Right. But for our own folks, folks like David, who are trying to service these clients with having to bring them these solutions that we're going to solve their digital business needs, um, today and not five years from now. >>Yeah. So David let's, let's talk about that. I mean, what Marie just described, I call it the forced March to digital, because as Maria, as you were saying, people were on a digital transformation, but there was a little bit of complacency and okay, we'll get there. We're really busy doing some other stuff. And then all of a sudden you've probably seen the meme of the COVID wrecking ball coming, coming into the building, the office building and saying, you know, well, we're doing fine. And all of a sudden, boom, the forest COVID comes in. So, so, so, so how did that affect your clients and how did you respond? I mean, they're asking for VDI and get me some laptops, I need end point security. And so how did that affect the, the application modernization efforts and David, maybe you could comment on that. >>So I, I think for, for me, the biggest challenge was all business, the competition within business to survive COVID, uh, you know, they had to put on first thing was how do we get our, our customer, uh, supported correctly and how do we get our workers supportive, working at home? So the very first thing we did over the initial six months was most companies had to transform immediately within the first 30 to 90 days to allow their workforce to work from home. Uh, that happened throughout my, my customer base, uh, both in Southern California, uh, was customers really focused on, uh, how do we business process, how do we compete in this marketplace and get return on investment speed, you know, time to value or what we invest in these, uh, COVID times so that we can compete with other, uh, businesses that are trying to stay alive, uh, through this transition. And, and now, you know, we're seeing on, uh, on the backend, uh, you know, that time, the value in terms of investment is even more important because some businesses have been significantly impacted from not only cashflow, uh, but you know, certainly in terms of profitability during this time >>Makes sense. And so I'm read, so we were talking earlier about the, sort of the initial path to digital transformation, and I wonder if that's gotta be course corrected. I would think we were forced in to compress, you know, the digital reality, uh, and, and I guess in a way that's good. Uh, but in a way it was, we probably made a lot of mistakes. It was a bit of a Petri dish. So now as we begin to knock on exit COVID, you would think those, those imperatives, uh, adjust and they start to become aligned. What's your take on that, especially as it relates to application and infrastructure modernization. >>Um, so I would agree with that. I think that there's definitely has to be a little bit of a, of a real alignment happening. And I know recently I read that, um, 20, 21 is expected to be a very, um, large year in it spend because all of those, um, initiatives that CEOs and others were going after pre COVID kind of got put on hold, right. So they could then go focus on all of those digital needs that were needed, like, you know, the CDI, you know, work at home, all the security stuff for that. So I think we're going to see, I'm thinking, we're going to see a shift again now, and maybe businesses are going to go back and try to pick up where they were, uh, prior to COVID and now start working on more of really of the application modernization, um, initiatives that were in mind. And I know we wanted to talk about that as well, because David's been working on quite a bit of application modernization with, um, a few of his clients, um, as we're seeing again, businesses change. Um, and, and I don't know that all of that changes because of COVID. I think all of that change was for their competitiveness, um, to get there anyway. So I think that's going to start, as you said before, Dave, I think it's going to start now having to >>Kind of rethink, >>It reminds me of traffic on the David, if you've ever been to driving in, in London when it's slingshots, right. It's that's what's COVID was like Murray you're absolutely right. Last year it spend was down four to 5% this year. I mean, our prediction is going to be in the six to 7% range, which, which kind of aligns with where Gartner and IDC are based on our surveys. But, you know, back in, in April, like I think the 16th of April, it was a headline in the wall street journal that the China grew 18% GDP in the quarter. So it's very hard to predict, but, but it's coming back, you know, we, we can see that David and so, so spending is really gonna accelerate. There's probably some pent-up demand for that application modernization. Maybe it's been a little bit, uh, neglected as we've done, as Maria was saying. And you were saying the work from home. So maybe you could talk a little bit more about the modernization aspects and maybe I'm really interested in the things that you guys deliver in your portfolio with IBM. >>Sure. Uh, so what I have customers in multiple phases within this, uh, current digital transformation, their customer, uh, moving everything to next gen, uh, development, which is, uh, only containerized code, uh, being able to, you know, swiftly go through their development tests, uh, and, uh, hybrid cloud environments where they're, um, they haven't made an investment yet, but they're sampling what it might be like to, uh, change into that world. And then there are customers are still in the, uh, typical environment, uh, the traditional environment, and are looking at what the solutions, as far as packages are available for them moving forward. So they can kind of skip over, uh, any kind of development and being able to, uh, leverage, uh, what I call them next, gen development or next gen systems, uh, immediately, as you know, you asked, you know, what are the, what are the systems that are available? IBM's cloud pack, uh, solution set. It provides a portfolio of capabilities, uh, both in the application, suite, database, suite security. Uh, I have customers today leveraging that. Uh, and, and so that is one of the first pieces, uh, that, that customers I see who are on the leading edge, or are also kind of trailing, are looking at, uh, these cloud packs to be able to, uh, uh, go time to market and time to value, uh, quickly. >>Yeah. So when I look at your portfolio, I just sort of scan the web. Uh, David just mentioned Marie cloud pack. I mean, we're talking software here. You guys do have a lot of expertise in ZZ Linux power, you mentioned is not a commodity. And it's one of the few pieces of hardware that, and Z they're not a commodity storage. I would think business resiliency fits in there beyond disaster recovery, your red hat, we're talking, you know, things like open OpenShift and Ansible for automation. So these are, these are not your grandfather's main line. These are toolkits are a piece of, you know, parts of the tool bag that you bring to bear to focus on on client outcomes and solutions is, am I getting that right? >>Yes, absolutely. Absolutely. Um, and again, right, that goes back to the original opening comment about how we've transformed as a business, right. To become, uh, an integrator, um, putting all of these different pieces together. I mean, I know that, um, something that, that David recently had worked on, Oh my goodness. If you would have looked at the list of pieces of elements to that solution, um, it was really quite incredible between, um, open source stuff, you know, and a bunch of IBM stuff. Um, yes, it was some storage and yeah, there was some power, um, yes, there was red hat. Right. But then there was other stuff there was VMware. Um, there was, um, some things that, um, I can't even remember now all the names to all the components, but it was, it was a laundry list. Right. And so that's where though mainline stepped in and put the pieces together, uh, for the customer so that the customer then can get done what they needed to get done, which was, which was really solve their business problem, which was trying to become more competitive in their market space. >>Okay, David, so when Maria was sustained was basically, my takeaways is as a system integrator, you've got all these piece parts with these technologies, you've got virtualization, you've got automation, you've got containers and so forth. Uh, and yes, there's there's hardware, but there's this integration that has to occur. And your job is to abstract that complexity, that underlying complexity away so that the customers can focus on the outcome. Maybe you could talk about that and how you do that. >>Sure. I'll give you a good example of a recent customer that we work with who was, uh, basically, I mean, we consider an enterprise data platform that, that, uh, was going to rework their entire data warehouse into something that had governance surrounding it, uh, where they could validate all the data that was coming into their warehouse. And so we underpinned that, uh, with an infrastructure of power, uh, we're running, uh, obviously IBM, uh, uh, pack for data, uh, with DB two warehouse. Uh, we use a combination of that with, uh, Cloudera data flow through IBM, uh, with the streaming and, uh, the governance, uh, IBM governance catalog piece, which is, uh, lots of knowledge catalog. So, uh, we've been able to take not only what their base requirements were, but all the microservices that are packaged in with cloud pack, uh, all running on OpenShift, uh, which was a great acquisition that IBM did last year. And, uh, then, uh, they also required other microservices outside, uh, to support that environment and paint a picture for >>Us as to what the future looks like. Uh, it's, it's much different than the past 30 years, uh, and bring us home please >>Or so, um, I think the future for us is to continue to, um, to find all of the solutions, um, that will, that will help our customers, um, you know, get to their next steps. Right. And, and there's a lot, as you know, there's lots of solutions out there. There's lots of new companies that are popping up all the time. Um, you know, inherently, you know, mainline is an IBM partner. We've been an IBM partner for 30 plus years since our inception. And that's the base of our business is, is IBM. But, but there are other requirements that are needed by, by businesses, by our customers. And that's where we, we reach out and partner up. We probably have gone my goodness, 200 plus partnerships with various companies, various technology companies that we can then, um, lean on and pull in those ancillary solutions, um, to, to, to complete that, that solution for the customer. >>So I think we're going to continue going down that path. We're going to continue making sure that we're partnered with the, um, the, the leading technology companies. So we can build that IBM solution for our customer and, and bolt on the other pieces that are needed. Uh, we're going to continue to grow and enhance our services business because we've got quite a large services business, whether it's implementation services, uh, we do managed services. We have staffing services. I think you're going to see if we're still going to continue to, to grow that business, because that is a piece where companies, you know, they don't want to worry about running all of that stuff, right. They want to know that their system's going to be running 24 seven. And if there is a bump or a burp or something happens, Hey, they could pick up the phone, they can call mainline. We can help them get things corrected. So I think we're going to still see a lot of that going on as well, um, within our, our, our offerings. >>Excellent. Well, congratulations for making it through that. Not a whole lot, not, not every, uh, hardware seller reseller made it through and you guys transformed. It's a, it's an inspiring story. Maria, David, thanks so much for coming on the cube. Thank you. Thank you very much. You're really welcome. And thank you for watching everybody. This is Dave Volante in our continuous coverage and the cube of IBM think 20, 21. Keep it right there.

>> From around the globe, it's the cube, with digital coverage of IBM think 2021 brought to you by IBM. >> Hi everybody, Welcome back to IBM Think 2021. My name is Dave Vellante and you're watching the cubes continuous coverage of this event. We go out to the events, we extract the signal from the noise but doing that virtually for the better part of a 14 months now, we're going to get deeper into application modernization. Marie Ashway is here. She's the director of marketing at Mainline Information Systems and David burrows. Burrows is an account executive at Mainline folks. Welcome to the cube, great to have you on today. >> Thank you. Nice to be here. >> Marie, I want to start with, with Mainline. A lot of people might not be familiar with Mainline but you've transformed over the past five years. I wonder if you could describe that for our audience? >> Yes, we have, indeed we have, Mainline, you know is a 30 plus year company and, and for 30 odd years we had really been focused a lot in hardware, right? Hardware reselling. That's what the market needed. That's what we did a lot of. But then in the past I would say five to eight years, maybe even 10 years we started on this transformation project for the business where we started transforming ourselves into really systems integrators versus just hardware reseller. So now we can go to a client and we can say, Hey now what are you struggling with? Right? What are your business challenges? And then from there we can integrate a solution that might be hardware. It might be software, it might be some services it could be managed services. It could be staffing services could be a number of different things and put all that together and then deliver a complete solution that helps them with their, their business requirements. >> Well, David, that that must've been an interesting transition because what Marie just described as it used to be every opportunity was a nail and whatever box you were selling was the hammer. And that, that has changed dramatically. Of course. So you, you, I wonder what that discussion was like with, with, with clients. You must have heard that early on and said, Uh-Oh this cloud thing is happening. The world is changing. We've got to change too. I wonder if you could chime in on that transformation. >> Yes. That's our, as our clients have been changing what we've been doing is, you know, making sure that we fully understand what's available, not only in the marketplace, but the competition. What, what each industry segment, for example, banking versus insurance versus a utility maybe facing during this this time. And so, you know, being able to transform as a as an accounting dedicated, we've been able to indicate. And so provide solutions as Marie indicated, the large focus over the last five years has been networking and security. As we move more compute to the edge, close to the edge security has been predominant. And so, you know, hardware is really almost commoditized through and through and with the exception of, you know IBM, Z and, and power. And so, you know, we've had to really sellers, you know focus on what customers are dealing with and how they transition. And as we, you know, through COVID, it's actually been a bigger challenge, a bigger focus on security. And I think we'll talk about that a little bit later in more detail >> Let's, let's, let's do that now. So, so Marie, maybe at a high level, you could talk about those challenges that your clients are facing. And then we can sort of double click on how that was exacerbated by, by COVID. And I'm really interested in your perspectives on sort of the post isolation economy and how those challenges are going to shift, but, but maybe maybe kick us off at the high level if you could. >> Sure. So, so, you know, people, companies were moving toward the the whole digital transformation, right? Probably for the past three to four years we started seeing more and more that constantly everybody sees those buzzwords all the time. So clients were shifting in that direction and we were shifting to try to satisfy them with their needs with those solutions but then came COVID and all of a sudden, right. What people were, were planning on doing for the next, let's say five years. I mean, most of the CEO's were saying, yeah we're going to get there in five years. Well, that had to happen. Right. It had to have brakes went on and it had to happen instantaneously. So that put a big change in focus a big change in direction for not only our clients. Right. But for our own folks, folks like David who are trying to service these clients with having to bring them these solutions that we're going to solve their digital business needs today and not five years from now. >> Yeah. So David let's, let's talk about that. I mean, what Marie just described I call it the forced march to digital, because as Marie as you were saying, people were on a digital transformation but there was a little bit of complacency and okay, we'll get there. We're really busy doing some other stuff. And then all of a sudden you've probably seen the meme of the COVID wrecking ball coming, coming into the building the office building and saying, you know, you know, well we're doing fine and all of a sudden, boom the forced COVID comes in. So, so, so so how did that affect your clients and how did you respond? I mean, they're asking for VDI and get me some laptops, I need end point security. And so how did that affect the the application modernization efforts and David maybe you could comment on that. >> So I, I think for, for me, the biggest challenge was all business, the competition within business to survive COVID, you know, they had to put on first thing was how do we get our, our customer supported correctly? And how do we get our workers supported working at home? So the very first thing we did over the initial six months was most companies had to transform immediately within the first 30 to 90 days to allow their workforce to work from home. That happened throughout my, my customer base, both in Southern California, was customers really focused on how do we do business process? How do we compete in this marketplace and get return on investment speed, you know, time to value or what we invest in these COVID times so that we can compete with other businesses that are trying to stay alive through this transition. And, and now, you know, we're seeing on the, on the back end you know, that time, the value in terms of investment is even more important because some businesses have been significantly impacted from knowing cashflow, but you know, certainly in terms of profitability during this time. >> Makes sense. And so, Marie, so we were talking earlier about the sort of the initial path to digital transformation. And I wonder if that's got to be course corrected. I would think we were forced in to compress, you know the digital reality and, and I guess in a way that's good but in a way it was, we probably made a lot of mistakes. It was a bit of a Petri dish. So now as we begin to ,knock on, exit COVID you would think those those imperatives adjust and they start to become aligned. What's your take on that, especially as it relates to application and infrastructure modernization. >> So I would agree with that. I think that there's definitely has to be a little bit of a of a realignment happening. And I know recently I read that 2021 is expected to be a very large year in IT spend because all of those initiatives that CEOs and others were going after pre COVID kind of got put on hold, right. So they could then go focus on all of those digital means that were needed. Like, you know, the CDI, you know, work at home all the security stuff for that. So I think we're going to see, I'm thinking, we're going to see a shift again now, and maybe businesses are going to go back and try to pick up where they were prior to COVID and now start working on more of really of the application modernization initiatives that were in mind. And I know we wanted to talk about that as well because David's been working on quite a bit of application modernization with a few of his clients as we're seeing again, businesses change. And, and I don't know that all of that changes because of COVID. I think all of that change was for their competitiveness, to get there anyway. So I think that's going to start, as you said before, David I think it's going to start now having to kind of rethink up >> It reminds me of traffic on the M four David have you ever been to driving in in London when it's slingshots? Right? It's that's what's COVID was like Marie, you're absolutely right. Last year IT spend was down 4 to 5% this year. I mean, our prediction is it's going to be in the 6 to 7% range, which, which, which kind of aligns with where Gartner and IDC are based on our surveys. But, you know, back in, in April like I think the 16th of April it was a headline of wall street journal that the China grew 18% GDP in the quarter. So it's very hard to predict, but, but it's coming back you know, we can see that David and so so spending is really going to accelerate. There's probably some pent-up demand for that application modernization. Maybe it's been a little bit neglected as we've done as Maria was saying. And you were saying that work from home. So maybe you could talk a little bit more about the modernization aspects and maybe I'm really interested in the things that you guys deliver in your portfolio with IBM. >> Sure. So what I have customers in multiple phases within this current digital transformation there are customers moving everything to the next gen development which is a fully containerized code. Being able to, you know swiftly go through their development tests and hybrid cloud environments where they're they haven't made an investment yet but they're sampling what it might be like to change into that world. And then there are customers are still in the typical environment, the traditional environment and are looking at what the solutions as far as packages are available for them moving forward. So they can kind of skip over any kind of development and being able to leverage what I call next gen development or next gen systems immediately as you know, you ask, you know, what are the what are the systems that are available? IBM's cloud pack solution set. It provides a portfolio of capabilities both in the application suite, database suite, security. I have customers today leveraging that. And, and so that is one of the first pieces that that customers I see who are on the leading edge or are also kind of trailing, are looking at these cloud bags to be able to go time to market and time to value quickly. >> Yeah. So when I look at your portfolio I just sort of scan the web. David just mentioned Marie, cloud pack. I mean, we're talking software here. You guys do have a lot of expertise in Z, Z Linux, Power. You mentioned is not a commodity. And it's one of the few pieces of hardware that and Z they're not a commodity. Storage, I would think business resiliency fits in there beyond disaster recovery. You Red Hat, we're talking, you know, things like open open shift and Ansible for automation. So these are, these are not your grandfather's main line. These are toolkits are a piece of, you know, parts of the tool bag that you bring to bear to focus on on client outcomes and solutions is am I getting that right? >> Yes, absolutely. Absolutely. And again, right, that goes back to the original opening comment about how we've transformed as a business, right. To become an integrator putting all of these different pieces together. I mean, I know that something that that David recently had worked on, Oh my goodness. If you would have looked at the list of pieces of elements to that solution, it was really quite incredible between open source stuff, you know and a bunch of IBM stuff. Yes. It was some storage and yeah, there was some power. Yes. There was Red Hat. Right. But then there was other stuff, there was VMware there was some things that I can't even remember now all the names to all the components, but it was it was a laundry list. Right. And so that's where though Mainline stepped in and put the pieces together for the customer so that the customer then can get done what they needed to get done, which was which was really solve their business problem which was trying to become more competitive in their market space. >> Okay, David, so when Marie was just staying was basically my takeaway is, is this a system integrator? You've got all these piece parts with these technologies you've got virtualization, you've got automation you've got containers and so forth. And yes, there's there's hardware but there's this integration that has to occur. And your job is to abstract that complexity that underlying complexity away so that the customers can focus on the outcome. Maybe you could talk about that and how you do that. >> Sure. I'll, I'll give you a good example of a recent customer that we work with, who was basically implying, we consider an enterprise data platform that, that was going to rework their entire data warehouse into something that had governance surrounding it where they could validate all the data that was coming into their warehouse. And so we underpinned that with an infrastructure of power. We're running, obviously IBM pack for data with DB two warehouse. We use a combination of that with five-year data flow through IBM with the streaming and the governance IBM governance catalog piece, which is lots of knowledge catalog. So we've been able to take not only what their base requirements were, but all the microservices that are packaged in with cloud pack, all running on open shift which was a great acquisition that IBM did last year. And then they also required other microservices outside to support that environment >> Paint a picture for us as to what the future looks like. It's, it's much different than the past 30 years and bring us home, please. >> Sure. So I think the future for us is to continue to to find all of the solutions that will that will help our customers, you know get to their next steps. Right. And, and there's a lot, as you know did this lots of solutions out there. There's lots of new companies that are popping up all the time. You know, inherently, you know, Mainline is an IBM partner. We've been an IBM partner for 30 plus years since our inception. And that's the base of our business is, is IBM. But, but there are other requirements that are needed by by businesses, by our customers. And that's where we, we reach out and partner up. We probably have gone my goodness 200 plus partnerships with various companies various technology companies that we can then lean on and pull in those ancillary solutions to, to to complete that, that solution for the customer. So I think we're going to continue going down that path. We're going to continue making sure that we're partnered with the, the, the leading technology companies. So we can build that IBM solution for our customer and and bolt on the other pieces that are needed. We're going to continue to grow and enhance our services business because we've got quite a large services business whether it's implementation services, we do manage services we have staffing services. I think you're going to see we're still going to continue to, to grow that business because that is a piece where companies, you know they don't want to worry about running all of that stuff, right. They want to know that their system's going to be running 24 seven. And if there is a bump or a burp or something happens, Hey they could pick up the phone, they can call Mainline. We can help them get things corrected. So I think we're going to still see a lot of that going on as well within our, our, our offerings. >> Excellent. Well, congratulations for making it through that. Not a whole lot, not not every hardware seller reseller made it through and you guys transformed. It's a, it's an inspiring story. Marie, David, thanks so much for coming on the cube. >> Thank you. >> Thank you very much. >> You're really welcome. And thank you for watching everybody. This is Dave Volante in our continuous coverage and the cube of IBM think 2021. Keep it right there.

>> Announcer: From around the globe, it's theCUBE with digital coverage of AWS re:Invent 2020, sponsored by Intel, AWS and our community partners. >> You're watching continued coverage of AWS re:Invent 2020. I'm sure you're joining just a couple of hundred thousand of your closest friends and family on the web as we engage this AWS builder community in a very different way this year. I'm super excited to have one, for the first time Flexera on theCUBE program, I'm Keith Townsend @CTOAdvisor on Twitter and I'm joined by the CEO of Flexera, Jim Ryan. Jim, welcome to the show. >> Thanks for having us Keith. >> And Marie Godfrey, Senior Vice President of Product at Flexera. >> Thanks. It's good to be here. >> Welcome to the show. So, first off, I think most of the industry knows Flexera from the famous survey you guys do every year. Help us understand, what's the purpose of the survey and the intent of it? >> I think the purpose of the survey is to continue to provide the pulse of the market to our customers and the market at large. This is not a revelation to say that cloud, hybrid cloud, multi-cloud is an ever-changing fast, fast moving target in the industry and we find that by pulsing our customers and pulsing the market and then in return, giving people a broader sense as to what's going on, how they view the current top three challenges that they're facing, allows people to just stay relevant and stay current without having to do so much heavy lifting themselves. >> So, talk to me about the other part that's not as famous. Marie, the product, what's the primary goal of Flexera? >> So, to take off from what Jim said, the state of the cloud report that we issue every year is just one of many that we do research on and we published and Flexera hasn't always been known as a cloud management tool or a cloud provider of optimization solutions for the cloud. We have grown up and our legacy is very much on software asset management. So, over the course of both organic and inorganic means, we find ourselves in this great position now to be able to talk to not only our core strengths as an organization and as a company, but also what we do to help our customers optimize their cloud cost. >> So, one of the interesting outputs or data points from the report is this 70/30 split. I've seen it as 80/20, 70/30, more or less the same ideal concept that we spend 30% of our time basically on these innovative projects but 70% of our time basically on traditional IT operations. How does that impact your team's view of the market? >> Well, I think it profoundly impacts our view. You can call it the elephant in the room or you can call it the immovable object. The fact of the matter remains is that although a lot of the focus, attention and an ever increasing share of everybody's budget is being focused and centered on the cloud, if you're a CIO or somebody working in the CIO's organization, what you've got to realize and focus on is that 70% of your applications in your spending in your tech stack, are still on premise and VMs and other things that simply cannot be ignored. So, our overarching value proposition above and beyond remaining relevant in the cloud and publishing the state of the cloud is we focus on giving CIOs and IT teams the insight as to what's going on in your on-prem estate and if we do our jobs properly with our technology stack, it's identifying overuse or cost optimization opportunities, so, you can take dollars from your legacy stack and throw it over to invest in more innovative things that's going to move the needle for your business. >> So, that's a pretty interesting, I think value pop especially where the public cloud show help me understand kind of the overall challenge when we're thinking about public cloud, where typically less than 30% of our resources are probably in the public cloud. For most people watching this interview and the majority are on the private cloud, how does like Flexera help me to extract the value of both environments? >> Well, that's by robbing Peter to pay Paul, right? So, for everybody listening in here, lean in and listen. The biggest problem that we have when we're talking with our customers is that the cloud people aren't talking to the legacy on-prem asset management people and like Americans or everybody else, we got to just get together and talk to one another so, there's money and budget dollars to be extracted on the legacy on-prem last glamorous stuff of the house here and I say with great certainty not knowing all of the situations with everybody that's watching this, that I'm sure that you fight for single Dollar, Euro, Pound, Yen, et cetera, et cetera that you want to spend on your cloud initiatives. By collaborating with your brethren and your sisters over on the other side of the aisle and by looking at what's going on on the on-prem estate here, you can identify opportunities where you can reallocate budget dollars. >> So Marie, you guys have this term that I've not seen before, Technology Value Optimization or TVO, explain that to me. >> So, TVO is just the latest evolution in terms of how we think about our portfolio and our place in this ecosystem. That includes not just your traditional infrastructure management but this bridging and this realization of value when it comes to how we help our customers extract the value from what we do really, really well which is all around discovery of IT assets. It's around knowing my entitlements, it's around understanding my usage and now of course we brought cloud assets into the picture and helping our customers not only understand and see into those cloud assets but really look at how do I right size? How do I reclaim dollars? How do I avoid failed audits and really understand my usage patterns and what it is I need to do to enact and move toward that digital transformation that Jim referred to? So, at the end of the day, how we think about technology value optimization is that critical factor which is all around understanding the return on the investment and how to better understand and monetize the value for our customers in terms of what they have today and where they need to go. >> Ken, I wanted you to shed some light in what we consider or what we should now consider assets in this new era of cloud, and that your traditional products that how could others understand the AS or the asset either is a server or a virtual machine on that server networks switch etcetera but as I look at SaaS and past platforms and infrastructure as a service platform, what is the asset in this new world? >> By my definition, an asset is anything that your company spend money on and you need to get a return on it. So, 10 years ago, if we were having this conversation, an asset would have been a desktop, a router, a server, or maybe it would be a multi-core server and as things started to get a little bit more complicated, we added virtual machines. So, assets weren't just physical devices, they were virtual devices where we really cut our teeth and made a name for ourselves at Flexera was in software license optimization or software asset management, which is you take all of your physical assets and then you throw software applications from IBM, Oracle SAP, Microsoft and you put those two together and what you have are licensable events or financial exposure, because it's not just as simple as buying a database from Oracle, Oracle is going to want to know how many cores you're running on the server, and all of those different combinations in a Rubik's cube of complexity throw off licensable or financial events and while I'd love to tell everybody that the cloud and hybrid cloud and multi-cloud is making it easier, it's actually making it more sophisticated and more complicated to try and get your head around it because now you have containers and just when we thought we had figured out VMs and what assets and things are running in VMs, you've got containers that are going up and down and trying to find out what assets are in containers across a hybrid multicloud environment says the latest instantiation of chasing your tail here in the business. >> And then help me think through, or at least visualize this concept of entitlements when it comes to the cloud era. When I had on premises assets, I could go and look at my Oracle license and maybe figure out what I was entitled to but now when I, especially when I think of multicloud multi-service and even hybrid where Microsoft gives me credits or on premises services versus off-prem services, help me understand how I should be looking at that and how Flexera helps. >> I think you've got to be looking at it at closely and you can't look at it in isolation. So what you can't do is look at what you've got spun up in an Azure environment and AWS or Google cloud environment, because you're only going to negotiate one agreement with Microsoft most likely. You're only going to negotiate one ELA with IBM or Oracle, or fill in the blank and you know what, Oracle's not going to care what you're running in just cloud if they come and audit you. They are going to perform an audit, and they're going to want to know what you're running in in an on-prem world in VMs, on your data center and your desktop, and then they're going to want you to bring to full account what you're running in your cloud environments as well. So the way Flexera helps you is that we can discover, and we can give you an unprecedented visibility into what's running throughout your IT assets estate, whether it's on-prem, on a desktop, in a data center, on a SaaS application and an infrastructure platform as a service, pull it back and normalize it and compare that to what you've actually signed with all of your suppliers and when we do our job right, our customers run our algorithms across what you're entitled to use and what you're actually using, and what we find is that there's anywhere from 30 zero to 30% of overused in spend in ways. >> Keith, I just want to add example of where I saw this in real time with one of our solution engineers this about two weeks ago, where he was demonstrating the power of what we deliver across entitlements and usage and understanding where a potential wasted spend is and the customer was really focused on Oracle, and making sure that the Oracle negotiation coming up was going to be one where the customer felt like they were in a position of strengths and really understood what entitlements and usage were but when we showed them that Oracle was one piece of a bigger puzzle and that their cloud spend and AWS spend, and even their spend with some of their largest SaaS applications was actually much smaller than the whole, it really showed the customer the power of looking at these assets back to your question around assets and how do we think about them in a way that compares them to one another so the customer gets a full point of view. >> It's very difficult to get an Apple's and Apple's comparison with hybrid versus public and it's no longer just, I don't know if it was ever simple, but it's just more complex these days. Last question, as you look at the past few years, and I go to the Flexera website and look at your product portfolio, talk to me about the relationship between your customer in the industry and how that's changed and how customers consume Flexera as a product. >> I think over the years, our customers like the market has shifted to our SaaS and cloud offering we back in the day we used to have perpetual licenses and we were focusing on an on-prem scenario only, and our customers rightfully so have become far more demanding much like the market has and they now expect things to be delivered in real time with an agile mindset on a SaaS or cloud native basis and with that becomes a much, much higher expectation in terms of customer success and service that they get, because they're on a subscription basis, they can cancel at any time, just like we can do with our cable service provider. So we've really had to invest a lot, not just in R&D and making sure that our technology delivers outcomes, but in the way that we work with and service our customers. They're far more demanding than that they ever have and I wouldn't want it any other way and we think that our strategic imperatives is just keeping up with that in their high demands and expectations in the future. >> Well, I really appreciate you two taking out the time out of your busy schedules, both of you on the East coast, I'm in a Midwest, couple of hundred thousand people tuning into AWS re:Invent 2020 virtual learning to tackle a lot of these complex problems. The pandemic, the new reality of the market has forced us to address implementing and managing enterprise IT in a completely different way. This conference is a great example of that. We thank our friends at Flexera for sponsoring this interview. You want to learn more about theCUBE's coverage? Subscribe to the YouTube channel. Plenty of content with me and my fellow co-host this year coming out of AWS re:Invent 2020 talk to you next installment of theCUBE. (upbeat music)

>>from New York. It's the Q covering Escape. 19. >>Welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape, where in New York City was staying in New York, were not escaping from New York were in New York. It's all about multi Cloud, and we're here. Lisa Marie Nancy, developer advocate for Port Works, and Eric Conn, vice president of Products Works. Welcome back. Q. >>Thank you, John. Good to see >>you guys. So, um, whenever the first inaugural of anything, we want to get into it and find out why. Multi clouds certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data of the two kind of consistent themes. What shared guys take Eric, What's your take on this multi cloud trend? Yeah, >>I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had ah, customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications. Going forward, >>you know, you have almost two camps in the world. Want to get your thoughts on this guy's Because, like you have cloud native and people that are cloud native, they love it. They born the cloud that get it. Everything's cracking along. The developers air on Micro Service's They're agile train with their own micro service's. Then you got the hybrid I t. Trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, I see multi cloud as kind of a combination of old legacy Data center types of I t with cloud native, not just ops and dead. But how about like trying to build developer teams inside enterprises? This seems to be a big trend, and multi club fits into that because now the reality is that I got azure. I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture? What are you trying to do? What's the workloads behavior outcome look like? What's the work flows? So there's a whole nother set of conversations that happened. >>I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plan perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the definition of cod you have to incorporate, just like with hybrid I t the legacy applications. And we saw that you throughout the years those crucial applications, as we call them People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot too. So I think when we talk about multi cloud, we also talk about what What is in your legacy? What is it? Yeah, I >>like I mean I use legacy. I think it's a great word because I think it really puts nail in the coffin of that old way because remember, if you think about some of the large enterprises, these legacy applications, they've been optimized for hardware and optimize their full stack. They've been build up from the ground up, so they're cool. They're running stuff, but it doesn't always translate to see a new platform designed point. So how do you mean Containers is great fit for their Cooper names. Obviously, you know is the answer. We you guys see that as well, but okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly, on the security side, we're seeing everyone running away from buying tools to thinking about platforms. What's the conversation like on the cloud side >>way? Did a talk are multiplied for real talk at Barcelona? Q. Khan put your X three on Sudden. Andrew named it for reals of Izzy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi cloud? It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of communities. I don't know if you know Eric was the first product manager for Pernetti. Hey, he's too shy to say it on Dhe. So yeah, and we think, you know, and criminal justice to be the answer to making all They caught a reality right now. >>Well, I want to get back into G, K, E and Cooper. Very notable historic moment. So congratulations, But to your point about multi cloud, it's interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I kill my exchange server, I'm essentially running azure by their definition. If I'm building it, stack on AWS. I'm a native, this customer. Let's just say I want to do some tensorflow or play with big table or spanner on Google. Now >>we have three >>clouds now they're not. So they have work clothes, specific objectives. I am totally no problem. I see that like for the progressive customers, some legacy be to be people who like maybe they put their toe in the cloud. But anyone doing meaningful cloud probably has multiple clouds. But that's workload driven when you get into tying them together and is interesting. And I think that's where I think you guys have a great opportunity in this community because if open source convene the gateway to minimize the lock in and when I say lock and I mean like locking them propriety respect if his value their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked >>in at the infrastructure level. So, like you said, if >>there's value at the higher levels of Stack, and it helps me do my business faster. That's an okay thing to exchange, but it is just locked in and it's not doing anything. They're that's not equal exchange, right, So there's definitely a move from infrastructure up the platform. So locking in >>infrastructure is what people are trying to move away from. >>From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting of how legacy will also start to running containers. And I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how V EMS can start >>to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point >>now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy, and that sourcing strategy is more regulation type o. R. In terms of not being locked in. And that's where I'm saying it's all those things. I'd >>love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of okay, standardization, kubernetes nights, containers, everyone knows what that is. But then you start talking about a P I gateways, for instance, right? So if I'm a car and I have five different gateways on my device, I ot devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something like that. So I'm starting. Envision them? I just made that news case up, but my point is is that you need some standards. So on the a p I side was seeing some trends there. One saying, Okay, here's my stuff. I'll just pass parameters with FBI State and stateless are two dynamics. What do you make of that? What, What? What has to happen next to get to that next level of happiness and goodness? Because Bernays, who's got it, got it there, >>right? I feel that next level. I feel like in Lisa, Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from the operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent. They automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. That's like low priority loving fruitcake manual stuff >>and communities was really good at the local food. That's a really use case that you brought up. Really. People were looking at the data now and when you're talking about persistent mean kun is his great for stateless, but for state full really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking to that >>state problem. Talk about your company. I want to go back to to, um, Google Days. Um, many war stories around kubernetes will have the same fate as map reduce. Yeah, the debates internally at Google. What do we do with it? You guys made the good call. Congratulations on doing that. What was it like to be early on? Because you already had large scale. You were already had. Borg already had all these things in place. Um, it wasn't like there was what was, >>Well, a few things l say one is It was intense, right? It was intense in the sense that amazing amount of intelligence amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers or package we're still looking at how infrastructure kit run and a lot of service is were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different. Today >>I will come back in the studio Palop of that. I gotta ask you now that you're outside. Google was a culture shock. Oh my God! People actually provisioning software provisioning data center culture shock when there's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application? Right? The idea of what is an application eyes, something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates. Where is saying there is no application? It's It's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company, what you guys are doing. Take a moment. Explain in context to multi cloud. We're here. Port works. What's the platform? It's a product. What's the value proposition? What's the state of the company. >>So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography ease over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern of doing containers and micro service is And how do I run it with my mission? Critical business crinkle workloads. And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way after now securely access for applications, and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bearer tokens to say, I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that storage. More complexity absolutely need abstraction >>layers, and you got compute. Look, leading work there. But you gotta have >>software to do it from a poor works perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. Lisa, >>we've been covering Dev up, going back to 2010. Remember when I first was hanging around San Francisco 2008 joint was coming out the woodwork and all that early days and you look at the journey of how infrastructures code We talked about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now The tipping point. It's just seems like this wave is big and people are on it. The developers air getting it. It's a modern renaissance of application developers, and the enterprises it's happening in the enterprise is not just like the nerds Tier one, the Alfa Geeks or >>the Cloud native. It's happening in the >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working for works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go creative. It'll open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application. You can google it and see what the work they're doing. It's all there publicly, Onda We built, you know, we built an open source project for them to help them get the most out of kubernetes. We can say so. There's a lot of people in the community system doing that. How can we make communities better halfway make commitments, enterprise grade and not take years to do that? Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast now. I mean, just think about how these projects being structured. Maur and Maur projects are coming online and user price, but a lot more vendor driven projects to use be mostly and used, but now you have a lot of vendors who are users. So the line is blurring between Bender User in Open source is really fascinating. >>Well, you look at the look of the landscape on the C N. C f. You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in this community together. It's one of things that makes it super exciting. And it it's how we know this is This was the right choice for us to base this on communities because that's what everybody, you guys >>are practically neighbors. So we're looking for seeing the studio. Palo Alto Eric, I want to ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe abilities becoming a key part of it, Obviously, automation, configuration management things are developing fast. State. What's the What's the road map for you guys? >>For us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery has been one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a d. R. Pale over into some of the things at least, is pointing out that we're announcing soon is non series autopilot in the idea, automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of the what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us and the customers are all asking for. You >>know, I think data they were back in recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup and recovery was built. It was built because of disruption of business, floods, our gains, data center failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor. So it's not like it after the hey, if we ever have, ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection it needs to be >>redefined. What do you think? Absolutely. I think there's a notion of How do I get last week's data last month? And then oftentimes customers will say, If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything. It gets changed. Suddenly. The important part is not what was just that one pot it becomes. How do I reconstruct everything? What action is not one thing. It's everywhere. That's right and protected all through the platform. If it was a platform decision, it's not some the cattlemen on the side. You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? And you guys have that philosophy. We absolutely, and it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes. You're my date a partner. We make it happen. >>This speaks to your point of why the enterprise is in. The vendors jumped in this is what people care about Security. How do you solve this last mile problem? Storage. Networking. How do you plug those holes in Kubernetes? Because that is crucial to our >>personal private moment. Victory moment for me personally, was been a big fan of Cuban is absolutely, you know, for years. Then there were created, talked about one. The moments that got me that was really kind of a personal, heartfelt moment was enterprise buyer. And, you know, the whole mindset in the Enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shiny new toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration za paying that. But for I t, they don't want that to do that. They hate doing migrations, but with containers and kubernetes that could actually they don't to end of life to bring in the new project. They can do it on their own timetable or keep it around. So that took a lot of air out of the tension in on the I t. Side because they say great I can deal with the lifecycle management, my app on my own terms and go play with Cloud native and said to me, that's like that was to be like, Okay, there it is. That was validation. That means this Israel because now they can innovate without compromising. >>I think so. And I think some of that has been how the ecosystems embrace it, right. So now it's becoming all the vendors are saying my internal stack is also based on community. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like awesome. Lisa >>Marie Nappy Eric on Thank you for coming on Port Works Hot start of multiple cities Kubernetes big developer Project Open Source. Talking about multi cloud here at the inaugural Multi cloud conference in New York City. It's the Cube Courage of escape. 2019. I'm John Period. Thanks for watching

>>from New York. It's the Q covering escape. 19. Hey, welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape. We're in New York City. Was staying in New York, were not escapee from New York were in New York. So about Multi Cloud. And we're here. Lisa Marie Nancy, developer advocate for report works, and Eric Conn, vice president of products. Welcome back with you. >>Thank you, John. >>Good to see you guys. So whenever the first inaugural of anything, we want to get into it and find out why. Multiplied certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data to kind of consistent themes. What's your guys take? Eric, What's your take on this multi cloud trend? >>Yeah, I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had a customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications Going forward. >>You know, you have almost two camps in the world to get your thoughts on this guy's because like you have a cloud native people that are cloud needed, they love it. They're born in the cloud that get it. Everything's bringing along. The developers are on micro service's They're agile train with their own micro service is when you got the hybrid. I t trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, Essie multi Cloud as a combination of old legacy Data Center types of I t with cloud native not just optioned. It was all about trying to build developer teams inside enterprises. This seems to be a big trend, and multi cloud fits into them because now the reality is that I got azure, I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture, What we're trying to do? What's the workloads behavior outcome look like? What's the workflow? So there's a whole nother set of conversations. >>Yeah, that happened. I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port Works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plane perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the death definition of cod, you have to incorporate, just like with hybrid a teeny the legacy applications. And we saw that you throughout the years those crucial applications, as we call them. People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot, too. So I think when we talk about multi cloud, we also talk about what what is in your legacy? What is your name? I mean, I >>like you use legacy. I think it's a great word because I think it really nail the coffin of that old way because remember, if you think about some of the large enterprises these legacy applications didn't optimized for harden optimize their full stack builds up from the ground up. So they're cool. They're running stuff, but it doesn't translate to see a new platform design point. So how do you continue? This is a great fit for that, cos obviously is the answer. You guys see that? Well, okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly on the security side, we're seeing everyone running away from buying tools were thinking about platform. What's the conversation like on the outside >>before your way? Did a talk are multiplied for real talk at Barcelona. Q. Khan put your X three on son. Andrew named it for reals of busy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi pod. It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of your vanities. I don't know if you know, Eric was the first product manager for Pernetti. T o k. He's too shy to say it on dhe. So yeah, and we think, you know, And when it does seem to be the answer to making all they caught a reality right now. >>Well, I want to get back into G k e. And Cooper was very notable historical. So congratulations. But your point about multi cloud is interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I killed my exchange server, I'm essentially running azure by their definition. If I'm building a stack I need of us, I'm a Navy best customer. Let's just say I want to do some tensorflow or play with big table. Are spanner on Google now? I have three clouds. No, they're not saying they have worked low specific objectives. I am totally no problem. I see that all the progressive customers, some legacy. I need to be people like maybe they put their tone a file. But anyone doing meaningful cloud probably has multiple clouds, but that's workload driven when you get into tying them together. It's interesting. I think that's where I think you guys have a great opportunity in this community because it open source convene the gateway to minimize the locket. What locket? I mean, like locking the surprise respect if its value, their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked in at the infrastructure level. So, like you said, if there's value at the higher levels of Stack and it helps me do my business faster, that's an okay thing to exchange. But if it's just locked in and it's not doing anything. They're that's not equal exchange, right? So there's definitely a move from infrastructure up the platform. So locking in infrastructure is what people are trying to move away from. From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting. How legacy will also start to run in containers, and I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how VM skin start to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy and that sourcing strategies Maura regulation type o. R in terms of not being locked in. And that's where I'm saying it's all those things. >>You love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of Okay, standardization kubernetes nights containing one does that. But then you're something about FBI gateways, for instance. Right? So if I'm a car, have five different gig weighs on my device devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something. So I started envisioned. I just made that this case up. But my point is, is that you need some standards. So on the A p I side was seeing some trends there once saying, Okay, here's my stuff. I'll just pass Paramus with FBI, you know, state and stateless are two dynamics. What do you make of that? What? What what has to happen next to get to that next level of happiness and goodness because Ruben is has got it, got it there, >>right? I feel like next level. I feel like in Lisa. Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent to automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did, it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. >>That's like Logan is priority looking fruity manual stuff >>and communities was really good at the food. That's a really use case that you brought up really. People were looking at the data now, and when you're talking about persistent mean Cooney's is great for stateless, but for St Paul's really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking about >>We'll get to that state problem. Talk about your company. I wanna get back Thio, Google Days, um, many war stories around kubernetes. We'll have the same fate as map reduce. You know, the debates internally and Google. What do we do with it? You guys made a good call. Congratulations doing that. What was it like to be early on? Because you already had large scale. You already had. Borg already had all these things in place. Was it like there was >>a few things I'll say One is. It was intense, right? It was intense in the sense that amazing amount of intelligence, amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers are package. We're still looking at how infrastructure Kate run and a lot of the service's were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different >>will. Come back and get in the studio fellow that I gotta ask you now that you're outside. Google was a culture shock. Oh my God. People actually provisioning software. Yeah, I was in a data center. Cultures. There's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application, right? The idea of what is an application eyes something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates wise saying there is no application. It's it's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company. What you guys are doing. Taking moments explaining contacts. Multi Cloud were here. Put worse. What's the platform? It's a product. What's the value proposition? What's the state of the company? >>Yes. So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography is over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern? Doing containers and micro service is, and how do I run it with my mission? Critical business crinkle workloads And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way, acting now securely access for applications and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bear tokens to say I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that >>storage. More complexity, absolutely needing abstraction layers and you compute. Luckily, work there. But you gotta have software to do it >>from a poor box perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. >>Lisa, we've been covering Jeff up. Go back to 2010. Remember when I first I was hanging around? San Francisco? Doesn't eight Joint was coming out the woodwork and all that early days. You look at the journey of how infrastructures code. We'll talk about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now the tipping point just seems like this wave is big and people are on developers air getting it. It's a modern renaissance of application developers, and the enterprise it's happening in the enterprise is not just like the energy. You're one Apple geeks or the foundation. It's happening in >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working poor works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go credible open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application, you can google it and see what the work they're doing. It's all out there publicly. Onda we built, you know, we've built an open source project for them to help them get the most out of kubernetes we can say so there's a lot of people in the community system doing that. How can we make communities better? Half We make competitive enterprise grade and not take years to do that. Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast. Now just think about having project being structured. More and more projects are coming online and user profit a lot more. Vendor driven projects, too used mostly and used with. Now you have a lot of support vendors who are users, so the line is blurring between then their user in open source is really fast. >>Will you look at the look of the landscape on the C N. C. F? You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in the community together. It's one of things that makes it super exciting, and it's how we know this is This was the right choice for us. Did they communities because that's what? Everybody? >>You guys are practically neighbors. We look for CNN Studio, Palo Alto. I wanna ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe. Ability is becoming a key part of it. The automation configuration management things are developing fast. State. What's the road for you guys? For >>us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery is one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a D. R fail over into a Some of the things, at least, is pointing out. That we're announcing soon is non Terry's autopilot in the idea of automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us, and the customers are all asking, >>You know, I think data that recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup recovery was built. It was built because of disruption of business, floods, our games. That's right. It is in their failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor, So it's not like it After today. If we hadn't have ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection needs to redefine. >>What do you think? Absolutely. I think there's a notion of how do I get last week's data last month and then oftentimes customers will say If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything, it gets changed. Suddenly, the important part is not what was just that one pot it becomes. How do I reconstruct everything? Action >>is not one thing. It's everywhere That's right, protected all through the platform. It is a platform decision. It's not some cattlemen on the side. >>You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? >>You guys have that philosophy? >>We absolutely. And it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes here, my data partner. How do you make it happen? >>This speaks to your point of why the enterprise is in the vendors jumped in. This is what people care about security. How do you solve this last mile problem? Storage, Networking. How do you plug those holes and kubernetes? Because that is crucial. >>One personal private moment. Victory moment for me personally, Waas been a big fan of Cuban, is actually, you know, for years in there when it was created, talked about one of moments that got me was personal. Heartfelt moment was enterprise buyer on. The whole mindset in the enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shame, your toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration is a pain in the butt fried. You don't want that to do that. They hate doing migrations, but with containers and kubernetes, they actually they don't end of life to bring in the new project they could do on their own or keep it around. So that took a lot of air out of the tension in on the I t. Side. Because it's a great I can deal with the life cycle of my app on my own terms and go play with Cloud native and said to me, I was like, That was to be like, Okay, there it is. That was validation. That means this is real because now they will be without compromising. >>I think so. And I think some of that has been how the ecosystems embraced it, right, So now it's becoming all the vendors are saying My internal stack is also based on company. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like >>the submarine and the aircon. Thank you for coming on court. Worse Hot started Multiple cities Kubernetes Big developer Project Open Source Talking about multi cloud here at the inaugural Multi Cloud Conference in New York City Secu Courage of Escape Plan 19 John Corey Thanks for watching.

>> Announcer: Live from Las Vegas, it's theCUBE. Covering UiPath Forward Americas 2019. Brought to you by UiPath. >> We're back, UiPath Forward III from Las Vegas at the Bellagio, you're watching theCUBE, the leader in live tech coverage, my name is Dave Vellante. Marie Myers is here, she's the CFO of the rocket-ship known as UiPath. Welcome to theCUBE, thanks for coming on. >> Thank you. >> So, wow. You must be under a lot of pressure to keep the ship moving in a fast direction. But I was just talking to Daniel, he said, you know, when we started the company, we had basic finance systems, kind of like every other startup, but that obviously has changed, so. Well, congratulations, I know you got a lot more work to do but how are you spending your time these days? >> Doing a lot of work, is what I would say. So, as you've kind of seen, that tremendous growth, so huge pressure to just scale the company and ensure that the company has the ability to meet the growth that we're experiencing. So right now I've been really focused on building the operational backbone and actually building a lot of robots for UiPath, actually. That's something I wasn't expecting but came into the role and really help build our own ecosystem around robotics as well. >> I was asking Daniel how much dogfooding, champagne sipping you guys have done and, if it has contributed to the growth and it sounds like quite a bit, actually. >> Absolutely, I'd say we're really hitting the gas pedal right now in terms of building out our own competency and kind of to your point, eating the dog food, drinking the champagne and starting to push the envelope on how we actually use automation and AI to really scale our own business. You asked me where I was spending my time and where I was focused, I literally moved my family to Bucharest for the summer to really focus in on helping to scale the infrastructure. >> So, CFOs usually have a philosophy, a framework, that they like to work with. Obviously you got to stay flexible. How would you describe your philosophy as to how you'd like to manage this company? >> Well clearly, for us we're at an incredible stage of momentum in the market, and the ability for us to continue to build distance in terms of being number one is critical, so in terms of strategy, supporting that number one position, being agile. Able to scale for growth and ultimately do so profitably is certainly the ambition that we have in mind. And that requires turning a lot of different dials, right? And being able to turn them at the right time but at the same time ensure that we've got enough, let's just say, cushion underneath to scale that growth, because the growth is happening very very quickly. >> So CFOs, today's CFO is definitely, I would say more strategic than when I first got into the business, we used to joke that the cheap financial officer. But, I think of CFOs that I really admire, guys like Mike Scarpelli, who was at ServiceNow, now he's at Snowflake. I think he was at Data Domain too, Tom Sweet at Dell, whole different example, they're doing crazy financial engineering. But, much more of a strategic focus. Want to throw gasoline in the fire, and drive growth, but at the same time, thinking about efficiency, so. How have you seen that role evolving and how does that apply to what you guys are doing? >> So I think your comments about the role of the CFO are really right on, I mean, what's perhaps even more interesting, I think, for CFOs that are in software and maybe in a space like we're in is that you ultimately also get involved in being an advocate for your business. In robotics process automation, almost 40% of the first use cases are in finance. So, you're out there supporting the business case with other CFOs who want to understand how does efficiency really, why they should buy from us and what's the business proposition? So you've got to balance the demands of the business with running the business and so, I think that does give you the very unique lens because you understand how this product, to your point, drives operational efficiency. And obviously all CFOs really care, that's right on the list of the top three. >> You know, that's interesting, Marie, because the tech company CIOs are always being pulled in. Because they're early users of some technology. It's not common anyway, that the CFO is one of the lead sales go-to people but it sounds like it is in your case. How much time do you spend in the field? >> I try to balance my time, because you could get pulled very heavily I feel because of the nature of our business into that but I think because robotics process automation has been a key entry point into finance, there's a lot of work for CFOs to do there. So I try to balance my time, but it is, I think, a very important part of our own learning for our company, we get a lot of feedback from our customers. And, even helps me in my role because I get use cases from customers that I apply internally to drive our own efficiency. >> Well, plus, you know, you can see what's happening in the field, you can feel the pain of the sales reps, you can tell which ones are kind of sandbagging, >> You're right, absolutely! >> 'cause they're all sandbaggers! >> You're right about that, so it's been great being at this event, I know a lot of the great reps and so you really understand, you've got a good pulse on what's happening in terms of the business and where the risks are in the quarter. So that's one advantage. >> What're the metrics that you're driving? I mean, obviously the conventional ones, throw those in, but. >> Yeah, I mean obviously productivity, very important for us, we've got a lot of folks we've hired so really understanding what that productivity looks like. The usual cast of characters, AR. Customer acquisition costs, really focused on, what is that first customer costing and then how we're managing our land and expand. What our upsell looks like, so I think the usual cast of characters. >> And then eventually, as all these M and As happen, you'll get cohort sales coming in and the like. So, is everything that you guys sell recognized on a deferred revenue basis? >> No, we're in the midst of converting to 606 right now so we're kind of like subscription one year on prem. So pretty conventional software, red rack. >> Okay, but as you move to the cloud model. >> That gives us a different model, yeah. And we have it, we're just starting that journey. >> It seems like, you see different models. You know, Adobe bit the bullet, Splunk sort of peeled the Band-Aid off very slowly and they both can work. But it seems like a lot of the, I'll call it game, maybe it's the wrong word. But that's what came to mind, is educating the street. On that metric, on that transition. You certainly see it, for instance, in Oracle's case. Putting a lot of emphasis on helping the street understand that transition. That's not your primary focus right now, I'm sure you're spending some time with the analysts, I saw many buzzing around here. >> There was a lot here in the last few days. >> Dave: Yeah, they all want your business! >> (she laughs) They all want your business! I got a lot of texts in the last 48 hours. >> Well, it's an exciting time. And you know, eventually you guys are going to do an IPO and why wouldn't they? Be smart to be here, but what are your thoughts on that? Is that something that you really don't pay attention to right now, are you preparing for that? >> I'd say we're just getting total transparency, we're just moving through 606. So we're digesting that transition first and we're just starting down the whole cloud migration path. So as we start to think that through it's going to be I'd say a priority for 2020. And it's going to be important, I mean, for this business we expect, who's to say what the uptake rate is as customers move to the cloud? But I suspect it's going to be fairly aggressive in our business just because of the nature of bots and how customers think about bots. >> Yeah, so, Daniel said on the previous segment, he said, look, IPO's in our future, probably not 2020, we need at least a year to get our act together. So we're looking at 2021 but it depends on what the climate is, et cetera. My question is, and I've talked to, I see you orange here, Pure Storage is a high flyer in the infrastructure business, they're all orange, so they paint the town orange. >> Seems orange is very popular right now. >> It's a great color, recognizable. But I was talking about, they're all about growth. Not about optimizing profit right now and that's the right play because the street's rewarding growth. You guys, clearly, all about growth. >> We've got the growth story buttoned down, yeah. >> Yeah, you've got that down. But you still want to put gas on the fire, right? So, right now you're still optimized for growth. >> Absolutely, you see what's happening here, right? So, yeah, I think that kind of-- >> And you're well capitalized, so that's not the issue. So the strategy, I presume, is keep growing, get escape velocity, because, the company that gets escape velocity and is the leader in this business, you guys are the leader right now. You're not going to rest, you're going to stay paranoid, I'm sure. But the one that leads is going to make the most money. That always happens. >> Well, extending that leadership role is part of our core strategy, right? Maintaining number one, putting distance. I think you've seen the products that we announced here the last couple of days, adding to the portfolio or giving us incremental TAM so we can grow across the space. I think growing both down the stack and up the stack is critically important for us as we think forward to the future, too, right? We just don't want to be a pure robotics process automation company. We want to look across AI, down the stack into process mining. >> How do you think about your TAM? >> That's a great question. So I've been studying up a little over the last few days preparing for the board meeting tomorrow. I mean, robotics process automation, TAM next year is about two and a half, or two and change in terms of revenue, two billion. I've been looking at it a lot more broadly because I do believe that it is defined today quite narrowly in terms of very traditional RPE. And that started very much in the back office. As we've spread automation and kind of created that platform mentality, the TAM becomes additive. You've got now the process mining TAM which I think we can clearly start to play in that space. And then also the BPMs and now, obviously, AI. So, I was just doing our own back of the envelope in the last few days and you can get, easily, I think now, above that $10 billion mark and it depends on how you start to think about AI as you go forward and that just adds incremental TAM. >> Well, and you throw in services, you're already there. >> Yeah, exactly. >> Probably be there by next year. I think generally, I'll just give you my quick opinion. I think the market's undercounting the TAM potential. And I haven't done a detailed TAM analysis of the, I don't even want to say RPA 'cause that's the core. >> Exactly. >> But I could see this thing expanding dramatically, we talked about cohort sales. Just talking to customers, you're like one to 2% penetrated and there's so many more use cases. As you bring in AI, which, I really think of AI as a horizontal. But if you start applying AI and bringing in automation as an adjacency to you guys, I think that TAM are going to be many many tens of billions beyond what you're thinking. >> That's exactly how I like to think about it, of course, I go back to my IDC friends and try to use some of their benchmarks. But I think they're somewhat conservative. And I think as the market matures and people understand the breadth of the category, I just think that when RPA started it was kind of pigeonholed as a back office opportunity. >> Yeah, I mean, I was at IDC for a long time and we were really crappy at long-term TAM analysis. And you saw it with, Craig LeClair was awesome today. >> Yeah, I love Craig. >> Love him, fantastic. >> Very witty. >> His forecast, however, and same with IDC, we were there, we used to do these linear forecasts and that's not how these markets grow. It's an ogive and a steep S-curve and I think that's my prediction. >> Marie: I couldn't agree more with you. >> We heard predictions this morning, I summarized the predictions and gave my own. And that's one that I see. I'd like to see a longer-term forecast. Maybe we'll work on that. >> Well, we'd love that, I think that's going to be important. I think, part of it's just the maturity of this category. And as folks are starting to understand the breadth of the application, if you think about it, that's why there was so much early work in finance. Now you're starting to see the business spread across the enterprise, right? And I think as it spreads across the enterprise it just adds that incremental TAM and it becomes a gateway to AI. >> I've been using ServiceNow as an example, even though a totally different business, they had a much heavier lift, they started in IT, and went on, so it took longer for adoption. But there's a lot of similarities that I see just in terms of extending beyond just the core of the business, growing the ecosystem, I think is a critical part of that but as far as the customer adoption and the applicability of your technology, I think it's got a lot of legs, so. Like you say, Marie, we'll work on that a little bit. >> I'd love that, thank you. >> Dave: Appreciate you coming on, it was great to have you and wonderful to meet you. >> Enjoyed it. You too, thank you very much. >> You're welcome. Alright, keep right there, buddy, we'll be back to wrap up UiPath Forward III right after this short break. You're watching theCUBE. (electronic music)

from our studios in the heart of Silicon Valley Palo Alto California this is a cute conversation hey welcome back it ready Jeff Rick here with the cube we're in our Palo Alto studios today for a cube conversation a little bit of a break from the road we'd like to have guests come into the palo alto studio and have a little bit calmer conversation without all the buzz of the show and we're excited to have a return guest he hasn't been on for like two and a half years which i find extremely hard to believe it's been too long maria tar she's the CMO of keysight technologies really great to see you wonderful yeah so last time we had you on i had to look it up it was it was october 2016 and you were the CMO of Ixia which is a little bit different or really not that different tell us how you got from ixia to to keysight so keysight technologies acquired Exia and i was fortunate enough to be chosen to be the CMO for keysight technologies so it was a great evolution both for me personally and professionally right and a very kind of similar product and solutions portfolio bigger obviously than what you were doing at Ixia but for people that aren't familiar with keysight give them kind of the quick overview sure so Ixia served two audiences they really targeted the QA engineer as well as the IT infrastructure and keysight actually targets I would say the design engineer the manufacturing engineer part of the Ixia business which is very closely aligned to keysight's is in the test and measurement space so keysight technologies really helped any electrical engineer develop and innovate and bring products to market that that basically have an electric signal going through them what keysight delivers are things like oscilloscopes Network analyzers you know power supplies signal generators and and anything in terms of test and measurement right of design of electronics so you guys in companies been around for a while is four billion in revenue so you guys are basically testing and measuring pretty much everything right this as you say has an electronic signal go through it we have a broad area that we cover and we also have a very very long history in terms of being in this space our heritage started off as the original heel at Packard evolved into Agilent and keysight was spent out about four four or five years ago as an independent company and we're doing really well in terms of raising our awareness and visibility of a new name because anytime you change names you have to re-educate the market right hey this is us you've worked with us for a very long time and we continue to be leaders in this space right good opportunity for you though right that's the that's what they can good see in Mo's four I love my so the cool thing is not only are you working with stuff that's shipping today but you guys have good visibility into the future and as we talked about all the time you know there's some really massive mega trends that are that are coming down the pike that would love to you know kind of get your thoughts off one of them is is 5g and where World Congress was just a couple weeks ago I think you're also at RSA 5g has been getting talked about for a while but it's it's coming and and we see more and more parts I think there's actually been a couple hands that's delivered you probably know way more than I intended tower so wonder if you can explain to people a little bit about 5g when you think about five gene their potential because I don't think many people know much beyond kind of the buzzword that it's you know bigger faster stronger but it's a pretty significant leap over the Kern LTE it's truly a revolutionary and disruptive technology and it enables so much more than what's available today which has really been what I would call incremental evolution with 5g it is it's truly transformative because it you know in addition to faster it is going into spectrum that was traditionally reserved for organizations getting into millimeter-wave so it really changes the technology that we're all used to with the big cell towers 5g uses much smaller antennas and multiple antennas that actually sit on buildings it's you know in terms of because you're using millimeter wave it doesn't travel as long distances there's what you have with LTE which is sub 6 gigahertz that's all on the technology front what's really amazing about 5g is it has capabilities such as ultra-low latency and it's supposed to consume a lot less power so you could almost see it as as really disrupting and transforming everything and how we think about everything whether it's enabling the car of the future and autonomous driving because now all of a sudden your car can actually communicate to everything with vehicle to everything communication or cellular vehicle to everything communications you can think about it as a way that it's transforming IOT and the evolution of everything that's happening in IOT right so yes it's bigger faster better much more reliable you know much more lower latency and and for for those of us who care a lot about sustainability it's supposed to also deliver much lower power consumption right just interesting right because LTE was I think kind of the first step into real data space and and people figured out that we're using our phones for a lot more than talk in fact you know the data transmission rates are way higher than then the voice course on voice over IP and people watched football on their on their TV switches or on their screens which is unimaginable a couple years ago but in 5g now that's really not necessarily optimized for but really an enabler for as you said IOT and kind of this next level of you know kind of machine to machine communication it's not just me texting you with a data input but more these super-high fast really require low latency applications in this IOT and in the industrial IOT world that everybody's so psyched about it can't happen without this type of technology it really can't I mean the whole industry 4.0 and in terms of manufacturing and robotics and real-time communication that can happen in in in that if you think about a lot of the the cars that are out there if you look at Tesla they're doing ongoing updates and ongoing communications with all their cars all the time and so something like 5g enables even a higher degree of communication and understanding of what's going on with the vehicle and as you get into more of autonomous vehicles understanding what all the sensors and the radar in the car is seeing basically communicating that to what's happening with edge computing having all of that processing happen there and being able to you know send that back and and be able to adapt to the environment is going to be pretty significant and revolutionary I mean I think in every area this new technology in some ways just in terms of what it opens up will enable us to think of really transformative and disruptive ways of how we do things right and it does require going along for the ride investing early understanding what it means and I would say it crosses so many vertical industries right we definitely have to have lunch with you and Sandra Rivera from Intel it would be a really really fun lunch but I one of the things you touched on with that I don't think people really appreciate is this kind of new age of connected device and clearly Tesla's an easy example right it checks in every night but as we see more and more devices being connected kind of back to the mothership and and the ability for a maker of something to actually know now how are people using it it's not just I build it I ship it to my distributor and maybe I'll get a few back every now and then and we can we can take it apart and see how people used it but just the whole kind of product management lifecycle when you've got connected devices that actually report home and to how they're actually being used and how people are using them is such a transformational both the relationship between the user and the device but now the device back to the man you that they never never used to have before yeah and it has both kind of technological as well as I would say society oriented ramifications if you think about in the Tesla example you're effectively saying hey it's okay for Tesla to constantly talk to my car a lot of times we're used to the model of once I buy something it's mine you know this is my device not something that's part of your ongoing network so to speak and so with with a lot of these evolutions that are going on there's going to be both a capability shift in terms of what we can enable but there's also going to come with it somewhat of a society shift of what's now accessed about you so for example with IOT if you choose to move towards this concept of body area networks and having sensors all over you or potentially even embedded in you how that is being leveraged to provide you information how do you protect that from a security standpoint from someone tapping into that to abuse that information so a lot of those topics were really big topics at Mobile World Congress in terms of the coming of 5g and you know just even kind of there the the completion of the standard because it's not yet fully ratified yet right so there's ongoing evolutions and not there's obviously a lot of hype out there on this we are very much involved with the whole ecosystem that's involved in 5g all the way from chipsets to the devices to the networks that carry them you know sort of looking at the whole end-to-end eCos to the antennas you name it to the base stations we're involved in in that whole ecosystem and you as keysight we actually have to get in really early because all of those innovators are depending on our technology to test and validate that it will perform as expected because you're working with all those pieces of electronics in that hole that holes system yeah well Mobile World Congress is interesting last week or the week before was our essay and a lot of the things you're talking about I would argue are probably gonna be more important on the RS a type of kind of view of the world versus the Mobile World Congress assuming you get everything to work which which which I'm sure everybody will but but kind of the legal ramifications and the moral ramifications and the data privacy ramifications when there is so many more connected devices and as you said body area network right now it's my heart rate I went to an interesting Wall Street Journal conference where people can sell back their 23andme genomic data back into a pool for researchers who are looking for certain profiles so they can do their clinical trials and you know that's basically it's basically an electronic representation of literally who you are and so again I think you I think you touch on a lot of really important points that it's the security and David privacy and and in the the moral issues around how that's used treated stored protected are gonna be the bigger issues as we just get more and more of these things becoming really its software and data which we see in the products tehsils a lot more software than it is a car and that's why they can do updates all the time and keep updating the features well even in our business we're becoming much more of a software oriented business in terms of our test and measurement and how we look at the whole design workflow and to end so in many ways everything is is becoming software right just because if you think about this concept of the digitization that's going on of everything there's a lot of discussions about this concept of digital twins right where there's enough information derived from something physical that you can essentially replicate the digital twin and you can do the simulations and in in what you're describing you know you basically you could potentially have it model and represent whether it's a robotic process or a car process and anticipate hey this is time when this is going to wear down you know this is what I'm seeing out there and and it's almost becomes predictive right in terms of what's going on in the real world so it's it's really exciting stuff and it's wonderful to be at the because of this right going to RSA i agree with you all of those topics we're front and center very important to understand and have the visibility in terms of a lot of these 5g networks there's so much throughput going in how do you you know let's say you're a service provider and you want to offer this service how do you actually measure and have visibility in terms of really that is the service that you're offering so there's a lot of discussion in terms of providing that visibility and that security in terms of for those types of customers right it's funny we've done a lot of stuff with GE and back with the software group with Bill ruin team and they've talked about gee talks about digital twins a lot in the context of the industrial products that they built whether it's a turbine engine or whatever to the point that you said so you can do testing and you can do maintenance scheduling and all this other stuff what was weird at the Wall Street Journal conferences they're talking about digital twins for people your digital twins so now I can test you know how would you respond to certain drug treatments how might you respond to a different diet regime how might you respond differently to a different exercise regime and I'd never kind of heard that digital twin concept applied to a person and it's that's really interesting it's really interesting times but before I let you go I imagine your business has changed quite a bit as the kind of percentage of make up of all these devices has shifted from you know kind of dedicated purpose-built hardware which is probably relatively easy to test to kind of hardware platforms that are supporting a larger and increasing amount of software that actually drive the functionality must be good for your business because I'm sure the testing has got to be much more complex not to mention people are pushing updates all of the time really different models and just testing a box well it has changed and actually what's you know when I talk to our customers their goal is to innovate and bring their products to market faster and as a company that supports them our goal is to accelerate their innovation and a lot of times it's how do you share the information as it's going from the design engineer - you know sort of the the quality and test - then go to manufacturing because a designer will build his product and then he'll send it off and say ok I'm kind of done how do you then make sure that at every cog of the wheel you're basically able to share back what his expectation were when he was building it in a CAD system versus what what they're actually seeing when they test the real-life product versus what they actually see when they're manufacturing and applying the same tests so having that consistent software which at keysight we call path wave it really allows that acceleration and the sharing across all of those different groups so that you can optimize the flow so to speak of your design the other exciting part is is you're right there's just so much innovation and evolution in terms of the areas that we participate in because all of these technologies are changing you know we talked about sort of the the autonomous vehicle just as important as the electric vehicle and and the growth in terms of how do you manufacture and test batteries in a scale that's going to be required to keep up with the demand because traditional methods it takes a long time to to test a battery to make sure it's available and can be used and we have some really innovative technology that allows us to to expedite and accelerate that testing so customers of ours like BMW are leveraging this technology so that they can accelerate their their battery production testing and deployment right well we'll have to have you back another time we're out of time dig just just I'm so excited by the whole kind of change of mobility which is driven by really high capacity inexpensive batteries and these really powerful little brushless motors and and as those things kind of permeate and all these different form factors thankfully driven by the high bania fact or the high volume car manufacturers since it's the same little cells that run a lot of these things it's pretty pretty cool space but but we can't get deep into that this time I'll have to say throw for next time so hopefully it won't be another two and a half years I hope very well thanks for stopping by and really appreciate catching up thanks a lot Jeff good see you alright she's Marie I'm Jeff you're watching the key we're in her cube Studios in Palo Alto thanks for watching we'll see you next time [Music]

>> Announcer: Live from Vancouver, Canada. It's the CUBE. Coverage OpenStack Summit North American 2018. Brought to you by Red Hat, the OpenStack Foundation and its ecosystem partners. >> Stu: Welcome to SiliconANGLE Media's coverage of OpenStack Summit 2018. This is the CUBE. We're on day two of three days of live coverage. I'm Stu Miniman here with my co-host, John Troyer. Beautiful city here in Vancouver. There's been a bunch of parties last night, community things going on and to help us kind of set the stage for day two happy to welcome back to the program Lisa-Marie Namphy whose an OpenStack ambassador and also now a developer advocate with Portworx. Lisa, great to see you. >> Lisa: Thank you, guys, always great to be here. >> Stu: So, you're wearing a new logo ?????? Why don't you bring us up to speed on some of the many hats you're wearing. >> Lisa: Yeah, I joined the team at Portworx a few months back, super exciting, cognitive storage. If you want to run safe provocations like databases and containers, that's where Portworx comes in. So, it's a great space and as you know I've been in the cognitive space for a long time so I'm very happy to join the team of Portworx. >> Stu: I love, there's the open dev stuff going on here at the show. There was a keynote this morning, Forrest did a nice job of it. We'll actually have Immam on the CUBE tomorrow to talk some more about this, but you're at that nice intersection of how the developers fit into this, containers has been a hot discussion here for a few years, that whole cloud-native term that you've brought up, what is that mean to the OpenStack community, give us your level set as to what you see happening here in the OpenStack and beyond. >> Lisa: Yes, as you intimated I am still the tech ambassador for North America and have been for a long time, so I have seen this change coming, this progression, super-exciting at this conference how they've embraced those technologies that have been part of the story, but they really embraced at a very serious way as you saw from the keynotes yesterday. All the other technologies like works being done around containers, like Edge, ioT, all these wonderful stories that are getting showcased at this conference and customers and partners and communities coming together and working together, I think that's the most exciting part. >> John: Well, Lisa you run the meetup formally known as the Bay Area OpenStack meetup which just changed it name. Can you talk a little bit about that? >> Lisa: Yeah, well we just thought that, after looking at our schedule, and over the last two years I think that I've run 18 meetups on Kubernetes and Docker and Mesos and I just felt like networking and storage and all of the stuff we showcased I would keep. We didn't feel like the name was really reflective of the content that we were delivering and Cloud-native and Open-infrastructure is more of a broad term and that's the content that we've been delivering, and that's what the community has been wanting to talk about and wanting to come together over. So I changed the name. >> John: You guys have had great success, right? It's one of the biggest, or one of the biggest, meetup in this space. >> Lisa: It is, yeah, it's the world's largest ever tech issue group. We have over 6,000 members. >> John: People show up >> Lisa: They do. >> John: I've been to meetings. >> Lisa: A nice note to everybody, I didn't want anyone to panic, we still love OpenStack, and remember, OpenStack is a foundation of this, it was the first OpenStack meetup, but OpenStack is at the core of all of this technology, so it's built on OpenStack OpenStack's inside and so it's open infrastructure's a better, more encompassing title. >> Stu: I think that's great, we actually in some of the interviews we did yesterday, we had a COB provider from Australia and you go look around their website and it's not like they're saying, "Hey, OpenStack" all over the place, they're infrastructure and service for government and when you dig down underneath, what do you know, there's OpenStack there. Talk to a number of software companies that, when you dig into their IP, it's like "Oh, okay, we're using one of these projects from OpenStack." So, the premise I had had a few years ago is we know Opensource is a bunch of tools out there and it's not necessarily just like Linux permeated throughout the data center, OpenStack has that opportunity to that next generation of helping us to build everything from structure to service to all of these software products that are inside. >> Lisa: Absolutely and we saw during all those keynotes yesterday all the different projects when they did show what was being shown as the demo, all these projects coming together, maybe only two of them, that an OpenStack project, it's all of these communities coming together, working together, and it's kind of changed because everything's been focusing on business problems and this, I think, is the biggest shift that this shows. You know, these user communities not being so focused on the project that they're working on, but really focusing on use cases and trying to solve those problems, and now, I haven't said this to Lauren and Jonathan, I feel like when they pull the design from it out, I think that went a long way to taking away the project focus, because when you have a design summit and everyone runs off into their rooms to talk about cinder or nova or whatever it was they argue about the next release, that has all been removed and now its happening elsewhere and it really let the community come together and work together and bring all the technologies together. >> Stu: What do you, the conference in general, what's the vibe here? Obviously, we're in a beautiful place, everyone's really kind of stunned by the mountains everyone, not the first time though OpenStack Summit's been here in Vancouver, but what's the vibe, what's the feeling? >> Lisa: Yeah, it's so great to be back here. Congratulations on the trained whales that you've got for the free tram behind us. Vancouver, I mean, yeah Canada. It's just everyone's been so nice, so wonderful, it's so beautiful, wow, extremely happy to be back here. I think the Summit's been going great, you know. Non-dairy options at the coffee stations, I love that, too. They've thought of everything, the marketplace was booming last night, we had a little ambassador stand where people could come up and do a meet and greet and I was like pilled that there was so many people coming by for the whole hour. The energy has been wonderful and everybody feels involved. You know, this is a very communal feeling to this Summit. >> Stu: Great, to tell us about Portworx, give us the update there, how that fits into what's happening at the show. You've been lost in shows lately, you've got more coming up in the next month. >> Lisa: Absolutely, I mean, people just think okay it's an OpenStack summit, is it really going to be relevant? I have so many customers here, it's been fantastic to catch up with people and Portworx, it's a startup out of Spokane Valley, based in Los Altos and we have almost a hundred customers now and it's live in production, running Kubernetes in production and the problem with when you wanted to run those fateful applications, people think of containers as stateless traditionally, particularly Kubernetes, but what are you going to do with the data, right? The database is still super important so whether it's Postscript or MySequal or Kassberg or Santros, those fateful applications are really important and not the problem that Portworx solves. It's a cognitive storage company, but it's really beyond that, things you would expect from traditional VM, high availability, things like that, we can solve those problems if you want to run Postscript in a container. We worked really closely with Nasos, say resallas, the Kubernetes team with Docker. We'll be at DockerCon, the other, next week, and so we are actually doing the next meetup in the San Francisco Bay area. The first one we're going to bring all of these group together, we're doing it in conjunctions with our french and code press who run the production ready container, used to be container 101 meetup, so we're going to get together with them and with our Cloud-native open-infra user group. So, we're going to a meetup on June 6th, so I hope you guys come? >> John: Great, so I mean you said there's a lot of, going back to the conflict of business users, you know, folks who actually need to get stuff done, anything you're looking at in a conference in terms of the news, the clean release is out, so in terms of technologies, you're hearing about, talked about, buzz, the VTBU stuff, I don't know all what different, I know there's a lot of other storage news coming out this week, but anything that you guys are hearing in the air? >> Lisa: I mean, around again the adjacent technologies, CASA containers, a big focus here, and I hope that they're going to be a big focus, I hope I can finally run the first ever robotic containment meetup. We're going to have them do a hands-on lab at our OpenStack birthday party event on the "8th" I put that in quotes because it's a half-day hands-on lab training, it's sorry the 10th, July 10th, we want to focus on product containers, we want to focus on some of the new technology, Akrana, you heard me mention that yesterday. That's coming out, Edge, so Edge technology is huge, Vast was on stage again, right, talking about what they are doing, OpenDev as a subtrack of this constant or however they say that, it's super exciting. I think Boris Sunstach this morning, Boris is a sponsor Lawrence was a sponsor of that and I think the OpenDev community is really, it's bringing kind of of the developers and technology back into the fold and having this kind of of un-conference or sub-conference going on as a track, which is fantastic. I'm speaking tomorrow on the container track, container info-structure track, so super-excited about that it's also a track, but that's what I loved about this conference, about how they're really focusing on these kind of new and up-and-coming areas that are super hot. >> Stu: Lisa-Marie Namphy, really appreciate you helping us kick off day two coverage, so much these blendings of these communities helping the users put together the overall solution to get done what they need to get done. >> Lisa: Yeah, Bob Obasek of that foundation they've done a fantastic job, the energy of this summit has been fantastic. >> Stu: We've got a full lineup today, we've got practitioners, we've got the ecosystem, and for John Troyer I'm Stu Miniman. Thanks for watching the CUBE.

>> Announcer: Boston, Massachusetts It's theCUBE. Covering OpenStack Summit 2017. Brought to you by the OpenStack Foundation, RedHat, and additional ecosystem support. (upbeat techno music fades out) >> Hi, I'm Stu Miniman, joined by John Troyer, and this is theCUBE, SiliconANGLE Media's live broadcast of OpenStack 2017 here in beautiful Boston, Massachusetts. Actually, the clouds have been breaking up, a little bit of sunshine here, and it's our third day of broadcasts. We have really a lot of our editorial segment today. Going to be talking to more community members, talking to one of the Superuser winners, a number of startups, and happy to start the day, Lisa-Marie Namphy who is the US OpenStack ambassador. CUBE alum, been on a number of times. Lisa, tell us what's new in your world. >> Thank you Stu, and thanks John and what a pleasure to be here with you folks, and hello, Boston and world, good morning. What's new, well the OpenStack ambassador program is expanding all the time, we just had a great session that Sonia did to kick off the day today to really talk about, you know, how to get involved in OpenStack, even if you're not necessarily a technical person. It's really important to acknowledge how everybody in our community can contribute, and that's one of the things the ambassador program does really well. So we just had a session on that. One of the things that I've done with our user group that is new and super exciting is I've morphed it into a little bit of the OpenStack in Containers user group. So I've been focusing a lot on containers, done 12 or 13 meetups on Kubernetes and or Docker since last summer, and I just had the pleasure of speaking in the CNCF communities track, communities day track yesterday, and that was so much fun, out there in the grand ballroom, so that's kind of some new and fun things we're doing. >> It's great, this is our fifth year doing theCUBE at this show, always a robust community, really. When we started coming, it was the people building it, Now we have a lot of the users, there's different sub-segments, can you speak a little bit to the kind of maturity of the community, and, you know how do people get involved in the ambassador program, how many are there geographically, number wise, diversity, those kind of things. >> Oh gosh, yeah so it's geo, or it's a worldwide program and it's been going a lot, and you're right, you know years ago, here it was the Design Summit, and we sat around and talked about, you know the next six months of the project, and then it morphed into more users, adoption, customers, operators are a really big one too. And now those things are all so big, we have operators, Midcycles, and all and the Design Summit has been, you know sequestered off into, separated out so that we can really focus here on the customers, the community, users, and those type of contributors as well. So things have changed a lot in the seven years since we've been doing OpenStack. The ambassador program is fantastic. The foundation has done a really good job in the last couple of years of acknowledging the contributions of the user community, and so not necessarily the code contributors only, but the people who are also spending as much time contributing in really significant ways to our community, and growing our commnity. Open source doesn't work without a community. So we know that, and we're doing a much better job of acknowledging who those people are and rewarding them. >> John: How many ambassadors worldwide? >> There's about twenty of us. I'm the only one in the US right now, but we're about to change that. I believe my friend Sheila is going to join and cover the East Coast, and I'll be able to do everything west of the Mississippi, but most countries only have one, and... >> And the role of an ambassador, do you do a lot of meetups? Do you go speak? You're there as a, for people to contact as well, right? >> Yeah, we generally recruit or ask people to be ambassadors if they are already doing those things, if they're already running a local user group, if they already have a brand in OpenStack, and they speak, and they kind of already know how to reach out to people, and how to inspire people, or people see them on stage, and that's why the foundation approached me to do it. I had been running the San Francisco Bay area meetup for three years, and speaking, I don't know this is probably my eighth, ninth, maybe tenth OpenStack Summit that I've been speaking at, and OpenStack days and all of that. And so, you kind of see who's already doing it. The cool thing about community is nobody is asked to do it, like you do it because you have a passion for it, because you love it, because it's the right thing to do, because it's helpful to push the technology forward because you have a passion for the technology, because you love people, all these reasons is why people get into it. So you find all over the world people who are doing this. They're already doing it and they're not being paid to do it they're doing it, those are the people you grab, because you know, there is a burnout level to it but those are the people who have enough passion about it and commitment, and believe in community that they're going to be successful at it. >> Can you talk a little bit about the Bay Area OpenStack user group? It's one of the largest OpenStack user groups, and one of the themes we've seen this week is a lot of talk about containers, a lot of talk about, well, Kubernetes, but containers in general, kind of demystifying the sometimes confusing story about where's OpenStack good for, where's the container layer good for, it turns out it's good for a couple different places, you can containerize OpenStack, you can also... A lot of talk about the app layer on top, but you actually, what you just said, you've actually expanded the conversation, you don't just sit there and say "this month we're talking about Neutron," you talk about a lot of different topics, and you bring people to the table. >> Yeah, San Francisco area, you are correct, it is the world's largest OpenStack user group, we have over 6,000 members. Not all of them are located in the Bay Area, I think people like to join the user group because we provide a lot of really good content, and we live stream our meetups, we have Google Hangouts, I record them all, they're all on our calendar, if you go to meetup.com/openstack, you get to us because we were the first one. So we do get a lot of people from around the world, and I write newsletters with lots of interesting information but it is a local community and we do encourage people to participate, so the meetups are super important and the only way to make sure that you keep your community strong and keep people coming back is to have phenomenal content in your meetups. So I work really hard to make sure that the content is interesting, that it's relevant, and the most exciting, most relevant conversation since last summer has been containers. The year before that it was networking, and it still kind of is and always will be. So we do a lot of meetups on networking, too, but containers has been what people want to talk about. They're trying to figure this out. OpenStack has reached a maturity level where people, you know, they're not necessarily learning or if they are they can take an OpenStack 101 course and those exist all over the place. So we've gone to the next level, and whether it was Cloud Foundry or now Containers we do like to talk about what else you can do with this fabulous technology, and how you should do it. So we've had meetups where we've presented OpenStack on communities, communities on OpenStack, where I personally came in and did a whole meetup on Kubernetes as the underlay, and Rob Starmer came in and did a whole workshop and hands-on about how to run OpenStack on containers. Yesterday our panel, you heard Dan Berg talk about just simplifying it, run everything in a container, but keep it as simple as possible, so what pieces do you need? So these are the conversations that we like to have in our user group, and people keep coming back because it's an exciting conversation. >> Yeah, expanding on that, you talked about just people are always coming, new people to the community that don't know it, people that are changing jobs all the time, new technologies, I mean, we all know community building is a constant, you know, reinvention in something, you keep needing to work How do the ambassadors, how do stay energized on it, how do you keep the momentum and the energy of the community going? >> Yeah, well the cool thing about an open source community is no matter where you're working, you're still part of the community. So I've worked with so many other people here, I don't even know where they are sometimes. I mean we don't tend to talk about what company we're actually working for, or who's paying your paycheck, and especially in the early days of the project that was definitely true, and so some of my good friends have been at four different companies in the time that we've been doing this OpenStack thing, but we're all still working on OpenStack, and I suspect Kubernetes will be very similar, or Docker. You know, how many people are working on Docker? But there's only 200 people that work for Docker, right? So these technologies kind of take on these lives of their own, and people do switch jobs a lot, but people come to meetups because it's a constant thing, and it's also a good place to keep networking and keep looking for work, so we got a lot of that. The beginning of every meetup, I ask for a show of hands of who's hiring. If I ask for who's looking, not everybody raises their hand but if you ask who's hiring, there's a lot of people hiring all the time, and so then the people can look around and say "okay I'm going to go talk to those people," so yeah, the networking is an important part. >> On that point, are you seeing any trends as to what are the roles that they're hiring for, or you know, companies or industries that definitely have changing skillsets, you know John spent a lot of time helping all those virtualization people moving to that next thing, what are you seeing? >> Engineering is the big one, and people are still looking for OpenStack engineers. I mean people ping me all the time, saying "do you know any OpenStack engineers?" So that's usually the number one thing, developers to help build out these things, and then also the companies that, you know, that aren't OpenStack companies, you know companies like GE that are trying to hire what, 20,000 developers in the next couple years, and Mercedes and Tesla, and you see all these companies that are trying to build out their software developer programs. So another role that is interesting that people are hiring for is these developer, DevRel, Developer IVC community roles to try to figure out, you know how are we going to build our developer community within our company? If these are really large companies, or you know, companies like IBM which have interest in things like the Apache Spark community, or you know, you find these pockets in these large companies as well. Or there's a lot of startups, you know unlike, probably not like Docker as much, but Kubernetes is going to have this ecosystem of partners that build around it, and these companies are popping up out of the woodwork and they're growing like crazy, and there's like 30 of them in the Bay Area, right? So they're really trying to expand as well. >> I wanted to ask about the general mood of the summit. My first summit... You know, it happens every six months. I've been impressed by how grounded people are, I see a lot of first time attendees, people starting new OpenStack installations in 2017 right now, here to learn... I'm just kind of curious, over the last couple summits is there anything different you see about here in Boston, anything you're looking forward to going to in the next one, in terms of kind of mood and how people are, are people feeling good, are people, you know, are people still puzzling out this container issue, or are people still talking about public versus private, or what are kind of the mood and conversations you hear from other community members? >> I think people are talking about public versus private again, not still right? I mean is it, that was kind of an interesting one, and I think Johnathan brought it up on main stage on the first day about that kind of readoption of private cloud, and that you know, we knew that was a sweet spot for OpenStack particularly in the US. You know, lots of public clouds running on other parts of the world, but that's a fun conversation, and it's containers of course, but not just containers. I think it was maybe Lauren Sell who put the slide up of all of those other technologies that are, you know affiliate now, and... >> Another ecosystem of open source projects >> Lisa: Yeah, yeah >> that can all interoperate with openstack. >> With Cloud Foundry, and Ansible was up there, and Ceph, and you had a slide full of technologies, OpenDaylight, that are all playing a role here and that the conversation has been about, and I just encouraged in the ambassador session and in the meetup sessions to do that with your meetup. Our meetup has been really successful and the people have loved it because we started bringing in this other technology. People want to talk about IoT, they want to talk about AI, they want to talk about machine learning, so there's those, they want to talk about, you know what are the best use cases for OpenStack so we showcased to GoDaddy what they built with Docker on top of OpenStack. So there's a lot of fun conversations to be had right now, and I think there's a buzz around here, you know that, what, day one when Johnathan put the slide up saying, you know, people have predicted the end of OpenStack and that was like four years ago or whatever, that was an awesome slide, right? I'm sure talked to him about it. >> Yeah, I absolutely traded notes, and caught opinion about it, too. Lisa, you live in The Valley, I'm curious about perception in The Valley, you know, OpenStacks now been around seven years, it's kind of, you know, it's matured, it's moved on, some called it boring because we fixed some of the main issues, you know We mentioned all the OpenStack days with you know Cloud Foundry, Kubernetes, all these software pieces on top, what do you hear in The Valley when people talk about OpenStack, any misperceptions you'd want to clarify? >> Yeah, yeah it's not boring. It's funny when you say to a California girl "you live in The Valley," I'd be like, "let's just say The Silicon Valley." Not the, not the other Valley. >> Stu: Not the Valley girl >> Don't make me start talking like that, right? >> Stu: Oh my god! (laughs) >> Right, so, no. It's never boring, it's never... It hasn't been boring from day one, and there's been times where I felt like okay we've been talking about infrastructure for years now, let's talk about some other things, but I love the way at this conference they're talking about, they're calling it the "open infrastructure conference." You know, this is what OpenStack has become, and that just opens the conversation. You know, I love that shift. There's always something exciting to talk about, and I don't mean the little inside baseball things, like should we have done Big Ten, should Stackalytics go away, I mean, you know people like to talk about that stuff, but I don't find that customers or the people at the meetups are talking about that stuff. People at the meetups are talking about you know, how should we run this with Kubernetes? How do these technologies fit together? You know, lots of different things, you know where does Docker play into it? Networking is still a conversation and a problem to still be solved, and how are we going to do this? We had OpenContrail do a meetup with us a couple of weeks ago. There's still a lot of interest in figuring out the networking piece of it, and how to do that better. So we're never going to run out of things to talk about. >> Alright, so how do more people get involved, how do they find their meetups, where do they find resources? >> Most of, openstack.org has a list of all the communities, but most of the communities use meetup.com, almost globally, so if you go to meetup.com, and you put in your geo, you'll find one. You can contact your local ambassador. If you want to get involved, I say just go to a meetup. I mean you can't start leading communities until you participate in communities. There is no way to phone this in. You have to, it's hands-on, roll up your sleeves, let's get to work and participate, and have some fun. So go to a local meetup, and meet your meetup organizers, volunteer, help, and it's so rewarding. Some of my best friends that I have, I've met through OpenStack or open source projects. It creates many opportunities for jobs. So just start going to meetups and get involved, and if you want to be an ambassador, there's a list on the website of how to figure that out. Tom Fifield runs the whole program with Sonia's help out of Australia, but regionally we're always looking for help. There's no shortage of roles that people can play if people really want to. >> Definitely a vibrant community here, doing well, Lisa-Marie Namphy, always a pleasure to catch up with you, and we have a full day of programming coming, so stay tuned and thank you for watching the cube. >> Lisa: Thanks Stu, thanks John. (upbeat techno music)

>> Announcer: Live from Santa Clara, California, it's The Cube. Covering open networking summit 2017. Brought to you by the Linux foundation. >> Welcome back. We are live in Santa Clara at the open networking summit 2017. Been coming here for a couple years, it's a lot of open source going on in storage, for a long time, a lot of open source going on in compute for a long time, and you know, networking was kind of the last one, but we had Martin Casado on on earlier today. He says it's 10 years since he started Nicira. And now, it's a billion dollar revenue run raid inside vmware, so I think the software defined networking is pretty real. We're excited for this next segment, Scott Raynovich, been cohosting all day, good to see you again, Scott. But we're kind of shifting, we're going to add to open networking, we're going to add to open, not compute, but OpenStack, I get them all mixed up, we were just-- >> It's all infrastructure, it's all in the family. >> All right, so our next guest here, representing the OpenStack foundation, is Ildiko Vancsa, get that right? She is the ecosystem technical lead for OpenStack, welcome. And Lisa-Marie Namphy, she's now officially the OpenStack ambassador, which if you follow her on Twitter, you would have known that a long time ago. >> For the U.S. There's several others globally, but for the U.S., yeah. >> So first off, welcome. >> Thank you. >> And what is the OpenStack team doing here at open networking summit? >> So OpenStack itself is a multipurpose generated cloud platform, so we are not just looking into enterprise, IT use cases, but also trying to address the telecom and NFV space. And this is the conference where we are finding many of our ecosystem member companies represented, and we are also learning what's new in the networking space, what are the challenges of tomorrow and how we can start to address them today. >> Right, 'cause the telco is a very active space for OpenStack as well, correct, there's been a good market segment for you. >> Yes, it is an emerging area. I would say we have more and more telecommunications company around and they are also more and more involved in open source. Because I think it's kind of clear that they are also using open source for a while now, but using open source and participating in open source, those are two different things. So this kind of mindset change and transition towards participating In these communities and going out to the public field and do software development there and collaborate with each other and the enterprise IT segment as well, this is what is happening today and it is really great to see it. >> Host: Great, great. >> And you've seen more and more telco's participating in the OpenStack summits, there was an NFV day, I think, even going all the way back to the Atlanta summit. And certainly, in Barcelona, Ildiko was actually doing one of the main stage key notes, which was very focused on telco. And some of the main sponsors of this upcoming summit are telco's. So there's definitely a nice energy between telco and OpenStack. >> Now, why do you think the telco is just the one that's kind of getting ahead of the curve in terms of the adoption? >> Scalable low class clouds. (all laugh) >> Right, and we had John Donovan from AT&T said today that they're either rapidly approaching or going to hit, very soon, more than 50% of software defined networking within the AT&T network. So if there's any questions as to whether it's real or still in POC's, I think that pretty much says it's in production and running. >> I'm doing a lot more of that, so I also run the OpenStack user group for the San Francisco bay area and have been for the last three years, and if we're not talking about Kupernetes, or Docker and OpenStack, we're talking about networking. And tonight, actually, we're going to, the open contrail team is talking about some of the stuff they're doing with open contrail and containers and sort of just to piggyback off of this conference. And next week, as well, we're talking about the network functionality in Kupernetes at OpenStack, if you want to run in down to the OpenStack cloud. So it's a huge focus and the user group can't get enough of it. >> and your guys' show is coming up very, very soon. >> The OpenStack summit? >> Yes. >> Oh, absolutely, May 8th through 11th in Boston, Massachusetts. >> Host: Like right around the corner. >> Yeah. >> The incredible moving show, right? It keeps going and going and going. >> Yeah, yeah, there's going to be 6,000 plus people there. There was just some recent press releases about some of the keynotes that are happening there. There's a huge focus on, you know, I keep calling this the year of the user, the year of OpenStack adoption. And we're really, throughout the meetups, we're really doing a lot to try to showcase those use cases. So Google will be one that's onstage talking about some really cool stuff they're doing with OpenStack, some machine learning, just really intelligent stuff they're working on, and that's going to be a great keynote that we're looking forward to. Harvard will be up on there, you know, not just big name foundation members, but a lot of use cases that you'll see presented. >> So why do you think this is the year, what's kind of the breakthrough that it is the year of the user, would you say? >> Well, I think that just the reliability of OpenStack. I think enterprises are getting more comfortable. There are very large clouds running on OpenStack, more in Asia and in Europe and Ildiko can probably talk about it, particularly some of the telco related ones. But you know, the adoption is there and you see more stability around there, more integration with other, I don't know what to call it, emerging technologies like containers, like AI, like IOT. So there's a big push there, but I think enterprises have just, they have adopted it. And there's more expertise out there. We've focused a lot on the administrators. There's the COA, the certified administrator of, you know, OpenStack administrator exam you can take. So the operators have come a long way and they're really helping the customers out there get OpenStack clouds up and running. So I just think, you know, it's seven years now, into it, right, so we got to turn the corner. >> So there have been some growing pains with OpenStack, so what can you tell us about the metrics today versus, say, three or four years ago in terms of total installations, maybe breakdown of telecom versus enterprise, what kind of metrics do you have you there? >> I'll let you take that one. >> We are running, continuously running a user survey and we are seeing growing numbers in the telecom area. I'm not prepared with the numbers from the top of my head, but we are definitely seeing more and more adoption in the telecom space like how you mentioned AT&T, they are one of the largest telecom operators onboard in the community, and they are also very active, showing a pretty great example of how to adopt the software and how to participate in the community to make the software more and more NFV ready and ready for the telecom use cases. We also have, as Lisa-Marie just mentioned, the China area and Asia are coming up as well, like we have China Mobile and China Telecom onboard as well. Or Huawei, so we have telecom operators and telecom vendors as well, around the community. And we are also collaborating with other communities, so like who you see around OPNFV, OpenDaylight, and so forth. We are collaborating with them to see how we can integrate OpenStack into a larger environment as part of the full NFV stack. If you look into the ETSI NFV architectural framework, OpenStack is on the infrastructure layer. The NFV infrastructure and virtual infrastructure manager components are covered with OpenStack services mostly. So you also need to look into, then, how you can run on top of the hardware that the telecom industry is expecting in a data center and how to onboard the virtual network functions on top of that, how to put D management and orchestration components on top of OpenStack, and how the integration works out. So we are collaborating with these communities and what is really exciting about the Upcoming summit is that we are transforming the event a little bit. So this time, it will not be purely OpenStack focused, but it will be more like an open infrastructure, even. We are running open source days, so we will have representation from the communities I mentioned and we will also have Kubernetes onboard, for example, to show how we are collaborating with the representatives of the container technologies. We will also have Cloud Foundry and a few more communities around, so it will be a pretty interesting event and we are just trying to show the big picture that how OpenStack and all these other components of this large ecosystem are operating together. And that is going to be a super cool part of the summit, so the summit is May 8th through 11th and on May 9th, the CNCF, the Linux foundation, actually, behind this, the CNCF day, they're calling it Kupernetes day. And the whole day will be dedicated, there will be a whole track dedicated to Kupernetes, basically. And so they did another call for papers and it's like a little mini conference inside the conference. So that's kind of what I was saying about the adoption of other technologies. I'm sure the OpenStack foundation is putting those numbers together that you asked about and probably Jonathan or Bryce will stand onstage on the first day and talk about them. But what I think is more interesting and what I would encourage people to go, there's a Superuser magazine. Superuser does a great job telling the stories of what's happening out there, and some of these use cases, and who's adopting this technology and what they're doing with it. And those stories are more interesting than just, you know, the numbers. Because you can do anything with numbers and statistics, but these actual user stories are really cool so I encourage readers to go out to Superuser magazine and check that out. >> It's like, Lego uses it. >> There you go. >> I had to check real fast. >> Lot of information on there. They do a good job of that. >> Lego alligators. >> So you talked about this day with the Linux foundation, is there increasing amounts of cooperation between OpenStack and Linux foundation? Given all the projects that seem to be blossoming. >> Yeah, I don't even know that it needed to increase, there's always been nice energy between the two. There is, you know, Eileen Evans, who we know very well, was on the board of both, the first woman on both boards. She was my colleague for many years at Hewlett-Packard. She's still on the Linux foundation board and there's been a lot of synergy between those foundations. They've always worked closely together, especially things like the Cloud Foundry foundation that came out of the Linux foundation has always worked very closely with OpenStack, the OpenStack foundation, and the board members, and it's all one big happy family. We're all open source, yeah. >> And you talked about the enterprises being, you know, they've been using open source for a long time, Linux has been around forever. They're really more adopting kind of an open source ethos in terms of their own contributions back and participating back in. So you see just increased adoption, really, of using the open source vehicle as a way to do better innovation, better product development, and to get involved, get back to their engineers to get involved in something beyond just their day job. >> It is definitely a tendency that is happening, so it's not just AT&T, like, I can mention, for example, NTT DoCoMo, who now has engineers working on OpenStack code. They are a large operator in Japan. And it is really not something, I think, that a few years back, they would've imagined that they will just participate in an open source community. I've been involved with OPNFV for, I think, two years now, or two and a half. I'm an OPNFV ambassador as well, I'm trying to focus on the cross-community collaboration. And OPNFV is an environment where you can find many telecom operators and vendors. And it was a really interesting journey to see them, how they get to know open source more and more and how they learned how this is working and how working in public is like and what the benefits are. And I remember when a few people from, for example, DoCoMo came to OPNFV and they were, like, a little bit more shy, just exploring what's happening. And then like a half year later when they started to do OpenStack contributions, they had code batches merged into OpenStack, they added new functionalities, they kind of became advocates of open source. And they were like telling everywhere that open source is the way to go and this is what everyone should be doing and why it is so great to collaborate with other operators out in the public so you can address the common pain points together, rather than everyone is working on it behind closed doors and trying to invent the same wheel at the same time, separately. >> Right. >> So that was a really, really Interesting journey. And I think more and more companies are following this example. And not just coming and giving feedback, but also more and more participating and doing coding documentation work in the community. >> And I think if I can understand, what I think, also, the question you might have been asking, there wasn't a ton of python developers in the beginning and everybody's like how do we get these OpenStack developers in the company, you know, it was this huge shortage. And Linux was the little hanging fruit, it's like well, why do we just hire some Linux developers and then teach them python, and that's how a lot of OpenStack knowledge came into companies. So that was the trend. And I think enough companies, enough enterprises do see the value of something like OpenStack or Linux or Kupernetes or whatever the project has, Docker, to actually dedicate enough full time employees to be doing just that for as long as it makes sense and then maybe it's another technology. But we saw that for years, right, with OpenStack, huge companies. And there still are. Not always the same companies, depending on what a company needs and where they are, they absolutely find value in contributing back to this community. >> Okay, and you said you got a meetup tonight? >> I do, yeah. >> Give a plug for the meetup. >> Juniper, it's open contrail talking about open contrailing and containers. And it's at Juniper here in Sunnyville, so if you go to meetup.com/openstack, that's our user group. We're the first ones, we got that one. So meetup.com/openstack is the Silicon Valley, San Francisco bay area user group. And then next week, we're talking about networking and Kupernetes. >> All right, it's always good to be above the fold, that's for sure. All right, Ildiko, Lisa-Marie, great to see you again and thanks for stopping by, and we'll see you in Boston, if not before. >> Absolutely, we'll both be quite busy, we have four, both four presentations each, it's going to be a nutty week. So I'm looking forward to seeing you guys in Boston, always a pleasure, thanks for inviting us. >> Absolutely, all right, thanks for stopping by. With Scott Raynovich, I'm Jeff Frick, you're watching The Cube from open networking summit 2017. We'll be back after this short break, thanks for watching.

>> Announcer: Live from Las Vegas, it's theCUBE. Covering InterConnect 2017. Brought to you by, IBM. >> Hey, welcome back everyone. Live in Las Vegas, the Mandalay Bay. We're at the IBM Interconnect 2017. This is CUBE's exclusive coverage of three days of wall to wall. Day three winding down here at the event. Great show about cloud, data, and blockchain. Our next guest is Marie Wieck, who's the general manager of the Blockchain group within IBM, and Greg Wolfond, who's the chairman and CEO of SecureKey Technologies, announced a partnership with IBM. A lot of great success of blockchain. It's now a business unit in IBM. Marie, great to see you. Congratulations on the new role. >> Absolutely, we're really excited. We've seen so much momentum in blockchain that we really are investing heavily, created a new division, part of our Industry Platforms team, and we're off to the races. >> Exciting. >> So six weeks in the role now. >> Six weeks, I guess the business model is keeping running hard, (laughter) 'cause you guys have made great success. We had Ramesh, one of your workers in your division, on early, he came from the labs, or the research team, >> Marie: Right, research. >> and now he's in Solutions. The traction has been pretty amazing, so take us through, from a business standpoint, obviously you're now got the P&L applet running, you're going, engaging customers on use cases. Where'd this progress come from? Was it just, the internal coalesce of IBMers and customers coming together, give us why this is at its point today. >> I mean I think the most important point about blockchain, is that it really is a network effect. The whole idea of a shared distributed ledger, where everybody has visibility to the appropriate parts of data that they want, gives you some really interesting new business models, but you can't have a network effect, you can't have a community and an ecosystem if you don't have a common set of standards, and a way to drive interoperability. So just 15 months ago, we launched with 30 other people, the Hyperledger Project, in the Linux Foundation. It's been the fastest growing open source project since the Linux Foundation started, so really impressive momentum, and, you know if you think back just a year, at InterConnect last year in February, we had this little demo of trading marbles. This year, fast forward a year, we have a new division, we have 400 clients that we're working with on real production level use cases. We have eight networks in production. We've got now version one of the standard, which really brings a lot of the enterprise requirements, and we're seeing all kinds of new use cases. Supply chain, health care, government, financial services, all where we're really talking about being real now and trusted for business. >> And I would add that Ginni Rometty on stage, hammering home the focus, >> Exactly. >> like big time, at a Watsonesque level, >> Marie: Absolutely. >> so that must to mobilizing the IBMers new division. What's the buzz internally? (laughter) People want to come work for your division now, I mean what's happening? >> I do get an awful lot of emails from a lot of people who are very interested, but I always know when there's real momentum, when there are people who are doing it that we didn't tell to do it, you know, so we're starting with a pretty small team internally, my group itself Direct Line, is about 200 people. There's about 600 people in the extended team across the different functions across IBM, but when I do a search on our internal directory and search for blockchain, there's over a thousand people who have that name already in their title or in their description because they're working on it, and they see the power of it. >> Innovative people get intoxicated by blockchain, because they can just see the disruption elements. Greg, I want to ask you, because you're actually doing it, not only is it intoxicating to kind of grok what blockchain can be, this some real use cases right now, really jamming hard on blockchain with the ledger, can you just share quickly how that's playing out in context IBM and in the marketplace. >> Yeah, so SecureKey's a digital ID company. So we started in Canada years ago doing this login service for government. You show up, you want to see your taxes, your unemployment, your pension, any of 80 different departments, we made it easy for citizens to go there. You can redirect into a federated login with your TD login, or your Royal Bank login. We have millions of Canadians who use that, and we had hundreds of thousands a month, but it's really a login service, and it saved the federal government I think eight hundred million dollars to get that done, but we wanted to move to the next step, which is sharing identity, so digital identity and how do I share my attributes from TD Bank or Royal Bank or my data from Equifax or TransUnion in a trusted way with parties I want to, and not share it in other ways. And we couldn't do that without Hyperledger. So we can talk a little bit about why we went to it, but we have a network in Canada, we tested already phase one, we're launching later this year with Royal Bank, TD Bank, Bank of Montreal, Scotia. Where a citizen can show up at a Telco to create a new account. Is it okay to share my name and address and my credit score? Yes, done, account's open in seconds. FINTRAC changed the rules in Canada so you can open a bank account. Can I show up at a bank and share my attributes from the province and from a credit agency, and create my bank account in seconds. And we've all had this problem, right? I talk to my wife... >> I mean we live it everyday, I mean identity theft is I think front and center in mainstream life. Everyone has either someone close to them or themselves get the phone call, the credit score's dropping, or hey, someone's had my identity for a couple weeks, this is brutal, even the credit cards are gettin'... >> It's funny, when I started this business two of my friends had their identity taken over and someone put mortgages on their homes, and I said there had to be a better way to do it. With blockchain if we can take data from different sources, that the bank knows it's me and I can log in right now, that I possess this phone, that the province knows it's me and I can turn on the camera and check it's me, we can raise the ID validation score for everyone in the whole industry. For healthcare, to government, to banking, and we not only raise the ID validation we also raise the AuthScore, because I'm not just logging in with my bank, I must have this phone, with this SIM in it, and if it's canceled it's not me. And normally people would put that through brokers in the middle, but NIST in the U.S. said, we don't want brokers in the middle. They could peek, they could see your data. I have single points of failure. If this is identity for health here's how it goes down. I have honeypots of data. People are collecting all of my stuff in one place, it's encrypted, but the bad guy's going to get that, right? They could go after the person, and say I need the keys, I have a member of your family... >> I mean we're living in a world, in cloud, Marie knows, there's no perimeter anymore. >> Marie: Right right. The security experts that are state of the art right now, are saying, even saying theCUBE in day one here, data is the new perimeter. So there it is, right, this is fundamental, what you're saying, this is the new perimeter, the data, and you distribute it. >> So no broker right, means less of a threat matrix for people to hack. You don't need a trusted third party to arbitrate. >> You shouldn't have to get other credentials and things to go right, if I can login at my bank right now` and prove I've got the mobile device, can I release data from different sources? Ten percent of Americans move every year, if I show up at an apartment, can I share that I'm Greg and my bank says I'm me, that I have this device from my mobile company, can I share a background check to say that it's me? We're going to do that in about eight seconds, compared to the landlord having to go and pay a real estate agent one month's rent to vet you. And then when you do that, imagine the power now right? Would you like to sign up for internet? Share your data, yes, click. Would you like contents insurance, click. Totally taking friction out for consumers, but making sure that the parties who provide that data, whether it's my bank, whether it's my government, they can't track me. I don't want my government or my bank knowing if I go to mental health, or if I go to a cancer clinic. Really important that they don't know, right? >> Yeah, healthcare here, I don't know what it's like in Canada, but certainly in the United States you can't get information about yourself (laughter). >> And it's a perfect connection to blockchain, 'cause the whole notion of blockchain in our mind is about a trusted network, and how do you get trust if you don't know who the people are who are participating. So, we signed an agreement with the Food and Drug Administration in the United States, to focus on leveraging blockchain for exchange of information around patients, privately and securely for clinical drug trials. You know, it's just one example of now, you bring that trust element, that's built on a blockchain already, as a new interoperable component of these new supply chain networks. Whether it's around supply chain in global sourcing, whether it's the providence of food or diamonds, there's some really interesting aspects that you can now add on top. And we're now even connecting, you mentioned Cognitive, you know, now apply Watson on top of that. How do you increase the trust level in our new version one delivery of Hyperledger on the IBM cloud, we actually provide a trust score for the network, scale, a one to a hundred. What if Watson could actually look at your use case and hear the recommendations and suggestions for how to improve the trust level? Improving it means getting more members, so it's more distributed, and there's more sharing of information. But they're not going to want to share that information if there isn't a trust model. >> So give us a glimpse as to, sort of, your business. You got 200 people, but you've got thousands of people within IBM that you can tap, in addition to the huge portfolio of things like Cognitive. So you've got this startup (laughs), >> Marie: Right. >> inside of IBM. >> Marie: A startup in IBM. >> And you said it's inside the Industry Platform's team, so what is that, and what are you actually building out? >> So, we are building, we're taking, and contributing, we're investing really, in the Hyperledger project ourselves. We are one of now 122 members of the open source and open community project, and we're actually developing and contributing content there. >> Dave: Big committer there. >> Big committer, and we provide a support model for anybody who wants to use just Hyperledger, but we take Hyperledger back, and now we're delivering it as a secure platform on our high security network, that is production grade, you know enterprise strong, would be Ginni's word for that, right, and delivering that on our cloud, or letting you take a container and put it on your own enterprise if you really want your own private cloud. But we're also building industry solutions on top of that. So we announced a partnership with Maersk, for global shipping on global trade digitization to provide greater visibility. >> But on that deal, just to interrupt, that Ramesh was put in, that wasn't a solution specifically for them, that was an industry scope solution. >> Correct. So it's really a partnership. So in this case again, it's that network effect, it's that ecosystem, it's not Maersk, the customer, it's Maersk and IBM the partners, who are now bringing forward as the anchor tenants in this new network, the rest of our ecosystems, and we were interested 'cause we have a big supply chain business for all our hardware as well. >> And you're selling a SAS product, is that right? >> Correct. >> So it's a subscription based model? >> Correct. >> And then services on top of that? >> And services both to develop new blockchain applications, we've had a number of our clients here from the 20 thousand at InterConnect, that've come up with new ideas. We're going to help them build that, in a services kind of model, but many of these are going to be essentially SAS networks where either they're going to pay a membership fee or they're going to pay per transaction, a percentage of the price, or they're going to participate in the savings, because this is actually going to streamline the opportunity. In the case of SecureKey, the model we see customers willing to buy, the validation of an identity for an individual if they're participating in a critical transaction. A bank would certainly be willing to pay to increase the confidence that Greg is Greg, if he was applying for a mortgage online. >> And the consumption is through the IBM cloud, correct? >> Yeah, so there's a toolkit, we're big believers in open source. It's open at the ends, really easy using things like Bluemix to connect to the endpoints. And for us, it's just a magnificent coming together, because things like the high security network to turn banks on quickly, where they trust it, and they can put their data in a secure and trusted way, make this all go faster. >> Dave: But that's the only place in the world I can get this, correct? >> Marie: It is certainly the only place that you can get that level of security in a blockchain network. >> But from a competitive standpoint, somebody else has to build this out, and create as a competitive product as IBM has, and run it on somebody else's cloud, for them to compete, correct? >> That is correct. >> The strategy is not to spam the world's clouds, it's to say hey, we've got this solution, here's how you get it, here's how you consume it. >> And we really firmly believe that if this is an interoperable set of standards, there will be other networks, there will be other participants. We want them all to be interoperable. We want a global identity standard for interlocking networks, because that is actually the tide that raises all boats. So if they want to take Hyperledger and put it on their own private cloud or somebody else's cloud, we support that thoroughly. We think that the most enterprise grade cloud though, is with IBM. >> You just got thousands of people doing it, and you say, go for it. >> Exactly. >> Dave: Bring it on baby! >> First of all, you had me at blockchain beginning the interview. I love blockchain, and I think it's very intoxicating from a disruption standpoint. Any entrepreneur, any innovator... This is a bulldozer on existing business models, and of how people do things. So, I'm sure the organic growth that you guys see is proving it, internal IBM and external. How do people get involved? What's your plans on building the ecosystem now, because you got a tiger by the tail here as the GM of this division now. You got to run hard, you got to embrace people, you got to have events, what's your plan, and how do I get involved if I'm someone watching and we want to get involved? >> So, great simple ways to get involved, the developers, we want 'em to be involved directly through the cloud and through developerWorks. You get free access, you can get started quickly. In three clicks you can have a four peer Hyperledger network up and running on Bluemix, and you can start your own services and create. If you are a customer, what we're really suggesting is come and bring us your use case. Bring the participants in your network as well. Come into one of our IBM garages, and we'll work that out for you. And I think it's important that, we think blockchain has a huge potential or I wouldn't be in this new role, but we also think it's not for everything. It's not the panacea for every business problem. We want to make sure the people are using it in the right way for areas where it really makes the most impact, and then we'll help you implement that and develop it. And then we really see the whole ecosystem around our partners, you're going to onboard people into a blockchain network. You're going to have to integrate with your back ends. You're going to extend your mobile devices to provide these new services through apps. So our GSI community is really helping with the integration and the onboarding. Our ISVs are developing new services that run on those blockchain networks, and we just launched our new IBM Cloud for Financial Services, has a blockchain zone, for all those fintech startups to get access and reuse components, so that we can accelerate the effect. >> Alright, well, congratulations Marie, great to see you in the new role, congratulations, >> Marie: Thank you. >> We're super excited for you, and looking forward to getting the update soon at our new studio. We'll try to rope you into our new Palo Alto studio. Greg, great to hear your success. This is the nirvana, I mean, secure ID is like, the big, I mean easily, not like with some either token or engineered identity system, and this is a home run. >> It's privacy, and it's as we talked about before the broadcast. Facebook, would you trust Facebook to go see your medical records? Would you unlock your title using Facebook? You want things that are private, where people aren't tracking you and are more secure than that, so this is really... >> Don Tapscott called Facebook data fracker. (laughing) We provide all our data for Facebook, they've got billionaires on it. Thanks so much for spending the time. >> Thank you. >> Blockchain revolution here inside theCUBE, bringing you really trusted content here on theCUBE. Distribute it out around the world, I'm John Furrier, Dave Vellante, thanks for watching. More great coverage coming up here, stay with us.

>>Good morning from New York city, Lisa Martin and John furrier with the cube. We are at AWS summit NYC. This is a series of summits this year, about 15 summit globally. And we're excited to be here, John, with about 10,000 folks. >>It's crowded. New York is packed big showing here at 80 of us summit. So it's super exciting, >>Super exciting. Just a little bit before the keynote. And we have our first guest, Kevin Farley joins us the director of strategic alliances at Maria DB. Kevin, welcome to >>The program. Thank you very much. Appreciate you guys having us. >>So all of us out from California to NYC. Yeah, lots of eyes. We got keynote with Warner Vogels coming up. We should be some good news, hopefully. Yep. But talk to us about Maria DB Skys cloud native version released a couple years ago. What's going on? >>Yeah, well, it's, you know, Skys SQL for us is really a be on the future. I think when we think about like the company's real mission is it's just creating a database for everyone. It's it's any cloud, any scale, um, any size of performance and really making sure that we're able to deliver on something that really kind of takes advantage of everything we've done in the market to date. If you think about it, there's not very many startups that have a billion downloads and 75% of the fortune 500 already using our service. So what we're really thinking about is how do we bridge that gap? How do we create a natural path for all of these customers? And if you think about not just Maria DB, but anyone else using the sequel query language, all the, my people, what I think most Andy jazzy TK, anyone says, you know, it's about 10% of the market currently is in the clouds. That's 90% of a total addressable market that hasn't done it yet. So creating cloud modernization for us, I think is just a huge opportunity. Do >>You guys have a great history with AWS? I want to just step back, you mentioned some stats on, on success. Can you scope the size and track record of Maria DB for us real quick and set the table? Because I think there's a bigger picture going on that we've been tracking for the past 13 years we address is the role of the database has always been one of those things where they didn't believe a one database fits all things, right. You guys have been part of that track record scope, the size and scale of Maria DB, the usage, the use cases and some of the successes. >>Yeah. I mean, like I said, some of the stats are already threw out there. So, you know, it is pervasive, I think is the best way to put it. I think what you look at what the database market really became is very siloed. Right? I think there was a lot of unique solutions that were built and delivered that had promise, but they also had compromise. And I think once you look at the landscape of a lot of fortune 500 companies, they have probably 10 to 15 different database solutions, right? And they're all doing unique things. They're difficult to manage. They're very costly. So what Marie DB is always kind of focused on is how do we continue to build more and more functionality into the database itself and allow that to be a single source of truth where application developers can seamlessly integrate applications. >>So then the theme of this event in New York city, which is scale dot, dot, dot, anything must align quite well with Maria and your >>Objectives. I mean, honestly, I think when I think of the problems that most database, um, companies, um, face customers, I should say it, it really comes down to performance and scale. Most of them like Maria DB, like you said, they it's like the car, you know, and love you've been driving it for years. You're an expert at it. It works great, but it doesn't have enough range. It doesn't go fast enough. It's hitting walls. That modern data requirements are just breaking. So scale for me is the favorite thing to talk about because what we launched as MariaDB expand, which is a plugable storage engine that is integrated into Skye, and it really gives you dynamic scale. So you can scale in, you can scale out, it's not costly compute to try to get for seasonality. So you can make your black Friday numbers. It's really about the dexterity to be able to come in and out as you need in a share, nothing architecture with full failover sale healing, high availability, married to the cloud for full cloud scale. And that's really the beauty of the AWS partnership. >>Can you elaborate a bit more on the partnership? How long have you guys been partners? Where is it now anything exciting coming out? >>Yeah, it it's, it's actually been a wonderful ride. They've really invested from the very beginning we went for the satisfactory. So they really brought a lot of resources to bear. And I think if you're looking at why it works, um, it's probably two things. I think the number one thing is that we share one of the core tenants and it's customer obsession in a, in a, in an environment where there is co-opetition right. You have to find paths for how do you get the best thing for the customer? And the second is pretty obvious, but if you look at any major cloud, their number one priority is getting large mission critical workloads into their cloud because the revenue is exponential on the backside. So what do we own? Large mission critical workloads. So if you marry that objective with AWS, the partnership is absolutely perfect for driving true revenue, growth scale, and, and revenue across, across both entities in the partner ecosystem. >>So Kevin talk about the, um, the hybrid strategy, cuz you're seeing cloud operations. Yep. Go hybrid. Amazon announced AWS announced outpost like four years ago. Right now edge is super hot. Yeah. So you're seeing like most of the enterprise is saying mm-hmm <affirmative> okay. Love cloud love the cloud database, but I got the on-prem hybrid cloud operations. Right. So it's not just proprietary operations. It's cloud ops. Yeah. How do you guys fit into that? What's the story. >>We, we actually it's. I mean, there's, there's all these new deliverables outposts, you know, come out with a promise. What we have is a reality right now, um, one of the largest, um, networking companies, which I can't mention yet publicly, um, we want a really big sky SQL deal, but what they had manufacturing plants, they needed to have on-prem deployments. So Maria DB naturally syncs with sky SQL. It's the same technology. It works in perfect harmony. So we really already deliver on the promise of hybrid, but of course there's a lot more we can grow in that area. And certainly thinking about app posts and other solutions, um, is definitely on the, the longer term roadmap of what could make sense for in our customer. What, >>What are some of the latest things that, that you guys are doing now that you weren't doing a few years ago that customers should know about the audience should know about? >>I mean, I think the game changer, we're always innovating. I mean, when you're the company that writes the code owns the code, you know, we can do hot fixes, we can do security patches, we can always do the things that give you real time access to what you need. But I think the game changer is what I mentioned a little bit earlier. And I think it's really the, the holy grail of the cloud. It's like, how can we take the, the SQL query language, which is well over 50% of the open source market. Right. And how do we convert that seamlessly into the cloud? How do we help you modernize on that journey? And expand gives you the ability to say, I can be the small, I can be a small startup. I got my C round. I don't wanna manage databases. I can use the exact same service as the largest fortune 100 company that has massive global scale and needs to be able to drive that across globe. Yeah. So I think that's the beauty is that it's really a democratization of the database, >>At least that, you know, we've been covering the big data space for 10 years. Remember all those different conversations had do those days and oh, they have big data and right. But then it's like too hard to set up. Then you had that kind of period where you saw a spark and data lakes emerge. Yeah. Then you, now it almost seems, seems like now more than ever, there's a data revolutions back. Right. It was almost like a lull in the, in, in the, in the market a little bit. Yeah. I'm gonna democratize data science right now. You got data. So now it just seems to be an explosion at that level. What's your analysis on that? Because you you've been in, in, in the weeds and in the, in the, in this market for 10 years. Yeah. And nothing really changed. It's just now it's more ready. Yeah. I think what's your observation. Why >>Is that? I think that's a really good question. And I love it cuz I mean, what the promise of things like could do and net new technologies sort of, it was always out there, but it required this whole net new lift and how do I do it? How do I manage it? How do I optimize it? The beauty of what we can do with Maria DB is that sky SQLs, which you already know and love. Right? And now we can Del you can deliver a data lake on S3, right? You can pull that data. And we also have the ability to do both analytical data and transactional data from the same database. So you can write applications that can pull column, store data up into, um, your application, but you can also have all of your asset transactions, which are absolutely required for all of your mission critical business. So I think that we're seeing more and more adoption. You've seen other companies start to talk about bringing the different elements in, but we're the only ones that really >>Do it and SQL standardizing that front end. Yeah. Even better than ever before. All the stuff under the covers is all being connected. >>That's the awesome part is right. Is you're literally doing what you already know how to do, but you blow it out on the back end, married to the cloud. And that I think is the real revolution of what makes usability real in the data space. And I think that's what was always the problem before >>When you're in partner conversations, you mentioned co-opetition. Yeah. <laugh> so I think when you're in partner conversations and customer conversations, there is a lot of the, the there's a lot of competition out there. Absolutely. Everyone's got their own key messages. What are the key differentiators that you're saying AWS Marie to be together better? And here's why, >>Yeah. I, I think that certainly you, you start with the global footprint of AWS, right? So what we rely on the most is having the ability to truly deal with global customers in availability zones, they're gonna optimize performance from them. But then when we look at what we do that really changes the game, it comes down to scale and performance. We actually just ran, um, a suspense test against cockroach that also does distributed sequel. Absolutely. You know, the results were off the chart. So we went public and said, we have an open challenge. Anyone that wants to try to beat, um, expand and Skye will we'll if you can, we'll put $25,000 towards charity. So we really are putting our money where our mouth is on that challenge. So we believe the performance cuz we've seen it and we know it's real, but then it's really always about data scale. Modern data requirements are breaking the mold of charting. They're breaking the mold of all these bandaids that people have put in these traditional services. And we give them future. We, we feature proof their investments, so they can say, Hey, I can start here. But if I end up being a startup that becomes Airbnb, I'm already built to blow it out on the back end. I can already use what I have. >>Speaking of startups, being the next Airbnb. If you look at behind us here, you can see, this is a really packed event in New York city events are back, but the ecosystem here is even flourishing. So Dave and I and Lisa were observing that we're still kind of in a growth mode, big time. So yeah, there's some market forces headwinds for the big unicorns, overfunded, you know, public companies, maybe the valuations are a little bit off, but there's still a surge of new innovations, new companies coming out of this. Um, and it's all around data and scale. It's all around new names. We've never heard of. Absolutely. What's your take on >>Reaction? Well, actually another awesome segues cuz in addition to the public clouds, I manage the ecosystem. And one of the things that we've really been focused on with Skys SQL is making it accessible API accessible. So if you're a company that has a huge Marine DB footprint change data capture might be the most important thing for you to say, we wanna do this, but we want you to stay in sync with our environments. Um, things like monitoring, things like BI, all of these are ecosystem plays and current partners that we have, um, that we really think about how do you holistically look at not only the database and what it can do, but how does it deliver value to different segments of your customer base or just your employee base that are using that stuff? So I think that's huge for us. >>Well, you know, one of the things that we talk often about is that every company, these days, regardless of industry, has to be a data company. Yep. You've gotta be able to access the data glean insights from an act on it quickly, whether it's manufacturing, retail, healthcare, are there any verticals in where Maria DB really excels? >>Um, so certainly we Excel in areas like financial services is huge DBS bank. Um, in APAC, one of our biggest customers, also one of the largest Oracle migrations, probably the, that we've ever done. A lot of people trying to get off Oracle, we make it seamless to get into Maria DB. Um, you can think about Samsung cloud and another, their entire consumer cloud is built on Maria DB, why it's integrated with expand right seasonality. So there's customers like that that really bring it home for us as far as ServiceNow tech sector. Right? So these are all different ones, but I think we're really strong in those >>Areas. So this brings up a good point. Dave and I a coined a term called super cloud at reinvent and Lisa and Dave were at multiple events we're together at events. And so a lot of people are getting behind this cuz it's multi-cloud sounds like something's broken. Yes. But so we call it super cloud because customers are building on top of ecosystems like Maria DB and others. Yeah. Not just AWS SOS does all the CapEx absolutely provide the value. So now people are having this new super cloud moment. We' saying we can get all the benefits of cloud scale mm-hmm <affirmative> without actually being a cloud. Right. So this is where the next gen layer comes. What's your reaction to, to super cloud. Do you think it's a thing? >>Well, I think it's a thing in the sense, from our perspective as an ISV, we're, we're laser focused on making sure that we support any cloud and we have a truly multicloud cloud platform. But the beauty of that as well is from a single UI, you're able to deploy databases in different clouds underneath that you're not looking at so you can have performance proximity, but you're still driving it through the same Skys UI. So for us it's, it's unequivocally true. Got it. And I think it's only ISVs like Maria DB that can deliver on that value because >>You're enabling, >>We're enabling it. Right. We partner, we build on top of everything. Right. So we can access everything underneath >>And they can then build on top of you. >>Sure, exactly. And that's exactly where it goes. Right? Yeah. So that, I think in that sense, the super cloud is actually already somewhat real. >>It's interesting. You look at the old, it spend, you take a big company. I won't say a name, but a leader in a, a vertical, they have such a big spend. Now they can leverage that spend in with the super cloud model. They then could become a service provider in the vertical. Absolutely capital one S doing it. Yeah. You're seeing, um, Goldman Sachs doing it. They have the power on the spend that they're leveraging in for their business and servicing their vertical and the smaller players. Do you see that trend? >>Well, I think that's the reality is that everyone is getting this place where if you're talking about sort of this broader super concept, you're talking about global scale, right? That's if in order to deliver a backbone that can service that model, you have to have the right data structure and the right database footprint to be able to scale. And I think that's what they all need to be able to do. And that's what we're really well positioned with Skys >>To enable companies, as we talked about a minute ago to truly become data companies. Yeah. And to be competitive and to scale on their own, where are your customer conversations? Are they at the C-suite level? Has that changed in the last couple of years? >>Uh, that's actually a really great way to state that question because I think you would've traditionally probably talked more to, um, the DBAs, right? They're the people that are having headaches. They're having problems. They're, they're trying to solve. We see a lot of developers now tons, right? They're thinking about, I have this, I have this new thing that I need to do to deliver this new application. And here's the requirements and the current model's broken. It doesn't optimize that it's a lot of work and it's hard to manage. So I think that we're in a great position to be able to take that to that next phase and deliver. And then of course, as you get deeper in with AWS, you're talking about, you know, CIO level, CISO level, they're they need to understand how do you fit into our larger paradigm. And many of these guys have, you know, hundreds of million dollar commits with AWS. So they think of their investment in the sense of the cloud stack. And we're part of that cloud stack, just like AWS services. So those conversations continue to happen certainly with our larger customers, cuz it truly is married. >>It is. And they continue to evolve. Kevin, thank you so much >>For joining. You're welcome. Great, >>John and me talking about what's going on with Maria >>D. Thank you, John. Thank you, Lisa. On behalf of Maria B, it was wonderful. Really >>Appreciate it. Fantastic as well for John furrier. I'm Lisa Martin. You're watching the cube live from New York city at AWS summit NYC, John and I we're back with our next guest in a minute.

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