(bright music) >> Announcer: From the Cube studios in Palo Alto in Boston, connecting with thought leaders all around the world. This is a Cube conversation. >> Hi, I'm Stu Miniman, and welcome to a Cube conversation. I'm coming to you from our Boston area studio. And we're going to be digging into P4, which is, the programming protocol independent packet processors. And to help me with that, first time guest on the program, Mario Baldi, he is a distinguished technologist with Pensando. Mario, so nice to see you. Thanks for joining us. >> Thank you. Thank you for inviting. >> Alright, so Mario, you have you have a very, you know, robust technical career, lot of patents, you've worked on, you know, many technologies, you know, deep in the networking and developer world, but give our audience a little bit of your background and what brought you to Pensando. >> Yeah, yes, absolutely. So I started my my professional life in academia, actually, I worked for many years in academia, about 15 years exclusively in academia, and I was focusing both my teaching in research on computer networking. And then I also worked in a number of startups and established companies, in the last about eight years almost exclusively in the industry. And before joining Pensando, I worked for a couple of years at Cisco on a P4 programmable switch and that's where I got in touch with P4 actually. For the occasion I wore a T shirt of one of the P4 workshops. Which reminds me a bit of those people when you ask them, whether they do any sports, they tell you they have a membership at the gym. So I don't just have membership, I didn't just show up at the workshop. I've really been involved in the community and so when I learned what pensando was doing, I immediately got very excited that the ASIC that Pensando has developed these is really extremely powerful and flexible because it's fully programmable, partly programmable, with P4 partly programmable differently. And Pensando is starting to deploy these ASIC at the edge and Haas. And I think such a powerful and flexible device, at the edge of the network really opens incredible opportunities to, on the one hand implement what we have been doing in a different way, on the other hand, implement completely different solution. So, you know, I've been working most of my career in innovation, and when when I saw these, I immediately got very excited and I realized that Pensando was really the right place for me to be. >> Excellent. Yeah, interesting, you know, many people in the industry, they talk about innovation coming out of the universities, you know, Stanford often gets mentioned, but the university that you, you know, attended and also were associate professor at in Italy, a lot of the networking team, your MPLS, you know, team at Pensando, many of them came from them. Silvano guy, you know, written many books, they're, you know, very storied career in that environment. P4, maybe step back for a second, you know, you're you're deep in this group, help us understand what that is, how long it's been around, you know, and who participates in it with P4? >> Yeah, yeah. So as you were saying before, one of the few P4 from whom I've heard saying it, because everyone calls it P4 and nobody says what it really means. So programming protocol, independent packet processor. So it's a programming language for packet processors. And it's protocol independent. So it doesn't start from assuming that we want to use certain protocols. So P4 first of all allows you to specify what packets look like. So what the headers look like, and how they can be parsed. And secondly, because P4 is specifically designed for packet processing, and it's based on the idea that you want to look up values in tables. So it allows you to define tables, in keys that are being used to look up those tables and find an entry in the table. And when you find an entry, that entry contains an action and parameters to be used for that action. So the idea is that the package descriptions that you have in the program, define how the package should be processed. Header fields should be parsed, values extracted from them, and those values are being used as keys to look up into tables. And when the appropriate entry in the table is found, an action is executed and that action is going to modify those header fields, and these happens a number of times, the program specifies a sequence of tables that are being looked up, header fields being modified. In the end, those modified header fields are used to construct new packets that are being sent out of the device. So this is the basic idea of a P4 program. You specify a bunch of tables that are being looked up using values extracted from packets. So this is very powerful for a number of reasons. So first of all, its input, which is always good as we know, especially in networking, and then it maps very well on what we need to do, when we do packet processing. So writing a packet processing program, is relatively easy and fast. Could be difficult to write a generic programming in P4, you could not, but the packet processing program, it's easy to write. And last but not least, P4 really maps well on hardware that was designed specifically to process packet. What we call domain specific processes, right. And those processes are, in fact designed to quickly look up tables that might have decamping side, they might have processes that are specialized in performing, in building keys and performing table lookup, and modifying those header fields. So when you have those processors that are usually organized in pipelines to achieve a good throughput, then you can very efficiently take a P4 program and compile it to execute it very high speed on those processors. And this way, you get the same performance of a fixed function ASIC, but it's fully programmable, nothing is fixed. Which means that you can develop your features much faster, you can add features and fix bugs, you know, with a very short cycle, not with a four or five year cycle of baking a new ASIC. And this is extremely powerful. This is the strong value proposition of P4. >> Yeah, absolutely. I think that that resonates Mario, you know, I used to do presentations about the networking industry and you would draw timelines out there in decades. Because from the standard to get deployed for, you know, the the hardware to get baked, the customers to do the adoption, things take a really long time. You brought up, you know, edge computing, obviously, you know, we are, you know, it is really exciting, but it is changing really fast, and there's a lot of different, you know, capabilities out there. So if you could help us, you know, connect the dots between what P4 does and what the customers need. You know, we talked about multi-cloud and edge. What is it that you know, P4 in general, and what Pensando is doing with P4 specifically, enables this next generation architecture? >> Yeah, sure. So, Pensando has developed these card, which we call DSC distribute services card, that is built around an ASIC, that has a very very versatile architecture. It's a fully programmable. And it's fully programmable it's various levers, and one of them is in fact P4. Now this card and has a PCIE interface. So it can be installed in horse. And by the way, this is not the only way this powerful as you can be deployed. It's the first way Pensando has decided to use it. And so we have this card, it can be plugged into a host, it has two network interfaces. So it can be used as a network adapter. But in reality, because the card is fully programmable and it has several processors inside, it can be used to implement very sophisticated services. Things that you wouldn't even dream of doing with the typical network adapter, with a typical NIC. So in particular, this card, this ASIC contains a sizable amount of memory. Right now we have two sizes four, an eight gig but we are going to have versions of the card with even larger memory. Then it has some specialized hardware for specific functions like cryptographic functions, compression, computation of CRCs and if sophisticated queueing system with packet buffer with the queuing system to end the packets that have to go out to the interfaces or coming from the interfaces. Then it is several types of processors. It has generic processors, specifically arms, arm processors that can be programmed with general purpose languages. And then a set of processors that are specific for packet processing that are organized in a pipeline. In those, idea to be programmed with P4. We can very easily map a P4 program, on those pipeline of processor. So that's where Pensando is leveraging P4, is the language for programming those processes that allow us to process packets at the line rate of our 200 gigabit interfaces that we have in the card. >> Great. So Mario, what about from a customer viewpoint? Do they need to understand you know, how to program in P4, is this transparent to them? What's the customer interaction with it? >> Oh yeah, not at all. The Pensando platform, Pensando is offering a platform that is a completely turnkey solution. Basically the platform, first of all, the platform has a controller with which the user interacts, the user can configure policies on this controller. So using an intent based paradigm, the user defines policies that the controller is going to push those policies to the cards. So in your data center in your horse, in your data center, you can deploy thousands of those cards. Those cards implement distributed services. Let's say, just to give a very simple example, a distributed stateful firewall implemented on the all of those cards. The user writes a security policy, says this particular application can talk to these other particular application, and then translate it into configuration for those cards. It's transparently deployed on the cards that start in force the policies. So the user can use this system at this very high level. However, if the user has more specific needs, then the system, the platform offers several interfaces and several API's to program the platform through those interfaces. So the one at the highest level, is a REST API to the controller. So if the customer has an orchestrator, they can use that orchestrator to automatically send policies to the controller. Or if a customer already have their own controller, they can interact directly with the DSCs with the cards on the horse, with another API's that's fully open, is based on GRPC. And in this way, they can control the cards directly. If they need something even more specific, if they need a functionality that Pensando doesn't offer on those card, hasn't already ever written software for the cards, then customers can program the card, and the first level at which they can program it is the ARM processors. We have ARM processors, those are running in version of Linux, so customers can program it by writing C-code or Python. But if they have very specific needs, like when they write a software for the ARM processor, they can leverage the P4 code that we have already written for the card for those specialized packet processors. So they can leverage all of the protocols that our P4 program is already supported. And by the way because that's software, they can pick and choose in a Manga library of many different protocols and features we support, and decide to deploy them and then integrate them in their software running on the ARM processor. However, if they want to add their own proprietary protocols, if they want, if they need to execute some functionalities at very high performance, then they that's when they can write P4 code. And even in that case, we are going to make it very simple for them. Because they don't have to write everything from scratch. They don't have to worry about how to process AP packets, how to terminate TCP, we have to solve the P4 code for them. They can focus just on their own feature. And we are going to give them a development environment that allows them to focus on their own little feature and integrate it with the rest of our P4 program. Which by the way, is something that P4 is not designed for. P4 is not designed for having different programmers, write different pieces of the program and put them together. But we have the means to enable this. >> Okay, interesting. So, you know, maybe bring us inside a little bit, you know the P4 community, you're very active in it, when I look online, there's a large language consortium, many of, you know, all the hardware and software companies that I would expect in the networking space are on that list. So what's Pensando's participation in the community? And you were just teasing through, you know, what does P4 do and then what does Pensando, maybe enable, you know, above and beyond what, you know, P4 just does on its own? >> Yeah, so yes Pensando is very much involved in the community. There has been recently an event, online event that substituted the yearly P4 workshop. It was called the P4 expert round-table series. And Pensando had very strong participation. our CTO, Vipin Jain, had the keynote speech. Talking about how P4 can be extended beyond packet processing. P4, we said, has been designed for packet processing, but today, there are many applications that require message processing, which is more sophisticated then. And he gave a speech on how we can go towards that direction. Then we had a talk that was resulting from a submission that was reviewed and accepted on in fact, the architecture of our ASIC, and how it can be used to implement many interesting use cases. And finally, we participated into a panel in which we discussed how to use P4 in mix-ins Martin at the edge of the network. And there we argued with some use cases and example and code, how before it needs to be extended a little bit because NICs have different needs and open up different opportunities rather than switches. Now P4 was never really meant only for switches. But if we looked at what happened, the community has worked mostly on switches. For example it is defined that what is called the PSA, portable switch architecture. And we see that the NICs have an edge devices, have a little bit different requirements. So, one of the things we are doing within the communities working within one of the working groups, is called the architecture work group. And they are working in there to create the definition of a PNA, Portable NIC Architecture. Now, we didn't start this activity, this activity has started already in 2018. But it did slow down significantly, mostly because there wasn't so much of a push. So now Pensando coming on the market with this new architecture really gave new life to this activity. And we are contributing, actively we have proposed a candidate for a new architecture which has been discussed within the community. And, you know, just to give you an example, why do we need a new architecture? Because if you think of the switch, there are several reasons but one, it's very intuitive. If you think of a switch, you have packets coming in, they've been processed and packets go out. As we said before, there's the PMA then sorry, PSA architecture is meant for these kinds of operation. If you think of a NIC, it's a little bit different because yes, you have packets coming in, and yes, if you have multiple interfaces like our card, you might take those packets and send them out. But most likely what you want to do, you want to process those packets, and then not give the packets to the host. Otherwise the host CPU will have to process them again, to pass them again. You want to give some artifacts to the host, some pre-processed information. So you want to, I don't know take those packets for example, assemble many TCP messages and provide a stream of bytes coming out of this TCP connection. Now, these requires a completely different architecture, packets come in, something else goes out. And goes out, for example, through a PCI bus. So, you need the some different architecture and then you will need in the P4 language, different constructs to deal with the fact that you are modifying memory, you are moving data from the card to the host and vice versa. So again, back to your question, how are we involved in the workgroups? We are involved in the architecture workgroup right now to define the PNA, the Portable NIC Architecture. And also, I believe in the future we will be involved in the language group to propose some extensions to the language. >> Excellent. Well, Mario, thank you so much for giving us a deep dive into P4, where it is and you know some of the potential futures for where it will go in the future. Thanks so much for joining us. >> Thank you. >> Alright. I'm Stu Miniman, thank you so much for watching the Cube. (gentle music)

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Welcome back to San Francisco, everybody. My name is David Lantz. I'm here with my co host John Troia. This is Day three of V M World 2019 2 sets. >> This is >> our 10th year at the M. World Cube is the leader in live enterprise tech coverage. Marry on Blondie is here. He's the C m o and chief evangelist that 10 tree by DDN Yes, sir. He's joined by Graham Breezes The Field CTO at 10 Tree also by DDN Recent acquisition jets Great to see you. >> Likewise, as they say, we're back. I like I like to call it a hibernation in the sense that people may have not known where did Ian or 10 Trias and Tension by Dede and, as the name implies, were acquired a year ago at the M World August 31st of 2018. And in the year since, we've been ableto invest in engineering support, my joining the company in marketing to take this solution, we've been able to save thousands of customers millions of man hours and bring it to a larger number of users. Way >> first saw 10 tree, we said, Wow, this is all about simplification. And Jonah Course you remember that when you go back to the early early Dick Cube days of of'em World, very complex storage was a major challenge. 10 Tree was all about simplifying that. Of course, we know DDN as well is the high performance specialist and have worked with those guys for a number of years. But take >> us >> back Married to the original vision of 10 Cherie. Is that original vision still alive? How was it evolved? >> Well, I'd say that it's, ah, number one reason why we're a part of the DD and family of brands because, as, ah, portfolio company, they're looking good. Bring technologies. I'm the marketing guy for our enterprise or virtual ization audience, and the product sets that cover high performance computing have their own audience. So for me, I'm focused on that. Graham's also focused on that, and, uh, really what continues to make us different today is the fact we were designed to learn from the beginning to understand how virtual machines end to end work with infrastructure. And that's really the foundation of what makes us different today. The same thing, right? >> So from the very beginning we were we were built to understand the work clothes that we service in the data center. So and that was virtual machines. We service those on multiple hyper visors today in terms of being able to understand those workloads intrinsically gives us a tremendous capability. Thio place. I owe again understanding that the infrastructure network storage, hyper visor, uh, weaken view that end end in terms of a latent a graph and give customers and insight into the infrastructure how it's performing. I would say that we're actually extending that further ways in terms of additional workload that we're gonna be able to take on later this year. >> So I know a lot >> of storage admits, although I I only play one on >> TV, but, uh, no, consistently >> throughout the years, right? 10 tree user experiences that is the forefront there. And in fact, they they often some people have said, You know what? I really want to get something done. I grab my tent Reeboks and so it can't talk. Maybe some examples of one example of why the user experience how the user experiences differ or why, why it's different. >> I'll start off by saying that I had a chance being new to the company just two weeks to meet a lot of 10 tree users. And prior to taking the job, I talkto us some folks behind the scenes, and they all told me the same thing. But what I was so interested to hear is that if they didn't have 10 tree, they'd otherwise not have the time to do the automation work, the research work, the strategy work or even the firefighting that's vital to their everyday operations. Right? So it's like, of course, I don't need to manage it. If I did, I wouldn't be able to do all these other things. And I think that's it. Rings true right that it's hard to quantify that time savings because people say, 0 1/2 of it. See, that's really not much of the greater scheme of things. I don't know. 1/2 50. Working on strategic program is a huge opportunity. Let's see >> the value of 10 tree to our end users and we've heard from a lot of them this week actually spent a fantastic event hearing from many of our passionate consumers. From the very beginning. We wanted to build a product that ultimately customers care about, and we've seen that this week in droves. But I would say the going back to what they get out of it. It's the values and what they don't have to do, so they don't have to carve up ones. They don't have to carve up volumes. All they have to do is work with the units of infrastructure that air native to their environment, v ems. They deal with everything in their environment from our virtual machine perspective, virtual machines, one thing across the infrastructure. Again, they can add those virtual machines seamlessly. They can add those in seconds they don't have toe size and add anything in terms of how am I gonna divide up the storage coming in a provisional I Oh, how am I going to get the technical pieces right? Uh, they basically just get place v EMS, and we have a very simplistic way to give them Ah, visualization into that because we understand that virtual machine and what it takes to service. It comes right back to them in terms of time savings that are tremendous in terms of that. >> So let's deal with the elephant in the room. So, so 10 tree. We've talked about all the great stuff in the original founding vision. But then I ran into some troubles, right? And so what? How do you deal with that with customers in terms of just their perception of what what occurred you guys did the eye poets, et cetera, take us through how you're making sure customers are cool with you guys. >> I'm naturally, glass is half full kind of guy from previous, uh, times on the Cube. The interesting thing is, not a lot of people actually knew. Maybe we didn't create enough brand recognition in the past for people to even know that there was a transition. There were even some of our customers. And Graham, you can pile on this that because they don't manage the product every day because they don't have to. It's kind of so easy they even for gotten a lot about it on don't spend a lot of time. I'd say that the reason why we are able to continue. Invest today a year after the acquisition is because retaining existing customers was something that was very successful, and to a lot of them, you can add comments. It wasn't easy to switch to something. They could just switch to something else because there's no other product, does these automatic things and provides the predictive modeling that they're used to. So it's like what we switched to so they just kept going, and to them, they've given us a lot of great feedback. Being owned by the largest private storage company on planet Earth has the advantages of strong source of supply. Great Leverett reverse logistics partnerships with suppliers as a bigger company to be able to service them. Long >> trial wasn't broke, so you didn't need to fix it. And you were ableto maintain obviously a large portion of that customer base. And what was this service experience like? And how is that evolving? And what is Dede and bring to the table? >> So, uh, boy DD and brings so many resources in terms of bringing this from the point when they bought us last year. A year ago today, I think we transition with about 40 people in the company. We're up about 200 now, so Ah, serious investment. Obviously, that's ah have been a pretty heavy job in terms of building that thing back up. Uh, service and support we've put all of the resource is the stated goal coming across the acquisition was they have, ah, 10. Tree support tender by DNC would be better than where 10 tree support was. We fought them on >> rate scores, too. So it's hard to go from there. Right? And >> I would say what we've been doing on that today. I mean, in terms of the S L. A's, I think those were as good as they've ever been from that perspective. So we have a big team behind us that are working really hard to make sure that the customer experience is exactly what we want. A 10 tree experience to be >> So big messages at this This show, of course, multi cloud kubernetes solving climate change, fixing the homeless problem in San Francisco. I'm not hearing that from you guys. What's what's your key message to the VM world? >> Well, I personally believe that there's a lot of opportunity to invest in improving operations that are already pretty darn stable, operating these environments, talking to folks here on the floor. These new technologies you're talking about are certainly gonna change the way we deploy things. But there's gonna be a lot of time left Still operating virtualized server infrastructure and accelerating VD I deployments to just operationalized things better. We're hoping that folks choose some new technologies out there. I mean, there's a bill was a lot of hype in past years. About what technology to choose. We're all flash infrastructure, but well, I'd liketo for the say were intelligent infrastructure. We have 10 and 40 get boards were all flash, but that's not what you choose this. You choose this because you're able to take their operations and spend more your time on the apse because you're not messing around with that low level infrastructure. I think that there's a renaissance of, of, of investment and opportunity to innovate in that space into Graham's point about going further up the stack. We now have data database technology that we can show gives database administrators the direct ability to self service their own cloning, their own, staging their own operations, which otherwise would be a complex set of trouble tickets internally to provision the environment. Everyone loves to self service. That's really big. I think our customers love. It's a self service aspect. I see the self service and >> the ability to d'oh again, not have to worry about all the things that they don't have to do in terms of again not having to get into those details. A cz Morrow mentioned in terms of the database side, that's, ah, workload, the workload intelligence that we've already had for virtual machines. We can now service that database object natively. We're going to do sequel server later this year, uh, being ableto again, being able to see where whether or not they've got a host or a network or a storage problem being able to see where those the that unit they're serving, having that inside is tremendously powerful. Also being able the snapshot to be able to clone to be able thio manage and protect that database in a native way. Not having to worry about, you know, going into a console, worrying about the underlying every structure, the ones, the volumes, all the pieces that might people people would have to get involved with maybe moving from, like, production to test and those kinds of things. So it's the simplicity, eyes all the things that you really don't have to do across the getting down in terms of one's the volumes, the sizing exercises one of our customers put it. Best thing. You know, I hear a lot of things back from different customer. If he says the country, the sentry box is the best employee has >> I see that way? Reinvest, Reinvest. I haven't heard a customer yet that talks about reducing staff. Their I t staff is really, really critical. They want to invest up Kai throw buzzword out there, Dev. Ops. You didn't mention that it's all about Dev ops, right? And one thing that's interesting here is were or ah, technology that supports virtual environments and how many software developers use virtual environments to write, test and and basically developed programmes lots and being able to give those developers the ability to create new machines and be very agile in the way they do. Their test of is awesome and in terms of just taking big amounts of data from a nap, if I can circling APP, which is these virtual machines be ableto look at that on the infrastructure and more of her copy data so that I can do stuff with that data. All in the flying virtualization we think of Dev Ops is being very much a cloud thing. I'd say that virtual ization specifically server virtualization is the perfect foundation for Dav ops like functionality. And what we've been able to do is provide that user experience directly to those folks up the stacks of the infrastructure. Guy doesn't have to touch it. I wanted to pull >> a couple of threads together, and I think because we talked about the original vision kind of E m r centric, VM centric multiple hyper visors now multi cloud here in the world. So what >> are you seeing >> in the customers? Is that is it? Is it a multi cloud portfolio? What? What are you seeing your customers going to in the future with both on premise hybrid cloud public. So where does where does 10 tree fit into the storage portfolio? >> And they kind of >> fit all over the map. I think in terms of the most of the customers that we have ultimately have infrastructure on site and in their own control. We do have some that ultimately put those out in places that are quote unquote clouds, if you will, but they're not in the service. Vendor clouds actually have a couple folks, actually, that our cloud providers. So they're building their own clouds to service customers using market. What >> differentiates service is for serving better d our offerings because they can offer something that's very end end for that customer. And so there's more. They monetize it. Yeah, and I think those type of customers, like the more regional provider or more of a specialty service provider rather than the roll your own stuff, I'd say that Generally speaking, folks want tohave a level of abstraction as they go into new architecture's so multi cloud from a past life I wrote a lot about. This is this idea that I don't have to worry about which cloud I'm on to do what I'm doing. I want to be able to do it and then regards of which clouded on it just works. And so I think that our philosophy is how we can continue to move up the stack and provide not US access to our analytics because all that analytic stuff we do in machine learning is available via a P I We have ah v r o plug in and all that sort of stuff to be able allow that to happen. But when we're talking now about APS and how those APS work across multiple, you know, pieces of infrastructure, multiple V EMS, we can now develop build a composite view of what those analytics mean in a way that really now gives them new inside test. So how can I move it over here? Can I move over here? What's gonna happen if I move it over here over there? And I think that's the part that should at least delineate from your average garden variety infrastructure and what we like to call intelligent infrastructure stopping that can, Actually that's doing stuff to be able to give you that data because there's always a way you could do with the long way. Just nobody has time to do with the long way, huh? No. And I would actually say that you >> know what you just touched on, uh, going back to a fundamental 10 tree. Different churches, getting that level of abstraction, right is absolutely the key to what we do. We understand that workload. That virtual machine is the level of abstraction. It's the unit infrastructure within a virtual environment in terms of somebody who's running databases. Databases are the unit of infrastructure that they want to manage. So we line exactly to the fundamental building blocks that they're doing in those containers, certainly moving forward. It's certainly another piece we're looking. We've actually, uh I think for about three years now, we've been looking pretty hard of containers. We've been waiting to see where customers were at. Obviously Of'em were put. Put some things on the map this week in terms of that they were pretty excited about in terms of looking in terms of how we would support. >> Well, it certainly makes it more interesting if you're gonna lean into it with someone like Vienna where behind it. I mean, I still think there are some questions, but I actually like the strategy of because if I understand it correctly of Visa, the sphere admin is going to see the spear. But ah ah, developers going to see kubernetes. So >> yeah, that's kind of cool. And we just want to give people an experience, allows them to self service under the control of the I T department so that they can spend less time on infrastructure. Just the end of the I haven't met a developer that even likes infrastructure. They love to not have to deal with it at all. They only do it out. It assessed even database folks They love infrastructural because they had to think about it. They wanted to avoid the pitfalls of bad infrastructure infrastructures Code is yeah, way we believe in that >> question. Go to market. Uh, you preserve the 10 tree name so that says a lot. What's to go to market like? How are you guys structuring the >> organizational in terms of, ah, parent company perspective or a wholly owned subsidiary of DDN? So 10 tree by DDN our go to market model is channel centric in the sense that still a vast majority of people who procure I t infrastructure prefer to use an integrator or reseller some sort of thing. As far as that goes, what you'll see from us, probably more than you did historically, is more work with some of the folks in the ecosystem. Let's say in the data protection space, we see a rubric as an example, and I think you can talk to some of that scene where historically 10 Tree hadn't really done. It's much collaboration there, but I think now, given the overall stability of the segment and people knowing exactly where value could be added, we have a really cool joint story and you're talking about because your team does that. >> Yeah, so I would certainly say, you know, in terms of go to market Side, we've been very much channel lead. Actually, it's been very interesting to go through this with the channel folks. It's a There's also a couple other pieces I mentioned you mentioned some of the cloud provider. Some of those certainly crossed lines between whether they're MSP is whether they are resellers, especially as we go to our friends across the pond. Maybe that's the VM it'll Barcelona discussion, but some of those were all three, right? So there are customer their service providers there. Ah ah, channel partner if you want terms of a resellers. So, um, it's been pretty interesting from that perspective. I think the thing is a lot of opportunity interview that Certainly, uh, I would say where we're at in terms of, we're trying to very much. Uh, we understand customers have ecosystems. I mean, Marco Mitchem, the backup spaces, right? Uh, customers. We're doing new and different things in there, and they want us to fit into those pieces. Ah, and I'd certainly say in the world that we're in, we're not tryingto go solve and boil the ocean in terms of all the problems ourselves we're trying to figure out are the things that we can bring to the table that make it easier for them to integrate with us And maybe in some new and novel, right, >> So question So what's the number one customer problem that when you guys hear you say, that's our wheelhouse, we're gonna crush the competition. >> I'll let you go first, >> So I'd say, you know, if they have a virtualized environment, I mean, we belong there. Vermin. Actually, somebody said this bed is the best Earlier again. Today in the booze is like, you know, the person who doesn't have entries, a person who doesn't know about 10 tree. If they have a virtual environment, you know, the, uh I would say that this week's been pretty interesting. Lots of customer meetings. So it's been pretty, pretty awesome, getting a lot of things back. But I would say the things that they're asking us to solve our not impossible things. They're looking for evolution's. They're looking for things in terms of better insights in their environment, maybe deeper insights. One of the things we're looking to do with the tremendous amount of data we've got coming back, Um, got almost a million machines coming back to us in terms of auto support data every single night. About 2.3 trillion data points for the last three years, eh? So we're looking to make that data that we've gotten into meaningful consumable information for them. That's actionable. So again, again, what can we see in a virtual environment, not just 10 tree things in terms of storage of those kinds of things, but maybe what patches they have installed that might be affecting a network driver, which might affect the certain configuration and being able to expose and and give them some actionable ways to go take care of those problems. >> All right, we gotta go marry. I'll give you. The last word >> stated simply if you are using virtual, is a Shinto abstract infrastructure. As a wayto accelerate your operations, I run the M where, if you have ah 100 virtual machine, 150 virtual machines, you could really benefit from maybe choosing a different way to do that. Do infrastructure. I can't say the competition doesn't work. Of course, the products work. We just want hope wanted hope that folks could see that doing it differently may produce a different outcome. And different outcomes could be good. >> All right, Mario Graham, Thanks very much for coming to the cubes. Great. Thank you so much. All right. Thank you for watching John Troy a day Volante. We'll be back with our next guest right after this short break. You're watching the cube?

