>> theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (ambient music) >> Lisa: Hey everyone, welcome back to Barcelona, Spain. It's theCUBE Live at MWC 23. Lisa Martin with Dave Vellante. This is day two of four days of cube coverage but you know that, because you've already been watching yesterday and today. We're going to have a great conversation next with EnterpriseWeb and Red Hat. We've had great conversations the last day and a half about the Telco industry, the challenges, the opportunities. We're going to unpack that from this lens. Please welcome Dave Duggal, founder and CEO of EnterpriseWeb and Azhar Sayeed is here, Senior Director Solution Architecture at Red Hat. >> Guys, it's great to have you on the program. >> Yes. >> Thank you Lisa, >> Great being here with you. >> Dave let's go ahead and start with you. Give the audience an overview of EnterpriseWeb. What kind of business is it? What's the business model? What do you guys do? >> Okay so, EnterpriseWeb is reinventing middleware, right? So the historic middleware was to build vertically integrated stacks, right? And those stacks are now such becoming the rate limiters for interoperability for so the end-to-end solutions that everybody's looking for, right? Red Hat's talking about the unified platform. You guys are talking about Supercloud, EnterpriseWeb addresses that we've built middleware based on serverless architecture, so lightweight, low latency, high performance middleware. And we're working with the world's biggest, we sell through channels and we work through partners like Red Hat Intel, Fortnet, Keysight, Tech Mahindra. So working with some of the biggest players that have recognized the value of our innovation, to deliver transformation to the Telecom industry. >> So what are you guys doing together? Is this, is this an OpenShift play? >> Is it? >> Yeah. >> Yeah, so we've got two projects right her on the floor at MWC throughout the various partners, where EnterpriseWeb is actually providing an application layer, sorry application middleware over Red Hat's, OpenShift and we're essentially generating operators so Red Hat operators, so that all our vendors, and, sorry vendors that we onboard into our catalog can be deployed easily through the OpenShift platform. And we allow those, those vendors to be flexibly composed into network services. So the real challenge for operators historically is that they, they have challenges onboarding the vendors. It takes a long time. Each one of them is a snowflake. They, you know, even though there's standards they don't all observe or follow the same standards. So we make it easier using models, right? For, in a model driven process to on boards or streamline that onboarding process, compose functions into services deploy those services seamlessly through Red Hat's OpenShift, and then manage the, the lifecycle, like the quality of service and the SLAs for those services. >> So Red Hat obviously has pretty prominent Telco business has for a while. Red Hat OpenStack actually is is pretty popular within the Telco business. People thought, "Oh, OpenStack, that's dead." Actually, no, it's actually doing quite well. We see it all over the place where for whatever reason people want to build their own cloud. And, and so, so what's happening in the industry because you have the traditional Telcos we heard in the keynotes that kind of typical narrative about, you know, we can't let the over the top vendors do this again. We're, we're going to be Apifi everything, we're going to monetize this time around, not just with connectivity but the, but the fact is they really don't have a developer community. >> Yes. >> Yet anyway. >> Then you have these disruptors over here that are saying "Yeah, we're going to enable ISVs." How do you see it? What's the landscape look like? Help us understand, you know, what the horses on the track are doing. >> Sure. I think what has happened, Dave, is that the conversation has moved a little bit from where they were just looking at IS infrastructure service with virtual machines and OpenStack, as you mentioned, to how do we move up the value chain and look at different applications. And therein comes the rub, right? You have applications with different requirements, IT network that have various different requirements that are there. So as you start to build those cloud platform, as you start to modernize those set of applications, you then start to look at microservices and how you build them. You need the ability to orchestrate them. So some of those problem statements have moved from not just refactoring those applications, but actually now to how do you reliably deploy, manage in a multicloud multi cluster way. So this conversation around Supercloud or this conversation around multicloud is very >> You could say Supercloud. That's okay >> (Dave Duggal and Azhar laughs) >> It's absolutely very real though. The reason why it's very real is, if you look at transformations around Telco, there are two things that are happening. One, Telco IT, they're looking at partnerships with hybrid cloud, I mean with public cloud players to build a hybrid environment. They're also building their own Telco Cloud environment for their network functions. Now, in both of those spaces, they end up operating two to three different environments themselves. Now how do you create a level of abstraction across those? How do you manage that particular infrastructure? And then how do you orchestrate all of those different workloads? Those are the type of problems that they're actually beginning to solve. So they've moved on from really just putting that virtualizing their application, putting it on OpenStack to now really seriously looking at "How do I build a service?" "How do I leverage the catalog that's available both in my private and public and build an overall service process?" >> And by the way what you just described as hybrid cloud and multicloud is, you know Supercloud is what multicloud should have been. And what, what it originally became is "I run on this cloud and I run on this cloud" and "I run on this cloud and I have a hybrid." And, and Supercloud is meant to create a common experience across those clouds. >> Dave Duggal: Right? >> Thanks to, you know, Supercloud middleware. >> Yeah. >> Right? And, and so that's what you guys do. >> Yeah, exactly. Exactly. Dave, I mean, even the name EnterpriseWeb, you know we started from looking from the application layer down. If you look at it, the last 10 years we've looked from the infrastructure up, right? And now everybody's looking northbound saying "You know what, actually, if I look from the infrastructure up the only thing I'll ever build is silos, right?" And those silos get in the way of the interoperability and the agility the businesses want. So we take the perspective as high level abstractions, common tools, so that if I'm a CXO, I can look down on my environments, right? When I'm really not, I honestly, if I'm an, if I'm a CEO I don't really care or CXO, I don't really care so much about my infrastructure to be honest. I care about my applications and their behavior. I care about my SLAs and my quality of service, right? Those are the things I care about. So I really want an EnterpriseWeb, right? Something that helps me connect all my distributed applications all across all of the environments. So I can have one place a consistency layer that speaks a common language. We know that there's a lot of heterogeneity down all those layers and a lot of complexity down those layers. But the business doesn't care. They don't want to care, right? They want to actually take their applications deploy them where they're the most performant where they're getting the best cost, right? The lowest and maybe sustainability concerns, all those. They want to address those problems, meet their SLAs meet their quality service. And you know what, if it's running on Amazon, great. If it's running on Google Cloud platform, great. If it, you know, we're doing one project right here that we're demonstrating here is with with Amazon Tech Mahindra and OpenShift, where we took a disaggregated 5G core, right? So this is like sort of latest telecom, you know net networking software, right? We're deploying pulling elements of that network across core, across Amazon EKS, OpenShift on Red Hat ROSA, as well as just OpenShift for cloud. And we, through a single pane of deployment and management, we deployed the elements of the 5G core across them and then connected them in an end-to-end process. That's Telco Supercloud. >> Dave Vellante: So that's an O-RAN deployment. >> Yeah that's >> So, the big advantage of that, pardon me, Dave but the big advantage of that is the customer really doesn't care where the components are being served from for them. It's a 5G capability. It happens to sit in different locations. And that's, it's, it's about how do you abstract and how do you manage all those different workloads in a cohesive way? And that's exactly what EnterpriseWeb is bringing to the table. And what we do is we abstract the underlying infrastructure which is the cloud layer. So if, because AWS operating environment is different then private cloud operating environment then Azure environment, you have the networking is set up is different in each one of them. If there is a way you can abstract all of that and present it in a common operating model it becomes a lot easier than for anybody to be able to consume. >> And what a lot of customers tell me is the way they deal with multicloud complexity is they go with mono cloud, right? And so they'll lose out on some of the best services >> Absolutely >> If best of, so that's not >> that's not ideal, but at the end of the day, agree, developers don't want to muck with all the plumbing >> Dave Duggal: Yep. >> They want to write code. >> Azhar: Correct. >> So like I come back to are the traditional Telcos leaning in on a way that they're going to enable ISVs and developers to write on top of those platforms? Or are there sort of new entrance and disruptors? And I know, I know the answer is both >> Dave Duggal: Yep. >> but I feel as though the Telcos still haven't, traditional Telcos haven't tuned in to that developer affinity, but you guys sell to them. >> What, what are you seeing? >> Yeah, so >> What we have seen is there are Telcos fall into several categories there. If you look at the most mature ones, you know they are very eager to move up the value chain. There are some smaller very nimble ones that have actually doing, they're actually doing something really interesting. For example, they've provided sandbox environments to developers to say "Go develop your applications to the sandbox environment." We'll use that to build an net service with you. I can give you some interesting examples across the globe that, where that is happening, right? In AsiaPac, particularly in Australia, ANZ region. There are a couple of providers who have who have done this, but in, in, in a very interesting way. But the challenges to them, why it's not completely open or public yet is primarily because they haven't figured out how to exactly monetize that. And, and that's the reason why. So in the absence of that, what will happen is they they have to rely on the ISV ecosystem to be able to build those capabilities which they can then bring it on as part of the catalog. But in Latin America, I was talking to one of the providers and they said, "Well look we have a public cloud, we have our own public cloud, right?" What we want do is use that to offer localized services not just bring everything in from the top >> But, but we heard from Ericson's CEO they're basically going to monetize it by what I call "gouge", the developers >> (Azhar laughs) >> access to the network telemetry as opposed to saying, "Hey, here's an open platform development on top of it and it will maybe create something like an app store and we'll take a piece of the action." >> So ours, >> to be is a better model. >> Yeah. So that's perfect. Our second project that we're showing here is with Intel, right? So Intel came to us cause they are a reputation for doing advanced automation solutions. They gave us carte blanche in their labs. So this is Intel Network Builders they said pick your partners. And we went with the Red Hat, Fort Net, Keysite this company KX doing AIML. But to address your DevX, here's Intel explicitly wants to get closer to the developers by exposing their APIs, open APIs over their infrastructure. Just like Red Hat has APIs, right? And so they can expose them northbound to developers so developers can leverage and tune their applications, right? But the challenge there is what Intel is doing at the low level network infrastructure, right? Is fundamentally complex, right? What you want is an abstraction layer where develop and this gets to, to your point Dave where you just said like "The developers just want to get their job done." or really they want to focus on the business logic and accelerate that service delivery, right? So the idea here is an EnterpriseWeb they can literally declaratively compose their services, express their intent. "I want this to run optimized for low latency. I want this to run optimized for energy consumption." Right? And that's all they say, right? That's a very high level statement. And then the run time translates it between all the elements that are participating in that service to realize the developer's intent, right? No hands, right? Zero touch, right? So that's now a movement in telecom. So you're right, it's taking a while because these are pretty fundamental shifts, right? But it's intent based networking, right? So it's almost two parts, right? One is you have to have the open APIs, right? So that the infrastructure has to expose its capabilities. Then you need abstractions over the top that make it simple for developers to take, you know, make use of them. >> See, one of the demonstrations we are doing is around AIOps. And I've had literally here on this floor, two conversations around what I call as network as a platform. Although it sounds like a cliche term, that's exactly what Dave was describing in terms of exposing APIs from the infrastructure and utilizing them. So once you get that data, then now you can do analytics and do machine learning to be able to build models and figure out how you can orchestrate better how you can monetize better, how can how you can utilize better, right? So all of those things become important. It's just not about internal optimization but it's also about how do you expose it to third party ecosystem to translate that into better delivery mechanisms or IOT capability and so on. >> But if they're going to charge me for every API call in the network I'm going to go broke (team laughs) >> And I'm going to get really pissed. I mean, I feel like, I'm just running down, Oracle. IBM tried it. Oracle, okay, they got Java, but they don't they don't have developer jobs. VMware, okay? They got Aria. EMC used to have a thing called code. IBM had to buy Red Hat to get to the developer community. (Lisa laughs) >> So I feel like the telcos don't today have those developer shops. So, so they have to partner. [Azhar] Yes. >> With guys like you and then be more open and and let a zillion flowers bloom or else they're going to get disrupted in a big way and they're going to it's going to be a repeat of the over, over the top in, in in a different model that I can't predict. >> Yeah. >> Absolutely true. I mean, look, they cannot be in the connectivity business. Telcos cannot be just in the connectivity business. It's, I think so, you know, >> Dave Vellante: You had a fry a frozen hand (Dave Daggul laughs) >> off that, you know. >> Well, you know, think about they almost have to go become over the top on themselves, right? That's what the cloud guys are doing, right? >> Yeah. >> They're riding over their backbone that by taking a creating a high level abstraction, they in turn abstract away the infrastructure underneath them, right? And that's really the end game >> Right? >> Dave Vellante: Yeah. >> Is because now, >> they're over the top it's their network, it's their infrastructure, right? They don't want to become bid pipes. >> Yep. >> Now you, they can take OpenShift, run that in any cloud. >> Yep. >> Right? >> You can run that in hybrid cloud, enterprise web can do the application layer configuration and management. And together we're running, you know, OSI layers one through seven, east to west, north to south. We're running across the the RAN, the core and the transport. And that is telco super cloud, my friend. >> Yeah. Well, >> (Dave Duggal laughs) >> I'm dominating the conversation cause I love talking super cloud. >> I knew you would. >> So speaking of super superpowers, when you're in customer or prospective customer conversations with providers and they've got, obviously they're they're in this transformative state right now. How, what do you describe as the superpower between Red Hat and EnterpriseWeb in terms of really helping these Telcos transforms. But at the end of the day, the connectivity's there the end user gets what they want, which is I want this to work wherever I am. >> Yeah, yeah. That's a great question, Lisa. So I think the way you could look at it is most software has, has been evolved to be specialized, right? So in Telcos' no different, right? We have this in the enterprise, right? All these specialized stacks, all these components that they wire together in the, in you think of Telco as a sort of a super set of enterprise problems, right? They have all those problems like magnified manyfold, right? And so you have specialized, let's say orchestrators and other tools for every Telco domain for every Telco layer. Now you have a zoo of orchestrators, right? None of them were designed to work together, right? They all speak a specific language, let's say quote unquote for doing a specific purpose. But everything that's interesting in the 21st century is across layers and across domains, right? If a siloed static application, those are dead, right? Nobody's doing those anymore. Even developers don't do those developers are doing composition today. They're not doing, nobody wants to hear about a 6 million lines of code, right? They want to hear, "How did you take these five things and bring 'em together for productive use?" >> Lisa: Right. How did you deliver faster for my enterprise? How did you save me money? How did you create business value? And that's what we're doing together. >> I mean, just to add on to Dave, I was talking to one of the providers, they have more than 30,000 nodes in their infrastructure. When I say no to your servers running, you know, Kubernetes,running open stack, running different components. If try managing that in one single entity, if you will. Not possible. You got to fragment, you got to segment in some way. Now the question is, if you are not exposing that particular infrastructure and the appropriate KPIs and appropriate things, you will not be able to efficiently utilize that across the board. So you need almost a construct that creates like a manager of managers, a hierarchical structure, which would allow you to be more intelligent in terms of how you place those, how you manage that. And so when you ask the question about what's the secret sauce between the two, well this is exactly where EnterpriseWeb brings in that capability to analyze information, be more intelligent about it. And what we do is provide an abstraction of the cloud layer so that they can, you know, then do the right job in terms of making sure that it's appropriate and it's consistent. >> Consistency is key. Guys, thank you so much. It's been a pleasure really digging through EnterpriseWeb. >> Thank you. >> What you're doing >> with Red Hat. How you're helping the organization transform and Supercloud, we can't forget Supercloud. (Dave Vellante laughs) >> Fight Supercloud. Guys, thank you so much for your time. >> Thank you so much Lisa. >> Thank you. >> Thank you guys. >> Very nice. >> Lisa: We really appreciate it. >> For our guests and for Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live tech coverage coming to you live from MWC 23. We'll be back after a short break.

(electronic music) (background party chatter) >> All right. Hello, everyone. Welcome to The Cube. Coming up, Bryan Talebi will be here with Ahura A.I? >> Ahura A.I. >> Ahura A.I. Bryan Talebi here with Ahura A.I. We are at The Cube post party networking event, special on the ground, extended coverage. Bryan, we were at The Futurist, not The Futurist Conference, The Future of Blockchain which was the Monaco Crypto Summit over at the Grimaldi Center. Now we're at the VIP gala, the prince is here, a lot of action's happening. You had a chance to look all the presentations we have all the heavy hitters here, kind of a movement going on, right? >> Absolutely. Well, first of all, I think it's absolutely amazing that Prince Albert II put this all together. He obviously understands the future and understands technology. It's absolutely brilliance. And Julio as well, I mean is incredible. So I take off my hat to all the people that put this event together and the speakers were brilliant. I mean, did you see all the speakers the technologies that they've built have the potential to radically transform billions of people's lives. >> It's interesting, you know, I've been covering crypto for a very long time and watched it emerge and then start exploding. And there's always been, and I saw this with the web too early on, legit versus not legit. And all early markets have the hype cycles go down and up, and you always kind of have that but now you're starting to see legitimate tie-in between physical digital assets where, and the confluence of the business value, societal value, government value, all across the spectrum. Every vertical, every use case is got a decentralized vibe going on right now because it's a forcing function. And, and here in Monaco, the price and the king they're leaning into it cause I think they see the future because they could answer their legacy. >> Yeah. Absolutely. And look, you're absolutely right about this because this downturn that we're facing, especially this new crypto winter, I think is the best thing that could possibly have happened to the crypto space because what it's doing is pushing out the let's call them the less than honest brokers within the crypto community, the people that were just in it for a buck, the pump and dumpers and so forth it's really pushing those folks out. And the companies that remain are the true technologists that aren't looking at crypto as just a speculative asset, but rather an underlying technology that can transform the way that we engage with the world in a decentralized way. >> Bryan, you know, we didn't mention in the intro but you also do investment. >> I do. >> You also have a lot of things going on. You got a great history, great pedigree of seeing the waves of innovation the best. That's something, an investment question, like are you in it for the money or are you in it for the make it happen mission? That becomes kind of like the probing question. Someone comes to the table, "Hey, I need some cash. We do funding." What's your exit strategy? "I want to make an exit in two years." Okay. You're out. (Bryan laughs) (John) But it's almost that easy now, right? >> Sure. >> (John) To figure out who's in it for the money. >> Sure. >> (John) Who's in it for the mission. Yeah, the mission's successful. You make a lot of money. >> That's exactly right. Look, one of my mentors once taught me is, money like power is only amassed in great amount if indirectly sought because money by itself is not intrinsically a motivator. And so, what we do at our AB+ Ventures, my venture capital fund, is we only invest, not only in companies that are impact driven and have the capacity to impact a billion people, but we invest in founders that are climbing their third or fourth mountain. So these are people who've already made their money. They either had a couple big exits at over a hundred million dollars or they became rock stars or they became astronauts. They did things where they achieved the highest levels of achievement. And now are building technologies because they believe that they're going to impact the world in a meaningful way. >> They kind of know it's important, right? They made some money, they've been successful. They have scar tissue and experience to apply almost I want to say for the legacy of it, but more for value. >> Yeah. >> For everybody. >> Absolutely. >> All right. So I got to ask about what your current venture, I know you got some good action going on. It's growing pretty good. As they say in golf, it's middle of the fairway. It's growing, got momentum. It's a turbine market. You probably has some offers on the table. I mean, I could imagine all the AI you got going on. Blockchain, very attracted. It's a hard problem, but it's the first inning. Not even. >> Yeah. >> What going on with the company? >> We're very early. Look, we've been building our technologies, the deep tech platform we've been building for four and a half years. There's a whole bunch of offers on the table to buy us. But look, the reality is right now is a fantastic hiring opportunity. There's a lot of amazing talent out there that now wants to come to us, which is great. Number one, number two, if you look back to the 2000 Dot-com bubble, what you saw is all of the companies that didn't really solve real problems went away and it left a more oxygen in the room for the companies that were really solving problems that needed to be solved. And those are now all trillion dollar companies. So, >> Well, Brian, you and I both got a little gray hair. So let's talk about the Dot-com bubble. The other thing, I'll add to that, by the way great commentary, is that everything that was like bullshit actually happened. People bought pet food online, >> Right. >> Groceries delivered to their house. So to your point, the things actually happen. See the visions and the aspirations were correct, timing and capital markets spree. >> Sure. >> Is there similarities going on in crypto? Is it the crypto winter, weeding out those pretenders? Is that what you're saying? >> Well, there's definitely a lot of similarities there but if you look at the example that you use, right, pets.com versus Amazon, people are still buying pet food online. I buy all my pet supplies for my two puppies online. However, if you look at the reason that Amazon works is because of their supply chain and the innovations that they created on being able to deliver anything to you within a day or two days in an extremely cost effective manner. It wasn't just because they had a website and they did some hand wavy stuff to say isn't this a good idea. You actually have to have the underlying operational capability and innovation from a technology standpoint to make it happen. And so, when we talk about crypto over the past number of years, and I've been in the crypto space for a long time, as you have there's been a lot of hand wavy stuff. There's been a lot of people like, "wouldn't this be a good idea?" but then you have the true operators that are able to find the underlying competitive advantages that actually make it work. And that's what I'm interested in. >> I'd love to get your thoughts on that. First of all, great point if you look at like, I was just commentating earlier I was asked the question what I think, and I said, well, I do a lot of lot of reporting and analysis on cloud computing. I watch what Amazon Web Service has done from many, many years ago. And all the followers now. Scale data, higher level services, they're all happening and it's creating a lot of value. Okay? That's going to come to crypto. And so, okay, the dots aren't connected there yet, but you've got this, but one of the things that has proven to be a success criteria, ecosystems. When you have enabling technology like DigitalBits, for instance, is kind the main powering of this ecosystem here, the value that's being created on top of it has to be a step function or multiple of the cost or operational cost to deploy the platform. Okay, so that's kind of in concert with everyone else. You product decentralized, what's your thoughts on that? Because now you have a lot of potential ecosystems that could connect together cause there's no one centralized ecosystem. >> (Bryan) Absolutely. >> But what is, what, how do you get that? How do you square that circle? So to speak. What's your take on that? How does ecosystems play into defi, decentralization, de-apps blockchain? >> So what you really talking about is interoperable, right? So again, if we use an analogy, if we look back to the late nineties, when Web 1.0 was really flourishing and then in the 2000s where everybody created their own websites, people went to the world wide web, but every company had their own website. They had their own social media platform. They had their entire Salesforce platform or what have you. So everyone had their entire separate organization. And so, I suspect that the future of crypto is going to be very similar, where there's going to be a bunch of different metaverses, a bunch of different ecosystems, but someone's going to come along, and I think there's a number of people on the back end that are actually working on this, Some of them are really brilliant, that are going to create an interoperable mechanism for people that jump from metaverse to metaverse from chain to chain in a completely easy experience from a user experience standpoint where you don't have to have a PhD in crypto, so to speak, that doesn't exist, but you don't have to have that level. >> Well, if you're working on crypto for the past five years you've got a PhD. >> Basically. >> The thesis is, you're still alive producing. (Brian laughs) Well, that's a good point. So I'm looking for like, this defacto enabler, right? Because TCP/IP was an example in the old days, you know, the levels of the stack that never, TCP/IP is part of the OSI model. It's just interconnect. That layer, nothing got above it, was open. It was just hard and top that TCP/IP the rest was all standard. Ethernet, token ring add that data layer and then cards. That worked, the industry could galvanize around that. I'm waiting for the crypto moment now, where, what is going to be that cloud (indistinct), Kubernetes and service matches and whatnot. What, is there anything on the horizon that you see that has that kind of coalescent ecosystem, let's get, if we all get behind this, we all win. Rather than chasing crumbs. >> Sure. >> You know, the bigger pie, rising tide, all that stuff. >> Well, so I think there's a really interesting analogy from a couple of hundred years ago on this. So most people don't realize that when the United States first had their railroad system which was the innovative infrastructure play at the time each state or each region had their own systems they had different size railroad. So what would happen if you were trying to ship a bunch of grain from one part of the country to the other you would take it by a train. You get to a train station, you'd have to take everything off, put it on a different train, on a different set of train tracks. You would go a couple states over. You'd have to do that again, go a couple states over. You have to do that again. Eventually what happened is the federal government came in and said, hey, we need to create a system of policies around one set of rules for all trains and all logistics across the country. And so, I do think there's a role for governments to come together, along with the operators and the companies to work collaboratively together to say, hey, what are the regulations? What are the rules of the road? How do we make sure we get all the scam artists out of the system? How do we create a system that actually works for everybody? Now, there's always dangers there, right? You have regulatory capture. Sometimes the government, oftentimes they're slow, they don't understand the technology. So they come down with a heavy hand. And so if it's done properly, and it's not just the United States alone, by the way, it's all the countries in the world. Now at this point, it's a global effort. >> There's money involved, too. >> Exactly. But if we are able to bring together people that are much smarter than me from the public and private sectors as well as the nonprofit sectors, together to come up with one set of rules I think that will enable crypto to massively expand across the entire globe. >> What are you passionate about right now? I know you got the investment fund for, you know, helping society and the planet, you get your project with your startup company, AI is in a hot area. What's going on? What's your top goals for the year? >> So there's two things. Number one, my company, Ahura A.I. is my baby. It's where I spend 70, 80 hours a week. We invent a technology that enables people to learn three to five times faster than traditional education. >> (John) Is that so? >> Because I believe that education is the first step. It's the first variable, that impacts all of the sustainable development goals, impacts the world in a very real way. >> And you're not wearing your UA pin. >> I'm not wearing my pin, I always point to it. >> I wanted to grab it, I saw it earlier. >> But then the second thing I'm super focused on is existential risk. Look, so I throw a lot of events where I bring together four categories of people, CEOs of impact driven companies, investors, whether they're VCs or billionaires or family offices, global experts, and celebrities that want to use their influence for good in the world. And one of the speakers that I had at one of my events is a guy at Stanford who runs their lab on existential risk and what he told the group, and what he told me, is according to Stanford and all the researchers, there's a one in six chance that we're all going to go extinct by 2050. One in six, that's a dice roll. And so to me, the most important thing I can do is bring people together that have capacity, have resources, have capabilities, to address these drivers of existential risk because selfishly, I don't want to live in a dystopian Hellscape. >> Exactly, yeah. Bryan, thanks for coming on. We're going to get back into dinner. Great to see you. >> Thank you very much. >> The Cube after dark, extended hours. Look at us, we're going the whole day. VIP gala, Prince Albert, the team, DigitalBits, The Cube, all here at the Yacht Club in Monaco. I'm John Furrier. Thanks for watching.

(upbeat music) >> Greetings from Los Angeles, Lisa Martin here with Dave Nicholson. We are on day three of the caves wall-to-wall coverage of KubeCon CloudNativeCon North America 21. We're pleased to welcome Mark Hinkle to the program, the co-founder and CEO of TriggerMesh. Mark welcome. >> Thank you, It's nice to be here. >> Lisa: Love the name. Very interesting TriggerMesh. Talk to us about what TriggerMesh does and what, when you were founded and what some of the gaps were that you saw in the market. >> Yeah, so TriggerMesh actually the Genesis of the name is in, cloud event, driven architecture. You trigger workloads. So that's the trigger and trigger mesh, and then mesh, we mesh services together, so cloud, so that's why we're called TriggerMesh. So we're a cloud native open source integration platform. And the idea is that, the number of cloud services are proliferating. You still have stuff in your data center that you can't decommission and just wholesale lift and shift to the cloud. So we wanted to provide a platform to create workflows from the data center, to the cloud, from cloud to cloud and not, and use all the cloud native design principles, but not leave your past behind. So that's, what we do. We're, very, we were cloud, we are cloud operators and developers, and we wanted the experience to be very similar to the way that DevOps folks are doing infrastructure code and deploying that we want to make it easy to do integration as code. So we follow the same design patterns, use the same domain languages, some of those tools like Hashi corpse, Terraform, and that that's what we do and how we go about doing it. >> Lisa: And when were you guys founded? >> September, 2018. >> Oh so your young, your three years young. >> Three years it's feels like 21 >> I bet. >> And startup years it's a lot has happened, but yeah, we my co-founder and I were former early cloud folks. We were at cloud.com worked through the OpenStack years and the CloudStack, and we just saw the pattern of, abstraction coming about. So first you abstract the hardware, then you abstract the operating system. And now at with the Kubernetes container, you know, evolution, you're abstracting it up to the application layer and we want it to be able to provide tooling that lets you take full advantage of that. >> Dave: So being founded in 2018, what's your perception of that? The shift that happened during the pandemic in terms of the drive towards cloud adoption and the demands for services like you provide? >> Mark: Yeah, I think it's a mixed blessing. So we, people became more remote. They needed to enable digital transformation. Biggest thing, I think that that for us is, you know, you don't go to the bank anymore. And the banking industry is doing, you know, exponentially more remote, online transactions than in person. And it's very important. So we decided that financial services is where we were going to start with first because they have a lot of legacy architecture. They have a lot of need to move to the cloud to have better digital experiences. And we wanted to enable them to, you know, keep their mainframes online while they were still doing cutting edge, you know, mobile applications, that kind of thing. >> Lisa: And of course the legacy institutions like the BFA's the Wells Fargo, they're competing with the fintechs who are much more nimble, much more agile and able to sort of disrupt the financial services industry. Was that part of also your decision to start in financial services? >> It was a little bit of luck because we started with our network and it turned out the, you know, we saw, we started talking to our friends early on, cause we're a startup and said, this is what we're going to do. And where it really resonated was PNC bank was our, one of our first customers. You know, another financial regulatory company was another one, a couple of banks in Europe. And we, you know, as we started talking about what we were doing, that we just gravitated there because they had the, the biggest need, even though everybody has the need, their businesses are, you know, critically tied to digital transformation. >> So starting with financial services. >> It's, it's counter intuitive, isn't it? >> It was counterintuitive, but it lends credibility to any other industry vertical that you're going to approach. >> Yeah, yeah it does. It's a, it's a great, they're going to be our hardest customers and they have more at stake than a lot of like transactions are millions and millions of dollars per hour for these folks. So they don't want to play around, they, they have no tolerance for failure. So it's a good start, but it's sort of like taking up jogging and running a marathon in your first week. It's very very grilling in that sense, but it really has made us a lot better and gave us a lot of insight into the kinds of things we need to do from not just functionality, but security and that kind of thing. >> Where are you finding these customers with respect to adoption of Kubernetes? Are they leading? Are they knowing we've got to get there eventually from an infrastructure perspective? >> So the interesting thing is Kubernetes is a platform for us to deliver on, so we, we don't require you to be a Kubernetes expert we offer it as a SaaS, but what happens is that the Kubernetes folks are the ones that we end up really engaging with earlier on. And I think that we find that they're in this phase of they're containerizing their apps, that's the first step. And then they're putting them on Kubernetes and then their next step is a security and integration path. So once she, I think they call it and this is my buzzword of the show day two operations, right? So they, they get to day two and then they have a security and an integration concern before they go live. So they want to be able to make sure that they don't increase their attack face. And then they also want to make sure that this newly deployed containerized infrastructure is as well integrated as the previous, you know, virtualized or even, you know, on the server infrastructure that they had before. >> So TriggerMesh, doesn't solely work in the containerized world, you're, you're sort of you're bridging the divide. >> Mark: Yes. >> What percentage of the workloads that you're seeing are the result of modernization migration, as opposed to standing up net new application environments in Kubernetes? Do you have a sense for that? >> I think we live in a lot in the brown field. So, you know, folks that have an existing project that they're trying to bridge to it versus the Greenfield kind of, you know, the, the huge wins that you saw in the early cloud days of the Netflix and the Twitter's Dwayne scale. Now we're talking to the enterprises who have, you know, they have existing concerns. So I would say that it's, it's mostly people that are, you know, very few net new projects, unless it's a modernization and they're getting ready to decommission an old one, which is. >> Dave: So Brownfield financial services. You just said, you know, let's just, let's just go after that. >> You know, yeah. I mean, we had this dart forward and we put up buzzwords, but no, it was, it was actually just, and you know, we're still finding our way as far as early on where we're open source folks. And we did not open source from day one, which is very weird when everybody's new, your identity is, you know, I worked, I was the VP of marketing for Linux foundation and no JS and all these open source projects. And my co-founder and I are Apache committers. And our project wasn't open yet because we had to get to the point where it could be open and people could be productive in the use and contribution. And we had to staff up engineers. And now I think this week we open-sourced our entire platform. And I think that's going to open up, you know, that's where we started because it was not necessarily the lowest hanging fruit, but the profitable, less profitable, lowest hanging fruit was financial services. Now we are letting our code out into the wild. And I think it'll be interesting to see what comes back. >> So you just announced that this week TriggerMesh integration platform as an open source project here at KubeCon, what's been some of the feedback? >> It's all been positive. I haven't heard anything negative. We did it, so we're very, very, there's a very, the culture around open source is very tough. It's very critical if you don't do it right. So I think we did a good job, we used enough, we used a OSI approved. They've been sourced, licensed the Apache software, a V2 license. We hired someone who was well-respected in the DevREL world from a chef who understands the DevOps sort of culture methodologies. We staffed up our engineers who are going to be helping the free and open source users. So they're successful and we're betting that that will yield business results down the road. >> Lisa: And what are the two I see on your website, two primary use cases that you guys support. Can you dig into details on that? >> So the first one is sort of a workflow automation and a really simple example of that is you have a, something that happens in one cloud. So for example, you take a picture on your phone and you upload it and it goes to Amazon and there is a service that wants to identify what's in that picture. And once you put it on the line and the internship parlance, you could kick off a workflow from TensorFlow, which is artificial intelligence to identify the picture. And there isn't a good way for clouds to communicate from one to the other, without writing custom blue, which is really what, what we're helping to get rid of is there's a lot of blue written to put together cloud native applications. So that's a workflow, you know, triggering a server less function is the workflow. The other thing is actually breaking up data gravity. So I have a warehouse of data, in my data center, and I want to start replicating some portion of that. As it changes to a database as a service, we can based on an event flow, which is passive. We're not, we're not making, having a conversation like you would with an API where there's an event stream. That's like drinking from the fire hose and TriggerMesh is the nozzle. And we can direct that data to a DBaaS. We can direct that data to snowflake. We can direct that data to a cloud-based data lake on Microsoft Azure, or we can split it up, so some events could go to Splunk and all of the events can go to your data lake or some of those, those things can be used to trigger workloads on other systems. And that event driven architecture is really the design pattern of the individual clouds. We're just making it multi-cloud and on-prem. >> Lisa: Do you have a favorite customer example that you think really articulates that the value of that use case? >> Mark: Yeah I think a PNC is probably our, well for the, for the data flow one, I would say we have a regular to Oracle and one of their customers it was their biggest SMB customer of last year. The Oracle cloud is very, very important, but it's not as tool. It doesn't have the same level of tooling as a lot of the other ones. And to, to close that deal, their regulatory customer wanted to use Datadog. So they have hundreds and hundreds of metrics. And what TriggerMesh did was ingest the hundreds and hundreds of metrics and filter them and connect them to Datadog so that, they could, use Datadog to measure, to monitor workloads on Oracle cloud. So that, would be an example of the data flow on the workflow. PNC bank is, is probably our best example and PNC bank. They want to do. I talked about infrastructure code integration is code. They want to do policy as code. So they're very highly regulatory regulated. And what they used to do is they had policies that they applied against all their systems once a month, to determine how much they were in compliance. Well, theoretically if you do that once a month, it could be 30 days before you knew where you were out of compliance. What we did was, we provided them a way to take all of the changes within their systems and for them to a server less cluster. And they codified all of these policies into server less functions and TriggerMesh is triggering their policies as code. So upon change, they're getting almost real-time updates on whether or not they're in compliance or not. And that's a huge thing. And they're going to, they have, within their first division, we worked with, you know, tens of policies throughout PNC. They have thousands of policies. And so that's really going to revolutionize what they're able to do as far as compliance. And that's a huge use case across the whole banking system. >> That's also a huge business outcome. >> Yes. >> So Mark, where can folks go to learn more about TriggerMesh, maybe even read about more specifically about the announcement that you made this week. >> TriggerMesh.com is the best way to get an overview. The open source project is get hub.com/triggermesh/trigger mesh. >> Awesome Mark, thank you for joining Dave and me talking to us about TriggerMesh, what you guys are doing. The use cases that you're enabling customers. We appreciate your time and we wish you best of luck as you continue to forge into financial services and other industries. >> Thanks, it was great to be here. >> All right. For Dave Nicholson, I'm Lisa Martin coming to you live from Los Angeles at KubeCon and CloudNativeCon North America 21, stick around Dave and I, will be right back with our next guest.

>> From around the globe, it's theCUBE, with coverage of KubeCon and CloudNativeCon Europe 2021 Virtual. Brought to you by Red Hat, the Cloud Native Computing Foundation and ecosystem partners. >> Hello, welcome back to theCUBE's coverage of KubeCon 2021 CloudNativeCon Europe Virtual, I'm John Furrier your host, preview with Brian Gracely from Red Hat Senior Director Product Strategy Cloud Business Unit Brian Gracely great to see you. Former CUBE host CUBE alumni, big time strategist at Red Hat, great to see you, always great. And also the founder of Cloudcast which is an amazing podcast on cloud, part of the cloud (indistinct), great to see you Brian. Hope's all well. >> Great to see you too, you know for years, theCUBE was always sort of the ESPN of tech, I feel like, you know ESPN has become nothing but highlights. This is where all the good conversation is. It's theCUBE has become sort of the the clubhouse of tech, if you will. I know that's that's an area you're focused on, so yeah I'm excited to be back on and good to talk to you. >> It's funny you know, with all the events going away loved going out extracting the signal from the noise, you know, game day kind of vibe. CUBE Virtual has really expanded, so it's been so much more fun because we can get more people easy to dial in. So we're going to keep that feature post COVID. You're going to hear more about theCUBE Virtual hybrid events are going to be a big part of it, which is great because as you know and we've talked about communities and ecosystems are huge advantage right now it's been a big part of the Red Hat story. Now part of IBM bringing that mojo to the table the role of ecosystems with hybrid cloud is so critical. Can you share your thoughts on this? Because I know you study it, you have podcasts you've had one for many years, you understand that democratization and this new direct to audience kind of concept. Share your thoughts on this new ecosystem. >> Yeah, I think so, you know, we're sort of putting this in the context of what we all sort of familiarly call KubeCon but you know, if we think about it, it started as KubeCon it was sort of about this one technology but it's always been CloudNativeCon and we've sort of downplayed the cloud native part of it. But even if we think about it now, you know Kubernetes to a certain extent has kind of, you know there's this feeling around the community that, that piece of the puzzle is kind of boring. You know, it's 21 releases in, and there's lots of different offerings that you can get access to. There's still, you know, a lot of innovation but the rest of the ecosystem has just exploded. So it's, you know, there are ecosystem partners and companies that are working on edge and miniaturization. You know, we're seeing things like Kubernetes now getting into outer space and it's in the space station. We're seeing, you know, Linux get on Mars. But we're also seeing, you know, stuff on the other side of the spectrum. We're sort of seeing, you know awesome people doing database work and streaming and AI and ML on top of Kubernetes. So, you know, the ecosystem is doing what you'd expect it to do once one part of it gets stable. The innovation sort of builds on top of it. And, you know, even though we're virtual, we're still seeing just tons and tons of contributions, different companies different people stepping up and leading. So it's been really cool to watch the last few years. >> Yes, interesting point about the CloudNativeCon. That's an interesting insight, and I totally agree with you. And I think it's worth double clicking on. Let me just ask you, because when you look at like, say Kubernetes, okay, it's enabled a lot. Okay, it's been called the dial tone of Cloud native. I think Pat Gelsinger of VMware used that term. We call it the kind of the interoperability layer it enables more large scale deployments. So you're seeing a lot more Kubernetes enablement on clusters. Which is causing more hybrid cloud which means more Cloud native. So it actually is creating a network effect in and of itself with more Cloud native components and it's changing the development cycle. So the question I want to ask you is one how does a customer deal with that? Because people are saying, I like hybrid. I agree, Multicloud is coming around the corner. And of course, Multicloud is just a subsystem of resource underneath hybrid. How do I connect it all? Now I have multiple vendors, I have multiple clusters. I'm cross-cloud, I'm connecting multiple clouds multiple services, Kubernetes clusters, some get stood up some gets to down, it's very dynamic. >> Yeah, it's very dynamic. It's actually, you know, just coincidentally, you know, our lead architect, a guy named Clayton Coleman, who was one of the Kubernetes founders, is going to give a talk on sort of Kubernetes is this hybrid control plane. So we're already starting to see the tentacles come out of it. So you know how we do cross cloud networking how we do cross cloud provisioning of services. So like, how do I go discover what's in other clouds? You know and I think like you said, it took people a few years to figure out, like how do I use this new thing, this Kubernetes thing. How do I harness it. And, but the demand has since become "I have to do multi-cloud." And that means, you know, hey our company acquires companies, so you know, we don't necessarily know where that next company we acquire is going to run. Are they going to run on AWS? Are they going to, you know, run on Azure I've got to be able to run in multiple places. You know, we're seeing banking industries say, "hey, look cloud's now a viable target for you to put your applications, but you have to treat multiple clouds as if they're your backup domains." And so we're, you know, we're seeing both, you know the way business operates whether it's acquisitions or new things driving it. We're seeing regulations driving hybrid and multi-cloud and, even you know, even if the stalwart were to you know, set for a long time, well the world's only going to be public cloud and sort of you know, legacy data centers even those folks are now coming around to "I've got to bring hybrid to, to these places." So it's been more than just technology. It's been, you know, industries pushing it regulations pushing it, a lot of stuff. So, but like I said, we're going to be talking about kind of our future, our vision on that, our future on that. And, you know Red Hat everything we end up doing is a community activity. So we expect a lot of people will get on board with it >> You know, for all the old timers out there they can relate to this. But I remember in the 80's the OSI Open Systems Interconnect, and I was chatting with Paul Cormier about this because we were kind of grew up through that generation. That disrupted network protocols that were proprietary and that opened the door for massive, massive growth massive innovation around just getting that interoperability with TCP/IP, and then everything else happened. So Kubernetes does that, that's a phenomenal impact. So Cloud native to me is at that stage where it's totally next-gen and it's happening really fast. And a lot of people getting caught off guard, Brian. So you know, I got to to ask you as a product strategist, what's your, how would you give them the navigation of where that North star is? If I'm a customer, okay, I got to figure out where I got to navigate now. I know it's super volatile, changing super fast. What's your advice? >> I think it's a couple of pieces, you know we're seeing more and more that, you know, the technology decisions don't get driven out of sort of central IT as much anymore right? We sort of talk all the time that every business opportunity, every business project has a technology component to it. And I think what we're seeing is the companies that tend to be successful with it have built up the muscle, built up the skill set to say, okay, when this line of business says, I need to do something new and innovative I've got the capabilities to sort of stand behind that. They're not out trying to learn it new they're not chasing it. So that's a big piece of it, is letting the business drive your technology decisions as opposed to what happened for a long time which was we built out technology, we hope they would come. You know, the other piece of it is I think because we're seeing so much push from different directions. So we're seeing, you know people put technology out at the edge. We're able to do some, you know unique scalable things, you know in the cloud and so forth That, you know more and more companies are having to say, "hey, look, I'm not, I'm not in the pharmaceutical business. I'm not in the automotive business, I'm in software." And so, you know the companies that realize that faster, and then, you know once they sort of come to those realizations they realize, that's my new normal, those are the ones that are investing in software skills. And they're not afraid to say, look, you know even if my existing staff is, you know, 30 years of sort of history, I'm not afraid to bring in some folks that that'll break a few eggs and, you know, and use them as a lighthouse within their organization to retrain and sort of reset, you know, what's possible. So it's the business doesn't move. That's the the thing that drives all of them. And it's, if you embrace it, we see a lot of success. It's the ones that, that push back on it really hard. And, you know the market tends to sort of push back on them as well. >> Well we're previewing KubeCon CloudNativeCon. We'll amplify that it's CloudNativeCon as well. You guys bought StackRox, okay, so interesting company, not an open source company they have soon to be, I'm assuring, but Advanced Cluster Security, ACS, as it's known it's really been a key part of Red Hat. Can you give us the strategy behind that deal? What does that product, how does it fit in that's a lot of people are really talking about this acquisition. >> Yeah so here's the way we looked at it, is we've learned a couple of things over the last say five years that we've been really head down in Kubernetes, right? One is, we've always embedded a lot of security capabilities in the platform. So OpenShift being our core Kubernetes platform. And then what's happened over time is customers have said to us, "that's great, you've made the platform very secure" but the reality is, you know, our software supply chain. So the way that we build applications that, you know we need to secure that better. We need to deal with these more dynamic environments. And then once the applications are deployed they interact with various types of networks. I need to better secure those environments too. So we realized that we needed to expand our functionality beyond the core platform of OpenShift. And then the second thing that we've learned over the last number of years is to be successful in this space, it's really hard to take technology that wasn't designed for containers, or it wasn't designed for Kubernetes and kind of retrofit it back into that. And so when we were looking at potential acquisition targets, we really narrowed down to companies whose fundamental technologies were you know, Kubernetes-centric, you know having had to modify something to get to Kubernetes, and StackRox was really the leader in that space. They really, you know have been the leader in enterprise Kubernetes security. And the great thing about them was, you know not only did they have this Kubernetes expertise but on top of that, probably half of their customers were already OpenShift customers. And about 3/4 of their customers were using you know, native Kubernetes services and other clouds. So, you know, when we went and talked to them and said, "Hey we believe in Kubernetes, we believe in multi-cloud. We believe in open source," they said, "yeah, those are all the foundational things for us." And to your point about it, you know, maybe not being an open source company, they actually had a number of sort of ancillary projects that were open source. So they weren't unfamiliar to it. And then now that the acquisition's closed, we will do what we do with every piece of Red Hat technology. We'll make sure that within a reasonable period of time that it's made open source. And so you know, it's good for the community. It allows them to keep focusing on their innovation. >> Yeah you've got to get that code out there cool. Brian, I'm hearing about Platform Plus what is that about? Take us through that. >> Yeah, so you know, one of the things that our customers, you know, have come to us over time is it's you know, it's like, I've been saying kind of throughout this discussion, right? Kubernetes is foundational, but it's become pretty stable. The things that people are solving for now are like, you highlighted lots and lots of clusters, they're all over the place. That was something that our advanced cluster management capabilities were able to solve for people. Once you start getting into lots of places you've got to be able to secure things everywhere you go. And so OpenShift for us really allows us to bundle together, you know, sort of the complete set of the portfolio. So the platform, security management, and it also gives us the foundational pieces or it allows our customers to buy the foundational pieces that are going to help them do multi and hybrid cloud. And, you know, when we bundle that we can save them probably 25% in terms of sort of product acquisition. And then obviously the integration work we do you know, saves a ton on the operational side. So it's a new way for us to, to not only bundle the platform and the technologies but it gets customers in a mindset that says, "hey we've moved past sort of single environments to hybrid and multi-cloud environments. >> Awesome, well thanks for the update on that, appreciate it. One of the things going into KubeCon, and that we're watching closely is this Cloud native developer action. Certainly end users want to get that in a separate section with you but the end user contribution, which is like exploding. But on the developer side there's a real trend towards adding stronger consistency programmability support for more use cases okay. Where it's becoming more of a data platform as a requirement. >> Brian: Right. >> So how, so that's a trend so I'm kind of thinking, there's no disagreement on that. >> Brian: No, absolutely. >> What does that mean? Like I'm a customer, that sounds good. How do I make that happen? 'Cause that's the critical discussion right now in the DevOps, DevSecOps day, two operations. What you want to call it. This is the number one concern for developers and that solution architect, consistency, programmability more use cases with data as a platform. >> Yeah, I think, you know the way I kind of frame this up was you know, for any for any organization, the last thing you want to to do is sort of keep investing in lots of platforms, right? So platforms are great on their surface but once you're having to manage five and six and, you know 10 or however many you're managing, the economies of scale go away. And so what's been really interesting to watch with Kubernetes is, you know when we first got started everything was Cloud native application but that really was sort of, you know shorthand for stateless applications. We quickly saw a move to, you know, people that said, "Hey I can modernize something, you know, a Stateful application and we add that into Kubernetes, right? The community added the ability to do Stateful applications and that got people a certain amount of the way. And they sort of started saying, okay maybe Kubernetes can help me peel off some things of an existing platform. So I can peel off, you know Java workloads or I can peel off, what's been this explosion is the data community, if you will. So, you know, the TensorFlows the PItorches, you know, the Apache community with things like Couchbase and Kafka, TensorFlow, all these things that, you know maybe in the past didn't necessarily, had their own sort of underlying system are now defaulting to Kubernetes. And what we see because of that is, you know people now can say, okay, these data workloads these AI and ML workloads are so important to my business, right? Like I can directly point to cost savings. I can point to, you know, driving innovation and because Kubernetes is now their default sort of way of running, you know we're seeing just sort of what used to be, you know small islands of clusters become these enormous footprints whether they're in the cloud or in their data center. And that's almost become, you know, the most prevalent most widely used use case. And again, it makes total sense. It's exactly the trends that we've seen in our industry, even before Kubernetes. And now people are saying, okay, I can consolidate a lot of stuff on Kubernetes. I can get away from all those silos. So, you know, that's been a huge thing over the last probably year plus. And the cool thing is we've also seen, you know the hardware vendors. So whether it's Intel or Nvidia, especially around GPUs, really getting on board and trying to make that simpler. So it's not just the software ecosystem. It's also the hardware ecosystem, really getting on board. >> Awesome, Brian let me get your thoughts on the cloud versus the power dynamics between the cloud players and the open source software vendors. So what's the Red Hat relationship with the cloud players with the hybrid architecture, 'cause you want to set up the modern day developer environment, we get that right. And it's hybrid, what's the relationship with the cloud players? >> You know, I think so we we've always had two philosophies that haven't really changed. One is, we believe in open source and open licensing. So you haven't seen us look at the cloud as, a competitive threat, right? We didn't want to make our business, and the way we compete in business, you know change our philosophy in software. So we've always sort of maintained open licenses permissive licenses, but the second piece is you know, we've looked at the cloud providers as very much partners. And mostly because our customers look at them as partners. So, you know, if Delta Airlines or Deutsche Bank or somebody says, "hey that cloud provider is going to be our partner and we want you to be part of that journey, we need to be partners with that cloud as well." And you've seen that sort of manifest itself in terms of, you know, we haven't gone and set up new SaaS offerings that are Red Hat offerings. We've actually taken a different approach than a lot of the open source companies. And we've said we're going to embed our capabilities, especially, you know OpenShift into AWS, into Azure into IBM cloud working with Google cloud. So we'd look at them very much as a partner. I think it aligns to how Red Hat's done things in the past. And you know, we think, you know even though it maybe easy to sort of see a way of monetizing things you know, changing licensing, we've always found that, you've got to allow the ecosystem to compete. You've got to allow customers to go where they want to go. And we try and be there in the most consumable way possible. So that's worked out really well for us. >> So I got to bring up the end user participation component. That's a big theme here at KubeCon going into it and around the event is, and we've seen this trend happen. I mean, Envoy, Lyft the laying examples are out there. But they're more end-use enterprises coming in. So the enterprise class I call classic enterprise end user participation is at an all time high in opensource. You guys have the biggest portfolio of enterprises in the business. What's the trend that you're seeing because it used to be limited to the hyperscalers the Lyfts and the Facebooks and the big guys. Now you have, you know enterprises coming in the business model is working, can you just share your thoughts on CloudNativeCons participation for end users? >> Yeah, I think we're definitely seeing a blurring of lines between what used to be the Silicon Valley companies were the ones that would create innovation. So like you mentioned Lyft, or, you know LinkedIn doing Kafka or Twitter doing you know, whatever. But as we've seen more and more especially enterprises look at themselves as software companies right. So, you know if you talk about, you know, Ford or Volkswagen they think of themselves as a software company, almost more than they think about themselves as a car company, right. They're a sort of mobile transportation company you know, something like that. And so they look at themselves as I've got to I've got to have software as an expertise. I've got to compete for the best talent, no matter where that talent is, right? So it doesn't have to be in Detroit or in Germany or wherever I can go get that anywhere. And I think what they really, they look for us to do is you know, they've got great technology chops but they don't always understand kind of the the nuances and the dynamics of open-source right. They're used to having their own proprietary internal stuff. And so a lot of times they'll come to us, not you know, "Hey how do we work with the project?" But you know like here's new technology. But they'll come to us and they'll say "how do we be good, good stewards in this community? How do we make sure that we can set up our own internal open source office and have that group, work with communities?" And so the dynamics have really changed. I think a lot of them have, you know they've looked at Silicon Valley for years and now they're modeling it, but it's, you know, for us it's great because now we're talking the same language, you know we're able to share sort of experiences we're able to share best practices. So it is really, really interesting in terms of, you know, how far that whole sort of software is eating the world thing is materialized in sort of every industry. >> Yeah and it's the workloads of expanding Cloud native everywhere edge is blowing up big time. Brian, final question for you before we break. >> You bet. >> Thanks for coming on and always great to chat with you. It's always riffing and getting the data out too. What's your expectation for KubeCon CloudNativeCon this year? What are you expecting to see? What highlights do you expect will come out of CloudNativeCon KubeCon this year? >> Yeah, I think, you know like I said, I think it's going to be much more on the Cloud native side, you know we're seeing a ton of new communities come out. I think that's going to be the big headline is the number of new communities that are, you know have sort of built up a following. So whether it's Crossplane or whether it's, you know get-ops or whether it's, you know expanding around the work that's going on in operators we're going to see a whole bunch of projects around, you know, developer sort of frameworks and developer experience and so forth. So I think the big thing we're going to see is sort of this next stage of, you know a thousand flowers are blooming and we're going to see probably a half dozen or so new communities come out of this one really strong and you know the trends around those are going to accelerate. So I think that'll probably be the biggest takeaway. And then I think just the fact that the community is going to come out stronger after the pandemic than maybe it did before, because we're learning you know, new ways to work remotely, and that, that brings in a ton of new companies and contributors. So I think those two big things will be the headlines. And, you know, the state of the community is strong as they, as they like to say >> Yeah, love the ecosystem, I think the values are going to be network effect, ecosystems, integration standards evolving very quickly out in the open. Great to see Brian Gracely Senior Director Product Strategy at Red Hat for the cloud business unit, also podcasts are over a million episode downloads for the cloud cast podcast, thecloudcast.net. What's it Brian, what's the stats now. >> Yeah, I think we've, we've done over 500 shows. We're you know, about a million and a half listeners a year. So it's, you know again, it's great to have community followings and, you know, and meet people from around the world. So, you know, so many of these things intersect it's a real pleasure to work with everybody >> You're going to create a culture, well done. We're all been there, done that great job. >> Thank you >> Check out the cloud cast, of course, Red Hat's got the great OpenShift mojo going on into KubeCon. Brian, thanks for coming on. >> Thanks John. >> Okay so CUBE coverage of KubeCon, CloudNativeCon Europe 2021 Virtual, I'm John Furrier with theCUBE virtual. Thanks for watching. (upbeat music)