>> From Boston, Massachusetts, it's theCUBE, covering LiveWorx 18. Brought to you by PTC. >> Welcome back to Boston, everybody, to the LiveWorx show, hashtag LiveWorx with an "x" at the end. You're watching theCUBE, the leader in live-tech coverage. My name is Dave Vellante, and I'm with my co-host Stu Miniman. Mario Armstrong is here. He's a two-time Emmy winner, contributor to NBC today. He's the creator of the "Never Settle Show". He's an NPR contributor. >> Yep. >> And the host of LiveWorx. >> Yeah! >> Thanks so much coming on theCUBE. >> Yeah, it's a pleasure to see both of you. Good to see you too, Stu. Thanks for having me on the show. >> So yeah, this morning, a lot of action-- >> Yes. >> First of all, I tweeted out, that was like an Olympic opening, I mean-- >> That open was phenomenal. I mean, an LED-lit troop, full LED uniforms on, being acrobatic, what you can't see behind the scenes, by the way, 'cause you think it's kind of like Cirque du Soleil type of thing, with like, tech, but what you don't see are, like, these three other people that are way in the back behind the scenes, going up, scaling up and down like this truss that's like dropping them or raising them. It's just, the performance was phenomenal. >> Yeah, it was really great. And you kicked it off... 6,000 plus people here. >> Yes. >> You said the largest digital transformation conference on the planet, which of course, we were joking. Everybody says their digital-- >> Yeah. (laughs) >> But this really is digital transformation, isn't it? >> It's a lot that's taking place. I mean when you think about manufacturing, smart manufacturing, when you think about how you're trying to accelerate processes and you start looking at where things were like 20 or 30 years ago and how physical things had to be and how you actually had to, like, maybe even work on a thing then leave it, go to another place, report on it, come back to it, tweak it, and so now when you start seeing the merging of AI, VR, and so you're taking the physical and the human, and you're putting these... and the virtual, and you're putting these things together, you're seeing things like what PTC is showing us today. I mean, some of the demonstrations that I saw were absolutely mind blowing in terms of the acceleration of the process that you can actually get things done with how they're merging the different technologies and integrating them together. >> Yes, Stu and I, we're talking earlier, it's hard to get your head around this whole IOT, industrial IOT, there's just so many segments, it's so fragment that, and it's-- >> Yeah. >> It's enormous, it's almost impossible to size, I mean it's trillion dollars, this whole economy of its own. What are your takeaways on just that whole space? >> You know, a lot of what I focus on, too, when I'm doing everything from NBC or NPR and stuff like that is on the consumer impact. So I'm looking at the consumer side but I'm also an entrepreneur, so I'm thinking about what's happening on the business side. And when I see on both ends, you're absolutely right. The field is enormous when you really think about it. Whether you want to look at how we can replace old school manufacturing and how this is going to transfer... That's a whole sector just in it of itself. We haven't even now talked about, you know, AI for children or for (incoherent) or for the health and wellness sector, whole other sector that's looking at IOT and the power of that. I mean, being able to look at.. I was just in one of the other, in the deluxe lounge and I was checking out one of our fun games. It's called Sphero. It's a consumer game, but its a small ball that you control through VR and AR on your phone, but you can actually use the phone to program things in real time to make it respond in real time. So all of these things together, to me, start to paint this large ecosystem because now you have kids that are growing up using devices and using technologies that we're just starting to get our hands on but this is how they're solving problems and thinking about things already. So when this economy and this ecosystem starts to mature, you're going to have a ready-made audience that's already been exposed to 90% of this. >> Well, and Stu I wonder if you could chime into it, it makes me think that these worlds, even though consumer and industrial are so seemingly different, it seems like parts of them, anyway, adjacencies are coming together. >> Absolutely. And there's always going to be that... There's always going to be... Look, when I talk about innovation and whether you look at Dr. Hill, who's speaking here today, Dr. Linda Hill from Harvard and others, when I look at it, she calls it creative abrasion, like the difference between brainstorming and actually utilizing new ideas to create new concepts. I call it hybrid design. Normally, it's taking something that you know exists and then taking two things that don't seem to go together-- that's normally where you find creation. I don't like to say disruption, I like to say creation. >> Yeah, actually there's a good friend of mine that I work with and I worked at EMC, he called it venn diagram innovation. >> Oh, that's it! That's it! >> I take a few things and I put it together and we were talking about the consumer side-- >> Yeah! >> We've looked so many technologies, you get the scale usually from the consumer. When we look at things like flash in all of our devices-- >> That's right. >> Really enabled the enterprise to do things. The VR and AR is something that we've actually got some folks on the team that are heavy gamers that they're the ones that I go to when I want to learn, "Okay, what's the cutting-edge--" >> 'Cause they've already been in it. That's right. >> They're on their Steam, they're doing everything. >> That's right. >> They sort everything out. You leverage a lot of technology in how you really get your message out there. Talk a little about how you think of media these days. >> Oh, it's completely different. I mean, when we're looking at how media is even utilized in these new technologies, you know, our talk show is a talk show that we shoot in Nasdaq Studios, so it's shot in New York City, it's called the "Never Settle Show", it's a weekly one-hour live stream talk show, so we get and appreciate what you have to go through. These guys are pros by the way. (Dave and Stu laugh) Yeah, they're pros 'cause this is not easy to do. >> It's a minor miracle, right? Every time. >> (laughs) It's not easy to do at all. And so a lot of kudos to you and the team behind the scenes that make that happen. >> Thank you. >> With that being said, it's a great time if you have an expertise or if you have content to share especially in a live scenario because now you can start to really utilize other technologies within that. For example, we kind of claim ourselves to be one of the most interactive talk shows out there. What we do in our show is we're using other technologies, bringing them together to create real time conversations. So how that practically plays out is I'll have a guest on the show, we'll be talking, I'll put up a screen of three options and people can vote right then and there while they're watching in stream and you'll see which of what they want me to do next. I'll say something like, "Which thing is most appealing... Which topic do you want us to talk about next?" And they'll actually vote in real time and then the control room in everyone doesn't know what the answer's going to be, but we're all waiting for the answer and then when the popular vote comes out, few seconds later, we scramble and adjust to that. That's real time television, giving viewers what they really want in real time, using different technologies. So that's this hybrid approach. We can be a standard show and just do... talk and have that format, or we could really be looking at things that we could integrate in other technologies that would enhance the viewing experience and make it much more productive. >> Well you're actually affecting the, you call it "creation" as supposed to "disruption" of this new media industry, I mean, you've seen... I saw a stat the other day that cost the New York Times 200 million dollars to run a news desk. (Mario laughs) You're seeing, you know, billionaires buy up, you know, the Boston Globe, the Washington Post-- >> Yes, that's right. >> The industry is transforming in a huge way. You're seeing, you know, Facebook backlash with fake news. What's your senses as to what's going on in the media business? Obviously you're "creating", "disrupting", whatever you like to call it, sure. What do you see is the future of the media business? >> Well, I mean I think it's going to become something where the end reader, the end viewer has more control. Ultimately, that's... the problem with most systems and most structures is when people want to hold the control and not share because whether that's ego, whether they're worried about intellectual property loss, or whether they really think that the market's going to swallow them up.... Now I'm not saying, obviously you give away all your secret sauce, but what I am saying is when you start thinking from that small limiting position, you've already lost the game. And so what I think is going to happen, yes, you have big people buying a lot of media and there's a lot of discussion in politics about whether or not, you know, billionaires buying media are problems and what that's going to mean in terms of the message that's going to be reported to people, that's going to always be an issue, but I think even with that, that's why it's even more empowering that the individuals are taking more control over their own narrative. And that's why I think you've seen social media, Instagram video, Instagram talking about going to sixty minutes in it's video, not just a minute, for publishers, I think the power's now more in the person's hand to really pick and choose and so they vote with their eyeballs, they vote with their engagement, they vote with their interactivity. And so I think no matter what happens on the big end, people are going to be able to create and get the stories that they want to be able to get. >> Well we're big believers of that, Stu, and we're decentralized media and we really believe that there's got to be an incentive system to put the power back in the hands of the users to control their data. >> This is how it works. >> Right? I mean... >> Yeah. And, Mario, so we've talked about the tech and your show "Never Settle" actually won an Emmy for the interactivity nature of it? >> Yeah. It did. >> But talk to the people and passion, how that fits into "Never Settle". >> Yeah, so it's a blending. So what we try to do on our show is blend how you can leverage technology to move forward on your passion. But you can't use technology to move forward on your passion if you don't know what your passion is. So a lot of our discussions really work more around, "how do we get you to think differently"? How do we, you know... our vision for our company is to motivate people across the globe to never settle. How we do that through our mission is that we inspire the humans spirit, we want to teach lessons that matter and we want to uncover new perspectives. What that means, tangibly, is that when you watch our show, you should be having notes. You should be, like... our show is meant for you to want to take notes so that you actually know the process. What people are missing for the most part today is they see how to maybe start something or they see how someone else did and how they succeeded or how they failed, but they don't get the in between, the recipe. And so the more we can be sharing about the process about someone's success or, even better, someone's failure, 'cause that's where you learn more and you get more uncomfortable, makes you more comfortable, it's a blending of those two things of getting your mental position and getting you stronger mentally and building up your resilience so that you can actually go find your purpose, be happier in your life, but then use technology to accelerate. Like, that's the, as Jim put, like, you know, put gasoline and make it fast or make it go quicker. And so I think the blending of the two, again, a hybrid... Even how we approach our content is that. So we'll have everyone from tech luminaries on the show but also we'll just have everyday folks that have really proven success, like these people deserve attention but they're not maybe, quote on quote, big-names. >> And this idea of combinatorial innovation, you certainly heard Jim Heppelmann talking about that today with machines that are powerful and computers that are fast and can do things repetitively and then humans, which are creative. I like that theme. >> You can't do it any other way, I mean, this is why, you know, it's determination and direction. Your team needs to be determined but also have the direction. You need to have what I call the three P's. You need to have your passion in place. Like, what are you ultimately passionate about as a team? As an organization? What are you driving towards? What's your "why"? And then once you have that, then you can start to really push through on the perseverance. You're going to bump your head. You're going to fail fast. A great tech term, I love flipping that tech term because we learn in programming to fail to quick so that we can find the bugs fast and correct our course really quick. So that persistence happens. And then, the hardest part is you got to have some patience. Because then you have to kind of sit back. Let the market also play. Let the universe come around. Sometimes we're ahead. Sometimes we're behind. But we need to have a little bit of that patience to have some reflection to see where we are, so I think, you know, now is really just a great time for a lot of people that are looking to really figure out where they can make their moves... the opportunities that keep creating themselves in IOT are endless. I don't care if you're talking from someone that's a graphic designer all the way up to an engineer or a coder, to marketing and sales, like there's so many different facets of this ecosystem and opportunity now. >> I love that, Mario. Patient, passion, persistence, patience-- >> Yes. >> The three P's kind of start with why, the old-- >> Yeah. Simon Sinek. That's right. >> People don't buy what you do. They buy why you do it. >> That's right. >> Break stuff. >> (laughs) Love that. Break stuff. >> And don't give up. Don't give up. (Mario laughs) >> No, it's, you know... it's because what we're trying to do, if you really wanted to have action, you want to take complex things and you want to pull them together in a hybrid scenario and start to bang upon them. As opposed to the other idea of planning, planning, planning, planning, you actually want to practice, practice, practice, practice. That's what's going to get you there fast. So I just think that with a lot of the technologies it can be overwhelming to people 'cause they start to hear so much so that's why I say it comes back to, "What's your purpose?" If you can stay focused on why you're doing what it is you're doing, you'll know which technologies to pay more attention to. You'll know where your curiosity should veer more into. You'll study the things that you need to really study. And then you'll accelerate faster because you've identified your niche. It's like having a, you know, an Italian restaurant. You're not just, you know... somebody's going to come by and present to you... Some sales rep is going to come by and present to you, like, beer that's not a fit for like Italian restaurant, you know, like, I know that's not for me instantly. As opposed to being pulled in so many directions, which is what the danger of all this technology can do, is it can overwhelm us and pull us into so many directions that we want to go and pursue the hottest new trend or the hot thing. If we come back to our "why", we're always going to be secure. >> That's a great point, I mean there are an infinite opportunities of purposes in this world. >> Yes. >> It's sometimes hard to get a grasp on things and really focus. But you're seeing some of this successful projects really do start with a main spring and a focus and a purpose. >> Yeah. >> And a mission. >> It does. I mean, that's where it all becomes. I mean, it has to start there in order to get other people on board with your dream, whether you're the leader of the organization or the leader of a project. And, you know, I just feel that for many people, they are at an age where they have been in this business for quite some time. They've seen a lot of things evolve. Accepting change and, like Jim had said today, preparing to change is one of the best keys of information that you can take away because we all have the skill, the talent, the ability, it's just a matter or not, are we willing to adjust or are we... do we want to do status quo. >> Awesome. Hey, you're a clear thinker, articulate, you look great. Thanks so much for coming to theCUBE. >> (laughs) Aw man, Dave and Stu, it's been a pleasure. Thank you so much for having me on theCUBE. >> Our pleasure. >> This has been awesome. >> Alright, keep it right there, buddy, we'll be back from LiveWorx with our next guest right after this short break. You're watching theCUBE. We'll be right back.