from the silicon angle media office in Boston Massachusetts it's the queue now here's your host David on tape hello everyone and welcome to this special presentation we're gonna introduce you to a new kind of company first you might recall we've been reporting extensively on multi cloud and the need to create consistent experiences across cloud at high performance now a key to that outcome is the ability to leave data in place where it belongs not moving it around and bringing a cloud like experience to that data we've talked about kubernetes as a multi cloud enabler but it's an insufficient condition for success latency matters in fact it's critical and the ability to access data at high speeds wherever that data lives well we believe be a fundamental tenet of multi cloud now today I want to introduce you to a company called vicinity V CIN ity the simplest way to think of this company is they turn wide area networks into a global land and with me is Craig Hobart to talk about this he's the VP at vicinity Craig good to see you again thanks a lot thanks Howie middays good to be back so when I first heard about this company I said wow no it can't that breaking the law of physics so first of all tell me a little bit background about the company sure yeah absolutely so about two decades ago this company was formerly known as Bay Microsystems they were they were asked to come up with a solution specific for the United States military and there was a couple of people involved in that that tender fortunately for us Bay Microsystems prevailed and they've had their solution in place with the US military for well over a decade approach in two decades so that is the foundation that is the infrastructure of where we originated so did I get it right it kind of come through what you do can you add some color to that yeah yeah as much as I can right so based on who the the main consumer is so we do some very creative things where we we take the benefits of tcp/ip which is the retransmit the ability to ensure the data arrives there in one piece but we take away all the bad things with it things like dropping packets typically ones are lossy networks and and most people are accustomed to two fiber channel networks which of course which are lossless right and so what we've done is take the beauty of tcp/ip but remove the hindrances to it and that's how we get it to function at the same speeds as Al and overall one so but there's got to be more to it than that I mean it just sounds like magic right so you're able to leave data in place and access it at very low latency very high speeds so you know what's the secret sauce behind that is it is it you know architecture patents I mean yeah absolutely so we have over 30 unique patents that contribute to that we're not just doing those things that I just thought about before is a lot more we're actually shortly in the typical OSI stack the the moving through those layers and using our DMA so a lot of companies users today obviously infinite out uses in between the nodes Dell uses at HP is it's a very ubiquitous technology but typically it has a very short span it's designed for low latency as a 21-foot limitation there's certain things you can do to get around that now so what we did in our earlier iterations is extend that so you could go across the world but utilizing that inside a proprietary sort of l2 a tunneling protocol allows you to reinstate those calls that happened on the local side and bring them up on the other side of the world so presumably that sets up for Rocky it does yeah and rocky to you absolutely so we use that we use it converged Ethernet we can do some magical things where we can go in InfiniBand and potentially come out rocky at the other end there's a lot of really good things that we do obviously if it uh bans expensive converged Ethernet it's a lot more feasible and a lot easier to adapt when we can make sure I understand this so you think InfiniBand you're thinking you know in a data center you know proximate and shocking synchronous distances are you saying that you can extend that we can but extended not extending finna band but you're saying you can you translate it into Ethernet yeah yeah we we translate into we have some proprietary mechanisms obviously that that all the patents on but in essence that's exactly what we're doing yeah we take in the earlier years InfiniBand and extend that to wherever it needed to be over any distance and and now we do it with conversion and infinite in like speeds yeah yeah so obviously you've got that we can't get around physics oh I mean it for instance between our Maryland office and our San Jose office it's a 60 millisecond r/t team we can't get beyond that we can't achieve physics but what we can do is deliver us sometimes a 20x payload inside that same RTT so in essence you could argue that would be due to the speed of light by delivering a higher payload is what's the trade-off I mean there's got to be something here yeah so it's today it's not it's not ideal for every single situation if you were to do a transactional LTP a database at one side of the world to the other it would that would not be great for that something files yeah so so what we actually do I mean some some great examples we have is seismic data we have some companies that are doing seismic exploration and it used to take a lot of time to bring that data back to shore copied to a disk array and then you know copied to multiple disk arrays across the world so people can analyze it in that particularly use case we bring that data back we can even access it via satellite directly from the boats that are doing the the surveys and then we can have multiple people around the world looking at that sample live when we do a demonstration for our customers that shows that so that's one great example of time to market and getting ahead of your competition what's the file system underneath so we have a choice of different file system is a parallel file system we chose spectrum Connect it's a very ubiquitous file system it's well known it has there is no other file system that has the the hours of runtime that that has we off you skate the complexities from the customers we do all of the tuning so it's a custom solution and so they don't see it but we do have some of the hyper scales that want to use lustre and cluster and be GFS and things that we can accommodate those so you have a choice but the preferred is gpfs is a custom one we have you absolutely if somebody wants to use another one we have done that and can certainly have dialogues around it could talk about how this is different from competitors I think of like guys like doing Wayne acceleration sure sure yeah so what acceleration regardless of who you are today with it's predicated upon caching substantial caching and some of the problems with that are obviously once you turn on encryption that compression and those deduplication or data reduction technologies are hampered in that caching based on who our primary customer was we're handed encrypted data from them we encrypted as well so we have double layers of encrypted data and that does not affect our performance so massive underlying technological differences that allow you to adapt to the modern world with encrypted data so we've been talking about I said in the intro a lot about multi cloud can you tell us sooner where do you fit in but first of all how do you see that evolving sure and where do you guys fit in Joe so I actually read to assess very certain dividends I read your article before we had a dialogue last week and there was a good article talking about the complexities around multi cloud and I think you know you look at Google it's got some refactoring involved in it they're all great approaches we think the best way to deal with multi cloud today is to hold your data yourself and bring those services that you want to it and before we came along you couldn't do that so think now a movie studio we have a company in California that needs people working on video editing across the world and typically they would proliferate multiple copies out to storage in India and China and Australia and not only is that costly but it's incredibly time consuming and in one of those instances it opens up security holes and the movies were getting hacked and stolen and of course that's billions of dollars worth of damage to to any movie company so by having one set of security tenants in your in your physical place you can now bring anybody you want to consume that day to bring them all together bid GCP AWS as you for the compute and you maintain your data and that segues well into things like gdpr and things like that where the data isn't moving so you're not affected by those rules and regulations the data stays in one place it's we think it's a huge advantage so has that helped you get some business I mean the fact that you have to move data and you can keep it in you can give us an example yeah it absolutely doesn't mean if you think of companies like pharmaceutical companies that have a lot of data to process whether it's electron microscopy data nano tissue samples they need heavy iron to do that we're talking craze so we can facilitate the ability to rent out supercomputers and the security company of the farmers is happy to do that because it's not leaving the four walls present the data and run it live because we're getting land speeds right we're giving you land speed performance over the wine so it's it's possible we've actually done it for them to do that craze make money by renting the farmers are happy because they can't afford craze it's a great way to accelerate time to marketing in that case they're making drug specific for your genome specific for your body tissue so the efficacy of the drugs is greatly improved as well well as you have been we know the storage business primary storage right now is I've said it's a knife fight yeah and it's a cloud is eating away at it flash was injected and gave people a lot of head rooms and they're not buying spindles for performance anymore but but data protection and backup and and data management is really taking off do you guys fit in there is are there use cases for you you there when you think of companies like cookie City and rubric and and many others that are the cloud seems to be a tailwind for them is it a tailwind for you I think so and I think he just brought up a great point if you look at and again another one of your articles I'm giving you some thanks Rick you know saying I won't forget it is the article you wrote I thought was excellent about how data is changed it's not so much about the primary data now it's about the backup data and what rubric and cohesive tea especially have done is bring value to that data and they've elevated it up the stack for analytics and AI and made available to DevOps and that's brilliant but today that can find it too within the four walls of that company what vicinity can do for those companies has come along and make that data available anywhere in the world at anytime so if they've got different countries that they're trying to sell into that may have diff back up types or different data they can access this and model the data and see how it's relevant to their specific industry right as we say our zeros and ones are different than your zeros and ones so it's a massive expansion it take that richness that they've created and extrapolate that globally and that's what facility brings to the table you know within the days of big data we used to look at high performance computing as an example going more into commercial notes that's clearly happened but mainstream is still VMware is there a VMware play for you guys or opportunity great question great question in q1 of this year so so January end of January 2020 typically in the intro we talked about how we were born on a6 which is incredibly expensive and limited you get one go ahead and then we move to FPGAs we actually wrote a lot of libraries that took the FPGAs into a VMware instance and so what we're doing now with our customers is when we go in and present they say there's no way you can do this and we show them the demo when we actually leave they can log-in download to VMware instances put one in in these case one the west coast or with one of my customers we have now one on the east coast one in London download the VM and see the improvement that we can get over their dedicated lines or even the Internet by using the VM fact we did that in a test with AWS last week and got a 90 percent improvement just using the VM so when you are talking to customers what's the you know what's the the situation that you're looking for the the problem that comes up that you say bone that's vicinity maybe you could show not you do slash call in there so I think a lot of that is people looking to use multi cloud right that aren't sure which way they want to go how they want to do it and for other companies that can't move the data there's a lot of companies that either went to the cloud and came back or cannot go to the cloud because of the sensitivity of the data so and also things like the the seismic exploration right there is no cloud solution that makes that expedient enough to consume it as it's been developed and so anybody that needs movie editing large file transfer dr you know if you're moving a lot of files from one location to another we can't get involved in storage replication but if it's a file share we can do that and one of the great things we do is if you have cysts or NFS shares today we can consume those shares with the with the spectrum scale the gpfs under the cover and make that appear anywhere else in the world and we do that through our proprietary technology of course so now remote offices can collapse a lot of the infrastructure they have and consume the resources from the main data center because we can reach right back here at land space they just become an extension of the land no different than me plug in the laptop into an Ethernet you pay a penalty on first byte we do but it's almost transparent because of the way tcp/ip works very chatty yeah it is so we drop all that and that that's a great question an analogy we use in house is you turn on a garden house and it takes a few seconds for that garden hose to fill but with us that water stream is constant and it's constantly output in water with tcp/ip a bit stop start stop start stop start and if you have to start doing retransmit which is a regular occurrence of tcp/ip and that entire capacity of that garden hose will be dropped and then refilled and this is where our advantage is the ability to keep that full and keep serving data in that what you just described makes people really think twice about multi clouds essentially they want to put the right workload in the right place and kind of leave it there and essentially it's like the old mini computer days they're creating you know silos you're helping sort of bridge those we are that and that is the plot and so you know we have B to B we are B to C I mean if you sit and think about the possibilities I mean it could end up on every one of these right this software you know do we tackle every Wireless point this is this is some of the things that we can do you're an app or do we put vicinity on that to take the the regular tcp/ip and send the communication you know through through our proprietary Network around proprietary configuration so there's a lot of things that we can do we can we can affect everybody and that is that is the goal so divide by hardware from you or software or both that's another great question so if you are in a data center in the analogy I just gave before about being a a big data center you would use a piece of hardware that's got accelerants in it and then the remote office could use a smaller piece of hardware or just the VM with the movie company example I gave you earlier India and Australia is edit in live files on the west coast of the United States of America just using the VM so it depends what we come in as we look at your needs and we don't oversell you we try and sell you the correct solution and that typically is a combination of some hardware in the main data center and some software at the others so I've said you know multi-cloud in many ways creates more problems today than it solves you guys are really in there attacking that multi-cloud is a reality it's it's happening you know I said historically it's been a symptom of multi-vendor but now it's becoming increasingly a strategy and I think frankly I think companies like yours are critical in the ecosystem to really you know drive that transformation for organizations so congratulations thank you thank you we hope so and I'm sure we'll be seeing more of you in the future excellent well thanks for coming in Craig and we'll talk to you soon thank you for watching everybody this is Dave latte for the cube and we'll see you next time

ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 alright so we've got a fantastic event today really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event this is not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a take-off of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any powerpoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got Simone Rashard Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the u.s. it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Frank kibrit you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission critical they care about visibility they care about control they care about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers did they see the same thing we're gonna validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is architecture again with IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're gonna talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day 2 operations what does that mean well day 1 is one day of your life that's who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do I operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix we as leaders do we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CCI ease where Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when to try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of tube Jon Fourier okay awesome great great speech they're awesome I'd totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix were we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel two customer panels before that Gartner is going to come on talk about the industry we have a global system integrators we talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask someone rashard to come on stage from Gartner check it all up [Applause] okay so kicking things off sitting started gartner the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer in a 92 a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering at the marketplace with hybrid cloud and now moving quickly to multi cloud is really was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow I to your application people are some kind of DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right with different account and they create mesh to manage them and their direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides that the audinate that are sent removing that to that cloud and I ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the ad hoc way doesn't scale at some point idea has to save them because they don't think about the two they don't think about operations they have a bunch of VPC and multiple clouds the other way that if you do the left and shift wake they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these ways are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct then that's what I call the optimal phase but even that they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS has accounts there's subscription and in adarand GCP their projects it's a real mess so they realize well I can't really like concentrate use the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that I still wanna manage the cloud from an API to interview I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they really building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway I'm just a joke what do you see in terms of where people are in that multi-cloud so a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in deserve one app in individuals one get happen Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never going to happen what I've seen with enterprise is I'm gonna put the workload in the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking team be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while their network part of the cloud connectivity to the cloud is kind of simple I agree IPSec VP and I reckon Express that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which free cloud providers right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean this is the day-to-day operations after you know the natural let's add an app let's add a server let's troubleshoot a problem so so your life something changes how would he do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's been a hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi cloud wave that's coming as cloud native networking well there's no you know official garner definition but I can create one on and if another spot is do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't even understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose api's where is that optimization where's the focus well I take what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of the cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of you right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plane out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that plane out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and ship or they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco monks bring you star and the cloud recall that each guy anywhere right so everyone what and and then there's cloud vision for my red star and contrail is in the cloud so they just want to bring the management plane in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not truly cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive clown that so close one letter yeah so that was a big con surgeon reinvent take the tea out of cloud native it's cloud naive that went super viral you guys got t-shirts now I know you love but yeah but that really ultimately is kind of double edged sword you got to be you can be naive on the on the architecture side and rolling out but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in Cisco you it's a little bit more native than other ones because they're really scr in the cloud you can't you you really like configure API so the cloud and NSX is going that way and so is Arista but they're incumbent they have their own tools is difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know a network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like al kira for example that just started now that doing more connectivity but they wanna create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week oh the only b2 networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like aviation others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in AWS you can user it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck Nets a cops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you this programmability their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get every line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this VP see but this VP see automatically being associate to your account you cannot go out on the internet you have to go to the transit VP see so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI mace which for us old folks know what that means but you guys know what this means I want to ask you the question as you look at the future of networking here a couple of objectives oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well as I said earlier that once you you could easily provision in the cloud you can easily connect to that cloud is when you start troubleshooting application in the cloud and try to scale so this that's where the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead to 20% extra functionality that of course every Enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that Cambrian explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always gonna be that extra functionality the in in an automated and simple way that you talked about but yet powerful with up with the visible in control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggers who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some the signals that are going on in their environment what are some of the thresholds or things that are going on that there can pay attention to well well once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robber will hit the road but as I said it's easier to prove it it's ok it's 80s it's easy use a transit gateway put a few V PCs and you're done and use create some presents like equinox and do Direct Connect and Express route with Azure that looks simple is the operations that's when they'll realize ok now I need to understand our car networking works I also need a tool that give me visibility and control not button tell me that I need to understand the basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi Bob because you think about what's happening it kind of has that same vibe of interoperability choice multi-vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client server and internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this more because honestly public cloud check hybrid cloud they're working on that that gets on-premise is done now multi clouds right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what there's cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start with especially an incumbent one so it's tempting to say on and I have a bunch of f5 experts nothing against that five I'm going to bring my five in the cloud when you can use a needle be that automatically understand Easy's and auto scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that met I'm going to use legacy stuff and then you have to start thinking okay what about visibility control about the tree cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming someone in charge with Gardner thanks for sharing informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in the business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of that data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement with aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for her aviatrix already working in Amazon and now works in Missouri as well before we knew what GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake assure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at 3 o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build or done in hours I think the most important thing about a matrix is it provides me a Beatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments David should Nick with fact set guys welcome to the stage for this digital event come on up [Applause] [Music] hey good to see you thank you okay okay customer panelist is my favorite part we get to hear the real scoop gets a gardener given this the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with a live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and is soon gonna be a lot more coming so we want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets and different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting which what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation 'el opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on bram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we're we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources from Azure like HPC you know as your ad things like that even recently Google Google Analytics our journey has evolved into more of a multi cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you you know had some comments about architecture matters it all starts I mean every Enterprise I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a fun architecture perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network marketer and we call it networking security net SEC yeah versus Justice Network yeah and that fourth generation architectures be based primarily upon Palo Alto Networks an aviatrix I have Atrix doing the orchestration piece of it but that journey came because of the need for simplicity ok the need for a multi cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around how we provision networks but cloud formation has become a little bit like the new manual for us so we we're now having issues with having the to automate that component and making it consistent with our on premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that SEO and brought to the to the web side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was some of the that's probably the biggest list and there is that when you think you finally figured it out you have it right Amazon will change something as you or change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective we like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's that I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those that we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gate without a trans a gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and in evolve later and maybe optimize or change the way you're doing things in the future but don't sit around and wait you can't I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model how do I do my day one work so that I'm not you know spending 80 percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice the architect I don't know what else I can do that simplicity operations is key right all right so the holistic view of j2 operation you mentioned let's can jump in day one is your your your getting stuff set up day two is your life after all right this is kind of what you're getting at David so what does that look like what are you envisioning as you look at that 20 mile stare at post multi-cloud world what are some of the things that you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router seoi and troubleshooting things on in an ad hoc nature so moving more towards the DevOps model yes anything on that day - yeah I would love to add something so in terms of day 2 operations you can you can either sort of ignore the day 2 operations for a little while where you get well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to realize it's it's such as such a big gap I think that's key because for us we're moving to more of an event-driven operations in the past monitoring got the job done it's impossible to modern monitor something there's nothing there when the event happens all right so the event-driven application and then detection is important yeah I think Gardiner was all about the cloud native wave coming into networking that's going to be here thing I want to get your guys perspectives I know you have different views of how you came on into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies the network's laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have a requirement to encrypt and they never get the question should I encryption or not encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely expense in some cases so we have been mandated that we have to encrypt everything leave from the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you've got a lot of complexity in your network what do you guys look at the future for yours environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance of things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secured in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting and get a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's okay we want to hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like encryption and things like so you're encrypting tunnels and crypting the path and those things are it should it should should be second nature really when you when you look at building those back ends and managing them with your team it becomes really painful so tools like a Beatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I'll see aviatrix is here they're their supplier to this sector but you guys are customers everyone's pitching you stuff people are not going to buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's that what's it like we're API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like it's definitely it's definitely API driven we we definitely look at the at the PAP i structure of the vendors provide before we select anything that that is always first in mind and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking and more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what do what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on site and they're gonna sit with you for your day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so I you know having having some ease-of-use and the team being comfortable with it and understanding it is really important Bobby how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore but what's the Volvic a bake-off last year for us do you win so but that's different now because now when you when you get the product you can install the product and they double your energy or have it in a matter of minutes and so the key is is they can you be operational you know within hours or days instead of weeks but but do we also have the flexibility to customize it to meet your needs could you want to be you want to be put into a box with the other customers when you have needs that your pastor cut their needs yeah almost see the challenge that you guys are living where you've got the cloud immediate value depending how you can roll up any solutions but then you have might have other needs so you got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and experimenting with the different concepts of cloud and and really leveraging the the native constructs of each cloud but but there's a there's a breaking point for sure you don't you don't get to scale this like Alexa mom said and you have to focus on being able to deliver a developer they're their sandbox or they're their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so use a lot more stuff to be coming pretty quickly hides area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms-up organization Nick pops you're kind of like off a little bit it's not how it works I mean what is the reality in terms of implementing you know in as fast as possible because the business benefits are but it's not always clear in the technology how to move that fast yeah what are some of the barriers one of the blockers what are the enablers I think the reality is is that you may not think you're multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements and then secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go yeah scale is a big part of what I see is the competitive advantage to a lot these clouds and needs to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the upfront from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business need and and like like you said it's whether whether you're in denial or not of the multi cloud fact that then your company is in already that's it becomes really important for you to move quickly yeah and I a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or Azure and just helping facilitate things they're doing the you know the heavy lifting API work for you or are they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know makes you have designed yourself into a corner so the closer they're more than cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will it make sense tgw is a game changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool give you the beauty of both worlds you can use tgw with a gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go Mull one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint do you agree with that premise and then witness multi-cloud stitch them all together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction that value but the the network problem is still the same doesn't go away yeah yeah yeah I mean you don't want to be trying to fit a square into a round Hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the network infrastructure is there secure is available and is multi cloud capable yeah I'm at the end of the day you guys just validating that it's the networking game now cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate it thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John fritz T Blaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Koopa welcome to stage [Applause] all right thank you thank you okay he's got all the the cliff notes from the last session welcome back rinse and repeat yeah yeah we're going to go under the hood a little bit I think I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move a pack from A to B and you get workloads exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds and that's like I mean almost sounds impossible to me what's your take yeah I mean it it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to iterate and make improvements over the time we get to Justin's over here so I have to be careful when I point a question in Justin they both have the answer but okay journeys what's the journey been like I mean is there phases we heard that from Gartner people come in to multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from our perspective we started out very much focused on one cloud and as we started doing errands we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tore in the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are available and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really that's the enabler for this multi cloud trend but you guys taken we'll start with Amit what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it matter of how you are going to build your networks how we are gonna run security how we are going to do egress ingress out of it so it's a big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditionally on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make a sense of all of that and I think that's where tools like a v8 ryx make a lot of sense in that space from our site it's it's really simple its latency its bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea our job is to enable them not to disable them do you think you guys think infrastructure is code which I love that I think it's that's the future it is we saw that with DevOps but I do start getting the networking is it getting down to the network portion where it's network is code because storage and compute working really well is seeing all kubernetes and service master and network as code reality is it there is got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same unit yeah and even security groups and then on top an aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us was similar on-premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored Confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now I want to pick up on what you said to you others agree that the center of architect of gravity is here I'm now pushing what I do in the cloud back into on pram and and then so first that and then also in the journey where are you at from 0 to 100 of actually in the journey to cloud DUI you 50% there are you 10% yes I mean are you evacuating data centers next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together right in our case the data gravity sold mostly on Prem but our network is now extending out to the app tier that's going to be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of you know lift and shift and when did that start and we started about three years ago okay okay go by it's a very different story it started from a garage and one hundred percent on the clock it's a business spend management platform as a software-as-a-service one hundred percent on the cloud it was like ten years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask user you guys mentioned DevOps I mean obviously we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this isn't about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interesting we we have moved from having a backbone that we bought that we own that would be data center connectivity we now I work for as or as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth I think availability with your sim pop3 things guys SLA I mean you just do ping times between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workload I mean SL leis will be all over the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and what our ability is hour is there and our authority needs to operate on that so it's solely use the software dashboard look at the times and look at the latency in the old days strong so on open so on you try to figure it out and then your day is you have to figure out just and what's your answer to that because you're in the middle of it yeah I mean I think the the key thing there is that we have to plan for that failure we have to plan for that latency and our applications it's starting start tracking in your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment or was it was it from day one now there are two divisions one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so it has a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot network load or you are going to run machine learning or AI so that you have you would have that preference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting is how do I solve or guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just on your thoughts on that I think any comment on that so actually multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as those are acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are haiku people using them but Google's got a great Network Google's networks pretty damn good and then you got a sure what's the difference between the clouds who where they've evolved something whether they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes Azure better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is the approach is different in many places Google has a different approach very devops friendly and you can run your workload like your network can spend regions time I mean but our application ready to accept that MS one is evolving I mean I remember ten years back Amazon's network was a flat network we will be launching servers and 10.0.0.0 mode multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the I mean I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of that in mine is your architectural and solution for example Amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has advantages there to market and so it has seen what asier did wrong it's seen what AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the the inability or the ability for Amazon to limit layer 2 broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional Network facilities to us it's just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive question so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like when is the new land so if you think about what the land was at a data center when is the new link you get talking about the cloud impact so that means st when the old st was kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high speed but now when you take the win and make essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah I think it's the it's a thing that you have to work with your application architect so if you are managing networks and if you're a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the Layton sees and and the reliability has to be worked through the application there land when same concept as it be yesterday I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native when we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way than it was in a land that's what we're seeing so much infrastructure as code yeah yeah so for me I'll go back again to this its bandwidth and its latency right that bet define those two land versus win but the other thing that's comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it so for us we're able to deliver VRS or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning that's architecture thoughts on security are you guys are dealing with it yeah start from the base have app to have security built in have TLS have encryption on the data I transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principals day Security's day zero every day and so we we always build it into our design we load entire architecture into our applications it's encrypt everything it's TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff was interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now he being sure he's gonna got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to you know supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us its main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive and think that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for twenty years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we have we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's are you being closed-minded native being open-minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total B yes what what triggers use it so that I have two lines out of movies that are really I can if the if I say them without actually thinking them it's like 1.21 jigowatts how you're out of your mind from Back to the Future right somebody's gonna be a bank and then and then Martin ball and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speeds would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and okay 220 221 anytime I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need to benchmark yourself don't don't listen to the marketing on that that's that's all I'm a what triggers you and the bsp I think if somebody explains you a not simple they cannot explain you in simplicity then that's a good one all right guys thanks for the great insight great panel how about a round of applause practitioners DX easy solutions integrating company than we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba corkle will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs its when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products that incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the lance cloud connectivity there's a new line of networking services that we're getting into as our clients move into hybrid cloud networking it is much different than our traditional based services an aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a v8 church we were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed for work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole in their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basic law providing services we're taking our customers on a journey to simplify and optimize their IT infrastructure aviatrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John Ford with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native networking we heard from the customer panel you can see the diversity of where people come into the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk journey to multi cloud what do you guys seeing yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are exactly you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we were having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying we're starting to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the apps and then we evolved into that next journey which is a foundational approach to what are some of the problem statement customers are solving when they come to you what are the top things that are on their my house or the ease of use of jelly all that stuff but what specifically they did digging into yeah some complexity I think when you look at multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do and this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard part is now upon us are you referring to networking what is specifically were you getting at Tara so the easy parts done now so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises that are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the >> so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it okay in our internal environment as yeah you know we're a huge company or right customer zero or an IT so we're experiencing that internal okay and every one of our other customers so I have another question oh I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway d XE @ wwt massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that it worldwide technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking but simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the at the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I what I get excited about is not just putting yours in our lab and showing customers how it works it's Co developing a solution with you figuring out hey how can we make this better right mr. piller is a huge thing Jenna insecurity alone Network everything's around visibility what automation do you see happening in terms of progression order of operations if you will it's the low-hanging fruit what are people working on now and what are what are some of the aspirational goals around when you start thinking about multi cloud and automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were going to integrate those solutions you know we like to build everything with recipes where Network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of a VHS let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference architectures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi cloud in terms of you know customers want choice didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and be risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud applications a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an Billy approaches how do things interoperate we test it out we validate it we build a reference architecture it says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it invisibility so I think the visibility is what's what I see lacking across the industry today and the cloud needed that's been a big topic yep okay in terms of aviatrix that you guys see them coming in there one of the ones that are emerging and the new brands emerging with multi cloud you still got the old guard incumbents with huge footprints how our customers dealing with that that kind of component in dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question while we were defining de to operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does de two operations mean what's the definition of that yeah so I think from our perspective my experience we you know de to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve that the the cloud is very dynamic the the nature of how that fast is expanding the number of features is astonishing trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is that what's what happens there they call you up and say hey I need multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's looks like typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we got a factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what does VPC sharing you know what is a private link and Azure how does that impact your business you know customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts George oh yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah when I then is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs it so the patterns are similar great final question for you guys I want to ask you to paint a picture of what success looks like and you know for name customers you don't forget in reveal of kind of who they are but what does success look like in multi-cloud as you as you paint a picture for the folks here and watching on the live stream it's if someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in that is you build that network foundation an architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi-cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off Prem and so collectively I think the key is also is that we provide them an hld you got to start with in a high-level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed had a success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen what what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators [Applause] [Music] okay welcome back from the live feed I'm shuffle with the cube Steve Eleni CEO of aviatrix my co-host our next panel is the aviatrix certified engineers also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foster min from Attica Stacy linear from Terra data and Jennifer Reid with Victor Davis to the stage I was just gonna I was just gonna rip you guys and say where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear there above the clouds soaring to new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like a squadron leader Roger and leader yeah squadron leader so he's got a bunch of aces underneath him but share your perspective day-in-the-life Jeff we'll start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm eagerly working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but networking in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hmm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the V PCs and on the instant side is a security group or is it going on print and this is something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this such for 25 years but I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software and they work takes care of itself yes I'll be will get I'll come back to that I want to come back to that that problem solved with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in network have always been the network's fault and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you got a full stack DevOps you gotta know a lot more times another hundred and these times are changing yeah they say you're a squadron leader I get that right what is what does a squadron leader first can you describe what it is I think probably just leading all the network components of it but not they from my perspective when to think about what you asked them was it's about no issues and no escalation soft my day is a good that's a good day yes it's a good day Jennifer you mentioned the Amazon thing this brings up a good point you know when you have these new waves come in you have a lot of new things newly use cases a lot of the finger-pointing it's that guy's problem that girl's problem so what is how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in well is where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Stephen the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear but what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are full logs well as long as we turned on the flow logs when they built it you know and there's like each one of those little things that well if they had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before we came on up on stage about your career you've been networking all your time and then you know you're now entering a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about you know that's dimmer fault I walk in bare feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young P so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way or you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and old guys that's where we thrive Jennifer you mentioned you you got in from the Marines health spa when you got into networking how what was it like then and compared it now almost like we heard earlier static versus dynamic don't be static cuz then you just set the network you got a perimeter yeah no there was no such thing ya know so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it now I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network crimped five cat5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that it became Victor Davis but we went to help one of our customers Davis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this were the program abilities it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how a double u.s. senator and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable cuz we heard the global si help the business issues what does it mean to do that is it code is that networking is it configuration is that aviatrix what is the I mean op C aviatrix is the ASA certification but what is it about the multi cloud that makes it multi networking and multi vendor easy answer is yes so you got to be a generalist getting your hands and all you have to be right it takes experience because it's every every cloud vendor has their own certification whether that's hops and advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not gonna solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through with those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe months ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed good is that watching leader would put there yeah is that something that you see in your organization's are you recommending that to people do you see I mean I'm just I guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I say from my side because we operate in the multi cloud environment so it really helps and it's beneficial for us yeah I think I would add that uh networking guys have always needed to use certifications to prove that they know what they know right it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters buying helps give you validity um so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics and enough of the understandings that you have the tools necessary right so I guess my final question for you guys is why an eighth certification is relevant and then second part is share what the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why shouldn't someone want to be an ace-certified I'm uses the right engineer I think my views a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get no I mean they're backwards so when you've got the training and the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding of ok so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network definitions eating eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that's just the next progression there I would say I expand that to more automation engineers because we have those now probably extended as well well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but I've never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes them better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who have tradition down on Prem networking they can understand how that's going to work in the cloud - well I know we've got just under 30 seconds left I want to get one more question than just one more for the folks watching that are maybe younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacey we'll start with you we'll go down I'd say it's probably fundamental right if you don't deliver solutions networking use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you you've come from top down now you're gonna start looking from bottom up and you want those different systems to cross communicate and say you built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the how the pipes are working and because know what's going some plumbing that's right and the works a how to code it that's right awesome thank you guys for great insights ace certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John Currier yeah so great event great event I'm not going to take long we've got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the Aces you know for those of you out on the stream here become a certified right it's great for your career it's great for knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the Cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community bh6 comm starting a community at multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as to start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more importantly where they're going in that in-state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we saw we help you cook define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their twenty-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music]

ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 all right so we've got a fantastic event today really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a take-off of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any powerpoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got Simone Rashard Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the u.s. it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Frank kibrit you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission critical they care about visibility they care about control they care about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers do they see the same thing we're gonna validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're gonna talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day 2 operations what does that mean well day 1 is one day of your life that's who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do I operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix as leaders knew we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CC IES where Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of Tube John Fourier okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel two customer panels before that Gartner is going to come on talk about the industry we have a global system integrators we talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask someone rashard to come on stage from Gartner we'll check it all up [Applause] [Music] okay so kicking things off certain started gartner the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer in the 90 to a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering at the marketplace with hybrid cloud and now moving quickly to multi cloud is really I was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow whitey or application people or some kind of DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right with a different account and they create mesh to manage them and their direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides the data that are sent removing that to that cloud and I ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the adduct way doesn't scale at some point idea has to save them because they don't think about the two they don't think about operations they have a bunch of VPC and multiple clouds the other way that if you do the left and shift wake they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these ways are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct then that's I would I call the up optimal phase but even that they they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS has accounts there's subscription and in adarand GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that I still wanna manage the cloud from an API to interview I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they really building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway I'm just a joke what do you see in terms of where people are in that multi cloud a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in deserve one app in individuals one get happened Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never going to happen what I've seen with enterprise is I'm gonna put the workload in the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking team be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run Network part of the cloud connectivity to the cloud is kind of simple I agree IPSec VP and I reckon Express that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud provider right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean this is the day-to-day operations after it you know the natural let's add an app let's add a server let's troubleshoot a problem so what so your life something changes how would he do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's been a hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi-cloud wave that's coming as cloud native networking well there's no you know official garner definition but I can create one on another spot it's do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't even understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose api's where is that optimization where's the focus well I take what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of the cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of you right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plane out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that plane out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and ship or they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco monks bring you star in the cloud recall that each guy anywhere right so everyone what and and then there's cloud vision for my red star and contrail is in the cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not truly cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive clown that close one letter yeah so that was a big con surgeon i reinvent take the tea out of cloud native its cloud naive i went super viral you guys got t-shirts now i know you love it but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling out but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in cisco you it's a little bit more native than other ones because they're really ACI in the cloud you call you you really like configure api so the cloud and nsx is going that way and so is Arista but they're incumbent they have their own tools it's difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know and network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week oh the only b2 networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like AV X and others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in AWS you can user it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck Nets a cops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this program their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it via line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this VP see but this VP see automatically being your associate to your account you cannot go out on the internet you have to go to the transit VP C so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI mace which for us old folks know that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objectives oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well I as I said earlier that once you you could easily provision in the cloud you can easily connect to that cloud is when you start troubleshooting application in the cloud and try to scale so this that's where the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead the 20% extra functionality that of course every enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always gonna be that extra functionality the in in an automated and simple way that you talked about but yet powerful with up with the visibility and control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggards who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some the signals that are going on in their environment what are some of the threshold or things that are going on that there can pay attention to well well once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robber will hit the road but as I said it's easier to prove it it's okay it's 80s it's easy user transit gateway put a few V pcs and you're done and use create some presents like equinox and do Direct Connect and Express route with Azure that looks simple is the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not button tell me that I need to understand the basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi-vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server and internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this market because honestly public check hybrid cloud they're working on that that gets on-premise is done now multi-class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what their cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start to it especially an incumbent one so it's tempting to say on and I have a bunch of f5 experts nothing against f5 I'm going to bring my five in the cloud when you can use a needle be that automatically understand ease ease and auto-scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that net I'm going to use legacy stuff and then you have to start thinking okay what about visibility control about the tree cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming someone in charge with Gardner thanks for sharing thank you appreciate it [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of them data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement with aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for aviatrix already working in Amazon and now works in Missouri as well before we knew it GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake assure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build are done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments and David should Nick with fact set guys welcome to the stage for this digital event come on up [Music] hey good to see you thank you okay okay customer panelist is my favorite part we get to hear the real scoop we got the gardener giving us the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with the live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and it's soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets in different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation 'el opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on pram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into mortal multi-cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi-cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you you know had some comments about architecture matters it all starts I mean every Enterprise that I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep adverse adjusters network and that fourth generation or architectures be based primarily upon Palo Alto Networks an aviatrix a matrix doing the orchestration piece of it but that journey came because of the need for simplicity okay I need for multi-cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having to to automate that component and making it consistent with our on-premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that SD when brought to the to the wine side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was some of the there was a path that's probably the biggest list and there is when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those there we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gate without a transit Gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and in evolve later and maybe optimize or change the way you're doing things in the future but don't sit around and wait you can I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's the David yeah talking as earlier about day two operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice the architect I don't know what else I can do that simplicity of operations is key alright so the holistic view of day to operation you mentioned let's can jump in day one is your your your getting stuff set up day two is your life after all right this is kinda what you're getting at David so what does that look like what are you envisioning as you look at that 20 mile stair out post multi-cloud world what are some of the things that you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router CLI and troubleshooting things on in an ad hoc nature so moving more towards the DevOps model is anything on that day - yeah I would love to add something so in terms of day 2 operations you can you can either sort of ignore the day 2 operations for a little while where you get well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to realize it's it's such a such a big gap I think that's key because for us we're moving to more of an event-driven or operations in the past monitoring got the job done it's impossible to modern monitor something there's nothing there when the event happens all right so the event-driven application and then detect is important yeah I think garden was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the networks laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an intern crypt and they they ever get the question should I encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you've got a lot of complexity in your network what do you guys look at the future for yours environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance of things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting and get a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok we want to hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I see AV traces here they're they're a supplier to the sector but you guys are customers everyone's pitching you stuff people are not gonna buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like where API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like um it's definitely it's definitely API driven we we definitely look at the at that the API structure of the vendors provide before we select anything that that is always first in mind and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking become more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what it what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on site and they're gonna sit with you for your day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important Bobby how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's the Volvic bake-off last year first you win so but that's different now because now when you you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so the key is is they can you be operational you know within hours or days instead of weeks but but do we also have the flexibility to customize it to meet your needs could you want to be you won't be put into a box with the other customers we have needs that surpass their cut their needs yeah I almost see the challenge that you guys are living where you've got the cloud immediate value to make an roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's a there's a breaking point for sure you don't you don't get to scale this I like like Simone said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've got a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization think pause you're kind of like off a little bit it's not how it works I mean what is the reality in terms of implementing you know and as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers one of the blockers what are the enabler I think the reality is is that you may not think you're multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements in a secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to allow these clouds and used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the moment from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business team and and like like you said it's whether whether you're in denial or not of the multi cloud fact that your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or sure and just helping facilitate things they're doing the you know the heavy lifting API work for you or they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know makes you have designed yourself into a corner so the closer they're more cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will it make sense tgw is a game-changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool give you the beauty of both worlds you can use tgw with a gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go Mull one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint do you agree with that premise and then wit is multi clouds did you mall together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction that add value but the the network problem is still the same doesn't go away yeah yeah I mean you don't want to be trying to fit a square into a round hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the network infrastructure is there secure is available and is multi cloud capable yeah I'm at the end of the day you guys just validating that it's the networking game now how cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John fritz T Blaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Cooper welcome to stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move a pack from A to B and you get workloads exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your take yeah I mean it's it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to ET rate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like - we started out very much focused on one cloud and as we started doing errands we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are of and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really that's the enabler for this multi cloud trend but you guys taken we'll start with Amit what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it's the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make them a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea now our job is to enable them not to disable them do you think you guys think infrastructure as code which I love that I think it's that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network as code because storage and compute working really well is seeing all kubernetes on ServiceMaster and network is code reality is it there is it still got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way we get to do it yeah and even security groups and then on top and aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us it was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on Prem and wait and then so first that and then also in the journey where are you at from zero to a hundred of actually in the journey to cloud do you 50% there are you 10% yes I mean are you evacuating data centers next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together right in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's going to be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of you know lift and shift and when did that start and we started about three years ago okay okay go by it's a very different story it started from a garage and one hundred percent on the clock it's a business spend management platform as a software-as-a-service one hundred percent on the cloud it was like ten years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you Sora you guys mentioned DevOps I mean obviously we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this layer this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interestingly we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for soar as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth availability with your sim pop3 things guys SLA I mean you just do ping times are between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads I mean s LA's will be all over the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and whatever ability is our is there and our authority needs to operate on that so it's so you use the software dashboard look at the times and look at the latency in the old days strong so on open so on you try to figure it out and then your days you have to figure out just what she reinsert that because you're in the middle of it yeah I mean I think the the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that start thinking start tracking in your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment was it was it from day one no there were two reasons one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot Network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting is how do I solve or guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just in your thoughts on anything any common uh so actually a multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are how could people using them but Google's got a great network Google's networks pretty damn good and then you got a sure what's the difference between the clouds who with they've evolved something whether they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is approaches different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network and spend regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the yeah I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architectural solution for example amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has advantages its third to market and so has seen what Asia did wrong it seemed with AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the inability or the ability for Amazon to limit layer 2 broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional Network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you could talking about the cloud impact so that means st when the old st way is kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high-speed but now when you take the win and make it essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah I think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you are a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there Lanois same concept is that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's where is what you're seeing so much infrastructure as code yeah yes so for me I'll go back again to this its bandwidth and its latency right that bet define those two land versus win but the other thing that's comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to to protect what's inside of it so for us we're able to deliver vr af-s or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning this architecture thoughts on security are you guys are dealing with it yeah start from the base have apt to have security built in have TLS have encryption on the data I transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principles day Security's day zero every day and so we we always build it into our design build into our architecture into our applications it's encrypt everything it's TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff is interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive and think that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's are you being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total BS but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's getting a bang and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need to benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great time how about a round of applause DX easy solutions integrating company than we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba corkle will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products have incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the Lyons cloud connectivity is a new line of networking services so we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services and aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a VA Church were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed to work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole and their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT maybe Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John Ford with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we just heard from the customer panel you can see the diversity of where people come in to the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are exactly you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we're having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the and then we evolved into the next journey which is a foundational approach to what are some of the problem statement customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they digging into yeah so complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we tis anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard part's now upon us are you referring to networking what is specifically were you getting at Terrance's the easy parts done now so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the - so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it not okay in our internal environment as you know we're a huge company or as customers so we're experiencing that internal okay and every one of our other customers so I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c + w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking let's simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I would I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better right visibility's a huge thing jump in security alone network everything's around visibility what automation do you see happening in terms of progression order of operations if you will it's a low-hanging fruit what are people working on now what are what are some of the aspirational goals around when you start thinking about multi cloud and automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were gonna integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of a VHS let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference textures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi-cloud in terms of you know customers want choice they didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and be risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an interoperability approach is how do things interoperate we test it out we validate it we build a reference architecture it says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it in visibility so I think the visibility is what's what I see lacking across the industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in they're one of the ones that are emerging and the new brands emerging but multi-cloud you still got the old guard incumbents with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question while we were defining day two operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve the the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonish trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is that what's what happens do they call you up and say hey I need some multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's looks like typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got a factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what is VP she's sharing you know what is a private Lincoln or how does that impact your business we have customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I then is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to beep their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't forget in reveal kind of who they are but what does success look like in multi-cloud as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in that as you build that network foundation that architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off from and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen what what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good point guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators Hey [Applause] [Music] okay welcome back from the live feed I'm chef for with the cube Steve Eleni CEO of aviatrix my co-host our next panel is the aviatrix certified engineers also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foster min from Attica Stacy linear from Teradata and Jennifer Reid with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds towards a new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like a Squadron Leader Roger and leader yeah Squadron Leader so he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer will start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm eagerly working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but now working in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hmm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the VP C's and on the instance side is a security group or is it going on print and this is something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and I actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be we'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in network have always been the network's fault sure and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another hundred and these times are changing they see your squadron leader I get that right what is what is a squadron leader first can you describe what it is I think it probably just leading all the network components of it but are they from my perspective when to think about what you asked them was it's about no issues and no escalation soft my day is like that's a good outcome that's a good day it's a good day Jennifer you mentioned the Amazon thing this brings up a good point you know when you have these new waves come in you have a lot of new things newly use cases a lot of the finger-pointing it's that guys problem that girls problem so what is how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in those where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Stephen the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear but what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are full logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about you know that's dimmer fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young P so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way or you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and that's old guys that's where we thrive Jennifer you mentioned you you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static cuz back then you just said the network you got a perimeter yeah no there was no such thing ya know so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it now I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this within the program abilities it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global si you help the business issues what does it mean to do that is it code is that networking is it configuration is that aviatrix what is the amine oxy aviatrix is a certification but what is it about the multi cloud that makes it multi networking and multi vendor and easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that's hops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not going to solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six months ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed a good is that watching leader would put there yeah something that you see in your organizations are you recommending that to people do you see I mean I'm just I would guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I say from my side because we operate in the multi cloud environment so it really helps an official for us I think I would add that networking guys have always needed to use certifications to prove that they know what they know it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters buying helps give you validity so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics enough of the understandings that you have the tools necessary right so okay I guess my final question for you guys is why an eighth certification is relevant and then second part is share what the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why shouldn't someone want to be an ace-certified I'm used to right engineer I think my views a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get no I mean they're backwards so when you've got the training and the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding it okay so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network definition getting eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that's just the next progression I don't say I expend that to more automation engineers because we have those nails probably well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but I've never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who've tradition down on prime networking they can understand how that's going to work in the cloud too well I know we got just under 30 seconds left but I want to get one more question than just one more for the folks watching that are you may be younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacey we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions no we're going use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you've come from top-down now you're gonna start looking from bottom up and you want those different systems to cross communicate and say you've built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the how the pipes are working you guys know what's going some plumbing that's right and they gotta know how it works I had a code it it's right awesome thank you guys for great insights ace certain ABS your certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not gonna take long we got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the Cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community aviatrix comm starting a community a multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as to start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more importantly where they're going and define that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we solve we help you define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their twenty-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] you