(upbeat electronic music) >> Voiceover: Live from New Orleans. It's theCUBE, covering VeeamON 2017. Brought to you by Veeam. >> We're back, Mario Angers is here. He's the senior manager of systems at the University of British Columbia. Welcome back to theCUBE, good to see you. >> Thank you, thank you. >> So how's VeeamON going? >> So far, so good. It's fabulous, actually. I love the event, cause it's not so big that you can't talk to a lot of people, and it's small enough that you get to know a lot of different folks. >> Yeah, it feels bigger, they're saying the number's 3,000. It feels bigger than that to me, but at the same time it is kind of intimate. >> Yeah no, I went to their first event, so certainly this is very different than what it was like. I think their first event was 2014? So, yeah, that's very good. >> So, tell us what's going on up at British Columbia. What's hot these days? >> Well, I spoke to this a little bit yesterday during the partner session, right? So, British Columbia's in a bit of unique position, because we have laws that prevent us from storing data outside Canada, right? So up until recently, we didn't have any of the large service providers, so we had to basically, to some degree, reinvent the wheel. So if wanted to provide or consume cloud, we had to basically build it, which is what the University of British Columbia did a few years ago. And, because we're the largest in BC, we were doing it at scale already, so we were approached by an organization inside British Columbia called BCNET, which basically services all the other higher ed, and they asked us if we wanted to provide cloud services to the community, and we've been doing this for almost three years now. >> Dave: As a partner to BCED? >> Yeah, to BCNET, yeah. >> Dave: BCNET, yeah. >> So we're basically the service operator, they're the service provider, right, but we do everything, we take care of the marketing, the communication. >> And Mark, could you walk us through, what's that stack look like? I did an interview with the OpenStack Summit with a Massachusetts higher ed cloud that they built that used OpenStack as the underlying piece. What's yours built on? >> So we went with, we're a VMware shop. So we went with the cloud directory as the front end basically, but the back end is a combination of Cisco servers, HP servers, net op storage, HP storage, data domain for our backup. Of course we use Veeam for our backup software, and then it's VMware stack end-to-end. >> Okay, it was funny, the gentlemen that I interviewed, actually, was the one who created VCD, when he was at VMware, so I'm just curious to see your viewpoint. One of the things we use to say is, cloud is not virtualization plus, but if you build a stack, if you can have kind of the orchestration and management pieces... So you feel you have a cloud, what differentiates what you have today, versus what you could have built five years ago? >> Well, I think five years ago, it would have been really challenging to provide the services in a self service capability to our end users. So today we can do that. The only involvement we have is we provision a virtual data center for our end user, and then it's self service from there, for them. We also use NSX, which is also a VMware product, so it's self service end-to-end. >> And how has your availability become better with what you have today versus what you had before? >> Veeam is a significant partner of ours, so we've been a Veeam customer for probably five or six years now, on the backup and restore side, probably about four years, and I would say it's made our jobs a lot easier. So historically our legacy backup system was just a bear and a monster to manage. So it required a huge amount of time to not just manage, but understand how it was done. With Veeam, they've really simplified that process, and we have a very large environment, and we basically have one guy managing backup. >> So it used to be, well that's pretty good productivity. So it used to be the conversation around, "Well, we're meeting our backup within the window." That was sort of the challenge. >> Mario: Yep. >> And now increasingly, it's, we want to get as close as RPO zero as possible for certain apps, not everything, as it's too expensive, and we want a much faster recovery time objective. So can you talk to us, first of all, do you converse in those terms with your line of business, and have you been able to affect those metrics? >> So, we're not quite there yet, from a sophistication, or a maturity perspective, We still have a bit of a ways to go to get there. However, can we now guarantee to our folks that we'll be able to bring workloads back within the service level that we have with our customers? Absolutely. So we can provide peace of mind now, knowing that if we lose something we can bring it back very quickly, as it's actually being restored to the production environment. >> So where do you want to go from here? It sounds like you've got the productivity thing nailed. You got one person managing all this, and you're able to meet those SLAs. What's next? >> I would say next for us is, so today we provide what I'll call a managed service around backup. So basically, the team that I manage is looking after backup for all the clients within the service, so our next step is really to provide them the ability to manage that themselves. So we're looking to do that over the summer. Once we do that, then we want to start partnering with Veeam as well and start looking at their Cloud Connect product. We've been in discussions for some time now about how we're going to do that, and that's the evolution of that. And then building on that, we're being also asked to add to the portfolio of services that we provide, and one of those services is disaster recovery as a service. So that's becoming very, very critical to the province. Vancouver is basically like San Francisco or Los Angeles. We live in one of the biggest fault zones in the world, so at one point it will happen. So now we've basically provisioned a data center in the middle of the province where it's outside your quake zone, so now we can start providing those services to our community. >> Could you speak to the relationship with Veeam with the storage arrays that you have? What's the interaction there? >> So when we went to Veeam it was really important that the full integration is there with the storage vendors that we have. So originally we were primarily in that app shop. So in that, integration was in place. So when we started looking at moving off of tape and moving onto disk for backup, we basically narrowed the list down to vendors that also fully integrated with Veeam. So we chose Data Domain, an EMC product. We've been very happy. And just recently we went to RFPing, we basically selected a new vendor for virtualization storage. And the same rules apply. Full integration needs to be in place. We need to be able to know that we're going to be able to read the data off of the storage arrays, and then move it to the backup. Without that integration, there's no guarantees that we can do that successfully. >> So a data demand customer, happy with that as the backup appliance, fast, great data reduction... Didn't EMC get you in a headlock and say, "You got to buy Networker and Avamar," and really push hard? >> Mario: Oh they tried. >> Of course, they did try. >> Okay, so what led to your decision to go with Veeam? >> The complexity of those solutions. So we're not going to reinvent how we're structured or how we're architected just to put a backup solution in place. And if you look at a lot of the other really big vendors in the marketplace today, that's basically the expectation, is okay well, you're built out like this, now you're going to have to do this in order to consume our solution. That just wasn't an option for us. >> And some people would say, "Well I get one thrown to choke and that simplifies things," but you don't buy that. >> Mario: No, not at all. I think it keeps vendors honest if you have more than one. It gives you some leverage to be able to negotiate. And to be quite honest with you, I've yet to find another vendor that provides the level of quality and support that Veeam does. And they're growing as a company, and I expect that things will change to some degree, because that's part of growing. However, so far, the experience that we've had is the same we had four years ago when they were a relatively small company. >> Can you give an example of what resonates with you as customer in terms of that service experience? >> I think as a bunch of IT guys, we think we know everything, right? So when we originally acquired Veeam, we thought, "Yeah, yeah, yeah, we get what you're telling us, but we know better than you do." So we went ahead and implemented based on what we felt was right. It wasn't right. So they didn't come over and say, "Told you so," or "We're not going to help you now, cause you decided to go this way." No, they provided us with all the support we needed in order to actually change what we had done, and there was never any finger pointing or any... It was basically, "You're a partner, we're going to help you be successful." And that's very rare, I think, in the industry today. >> Yeah, really, respecting sort of that you wanted to do it a certain way, and now I learned. >> Yeah, they did try to talk us out of it, but we decided to move in that direction anyway. To me it's like, yeah, it's a fantastic relationship. >> Anything that you've seen here today, or this week, the announcements, that was really interesting and exciting to you? >> Yeah, I think a lot of the things that are coming in Version 10 are going to allow us to expand on the things that we provide to our customers. For example, all the stuff they talk about around availability, primarily disaster recovery stuff, which is such a big thing for us. So I think this is going to add significant value. >> Mario, anything either Veeam or your vendor ecosystem that you're looking for that would make your life easier? You seem to have a pretty opinionated view of what you need. >> So to me is, we're it the business of solving problems. So as a vendor, you're not going to help me solve my problem unless you understand what my problem is. In my experience, I'm not going to say with all vendors, but with a lot of vendors in the past couple of years, is basically the caliber of the sales people I feel have changed. So it used to be that the sales folks used to be pretty knowledgeable about what they sold. Now it feels like all they're trying to do is make their quarter. And as a customer it's becoming frustrating, because I don't want to be sold to. I want someone that's going to help me solve problems, and deliver solutions to my customers. >> You must get a lot of different storage infrastructures, but NetApp is a primary supplier, of course. >> Mario: Yep, it's still very big in our environment. >> We just had NetApp on with Veeam, and they were talking about their relationship. As a customer, how do you find the relationship between Veeam and NetApp? Is there tangible value that you see in that working relationship? How do you interact with those two different companies? >> Oh of course there's tangible value. So we're an enterprise customer, right? And as we scaled within our environment, we came into a bottleneck between Veeam and NetApp. And all we had to do was expose it to both companies, and they worked together to resolve the issue. And I believe it was Version Nine that they released a fix for it. But that's been the experience, is the work that happens behind the scenes, we're not exposed to that, it always creates a positive experience for us in the end. >> We had Dave Russell on earlier from Gartner, and he was talking about pricing, and licensing, and specifically socket-based pricing, and said that that had a big impact on the marketplace. From a customer standpoint, what can you share with us about licensing, pricing, strategies that you employ, and maybe advice for other customers? >> So I think a lot of vendors are starting to try to simplify their licensing. Because if you look, I'm not going to pick on anyone specific, but they had, "Okay well we're going to sell you a number of VMs and then the storage on top of that." And it's like, okay that doesn't make sense. I don't want a PhD in math to be able to calculate how much I'm going to spend for licensing. So give me a model that is easy to manage, and I'm going to know exactly what my cost is, and have a very predictable cost going forward. And I understand Veeam has a couple different model, but they're still very simple. So you're either subscription or you're socket. So to me, just keep it simple. >> Dave: What's your preference? >> Right now it's socket. However, I'm not opposed to looking at something different. If it makes sense for my clients, I'm perfect fine with it. >> When you go subscription, does that have an effect? Does your CFO like that? Switching to a radical model? >> Well, we're just basically turning our capital into operational. And as long as my base cost doesn't change, I think it's perfectly fine. >> Dave: So from a capital budget standpoint, it's got to be neutral and go from there. >> Excellent, alright Mario, thanks for coming on theCUBE. Great insights. >> Thank you for having me. >> Dave: You're very welcome. Keep it right there, everybody, we'll be back with our next guest. This is theCUBE, Stu Miniman, Dave Vellante. We'll be right back. (upbeat electronic music)

>>Welcome back to super cloud 22, our inaugural event. It's a pilot event here in the cube studios we're live and streaming virtually until we do it in person. Maybe next year. I'm John fury, host of the cube with Dave Lon two great guests, distinguished engineers managers, CTOs investors. Mariana Tessel is a CTO of Intuit ins Ray founder of vertex ventures. Both have a lot of DNA. Founder allow cloud here with mark Andre and Ben Horowitz, a variety of other great ventures you've done. And now you're an investor. Yep. Maria, you've been a seasoned CTO, VP of engineering, VMware Docker Intuit. Now thanks for joining us. >>Absolutely. >>So super cloud is a, is a thing. And apparently it's got a lot of momentum and you guys got stats over there at, at Intuit in, so you're investing and we were challenged on super cloud. Our initial thesis was you build on the clouds, get all that leverage like snowflake, you get a good differentiation and then you compete and then move to other clouds. Now it's becoming a thing where I can do this. Every enterprise could possibly do it. So I want to get your guys thoughts on what you think of super cloud concept and where are the holes in it, what needs to be defined. And so we'll start with you. You've done a lot of cloud things in your day. What >>Do you think? Yeah, it's the whole cloud journey started with a desire to consolidate and desire to actually provide uniformity and, and standards driven ways of doing things. And I think Amazon was a leader there. They helped kind of teach everybody else. You know, when I was in loud cloud, we were trying to do it with proprietary stacks just wouldn't work. But once everyone standardized upon Unix and you know, the chip sets no longer became as relevant. They did a lot of good things there, but what's happened since then is now you've got competing standards at the API layer at the interface layer no longer at the chip set layer, no longer at the operating system layer. Right? So the evolution of the, the, the battles are still there. When you talk about multicloud and super cloud, though, like one of the big things you have to keep in mind is latency is not free. Latency is very expensive and it's getting even more expensive now with, with multi-cloud. So you have to really understand where the separations of boundaries are between your data, your compute, and, and the network is just there as a facilitator to help binding compute and data. Right? And I think there's a lot of bets being made across different vendors like CloudFlare Akamai, as well as Amazon Google Microsoft in terms of how they think we should take computing either to the edge, from the core or back and forth. >>These, this is structural change. I mean, this is structural, >>It's desired by incumbents, but it's not something that I'm seeing from the consumption. I'd love to hear, hear from our end's per perspective, from a consumption point of view, like how much edge computing really matters. Right. >>Mario. >>So I think there's like, there's kind of a, a story of like two, like it's kind of, you can cut it for both edges. No, no pun intended on one end. It is really simplifying to actually go into like a single cloud and standardize on it and just have everything there. But I think what over time companies find is that they end up in multiple clouds, whether like, you know, through acquisitions or through like needing to use a service in another cloud. So you do find yourself in a situation where you have multi multi-cloud and you have to kind of work through it and understand how to make it all like work and latency is an issue, but also for many, many workloads, you can work around it and you can make it work where you have workloads that actually span multiple vendors and clouds. You know, again, having said that, I would say the world is such, that is still a simplifying assumption. When if you go to a single cloud, it's much easier to just go and, and bet on that >>Easier in terms of everything's integrated, IAS works with SAS, they solve a lot of problems. >>Correct. And you can do like for your developers, you can actually provide an environment that's super homogenous, simple. You can use services easily up and down the stack. And, you know, we, we actually made that deliberate decision. When we started migrating to the cloud at the beginning, it was like, oh, let's do like hybrid we'll, you know, make it, so it work anywhere. It was so complicated. It was not worth it. >>When was the, when did you give up, what was the moment? Was there a flash point where you said, oh, this is terrible. This is >>Dead. Yeah. When, when we started to try to make it interoperable and you just see what it requires to do that and the complexity of the architecture that it just became not worth it for the gains you have. >>So speaking obviously as a SAS provider, right. So it just doesn't, it didn't make business case sense for you guys to do that. So it was super cloud. Then an infrastructure thing we just heard from Ben wa deja VI that they're not, they're going beyond instantiating their, their data cloud. They're actually running, you know, their own little snow grid. They called it. And, and then when I asked him, well, what about latency? He said, well, we copied data over, you know, so, okay. That's you have to do, but that's a singular experience with the same governance or the same security. Just wasn't worth it for you guys is what I'm hearing. >>Correct. But again, like for some workload or for some services that we want to use, we are gonna go there and we are gonna then figure out what is the work around the latency issue, whether it's like copy or, you know, redundancy. >>Well, the question I have Dave on snowflake is maybe the question for you and in the panel is snowflake a tan expansion opportunity, or is there a technical reason to go to other clouds? >>I think they wanted to leverage the hyperscale infrastructure globally. And they said that they're out there, it's a free gift. We're gonna go take it. I, I think it started with we're on AWS. Do you think? And then we're on Azure and then we're on Google. And then they said, why don't we just connect all these and make it a singular experience? And yeah, I guess it's a TA expansion as a differentiator and it's, it adds value. Right. If I can share data across that global network, >>We have customers on Azure now, >>Right? Yeah. Yeah. Of course. >>You guys don't need to go CP. What do you think about that? >>Well, I think Snowflake's in a good position cuz they work mostly with analytical workloads and you have capacity. That's always gonna increase like no one subtracts, their analytical workload like ever, right. So there was just compounded growth is like 50% or 80% for, you know, many enterprises despite their best intentions, not to collect more data, they just can't stop doing it. So it's different than if you're like an Oracle or a transactional database where you don't have those, you know, like kind of infinite growth paths. So Snowflake's gonna continue to expand footprint their customers. They don't mind as long as you, they can figure out the, the lowest cost on denominator for, for that. >>Yeah. So it makes sense to be in all the clouds >>For them, for, for them, for sure. Yeah. >>But, but, but Oracle just announced with Microsoft what I would call super cloud, a, a cross cloud database service running on OCI and Azure with very low latency and a database that looks like a, the singular experience. Yeah. With, with a PAs layers >>That lost me after OCI that's >>Okay. You know, but that's the, that's the, the BS answer for all U VCs. The do nobody develops on Oracle? Well, it's a 240 billion market cap company. Show me who you all want be. >>We're gonna talk about SRDF and em C next, you >>All want Oracle. So there we go. You throw that into, you all want Oracle to buy your companies, your funding, you know, cause, cause we all wanna be like Oracle with that kinda cash flow. But, but anyway, >>Here's, here's one thing that I'm noticing that is gonna be really practical. I think for companies that do run SA is because like, you know, you have all these solutions, whether it's like analytics or like monitoring or logging or whatever. And each one of them is very data hungry and all of them have like SAS solutions that end up copy the data, moving data to their cloud, and then they might charge you by the size of your data. It does become kind of overwhelming for companies to use that many tools and basically maybe have that data kind of charge for it, multiple places because you use it for different purposes or just in general, if you have a lot of data, you know, that that is becoming an issue. So that's something that I've noticed in our, in our own kind of, you know, a world, but it's just something that I think companies need to think about how they solve because eventually a lot of companies will say, I cannot have all these solutions, so there's no way I'm gonna be willing to have so many copies of the data and actually pay for that. >>So many times, just something to think about. >>But one of the criticisms of the super cloud concept is that it's just SAS. If I'm running workload on prem and I, and I've got, you know, a connection to the cloud, which you probably do, that's, that's SAS, what's, what's the big deal and that's not anything new or different. So I'd love to get your thoughts on that. But Goldman Sachs, for instance, just announced the service last reinvent with AWS, connecting their tools, their data, and their software from on-prem to AWS, they're offering it as a service. I'm like, Hmm. Kind of looking like Supercloud, but maybe it's just SAS. >>It could be. And like, what I'm talking about is not so much like, you know, like what you wanna connect your data. But the idea is like a lot of the providers of different services, like in the past and, and like higher layer, they're actually COPI the data. They need the data in their cloud or their solution. And it just becomes complicated and expensive is, is kind of like my point. So yes, connecting it like for you to have the data in one place and then be able to connect to it. I think that is a valid, if, if that's kinda what you think about as a super cloud, that is a valid need, I think that companies will >>Have where developers actually want access to tools that might exist. >>Also the key is developers, right? Yeah. Developers decide all decisions, not database on administrators, not, you know, a hundred percent security engineers, not admins. So what's really interesting is where are the developers going next? If you look at the current winners in the current ecosystem, companies like MongoDB, I mean, they capture the minds of yeah. The JavaScript, you know, no JS developers absolutely very early on. And I started catch base and I could tell you like the difference was that capture motion was so important. So developers are basically used to this game-like experience now where they want to see tools that are free, whether it's open source or not, they actually don't care. They just want, and they want it SAS. They want it SAS delivered on demand. Right. And pay as you go. And so there's a lot of these different frameworks coming out next generation, no code, low code, whether it's Java, JavaScript, rust, you know, whatever, you know, go Lang. And there's a lot of people fighting religious wars about how to develop the next kind of modern pattern design pattern. Okay. And that's where a lot of excitement is how we look at like investment opportunities. Like where are those big bets who are, you know, frustrated developers, who are they frustrated, what's wrong with their current environment? You know, do they really enjoy using Kubernetes or trying to use Kubernetes? Yeah. Right. Like developers have a very different view than operator, >>But you mentioned couch base. I mean, I look at couch base what they're doing with Capellas as a form of Supercloud. I mean, I think that's an excellent, they're bringing that out to the edge. We're gonna hear later on from someone from couch base. That's gonna talk about that now. It's kind of a lightweight, you know, sort of, it's gonna be a, a synchronization, but it's the beginning >>A cool new venture deal that I'm not in, but was like duck DB. I'm like, what's duck DB like, well, it's an Emory database that has like this like remote store thing. I'm like, okay, that sounds interesting. Like let's call Mike Olson cuz that sounds like sleepy cat redone red distributed world. But like it's, it's like there's a lot of people refactoring design patterns that we're all grew up with since the popup days of, you know, typical round. Right? >>Yeah. That's the refactory I think that's the big pattern. So I have to ask you guys, what are you guys investing in? We've got a couple minutes left to chat about that. What are you investing at into it from a, from a, a CTO engineering perspective and what are you investing in that feels super cloud like to you? >>Well, the, the thing that like I'm focused on is to make sure that we have absolutely best in the world development environment for our engineers, where it's modern, it's easy to use and it incorporates as many things as we can into that environment. So the engineers don't have to think about it. Like one big example would be security and how we incorporated that into development environment. So again, the engineers don't have to bother with trying to think through how they secure their workloads and every step of the way their other things that we incorporated, whether it's like rollbacks or monitoring or, you know, like baly enough other things. But I think that's really an investment that has panned off for us. We actually started investing in development environment several years ago. We started measure our development velocity and we, it actually went up by six X justly investing. So >>User experience, developer experience and productivity pretty much right. >>Yeah. AB absolutely. Yeah. That's like a big investment area for us that, you know, cloud cloud >>Sounds like super cloudlike factor and I'm assuming it's you're on AWS. >>We are mostly on AWS. Yes. >>And so what are you investing in that from a VC money doling out standpoint? That feels super cloudlike >>So very similar to what we just touched on a lot of developer tool experiences. We have a company that we've invested in called ops level that the service catalogs it's, it's helping, you know, understand your, where your services live and how they could be accessed and, and you know, enterprise kind of that come with that. And then we have a company called Lugo that helps you do serverless debugging container debugging, cuz it turns out debugging distributed, you know, applications is a real problem right now just you can only do so much by log tracing, right? We have a company haven't announced yet that's in the web assembly space. So we're looking at modernizing the next generation past stack and throwing everything out the window, including Java and all of the, you know, current prebuilt components because turns out 90% of enterprise workloads are actually not used. They're they're just policy code. You compiled with they're sitting there as vulnerabilities that no one's actually accessing, but you still have to compile with all of it. So we have a lot of bloatware happening in the enterprise. So we're thinking about how do you skinny that up with the next generation paths that's enterprise capable with security context and frameworks >>Super pass. >>Well, yeah, super pass. That's a kind of good way to, well, is >>It, is it a consistent developer experience across clouds? >>It is. And, and, and, and web assembly is a very raw standard if you can call it that. I mean it's, but it's supported by every modern browser, every major platform, vendor cloud, and Adobe and others, and are using it for their uses. And it's not just about your edge browser compute. It's really, you can take the same framework and compile it down to server side as well as client site, just like JavaScript was a client side tool before it became node. Right. Right. So we're looking at that as a very interesting opportunity. It's very nascent. Yeah. >>Great patterns. Yeah. Well, thanks so much for spending the time outta your busy day. Ariana. Thanks for your commentary. Appreciate your coming on the cubes first in IGUR super cloud event, pilot. Thanks for, for sharing. Thanks for having, thanks for having us. Okay. More coverage here. Super cloud 2022. I'm Jeff David Alane stay with us. We got our cloud ARA panel coming up next.

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

>>from the Cube >>Studios in Palo Alto and Boston connecting with thought leaders all around the world. This is a cube conversation. >>I am stupid, man. And welcome to a cube conversation. Really? Please welcome back to the program. One of our Cube alumni, Sony, Ge and Donnie. She is a co founder and also the business off of pensando. Tony, thanks so much for joining us. >>I thank you for having me here. >>All right. So, Sonny, we've had you on the program a few times. You know, those that have watched the program or followed your career? You've had a story career. You know, I've worked with you as a partner back through some of the spinning disk. You're one of the mpls group. And now, of course, Pensando we helped launch towards the end of 2019. I just want to take a step back and, you know, understand, You know, how did you find yourself in the startup world? >>You know, I got involved with startup ventures as part of the Mpls team. This is going back now. Gosh, 20 years ago, in calendar year 2000 my first venture was with Andy ammo. It was a very unique situation that Mario look up on myself or part of a set up on a startup venture. But all four of us, the Mpls group, did not have any equity in it. Look, and I basically what asked to operate within the with that venture to ensure its ultimate success from a product execution on the go to market perspective? Ah, lot of those elements did not exist from a go to market perspective in Cisco at that time, and it was basically a ground up effort for look and me to not have any financial association with the outcome off the Andy, um, a venture, but at the same time, take on the responsibility from the execution perspective and building up the whole go to market. >>Yeah, so, you know, talking about that these startups, you've been apart of two things. First of all, you were part of and, ya know, you ova in CNI. So did you need to learn Italian to be part of these projects? But more importantly, how did how did you work on that? You know, product customer fit, understanding what the build and, you know, you talk about right How do you make some things that festival? It is super challenging. >>Yeah, well, first and foremost, I think I've been fortunate in that the group that we're all part off it is definitely Italian Indian. And some folks, like from Indiana, for example, like Randy Pond, who is part of this venture with us at Pensando. If I if I would go back and take a look at the simple formula, I mean Mario look, and from, ah, they're veterans in this industry. And they typically focused on the conceiving off the idea and the brought up, uh, and starting with a clean slate approach. Of course, I participate from a market validation development, competitive landscape on a business on all related aspects, bringing the product to market on how that maps into customers and partners what we have consistently focused on market disruption. Particularly for the last two decades, the biggest focus has been on what are the market transitions occurring both from a business and a technology perspective on that is ultimately what creates the opportunity to emerge on and drive these concepts into reality and what yourself, in a market leadership position, is to capture the transition at the right time. >>Yeah, I think back. You know, some of your previous ventures and understand, you know, some of the waves of technologies coming together sometimes the maturity of a technology or being able to take advantage of something new to talk specifically about. Pensando what are you know, those waves of change and the technology coming together that makes the opportunity that you're in today? >>Well, I mean, if you go back and you take a look at really what has been exciting about this pensando opportunity has been to look at the unique ability that have been coming upon us. You know, with this market transition where the cloud is moving to the edge, what is ultimately driving this movement to the edge has been the application. Uh, the applications is is you know, whether it's driven by technology trends like five G, for example. Ah, and and the fact that bulk off what the customer's data is being driven is going to be at the edge. That when when you look at the cloud moving to the edge and evolving that with the transitions occurring, ah, this will require deep innovation. Deep innovation in the areas of distributed network processing security, like encryption, full observe ability while you have turned on encryption, traffic engineering and doing it at very low, predictable agency at the speeds of 100 gig and above all, doing it on a small footprint. We were really the only guys and gals who could do this. And we have done it, >>Yeah, so certainly some really big challenges that they laid out there bring >>us inside >>a little bit. You know, customers. You know, I think about, you know, when I've been watching edge computing for the last three or four years. Uh, you know, it's still relatively early days for customers, but there's a lot of technical challenges there, So help us understand how much you know it was you had technology that could help solve something and how much it is driven by some of the customers that you've been talking to over the years >>Now. One of the key things that we learned and this was going back to the early days of Cisco is that everything we were doing, we had the customer at the center off and at the heart off what innovation we were building from an engineering perspective. You want to build things that can have the most impact in the marketplace and within your customer base. So, uh, one of the early times we went back, who do getting our customers involved in the innovations we were bringing to bear. I still have recollections off a blueprint that we had iterated upon, uh, and sitting in a room, whether it was with the likes of Josh Matthew at Goldman Sachs all whether it was with some of our early cloud customers like the Oracle Cloud, to better understand with these innovation and these blueprints, what were their burning problems? What were they used, cases that we could really go and tackle? So it is one thing to think about market destructions. It's another to bring it to life and having customers engaged with you during the early phases. Off as you are incubating, something is a very important item because it helps you focus your biggest energy on the areas so that you can put your arms around what problems are worth solving. And how can you bring that to life with with customers? Use case. And this is something we have done time and over again. So this is a constant refinement off what we have been doing now for now, to over two decades. As I said, >>Yeah, it's, you know, fascinating here. And when you've got the chief business officer idle, Sony, You know, one of the biggest changes, obviously, is if I look back in the spin ins, you kind of understood how to go to market was what was involved the, you know, the Cisco execution machine that the sales process that they had in plug in a product, that they would help. All right, what you're doing now, you've got some, you know, feel, William partnerships. You have relationship with customers, help us understand a little bit. You know the update on the go to market, how you have. I have a solution that fits for not only the end users, but through multiple different, uh, you know, go to market partners. >>So I think it's, you know, it's very important that as a startup we stay very close to our customers and apart, not just men. We are thinking about what the innovation is and how can it solve their problems. But I think in a world where the way we want to go solve for what? The customer where we want the customer, where our customers want us to be our partnerships is a core part of it. I mean, if you look at from the early days we secured successfully funding from our customers and our strategic partners and it is these customers and strategic partners that are shaping the roadmap on are shaping the routes to market on. What we're doing is we're successfully not only delivering the product, so these strategic customers and partners, but we're also then replicating it across the verticals. If you think about in the enterprise space, our focus has been the focus on regulated market markets where security is essential. Real time, observe ability that can increase your security posture is a very important element. So taking the blueprints that we're taking into global financial services customers, the healthcare industry, the the education market on the federal market, then those are the industries that really care about, and I in regulated markets where we can take the blueprint that we have already built on an amplify across those customers. So there again includes alignment and a partnership with HP. We're working very closely that, while recognizing that we will be doing strategic elements only with partners like HP, we're also on boarding and getting certifications done with Dell because most enterprises have at least dual source vendors from a server, so that that is one aspect. The other aspect is working in a high touch model with the cloud customers and having the opportunity to deliver to them Ah, and onboard them from a production worthy perspective while taking that same blueprint and applying it to other cloud customers and other service provider edge providers that can take advantage of the similar capability. >>Yeah, um, I'm curious. Sony, you know, obviously, the cloud is a space that has been going through a lot of change and accelerating. You know, I'd say much faster than traditional networking did. So you know, curious what you see what you're hearing from customers when they talk about you know, their needs for your solution, what they're doing with multi cloud environment. What is that? That landscape you. And I guess we would love to hear a little bit about how you would compare and contrast yourself. The other solutions out there the one that comes to mind, of course, is you know, eight of us what they're doing with the Annapurna chip in there nitro offering as part of their out. >>You know, as I mentioned earlier, I think the cloud is pushing to the edge. There's a high demand for a lot of packet processing needs with these New Age applications. Customers want to build on and give the you know, we want to be in a position to provide through the democratization and open availability off our products to multiple cloud providers, our technology and as they are experiencing tremendous growth, they're seeking to build cloud with more capacity, with greater degree off security and services functionality. And the ability to process a lot of data at the edge is with millions of simultaneous connections happening at a very small footprint. And that's where we come in. The value that we are essentially providing who not only the existing cloud strategic partners but additional cloud customers we're taking into production this year is that we are enabling them to leapfrog the nitro technology on multiple, whether it is the ability to ah have predictably low latency on and consistently low jitter in the nanoseconds. That is the eight times superior than what a nitro can do today, or the ability to pack their toe process up to nine times more backend processes in the millions of on the ability to do it in a power footprint, which is almost 1/3 that of what you would need on AWS nitro, where they need five times more nitro elements than then we can with a single device, Um, or whether it is the ability now to handle not just power and latency, but millions off flows that can run simultaneously on maintaining the state of all of those and the power of the end, the ability to run multiple services. Uh, with security turned on at the same time are all elements that really differentiate us on. This technology is now readily available to all of us. >>All right, so I understand some of the technical issue items that you're stating there. What I'm curious about is when I look at out both, most customers don't really think about the night. It's that Amazon's providing an extension of their solution into my environment, and they manage everything and so you know, you can't talk about multi cloud environment without talking about Amazon is every customer almost everything right? More than one cloud in one of them is almost always Amazon, though. How does your solution fit into that whole discussion? And then? >>So I think that, you know, one of the things that becomes very important is that if I put my customer enterprise customer hat on, I want to be an enabling my private cloud the private cloud that I build. You have the ability to not just have the option to the port and Amazon cloud, but I typically already and minimal child and barn. So while Outpost and Nitro Nitrogen really enabling, are supposed to deliver those services on our customer's premises, it's only allowing that customer to be locked into one way off dealing with one public cloud company. But if I had to go and think about as I build out my hybrid cloud strategy as an enterprise customer, I want to have the same building blocks on the same policy models that are consistent with all the with the entire dress off cloud vendors that I'm dealing with. The bulk of our customers are essentially telling us I don't want to be locked into a single public cloud company from a hybrid strategy. I want to have the ability to drive a public, private cloud architect that is cloud like from a policy delivery perspective. But at the same time, I want to have the flexibility off deploying a multi cloud and BART, and what we would provide them is the consistency off that same policy model that you would only find in a public cloud with the freedom to not have to buy themselves or lock themselves up into a single public cloud costs. >>So your team, you said, over two decades of experience, there have been some global impacts that have happened during that you got together in 2000. 2001 was right there in front of you that the 2008 you know, down in there, though you're in 2020 obviously the global endemic, as you know, broad financial ripples. How's this impacting Dondo? How's that impacting your discussions with your partners and your customers? >>Well, you know, honestly, I would say that we, like everyone else, have been affected by the pandemic, and we pray that everyone recovers soon with minimum lost to themselves and their families. And this is something very personal. This is here. I feel very passionate about hoping that everybody comes through with this on and their families are all OK. That's all the most important thing in my mind now for us, from a pandemic perspective. What this has done is it has made us more resolute to continue to execute remotely to the best of our ability to meet our customers. Expectations. The advice that I would give to other startups is Keep your head down. Focus on the 80 20 rule, execute on 20% of the things that need to be done, that we'll have 80% of the impact to your business, including undeterred product execution. Stay close to your customers and your partners. Spend your cash judiciously. You know, be very careful on where you're spending your money to make it last. As long as you can ride this pandemic out and double down on being close to your partners and customers. Fortify your sales plans. Meet your customers where they are not where you thought they were, but where they really are and partner with them on this journey and partner with your supply chain. You're going to need that. So this is your time to really be a partner to them, as opposed to see how can you change them? No, no. The really partner with your supply chain Because you're gonna need that. >>Yeah, that's a very sound advice there, Sony. While we're talking advice that, you know, you're very successful career, I'm wondering what advice you would give the other women look at pursuing careers. In fact, specifically, if you know they wanted, you know, start a startup, be a founder, whether that in Silicon Valley or outside, what advice would >>you know? My advice would be to have an undeterred focus. Focus is extremely important. Look, I used to always remind me, Sony, when you're focused on two things, you're d focus. So focus on data. Focus, be driven. Believe in the vision that you have set out for yourself and your team on and keep your eye on the customer. I think in customers successful on your success. That's the message I would give. I would give that same message. My female and the male colleagues. >>Alright, well, we know that you and your team. Sony are very focused, so I'll give you the final word. Gives a little look forward if we go forward. You know, 18 to 24 months. What should we be expecting to see from PENSANDO and your solution? >>Well, in the next 18 to 24 months, we would like to meet and hopefully also exceed our customer's expectation in terms of product execution and the ramp off course. Profitability will be a very important aspect that we're going to keep a very close eye. I think it's too early to be thinking of an ideal, and our focus remains to be on customer success. We have been in the market for a little over. I was a little less than six months. Ah, with the product, September 2019 October 2019 is really when we launched the company on and, uh, the customer always is at the center of everything we do. So that's where we're gonna be focusing on product execution and ramp ramp off product, ramp off estimates. >>Well, so needy. And Dani, it's a pleasure to catch up with you. Thank you so much in the state. >>Thank you. You too. >>Alright. Be sure to check out the cube dot net for all the interviews, you can go see the launch videos that did at go back office in New York City from 2019. If you go to the cube dot net and many more interviews from Sony and her team, I'm stew Minimum. And thank you for watching you. Yeah, yeah, yeah, yeah, yeah.