from the silicon angle media office in Boston Massachusetts it's the queue now here's your host David on tape hello everyone and welcome to this week's wiki bond cube insights powered by ETR in this breaking analysis we want to dig into the so called multi-cloud arena some of the questions we're getting from our community are what is a multi cloud did we really need it what problems does multi-cloud solve and importantly what problems does it create how is this thing called multi cloud likely to evolve and who are some of the key players to watch how do they stack up relative to each other you know recently I got a couple of interesting questions from a customer that says I have all this AI action going on and doing sophisticated modeling and this data lives and oh clouds all over the place how do I cross connect to the data and the workloads that are running on these clouds with the consistence this consistent experience of what our other customers doing another question came up in the community today is there a financial advantage to multi cloud or is it just about avoiding lock-in so I'm gonna take a stab at addressing these questions so first of all let's look at some of the noise that's going on in the marketplace and try to extract a little signal every vendor especially the ones who don't own a cloud are touting this thing called multi cloud and they tell us that customers want to avoid lock-in and organizations want seamless integration across clouds and they say we the vendor are uniquely qualified to deliver that capability although as you can see here in for a not everybody agrees because some feel that multi cloud is less secure more complicated in higher cost now the reality is that one two and three are true as is for a to a certain degree but generally I would say that multi cloud to date is more of a symptom of multi vendor then a clear strategy but that's beginning to change and there's a substantial opportunity out there for anyone to win so let's explore this a little bit and an exclusive sit-down with aunty Jessie prior to reinvent 2019 John Fourier got Jessie to talk about this trend here's what he said we have a large number of companies who have gone all-in on AWS and that's growing but there's gonna be other companies who decide that they're going to use multiple clouds for different reasons you wouldn't have to say that the vast majority of organizations pursuing cloud tend to pick a predominant provider that it's not a 50/50 scenario it's rather it's more like a 70/30 or 8020 or even a 90/10 faria went on to write somewhat paraphrasing I think Jesse in my view it's not hard to find the reasons for using multiple clouds right is M&A there's shadow IT there's developer preference but it's really not multi cloud by design it's just more of the same Enterprise IT mishmash that we've seen for decades so I generally have to say I agree with that but it is changing and I want to dig into that a bit so first let me recap the basic premise that we work off of first cloud is winning in the marketplace we know this building data centers is not the best use of capital unless you're a data center operator or a hyper scaler or you know maybe a SAS provider maybe so more and more work is going to continue to move to the cloud this was pretty much the first wave of cloud if you will a cloud of remote infrastructure services for very obvious workloads like web test dev analytics and certain SAS offerings the second wave of cloud which we've been talking about for 15 years was or should I say is a hybrid connecting remote cloud services to on-prem workloads and the third wave which is really hitting somewhat in parallel is this thing that we call multi cloud now it's not a perfect analogy but these multi generational waves remind us of the early days of networking now some of you may remember that years ago the industry was comprised of multiple dominant vendors that control their own proprietary network stacks for example IBM had SN a digital or deck had decnet all the many computer vendors had their own proprietary nets now in the early to mid-1980s the OSI model emerged with the objective of creating interoperability amongst all these different communication systems and the idea was we're going to standardize on protocols and the model had seven layers all the way from the physical layer through the application but really in reality was a pipe dream because we were way too complicated and and it sort of assumed that customers are gonna rip and replace their existing networks and then standardize on the OSI model now in reality that was never gonna happen however what it did is it open the door for new companies and you saw firms like Cisco and 3com emerged with tcp/ip and Ethernet becoming standardized and enabling connections between these systems and it totally changed the industry as we now know it so what does this have to do with multi-cloud well today you kind of have a similar situation with dominant public cloud leaders like AWS and azure and in this analogy they are the proprietary siloed networks of the past like IBM and digital they're more open obviously but still ultimately customers are going to put workloads on the right cloud for the right job and that includes putting work on Prem and connecting it to the public cloud with call it a substantially similar and ideally identical experience that's what we call hybrid now that's today's big wave and you're seeing it with Amazon's outposts and VMware and Amazon and Azure stack etc so while all this hybrid action is getting wired up customers are putting work into AWS and Azure and certainly Google and IBM cloud and the Oracle cloud and so forth now customers are wanting to connect across clouds with a substantially similar experience because that reduces cost and of course it speeds business outcomes that's what we call multi cloud now I'm not by any means suggesting that Amazon and Microsoft are gonna go the way of the mini computer vendors I don't believe that I think leaders today are much more savvy and tuned into how to surf the waves they're more paranoid and they're frankly just smarter than back in the 70s and 80s but it's not a rite of passage if they ignore the trends they will face challenges that could become driftwood so you're seeing the emergence of some of the moves from the vendor crowd the big whales connecting their infrastructure like AWS and VMware and Microsoft and Oracle quite interesting and IBM Red Hat with everybody cisco Dell HPE with everyone Google with anthos and a lot of other players all are trying to stake a claim in this hybrid and multi cloud world but you also have these emerging players that are innovators companies like CrowdStrike in security cumulant in the backup space and many dozens of well-funded players looking to grab a share of this multi cloud pie and it's worth pointing out that they're all kind of going gaga over kubernetes now of course this makes sense because kubernetes has emerged as a standard it's certainly very popular with developers why because it enables portability and allows them to package applications and of course all they're related to tendencies around those applications and then hand that app off for testing or deployment and it's gonna behave in the exact same way as when they ran it locally this we've seen and we know this but I want to share something I had a great conversation with Bernard golden yesterday and he made an excellent point about well you know kubernetes and containers he said this portability is a necessary but insufficient condition for multi cloud to succeed you still have to have an integrated management approach to security ID management monitoring performance reporting and end get into cross-training of people and skills etc ok I want to shift gears and as always I want to dig into these segments and bring in the et our perspective now pretty sure ETR is a lot of data on multi cloud from their ven meetings and other surveys but what I've done today is pulled some data that I'm using is indicators or proxies for multi cloud so I can't go out and buy me some multi cloud today it doesn't really exist in that form so what we have to do is highlight some of the trends in the data and draw some inferences from that so let's take a look at this chart what it shows is the relative position of a number of companies that my view are participating in the multi cloud arena the chart plots these companies showing net score or remember spending momentum on the y-axis and we've just opposed that to what's called market share on the x-axis market share is a measure of pervasiveness in the data set and what we've done is we've filtered on three sectors cloud container orchestration and container platforms using that as a proxy for multi cloud so these are buyers 791 of them as you can see by the end who are spenders in these three areas and we're isolating on select group of names and as a last filter we selected only companies with 50 or more results in the data set from this survey and we're using this as a multi cloud sector proxy so let me make a couple of comments here first I know kubernetes is not a company but ETR captures spending on kubernetes it's one of the hottest areas in the data set with a nearly 82% net score so we're capturing that as a reference point the next thing I want to say is you can see the big cloud players Azure and AWS and once again as in previous breaking analysis segments we see those two look they're leaders they're out the lead both companies showing very very strong momentum from a net score standpoint now AWS you might say why are you including a diversity if they don't explicitly have a multi cloud offering but in my view you cannot talk about multi cloud without including the leading cloud supplier you also see Google not so much in the market share of the big two but Google's showing strong net score we've talked about that before and they're very well positioned in multi cloud with anthos there behind their playing cloud agnostic to try to catch up again remember this is a proxy that we are running it's not necessarily a reflection of firms specific multi cloud offerings it's an indicator based on the filters that we've run now let's take a look at some of the others rubric the data protection specialists and CrowdStrike was a security darling they show some real strengths both have multi cloud offerings and they have strategies around their look at how she Corp they stand out as an important player in our view as they provide developer tooling to run secure and and deploy applications across clouds VMware cloud is I believe it's a vfc VMware cloud foundation and it's right there in the mix and you can also see fortunate in there as well executing from a security position I talked about them last week in my braking analysis they have a nice cloud portfolio and they're benefiting from execution strong execution let me call your attention to IBM in Red Hat Red Hat OpenShift look at their respective positions on this chart IBM spending velocity or net score is low but Red Hat has quite strong spending velocity and this is CEO Arvind Krishna's opportunity leverage IBM's large install based presence shown here as market share or pervasiveness and bring red hat to the right and leverage open shifts coolness to increase IBM's relevance and elevate it elevated spending velocity if arvind can make the kind of progress that i'm showing here in this picture he'll end up being CEO of the decade but that really is IBM's opportunity you can also see I put Oracle in the chart as well because of their multi cloud relationship with Microsoft which which I actually think has great potential for running mission-critical Oracle databases as I've noted many times I've you know IBM and Oracle both have clouds they're in the cloud game there are hyper scalar clouds but they have very large installed software franchises why is that important because it insulates them from the I ass ix knife fight and the pricing pressures that are putting forth by the hyper scalars the finally I have to mention Cisco I've said many times comes at multi cloud from a position of strength and networking and of course security they've got a huge market presence and not without challenges but they clearly are a player here ok now let's go on and look at some similar proxy data basically the same cut isolated on a few big players participating in multi cloud so again same cut as before but this is this shows a time series isolating on some of those Biggie's showing their net score or spending momentum in cloud and container related sectors that I talked about you got Azure leading GCP showing momentum IBM Red Hat with open shift and VMware all with solid net scores that are in the green cisco not as strong from a net score or spending velocity standpoint but it's shared in or presence in the data set is significant in this cut so two takeaways here really are one this is a wide-open race it's jump ball you really can't pick a winner yet and to each is gonna come at this from their own unique position of strength which brings me to how we see this space evolving this simple chart here really shows how we see the multi cloud infrastructure stack emerging starting at the bottom we show in the stack networking you gotta have networking to cross connect clouds and this is where cisco you has to win the day not optional for them some big players are going after the control plane including Microsoft arc Google with anthos VMware with tans ooh IBM Red Hat and we think eventually AWS is a possibility to enter that game on the data plane you got some big whales like Dell EMC you got NetApp you've got HPE at IBM the big storage players as well you have specialists like pure who's doing some interesting things in block in the cloud and cumulonimbus mention you have a bunch of companies like Veritas cohesive the rubric vMac TIFIA is gonna be in there CommVault I mentioned Klum EO before IBM is another one you got a whole bunch of folks in networking big portfolio plays from the likes of Cisco I said to network I met security from Cisco Palo Alto fortunate along with many of the security specialists we've highlighted in the past like CrowdStrike and there are many many others now on the leftmost side of this chart is really interesting we showed the full stack interconnects here we're referring to the direct cloud to cloud connections in functions up and down the entire stack examples here are AWS VMware yes that hybrid but also emerging at the edge and Microsoft and Oracle so the bottom line is we're seeing a battle brewing between the big companies with larger appetites gobbling up major portions of the market with integrated suites that are playing out within each layer of the stack competing with smaller and nimble players that are delivering best to breed function along those stack layers all right let me summarize so here are the questions that I said I would answer let's see how I did what the heck is multi cloud well let me first say it feels like everything in IT is additive what do I mean by that well we never get rid of stuff you keep things forever think about it the typical enterprise has multiple data centers they get many SAS providers more likely they have you know more than one Iast provider and they're starting to think about what should I do with the edge there is no standard for hybrid or multi cloud deployments you talk to 100 customers and you're gonna hear 120 or 150 or 300 different environments and several orders of magnitude of challenges that they face do we really need multi-cloud not an ideal world no we wouldn't need multi cloud but we talked about how we got here earlier how real is it how real is multi cloud now look companies use multiple clouds it's is it easy to do things across scope these clouds no so it's one of these problems that the industry is created that it can now make money fixing it's a vicious cycle I know but so goes the enterprise IT business what problems does it does multi-cloud solve and create look the goal of multi cloud should be that it creates more value than just the sum of the individual parts and that is clearly not happening yet in my opinion moving data around is a problem so ultimately the value comes from being able to bring cloud services to data that resides all over the place and as Bernard golden implied even with kubernetes the experience is far from seamless so we understand that technology created this problem and IT people processes and technology will be asked to clean up the crime scene as I often say it's a common story in enterprise tech we talked about how multi-cloud will evolve along a stack that it comprises specialists and big companies with very big appetites my opinion is that multi-cloud will evolve as a mishmash and vendor relationships the right tools for the right job the edge IT and OT tensions mergers and acquisitions these are gonna create even a bigger mess down the road we have well-funded companies that are exceedingly capable in this business and the leaders are gonna get their fair share cloud is a trillion-dollar market opportunity and there will not be in my opinion a winner-take-all and multi cloud so who wins like I've tried to lay out some of the leaders within different parts of the stack but there's way more to this story I do believe that the cloud players are well positioned why cuz they're they invented cloud EWS and others who followed right now Microsoft and Google are playing actively in that market but I definitely think AWS will I that space but I think VMware Red Hat IBM Cisco etc some of this from the respective positions of strength and I've sort of they have the added benefit of being cloud semi agnostic because generally they're not wed to a hyper scale cloud you know IBM as a cloud oracle as a cloud but it's on a hyper scale cloud and as always there's specialists that are gonna solve problems that are too small initially for the big whales to see so they get a leader lead bleed to market advantage but those opportunities can grow over time and allow these guys to reach escape velocity now so I'll say multi-cloud in and of itself is I believe an opportunity one that will be attacked from a position of strength within the stack and there are opportunities to be specialists up and down that stack the Akashi Corp alright this is Dave Volante for wiki bonds cube insights powered by ETR thanks for watching this breaking analysis and remember these episodes are available as podcasts you can check it out as you're driving your car wherever you listen to two podcasts you can connect with me at David Villante at Silicon angle calm or at D Volante on Twitter or please comment on my LinkedIn posts thanks for watching everyone we'll see you next time [Music]

[Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you you you you [Music] [Music] [Music] [Music] ladies and gentlemen please take your seats good morning ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 alright so we've got a fantastic event today I'm really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a takeoff of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any PowerPoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got some owners chart of Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the US it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every Enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Franco Bree you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission-critical they care about visibility they care about control that about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers did they see the same thing we're going to validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're going to talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day two operations what does that mean well day 1 is one day of your life who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do i operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix we as leaders ooh we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CCI es what Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when to try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of joob John Ferrier [Applause] okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel to customer panels before that Gartner is going to come out and talk about the industry we have a global system integrators they talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask some own rashard to come on stage from Gartner we'll kick it all up [Applause] [Music] okay so kicking things off certain started gardener the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer the ninety-two a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering in the marketplace with hybrid cloud and now moving quickly to multi cloud is really was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow IT or application people are sometime a DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right as with different account and they create mesh to manage them and they have direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides that the atoms that are sent removing that to that cloud they ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the ad hoc way doesn't scale at some point idea has to save them because they don't think about the - they don't think about operations we have a bunch of VPC and multiple clouds the other way that if you do the left and shift week they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these words are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct and that's what I call the optimal phase but even that they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS as accounts there's subscription and in as ER and GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that still wanna manage the cloud from an epi xx view I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they read they building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third-party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway up just a joke what do you see in terms of where people are in that multi cloud like a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in Azure one app in individuals one get app in Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never gonna happen what I've seen with enterprise is I'm gonna put the work load and the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking King be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run network part of the cloud connectivity to the cloud is kind of simple you know I agree IPSec VPN and I reckon Express route that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud providers right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean it's just the day-to-day operations after you know the natural let's add an app that's not a server let's troubleshoot a problem so what ending so your life if something changes now what do you do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's the hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi cloud wave that's coming as cloud native networking well there's no you know official gardener definition but I can create one on another spot is do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose API guys where is that optimization where's the focus well I think what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of that cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of view right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plan out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that playing out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and chip are they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco wants bring you star in the cloud they call that each guy anywhere right so everyone what and and then there's cloud vision for my red star and Khan trailers in a cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not really cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive well not so close one letter yeah so that was a big culture to reinvent take the tea out of cloud native it's cloud naive that went super viral you guys got t-shirts now I know you love yeah but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling up but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in Cisco you it's a little bit more native than other ones because they're really scr in the cloud you can't you you really like configure API so the cloud and NSX is going that way and so is Arista but they're incumbent they have their own tools is difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know a network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week I was only be two networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like aviation others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in a table us you can use it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck net sec Ops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this ability their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it V line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this V PC but this V PC automatically being your associate your account you cannot go out on the internet you have to go to the transit VPC so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI days which for us old folks know what that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objections oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well as I said earlier that once you you could easily provision in the cloud you can easily connect to the cloud is when you start troubleshooting application in the cloud and try to scale so this that's what the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead to 20% extra functionality that of course every Enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always going to be that extra functionality that in an automated and simple way that you talked about but yet powerful with up with the visible in control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggers who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some of the signals that are going on their environment what are some of the thresholds or things that are going on that there can pay attention to well one once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robbery will hit the road but as I said it's easier to prove it it's okay it's a TBS it's easy use a transit gateway put a few V PCs and you're done and you create some presents like equinox and do Direct Connect and Express route with Azure that looks simple as the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not but I'm telling you that I need to understand a basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server an internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know you not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this because honestly public cloud check hybrid cloud they're working on that that kids on premise is done now multi class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what there's cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start with especially an incumbent one so it's tempting to say I have a bunch of f5 experts nothing against f5 I'm going to bring my five in a cloud when you can use a needle be that automatically understand is ease and auto scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that met I'm going to use legacy stuff and then you have to start taking okay what about visibility control about the three cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming summit in charge with Gardner thanks for sharing thank you appreciate it thanks [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of that data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement myth aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for her aviatrix already working in Amazon and now works in Missouri as well before we knew what GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake measure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build or done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments David should Nick with fact set guys welcome to the stage for this digital event come on up [Applause] [Music] hey good to see you thank you okay okay customer pal this is my favorite part we get to hear the real scoop against a gardener given this the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with a live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and the soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets and different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation --all opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on bram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we're we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into more of a multi cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you had some comments about architecture matters it all starts I mean every Enterprise I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep versus Justice Network and that fourth generation architectures be based primarily upon Palo Alto Networks an aviatrix I have a trick to in the orchestration piece of it but that journey came because of the need for simplicity ok the need for a multi cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having the to automate that component and making it consistent with our on premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that sty and brought to the do the web side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was the middle it was a path that's probably the biggest lesson there is that when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective we like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those now we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gateway about a trans a gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and it evolved later and maybe optimized for change the way you're doing things in the future but don't sit around and wait you can't I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's David yeah talking as we prepare about a day to operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice to the architect I don't know what else I can do that simplicity of operations is key right all right so the holistic view of j2 operation you mentioned let's could jump in day one is you're you're you're getting stuff set up day two is your life after all right this is kind of what you're getting at David so what does that look like what are you envisioning as you look at that 20 miles their outpost multi-cloud world what are some of the things then you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router seoi and troubleshooting things on in an ad hoc nature so moving more towards a DevOps model there's anything on that day - yeah I would love to add something so in terms of date to operations you can you can either sort of ignore the day - operations for a little while where you get well well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to to realize it's it's such as such a big gap I think that's key because for us we're moving to more of an event-driven operations in the past monitoring got the job done it's impossible to modern monitor something that it's nothing there when the event happens all right so the event-driven application and then detection is important yeah I think Gardner was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the network's laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an equipment to encrypt and they they never get the question should i encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you got a lot of complexity in your network what do you guys look at the future for your environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance or things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting you got a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok wanna hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like encryption and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I'll see aviatrix is here they're their supplier to the sector but you guys are customers everyone's pitching you stuff these people are not gonna here to buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like we're API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like it's definitely it's definitely API driven we we definitely look at the at the PAP i structure of the vendors provide before we select anything that that is always first of mine and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking and more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what do what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on-site and they're gonna sit with you for a day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important probably how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's involving take off last year first you win so but that's different now because now you and you when you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so key is is that it can you be operational you know within hours or days instead of weeks right but do we also have the flexibility to customize it to meet your needs could you want to be you want to be put into a box with the other customers we have needs that surpassed or cut their needs yeah I almost see the challenge of you guys are living where you've got the cloud immediate value depending on roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's it there's a breaking point for sure you don't you don't get to scale this I like like Seamon said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've spent a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah you know part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization take pause you're kind of like off it's not how it works I mean what is the reality in terms of implementing you know in as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers what are the blockers what are the enablers I think the reality is is that you may not think your multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements Inc and then secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to lot of these clouds and they used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the problem from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business need and and like like you said it's whether whether you're in denial or not of the multi cloud fact that then your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or Azure and just helping facilitate things they're doing the you know the heavy lifting API work for you or are they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know you have designed yourself into a corner so the closer they're more than cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will they make sense tgw is a game changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool gives you the beauty of both worlds you can use tgw or the Gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go mole to one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint you agree with that premise and then witness multi-cloud stitch them all together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction to add value but the the network problem is still the same go away yeah yeah I mean you don't want to be trying to fit a square into a round Hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the then they're working for structure is there secure is available and is multi cloud capable yeah I'm at the end the day you guys just validating that it's the networking game now cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate Thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John for its Dee Mulaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Koopa Pokemon stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move attack from A to B and you get work gloves exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your taking yeah I mean it it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to iterate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer but okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like to we started out very much focused on one cloud and as we started doing Atkins we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are available and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really got the enabler for this multi cloud trend but you guys taken we'll start with a mint what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it means the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's a latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea our job is to enable them not to disable them do you think I do you guys think infrastructure has code which I love that I think that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network is code because stores and compute working really well is seeing all kubernetes and service master and network is code reality is that there is got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way three guys do it yeah and even security groups and then on top an aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah think about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made cuz it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on-prem and what and then so first that and then also in the journey where are you at from 0 to 100 of actually in the journey to cloud do you 50% there are you 10% are you vacuum datacenters next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's gonna be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of lift and shift and when did that start and we started about three years ago okay okay cool bye it's a very different story it started from a garage and 100% on the clock it's a business spend management platform as a software as a service 100% on the cloud it was like 10 years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you is or you guys mentioned DevOps I mean honestly we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interesting we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for as or as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth I think availability with your sim pop3 things guys SLA I mean you just do ping times between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads SLA is will be all of the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and what our ability is hour is there and our authority needs to operate on that so it's solely use the software dashboard look at the times and look at the latency in the old day is strong so on open so on you try to figure it out and then your day is you have to figure out just what's your answer to that because you're in the middle of it yeah I mean I think the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that's starting start tracking your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment over that was it from day one now there are two divisions one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting how do I solve our guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public Internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just on your thoughts on that I think any comment on that so actually multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are hiking people using them but Google's got a great network he googles networks pretty damn good and then you got Asher what's the difference between the clouds who where they evolve something where they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is the approach is different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network can span regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the I mean I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architect your own solution for example Amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has a banjo it's third to market and so it has seen what a sure did wrong it's seen what AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the the inability or the ability for Amazon to limit layer two broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you get talking about the cloud impact so that means st when the old st winds kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high speed but now when you take a win and make the essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah i think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you're a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there land when same concept as that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's what you're seeing so much infrastructure as code yeah yeah so for me I'll go back again to this its bandwidth and its latency right that that define those two land versus when but the other thing that comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it so for us we're able to deliver VRS or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning that's architecture thoughts on security are you guys are dealing with it yeah start from the base have app to app security built-in have TLS have encryption on the data a transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principals day security is day zero every day and so we we always build it into our design we want our architecture into our applications its encrypt everything its TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff was interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive insane that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's not me being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total B yes but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's giving you all these and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need a benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great pen how about a round of applause DX easy solutions integrating company that we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba porco will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs its critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products that incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the lance cloud connectivity there's a new line of networking services that we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services an aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a v8 church we were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed for work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole in their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT infrastructure baby Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John fray with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we start from the customer panel you can see the diversity of where people come into the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yep yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we were having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying we're starting to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the apps and then we evolved into that next journey which is a foundational approach to what are some of the problem statements customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they did digging into yeah some complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard parts now upon us are you referring to networking what is specifically were you getting at Tara says the easy parts done that so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises that are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the >> so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean - does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it okay in our internal environment as you know we're a huge company or as customers are in 30 so we're experiencing that internal okay and every one of our other customers so I I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c @ w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking but simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the at the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I what I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better Bank visibily is a huge thing jump in security alone network everything's around visibility what automation you see happening in terms of progression order of operations if you will it's the low-hanging fruit what are people working on now and what are what are some of the aspirational goals around when you start thinking about multi cloud an automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were going to integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of athe let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference architectures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi cloud in terms of you know customers want choice didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and D risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an Billee approach is how do things interoperate we test it out we validate it we build a reference architecture says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it invisibility so I think the visibility is what's what I see lack in cross industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in there one of the ones that are emerging and the new brands emerging with multi cloud you still got the old guard incumbent with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question what we were defining day to operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve that the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonishing trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is the what's what happens there they call you up and say hey I need multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got to factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what does VPC sharing you know what is a private link and asher how does that impact your business you know customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I've been is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't again reveal kind of who they are but what does success look like in multi-cloud as you as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in is you build that network foundation at architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi-cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off Prem and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen with what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators [Applause] [Music] okay welcome back from the live feed I'm chef for with the q Steve Valenti CEO of aviatrix my co-host our next panel is the aviatrix certified engineer is also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foss from informatica Stacy linear from Teradata and Jennifer Reed with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds story to new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like it Squadron Leader Roger and leader yeah Squadron Leader he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer we'll start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm really working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but networking in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the V PC is and on the instant side is a security group or is it going on print and is this something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be will good I'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in never I've always been the network's fault and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another 100 and these times are changing yeah they say you're Squadron Leader I get that right what is what is the squadron leader first can you describe what it is I think probably just leading all the network components of it but not they from my perspective when to think about what you ask them was it's about no issues and the escalation soft my day is a good outcome that's a good day it's a good day again every mission the Amazon this brings up a good point you know when you have these new waves come in you have a lot of new things new we use cases a lot of the finger-pointing it's that guys problem that girls problem so what how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in was where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Steve and the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear like what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are four logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about yeah that's never fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young piece so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way here you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and old guys that's where we thrive Jennifer you mentioned you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static because back then you just said the network you got a perimeter yeah I know there was no such thing yeah no so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it and how I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this with and programmability is it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global s eyes cover the business issues what does it mean to do that is it code is that networking is the configuration is that aviatrix what is the I mean obviate races the ACE certifications but what is it about the multi cloud that makes it multi networking and multi vendor easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that is ops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not gonna solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed good is that watching leader would put there yeah is that something that you see in your organization's are you recommending that to people do you see I mean I'm just I guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I see from my side because we operate in the multi cloud environment so it really helps and it's beneficial for us yeah I think I would add that uh networking guys have always needed to use certifications to prove that they know what they know right it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters by your name helps give you validity um so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics and enough of the understandings that you have the tools necessary right so I guess my final question for you guys is why an eighth certification is relevant and then second part is share with the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why should someone want to be an ace-certified I'm used to write engineer I think my view is a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get know I mean they're backwards so when you've got the training in the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding of ok so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network initially eating eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that it's just the next progression I would say I expand that to more automation engineers because we have those nails probably extended as well well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but have never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who have tradition down on Prem networking they can understand how that's going to work in the cloud - well I know we've got just under 30 seconds left but I want to get one more question and just one more for the folks watching that are you maybe younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacy we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions networking use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you you've come from top-down now you're gonna start looking from bottom-up and you want those different systems to cross communicate and say you built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the pilot pipes are working and some plumbing that's right works at how to code it that's right awesome thank you guys for great insights ace certain babies you're certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not going to take long we've got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the Aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community a bh6 comm was starting a community at multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more important where they're going and to find that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we saw we help you cook define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their 20-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] [Applause] [Music] you

>> Live from Toronto, Canada, it's theCUBE, covering Global Cloud and Block Chain Summit 2018. Brought to you by theCUBE. >> Hello everyone, welcome back to theCUBE live coverage in Toronto for the Block Chain-Cloud Convergence Show. This is the Global Cloud Block Chain Summit part of the Futurist Event that's going on the next two days after this. Our next guest is Kesem Frank, AION co-founder and CEO of MavenNet. Doing a lot of work in the enterprise and also block chain space around the infrastructure, making it really interoperable. Of course, Jenna Pilgrim, co-founder and COO of a new opportunity called Network Effects. Welcome to the cube, thanks for joining us. >> Thanks, thanks for having us. >> Thanks, John. >> You guys were just on a panel, The Real World Applications of Block Chain. IBM was on it, which, been doing a lot of work there. This is real world, low hanging fruit, block chain, everyone's pretty excited about. A lot of people get it, and some don't. Some are learning. So you've got the believers, the I want to believe, and then the nonbelievers. Let's talk about the I want to believe and the believers in block chain. Some real world applications going on. As it's evolving, so there's evolution of the standards, technology, but people are putting it to use. What's going on in the sector around some of the real world cases you guys talked about? >> I think we're seeing a lot of collaboration as far as real world applications go, because I think people are sort of starting to understand that if a distributed network is going to work or is going to be secure, it needs diversity and it needs mass scale. If lots of different parties can work together, then they can actually form a community that's really working. As far as real world applications, there's some really interesting one as far as supply chain. Kathryn Harrison at IBM talked about their pilot about shipping, bringing together the global supply chain of distribution. There's a bunch of interesting ones about food providence and bringing together different parties just to make sure that people know what they're eating and that they are able to keep themselves safe, so I think those are two definitely interesting ones. >> Kesem, block chain, supply chain, value chains, these are kind of key words that mean something together. >> Right. >> Making things work in a new way, making things more efficient, seems to be a trend. You're kind of in that world. Is it efficient? (laughing) How's the tech working? What are some of the core threshold issues that people have to get over? >> So you know, John, that's exactly the question to ask. A lot of folks out there are looking at block chain and the promise it represents, and the one big question that keeps echoing over and over is when is this going mainstream? When are we going to see something, a domain, a use case, that is actually natively on a block chain? I think that, essentially, we kind of owe it to ourselves and to everyone that cares about this stuff to ask what's working today, August 2018 and what is still kind of pending? I co-founded a project called AION. For us, interoperability is really one of the key facets that you need to be able to solve for to make block chains real. And again, here's the 60 second argument. If you're going to grow all these solutions that are centric around the use case, they solve for different pinpoints and different stakeholders care about them. They don't really create the cohesive kind of ecosystem until they can all talk to each other, and then you have to ask yourself is the original hypothesis where it's going to be one main net, one chain that's going to rule them all, and everybody gets to play on it and everybody deploys their Dapps on stuff like Fabric or R3 or Ethereum, or whatever it might be. That is absolutely not the way we're seeing enterprise actually shaping into this domain of block chain. What we're seeing is big consortiums that already have value, tangible today, out of doing stuff on chain, and the biggest thing to solve is how do I take, to Jenna's point around supply chain or food providence, whatever it is, how do I actually open it so I can now start writing insurance events, payment events, banking, underwriting, auditing, regulation? There's this gigantic ecosystem that needs to be enabled, and again we are actively saying it's not going to be by an organic model where you and I do everything on top of a single solution. There will be a multitude of solutions, and what we need to solve for is how do we convert them from disparate islands that don't talk to each other into a cohesive ecosystem? >> This is a great point. We were talking on our intro, and we talked last night on our panel, about standards. If you look at all the major inflection points where wealth was created and value was created around innovation and entrepreneurship and industry inflection points, there's always some sort of standard thing that happened. >> Right. >> Whether it's the OSI model during the early days of the internet to certain protocols that made things happen with the internet. Here, it's interesting because if you have one chain and rule the world, it's got to be up and running. >> Yeah. >> It's not. There's no one thing yet, so I see that trend the cloud has, private cloud, public cloud, but public cloud was first but people had data centers. >> Right. >> Both not compatible, now the trend is multi-cloud. You can almost connect the dots of saying multi-chain >> Right. >> Might be a big trend. >> Right. >> This is kind of what you're teasing out here. >> That's exactly what we're about, and I think it's very interesting, the point you're making about dissimilarities between the two domains. We are in a cloud convention, and to me it means two things. One, we absolutely see the mainstream people, the mainstream players in industry, starting to take this seriously. It used to be a completely disparate world where you guys are a bunch of crazies with your Bitcoin and ether and what not. They're definitely taking this seriously now. The second thing, when you think of cloud as a model, how cloud evolved, we used to have these conversations around are you crazy, you're telling me that my data is not going to be on premise? >> It's not secure, now it's the most secure. >> Oh my God! It's in the cloud, what's a cloud? (laughing) You think of the progression model that was applicable back then, right? 10 years, 15 years back, where we started privately and we tell them OK, we'll take this side step of hybrid and then fully public. Took them a while, took them almost 20 years to get their heads around it. >> There's no one trajectory. What's interesting about block chain and crypto with token economics, there's no one trend you can map an analog to, you can't say this is going to be like this trend of the past. It's almost developing it's own kind of trajectory. A lot of organic community involvement. Different tech involvement. >> Totally. >> Different engineering mindsets coming together. You're seeing an engineering-led culture big time going on. That's propelling it up to the conversations of let's lay down the pipes, let's start running apps, but I'll do it within a two year window (laughing). >> I think the big thing to understand about that is yes, you need a whole host of developer talent to build distributed systems, but at the end of the day those systems still have to be used by people. They still have to be used by society, you still have to understand how to talk to your chief executives about what's happening within your company or what your tech teams are doing. There's a growing need for marketers, for PR people, for people who speak, I don't want to say plain English, but people who understand how-- >> Translate it to the real world. >> Yeah, they need to translate it, and how to bridge the gap between legacy systems and how do you take what you were doing before and transform it to a distributed ledger system? How do you do that without just paving the cow path? >> It's interesting, it's almost intoxicating, 'cause you got two elements that get people excited. You got the token economics, which gets people to go, "Whoa," the economics and the liquidity of money and/or value creation capture equations completely changing some of the business model stuff, which could be translated to software and Dapps and software general stuff or SaaS, et cetera. Then you got the plumbing or the networking side of it where things like latency, interoperability, absolutely matter, so with all that going on in real time, it's kind of happening at 30,000 feet and trying to change the airplane engine out. People are failing, and so there's some false promises, there's also false hopes that have not been achieved, so this clouds up the real big picture which is this is an innovative environment. We're seeing that trend. But when you get to the end of the day, what are people working on, to me, is the tell sign. Kesem, what's your project, talk about AION and the work you're doing, specifically give some examples of some of the things that you're doing in the trenches. >> Sure. >> What are you trying to solve, what are some examples you're running into and how does that relate to how things might evolve going forward? >> Sure, so there is a multitude of different problems that we work on but if you want to stick just to the fundamentals? Let's take one gigantic issue that everyone's kind of tackling from different perspectives, let's talk about scale. Scale is, especially in block chains especially challenging just because of how the technology works. How decentralized can you get before you're faced with gigantic latencies and before transaction cost are kind of through the roof? When you think about it, that is all a result of how we kind of contemplate these early stage networks. It was always the one network that is going to scale to infinity. Absolutely not the way it's going to work out. So from my perspective, again, sticking to this one issue, if you could actually give me a decentralized rail that maintains consensus throughout two networks, I can now actually have two trusted kind of go-tos instead of always putting the full brunt of the throughput on one single network. For us, that's kind of a no brainer application to interoperability. If you could actually give me all these trusted networks that work in tandem, I could now start splicing throughputs across many different parallel kind of rails. Not to similar than how we can solve for super computing. We understood there is a limit on how fast can a single CPU go and we started going wide. >> That's an interesting point, I want to just double click on that for a second because if you think about it, why would I have multiple rails and multiple systems? Maybe the use cases are different for them. >> Correct. >> You don't want to have to pick one cloud or one chain to rule them all because it's not optimized. We saw that with monolithic systems and cloud is all about levels of granularity and micro service and micro everything, right? >> Correct. >> And I would also say that gets into a security issue as well, right? You're talking about multiple layers but you also will have multiple layers of permission. You'll have multiple layers of how much information someone can see and what I think is emerging, if data is the new oil, then what's emerging is for the first time we're now able to trust data that we do not own. For corporations who say, "I don't know to market to you "if I don't know everything about you." But at the end of the day, they want to be able to leverage your data but they don't need to secure it and I think that cybersecurity issue is a huge, huge thing that's definitely coming. >> I want to get both of your thoughts on this, because we were talking about this last night. We were riffing on the notion that with cloud compute and data really drove scale. So Amazon is a great example and their value now is things like Kinesis and Aurora, some of their fastest growing services. You got SageMaker, probably will be announced at re:Invent coming up as the fastest growing service, right now it's Aurora. All data concepts. So the dataization really made cloud, great. >> True. >> Okay what's the analog for crypto and block chain? Tokenization is an interesting concept. There's almost an extension of cloud where you're saying, hey, with tokenization, the tokenization phase, how do you explain that to a common person? You say, is token going to be the token and the money aspect of and the economics the killer app? How's it transverse the infrastructures, plural? >> Yeah, or is the wallet going to be the browser? Or how are all of these things happening? >> How do you make sense of this? What's your reaction to that trend? >> So I actually get excited when I think about what token, on the most profound level, actually means. When you kind of think of where value happens in the context of these gigantic enterprises, right? You think of Apple, Amazon, Google, Facebook, any of them, and you kind of think of what the product is, it's all about the data and it's all about how do you convince people to give up data so they can monetize on it. And then you have two distinct, like literally gigantic groups of stakeholders at play. You have the users, that essentially get something free, right? I get to post on Facebook or I get to write an e-mail on Gmail. Then you have the stakeholders that actually extract all that value from my activities. A token, I think most profoundly represents, how do we actually get to a unified group where the user himself is the stakeholder that gets to extract the data? And again, the proposition is pretty straightforward. The more you use a network and the more the network becomes valuable and grows, the more value the token that drives at it. >> So it changes the value capture equation? >> Correct, different model altogether. >> The value creators get to capture the value and obviously network effects plays a big part in this? >> Yes. >> Which is your wheelhouse. (laughing) >> Yeah, definitely. I think it really comes down to core principles. Now you're able to really get down, to what Kesem was talking about, about when you're designing a token or if you're designing an incentive mechanism, you're really going down to the sort of deep game theory of why people do specific things and if we can financially incentivize people to do good rather than punish them or fine them for doing bad then we can actually create value for everyone. We're designing a new economy that now has the ability to propel itself in a fair and prosperous way, if done correctly, obviously that's the disclaimer afterwards, but. >> I love what you're saying there because if you look at collective intelligence a lot of the AI concepts came around from collective intelligence, predictive analytics, prescriptive analytics all came around using data to create value. I always talk about fake news because we have a cloud of media business that's kind of tokenized now but fake news it two things, it's payload, fake news, the fake content and then the infrastructure dynamics that they arbitraged, with network effects. They targeted specific people, fake payload, but the distribution was a network effect. Again, this was the perverse incentive that no one was monitoring, there was no- >> Well and I think in that case, yes there is news that is inherently false information but then there's also a whole spectrum of trueness, if you want to call it that so now we have this technology that allows us to overlay on top of that and say, "Well what is the providence of my information?" And with different layers of block chain systems you're actually able to prove the providence of your information without exposing the user's privacy and without exposing the whole supply chain of the media because there's like media buyers, go through all kinds of hands. >> And we believe the answer to fake news, frankly, is data access, collective intelligence and something like a block chain where you have incentive systems to filter out the fake news. >> Totally. >> Exactly. >> Reputation systems, these things are not new concepts. >> It's all about stake at the end of the day, right? It's how do you keep a stakeholder accountable for their action? You need backing so I think we're definitely on the same page. >> I love, I could talk about fake news all day because we think we can solve that with our CUBEcoin token coming out soon. I want to shift gears and talk about some of the examples we've seen with cloud. >> Sure. >> And try to map that to some navigation for people in how to get through the block chain token world. One of the key things about the cloud was something they called shadow IT. Shadow IT was people who said, hey, you know what? I could just put my credit card down and move this non core thing out in this cloud and prove to my boss, show them, not pitch 'em on the Power Point deck, to say look it, I just did this for that cost in this timeframe, and that started around 2009/2010 timeframe, the early digerati or the clouderati kind of did that but around 2012 it became, wow, this shadow IT is actually R and D practice. >> Mm-hmm. >> Right. >> You started to see that now, so the question that we see for people evaluating in the enterprise is how do you judge what's a good project? Certainly people are kicking the tires and doing a little bit, I won't call it shadow IT, but they're taking on some projects as you were talking about on the panel. How should they, the enterprises in general, the large companies, start thinking about how to enable a shadow IT-like dynamic and how should they evaluate the kind of projects? I think that's an area people just don't know what to look for. Your thoughts? >> I want to add a premise to that, because I think that's absolutely the right question to ask. We also need to add the why. Why should we, as people that do native crypto currency, even care about enterprises? A lot of people kind of theorized when Bitcoin was created to say it was anti institutional is an understatement, right? Aren't we meant to kill enterprise? The thing is, I don't think it's going to be a big bang. I don't think it's going be we wake up and nobody's using banking anymore or nobody's using the traditional healthcare or government and you know whatever insurance policies. We care about block chain in the context of enterprise because we think block chain is a fundamentally better model of doing things. It kind of does away with the black box where I need to be in business, I need to blindly trust you and it introduces a much more transparent and democratic model of doing things. We absolutely want to introduce and make block chain mainstream because that's important for us. When you think of how we do it, to your question, AION is all about interoperability, right? We create a solution that helps scale and helps different networks, decentralized networks, communicate to each other. What we also do with MavenNet, the company I run, is essentially make that enterprise friendly. It's extremely hard to do adoption and implementation within an enterprise, they're very immune to change. >> Antibodies as they say. >> Oh. >> The antibodies to innovation, they kill innovation. >> Totally, so going back to your original question, it all starts with a P and L. If somebody is going to authorize, you know, an actual production system in enterprise for block chain, it needs to create a tangible value, a tangible return, quickly and that's the key. The model that actually scales is you start by flushing out inefficiency plate. You show the enterprise how you could actually achieve, I don't know 20%/30%, that's the order of magnitude that they care about, efficiency by moving some part of your value chain on top of a block chain. >> It has to have an order of magnitude difference or so. I mean cloud was a great example, too, it changes the operating model. >> Yeah. >> They achieve what they wanted to achieve faster and more efficiently and operated it differently. >> Correct. >> And people were starting at it like a three headed monster like what is this thing, right? The cloud thing. And throwing all kinds of fud out there, but ultimately at the end of the day, it's a new operating model for the same thing that they're trying to do with the old stuff. >> Mm-hmm. >> I mean, it's almost that simple. >> Yeah, I think in some cases you need to really, in my previous life at the Block Chain Research Institute, we encouraged a lot of our clients to really take a step back and say, well will I actually, A, will I have this problem in eight years or seven years or 20 years or 50 years, if we're really fundamentally building a new financial system or a new way of doing things that is fundamentally different? Are we building it on old technology? We need to make sure that, and that's why you've seen banks were the first in the door to say, "Yeah, payments, that sounds great, that sounds great." But the real applications that we're seeing from banks are in loyalty, they're in AMLKYC, they're in the sort of fringe operations. Something like payments is going to take a really long time to push through because of those legacy systems because payments is the fundamentals of what banks do. >> This is an interesting point, I want to get your thoughts to end the segment because I think one of the things that we've certainly seen with cloud that over the generational shifts that have happened, the timeframe for innovation is getting shorter and shorter, so timeframe is critical so if the communities are fumbling around hitting that time to value, it seems to be trending to faster and we don't want to hear slower because these systems are inadequate, they're antiquated. >> Mm-hmm. >> These are the systems that are disrupted so the timing of, whether it's standards, or interoperability or business models, operating models, they got to be faster. >> Yeah. >> That's the table stakes. >> I think it all comes down to collaborative governance. >> People have to figure out block chain faster. >> Yeah. >> What's holding us back? Or what's accelerating us? What's the key for the community at large from the engineering community and the business community to make it go faster? Your thoughts? >> Right, so I think we're still searching for the next killer app. If Bitcoin is the reason we're all sitting here today and I profoundly believe that. >> Yeah. >> What is the next thing that drives change on a global scale? That's kind of what we're trying, collectively as an industry, to figure out. Sure, many kind of roadblocks on the way. Some of them educational, perceptional, regulation, technology, but the next big wave that's going to accelerate us to the next ten years of block chain is that next killer app. Organizations such as myself, Jenna, that's our day job, we wake up and that's what we do. >> I mean I've always said, and Dr. Wong, who's the founder of Alibaba Cloud agreed with me, I've been saying that the TCPIP protocol, that standard really enabled a lot of interoperability and created lots of diverse value up the stacks of the OSI model, Open Systems Interconnect, seven layer model, actually never got standardized. It's kind of stopped at TCPIP and that was good, everyone snapped at the line, that created massive value. >> But that's a collaborative governance thing. That's people coming together and saying that these are the standards that we wish to adhere to. >> We need the moment right now. >> Yeah, so you see organizations like the Enterprise Ethereum Alliance coming out with a prospective list of standards that they think the community should adhere here. You know you have the ERC20 standard, you have all these different organizations, the World Economic Forum is playing a role in that and the UN is playing a role, especially when it comes to identity and those kind of really big, societal issues but I think that it comes down to that everyone plays a role that I'm doing my best, I think it's going to be somewhere in the realm of data so that's where I've chosen to sort of make my course. >> I think this is a good conversation to have, and I think we could continue it. I mean, I read on Medium, everyone's reading these fat protocols, thin protocols but at the end of the day what does that matter if there's no like scale? >> Yeah. >> You can have all the fat protocols you want, more of a land grab I would say but there's certainly models but is that subordinate or is that the cart before the horse? This is the conversation I think is in the hallways. >> Totally agree, totally agreed. >> Guys, thanks so much for coming on theCUBE, really appreciate it. Breaking down real world applications of block chain we're at the Global Cloud and Block Chain Summit. It's an inaugural event and think it's going to be the kind of format we're going to see more of, cloud and block chain coming together. Collision course or is it going to come in nicely and land together and work together? We'll see, of course theCUBE's covering it. Thanks for watching. Stay with us for more all day coverage. Part of the Futurist Conference coming up the next two days. We're in Toronto, we'll be back with more after this short break. (theCUBE theme music)

>> [Narrator] From San Francisco, it's theCUBE, covering Radio 2018. Brought to you by VMware. (upbeat techno music) >> Welcome back everyone. We're here with theCUBE in San Francisco for exclusive coverage for VMware's Radio 2018. I'm John Furrier, your host. This is the event where everyone comes together in the R&D and the organic engineering organization of VMware to flex their technical muscles, stretch their minds, compete for the papers, and also get to know each other. And the key person behind this is the chief research officer David Tennenhouse. Thanks for joining us today. >> Thank you John. Really glad to be here. >> So you're the chief research officer. You got to look at the company-wide agenda. But this event is more of a special event, organically. Talk about for the folks out there watching what's different about this event that goes outside the scope of kind of the top-down research. >> Yeah this is really, you know, for the developers by the developers. So when you said I'm in charge, I'm definitely not in charge. And you know, we have a program committee. There's a programming committee chair. It's much like the way an academic conference might be organized, where you know, there's kind of a group of academics that sort of watch over the content. In this case, we have many hundreds of folks that submit proposals into radio. They can't all get selected. It's very competitive because in addition, if you get accepted, you get a ticket to radio. You get to attend. So everybody really wants to do that. >> Talk about the organic nature. 'Cause this is one of the things that I've seen that's been part of a world-class organization. Like Amazon has their own process for it called the big idea. They have certain working documents that process to foster any idea across the organization. How important is that as part of Radio? I mean literally it's anyone right? >> Well it's not just Radio. It's important to the whole company. So I think of this as when you're working on innovation, you're gonna have sort of a breadth component. You want everybody doing a little. And some of that's gonna be incremental. One thing I learned in a prior role at a different company is you know if you add up a lot of two percenters, that's how you can double things and keep on Moore's law every year. So you're gonna get some of that. And you're gonna get some really disruptive ideas. So you know, from a top-down point of view, we try to drive some disruptions. Some disruptions show up organically from the troops. And a ton of that breadth stuff shows up. >> I'm honored to be here. It's the 14th year, and some T-shirts commemorating the key milestones from way back in the day. This is the first year press was allowed in. I noticed a handful of folks came in to kind of document this. A lot of the brightest minds in VMware here. Again, great to have us. We're super excited. But share with us. Like, what's happened over the years. Give some examples of where people were coming together, where there's a collision of ideas, and just that combustion that happens. Can you share some stories around key notable, or potentially as Raghu pointed out, there's been some misses too. (laughing) >> Yeah, you're gonna get some of that. I mean you've gotta take risks. Not everything's gonna work. You know and just to speak to misses. What I've learned in the innovation and research space is as much as anything, it's about timing. It's pretty rare that you completely technically miss. Usually engineers have an idea. They'll figure out a way to make it happen. Then the question is, is it the right time? Are the customers ready? Is the market ready to go in that direction? So, that's just to talk to that. >> Timing's everything. >> Timing is a big deal. >> Well there's never a miss too in R&D because if you, like Pat Yelson said, understand when it's gotta be re-casted. Know if it works or not. >> Yeah just understanding. So those are the ones actually you know I feel, what I really hate is if for some reason we have to end a project and we haven't actually gotten to the bottom of it. And so you don't know yes or no. And sometimes that can be the kind of time's run out, right. You've decided well, even if it works, it's too late. But you know, getting back to some of the examples, I'll focus on some more recent ones. We had some really interesting work come together on containers. And there were some folks that, and this is going back like four years ago. Containers aren't a new story, and certainly not for VMware. But around four years ago, there was a proposal at Radio that had to do with hey let's make containers a first class citizen on VMware's platform. Okay, so top level that makes great sense. Let's go do it. Containers are great for developers. The IT folks still want the isolation they get form VMs. Let's put these together really effectively. So that was top level. There was a next level, the idea that said gee at Radio, a couple years before, there'd been this idea of being able to do something called VM fork, or being able to clone a VM. And saying you know... And this came out of our end user computing group, the VDI folks. And if you think about it, if you've got a virtualized PC, you want to be able to clone that so you can start these up really fast. And the container folks said hey, we've got the same problem. Could we actually try to make use of that technology and use that as part of our bigger container push? So you know, those are examples of things that came together at Radio. And there are also examples of things where the market timing may not have quite been there. So we went out with the container work. That was actually post-Radio. It was funded. We incubated it. You've got vSphere Integrated Containers hit the market exactly the right time. >> Timing right there. >> Right, timing right there. But what we learned as we actually started doing trials with customers was that they didn't actually need the instant clone on the containers. What they needed is throughput. They wanted to know that they could do large numbers per second as opposed to you'll get that container really quickly. So as the team went along, they actually shifted away from that fork idea. We'll probably come back to it when the time's right for it. >> Well you have a nice little positioning there. I like the timing. 'Cause by the way, entrepreneurial timing is the same way. You go outside... >> I was a VC. (laughing) >> Okay, so you know okay. Timing's everything. How many times you seen that entrepreneur wicked early on it going... And they keep scratching that itch and finally they get it. The art of the timing. But also the art of knowing when to, what to keep in inventory. Pat mentioned vCloud Air as an interesting example. Recognizing abandonment there. Okay hey, let's just stop, take pause. Let's use what we have. >> Do something else. >> Do something else. >> Gotta do something else. And by the way along the way, in parallel with vCloud Air, we had built up these vCloud partners. And that's phenomenal right. So we have you know, people think in terms of a couple of very large public clouds. But we've got literally thousands of people running public clouds in either specialized markets, or particular countries, that are running on our platform. And you know that whole vCloud Air effort helped push that forward. >> So where were you a VC? Just curious. >> I was actually in a company that fits with sort of my role in research and innovation. I was in a specialized firm, boutique firm, new venture partners, that specialized in spin outs from large companies. This goes to the timing, right. I'd previously been at another large company. You know, and whenever you have a research portfolio, you're gonna have some projects that you started. They were technically successful. That's your first notch. Then you go look and say hey, can I find a business model for it. Some of these are both technically successful. You find a business model, but you had anticipated that the company strategically was gonna zig. The company zagged. Now this is a great opportunity that doesn't quite fit. So you know, we did those as spin outs. >> Well I love the perspective too of you said earlier, David, around not getting to the bottom of it. And that's the most frustrating part. Because you just gotta get some closure you know. Like okay, this thing, we took it to the end, completion, this is not gonna... Good try guys. >> And we know why. >> And you know why. Now let's take it to the next level. Now the market we're living in now I heard with Ray O'Farrell, I was talking with earlier. We talked about the confluence of these big markets coming together. Infrastructure market, which is kinda declining on paper. But cloud is filling the void. Big data's becoming AI, and blockchain over the top. These are four major markets. And at the center of them, intersecting all these nuances, security, data, IoT. >> Governance. >> Governance. So there's some sticky areas that are evolving based upon these moving markets. Opportunity recognition's another one. So this is what you're kind of doing now with the research. Talk about opportunity recognition. >> We definitely do that. And I do want to say on the infrastructure side, you know something to recall is that as people, you know they've got their private clouds. Those are individually getting actually bigger as they consolidate. But now with IoT, you're seeing edge computing pop up. Right, so the private infrastructure doesn't go away, it moves around. It's like a liquid. And you pour it from place to place in some sense. >> Moving computer around. Sound like what Ray O'Farrell was talking about in his keynote, early days of VMware. Again, Compute's the center of this. >> Right, Compute, but you know I'm a networking guy so you know, we've grown that. And I think that in fact, you know more and more as we make progress with software defined network, and network virtualization. And if you think about that, so you know let's look at that. So Compute's definitely at the center of what happens in the data center, in the cloud, right. You're gonna want to be able to string those piece together. So today we've got AirWatch. I think that's strategically really key. Because it gives us a little bit of presence on the edge devices that touch people. That's one of the ways information gets from the physical world to the virtual world is through people. >> It's an edge device. People are things too. >> IoT, right. So we're you know, working hard. And that's one of the projects that we incubated, and researched, and is now become a business at Vmware. It's to get that presence right at the edge of the gateways that bridge between the things that are connected to the physical world, and bringing it into the virtual world. Now if we can put our software defined network between all that, so you got it between the public cloud, the private cloud, the mobile devices in people's hands. >> And on premise, data center. >> Exactly, all of 'em. >> All right, so here's a question for you. This is one of those trick questions. Is the cell phone an edge device or an IoT device? >> Well I think it's in many ways both. And what I think of it is is more of a gateway. If you think about the IoT world, you have the things. >> IoT is a strict definition though in your mind, right. People refer to IoT as more of a sensor thing to a physical device. >> I tend to think of it as it's got some connection to some physical device. It's able to bring information in from the physical world. Okay, so now you look at your cell phone. It can bring information. It's got that microphone. It's got that camera, right. It can bring information in. >> [John] Connect it to a physical person. >> It can put information back out. Yeah, through a physical person. I've been in the space for a long time. Going back to my time at DARPA, we set out to create the IoT world. This wasn't an accident, right. We looked at this and said, okay the main way information gets between these two worlds today is through human beings. The way I used to explain this to the generals is you know, we can't keep putting human beings in the direct line of fire of information technology. So we've gotta get these devices, gotta get all these sensors. It's taken a long time. This is you know again, timing. But if you look at the research world. >> By the way, incredible work you've done by the way from there to here, it's been amazing. >> You know pull this along. But you know so when you look at that cell phone, it's got some of those sensors. It's got actually a whole pile of sensors in the phones today. It's got actuation, the ability to put the information back out. It's also a gateway. Because typically you know, particularly through its Bluetooth functionality, and as we get Bluetooth low power now. So it's also acting as a gateway to connect up other devices around your body, network etc. >> Personal networking, whatever comes on your physical presence. >> So you know, turn that around and it says in the IoT world, we've gotta manage gateways. We've gotta make sure gateways stay secure. Because they're really gonna be the sort of main perimeter, the line of defense. If you think about all these things that are gonna be out there, as an industry, we're gonna collectively try very hard to secure all those things. But let's be realistic. They're gonna be supplied from a wide variety of companies, and they're gonna last longer than people might think. >> How much of those devices are operationally, operation technology is non IP, versus not IP. Internet Protocol. >> Non Internet Protocol. Yeah, yeah. >> Internet Protocol now. >> [David] Non Internet, you had it right. >> Got the VC in the brain there. The VC, IP, I'm like get that IP right. So internet protocol devices, which has some challenges but that's getting fixed, versus OT just sensors proprietary. >> Yeah well either proprietary or let's say, you know it may be an industry standard, but an industrial standard. So today, a very large fraction, particularly you asked about how we focused at Vmware. Well one of our foci is we're about what are our enterprise customers gonna need. So when we think IoT, we're not really thinking that much about the consumer devices. We're thinking about those enterprise devices. So a lot of those will use... >> That's where AirWatch might come in. So employees still have phones though. >> Employees still have phones. So that's why I said, so there's the human interface. We want to be there. And there's the other enterprise interfaces to all these sensors. That could be in a factory. It could be in a smart city, any number of places. So as we pull information in from those, we're gonna find that they come from a lot of different suppliers and they're gonna last a long time. You know, even if you buy a device that's got a three to four year lifetime, probably 10 to 20% of those still gonna be around 10 years later, right. You're smiling because you know that in your home you have some wifi connected devices that are a little older than they probably should be. >> And they have full processing capability threaded processes on it, which could be running malware as we speak. >> So as I said, as an industry, we'll try to secure those really edge things. But the reality is we're gonna have to draw the line at the gateway. >> It's a lot more security work. I totally hear you. I mean the light bulb could have a full thread on there. The surface area is so huge now. >> And there have been attacks on light bulbs. >> Yeah I know. So I gotta ask you a question. 'Cause you bring up this networking edge, which by the way I love anything that's network. 'Cause I think this is the future of work. How is the future of work impacting some of the R&D you're doing. Because you talked about AirWatch them having more mobility. The human impact, society, whether it's mission driven and or just human collaboration going digital. You're gonna need to have policies. You need to have a networked society. This is super relevant. But it brings back that future work. >> It does. And so couple different aspects. You know, one you know, which just relates to a point you raised is if you look at something like our Workspace ONE product, if you've had a chance to do that. It's kind of a win win, because you get one portal. So you know, an employee for an enterprise, they've got one portal. They get access, it doesn't matter whether they're getting to a web app, they're getting to a you know, a DVI supported application. They're getting to something that's on a server, something on a SAS player, right. They get through that portal. So for them it's convenient. I mean for me as a manager, I love this, right. Because whether I'm on my cell phone, I'm on a laptop, doesn't matter, I can get to the same expense app. I can approve things. >> You don't need to carry two phones. My work phone and my... >> And I can do all these approvals really easily, right. So I also don't worry. I don't see the difference between which device I'm on. At the same time that you're delivering that convenience to the user, you're delivering governance because the IT team can be deciding how that portal's populated, how things are connected, right, and how the wiring works. All the authorization, you've got a common identification system and all of that. So that's kind of very specific to you know, let's say near term changing the user interface. In terms of the broader future of work, clearly machine learning is the big story here, right. And I think that what we're gonna see is, particularly again in enterprise, more and more need for data analysts to be able to look at the big data. We're gonna see sort of more and more use of machine-learning technologies. It's gonna you know basically creep in everywhere. And we're getting this at just the right time. So if you want to think about future work in the big national and international scale, what you really sort of stop to look at is say, gee, okay, these machines are gonna do all this work. What about the people? And you know a lot of people therefore get concerned. Gee, the computers are gonna take away all the jobs. Right, you get these sound bytes. >> I think right now we're worried about fake news and real content. (laughing) >> Well let's come back to that one later. But there is a sense of gee, you know, the computers will take on all the jobs. And you know what I think people are not doing carefully is looking at the demographics. Because if you look at basically all the developed economies for practical purposes, we actually have a demographic problem. Our problem is actually not a surplus of workers. It's gonna be a shortage of workers. In fact, actually in the US right now, you're starting to feel this. Now that's at the peak of the economic cycle. So of course you feel it, you know, a bit. >> They need trained workers too. Also people who qualify. >> Right. So I think the thing we really need to look at is how do we do a much better job at matching, you know, sort of workers, both folks coming into the workplace, people with existing skills, to available opportunities. Because actually we're gonna have a shortage of workers. And it's not just sort of the US and Europe. I mean China, Japan. Well Japan for a long time. China, headed to a shortage of workers. I was out in Singapore not too long ago and was surprised to find out not just that they're concerned. But they went and looked at the Southeast Asian countries around them that are their markets. They're looking at a shortage of workers. So you know, if we didn't have something like machine-learning and AI coming along, we'd be sitting there saying, how are we gonna keep our economies growing? >> We need augmentation for sure. >> We need this augmentation. And it's coming at just, you know, you talked about timing. You know, it's coming at just the right time. Now, there definitely are gonna be some tough transitions along the way, right. So we definitely, you know, for example, as autonomous vehicles come along, we've gotta figure out, okay, all those people that are driving vehicles, what are they gonna do going forward? But let's not kid ourselves too, you know. If you've got trucks moving around with high-value cargoes, you're not gonna leave those unattended, right. We're gonna have to figure all this out. So there's gonna be a lot of interesting opportunities. >> What's your take on blockchain? Well first of all, GDPR, real quick. Train wreck, useful? >> I think it's you know, if you backed up and asked me four or five years ago, I'd have said train wreck. And largely because we still don't have the sort of kind of international consensus on what the rules should be. >> But you mentioned governance earlier. That certainly needs to be at the center of the action. >> Right, but you know, if we take a look now, it seems like it's showing up at just the right time, right. You know, in that sense. I think part of what's happened is over the intervening years, a lot of countries outside of Europe, because they realize these regulations would apply to them, they've worked with European regulators to help the regulators understand the technology, you know, help the companies understand. >> That's a good politically correct answer. I'll just say I think it's a shit-show personally. But you know. I mean it's gonna force people... It's like Y2K in money making, but Y2 never happened. It's forcing people to really, I think the value of GDPR is the big companies are gonna get hit hard on some suits. Just the trolling thing bothers me. Just the trolls that come out of the woodwork. But I think the positive that puts the center of the value proposition, making data, not a one off, like backup and recovery. It has to be core to technical operations. >> And making privacy something that's really in that first class category. You know, as I said. >> Great first step, but... There's a big but. >> There is more to be done. >> Hopefully they don't go after us little guys. All right, final question, blockchain. We are super excited about blockchain. You have teams working on this. >> [David] I am super excited about blockchain. >> Talk about your view on blockchain. Why are you excited about it? Obviously we feel it's very efficient, makes inefficiencies efficient across all industries. Your thoughts. >> Okay so again, we look at things through this prism. What are enterprise customers gonna be looking at? What do they want? And you know, so we're not you know... I think you're in the same place. We're not looking at the crypto currencies, right. That's not the thing. And in fact, we're not even looking at cohabiting on the Bitcoin blockchain. Because do you really want to run your business in the same place that a whole bunch of other people are running illegal businesses and the whole thing. >> And by the way, there's some technical issues. (laughing) >> We'll get to that. We're gonna get there. But just even as a starting point. So we pretty quickly looking even you know, three, four years ago said, okay enterprise is not gonna want to go that way. But this idea of a federated ledger, right. So if you can make federated ledgers and we can have reusable technology, that means now, if I want to federate with other companies or other organizations, or you know, or you need companies federating with governments, or governments federating with each other. Anywhere you want to pull together essentially a club for the exchange of data, with a persistent record of what happened, you've now got a common way of doing it, right. Or we can drive towards that. You know there'll be a standardization process to get there. But so it's not to me, federated ledgers means lowering the barrier to federation. And I think that's pretty exciting. Whole bunch of places. You know, supply chain, clearly one. Financial technology, but... >> David, we gotta spend some time, have you come in the studio. I'd love to explore some of these great topics with you. But I gotta ask you one final question. You know, with your history going back to ARPA, D-ARPA days, and looking at really the beginning of the information super highway, IP, connecting some universities together, to today, the waves that have gone through. We've talked about standards. The OSI stack, you had all these grandiose standard plans. Not all of them have happened exactly as planned. But defacto standards play a really important role. It galvanizes community, gives people guiding principles, a north star, whatever metaphor you want to use. The key is the enabling disrupting technologies, a defacto standard. What's happening now in your mind that you see out there that's starting to emerge as defacto? 'Cause certainly there's a lot of standard things going, open sources for tier one citizen growing, rapidly, which is greatness. Cloud is booming, unlimited resources, Compute, fingertip compute... All this is good. >> Yeah. >> All these new standards, I got Kubernetes, I got this going on, what's emerging? >> Well again, they're defacto, right. Kubernetes is an interesting example of basically open source meets defacto. And that's pretty exciting right. I mean, we're excited about it. I think people are often surprised we're a fan of open source. And I guess really, I just like to sort of back up a notch. Because you know what you touched on is defacto standards, whether it's open source or not, have suddenly become a lot easier. When I say suddenly, over like a 10 year period. And I think what's going on there is this is part of the change to software. So you know, if you're talking about hardware, and you got screws, you know, and you got threads, these physical things have to match, and they have to match exactly, right. Say when you travel overseas, you need to carry converters, physical converters to convert from one thing to another. So if you want to interoperate, if you and I want to have stuff that interoperates, we needed to build like either, do the same thing, or have a physical adapter. There was a cost to not having a standard. If you think about in the software world, we can build software converters, right. So if I've got you know, say we've got two, or three, or four, or even 50 defacto standards in the software world. You know, blockchain. So there's 50 new things. Everybody launches their own. Pretty quickly, the market will drive that down to a small number. And then you can put software converters in place. So we no longer actually have to get to one. >> [John] That's the software economic model. >> It's a big change. >> And that is huge. So by the way, we had Dirk Hohndel on at CubeCon. Love his open source mission, just a shout out to you guys, doing a great job. You guys at VMware certainly that we know, love you over on the East Coast. Final prediction. Final question. Give us a prediction. >> Give you a prediction. >> 2018, second half of the year, what's gonna happen? What's gonna be a notable thing that you see out on the horizon that might happen in the marketplace that might be notable for people to stand up and pay attention to? >> I think we're gonna see some significant developments in the blockchain space. And it's gonna be in the category of people starting to announce real deployments. And you know, if you're sort of looking at that time frame, you know you've had a lot of different enterprises try things. We've had people kind of dabble at things. I think you're gonna start seeing some people really move significantly in that space. >> And do you think like, just to follow up on that, do you think like in the database world now, where by the way, it's okay to have a zillion databases now. 'Cause you talk about databases. >> But it consolidated down to a few players. >> You get some extraction layers. It's okay to have a few variety of blockchains. I mean, there's no one blockchain. >> Correct, so that's where I think as I said, you're gonna see actually a bunch of these deployments. They'll be using different technologies. And then the fun really starts right. As people consolidate, especially with open source, they swap ideas. We boil it down to what's the best of the best. We've got you know, stuff we're doing certainly to knock the throughput down, sorry throughput up, latency down. (John laughing) And you know, we think we've got a very scalable approach. And most important, you know something that's really... I don't know if you talked to people about our sustainability. You know, it's a key value for VMware. >> [John] Yeah, lot of great standards there, yeah. >> So you can imagine we looked at blockchain. We looked at proof of work. And we said that's proof of energy wasted. We're not going there. >> Gotta make it more efficient. >> I think you're gonna see more and more folks focusing on things like Byzantine fault tolerant. Ours is scalable. You know SBFT. >> Yeah performance is key. And the energy's a huge problem. >> But performance and at acceptable energy. You can't you know, just waste. It's immoral to just waste energy. And it really goes against what a lot of the whole IT industry's built up. You know, I think we've, over the decades, we've done a lot of things for the good of society. And we gotta stay the mission. >> I think as the more, I won't say mature, but big world-class organizations join in, I think that'll straighten itself out. And certainly, as any evolution would see, the web. I remember dial-up and AOL. It can't go as fast as this minicomputer. Well you don't get it, it's the web okay. David, thanks so much for coming on, appreciate it. Great conversation here at Radio 2018. I'm John Furrier, Cube coverage of VMware's annual 14th year conference, at Radio 2018. Thanks for watching. (upbeat techno music)

>> Announcer: From San Francisco, it's theCUBE covering OSIsoft PI World 2018, brought to you by OSIsoft. >> Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're in downtown San Francisco at OSIsoft's PI World. It's been going on for 28 year, I think. I saw some 15 year pins. It's my first year pin, but I just heard that 28 years, 68 people. This year 3,000 people talking about the industrial internet, the internet of things, and it's happening here. A lot of places talk about it's coming, it's happening here. We're really excited to have two guests on from OSIsoft Richard Beeson. He's a CTO. Richard, great to see you. >> Yeah, thank you. >> And Michael Van Der Veeken, he's a senior developer. Welcome. So first off, impressions on this year's PI World compared to when you started out 28 years ago. >> Yeah, you said it. We started in San Francisco in 1990 at a small hotel down by Fisherman's Wharf, and we had 68 of our closest friends. And it's just been an amazing journey, an amazing journey to see the customer base just continue to appreciate the message, appreciate the value and the consistency that we've bene bring, and most recently just seeing this incredible explosion around the value of information in operations, in IoT and the time-space. >> It's funny because we usually cover it from the IT side and a lot of the IT players are excited now to be bringing IT and connecting it with OT and, in fact, I can show you very formal handshakes and exchanges of pleasantries around that. But you guys have been coming at it from the OT side for a very long time, before there was IP sensors on all these machines, before there was 5G, before there was saduke, before there was all these kind of enabling technologies for what people are talking about now for the industrial internet, but you guys have been doing it for a very long time with the existing infrastructure that was already in place at these places >> Yeah, it is kind of funny. Sometimes we'll say, hey, we've been doing this IoT or industrial IoT for the last 30 years. It's what process control engineers have been doing. You need to get the data from the sensors, from the operation to be able to control it. So the act of control, the act of optimization, the act of running a plant, of running any kind of operation requires that. >> Jeff: Right. >> The big shift has just been fundamentally in the scale, the cost point and just the general availability of that kind of information. It's really changing the game. >> Right. >> And a lot of the same principles still apply. And we've had experience here for 30 years now. And with the whole IoT boom, a lot of the same principles still apply to streaming data, to real-time data, and the PI system is able to support that. >> Right, but it's interesting because now you have a whole new level of computer horsepower that you did have many years ago. You've have a whole new level of networking speed which is even going to go up again with 5G on the mobile side shortly which is going to give massive amounts of more data, and the, of course, to store and everything else just gets cheaper, cheaper and cheaper so you're kind of enabling technologies under the cover or probably just allowing you to explore and expand dramatically the value that you guys are able to generate. >> Yeah, on one had it changes how we do what we do, but, fundamentally, you go back to the original proposition. For our customers, it's all about getting all of the information into the system, no matter where it's coming from, traditionally DCSs, now IoT devices and beyond. And it then becomes all about making that data available in the way, in the place, in the form that they will value it, and there's a myriad. One of the beautiful things about this conference is we see our partners, we see our customers. We see hundreds and thousands of different technologies and applications built around this information. That hasn't changed. It think that's one of the things Michael was eluding to. >> Yeah and you mentioned more available computing power and things like that, but what we see is that using that, people can get much more actionable information out of their data, things or types of analyses that were previously, we were unable to do that because we didn't have the right technology or the right computing power. >> Jeff: Right. >> But now we do. And especially if you can combine different sources of data and people are starting to share that data, you can get way more value out of that raw data that comes from those sensors. >> Right, but now we're going to talk about kind of the next thing, one of the next things. There's always the next thing. And that's blockchain. A lot of talk about blockchains. There's talk about bitcoin and cryptocurrencies. We're going to just put that on the side for now, and really talk about the fundamental technology under the covers which is this blockchain. We see IBM making big investments in it. We hear about it all the time. What are you guys doing in blockchain? And what do you kind of see as an opportunity that you hope that you eventually you'll be able to execute on using blockchain technology? >> Right so we have been researching blockchain for a little while now, and we're still kind of in exploration phase. We first wanted to really get a good understanding of the technology. Mainly to be able to separate the hype from the hope. There is a big hype around everything that is blockchain. But we really want to start looking at where does it actually make sense. Where does it actually add value? Are there situations where a centralized system might actually make much more sense? Or are there actually situations where this decentralized shared ecosystem makes more sense. So I think we have a decent understanding of the technology now, and we're starting to have those conversations with customers. Where should this make sense to you? So this week at PI World, we had our first conversations about that. We had our first session The session was very well attended. There was very good feedback. We'll have a more of a deep dive session this Thursday. And, yeah, we're really looking for those different use cases and to identify patterns within those different use cases across our different industries basically. >> And are you getting pull from the industries. Are they asking you for you guys to do this? Do they see either the curiosity or the opportunity or, I don't want to say hope, that's not a good word, to use blockchain in this distributed, trusted, non-centralized transaction engine to take care of some big issues that are out there right now. >> When I get out and I talk to executives around our customer base, I'm hearing at least three things, multiple times. It's a bit of a pattern. One is how could we use or would it be possible to use blockchain or some other technology in protecting or verifying the consumption or the use or the sharing of data, so kind of the outbound field. Another thing that I'm hearing frequently is most of our customers have very complex supply chains, very complex distribution chains, and as materials that they either depend on or create flow through these supply chains, there's often data around the conditions or the volumes or the paths that they take. And as that information transitions across various ownerships, various boundaries, how do they guarantee the authenticity, the availability and where that information can go in conjunction with that product. And then another one I've been hearing recently which was, I guess, not surprising, but it was novel when I first heard it is one of the activities in operations that every operator goes through is they send instructions or commands or settings or operational conditions down into their factory. How do you know if you can trust the instruction that has been delegated down? How do you know who did it? How do you know how long that instruction is valid for? All different aspects around that. So those are just three very, very significant challenges that our customers are surfacing for which this may be a solution. >> Right. >> And that's some of the fun, I think in going to this research path that we're going down. >> And I want to add to that the whole concept of the exchange of value within a blockchain network also makes the monetization of data very possible. People are starting to realize that the data they're collecting or the information they collected out of that data actually has value to other people. So can we find an easy way for them to monetize on that so see the data as an asset. And that's something that, you know, there are a number of startup projects that focus around that, and they're really looking into that, okay, would that make sense for our customers and how could we potentially tie into that or make that available to our customers. >> Right, the balance sheet value of data is an interesting topic because, you know, before data was just expensive because we had to store it and we had to keep it and we threw most of it away because we had to buy servers and machines to store it. Now, obviously, on the consumer side, you see the valuation of the data with companies like Google and Facebook whose valuation is a function of the value of that data even though its not reflected on their balance sheet and it's an interesting concept. How do you not only monetize it, but eventually get it on the balance sheet so that there is all the benefits that come by having that on the balance sheet with the value of that data. And that's the first time I've ever heard of using blockchain potentially as a way to capture, track and extract that value from that data. >> Exactly, and there are many different applications. It could be, for instance, a renewable company that has a wind farm that is monitoring the environment or monitoring the weather. That data is something that they use. But that data could potentially be very interesting to other companies or maybe to local governments as well. So is that data that they can monetize on? Another aspect could be, for instance, in autonomous vehicles where you're driving past somewhere and you want to get information about what are the gas prices or where can I get something to eat or things like that. So those could be really quick even microsecond transactions >> Jeff: Right. or interactions between a vehicle and whatever is in its environment. But maybe there are some way to do some quick micropayments of that data because that is valuable to that vehicle, and, in turn, that vehicle could also sell some of the data that it is collecting about the weather, about the road conditions, about traffic. So, in general, potentially we could see this whole economy around data arising. >> Right. >> And there's also a lot of cost in validating the trust now. We talked to some of the shipping lines and like 50% of the cost of shipping is the processing of the paperwork that basically does the validation that you just kind of outlined. Is it what it's supposed to be? Did it come from where it's supposed to be coming from? It is going to where it's supposed to be going to? And literally it's like 50% of the cost of shipments is processing this paper. So not only does it provide value, but it unlocks another whole set of value that currently is just getting eating up by super inefficient, still paper-based not even Excel, right. They probably still have copy machines. >> Transportation is one of the worse. (Jeff laughs) >> But you look at that scenario and a number of these others, immediately you go to this notion of data ownership. You eluded to it. Philosophically and practically, OSI is firmly committed to all of the information that we manage for our customers is our customer's data. They own that. But even as they get into these complex landscapes, then there really is that question. As materials flow through these supply chains, who owns the data associated with that. So this is going to be an interesting frontier >> Right. where these things have to get resolved and understood. And most of our customers consider the 10, 20, 30 years of operational data that they've preserved one of their more valuable IP assets. It's both an amazing frontier and amazing opportunity and something that's going to stir up some emotions as well. >> Right. And then you got the geopolitics of it as well because of the disparate laws all over the place about data, data treatment and exactly where was the data generated. That's always one of my favorite things when you really dig down as to where was that data actually generated. And it's not necessarily an easy thing to determine. So here we are 2018, what are you guys working on this year? If we come back a year from now, what are we going to be talking about? >> So right now, we are starting the conversation. We are starting to have this discussion. We have some assumptions where blockchain might make sense to us as a company especially to our customers. So this year, we really want to use this year to validate some of those assumptions, to really work with our customers but also with academia to find out where does this actually make sense. How can we get the most value out of this amazing new technology that has a lot of promise. And maybe we'll see us starting prototyping some of these solutions together with our customers. >> You going with that? >> Yeah, I'm going with that. >> All right, Richard's going with Michael, all right. So we're going to leave it there. And thanks for taking a few minutes and congratulations. I don't know if you've been here for all 28 years, Michael. >> Seven years. >> Seven years, pretty good. But what a great story, what a great success and really happy to come here and learn some of the story. >> Yeah, I'm honored every year. It just blows me away what I get to see and listen to and the people I get to meet so thank you. >> Thank you. All right, and he's Richard. >> Thank you. >> And he's Michael, I'm Jeff. You're watching theCUBE from OSIsoft PI World 2018 in downtown San Francisco. Thanks for watching. (upbeat music)

>> Announcer: From San Francisco, it's theCUBE! Covering OSIsoft PI World 2018. Brought to you by OSIsoft. >> Hey welcome back everybody Jeff Frick here with theCUBE. We're at OSIsoft's PI World 2018 in downtown San Francisco, they've been at it for decades and decades and decades talking really about OT and efficiency. And we're excited to be here it's our first time, and really want to talk to a customer, excited to have our next customer CJ Smith, She's a Project Manager for the city of Riverside CJ great to see you. >> Thank you, hi! >> So you represent a whole slew of mid-sized US cities, so how big is Riverside for people that aren't familiar? >> We serve 120,000 customers so we're not too small, but we're definitely not as big as some of the other cities. >> Right and then as we said before we turned on the cameras, you guys have a whole department for utilities, you have your own utility as well. >> Yes we do have a public utility division within the city, also an IT and public works, parks and recs like other cities as well. But we do have the utility, which is different than some of the stand along utilities, like LADWP for example. >> Right but it's good you were saying off camera that that gives you guys a nice revenue source, so it's a nice asset for the city to have. >> Yeah the utility is revenue generating department. >> Okay so what are you doing here at PI World, how are you guys using OSI software? >> So we started down PI back in August 2016, as an enterprise agreement customer, and at that time we really lacked visibility into our system so we needed something to help us gather the data and make sense of it, because we had data all over the place, and it was hard to answer simple questions it was hard to find simple data. And so we started down the PI journey at that time, and we basically used it like a data hub to aggregate data, turn that data into information, and then we disseminate it using dashboards. So PI Vision dashboards which used to be PI Coresight, as well as reports. >> So what were some of the early data sources that you leveraged, that you saw the biggest opportunity to get started, or yet even more importantly your earliest successes where'd your early success come from? >> So our very first work group that we worked with was our Water Operations and our Water SCADA team. >> Seems to be a pattern here a lot of water talk here at OSIsoft. >> Yeah I'll talk about electricity too. But we started on water and the first thing we did was implement their data, it was called a Water Operations dashboard, and they were doing it manually in Excel, and it would take a staff person over eight hours to do it. And they would do it the next day for the previous day data. So imagine how opposite of real time that is right? So we integrated that data with PI. >> And how many data elements? How big is the spreadsheet this poor person is working on? >> So the Water SCADA tags that we brought in were near 1500 tags, so you imagine that much data and calculations with over 1500 calculations behind it. So it was a ton of effort. >> Right. >> And a huge quick win for them! So it's saved staff time, they now have actual intelligence, real time data, the managers get alerts to their phones about the status of wells, and so it was really helpful to that work group. So that one was one of our first and earliest wins on PI. >> Was it a hard sell? To those people to use it? It wasn't because we did find a champion in that group, someone that would help us. Actually the manager he was very interested in technology and automation. And they understood that even though it would be a time investment up front, it would save them a ton of time in the long run, for the rest of the year. And so one of the things that helped us get buy-in early on is that we used an Agile approach. So we would tell the manager, I only need you for five weeks. I need you and your staff for five weeks, and then you don't have to talk to us anymore. We will deliver the product in five weeks, we will do all the work, but if you could give us five weeks of your time, then you could have all your time back the rest of the year. And that helped us get buy-in from the managers and a commitment, because they can identify with okay just five weeks. >> Right so those were probably the operational folks, what about on the IT folks how was getting buy-in from the IT folks? >> The funny thing is and the thing we did different is, we have a great relationship with IT, and we really forged a partnership with them early on, even from the very beginning when we were just reviewing the agreement. We got their buy-in early on to say okay, this is what we're thinking about doing, we want you to be part of the team, and we really built a partnership with this project so that it could be successful. So they work hand in hand with our PI implementation team every step of the way. They've been on this journey every step of the way with us. So we don't have some of the challenges that other companies that I hear are talking a lot about here with IT and it kind of being a bottleneck, we didn't have that same experience because we really worked hard up front to have the buy-in with them and really build a partnership with them, so that they're implementing PI with us. And another selling point with that is, we're using PI as a data hub or like a bus, a data bus essentially. So for them it's good because we're saying look we're only going to have this point to point system, instead of having all of these individual points we're only going to connect to one system, which will be easier for them to manage and maintain, and we'll instruct staff to go to PI to get the data. So that's a selling point for IT it's more secure, it's more manageable. >> And did you use an outside integrator, or did you guys do it all in house? >> Our implementation team is a combination of in house staff and a consulting firm as well. >> And then it's curious 'cause then you said once you add all the data it's kind of a data bus, how long did it take for somebody to figure out hmmm this is pretty cool maybe there's data set number two, data set number three, data set number four? >> So right after our first six week implementation, we rolled out a new implementation every four to six weeks. >> Every four to six weeks? >> Yeah so we did a sprint cycle the whole first year, and actually the whole second year we're currently in right now, and so we touched a different work group every single time, delivering a new solution to them. So we picked up a lot of traction so much that now, other departments in the city want it, public works is asking for it, the city manager's office so it's really picking up some good buzz, and we're kind of working our way down discussion of smart city talks, and seeing how PI can support smart city, big data advanced analytic initiatives at the city. >> So what are some of the favorite examples of efficiency gains, or savings that department A got that now department B sees and they want to get a piece of that what are some of your favorite success stories? >> I would say two of mine, I shared one on the big stage yesterday about the superpower I talked about our operations manager, who started receiving actionable intelligence overnight. And he got an alert around midnight, and he called his operator and said hey, what's going on with that well? And the operator said very puzzled, how do you know that there's something going on with this well? And he replied and said because I have superpowers. And so his superpower was PI, and that's one of my favorite stories because it's just simple and it resonates with people, because he is receiving alerts and push notifications that he never had before to his mobile device at home. So that's a huge win. >> Was the operator tied in to that same notification, or did that person know before the operator? >> The manager knew before the operator. So the operator didn't know about PI at the time and we had just rolled it out. And so the manager was just kind of testing it and adopting it, and so it was kind of like he had a leg up a little bit and they were confused like how do you know you're at home? >> Man: Right. >> He's like I have superpowers. (laughing) It's probably my funniest and best story, and one that I always tell because it helps everyone, no matter if it's an executive to a field person, really understand the power behind PI. I think another one if I had to pick another example of a win that I think was powerful is, our work order and field map. So we have our field crews right now that have a map, that's powered from our work order and asset management system pushing data to PI, which then pushes it to Esri through the PI integrator, and they're out using it in the field and it helps them route their work, they can see where their workers are, they can see customer information. And that map is really changing the way the field crews work. So imagine a day before this system where, they would go in and have to print every work order from the system. And not all asset management systems are really user friendly. They're kind of archaic a little clunky, so I won't say the name of our system. >> And doesn't work well if there's a change right? >> Yeah and they're not really mobile friendly. So that's part of the challenge, but because of that now public works wants that map, parks and rec every department that has field forces, they want something similar so that they can get all the data from all the other systems in one app in one location on their device. >> And do you find that's kind of a system pattern, where often department A needs very similar to what department B needed with just a slight twist? So it's pretty easy to make minor modifications to leverage work across a bunch of different departments? >> Absolutely a lot of work groups are similar, maybe a little different like you said, but especially those that have field forces. Sometimes it makes it easy to sell it to the next group, it's like look this is what we've done, is this something that you kind of need? Or what would you need differently? Like we've developed field collection tools. That's easy to replicate. Once you see it it's easy to say you know what that works but I need it to say this and I need it to say this. If you just show them a white paper, it's hard for them to say this is what I need. Most people just don't know, but it's easy once you see a suit to say oh I don't like that tie I don't like that shirt, I don't like those pants. >> But something close. >> Yeah but something like that right? So that's the benefit once you start having a solution to easily modify and reproduce. And then the good thing about Agile, you're running sprints so you're learning every sprint. You're kind of learning as you go, and you're able to refine it and refine it and make the process that much better. >> Right. On the superpower thing employee retention is a challenge, getting good people is a challenge, I'm just curious how that impacts the folks working for you, that now suddenly they do have this new tool that does allow them to do their job better, and it's not just talk it's actually real and gave that person a head up on the actual operation person sitting on the monitor devices. So as it proliferates what is the impact on morale, and are more people rising up to say hey, I want to use it for this I want to use it for that. >> Yeah we are getting a lot of interest, and I think the challenge is, and I talked about this a little bit during my session, is change management and culture. Some people see automation and technology as sometimes a threat because of job security, or the I've always done it this way type of mentality. >> Man: Never a good answer. >> Right but once you kind of get them to see that we're just automating your process to make it better so that you can do cooler and better things, so that you can actually analyze the data instead of inputting data. So you can actually solve problems versus spending all your time trying to identify the data and collect information. So staff are starting to see the value, and after the first year and a half, we've gotten a lot of traction. I don't really have to sell it as much, it's now such a huge part of our culture that the first question when we want to implement a new system is does that integrate with PI? I don't even have to ask them. Everyone else is asking well have you thought about using PI for that? So we always kind of look to PI first to say, can we create this solution in PI? And then if not we look at other solutions and if we're looking at other solutions we say, does that solution integrate with PI? So that's become part of our norm to make sure that it plays nice with what we're calling our foundational technology which is PI. >> Right so you talked a lot about departments. Is there kind of a cross-department city level play that you're rolling data and or dashboards into something that's a higher level than just the department level? >> Yeah so far the only thing that we have done that's kind of cross divisional not just in one division, is our overtime dashboards. So we recently created overtime dashboards throughout the entire city so that executive level department heads have visibility into overtime, which just gives them trends so that they can know what departments are receiving the most overtime? Is that overtime associated with what type of cause? Was it something outside of our control? Was it a planned overtime? And then most importantly where we're trending. Where are we on track to be by the end of the year, given our current rate so that they can be proactive in making changes. Do we need to do something different? Do we need to hire more people in this department? Do we have too many people in this department? Can we make shifts? So it's giving that level of visibility, and that's a new rollout that we just have completed, but it's something that we're already seeing a lot of interest in doing more of. Cross divisional things so that the city manager's office and that level has more view into the whole city. >> Right well CJ it sounds like you're doing a lot of fun stuff down at Riverside. >> Woman: We are we are! >> And you can never save enough water in California, so that's very valuable work. >> Woman: That's true! >> Well thanks for taking a minute and sharing your story, I really enjoyed it. >> Thank you for having me. >> Absolutely she's CJ Smith I'm Jeff Frick, you're watching theCUBE from OSIsoft PI World 2018 in San Francisco, thanks for watching. (upbeat music)

>> Narrator: Live from San Francisco, it's the CUBE. Covering Samsung Developer Conference 2017, brought to you by Samsung. >> Okay, welcome back everyone. We are here live with the CUBE coverage where Cloud Native and the SmartThings Conference from Samsung Developer Conference. I'm John Furrier, the founder, the co-founder of SiliconANGLE Media. Co-host of the cube here with Redg Snodgrass, who's the chairman of ReadWrite and ReadWrite Labs. >> Hello everybody. >> Also been an entrepreneur, he's done the Wearable World events, done a lot of things in tech, riding the waves. You seen them, a lot of action going on, Redg. Want to get your the thoughts as we wrap up day one of two days of wall-to-wall coverage of the cubes, Samsung Developer Conference, a lot going on. You know Samsung, they're trying to play their best hand that possible. Obviously, they're not going to come out and say, We're not really ready for primetime, for the cloud. But the reality is, they're not ready for primetime for the cloud and IoT. However, huge strides in positioning, messaging, and the self awareness of their stove pipes. They are series of stove pipes that they've recognized, We've got to make this a 2.0 Bixby that crosses across all of Samsung, open up IoT. >> Redg: Which I thought was great. >> Open ecosystem, everything else, to me, is a work in progress, kind of, cover the, hide the ball, a little bit, I mean, what's your thoughts? Do you agree or what's your reaction? >> Oh man, I was on a panel earlier today. And somebody was like, oh, this is great. And I wanted to go back to, back when we did the open API service with Alcatel-Lucent, when we roll out all this stuff for the telcos. I mean, it's just, it's a lot of hype, initially. But what I do like about it is it seems like there's a dogged commitment to creating all the different documentations necessary and bringing that in, I mean, if they really put the full marketing weight behind it, this could get really interesting really fast. I mean, they own almost every device in your home already. >> Well, I said the word hide-the-ball. Maybe I should take a step back and not be too harsh. What I mean by that is, they're not hiding the ball on purpose, I think they're, by design, and I think Greg mentioned this earlier. Greg Narain said, they're doing it by design. And I think that that's a good call. SmarterThings is a good positioning because it highlights multiple devices and connecting it together. I think if they played the data card and the cloud too much, they would've overplayed their hand, and it's not needed. I mean, do you think it's needed? I mean, I don't think it's needed. >> Well, one of the biggest problems with IoT right now is that you have multiple different silos creating data. And then all those data silos have to figure out how to come together and talk about it. I mean, it seems like they're taking a step out, and saying, hey, we want to build that solution. Which is great, I'm more interested in the orchestration between different OSs, like, how are they really going to do that? Because it, we talked a lot about, when you build one of these ecosystems, you're really just building an economy. And the more open that you let your economy, right, the more business models come in, the more people that can be there. And so, if we were to start thinking about these OSs as real economies, like what do you need to have economy work? >> Well, I think this is why, we were talking earlier, I think that you had a good point. I think that validates what I'm thinking out loud here, which is, why play the data card. They don't need to because it's still open-book. They still got to figure it out, and that's not a bad thing. They play with their best hand, which is the consumer hand. >> Redg: It's consumerism is where they're at >> The devices are awesome, the screen on the phones are phenomenal, they got TVs. They got a little bit of a family hub going on with the living room, kitchen thing, with the refrigerators. That's IoT, they got healthcare because it's a device issue. So they're working their way from the consumer edge into the industrial edge. Now, if you're in the IT world, you have security problems. So most people that we talk to, at the humans, they say, hey John, my plate is full, I got to staff up my DevOps and my application developers. I got to unbolt security from my IT department, make that report to the board as a profit center now. And I got all this machine learning and Cloud Ops, and you want me to do what? Like, instrument my entire factory with this IoT thing? So people are holding the brakes. >> Well, I mean think about it. Every day, right, you're confronted with another executive that has like fallen on a sword of a major security hack, a major security issue. And so, as an executive of a major like business unit, with a technology group in front of you, you're sitting there making all these decisions every day. And it used to, you used to come and say, okay, we're going to make decisions every eight, nine months. And you have this big waterfall thing in front of you. And you know that, from your vendors, that. >> John: It's predictable >> Everything was predictable, and now it's like, oh man, I got to get into this Google Glass stuff, and I've got, no, now it's wearables, and wearables, that doesn't work, I need my IoT infrastructure stuff. And so we're moving the court, you know, away from all these CIO, CTOs consistently of what they need to think about next. >> It's interesting, if you look at the stack, go back to the old 80s OSI model, you got the lower level stack, middleware, and then application stacks. If you follow the data, and the networks, and the packets, how it moves, you can almost see the trends, batch versus real time. And I think what we've seen in the big data world, in data sciences, which can be analytics, obviously specialty industry. But the role of data and realtime, self-driving cars, really highlights this really huge wave coming, which is how that people dealt with data and software, the relationship between software and data was different. You store it in a database, build the database, call the database, get the data out, load it in, slow, monolithic, siloed. But now you have data that you need in really low latency at any given time, in any different app, from any different database, in less than a millisecond how do you do that. >> Well, think of it. >> John: That takes intelligence. >> About two years ago, I had a great conversation with a big packet moving company that managed most of the packet movement for most of the internet. And we were talking about, what does it look like per person in the US in the next like three or four years? And it could be up to a petabyte a day at a per person. Now that sounds awesome because if you look at all the different like videos we watch, it's like, oh, that's great, really cool flying car. You know, connecting windows, no one's really doing the math on that. And if it's a petabyte per day per person, like in the US a year even, or you know. I could see models where it could be a month. Think about what that does to the network load. We just don't have the math to be able, you know, possibility to handle that. >> This is why the decentralization with Blockchain is interesting. Even though Blockchain is hyped up, I think it's fundamental to the internet, as this Dr. Wong from Alibaba, who told me that last week. He said it was like a TCP/IP, I agree with him because you have distributed computers, which we know about. We've been there, done that, but now you got decentralized and distributed, two different concepts at the same time. That's a fundamental paradigm shift. >> Well, I mean it's just, so, I mean, you got to. >> It's intoxicating to think about what that disrupts. >> No, no, I love it, I mean, honestly, I've fallen in love with narrow band networks the last week. For some reason, I'm the weirdest person on the planet. Because it's such a solution for security. It's such a solution for a lot of this back calling and data that we're going to have. It'll be interesting to look at, but when you think about the pure math on this. >> John: Are you back calling data or are you back calling compute? >> Oh, well it's so. >> That's a different conversation. The trend is, don't move the data. Throw the compute at it because compute is, this is an architectural renaissance happening, people are re-imagining. >> How many, how many startup. >> In global infrastructure. >> Execs can even like draw architecture? Right, with all the lame startups, I mean, when was the last time you saw like somebody pitch. When they came to pitch, it's like, let me talk about my architecture. >> John: That should be the first slide. >> It should be the slide that you talk about as an executive and everything, I don't see. >> If he can't get on the whiteboard. >> Startups deliver architecture. >> If you can't get on the whiteboard and lay out an architecture on fundamentally the core engine of your technology, you shouldn't get funded. >> Well, so that is a major issue that's happening right now because I do think that we have this group think where we've disallowed a lot of R&D thinking. We don't do longterm R&D before we get a product to market. And now, like all. >> John: Sometimes you can't. Sometimes you have to sprint out and put a stake in the ground and iterate. >> Think about all of the connected device product. How do you test the connected device product to scale? Right, I mean the iPhone, you know Samsung, everybody has all these devices out there, they're getting this data, it's coming in they can actually iterate on that product and make decisions, right? >> Well, that brings up a good point. We saw this at the Cube at VMWorld. For the first time we heard people grumbling in the hallways like, you know, I love the ENC tries, but they just haven't tested this use case. And the use case was a new workload that had unique characteristics. In this case they needed low latency. It was an edge device, so it was mandatory to have no latency with all this was trickling data in. But in this case, they had set up their virtual SAN in a tiered basis. And they needed a certain hardware configuration with vSAN. And they've never tested the hardware stack with the software stack. So it's just one of those things that the hardware vendor just never imagined, you can't QA the unknown. So this is where I'd see Samsung doing things like in-chip and seeing what Intel's doing with some of their FPGA stuff. You can see that these infrastructure guys got to bring that DevOps concept to the consumer world. >> Redg: Oh, it's going to be so hard. >> Which is programming the. >> Redg: So hard. >> The hardware at will. >> Yeah, well. >> John: Like the cloud DevOps ethos. What do you think of that? >> Yeah, no, no, no, look, I mean, I'm such a big fan of being able to get your product in people's hands, to be able to see the use cases, develop them out and push that forward. You know, big corporations can do that. You have 10 iterations of almost every iPhone right now, with thousands of engineers iterating on it. So when you look at like the competitor, which is your device right now, versus every other piece of IoT technology that isn't been perfected or anything. Our biggest issue is we're driven by the success of the smartphone for every other piece of technology today. And that's, that makes it hard to drive adoption for any other devices. >> So I get your thoughts on this, 'cause we wrap up day one. Obviously, let's talk about the developers that they're targeting, okay. >> Okay. >> The Samsung developers that they're targeting is the same kind of developers that Apple's targeting. Let's just call it out, however, you see voice-activated touch, you're seeing the services tools, now they're bringing in an IoT. You're not hearing Apple talk about IoT. This is unique, you got Google onstage, wink, wink, hey, everybody we're here, we're Google, Android, coming together. What is in the mind of the developer in the Samsung ecosystem right now, what's your take on it, what's the psychology of that developer? >> I built an app at one point in time. It was dating app a long time ago, right, with some other guys, they built it, I was just the mouth. It's called Scout and we were on the Simian platform, and the iPhone, and we were on web, we were on mobile web. And in the iPhone app store, all with one engineer. And it was really hard because we had real-time chat. It was just so much crazy things. At the end of the day, what always matters is, again, you're building economies, you're not building fun playgrounds or anything else like that. And if your economy is, your platform is the easiest to use, it has the capabilities and advantages that are the norm, right, you'll win. Bass Diffusion is great it's this guy out here, he won a Nobel prize, but what Bass Diffusion says, in order for you to win in a market, you need two things, imitation and innovation. Imitation, for instance, in TVs, is your TV black and white, is it color. As things move up, innovation eventually overtakes, and always becomes innovation. So when you look at like what's needed in market, the platform that is the easiest to use, the platform that has the most capable imitative qualities, it's just very easy for you to push things to market universally from OS to OS, along with certain pieces of innovation around business models, certain API capabilities that may make it easier for them to deliver revenues. If those are the things that are delivered, that we see pushed out, a good blend of imitation and innovation, the win. It's that person that actually can deliver it. >> Well, we're seeing gaming in entertainment really driving change, Netflix earnings just came out. They blew it away again, you're seeing the cord cutters are clearly there. >> So much for Disney, right? >> E-commerce, yeah, I mean, Amazon's still got to make some moves too, even though they were still winning. No one's really falling out of the chair for Prime. I mean, no, I don't know a lot of people who rigorously turn on Prime, they shop on Prime, but not necessarily watching any entertainment. So I'm a little critical of Amazon on that. But, then again, but Amazon's doing the right thing. Netflix, Amazon, YouTube, you're seeing a culture of digital entertainment shifting. E-commerce is shifting, and now you got web services. I think Amazon encapsulates, in my mind, a great strategy, retail and services, but if you extend that out to the rest of the world, voice-activated apps, you can blend in commerce entertainment, you can replicate Amazon. I mean, they could replicate everything out there in the open. >> Amazon is so good at understanding where they fit in the stack and then, pushing the edge case further and further and further along. They're really brilliant, versus like VMware that's like, oh man, we can make apps, no problem. They went to make apps, and it didn't work out so well, they're great with VMs, so. >> John: They're great with operators in the enterprise, not so much with DevOps. >> No, no, no, no, and it's. >> They got pivotal for that now. Michael Dell bought everyone up. >> Yeah, exactly. It's understanding where you fit in the stack and being able to take advantage of it strategically. I mean, like I said, I think Samsung's positioned really well, I mean, I wouldn't have come and hung out with everybody if I was like, ah, I'm going to be bored all day. There's a lot of really exciting things. >> We got a lot of eye candy, no doubt about it. I love their TVs, love their screens. The new Samsung phone, is spectacular, you what I mean. >> I'm pretty ecstatic. >> It was the first phone that wanted me to get transferred off my iPhone. And I ended up getting the little junior Samsung here, but. >> Oh no, well it'll be interesting as they start to connect their platform together as all a lot of these other developers start pushing the pieces of their strategy together. Remember, it's like whenever you throw a strategy out here like this, it's like you have a big puzzle with a lot of empty pieces. >> I mean, the question I have for you is, let's just close out the segment. What do you think, what area should Samsung really be doubling down on or peddling faster, I should say. What should be developing faster? Is it the open APIs, is it the cloud? And they got to get the open ecosystem going, in my opinion. That's my take, what do you think they should be working on the most right now? >> Yeah, I mean like look, cloud is going to be really, really, there's a lot of competitors out in cloud. There's a lot of multiple, there's a lot of choices, right. Where I've seen them like really do well, I'll go back to the fact that I firmly believe that Google never really monetized the Android that Samsung did that a lot better. And so, by looking at the different points in the market, where they're good, I mean, their ecosystem is solid. I mean, yes, I mean it seems like the sexy thing is Apple, but I've talked to several developers, and I know where they make their money, and they do a strong amount of revenue, if not equivalent to where the iPhone is, at least from what I've heard so far. >> The android market share it's not shabby at all. >> Not, so. >> Damn good. >> So they've, they've been able to do this, like, from that, taken that Android stack, applying that imitation and innovation on top of it, fascinatingly so, I wouldn't count them out for this. And I'm pretty encouraged to see all the other aspects, but I like the ecosystem built out too. >> Redg Snodgrass, ReadWrite Labs, quick plug for you. What's going on in your world? Got some recent activities happening, please share update. >> So, yeah it's great, so we just launched our IOT revolution event series where we look at the atomic unit of different markets. And what that means is, we find the real buyers and sellers, a lot like what Debbie Lann, who I love, did. And we look at the buyers and sellers together, along with the top series A startups, all around newsworthy issues. And so, whatever it's like, is it hacking and Russia. You know, then we'll get cybersecurity experts up, and we'll talk about those issues from an executive point of view. And that's the thing that's making me most excited because I get to have all these conversations with people. It will be on video, onstage, November 13th, is the first one, it's a private event, but we'll work out anybody. >> Where's it going to be? >> It'll be in San Francisco, around 100 Broadway. So it's kind of a quiet thing, but I'd love for everybody to come if you're interested. >> It's a quiet thing but I want everyone to come. It was, not going there, too many people are going. >> It's like my parties, right? >> It's like a Yogi Berra. Well, thanks for coming out, appreciate, wrapping up day one of coverage The Cube. This is Samsung Developer Conference 2017. Hashtag SDC2017, that's what they're calling it. Lot of great guests today go to YouTube.com/siliconangle for all the great footage. And also check the Twitter sphere, lot of photos. And shout-out to Vanessa, out there has like helped us set everything up. Appreciate it and great to the team. That's day one wrap up, thanks for watching. (upbeat music)