>>from the Cube Studios >>in Palo Alto and >>Boston connecting with thought leaders all around the world. This is a cube conversation. >>Hey, welcome back here. Ready? Jeff Frick here with the Cube. We're doing a special presentation today really talking about AI and making ai really with two companies that are right in the heart of the Dell EMC as well as Intel. So we're excited to have a couple Cube alumni back on the program. Haven't seen him in a little while. First off from Intel. Lisa Spelman. She is the corporate VP and GM for the Xeon Group in Jersey on and Memory Group. Great to see you, Lisa. >>Good to see you again, too. >>And we've got Ravi Pinter. Conte. He is the SBP server product management, also from Dell Technologies. Ravi, great to see you as well. >>Good to see you on beast. Of course, >>yes. So let's jump into it. So, yesterday, Robbie, you guys announced a bunch of new kind of ai based solutions where if you can take us through that >>Absolutely so one of the things we did Jeff was we said it's not good enough for us to have a point product. But we talked about hope, the tour of products, more importantly, everything from our workstation side to the server to these storage elements and things that we're doing with VM Ware, for example. Beyond that, we're also obviously pleased with everything we're doing on bringing the right set off validated configurations and reference architectures and ready solutions so that the customer really doesn't have to go ahead and do the due diligence. Are figuring out how the various integration points are coming for us in making a solution possible. Obviously, all this is based on the great partnership we have with Intel on using not just their, you know, super cues, but FPG's as well. >>That's great. So, Lisa, I wonder, you know, I think a lot of people you know, obviously everybody knows Intel for your CPU is, but I don't think they recognize kind of all the other stuff that can wrap around the core CPU to add value around a particular solution. Set or problems. That's what If you could tell us a little bit more about Z on family and what you guys are doing in the data center with this kind of new interesting thing called AI and machine learning. >>Yeah. Um, so thanks, Jeff and Ravi. It's, um, amazing. The way to see that artificial intelligence applications are just growing in their pervasiveness. And you see it taking it out across all sorts of industries. And it's actually being built into just about every application that is coming down the pipe. And so if you think about meeting toe, have your hardware foundation able to support that. That's where we're seeing a lot of the customer interest come in. And not just a first Xeon, but, like Robbie said on the whole portfolio and how the system and solution configuration come together. So we're approaching it from a total view of being able to move all that data, store all of that data and cross us all of that data and providing options along that entire pipeline that move, um, and within that on Z on. Specifically, we've really set that as our cornerstone foundation for AI. If it's the most deployed solution and data center CPU around the world and every single application is going to have artificial intelligence in it, it makes sense that you would have artificial intelligence acceleration built into the actual hardware so that customers get a better experience right out of the box, regardless of which industry they're in or which specialized function they might be focusing on. >>It's really it's really wild, right? Cause in process, right, you always move through your next point of failure. So, you know, having all these kind of accelerants and the ways that you can carve off parts of the workload part of the intelligence that you can optimize betters is so important as you said Lisa and also Rocket and the solution side. Nobody wants General Ai just for ai sake. It's a nice word. Interesting science experiment. But it's really in the applied. A world is. We're starting to see the value in the application of this stuff, and I wonder you have a customer. You want to highlight Absalon, tell us a little bit about their journey and what you guys did with them. >>Great, sure. I mean, if you didn't start looking at Epsilon there in the market in the marketing business, and one of the crucial things for them is to ensure that they're able to provide the right data. Based on that analysis, there run on? What is it that the customer is looking for? And they can't wait for a period of time, but they need to be doing that in the near real time basis, and that's what excellent does. And what really blew my mind was the fact that they actually service are send out close to 100 billion messages. Again, it's 100 billion messages a year. And so you can imagine the amount of data that they're analyzing, which is in petabytes of data, and they need to do real time. And that's all possible because of the kind of analytics we have driven into the power It silver's, you know, using the latest of the Intel Intel Xeon processor couple with some of the technologies from the BGS side, which again I love them to go back in and analyze this data and service to the customers very rapidly. >>You know, it's funny. I think Mark Tech is kind of an under appreciated ah world of ai and, you know, in machine to machine execution, right, That's the amount of transactions go through when you load a webpage on your site that actually ideas who you are you know, puts puts a marketplace together, sells time on that or a spot on that ad and then lets people in is a really sophisticated, as you said in massive amounts of data going through the interesting stuff. If it's done right, it's magic. And if it's done, not right, then people get pissed off. You gotta have. You gotta have use our tools. >>You got it. I mean, this is where I talked about, you know, it can be garbage in garbage out if you don't really act on the right data. Right. So that is where I think it becomes important. But also, if you don't do it in a timely fashion, but you don't service up the right content at the right time. You miss the opportunity to go ahead and grab attention, >>right? Right. Lisa kind of back to you. Um, you know, there's all kinds of open source stuff that's happening also in the in the AI and machine learning world. So we hear things about tense or flow and and all these different libraries. How are you guys, you know, kind of embracing that world as you look at ai and kind of the development. We've been at it for a while. You guys are involved in everything from autonomous vehicles to the Mar Tech. Is we discussed? How are you making sure that these things were using all the available resources to optimize the solutions? >>Yeah, I think you and Robbie we're just hitting on some of those examples of how many ways people have figured out how to apply AI now. So maybe at first it was really driven by just image recognition and image tagging. But now you see so much work being driven in recommendation engines and an object detection for much more industrial use cases, not just consumer enjoyment and also those things you mentioned and hit on where the personalization is a really fine line you walk between. How do you make an experience feel good? Personalized versus creepy personalized is a real challenge and opportunity across so many industries. And so open source like you mentioned, is a great place for that foundation because it gives people the tools to build upon. And I think our strategy is really a stack strategy that starts first with delivering the best hardware for artificial intelligence and again the other is the foundation for that. But we also have, you know, Milat type processing for out of the Edge. And then we have all the way through to very custom specific accelerators into the data center, then on top about the optimized software, which is going into each of those frameworks and doing the work so that the framework recognizes the specific acceleration we built into the CPU. Whether that steel boost or recognizes the capabilities that sit in that accelerator silicon, and then once we've done that software layer and this is where we have the opportunity for a lot of partnership is the ecosystem and the solutions work that Robbie started off by talking about. So Ai isn't, um, it's not easy for everyone. It has a lot of value, but it takes work to extract that value. And so partnerships within the ecosystem to make sure that I see these are taking those optimization is building them in and fundamentally can deliver to customers. Reliable solution is the last leg of that of that strategy, but it really is one of the most important because without it you get a lot of really good benchmark results but not a lot of good, happy customer, >>right? I'm just curious, Lee says, because you kind of sit in the catbird seat. You guys at the core, you know, kind of under all the layers running data centers run these workloads. How >>do you see >>kind of the evolution of machine learning and ai from kind of the early days, where with science projects and and really smart people on mahogany row versus now people are talking about trying to get it to, like a citizen developer, but really a citizen data science and, you know, in exposing in the power of AI to business leaders or business executioners. Analysts, if you will, so they can apply it to their day to day world in their day to day life. How do you see that kind of evolving? Because you not only in it early, but you get to see some of the stuff coming down the road in design, find wins and reference architectures. How should people think about this evolution? >>It really is one of those things where if you step back from the fundamentals of AI, they've actually been around for 50 or more years. It's just that the changes in the amount of computing capability that's available, the network capacity that's available and the fundamental efficiency that I t and infrastructure managers and get out of their cloud architectures as allowed for this pervasiveness to evolve. And I think that's been the big tipping point that pushed people over this fear. Of course, I went through the same thing that cloud did where you had maybe every business leader or CEO saying Hey, get me a cloud and I'll figure out what for later give me some AI will get a week and make it work, But we're through those initial use pieces and starting to see a business value derived from from those deployments. And I think some of the most exciting areas are in the medical services field and just the amount, especially if you think of the environment we're in right now. The amount of efficiency and in some cases, reduction in human contact that you could require for diagnostics and just customer tracking and ability, ability to follow their entire patient History is really powerful and represents the next wave and care and how we scale our limited resource of doctors nurses technician. And the point we're making of what's coming next is where you start to see even more mass personalization and recommendations in that way that feel very not spooky to people but actually comforting. And they take value from them because it allows them to immediately act. Robbie reference to the speed at which you have to utilize the data. When people get immediately act more efficiently. They're generally happier with the service. So we see so much opportunity and we're continuing to address across, you know, again that hardware, software and solution stack so we can stay a step ahead of our customers, >>Right? That's great, Ravi. I want to give you the final word because you guys have to put the solutions together, it actually delivering to the customer. So not only, you know the hardware and the software, but any other kind of ecosystem components that you have to bring together. So I wonder if you can talk about that approach and how you know it's it's really the solution. At the end of the day, not specs, not speeds and feeds. That's not really what people care about. It's really a good solution. >>Yeah, three like Jeff, because end of the day I mean, it's like this. Most of us probably use the A team to retry money, but we really don't know what really sits behind 80 and my point being that you really care at that particular point in time to be able to put a radio do machine and get your dollar bills out, for example. Likewise, when you start looking at what the customer really needs to know, what Lisa hit upon is actually right. I mean what they're looking for. And you said this on the whole solution side house. To our our mantra to this is very simple. We want to make sure that we use the right basic building blocks, ensuring that we bring the right solutions using three things the right products which essentially means that we need to use the right partners to get the right processes in GPU Xen. But then >>we get >>to the next level by ensuring that we can actually do things we can either provide no ready solutions are validated reference architectures being that you have the sausage making process that you now don't need to have the customer go through, right? In a way. We have done the cooking and we provide a recipe book and you just go through the ingredient process of peering does and then off your off right to go get your solution done. And finally, the final stages there might be helped that customers still need in terms of services. That's something else Dell technology provides. And the whole idea is that customers want to go out and have them help deploying the solutions. We can also do that we're services. So that's probably the way we approach our data. The way we approach, you know, providing the building blocks are using the right technologies from our partners, then making sure that we have the right solutions that our customers can look at. And finally, they need deployment. Help weaken due their services. >>Well, Robbie, Lisa, thanks for taking a few minutes. That was a great tee up, Rob, because I think we're gonna go to a customer a couple of customer interviews enjoying that nice meal that you prepared with that combination of hardware, software, services and support. So thank you for your time and a great to catch up. All right, let's go and run the tape. Hi, Jeff. I wanted to talk about two examples of collaboration that we have with the partners that have yielded Ah, really examples of ah put through HPC and AI activities. So the first example that I wanted to cover is within your AHMAD team up in Canada with that team. We collaborated with Intel on a tuning of algorithm and code in order to accelerate the mapping of the human brain. So we have a cluster down here in Texas called Zenith based on Z on and obtain memory on. And we were able to that customer with the three of us are friends and Intel the norm, our team on the Dell HPC on data innovation, injuring team to go and accelerate the mapping of the human brain. So imagine patients playing video games or doing all sorts of activities that help understand how the brain sends the signal in order to trigger a response of the nervous system. And it's not only good, good way to map the human brain, but think about what you can get with that type of information in order to help cure Alzheimer's or dementia down the road. So this is really something I'm passionate about. Is using technology to help all of us on all of those that are suffering from those really tough diseases? Yeah, yeah, way >>boil. I'm a project manager for the project, and the idea is actually to scan six participants really intensively in both the memory scanner and the G scanner and see if we can use human brain data to get closer to something called Generalized Intelligence. What we have in the AI world, the systems that are mathematically computational, built often they do one task really, really well, but they struggle with other tasks. Really good example. This is video games. Artificial neural nets can often outperform humans and video games, but they don't really play in a natural way. Artificial neural net. Playing Mario Brothers The way that it beats the system is by actually kind of gliding its way through as quickly as possible. And it doesn't like collect pennies. For example, if you play Mary Brothers as a child, you know that collecting those coins is part of your game. And so the idea is to get artificial neural nets to behave more like humans. So like we have Transfer of knowledge is just something that humans do really, really well and very naturally. It doesn't take 50,000 examples for a child to know the difference between a dog and a hot dog when you eat when you play with. But an artificial neural net can often take massive computational power and many examples before it understands >>that video games are awesome, because when you do video game, you're doing a vision task instant. You're also doing a >>lot of planning and strategy thinking, but >>you're also taking decisions you several times a second, and we record that we try to see. Can we from brain activity predict >>what people were doing? We can break almost 90% accuracy with this type of architecture. >>Yeah, yeah, >>Use I was the lead posts. Talk on this collaboration with Dell and Intel. She's trying to work on a model called Graph Convolution Neural nets. >>We have being involved like two computing systems to compare it, like how the performance >>was voting for The lab relies on both servers that we have internally here, so I have a GPU server, but what we really rely on is compute Canada and Compute Canada is just not powerful enough to be able to run the models that he was trying to run so it would take her days. Weeks it would crash, would have to wait in line. Dell was visiting, and I was invited into the meeting very kindly, and they >>told us that they started working with a new >>type of hardware to train our neural nets. >>Dell's using traditional CPU use, pairing it with a new >>type off memory developed by Intel. Which thing? They also >>their new CPU architectures and really optimized to do deep learning. So all of that sounds great because we had this problem. We run out of memory, >>the innovation lab having access to experts to help answer questions immediately. That's not something to gate. >>We were able to train the attic snatch within 20 minutes. But before we do the same thing, all the GPU we need to wait almost three hours to each one simple way we >>were able to train the short original neural net. Dell has been really great cause anytime we need more memory, we send an email, Dell says. Yeah, sure, no problem. We'll extended how much memory do you need? It's been really simple from our end, and I think it's really great to be at the edge of science and technology. We're not just doing the same old. We're pushing the boundaries. Like often. We don't know where we're going to be in six months. In the big data world computing power makes a big difference. >>Yeah, yeah, yeah, yeah. The second example I'd like to cover is the one that will call the data accelerator. That's a publisher that we have with the University of Cambridge, England. There we partnered with Intel on Cambridge, and we built up at the time the number one Io 500 storage solution on. And it's pretty amazing because it was built on standard building blocks, power edge servers until Xeon processors some envy me drives from our partners and Intel. And what we did is we. Both of this system with a very, very smart and elaborate suffering code that gives an ultra fast performance for our customers, are looking for a front and fast scratch to their HPC storage solutions. We're also very mindful that this innovation is great for others to leverage, so the suffering Could will soon be available on Get Hub on. And, as I said, this was number one on the Iot 500 was initially released >>within Cambridge with always out of focus on opening up our technologies to UK industry, where we can encourage UK companies to take advantage of advanced research computing technologies way have many customers in the fields of automotive gas life sciences find our systems really help them accelerate their product development process. Manage Poor Khalidiya. I'm the director of research computing at Cambridge University. Yeah, we are a research computing cloud provider, but the emphasis is on the consulting on the processes around how to exploit that technology rather than the better results. Our value is in how we help businesses use advanced computing resources rather than the provision. Those results we see increasingly more and more data being produced across a wide range of verticals, life sciences, astronomy, manufacturing. So the data accelerators that was created as a component within our data center compute environment. Data processing is becoming more and more central element within research computing. We're getting very large data sets, traditional spinning disk file systems can't keep up and we find applications being slowed down due to a lack of data, So the data accelerator was born to take advantage of new solid state storage devices. I tried to work out how we can have a a staging mechanism for keeping your data on spinning disk when it's not required pre staging it on fast envy any stories? Devices so that can feed the applications at the rate quiet for maximum performance. So we have the highest AI capability available anywhere in the UK, where we match II compute performance Very high stories performance Because for AI, high performance storage is a key element to get the performance up. Currently, the data accelerated is the fastest HPC storage system in the world way are able to obtain 500 gigabytes a second read write with AI ops up in the 20 million range. We provide advanced computing technologies allow some of the brightest minds in the world really pushed scientific and medical research. We enable some of the greatest academics in the world to make tomorrow's discoveries. Yeah, yeah, yeah. >>Alright, Welcome back, Jeff Frick here and we're excited for this next segment. We're joined by Jeremy Raider. He is the GM digital transformation and scale solutions for Intel Corporation. Jeremy, great to see you. Hey, thanks for having me. I love I love the flowers in the backyard. I thought maybe you ran over to the Japanese, the Japanese garden or the Rose Garden, Right To very beautiful places to visit in Portland. >>Yeah. You know, you only get him for a couple. Ah, couple weeks here, so we get the timing just right. >>Excellent. All right, so let's jump into it. Really? And in this conversation really is all about making Ai Riel. Um, and you guys are working with Dell and you're working with not only Dell, right? There's the hardware and software, but a lot of these smaller a solution provider. So what is some of the key attributes that that needs to make ai riel for your customers out there? >>Yeah, so, you know, it's a it's a complex space. So when you can bring the best of the intel portfolio, which is which is expanding a lot, you know, it's not just the few anymore you're getting into Memory technologies, network technologies and kind of a little less known as how many resources we have focused on the software side of things optimizing frameworks and optimizing, and in these key ingredients and libraries that you can stitch into that portfolio to really get more performance in value, out of your machine learning and deep learning space. And so you know what we've really done here with Dell? It has started to bring a bunch of that portfolio together with Dell's capabilities, and then bring in that ai's V partner, that software vendor where we can really take and stitch and bring the most value out of that broad portfolio, ultimately using using the complexity of what it takes to deploy an AI capability. So a lot going on. They're bringing kind of the three legged stool of the software vendor hardware vendor dental into the mix, and you get a really strong outcome, >>right? So before we get to the solutions piece, let's stick a little bit into the Intel world. And I don't know if a lot of people are aware that obviously you guys make CPUs and you've been making great CPIs forever. But there's a whole lot more stuff that you've added, you know, kind of around the core CPU. If you will in terms of of actual libraries and ways to really optimize the seond processors to operate in an AI world. I wonder if you can kind of take us a little bit below the surface on how that works. What are some of the examples of things you can do to get more from your Gambira Intel processors for ai specific applications of workloads? >>Yeah, well, you know, there's a ton of software optimization that goes into this. You know that having the great CPU is definitely step one. But ultimately you want to get down into the libraries like tensor flow. We have data analytics, acceleration libraries. You know, that really allows you to get kind of again under the covers a little bit and look at it. How do we have to get the most out of the kinds of capabilities that are ultimately used in machine learning in deep learning capabilities, and then bring that forward and trying and enable that with our software vendors so that they can take advantage of those acceleration components and ultimately, you know, move from, you know, less training time or could be a the cost factor. But those are the kind of capabilities we want to expose to software vendors do these kinds of partnerships. >>Okay. Ah, and that's terrific. And I do think that's a big part of the story that a lot of people are probably not as aware of that. There are a lot of these optimization opportunities that you guys have been leveraging for a while. So shifting gears a little bit, right? AI and machine learning is all about the data. And in doing a little research for this, I found actually you on stage talking about some company that had, like, 350 of road off, 315 petabytes of data, 140,000 sources of those data. And I think probably not great quote of six months access time to get that's right and actually work with it. And the company you're referencing was intel. So you guys know a lot about debt data, managing data, everything from your manufacturing, and obviously supporting a global organization for I t and run and ah, a lot of complexity and secrets and good stuff. So you know what have you guys leveraged as intel in the way you work with data and getting a good data pipeline. That's enabling you to kind of put that into these other solutions that you're providing to the customers, >>right? Well, it is, You know, it's absolutely a journey, and it doesn't happen overnight, and that's what we've you know. We've seen it at Intel on We see it with many of our customers that are on the same journey that we've been on. And so you know, this idea of building that pipeline it really starts with what kind of problems that you're trying to solve. What are the big issues that are holding you back that company where you see that competitive advantage that you're trying to get to? And then ultimately, how do you build the structure to enable the right kind of pipeline of that data? Because that's that's what machine learning and deep learning is that data journey. So really a lot of focus around you know how we can understand those business challenges bring forward those kinds of capabilities along the way through to where we structure our entire company around those assets and then ultimately some of the partnerships that we're gonna be talking about these companies that are out there to help us really squeeze the most out of that data as quickly as possible because otherwise it goes stale real fast, sits on the shelf and you're not getting that value out of right. So, yeah, we've been on the journey. It's Ah, it's a long journey, but ultimately we could take a lot of those those kind of learnings and we can apply them to our silicon technology. The software optimization is that we're doing and ultimately, how we talk to our enterprise customers about how they can solve overcome some of the same challenges that we did. >>Well, let's talk about some of those challenges specifically because, you know, I think part of the the challenge is that kind of knocked big data, if you will in Hadoop, if you will kind of off the rails. Little bit was there's a whole lot that goes into it. Besides just doing the analysis, there's a lot of data practice data collection, data organization, a whole bunch of things that have to happen before. You can actually start to do the sexy stuff of AI. So you know, what are some of those challenges. How are you helping people get over kind of these baby steps before they can really get into the deep end of the pool? >>Yeah, well, you know, one is you have to have the resource is so you know, do you even have the resource is if you can acquire those Resource is can you keep them interested in the kind of work that you're doing? So that's a big challenge on and actually will talk about how that fits into some of the partnerships that we've been establishing in the ecosystem. It's also you get stuck in this poc do loop, right? You finally get those resource is and they start to get access to that data that we talked about. It start to play out some scenarios, a theorize a little bit. Maybe they show you some really interesting value, but it never seems to make its way into a full production mode. And I think that is a challenge that has faced so many enterprises that are stuck in that loop. And so that's where we look at who's out there in the ecosystem that can help more readily move through that whole process of the evaluation that proved the r a y, the POC and ultimately move that thing that capability into production mode as quickly as possible that you know that to me is one of those fundamental aspects of if you're stuck in the POC. Nothing's happening from this. This is not helping your company. We want to move things more quickly, >>right? Right. And let's just talk about some of these companies that you guys are working with that you've got some reference architectures is data robot a Grid dynamics H 20 just down the road in Antigua. So a lot of the companies we've worked with with Cube and I think you know another part that's interesting. It again we can learn from kind of old days of big data is kind of generalized. Ai versus solution specific. Ai and I think you know where there's a real opportunity is not AI for a sake, but really it's got to be applied to a specific solution, a specific problem so that you have, you know, better chatbots, better customer service experience, you know, better something. So when you were working with these folks and trying to design solutions or some of the opportunities that you saw to work with some of these folks to now have an applied a application slash solution versus just kind of AI for ai's sake. >>Yeah. I mean, that could be anything from fraud, detection and financial services, or even taking a step back and looking more horizontally like back to that data challenge. If if you're stuck at the AI built a fantastic Data lake, but I haven't been able to pull anything back out of it, who are some of the companies that are out there that can help overcome some of those big data challenges and ultimately get you to where you know, you don't have a data scientist spending 60% of their time on data acquisition pre processing? That's not where we want them, right? We want them on building out that next theory. We want them on looking at the next business challenge. We want them on selecting the right models, but ultimately they have to do that as quickly as possible so that they can move that that capability forward into the next phase. So, really, it's about that that connection of looking at those those problems or challenges in the whole pipeline. And these companies like data robot in H 20 quasi. Oh, they're all addressing specific challenges in the end to end. That's why they've kind of bubbled up as ones that we want to continue to collaborate with, because it can help enterprises overcome those issues more fast. You know more readily. >>Great. Well, Jeremy, thanks for taking a few minutes and giving us the Intel side of the story. Um, it's a great company has been around forever. I worked there many, many moons ago. That's Ah, that's a story for another time, but really appreciate it and I'll interview you will go there. Alright, so super. Thanks a lot. So he's Jeremy. I'm Jeff Frick. So now it's time to go ahead and jump into the crowd chat. It's crowdchat dot net slash make ai real. Um, we'll see you in the chat. And thanks for watching

(upbeat music) >> Announcer: Live from Barcelona, Spain, it's theCUBE. Covering Cisco Live 2020. Brought to you by Cisco and it's ecosystem partners. >> Welcome back to Barcelona everybody. This is theCUBE, the leader in live tech coverage. We go out to the events and extract the signal from the noise. My name is Dave Vellante, I'm here with my co-hosts Stu Miniman, John Furrier is also in the house. We're here with Ryan Rose, Technical Program Manager at Cisco Devnet. Ryan, great to see you. What's goin' on? >> Hey, thank you so much. I'm really glad to be here. >> You know, we have a soft spot in our heart, for Devnet, because of course, we're in the Devnet zone, Devnet is the reason why theCUBE originally came to Cisco Live, and so it's been awesome seeing the evolution and the ascendancy of DevNet. It's now mainstream, you get a lot of love on the main stage, and really, it is the linchpin of the next generation of training and certifications for the engineers, the network engineers. So, tell us, give us a little quick history of Devnet, You've been here since the beginning, you remember the first Devnet. >> Oh yeah, in fact, so during my time at Cisco, like I was originally in learning at Cisco and being able to move over into Devnet, but I remember the very first Devnet experience that I had, and it started back when Devnet started about five years ago now. It was at Cisco Live San Francisco. At the time, they had split us across two streets, you know, they were trying to put, Cisco was trying to put a lot of activities going on in San Francisco. And they put Devnet in this walkway that was next to the Moscone Center, and, inside the Moscone Center. And when you went in there, it was packed. I mean, it was just shoulder to shoulder. Everyone there was just so excited because everyone was trying to learn, like, what is Devnet? And now, to look back on that, it's just so crazy how people have just been so quick to embrace the Devnet mission, the Devnet philosophy. Really getting into automation and programmability. And it's so exciting for us every year to be coming back, seeing you at theCUBE, being here in the Devnet zone, and being able to help people continue on that journey. Yeah, it's been great. >> Yeah, so, and we got some hard news to talk about today, I said in my breaking analysis this week that Cisco, when it rose, it pulled a number of levers, and one of them was really creating the role of the Network Engineer, the CCIE, and the certifications. People have really understood the challenges of what Stu calls the dark art of networking. And now you're bringing that sort of hardware certification to software, so let's get right into the news. What are you guys announcing today, and why is this important? >> Thank you so much for letting us talk about this because I think everybody has been really excited since Chuck came out in San Diego, announced the Devnet certification, said they were going to be, the new exams were going to be available February 24th, so we're about a month out from there. And to help people get started, we just announced here, about two big new offerings. The first is our Devnet Associate Fundamentals Training. Which we'll be launching on February 21st, so that way we can help individuals that are looking to start building up the skills and the exam readiness that they need to pursue a Devnet Associate Certification. We also announced our new Devnet Study Group Platform. Because we don't want people to just find the tools and the training that they need at Devnet, we want them to find each other. We want them to not just build together, but learn together. So we will now have a brand new Devnet Study Group Platform to help people have that type of interactivity. >> Ryan, I'm curious if you have much visibility into who's going to be taking these. You know, how many of them are the ones that, are the NetVets, the CCIE's that have done this year after year, and how many are new? >> Oh, I will tell you right now, we are actually getting this really wide and diverse audience, in fact, in the Devnet zone, we are providing a presentation on getting ready for Devnet certification four times a day, and it is packed every time we do it. And the audience is networking engineers, veteran networking engineers. When we ask people in the crowd how many of you have certifications, how many of you are CCIE's? We get a wide variety of CCIE's. This morning, we had a crew of software developers. So, we are getting people that are coming from kind of, all job roles, at all stages in their career. What they're embracing is that Devnet philosophy, around coding, around automation. They want to bring those practices back, whether that's DevOps, whether that's bringing a greater understanding of programmability, and so we're actually getting everyone, whether again, they're veterans or brand new. >> Yep, now I love that, because about 10 years ago there was this big movement, and they said, network engineers, your future is miserable, you all need to learn to decode, throw out what you learned, and fast forward to today, there's multiple paths to get there. As you were talking about, there's diverse backgrounds, there's lots of ways to be relevant to automation, of course, is hugely important. Coding is a major piece of it, but it's not, forget everything that you knew, it's how everything all works together. >> Yeah, I completely agree. I feel like, especially because the Devnet certifications aren't just the, are only one part of the launch on February 24th. In fact, the entire certification portfolio, and I know you're going to have other Cisco leaders on to talk about this, that is also being updated and launched on February 24th. And what I think you're going to see here is that flexibility that is in the program now, where you can actually have elements of automation baked into that network engineering journey. So you can still have the elements that people have been focusing on and building upon, except now you can stack on these new skills as you go. >> So, if I go back 10 years, maybe even a little bit more, but certainly 10 years ago, people were reticent to embrace automation. You know, you sort of alluded to that Stu, but now in this day and age, automation is fundamental. You can't scale without automation. And so the Devnet zone is really about taking beyond that existing skill set, going to the next level. Okay, so if you think about the network engineer and the training that they've gotten in the past, to deploy, manage, and optimize networks, automation comes in, simplifies all that. How do you describe what the future looks like for that engineer that's been Devnet certified? What are they doing? >> Oh, I think that now it's like, it opens up a brand new horizon of tasks and even efficiencies. New things that people have yet to even, or new job roles that even starting to emerge. A really good example, and one that we even talked about here at the Devnet zone, is the DevSecOps engineer, or the SecDevOps engineer. It's not that, and Susie has even talked about this as well too, Susie Wee, who leads Devnet. It's that jobs are changing, and roles are expanding, and so rather than just having this opportunity where you're looking at supporting a network or acting as a network administrator, now with automation, to your point, we actually can expand the opportunities of the roles themselves, and really open up things like, maybe you want to add those security automation elements, maybe you're interested in adding the collaboration automation elements, but whatever you are looking to do, the way that the program is built, post February 24th of 2020, you're able to actually have the opportunity to add in those skill validation exams, really build upon where you want to go. So I would say the horizon is wide and bright. >> So, to carry this up further, my question is, so the lines are blurring between, you know, Dev and Ops, right, and then, so a network engineer is going to become more Dev oriented, do you see them actually either contributing to or, certainly contributing to, but actually developing apps, say for instance, for the Edge? Maybe you can talk about that a little bit. >> Well, we are actually encouraging, as we have more and more people join the Devnet community, we actually have two elements, two exchanges, our automation exchange and our code exchange, to really help people as they're moving through that. We're already starting to see that learners, individuals, are coming through Devnet, making that change themselves, and actually contributing code to our code exchange, but also adding use cases to our automation exchange. So that way they're able to show not only how they're implementing these cases, buy why they're doing it. And the types of business outcomes that they're achieving. So that's a practice that has already started to take off. And I think certifications and things like the automation exchange, they go hand in hand, building the skills, and then adding to the program. >> Well, you hear in the keynote today, all the talk about bringing IT and OT together. Again, part of that, I've always said that the edge is going to be won by developers. Because critical infrastructure needs to be secured. And, you know, developers, the DevSecOps role, and I think this crowd is actually going to be an important lever in terms of bringing those two worlds together, your thoughts on that? >> Yeah, I actually think that that bridge is something that everyone is crossing right now. And, in fact, that's one of the motivations behind the updates to the certification portfolio. In fact, you'll find that we have parts of the portfolio that are shared between the hardware side and the software side. So that way we can have people as they're making that transition, as they're starting to move into that world, that larger world of network automation, we're actually having it be more of a clear journey for them, so they're able to work that into their own certification pouch. And I would say that these people that are here in the Devnet zone, they're the pioneers. They're the ones that are out there on that edge that are doing that exploration and building these new things, these new worlds that we are going to start experiencing in automation. >> And I guess Stu, it goes without saying, but it's worth saying, this is really all about programmable infrastructure, infrastructurous code, bringing the cloud operating model to your data, to your infrastructure, wherever it lives, right? >> Yeah, so Ryan, one of the things that struck us is not only is there so much enthusiasm, but the breadth of the offering here, everything from, here's some cool Meraki IOT things, to you, you talked about security, automation sprinkled throughout, can you just remind our audience a little bit as people get through the certifications, you know, what are some of the PaaS that they have for different parts of the portfolio? >> Oh, absolutely, so the certification journey that we have right now within Devnet, we actually align it to all of our five major technology tracks right now, so there are pathways within the portfolio around enterprise networking, security, collaboration, service provider, and also data center. But we also have pathways, as well, around application buildouts in IOT, and Edge computing, WebEx, and also, we have an entire practice that's now just dedicated to DevOps. And because DevOps is a concentration that can be, that is a horizontal throughout all of the certifications, this is something that you can now add to your journey. So we can actually have people here, and in fact, we've been answering this question more and more, how do I become more proficient at DevOps? A part of that is now in the certification journey. And so we've done that here. >> You should mention that we're in the IOT takeover right now in the Devnet zone. >> So Ryan, what about the partner ecosystem, talk to us about how, what impact do they have, how much of the ecosystem is getting involved in certifications too. >> Oh, well, I will say that we've actually, we've brought in a lot of people to help us develop this program initially. And I know that you're going to have additional Devnet leaders, they're going to be coming on, talking about partner ecosystems, so I don't want to take anything away from them, but I will say this. There is a lot of excitement because of the fact that when we brought the Devnet certifications out and what that would mean, for example, the new Devnet partner specialization. This is something that has been embraced by our partner community, but it's been embraced by the developers, whether they're our partner developers, they're our customers, or our networking engineers. Now that they have these as options for them to pursue, we have only been met with like positive enthusiastic engagement. And in fact, even now, we're starting to see a lot of people that aren't asking anymore, in fact, going back to San Francisco, when everyone was saying, what is Devnet, now they're asking how do I Devnet. And it is so great to be able to come and show them not only the certifications, but the associate fundamentals training, these new Devnet study group platforms that we have to show them you know the what now, here's the how. >> So, how challenging, cus I was talking to a lady on the floor yesterday, and we were chatting, and I said, "you were CCIE", she goes, "Oh, it's my dream, you know, I'm working my way there, it's very challenging, but I'm doing really well". Similar challenges, presumably, to get Devnet certified? >> Yes. >> How trivial. >> No, it is not trivial. It is a certification in the exact same hallmark that we hold CCNA, CCNP, and CCIE. The Devnet certifications are just as rigorous. And so we are giving people a lot of tools to help them get ready. And in fact, one of the things that we've done to help people on this journey take the initial steps, is we are not holding back any secrets. We've hosted every one of our exam topics for all 10 of our Devnet exams at developer.cisco.com/certification. There you can find out the exact skills we'll be testing you on for all of those exams. But we went a step further. We found every Devnet learning lab that you can take today for free to start getting ready on that exam journey. And so for every single exam, you can find training that you can engage with. So as people are starting this journey, if they want to get ready and just build their skills, especially if they're starting at zero, for example, if they think python is just a snake, we have a learning lab for them. So we have an entire plan that's built so they can start getting ready, and advance and move forward for that certification process. >> What should a college kid do to get prepared for this? If he or she wants to get into IT, become a network engineer, or Devnet is interested in them, what should they take, what courses should they be interested in? >> Oh man, that is a great question. We talk to a lot of people that are in a CS program, or computer science program, and so many young people that are moving through college now, they're already in the habit of programming. They've been working on things, they might have even been programming their own video games, or adding something to the new Mario games where you can actually build your own levels. What I would recommend to every young person, and in fact, to anyone that's on this journey, come to Devnet. We have an incredible amount of tools. At developer.cisco.com, just by signing up, you get access, not only to training that can take you from zero to coding, to making your first API call, to finding our Sandboxes, where you can take that theoretical knowledge and put it into practice using Cisco hardware and tools, and then you can also find use cases there too. I think everyone is often just looking for where can I start, how do I start. Devnet is gone so far as to even have a Start Now area on the Devnet main page. So when you come to Devnet, we're always trying to meet you where you're at. If you're a veteran networking engineer, if you're a veteran developer, or if you're just starting out, you're a college student, we've got a plan for you to be able to take. >> Awesome, right, check it out folks, you know, career builder, Cisco's always been renowned at that. Thanks so much for coming on theCUBE, it's great to have you. >> Oh, hey, thank you so much for having me. >> You're welcome, all right, keep it right there buddy, we'll be back with our next guest from Cisco Live in Barcelona. You're watching theCUBE. (upbeat music)

from New York City it's the cube covering welcome to the new edge brought to you by pensando systems hey welcome back here ready Jeff Rick here with the cube we are in downtown Manhattan at the top of goldman sachs it was a beautiful day now the clouds coming in but that's appropriate because we're talking about cloud we're talking about edge and the launch of a brand new company is pensando and their event it's called welcome to the new edge and we're happy to have since we're goldman the guys who have the money we're barry Eggers a founding partner of Lightspeed ventures and randy pond the CFO a pensando gentlemen welcome thank you thank you so Barry let's start with you you think you were involved at this early on why did you get involved what what kind of sparked your interest we got involved in this round and the reason we got involved were mainly because we've worked with this team before at Cisco we know they're fantastic they're probably the most prolific team and the enterprise and they're going after a big opportunity so we were pleased when the company said hey you guys want to work with us on this as a financial investor and we did some diligence and dug in and found you know everything to our liking and jump right in didn't anybody tell them this startup is a young man's game they mixed up the twenty-something I think yeah they sort of turned the startup on its head if you will no pun intended that's going right yeah yeah and Randy you've joined him a CFO you've known them for a while I mean what is it about this group of people that execute kind of forward-looking transformation transformational technologies time and time again that's not a very common trait it's a it's a great question so you know the key for these guys have been well they've been together since the 80s so Mario look and primitive this is the 80s I work with them at their previous startup before Christian two ladies and they're the combination of their skills are phenomenal together so you know one of them has some of the vision of where they want to go the second guy is a substantive sort of engineer takes it from concept first drawing and then the Prem takes over the execution perspective and then drives this thing and they've really been incredible together and then we added Sony at crescendo as a as a product marketing person and she's really stepped up and become integral part on the team so they work together so well it just makes a huge difference yeah it's it's it's amazing that that a that they keep doing it and B that they want to keep doing it right because they've got a few bucks in the bank and they don't really need to do it but still to take on a big challenge and then to keep it under wraps for two and a half years that's pretty pretty amazing so curious Barry from your point of view venture investing you guys kind of see the future you get pitched by smart people all day when you looked at John Chambers kind of conversation of these ten-year kind of big cycles you know what did you think of that how do you guys kind of slice and dice your opportunities and looking at these big Nick's yeah going back going back to the team a little bit they've been pretty good at identifying a lot of these cycles they brought us land switching a long time ago with crescendo they sort of redefined the data center several times and so there's another opportunity what's driving this opportunity really is the fact that explosion of applications in the network and of course east-west traffic in the network so networks were more designed north-south and they're slowly becoming more east-west but because the applications are closer to the edge and networks today mostly provide services in the core the idea for pensando is well why don't we bring the service deliver the services closer to the applications improve performance better security and better monitoring yeah and then just the just the hyper acceleration of you know the amount of data the amount of applications and then this age-old it's we're going to use the data to the computer do you move the compute to the data now the answer is yes all the above so you got some money to work with we do you got a round that he could be around you guys are closing the C round so I think 180 people approximately I think somebody told me close enough so as you put some of this capital to work what are some of your priorities going forward so we will continue to hire both in the engineering side but more importantly now we're hiring in sales and service we've been waiting for the product quite frankly so we've just got our first few sales guys hired we've got a pretty aggressive ramp especially with the HP relationship to put people out into the field we've hired a couple guys in New York will continue to hire at the sales team we're ramping the supply chain and we've got a relative complicated supply chain model but that has to react now that we're going to market all that might be pretty used to do that we're changing facilities we need to grow we're sort of cramped in a one-story building open up one floor of a building right now so the money is going to be used sort of critically to really scale the business down they can go to market okay but a pretty impressive list of both partners and customers on launch day you don't see Goldman HPE Equinix I think it was quite a slide some of that is the uniqueness of the way we went to market and did the original due diligence on the product and bringing customers in early and then converting them to investors you end up with a customer investment model so they stayed with us Goldman's been through all three rounds we've been about HP and last model we had NetApp has been um two rounds now so we've we've continued to develop as a business with this small core group of customers and investors that we could try to expand every time we move to the next round and as Barry said earlier this is the first time we had a traditional financial investor in our rounds the rest of them have all been customers they've been friends and family for the most part did you join the board too right I did yeah so what are you what are you excited about what what do you see is I mean just clearly your side you invested but is there something just extra special here you know react chambers put in a 10-year 10-year cycle yeah we've talked about it I mean I'm excited to work with the team right there best-in-class working closely with John again is a lot of fun a chance to not exhaust yeah yeah you know a chance to read redefine the data center and be part of the next way even as a VC you love waves and build my Connick company right and I think we have a real opportunity in front of us it it takes a lot of money to do this and do it right and I think we have the team that proven they can execute on this kind of opportunities from I'm excited to see what the next five years hold for this company good well it was funny John teased him a little bit about you know all the M&A stuff that he was famous for at Cisco he's like I don't do that anymore now I'm an investor I want IPOs all the way what's all 18 thinks it is 18 companies in his portfolio their routes they're going to IPO all the way yeah that's that's a good point actually this team has been prolific and they've delivered products that have generated fifty billion dollars and any walk into any data center in the world you're gonna see a product this team has built however this team has not taken a company public so that's really the opportunity I think that's what excites them Randy's here it's why Jon's here that's why I'm here we want to build a company that can be an independent company be a lasting leader in a new category yeah so last word Randy for you for people that aren't familiar with the team that aren't familiar with with with what they've done what would you tell them about why you came to this opportunity and why you're excited about it well this there is no higher quality engineering team in the world didn't these people so it's to get re-engaged with them again with an entirely new concept that's catching a transition and the market was just too good an opportunity to pass I mean I had retired for 15 months and I came out of retirement to join this team much to the chagrin of my wife but I just couldn't pass up the opportunity high caliber talent it's um every day is is interesting I have to say well thanks for for sharing the story with us and and congratulations on a great day and in a terrific event thank you thank you very much all right he's berry he's Randy I'm Jeff you're watching the cube from the top of goldman sachs in Manhattan thanks for watching we'll see you next time

>>From New York city. It's the cube covering. Welcome to the new edge brought to you by systems. >>Okay, we'll come back. You're ready. Jeff Frick here with the cube. We're in downtown Manhattan at the top of Goldman Sachs, like 43 stories above the Hudson. It was a really beautiful view a couple hours ago, but the cloud has moved in and that's only appropriate cause it's cloud is a big theme of why we're here today. We're here for the Penn Zando event. It's called welcome to the new edge. They just come out of stealth mode after two and a half years, almost three years, raised a ton of money, got a really rockstar team and we're excited to have the CEO with us today to tell us a little bit about more what's going on. And that's prem Jane and again, the CEO of Penn Sandow prem. Great to see you. Nice to see you too. So everything we did running up to this event before we could get any of the news, we, we, we tried to figure out what was going on and all it kept coming up was NPLS, NPLS, NPLS, which I thought was a technology, which it is, but it's really about the team. Tell us a little bit about the team in which you guys have built prior and, and why you're such a, a well functioning and kind of forward thinking group of people. >>So I think the team is working together. Mario Luca, myself and Sony were working together since 1983 except for Sony. Sony joined us after the first company, which has crescendo, got acquired by Cisco in 1993 and since then four of us are working together. Uh, we have done many, uh, spinnings inside the Cisco and demo was the first one. Then we did, uh, uh, Nova systems, which was the second, then we did recently in CMA. Uh, and then after we left we thought we are going to retire, but we talked about it and we says, you know, there is still transitions happening in the industry and maybe we have few more years to go back to the, you know, industry and, and do something which is very challenging and, and uh, impacting. I think everything which we have done in the past is to create a impact in the industry and make that transition which is occurring very successful, >>which is really hard to do. And, and John Chambers who, who's on the board and spoke earlier today, you know, kind of talked about these 10 year cycles of significant change in our industry and you know, Clayton Christianson innovator's dilemma, it's really easy when you are successful at one of those to kind of sit on your laurels. In fact, it's really, really hard to kill yourself and go on to the next thing you guys have done this time and time and time again. Is there a unique chemistry in the way you guys look forward or you just, you just get bored with what you built and you want to build something new. I mean, what is some of the magic, because even John said, as soon as he heard that you were the team behind it, he was like, sign me up. I don't know what they're building but I don't really care cause I know these people can deliver. >>I think it's very good the, whenever you look at any startup, the most important thing which comes up as the team and you're seeing a lot of startup fails because the team didn't work together or they got their egos into this one. Since we are working for so long, they compliment each other. That's the one thing which is very important. Mario, Luca, myself, they come from engineering backgrounds. Sony comes from marketing, sales, uh, type of background and we all lady in terms of the brain, if you think about is the Mario behind the scene, Luca is really the execution machine and I'm, you can think like as a heart, okay. Putting this thing together. Uh, as a team, we work very complimentary with each other. It does not mean that we agree on everything, right? We disagree. We argue. We basically challenge each other. But one thing good about this particular team is that once we come to a conclusion, we just focus and execute. And team is also known to work with customers all the time. I mean, even when we started Penn Sando, we talked to many customers in the very beginning. They shape up our ideas, they shape up the directions, which is we are going and what transitions are occurring in the industries and all that. That's another thing which is we take customer very seriously in our thought process of building a product. >>So when you were thinking around sitting around the table, deciding whether you guys wanted to do it again, what were the challenges that you saw? What was the kind of the feedback loop that came in that, that started this? The, uh, the gym of the idea >>thing is also is that, uh, we had, we had developed so many different products as you saw today in the launch, eight or nine, uh, billion dollar product line and stuff like that. So we all have a very good system experience what is really needed, what transitions are occurring and stuff like that. When we started this one, we were not really sure what we wanted to do it, but in the last one when we did the, uh, NCMA, we realize that the enterprise thing, which we deliver the ACI solution for the enterprise, the realize that these services was the most complex way of incorporating into that particular architectures. So right from the beginning of interview realized that the, this particular thing is nobody has touched it, nobody thought about it out of the box thinking that how can you make it into a distributed fashion, which has also realized that cloud is going, everything distributed. >>They got away from the centralized appliances. So as the enterprise is now thinking of doing it cloud-like architectures and stuff like that. And the third thing which was really triggered us also, there was a company which is a new Poona which got acquired by Amazon in 2016 and we were looking at it what kinds of things they are doing and we said we can do much better architecturally and next generation, uh, architecture, which can really enable all the other cloud vendors. Some of them are our partners to make sure they can leverage that particular technologies and build the next generation cloud. And that's where this idea of new edge came in because we also saw that the new applications like IOT is five G's and artificial intelligence, machine learning, robotics or drones, you just name it intelligent devices, which is going to get connected. What is the best place to process them is at the edge or also at the backend with the application where the server is running these and that is another edge compute edge, right? >>In that particular sense. So our idea was to develop a product so that it can cover wide segment of the market, enterprise cloud providers, service borders, but focus very narrowly delivering these services into existing architectures. Also people who are building, building the next generation architectures. Right, so it's the distributed services platform or the distributed services architecture. So at its core for people that didn't make it today, what is it? It's basically is a distributed service platforms. The foundation of that is really our custom processor, which is we have designed is highly programmable. It's software defined so that all the protocols, which is typically people hardwired in our case is programmable. It's all programs which is we are writing the language which you selected as before and before extensions. The software stack is the major differentiated thing which is running on the top of this particular processor, which is we have designed in such a way that is hardware agnostics. >>The the, the capabilities which we have built is easily integrated into the existing environment. So if people already have cloud and they want to leverage our technologies, they can really deploy it in the enterprise. We are basically replacing lot of appliances, simplifying the architectures, making sure they can enable the service as they grow model, which is really amazing because right now they had to say firewall goes here, load balancer goes here, these a VPN devices goes there. In our case it's very simple. You put in every server of our technologies and our software stack and our Venice, which is our policy manager, which is sitting outside and it's based upon Kubernete X a architectures is basically a microservices, which is we are running and managing the life cycle of this particular product family and also providing the visibility and uh, uh, accountability in terms of exactly what is going on in that particular network. >>And it's all driven by intent-based architecture, which is policy driven, right? So software defined sitting on software defined Silicon. So you get the benefits of the Silicon, but it's also programmable Silicon, but it's still, you're sitting, you've got a software stack on top of that that manages that cloud and then the form factors as small as a Nick. Yes. So he can stick it in the HP HP server. Yeah. It specifically goes into any PCI slot in any server, uh, in the industry. Yes. It's amazing. Well, first incarnation, but, but, but, but, but that's a really simple implementation, right? Just to get radiation and easy to deploy. Right. And you guys are, you're yourself where involved in security that's involved in managing the storage. It's simple low power, which I thought was a pretty interesting attribute that you defined early on. Clearly thinking about edge and these distributed, uh, things all over the place. >>They're metal programmable. And then the other thing that was talked about a lot today was the observability. Yes. Um, why observability why was that so important? What were you hearing from customers that were really leading you down that path? Yeah, it's important. Uh, you know, surprisingly enough, uh, the visibility is one of the biggest challenge. Most of the data center faces today. A lot of people tried to do multiple different things, but they're never able to do it, uh, in, in the way we are doing it. One is that we don't run anything on the host. Some people have done it right on the train running the agent on the host. Some people have tried to run virtual machines on the those particular environment. In our case there's nothing which is running on the host site. It runs on our card and having end to end that visibility we can provide latency, very accurate latency to the, to the applications which is very important for these customers. >>Also, what is really going on there is the problem in the network. Isolation is another big thing. When something get lost they don't know where it got lost. We can provide that thing. Another important thing that you're doing, which is not being done in the industries. Everything which is we are doing is flow based means if I'm talking to you, there is a flow being set up between you and me and we are monitoring every flow and one of the advantages of our processor is we have four to eight gigabytes of memory, so we can keep these States, have these flows inside, and that gives a tremendous advantage for us to do lots of things, which as you can imagine going forward, we will be delivering it such as, for example, behavior of these flows and things from this point of view, once you understand the behavior of the flow, you can also provide lot of security features because if I'm not talking to you and suddenly I start talking to you and I know that there's something went wrong, right, right. >>And they should be able to look at the behavior analysis and should be able to tell exactly what's going on. You mean we want a real time snapshot of what's really happening instead of a instead of a sample of something that happened a little. No, absolutely. You're absolutely connected. Yeah. Yeah. Um, that's terrific. So you put together to accompany and you immediately went out and talked to a whole bunch of customers. I was amazed at the number of customers and partners that you had here at the launch. Um, was that for validation? Were you testing hypotheses or, or were there some things that the customers were telling you about that maybe you weren't aware of or maybe didn't get the right priority? I think it's all of the above. What you mentioned our, it's in our DNA by the way. You know, we don't design products, we don't design things without talking to customers. >>Validation is very important that we are on the right track because you may try to solve the customer problem, which is not today's problem. Maybe future's problem. Our idea was that then you can develop the product it was set on the shelf. We don't want to do that. We wanted to make sure that, that this is the hard problem customer is facing today. At the same time looking at it, what futuristic in their architecture is understanding the customers, how, what are they doing today, how they're deploying it. The use cases are understanding those very well and making sure that we are designing. Because when we design a seeker, when your designer processor, you know, you cannot design for one year, it has to be a longterm, right? And you need to make sure that we understand the current problems, we understand the future problems and design that in pretty much your spark and you've been in this space forever. >>You're at Cisco before. And so just love to get your take on exponential growth. You know, such an interesting concept that people have a really hard time grasping exponential growth and we're seeing it clearly with data and data flows and ultimately everything's got to go through the network. I mean, when you, when you think back with a little bit of perspective at the incredible increase in the data flow and the amount of data is being stored and the distribution of these, um, applications now out to the edge and store and compute and take action at the edge, you know, what do you think about, how do you, how do you kind of stay on top of that as somebody who kind of sees the feature relatively effectively, how do you try to stay on top of exponential curves? As you know, very valuable data is very important for anybody in any business. >>Whether it's financial, whether it's healthcare, whether it's, and it's becoming even more and more important because of machine learning, artificial intelligence, which is coming in to really process this particular data and predict certain things which is going to happen, right? We wanted to be close to the data and the closest place to be data is where the application is running. That's one place clears closest to the data at the edge is where data is coming in from the IOT devices, from the 5g devices, from the, you know, you know all kinds of appliances which is being classified under IOT devices. We wanted to be, make sure that we are close to the data, doesn't matter where you deploy and we want to be agnostic. Actually our technologies and architectures designed that this boundary is between North, South, East, West is going to go away in future cloud. >>A lot of things which is being done in the backend will be become at the edge like we talked about before. So we are really a journey which is just starting in this particular detectors and you're going to see a lot more innovations coming from us continuously in this particular directions. And again, based upon the feedback which you're going to get from cloud customers with enterprise customers, but they were partners and other system ecosystem partners, which is going to give us a lot of feedback. Great. Well again, thanks for uh, for having us out and congratulations to uh, to you and the team. It must be really fun to pull the covers off. absolutely. It is very historical day for us. This is something we were waiting for two years and nine months to see this particular date, to have our customers come on the stage and talk about our technologies and why they think it's very important. Thank you very much for giving me this opportunity to talk to you. Thank you. Alright, thanks prem. Thanks. He's prem. I'm Jeff. You're watching the cube where it depends. Sandow launch at the top of Goldman Sachs in downtown Manhattan. Thanks for watching. We'll see you next time.

live from Las Vegas it's the queue covering del technology's world 2019 brought to you by Dell technologies and it's ecosystem partners okay welcome back everyone we live in Las Vegas with a cube tech cue coverage of Dell technology world I'm Jean for @d Volante we're here in Cuba Lumley MERIS house who's the president and chief commercial officer Dell technologies great to see you again always great to be here sir so the the movie just gets better and sequels and Dell 3 into the year 3 of the acquisition I love look I love the script and we're gonna keep going you guys are access to the Game of Thrones it's not going to end it's gonna one of the themes I want to get your thoughts on first of all welcome back to look you good to see you what's going on right now give us an update Mars you've you've seen the chessboard of MMA of big firms on the private equity side you worked at HP during those days you came to Dell with Michael early on partnering on the going private and then looking at the overall plan which is now in full execution mode at the integration part of integrating it all together it's working really good mill the fairway revenues at ninety plus billion where are we right now well I'll tell you I think you and I were just discussing it a second ago scale does matter but if you can align scale with ax in your portfolio that it's so well aligned to the trends in the industry and you're representing an opportunity for a customer to select a partner like Dell technologies to help them solve their key business channel and just not just for today we're into the future and then if you can do at scale right portfolio at the velocity we're doing it's a trifecta that we love it's a that you know I recently talked to Tom Tom sweet we grew the business eleven billion dollars on an already big number just last year alone so and we're gaining sharing all of our key lines of business so the Folies aligning really well customers have been extraordinary and obviously building those big trusted relationships not just now to the but into the future that's you guys ready and you guys got a great team the ability to attract the talent has been phenomenal give you guys props on that but I keep coming back to we had a few years ago which is okay the big waves coming everyone kind of got cloud they saw the scale of Amazon great gel sign that continues to do great for AWS now it's multi cloud now IT the original consolidation of IT that you guys were going after had good growth and value creation just out of the box and now the tail winds as you mentioned so I got to ask you about this end to end this is a land grab this end to end operational consistency thing because it's a very unique it's hard to copy it's in the middle if you can continue to pull that off that's going to be a great opportunity that's gonna feed up up the stack if you will talk about the challenges and why you guys are going this end to end and the benefits the customers there's there is no doubt that the customers are getting smarter every day in understanding what workloads what applications what data sets ought to reside in which ecosystems to better serve them and to better align to their overall economic needs and desires that they want and their flexibility and agility to be able to move those workloads in that data seamlessly to best address their particular needs the beauty of what we've been able to do is integrate the VMware architecture into the public cloud ecosystems and we've got many others that are ready knocking on the door to the beat want to be part of it so now what a customer can have is that true agility that true flexibility of moving applications and data seamlessly but all control through one mechanism because at the end of the day what's going to happen is they're gonna have their day to resign on multiple different sources but they want to be able to see it they want to be able to accident they want to be able to analyze it and once you're able to analyze it regardless of where it resides and then draw the conclusions from it that's what's enables them to then create a predictive model that almost a cost to zero so on day one of the keynotes Michael said he showed the be of a video he said if you're you know bank with two trillion and assets or your two-story farmhouse we care about you know that's kind of music to your ears you obviously you're a big part of that what's different about the commercial customers and and what's going on in that base in terms of their transformation their trends and how is that different from I mean in commercial customers Lisa my and my patch I've got the biggest of the public-sector account so I've got them of all different sizes and shapes and different stages of the journey and that's what we're finding everywhere even if you're a big account small account medium account everyone is on there's digital transformation journey and there's an intersection that we can play a very big part of in and then enabling them to create a playbook as to how do I go through this journey effectively but what we're finding is when we took the overall architecture kind of or indeed tenants if you will around making sure that we have a scale out architecture model it doesn't able to have our customers adopt things and then be able to scale it out as their economic or as their business grows as an example so you can jump into having leading-edge capabilities and technology to help you drive your your company today but know that we're there with you all the way to then scale at whatever rate you want to scale at Mars I got to ask you we had Tom sweet on as you just mentioned CFO he talked about the multiple levers to create multiple levers you guys are pulling to create shareholder value which is ultimately comes from free cash flow which is happy customers great to pay down the debt that's his job margin expansion get good product development increase go to market efficiencies okay and then so philosophy supply chain go to market efficiencies this is your wheelhouse as you guys go talk to the customers and go to the market now with the sets of partnerships one of the changes that we're seeing is in IT it shifted the conversation shifted from not just cost reduction but revenue generating so with these new tailwind is creating a business model opportunity for your customers this is not the old school best in breed got great storage low cost I I've you know low cost per storage gigabyte this is about I don't want to deal with infrastructure anymore you guys handle that this is what you're going after how are you guys going to market under the new reality that customers are critical do you agree with that and how are you going to market with this new shift in the customers mindset Mike the mindset is now that change or dying if I don't drive the digital transformation within my company someone else will do it and more than likely will be a competitor so you see it having on the the uber front air B&B front you can go down the list every single one of these industries are figuring out I better Drive this aggressively and make sure that I take advantage of what's happening in the technology landscape in order to progress and grow my business to be more relevant and more differentiated so instead of IT being a let me lower my cost structure model IT is now the enabler of changing the business model the enabler of a scaling at a much faster rate to take advantage of the options and how does that change the customer selection on vendor supplier because obviously this is obviously gonna probably good for saying you know one supplier gel but that's gonna change how they evaluate procure consume and they're partnering how is that going to change their selection they they want to move more and more towards having the conversation around what do we need to do to scale our business and again create a differentiated advantage right well last thing they want to be is a systems integrator of all the different IT suppliers so when you have a partner like Dell technologies that truly does have the broadest and and and what I'd say best capabilities on the planet to then become that partner of choice for them to move them in this direction faster that's a very simple decision for them to make and how is that dynamic translating into public sector where you know there's a lot of turnover in terms of administration's you might have edicts in terms of you know multi vendor what are you seeing there but I think this is consistent we have a built a a practice what we call smart digital cities that we seeing the need everywhere at the end of the day regardless what public sector entity you go to what country you go to whatever mean it's about you go to every single one of them are thinking about how can I create more jobs how can I create build and grow the economic engine of my city my state my country and guess what they're leaning on technology to do that so everywhere we go it's a conversation about how can we drive efficiencies and productivity improvements across all the things you do and provide a greater level of service to every one of your it's constituencies through technology anything from securing the environment driving protecting our citizens to providing better health care services to providing better traffic management to providing better education and reach waste management you just go down the list every single city every single Enterprise a public sector entity around the globe is thinking about it and what's again the beautiful thing is we can come in we can bring in our overall partner ecosystem because it is a broader ecosystem that is needed in order to be able to deliver those end-to-end capabilities but very much on demand everywhere I gotta ask you about first of all is on the IT side those four public sector entities have a huge job ahead of them and they're not IT huge that staffs they need nimbleness and they need horsepower basically out of the gate and the beauty of what we are able to do is we share the best practices of what we see around the world you can imagine that a city of Dubai very progressive right clearly have the budget clearly have less restrictions on data privacy clearly have less restrictions on legacy integrations into past solutions so they can move pretty quickly with a pretty broad base view as to where they want to go so you take those ideas take those best practices and then you you showcase that to the rest of the world it's - ok what can we use what can they use - to move their agenda forward quickly I want to switch gears talk about competition I saw the Tom sweets presentation the analyst briefing around competition I didn't see any cloud vendors on their office T going multi cloud with your own cloud I see that but just in the traditional IT space the numbers are great in your and you got bigger bigger is better so HPE when smaller they thought that focus would be better for them maybe it is but now you have existing competitors from the classic IT market it's a new new ground you're going after you got Alienware here it's a gaming world you're partnering with it's a beautiful set up so that's the future of TCS so you're in all these markets what's the competitive view how did you talk about your companies for competitive strategy - what we first talked about if you if you've got scale and you have a broad broad portfolio they can address the the core trends that are emerging for the next decade or two and you can do it at speed I'd say a very nice formula and that's what we're starting to really operate at that kind of cadence with the the the strategically aligned businesses like VM were like like pivotal like secure works that are all coming together very nicely to be able to drive these transformations collectively as one portfolio where's the partner coopertition kind of thing going on because you think Cisco for instance you know you guys partner with Cisco in some level but also at the same time NSX on the VMware family side looking like us competing directly with Cisco so this is this you're going to have direct competition and then other ones that are coopertition where you're working as a partner or maybe and it's evolving so how do you guys bet to have those balance conversations it's it's been like that for decades right and there's you you've got big players in the market at the end of the day as long as you service your customer and deliver to them what they want and how they want it at the end of the day we need to collaborate to make that happen - same exact reason why we announced our partnership with Microsoft and Azure earlier this week customer draw was there they said we want you to be that single that single broker that enables me to move my my data in my application seamlessly and securely containerized to any public cloud well guess what Azure needs to be part of that equation so when the customer drives it and it's clearly aligned to their particular needs the the IT ecosystem comes together the best serve that when you have when you meet with the top customers and the top senior people what's the pitch Mario's when you go in and say hey you know here's get we're just gel technology we've got all the puzzle pieces they'll be be successful what's your pitch when you go in what's the mean message that you guys say to those customers I like for the last couple of years we've been talking about that the transformations that are happening right at the highest level it's just a digital transformation journey that people are on the work force transformation they're doing the overall IT transformation that enables that then of course how do you the whole environment on top of that they're having the conversation about okay let's go build the blueprint as to what that looks like for me as a customer and then show me how I'm gonna you're gonna deliver to me the platforms that enables me to grow and make sure that I'm making the right batch long term right I don't want a solution that's just there for today I want to make sure that I've got a solution that good that that will take me into the future and that makes me ultra competitive so when you think about it if I wanted a an app development platform that clearly needs to be cloud native in mind I need to have agile development capabilities and I need to be able the time to value needs to continue to shrink well guess what we got that with pivotal right you want to be able to now do your data management ecosystem seamlessly and and across multiple platforms clearly we have assets like Bumi that enable that to happen very very well and and then you want to virtualize your overall infrastructure layer as much as possible so you truly can scale up or scale down any of your infrastructure capabilities in order to meet the needs of that particular workload seamlessly when you have the data platform when you have the app platform when you have the virtualization platform and you have all of the infrastructure platform so well aligned to the overall trends and transformations our customers are doing it's almost a no-brainer I mean it is an IQ test that all of our customers are clearly passing and okay and what you just laid out it's probably like a ten year he's gonna play out over the next ten years and there's still a lot of invention to be required if you guys aren't doing a lot of M&A right now you know paying down the debt tom was clear on that but as an M&A person I want if we can pick your brain and I'm more familiar with the tech M&A it's where myspace but most M&A much of it anyway fails and and from your perspective why is that and why are some successful why or some not I think it is the how do you how do you when you add a new entity into the broader entity what are the synergies that you're aligning to to make sure that that new entity has the opportunity scale and grow right and that's why you have meant you have sometimes smaller deals are interesting from an IP perspective but if you don't tie it back into how are you gonna go scale to go to market to make it available to your broader set of customer base you or it gets lost in the equation that's a problem and I think what we've done is a very good job making sure that we understand how each piece of the IP portfolio comes together and is aligned to our overall approach and how we how we how we help you have the conversation with the customer that we've been able to see what we call our cross synergies of all the acquisitions we've made significantly exceed any and all of our expectations and and that's important part to do ahead of time before you make the acquisition know not just how it fits into the IP stack but how it fits into your overall go to market stack and how it fits in your overall value proposition to the customer Marcus thanks for spending the time know you're really busy coming on the cube I got to ask you one final question of this showed here Dell technology world over three days what are the three top highlights that happened to you that give a tell sign of the next 10 years with Dell technology I mean we've always said that we do what we say so I think and I've had many of analyst tell us that my god you guys consistently have delivered what you said you would deliver so the early skepticism of hey this this is a big company there's multiple cultures not sure that operationally you will execute well guess what I think it's fair to say the teams are executing and then when you see the results of taking share in every line of business you see the results where the customer satisfaction is higher than it's ever been our partner satisfaction is higher than it's ever been our partner growth is higher is the fastest-growing route to market for us all of that is just a testament that we are operating on all cylinders but what's more exciting is the yet to come part and and the fortuity so big right the market is what three and a half trillion ninety billion is a fraction of that so this is what our our team members see it's what our customers see our partners see so that momentum it's just a tsunami that's just gonna keep on growing well the cube barometer certainly showing activity to sets when we get four you know you're doing well so we're gonna keep an eye on the pulse of the cube pan and we got here Mari it's great to see you always a pleasure great insight thanks for sharing John awesome grant appeared a virus awesome thank you so much Myers house president chief commercial officer Dell technologies Friends of the cube great executive tech athlete as we say live coverage day three here the cube coverage of Delta knows we will be right back with more after the short break [Music]

>> From Boston, Massachusets it's theCube. Covering LiveWorx 18. Brought to you by PTC. >> Welcome back to bean town, everybody. This is theCube, the leader in live tech coverage, and we're covering LiveWorx, the three day conference hosted by PTC. We're at the BCEC, which is kind of the Starship Enterprise. I'm Dave Vellante, with my co-host Stu Miniman. As I say, Cube one day coverage of this three day conference. Maciek Kranz is here. He's the Vice President of Strategic Innovations at Cisco. Maciek, thanks for coming on theCube. >> Thank you so much for having me. It really looks like a cube. >> Usually we're out in the open, but they've put us here in a cube, which is great. Of course we were at Cisco Live last week. You were there, it was an awesome show. 27, 28 thousand people. A lot of the innovations that we're talking about here, you guys, you know, at Cisco, are obviously touching upon. Whether it was blockchain or the edge. May I ask you, innovation's in your title. What are you doing here at this conference? >> Basically we're on the mission to make sure that every company, large and small, whatever the industry you're in, gets started on the IOT journey. All of us here, we were talking about it last week at Cisco Live, we are sort of on the mission to make sure that everybody knows how to do it, how to get started, how to go through the journey. So I'm here to promote the cause. >> You had posted a blog a little bit ago on LinkedIn. Check it out, if you go to Maciek's LinkedIn profile you'll see it. Five myths around IOT, and I thought it was quite instructive. I'm going to start with the middle of it, which is IOT is this one big market, and we've been talking about how it's a trillion dollar market. It's almost impossible to size. It's so fragmented, and bringing together the operations technology and information technology world, and there's the edge, there's the core, there's hardware, there's software, there's services. How should we think about the IOT, obviously not as one big market as you pointed out in your blog. >> Right, and you actually nailed it. When you think about sort of a traditional way that technology companies think about the market, it was sort of model of just get a billion people to get on your platform and the good things will happen. Well in the IOT space, as you pointed out, it's a very fragmented market. So you basically need to have two strategies. You either become a horizontal specialist and then you integrate with a vertical specialist to develop a joint solution, or you focus on use case and you focus on one market, and you go deep and focus with customers. So from that perspective the approach is different, but in a nutshell to be successful in this space, it's not only about technology, it's about ecosystem. It's about building the coaliltion of the willing, because at the end of the day, the customers want solutions to their problems. And they don't want to just buy your technology, they want to work with you on developing solutions that drive business outcomes. >> Maciek, one of the things that's been interesting to watch is that people want to try, and they want to try faster. One of the big benefits of public cloud was that I have this sandbox that I could throw some people at, have a little bit of money, and try things and fail and try again. One of the concerns I have when I hear things like PTC and Microsoft get up on stage and say, "It's going to take 20 to 25 partners to put this together." When I hear that it's fragmented, it's going to take time, it's going to take money, help us. Are there are ways I can start playing with things to understand what will and what won't work for my environment, or is this something that I have to throw a million dollars and group of people for a year and a half on? >> It's actually a great point, and it's another, I would say, misconception, which is I need to go deep, have a sort of a big strategy. One of the things that I talk about with the customers is, yes, dream big but start small. So yes, have a sort of a big vision, big architecture, but then focus on a first project, because it's a multi-year, multi-phased journey. So from that perspective, you know, at Cisco we have roughly 14,000 customers that already got started on this IOT journey, and the use cases that we've seen sort of are in four different categories. First one is connect things, so connecting your operations, the second one is remote operations, the third one is predictive analytics, the fourth one is preventive maintenance. So don't be a hero, pick one of these four use cases, try it out, then do a ROI on this, and if your ROI is positive then do a next, maybe more sophisticated, more adventurous kind of a project down the road. So pace yourself. >> This is our 9th year doing theCube, and the one thing we've learned about information technology, operations technology, is it all comes back to data. And you pointed out again, you pointed it out in your piece, it's not just about connecting, it's about the data. So let's talk about the data, the data model. You've got edge, you've got core. You've got this really increasingly complex and elongating data pipeline. You've got physics, you've got latency. So what's your perspective on the data, how that's evolving, and how organizations need to take advantage of the data? >> Dave, I think you nailed it. It may come across funny because I work for Cisco and we connect things, but if you think about the first wave of internet, the main purpose of the devices and the way we were connecting them, was basically for you and I to get access to each other, to get access to the online data, to the online processes. The main purpose we connecting IOT devices, so that they can generate the data, and then we can analyze that data, turn these systems into solutions to drive business outcomes. So from that perspective we're actually seeing a big shift in the sort of data model, and it requires flexibility. Traditionally, we talked about cloud, right? In a cloud we usually see the use cases that require a processing of a lot of data, sort of in the batch possessing mode, or for example if you want to connect a bunch of vending machines, you can connect them directly to the cloud, because these machines actually send only very few packets and they send them very infrequently. Basically saying, "Hey, come on over "and replenish a bunch of supplies." But if you look at connected vehicle, if you look at an oil rig, in the case of oil rig, there's let's say a large one that has 100,000 sensors. These sensors generate a couple terabytes of data per day. You can't just send this data directly to the cloud through the satellite connection, right? You have to process the data on the oil rig based on the policy coming from the cloud. So from that perspective we've seen that there's a need for a more flexible architecture. We call it Fog Computing, which basically allows you to have flexibility of extending the cloud to the edge so you can process the data at the edge. You can execute on the AI functions at the edge as well. So that's one of the big architectural shifts that we've seen with IOT as well. >> Maciek, one of the opportunities of new architectures has been to do a redo for security. When it comes to IOT, though, there's a lot of concern around that, because just the surface area that we're going to have, the devices. Talk to us about how security fits into IOT. >> Yeah, it's hard to talk about IOT without mentioning security, right? And we obviously seen over the last two years a lot of press around IOT denial of service attacks and so forth, and for me I think the silver lining out of all of this news is that, first of all, that we have seen the vendor community finally taking IOT security seriously. So all the security vendors are actually investing in IOT security now appropriately. We now working together as an industry on standards, on interoperability, on sort of come on architectures, even with the device vendors who traditionally didn't pay much attention to security as well. Sort of like what we did with wifi, you remember, about 15 years ago but at a much greater scale. So the vendor community's focusing on it, but more importantly also the businesses are moving from what I would consider sort of a... I would say that kind of a denial. Hoping that their plant is not connected to the outside world and that it's secure. Moving down now to the much more modern model, which is basically a comprehensive architecture working with are-see-sos, across the enterprise, focusing on before, during, and after. So IOT now is being integrated into a broader security architecture, and IT and OT are working together. So yes, there is a concern, yes. There are a lot of events hitting the news, but I also think as an industry we're making progress. >> Just to follow up on that, Cisco obviously has an advantage in security, because you go end-to-end, you guys make everything, and you can do deep-packet inspection, and that seems to be a real advantage here. But then there's this thing called blockchain, and everybody talks about how blockchain can be applied. Where do you see blockchain fitting into the security equation? >> Yeah, I think that's a good question. Maybe a bit more broader story, I actually believe there's four legs to this digital transformations tool. There's IOT generating the data and acting on the decisions, there's AI, there is the fog computing we talked about, and the fourth tool is blockchain, which basically allows us to make sure that the data we're using we can actually trust. At the high level blockchain, people often confuse blockchain and Bitcoin and cryptocurrencies, but blockchain is an underlying technology behind sort of the crypto, that allows basically multiple parties to write their transactions in a fast and permanent way. But in the enterprise context, in IOT context, blockchain allows us to actually come up with very new use cases by looking at the provenance, and looking at the data across multiple parties. The data we can trust. For example, the use cases such as counterfeiting, there are use cases like food safety. Like patient records. Like provenance of materials. So now we can enable these use cases, because we have a single source of truth. >> I want to ask you about disruption. I like the mental model and picture that you created before of a horizontal technologies, and you kind of get vertical industries, and it seems like, again I'm bringing it back to data. We heard Super Mario at the host of the conference say this was the largest digital transformation conference. Which we laughed, like every conference is a digital transformation conference. But to us, digital transformation, digital means data. And that picture you drew of horizontal technology and vertical industries, it's all data, and data enables disruption. It used to be a vertical stack of talent and manufacturing and supply chain within an industry, and now data seems to be blowing that to pieces in digital. You see Amazon getting into, you know, buying Whole Foods in grocery. You see Apple in financial services. Others, Silicon Valley type companies, disrupting healthcare, which we all know needs disruption. What do you make of disruption? It seems like no industry is safe. It seems like Silicon Valley has this dual disruption agenda. Horizontal technology and then partnering within industries, and everything is getting turned up on its side. What do you make of it all? >> Dave, I think you nailed it. It is about and verus or, right? When you think about companies, you mentioned Microsoft, Cisco, Amazon, verus PTC or Rockwell, or Emerson and others. 10 years ago we sort of lived on a different planet, right, and rarely these companies even talked to each other. And now, even at this show, these companies are actually showing joint solutions. So that's precisely, I think, what we've seen, which is technology competence coming from the Valley and from traditional technology industry, and then the vertical and market expertise coming from these more traditional vendors. At the end of the day, it is about technology, but it is also about talent. It is about skillsets. It's about all of us pulling our resources together to develop solutions to drive business outcomes. So cloud, obviously, was a very disruptive force in our industry. But when you think about IOT, just based on what you just said, it seems to me given the assets, the resources, the people, the plants, the equipment, it seems like IOT is maybe somewhat evolutionary. Not a completely... It's a disruptive force in that's new and that it's different, but it seems like the incumbents, I mean look at PTC, their resurgence. It seems like the incumbents have an advantage here. What are your thoughts? >> I think that if they play it right they absolutely do. But it requires also a shift in mindset, and I think we seeing it already, which is moving from a vertical, one company does it all kind of mentality, into the lets build an ecosystem based on open systems, open standards, interoperability. And that's sort of a shift I think we are seeing. So for me, I think that the incumbents, if they embrace this kind of a model, they absolutely have a critical role to play. On the flip side, the technology companies realizing that they need to, it's not only about technology, but it's also about partnering. It's about integrating within legacy ecosystems and the legacy infrastructure. So each of the sides of the coin need to learn new tricks. >> Okay, last question, is your initial thoughts, anyway, on this event, some initial take aways. I know it's early, day one, but you've been here. You've heard the keynotes. Final thoughts? >> I think so far it's actually a great start to the event. I have to say, what we've talked about already, my biggest take away is to see, and actually joy, is to see companies from different walks of life working together. You have robotics companies, you have AI companies, you have industrial companies. All of them are coming up with solutions together, and that's basically what we want to see. Is breaking the barriers and multiple companies working together to move the industry forward. >> And you're also seeing the big SIs are here. I can see Accenture, I can see Deloid. I know InfoSys is here, et cetera, et cetera. So if they're here, you know there's a lot of money to be made. So Maciek, thanks very much. It's really a pleasure having you. Alright, keep it right there, everybody. This is theCube, from LiveWorx in Boston. We'll be right back after this short break.