>>from around >>the globe. It's >>the cube presenting future >>Cloud one >>event. A >>world of opportunities >>brought to you by Cisco. >>Okay. We're here with costume. Does, who is the Senior Vice President, General Manager of Cloud and compute at Cisco And VJ Venugopal, who is the Senior Director for Product management for Cloud, compute at Cisco. KTV J Good to see you guys welcome. >>Great to see you. Dave >>to be here. >>Katie. Let's talk about cloud. You. And I, last time we're face to face was in Barcelona where we love talking about cloud. And I always say to people look, Cisco is not a hyper scaler, but the big public cloud players, they're like giving you a gift. They spent almost actually over $100 billion last year on Capex. The big four. So you can build on that infrastructure. Cisco is all about hybrid cloud. So help us understand the strategy. There may be how you can leverage that build out and importantly what a customer is telling you they want out of hybrid cloud. >>Yeah, no, that's that's that's a perfect question to start with Dave. So yes, so the hybrid hyper scholars have invested heavily building out their assets. There's a great lot of innovation coming from that space. Um there's also a great innovation set of innovation coming from open source and and that's another source of uh a gift, in fact the I. T. Community. But when I look at my customers, they're saying, well how do I in the context of my business, implement a strategy that takes into consideration everything that I have to manage um in terms of my contemporary work clothes, in terms of my legacy, in terms of everything my developer community wants to do on devops and really harness that innovation that's built in the public cloud, that built an open source that built internally to me and that naturally leads them down the path of a hybrid cloud strategy. And Siskel's mission is to provide for that imperative, the simplest, more power, more powerful platform to deliver hybrid cloud. And that platform uh is inter site, we've been investing in Inner side, it's a it's a SAS um service um inner side delivers to them that bridge between their estates of today. There were clothes of today, the need for them to be guardians of enterprise grade resiliency with the agility uh that's needed for the future. The embracing of cloud, Native of new paradigms of deVOPS models, the embracing of innovation coming from public cloud and an open source and bridging those two is what inner side has been doing. That's kind of, that's kind of the crux of our strategy. Of course, we have the entire portfolio behind it to support any any version of that, Whether that is on prem in the cloud, hybrid, cloud, multi, cloud and so forth. >>But but if I understand it correctly from what I heard earlier today, the inter site is really a linchpin of that strategy, is it not? >>It really is and may take a second to uh to totally familiarize those who don't know inner side with what it is. We started building this platform quite a few years back and we we built a ground up to be an immensely scalable SAs super simple hybrid cloud platform and it's a platform that provides a slew of service is inherently. And then on top of that there are suites of services, the sweets of services that are tied to infrastructure, automation. Cisco, as well as Cisco partners, their suite of services that have nothing to do with Cisco um products from a hardware perspective and it's got to do with more cloud orchestration and cloud native and inner side and its suite of services um continue to kind of increase in pace and velocity of delivery video. It's just over the last two quarters we've announced a whole number of things will go a little bit deeper into some of those, but they span everything from infrastructure automation to kubernetes and delivering community than service to workload optimization and having visibility into your cloud estate. How much it's costing into your on premise state into your work clothes and how they're performing. It's got integrations with other tooling with both Cisco Abdi uh as well as non Cisco um, assets. And then and then it's got a whole slew of capabilities around orchestration because at the end of the day, the job of it is to deliver something that works and works at scale that you can monitor and make sure is resilient and that includes that. That includes a workflow and ability to say, you know, do this and do this and do this. Or it includes other ways of automation, like infrastructure as code and so forth. So it includes self service that so that expand that. But inside the world's simplest hybrid cloud platform, rapidly evolving rapidly delivering new services. And uh, we'll talk about some more of those days. >>Great. Thank you. Katie VJ Let's bring you into the discussion. You guys recently made an announcement with the ASCII corp. I was stoked because even though it seemed like a long time ago, pre covid, I mean in my predictions post, I said, ha she was a name to watch our data partners. Et are you look at the survey data and they really have become mainstream. You know, particularly we think very important in the whole multi cloud discussion. And as well, they're attractive to customers. They have open source offerings. You can very easily experiment, smaller organizations can take advantage, but if you want to upgrade to enterprise features like clustering or whatever, you can plug right in. Not a big complicated migration. So a very, very compelling story there. Why is this important? Why is this partnership important to Cisco's customers? >>Mhm. Absolutely. When the spot on every single thing that you said, let me just start by paraphrasing what ambition statement is in the cloud and compute group right ambition statement is to enable a cloud operating model for hybrid cloud. And what we mean by that is the ability to have extreme amounts of automation orchestration and observe ability across your hybrid cloud idea operations now. Uh So developers >>and applications >>team get a great amount of agility in public clouds and we're on a mission to bring that kind of agility and automation to the private cloud and to the data centers. And inter site is a quickie platform and lynchpin to enable that kind of operations. Uh, Cloud like operations in the in the private clouds and the key uh as you rightly said, harsher Carp is the, you know, they were the inventors of the concept of infrastructure at school and in terra form, they have the world's number one infrastructure as code platform. So it became a natural partnership for Cisco to enter into a technology partnership with Harsher Card to integrate inter site with hardship cops, terra form to bring the benefits of infrastructure as code to the to hybrid cloud operations. And we've entered into a very tight integration and uh partnership where we allow developers devops teams and infrastructure or administrators to allow the use of infrastructure as code in a SAS delivered manner for both public and private club. So it's a very unique partnership and a unique integration that allows the benefits of cloud managed. I see to be delivered to hybrid cloud operations and we've been very happy and proud to be partnering with Russia Carbonara. >>Yeah, telephone gets very high marks from customers. The a lot of value there, the inner side integration adds to that value. Let's stay on cloud Native for a minute. We all talk about cloud native cady was sort of mentioning before you got the the core apps uh you want to protect those, make sure their enterprise create but they gotta be cool as well for developers. You're connecting to other apps in the cloud or wherever. How are you guys thinking about this? Cloud native trend. What other movies are you making in this regard? >>I mean cloud Native is there is one of the paramount I. D. Trends of today and we're seeing massive amounts of adoption of cloud native architecture in all modern applications. Now. Cloud native has become synonymous with kubernetes these days and communities has emerged as a de facto cloud native platform for modern cloud native app development. Now, what Cisco has done is we have created a brand new SAs delivered kubernetes service that is integrated with inter site, we call it the inter site community service for a. Ks and this just gave a little over one month ago now, what interstate Kubernetes service does is it delivers a cloud managed and cloud delivered kubernetes service that can be deployed on any supportive target infrastructure. It could be a Cisco infrastructure, it could be a third party infrastructure or it could even be public club. But think of it as kubernetes anywhere delivered, as says, managed from inside. It's a very powerful capability that we've just released into inter site to enable the power of communities and cognitive to be used to be used anywhere. But today we made a very important aspect because we have today announced the brand new Cisco service mess manager. The Cisco service mesh manager, which is available as an extension to I K s are doing decide basically we see service measures as being the future of networking. Right in the past we had layer to networking and layer three networking and now with service measures, application networking and layer seven networking is the next frontier of of networking. But you need to think about networking for the application age very differently, how it is managed, how it is deployed, it needs to be ready, developer friendly and developer centric. And so what we have done is we've built out an application networking strategy and built out the service match manager as a very simple way to deliver application networking through the consumers, like like developers and application teams. This is built on an acquisition that Cisco made recently of Banzai Cloud. And we've taken the assets of Banzai Cloud and deliver the Cisco service mash Manager as an extension to KS. That brings the promise of future networking and modern networking to application and development gives >>God thank you BJ. And so Katie, let's let's let's wrap this up. I mean, there was a lot in this announcement today, a lot of themes around openness, heterogeneity and a lot of functionality and value. Give us your final thoughts. >>Absolutely. So couple of things to close on. First of all. Um, inner side is the simplest, most powerful hybrid cloud platform out there. It enables that that cloud operating model that VJ talked about but enables that across cloud. So it's sad, it's relatively easy to get into it and give it a spin so that I'd highly encouraged anybody who's not familiar with it to try it out and anybody who is familiar with it to look at it again, because they're probably services in there that you didn't notice or didn't know last time you looked at it because we're moving so fast. So that's the first thing, the second thing I close with is, um we've been talking about this bridge that's kind of bridging, bridging uh your your on prem your open source, your cloud estates. And it's so important to to make that mental leap because uh in past generation we used to talk about integrating technologies together and then with Public cloud, we started talking about move to public cloud, but it's really how do we integrate, how do we integrate all of that innovation that's coming from the hyper scale is everything they're doing to innovate superfast. All of that innovation is coming from open source, all of that innovation that's coming from from companies around the world including Cisco. How do we integrate that to deliver an outcome? Because at the end of the day, if you're a cloud of Steam, if you're an idea of Steam, your job is to deliver an outcome and our mission is to make it super simple for you to do that. That's the mission we're on and we're hoping that everybody that's excited as we are about how simple we made that. >>Great, thank you a lot in this announcement today, appreciate you guys coming back on and help us unpack you know, some of the details. Thanks so much. Great having you. >>Thank you. Dave. >>Thank you everyone for spending some time with us. This is Dave Volonte and you're watching the cube, the leader in tech event >>coverage. >>Mm mm.

>>mhm, mm. All right. Mhm. Mhm, mm mm. Mhm. Yeah, mm. Mhm. Yeah, yeah. Mhm, mm. Okay. Mm. Yeah, Yeah. >>Mhm. Mhm. Yeah. Welcome to future cloud made possible by Cisco. My name is Dave Volonte and I'm your host. You know, the cloud is evolving like the universe is expanding at an accelerated pace. No longer is the cloud. Just a remote set of services, you know, somewhere up there. No, the cloud, it's extending to on premises. Data centers are reaching into the cloud through adjacent locations. Clouds are being connected together to each other and eventually they're gonna stretch to the edge and the far edge workloads, location latency, local laws and economics will define the value customers can extract from this new cloud model which unifies the operating experience independent of location. Cloud is moving rapidly from a spare capacity slash infrastructure resource to a platform for application innovation. Now, the challenge is how to make this new cloud simple, secure, agile and programmable. Oh and it has to be cloud agnostic. Now, the real opportunity for customers is to tap into a layer across clouds and data centers that abstracts the underlying complexity of the respective clouds and locations. And it's got to accommodate both mission critical workloads as well as general purpose applications across the spectrum cost, effectively enabling simplicity with minimal labor costs requires infrastructure i. E. Hardware, software, tooling, machine intelligence, AI and partnerships within an ecosystem. It's kind of accommodate a variety of application deployment models like serverless and containers and support for traditional work on VMS. By the way, it also requires a roadmap that will take us well into the next decade because the next 10 years they will not be like the last So why are we here? Well, the cube is covering Cisco's announcements today that connect next generation compute shared memory, intelligent networking and storage resource pools, bringing automation, visibility, application assurance and security to this new decentralized cloud. Now, of course in today's world you wouldn't be considered modern without supporting containers ai and operational tooling that is demanded by forward thinking practitioners. So sit back and enjoy the cubes, special coverage of Cisco's future cloud >>From around the globe. It's the Cube presenting future cloud one event, a world of opportunities brought to you by Cisco. >>We're here with Dejoy Pandey, a VP of emerging tech and incubation at Cisco. V. Joy. Good to see you. Welcome. >>Good to see you as well. Thank you Dave and pleasure to be here. >>So in 2020 we kind of had to redefine the notion of agility when it came to digital business or you know organizations, they had to rethink their concept of agility and business resilience. What are you seeing in terms of how companies are thinking about their operations in this sort of new abnormal context? >>Yeah, I think that's a great question. I think what what we're seeing is that pretty much the application is the center of the universe. And if you think about it, the application is actually driving brand recognition and the brand experience and the brand value. So the example I like to give is think about a banking app uh recovered that did everything that you would expect it to do. But if you wanted to withdraw cash from your bank you would actually have to go to the ATM and punch in some numbers and then look at your screen and go through a process and then finally withdraw cash. Think about what that would have, what what that would do in a post pandemic era where people are trying to go contact less. And so in a situation like this, the digitization efforts that all of these companies are going through and and the modernization of the automation is what is driving brand recognition, brand trust and brand experience. >>Yeah. So I was gonna ask you when I heard you say that, I was gonna say well, but hasn't it always been about the application, but it's different now, isn't it? So I wonder if you talk more about how the application is experience is changing. Yes. As a result of this new digital mandate. But how should organizations think about optimizing those experiences in this new world? >>Absolutely. And I think, yes, it's always been about the application, but it's becoming the center of the universe right now because all interactions with customers and consumers and even businesses are happening through that application. So if the application is unreliable or if the application is not available is untrusted insecure, uh, there's a problem. There's a problem with the brand, with the company and the trust that consumers and customers have with our company. So if you think about an application developer, the weight he or she is carrying on their shoulders is tremendous because you're thinking about rolling features quickly to be competitive. That's the only way to be competitive in this world. You need to think about availability and resiliency. Like you pointed out and experience, you need to think about security and trust. Am I as a customer or consumer willing to put my data in that application? So velocity, availability, Security and trust and all of that depends on the developer. So the experience, the security, the trust, the feature, velocity is what is driving the brand experience now. >>So are those two tensions that say agility and trust, you know, Zero Trust used to be a buzzword now it's a mandate. But are those two vectors counter posed? Can they be merged into one and not affect each other? Does the question makes sense? Right? Security usually handcuffs my speed. But how do you address that? >>Yeah that's a great question. And I think if you think about it today that's the way things are. And if you think about this developer all they want to do is run fast because they want to build those features out and they're going to pick and choose a piece and services that matter to them and build up their app and they want the complexities of the infrastructure and security and trust to be handled by somebody else is not that they don't care about it but they want that abstraction so that is handled by somebody else. And typically within an organization we've seen in the past where this friction between Netapp Sec ops I. T. Tops and and the cloud platform Teams and the developer on one side and these these frictions and these meetings and toil actually take a toll on the developer and that's why companies and apps and developers are not as agile as they would like to be. So I think but it doesn't have to be that way. So I think if there was something that would allow a developer to pick and choose, discover the apis that they would like to use connect those api is in a very simple manner and then be able to scale them out and be able to secure them and in fact not just secure them during the run time when it's deployed. We're right off the back when the fire up that I'd and start developing the application. Wouldn't that be nice? And as you do that, there is a smooth transition between that discovery connectivity and ease of consumption and security with the idea cops. Netapp psych ops teams and see source to ensure that they are not doing something that the organization won't allow them to do in a very seamless manner. >>I want to go back and talk about security but I want to add another complexity before we do that. So for a lot of organizations in the public cloud became a staple of keeping the lights on during the pandemic but it brings new complexities and differences in terms of latency security, which I want to come back to deployment models etcetera. So what are some of the specific networking challenges that you've seen with the cloud native architecture is how are you addressing those? >>Yeah. In fact, if you think about cloud, to me that is a that is a different way of seeing a distributed system. And if you think about a distributed system, what is at the center of the distributed system is the network. So my my favorite comment here is that the network is the wrong time for all distribute systems and modern applications. And that is true because if you think about where things are today, like you said, there's there's cloud assets that a developer might use in the banking example that I gave earlier. I mean if you want to build a contact less app so that you get verified, a customer gets verified on the app. They walk over to the ATM and they were broadcast without touching that ATM. In that kind of an example, you're touching the mobile Rus, let's say U S A P is you're touching cloud API is where the back end might sit. You're touching on primary PS maybe it's an oracle database or a mainframe even where transactional data exists. You're touching branch pipes were the team actually exists and the need for consistency when you withdraw cash and you're carrying all of this and in fact there might be customer data sitting in salesforce somewhere. So it's cloud API is a song premise branch. It's ass is mobile and you need to bring all of these things together and over time you will see more and more of these API is coming from various as providers. So it's not just cloud providers but saas providers that the developer has to use. And so this complexity is very, very real. And this complexity is across the wide open internet. So the application is built across this wide open internet. So the problems of discovery ability, the problems of being able to simply connect these apis and manage the data flow across these apis. The problems of consistency of policy and consumption because all of these areas have their own nuances and what they mean, what the arguments mean and what the A. P. I. Actually means. How do you make it consistent and easy for the developer? That is the networking problem. And that is a problem of building out this network, making traffic engineering easy, making policy easy, making scale out, scale down easy, all of that our networking problems. And so we are solving those problems uh Francisco. >>Yeah the internet is the new private network but it's not so private. So I want to go back to security. I often say that the security model of building a moat, you dig the moat, you get the hardened castle that's just outdated now that the queen is left her castle, I always say it's dangerous out there. And the point is you touched on this, it's it's a huge decentralized system and with distributed apps and data, that notion of perimeter security, it's just no longer valid. So I wonder if you could talk more about how you're thinking about this problem and you definitely address some of that in your earlier comments. But what are you specifically doing to address this and how do you see it evolving? >>Yeah, I mean, that's that's a very important point. I mean, I think if you think about again the wide open internet being the wrong time for all modern applications, what is perimeter security in this uh in this new world? I mean, it's to me it boils down to securing an API because again, going with that running example of this contact lists cash withdrawal feature for a bank, the ap wherever it's it's entre branch SAs cloud, IOS android doesn't matter that FBI is your new security perimeter. And the data object that is trying to access is also the new security perimeter. So if you can secure ap to ap communication and P two data object communication, you should be good. So that is the new frontier. But guess what software is buggy? Everybody's software not saying Cisco software, everybody's Softwares buggy. Uh software is buggy, humans are not reliable and so things mature, things change, things evolve over time. So there needs to be defense in depth. So you need to secure at the API layer had the data object layer, but you also need to secure at every layer below it so that you have good defense and depth if any layer in between is not working out properly. So for us that means ensuring ap to ap communication, not just during long time when the app has been deployed and is running, but during deployment and also during the development life cycle. So as soon as the developer launches an ID, they should be able to figure out that this api is security uses reputable, it has compliant, it is compliant to my to my organization's needs because it is hosted, let's say from Germany and my organization wants appears to be used only if they are being hosted out of Germany so compliance needs and and security needs and reputation. Is it available all the time? Is it secure? And being able to provide that feedback all the time between the security teams and the developer teams in a very seamless real time manner. Yes, again, that's something that we're trying to solve through some of the services that we're trying to produce in san Francisco. >>Yeah, I mean those that layered approach that you're talking about is critical because every layer has, you know, some vulnerability. And so you you've got to protect that with some depth in terms of thinking about security, how should we think about where where Cisco's primary value add is, I mean as parts of the interview has a great security business is growing business, Is it your intention to to to to add value across the entire value chain? I mean obviously you can't do everything so you've got a partner but so has the we think about Cisco's role over the next I'm thinking longer term over the over the next decade. >>Yeah, I mean I think so, we do come in with good strength from the runtime side of the house. So if you think about the security aspects that we haven't played today, uh there's a significant set of assets that we have around user security around around uh with with do and password less. We have significant assets in runtime security. I mean, the entire portfolio that Cisco brings to the table is around one time security, the secure X aspects around posture and policy that will bring to the table. And as you see, Cisco evolve over time, you will see us shifting left. I mean, I know it's an overused term, but that is where security is moving towards. And so that is where api security and data security are moving towards. So learning what we have during runtime because again, runtime is where you learn what's available and that's where you can apply all of the M. L. And I models to figure out what works what doesn't taking those learnings, Taking those catalogs, taking that reputation database and moving it into the deployment and development life cycle and making sure that that's part of that entire they have to deploy to runtime chain is what you will see. Cisco do overtime. >>That's fantastic phenomenal perspective video. Thanks for coming on the cube. Great to have you and look forward to having you again. >>Absolutely. Thank you >>in a moment. We'll talk hybrid cloud applications operations and potential gaps that need to be addressed with costume, Das and VJ Venugopal. You're watching the cube the global leader in high tech coverage. Mhm >>You were cloud. It isn't just a cloud. It's everything flowing through it. It's alive. Yeah, connecting users, applications, data and devices and whether it's cloud, native hybrid or multi cloud, it's more distributed than ever. One company takes you inside, giving you the visibility and the insight you need to take action. >>One company >>has the vision to understand it, all the experience, to securely connect at all on any platform in any environment. So you can work wherever work takes you in a cloud first world between your cloud and being cloud smart, there's a bridge. Cisco the bridge to possible. >>Okay. We're here with costume does, who is the Senior Vice President, General Manager of Cloud and compute at Cisco. And VJ Venugopal, who is the Senior Director for Product Management for cloud compute at Cisco. KTV. J. Good to see you guys welcome. >>Great to see you. Dave to be here. >>Katie, let's talk about cloud you And I last time we're face to face was in Barcelona where we love talking about cloud and I always say to people look, Cisco is not a hyper Scaler, but the big public cloud players, they're like giving you a gift. They spent almost actually over $100 billion last year on Capex. The big four. So you can build on that infrastructure. Cisco is all about hybrid cloud. So help us understand the strategy. There may be how you can leverage that build out and importantly what a customer is telling you they want out of hybrid cloud. >>Yeah, no that's that's that's a perfect question to start with. Dave. So yes. So the hybrid hyper scholars have invested heavily building out their assets. There's a great lot of innovation coming from that space. Um There's also a great innovation set of innovation coming from open source and and that's another source of uh a gift. In fact the I. T. Community. But when I look at my customers they're saying well how do I in the context of my business implement a strategy that takes into consideration everything that I have to manage um in terms of my contemporary work clothes, in terms of my legacy, in terms of everything my developer community wants to do on DEVOPS and really harnessed that innovation that's built in the public cloud, that built an open source that built internally to me, and that naturally leads them down the path of a hybrid cloud strategy. And Siskel's mission is to provide for that imperative, the simplest more power, more powerful platform to deliver hybrid cloud and that platform. Uh It's inter site we've been investing in. Inner side, it's a it's a SAS um service um inner side delivers to them that bridge between their estates of today that were closer today, the need for them to be guardians of enterprise grade resiliency with the agility uh that's needed for the future. The embracing of cloud. Native of new paradigms of deVOPS models, the embracing of innovation coming from public cloud and an open source and bridging those two is what inner side has been doing. That's kind of that's kind of the crux of our strategy. Of course we have the entire portfolio behind it to support any, any version of that, whether that is on prem in the cloud, hybrid, cloud, multi cloud and so forth. >>But but if I understand it correctly from what I heard earlier today, the inter site is really a linchpin of that strategy, is it not? >>It really is and may take a second to totally familiarize those who don't know inner side with what it is. We started building this platform quite a few years back and we we built a ground up to be an immensely scalable SAs, super simple hybrid cloud platform and it's a platform that provides a slew of service is inherently and then on top of that there are suites of services, the sweets of services that are tied to infrastructure, automation. Cisco, as well as Cisco partners. The streets of services that have nothing to do with Cisco um products from a hardware perspective. And it's got to do with more cloud orchestration and cloud native and inner side and its suite of services um continue to kind of increase in pace and velocity of delivery video. Just over the last two quarters we've announced a whole number of things will go a little bit deeper into some of those but they span everything from infrastructure automation to kubernetes and delivering community than service to workload optimization and having visibility into your cloud estate. How much it's costing into your on premise state into your work clothes and how they're performing. It's got integrations with other tooling with both Cisco Abdi uh as well as non Cisco um, assets and then and then it's got a whole slew of capabilities around orchestration because at the end of the day, the job of it is to deliver something that works and works at scale that you can monitor and make sure is resilient and that includes that. That includes a workflow and ability to say, you know, do this and do this and do this. Or it includes other ways of automation, like infrastructure as code and so forth. So it includes self service that so that expand that. But inside the world's simplest hybrid cloud platform, rapidly evolving rapidly delivering new services. And uh we'll talk about some more of those day. >>Great, thank you, Katie VJ. Let's bring you into the discussion. You guys recently made an announcement with the ASCIi corp. I was stoked because even though it seemed like a long time ago, pre covid, I mean in my predictions post, I said, ha, she was a name to watch our data partners. Et are you look at the survey data and they really have become mainstream? You know, particularly we think very important in the whole multi cloud discussion. And as well, they're attractive to customers. They have open source offerings. You can very easily experiment. Smaller organizations can take advantage. But if you want to upgrade to enterprise features like clustering or whatever, you can plug right in. Not a big complicated migration. So a very, very compelling story there. Why is this important? Why is this partnership important to Cisco's customers? Mhm. >>Absolutely. When the spot on every single thing that you said, let me just start by paraphrasing what ambition statement is in the cloud and computer group. Right ambition statement is to enable a cloud operating model for hybrid cloud. And what we mean by that is the ability to have extreme amounts of automation orchestration and observe ability across your hybrid cloud idea operations now. Uh So developers and applications team get a great amount of agility in public clouds and we're on a mission to bring that kind of agility and automation to the private cloud and to the data centers and inter site is a quickie platform and lynchpin to enable that kind of operations. Uh, Cloud like operations in the in the private clouds and the key uh As you rightly said, harsher car is the, you know, they were the inventors of the concept of infrastructure at school and in terra form, they have the world's number one infrastructure as code platform. So it became a natural partnership for Cisco to enter into a technology partnership with harsher card to integrate inter site with hardship cops, terra form to bring the benefits of infrastructure as code to the to hybrid cloud operations. And we've entered into a very tight integration and uh partnership where we allow developers devops teams and infrastructure or administrators to allow the use of infrastructure as code in a SAS delivered manner for both public and private club. So it's a very unique partnership and a unique integration that allows the benefits of cloud managed i E C. To be delivered to hybrid cloud operations. And we've been very happy and proud to be partnering with Russian government shutdown. >>Yeah, Terra form gets very high marks from customers. The a lot of value there. The inner side integration adds to that value. Let's stay on cloud native for a minute. We all talk about cloud native cady was sort of mentioning before you got the the core apps, uh you want to protect those, make sure their enterprise create but they gotta be cool as well for developers. You're connecting to other apps in the cloud or wherever. How are you guys thinking about this? Cloud native trend? What other movies are you making in this regard? >>I mean cloud native is there is one of the paramount I. D. Trends of today and we're seeing massive amounts of adoption of cloud native architecture in all modern applications. Now, Cloud Native has become synonymous with kubernetes these days and communities has emerged as a de facto cloud native platform for modern cloud native app development. Now, what Cisco has done is we have created a brand new SAs delivered kubernetes service that is integrated with inter site, we call it the inter site community service for A. Ks. And this just geared a little over one month ago. Now, what interstate kubernetes service does is it delivers a cloud managed and cloud delivered kubernetes service that can be deployed on any supported target infrastructure. It could be a Cisco infrastructure, it could be a third party infrastructure or it could even be public club. But think of it as kubernetes anywhere delivered as says, managed from inside. It's a very powerful capability that we've just released into inter site to enable the power of communities and clog native to be used to be used anywhere. But today we made a very important aspect because we are today announced the brand new Cisco service mess manager, the Cisco service mesh manager, which is available as an extension to the KS are doing decide basically we see service measures as being the future of networking right in the past we had layer to networking and layer three networking and now with service measures, application networking and layer seven networking is the next frontier of, of networking. But you need to think about networking for the application age very differently how it is managed, how it is deployed. It needs to be ready, developer friendly and developer centric. And so what we've done is we've built out an application networking strategy and built out the service match manager as a very simple way to deliver application networking through the consumers, like like developers and application teams. This is built on an acquisition that Cisco made recently of Banzai Cloud and we've taken the assets of Banzai Cloud and deliver the Cisco service mesh manager as an extension to KS. That brings the promise of future networking and modern networking to application and development gives >>God thank you. BJ. And so Katie, let's let's let's wrap this up. I mean, there was a lot in this announcement today, a lot of themes around openness, heterogeneity and a lot of functionality and value. Give us your final thoughts. >>Absolutely. So, couple of things to close on, first of all, um Inner side is the simplest, most powerful hybrid cloud platform out there. It enables that that cloud operating model that VJ talked about, but enables that across cloud. So it's sad, it's relatively easy to get into it and give it a spin so that I'd highly encouraged anybody who's not familiar with it to try it out and anybody who is familiar with it to look at it again, because they're probably services in there that you didn't notice or didn't know last time you looked at it because we're moving so fast. So that's the first thing. The second thing I close with is um, we've been talking about this bridge that's kind of bridging, bridging uh your your on prem your open source, your cloud estates. And it's so important to to make that mental leap because uh in past generation, we used to talk about integrating technologies together and then with public cloud, we started talking about move to public cloud, but it's really how do we integrate, how do we integrate all of that innovation that's coming from the hyper scale, is everything they're doing to innovate superfast, All of that innovation is coming from open source, all of that innovation that's coming from from companies around the world, including Cisco, How do we integrate that to deliver an outcome? Because at the end of the day, if you're a cloud of Steam, if you're an idea of Steam, your job is to deliver an outcome and our mission is to make it super simple for you to do that. That's the mission we're on and we're hoping that everybody that's excited as we are about how simple we made that. >>Great, thank you a lot in this announcement today, appreciate you guys coming back on and help us unpack you know, some of the details. Thank thanks so much. Great having you. >>Thank you >>Dave in a moment. We're gonna come back and talk about disruptive technologies and futures in the age of hybrid cloud with Vegas Rattana and James leach. You're watching the cube, the global leader in high tech coverage. >>What if your server box >>wasn't a box at >>all? What if it could do anything run anything? >>Be any box you >>need with massive scale precision and intelligence managed and optimized from the cloud integrated with all your clouds, private, public or hybrid. So you can build whatever you need today and tomorrow. The potential of this box is unlimited. Unstoppable unseen ever before. Unbox the future with Cisco UCS X series powered by inter site >>Cisco. >>The bridge to possible. Yeah >>we're here with Vegas Rattana who's the director of product management for Pcs at Cisco. And James Leach is the director of business development for U. C. S. At the Cisco as well. We're gonna talk about computing in the age of hybrid cloud. Welcome gentlemen. Great to see you. >>Thank you. >>Thank you because let's start with you and talk about a little bit about computing architectures. We know that they're evolving. They're supporting new data intensive and other workloads especially as high performance workload requirements. What's this guy's point of view on all this? I mean specifically interested in your thoughts on fabrics. I mean it's kind of your wheelhouse, you've got accelerators. What are the workloads that are driving these evolving technologies and how how is it impacting customers? What are you seeing? >>Sure. First of all, very excited to be here today. You're absolutely right. The pace of innovation and foundational platform ingredients have just been phenomenal in recent years. The fabric that's writers that drives the processing power, the Golden city all have been evolving just an amazing place and the peace will only pick up further. But ultimately it is all about applications and the way applications leverage those innovations. And we do see applications evolving quite rapidly. The new classes of applications are evolving to absorb those innovations and deliver much better business values. Very, very exciting time step. We're talking about the impact on the customers. Well, these innovations have helped them very positively. We do see significant challenges in the data center with the point product based approach of delivering these platforms, innovations to the applications. What has happened is uh, these innovations today are being packaged as point point products to meet the needs of a specific application and as you know, the different applications have no different needs. Some applications need more to abuse, others need more memory, yet others need, you know, more course, something different kinds of fabrics. As a result, if you walk into a data center today, it is very common to see many different point products in the data center. This creates a manageability challenge. Imagine the aspect of managing, you know, several different form factors want you to you purpose built servers. The variety of, you know, a blade form factor, you know, this reminds me of the situation we had before smartphones arrived. You remember the days when you when we used to have a GPS device for navigation system, a cool music device for listening to the music. A phone device for making a call camera for taking the photos right? And we were all excited about it. It's when a smart phones the right that we realized all those cool innovations could be delivered in a much simpler, much convenient and easy to consume through one device. And you know, I could uh, that could completely transform our experience. So we see the customers were benefiting from these innovations to have a way to consume those things in a much more simplistic way than they are able to go to that. >>And I like to look, it's always been about the applications. But to your point, the applications are now moving in a much faster pace. The the customer experience is expectation is way escalated. And when you combine all these, I love your analogy there because because when you combine all these capabilities, it allows us to develop new Applications, new capabilities, new customer experiences. So that's that I always say the next 10 years, they ain't gonna be like the last James Public Cloud obviously is heavily influencing compute design and and and customer operating models. You know, it's funny when the public cloud first hit the market, everyone we were swooning about low cost standard off the shelf servers in storage devices, but it quickly became obvious that customers needed more. So I wonder if you could comment on this. How are the trends that we've seen from the hyper scale, Is how are they filtering into on prem infrastructure and maybe, you know, maybe there's some differences there as well that you could address. >>Absolutely. So I'd say, first of all, quite frankly, you know, public cloud has completely changed the expectations of how our customers want to consume, compute, right? So customers, especially in a public cloud environment, they've gotten used to or, you know, come to accept that they should consume from the application out, right? They want a very application focused view, a services focused view of the world. They don't want to think about infrastructure, right? They want to think about their application, they wanna move outward, Right? So this means that the infrastructure basically has to meet the application where it lives. So what that means for us is that, you know, we're taking a different approach. We're we've decided that we're not going to chase this single pane of glass view of the world, which, frankly, our customers don't want, they don't want a single pane of glass. What they want is a single operating model. They want an operating model that's similar to what they can get at the public with the public cloud, but they wanted across all of their cloud options they wanted across private cloud across hybrid cloud options as well. So what that means is they don't want to just consume infrastructure services. They want all of their cloud services from this operating model. So that means that they may want to consume infrastructure services for automation Orchestration, but they also need kubernetes services. They also need virtualization services, They may need terror form workload optimization. All of these services have to be available, um, from within the operating model, a consistent operating model. Right? So it doesn't matter whether you're talking about private cloud, hybrid cloud anywhere where the application lives. It doesn't matter what matters is that we have a consistent model that we think about it from the application out. And frankly, I'd say this has been the stumbling block for private cloud. Private cloud is hard, right. This is why it hasn't been really solved yet. This is why we had to take a brand new approach. And frankly, it's why we're super excited about X series and inter site as that operating model that fits the hybrid cloud better than anything else we've seen >>is acute. First, first time technology vendor has ever said it's not about a single pane of glass because I've been hearing for decades, we're gonna deliver a single pane of glass is going to be seamless and it never happens. It's like a single version of the truth. It's aspirational and, and it's just not reality. So can we stay in the X series for a minute James? Uh, maybe in this context, but in the launch that we saw today was like a fire hose of announcements. So how does the X series fit into the strategy with inter site and hybrid cloud and this operating model that you're talking about? >>Right. So I think it goes hand in hand, right. Um the two pieces go together very well. So we have uh, you know, this idea of a single operating model that is definitely something that our customers demand, right? It's what we have to have, but at the same time we need to solve the problems of the cost was talking about before we need a single infrastructure to go along with that single operating model. So no longer do we need to have silos within the infrastructure that give us different operating models are different sets of benefits when you want infrastructure that can kind of do all of those configurations, all those applications. And then, you know, the operating model is very important because that's where we abstract the complexity that could come with just throwing all that technology at the infrastructure so that, you know, this is, you know, the way that we think about is the data center is not centered right? It's no longer centered applications live everywhere. Infrastructure lives everywhere. And you know, we need to have that consistent operating model but we need to do things within the infrastructure as well to take full advantage. Right? So we want all the sas benefits um, of a Ci CD model of, you know, the inter site can bring, we want all that that proactive recommendation engine with the power of A I behind it. We want the connected support experience went all of that. They want to do it across the single infrastructure and we think that that's how they tie together, that's why one or the other doesn't really solve the problem. But both together, that's why we're here. That's why we're super excited. >>So Vegas, I make you laugh a little bit when I was an analyst at I D C, I was deep in infrastructure and then when I left I was doing, I was working with application development heads and like you said, uh infrastructure, it was just a, you know, roadblock but but so the target speakers with Cisco announced UCS a decade ago, I totally missed it. I didn't understand it. I thought it was Cisco getting into the traditional server business and it wasn't until I dug in then I realized that your vision was really to transform infrastructure, deployment and management and change them all. I was like, okay, I got that wrong uh but but so let's talk about the the ecosystem and the joint development efforts that are going on there, X series, how does it fit into this, this converged infrastructure business that you've, you've built and grown with partners, you got storage partners like Netapp and Pure, you've got i SV partners in the ecosystem. We see cohesive, he has been a while since we we hung out with all these companies at the Cisco live hopefully next year, but tell us what's happening in that regard. >>Absolutely, I'm looking forward to seeing you in the Cisco live next year. You know, they have absolutely you brought up a very good point. You see this is about the ecosystem that it brings together, it's about making our customers bring up the entire infrastructure from the core foundational hardware all the way to the application level so that they can, you know, go off and running pretty quick. The converse infrastructure has been one of the corners 2.5 hour of the strategy, as you pointed out in the last decade. And and and I'm I'm very glad to share that converse infrastructure continues to be a very popular architecture for several enterprise applications. Seven today, in fact, it is the preferred architecture for mission critical applications where performance resiliency latency are the critical requirements there almost a de facto standards for large scale deployments of virtualized and business critical data bases and so forth with X series with our partnerships with our Stories partners. Those architectures will absolutely continue and will get better. But in addition as a hybrid cloud world, so we are now bringing in the benefits of canvas in infrastructure uh to the world of hybrid cloud will be supporting the hybrid cloud applications now with the CIA infrastructure that we have built together with our strong partnership with the Stories partners to deliver the same benefits to the new ways applications as well. >>Yeah, that's what customers want. They want that cloud operating model. Right, go ahead please. >>I was going to say, you know, the CIA model will continue to thrive. It will transition uh it will expand the use cases now for the new use cases that were beginning to, you know, say they've absolutely >>great thank you for that. And James uh have said earlier today, we heard this huge announcement, um a lot of lot of parts to it and we heard Katie talk about this initiative is it's really computing built for the next decade. I mean I like that because it shows some vision and you've got a road map that you've thought through the coming changes in workloads and infrastructure management and and some of the technology that you can take advantage of beyond just uh, you know, one or two product cycles. So, but I want to understand what you've done here specifically that you feel differentiates you from other competitive architectures in the industry. >>Sure. You know that's a great question. Number one. Number two, um I'm frankly a little bit concerned at times for for customers in general for our customers customers in general because if you look at what's in the market, right, these rinse and repeat systems that were effectively just rehashes of the same old design, right? That we've seen since before 2000 and nine when we brought you C. S to market these are what we're seeing over and over and over again. That's that's not really going to work anymore frankly. And I think that people are getting lulled into a false sense of security by seeing those things continually put in the market. We rethought this from the ground up because frankly future proofing starts now, right? If you're not doing it right today, future proofing isn't even on your radar because you're not even you're not even today proved. So we re thought the entire chassis, the entire architecture from the ground up. Okay. If you look at other vendors, if you look at other solutions in the market, what you'll see is things like management inside the chassis. That's a great example, daisy chaining them together >>like who >>needs that? Who wants that? Like that kind of complexity is first of all, it's ridiculous. Um, second of all, um, if you want to manage across clouds, you have to do it from the cloud, right. It's just common sense. You have to move management where it can have the scale and the scope that it needs to impact your entire domain, your world, which is much larger now than it was before. We're talking about true hybrid cloud here. Right. So we had to solve certain problems that existed in the traditional architecture. You know, I can't tell you how many times I heard you talk about the mid plane is a great example. You know, the mid plane and a chastity is a limiting factor. It limits us on how much we can connect or how much bandwidth we have available to the chassis. It limits us on air flow and other things. So how do you solve that problem? Simple. Just get rid of it. Like we just we took it out, right. It's not no longer a problem. We designed an architecture that doesn't need it. It doesn't rely on it. No forklift upgrades. So, as we start moving down the path of needing liquid cooling or maybe we need to take advantage of some new, high performance, low latency fabrics. We can do that with almost. No problem at all. Right, So, we don't have any forklift upgrades. Park your forklift on the side. You won't need it anymore because you can upgrade gradually. You can move along as technologies come into existence that maybe don't even exist. They they may not even be on our radar today to take advantage of. But I like to think of these technologies, they're really important to our customers. These are, you know, we can call them disruptive technologies. The reality is that we don't want to disrupt our customers with these technologies. We want to give them these technologies so they can go out and be disruptive themselves. Right? And this is the way that we've designed this from the ground up to be easy to consume and to take advantage of what we know about today and what's coming in the future that we may not even know about. So we think this is a way to give our customers that ultimate capability flexibility and and future proofing. >>I like I like that phrase True hybrid cloud. It's one that we've used for years and but to me this is all about that horizontal infrastructure that can support that vision of what true hybrid cloud is. You can support the mission critical applications. You can you can develop on the system and you can support a variety of workload. You're not locked into one narrow stovepipe and that does have legs, Vegas and James. Thanks so much for coming on the program. Great to see you. >>Yeah. Thank you. Thank you. >>When we return shortly thomas Shiva who leads Cisco's data center group will be here and thomas has some thoughts about the transformation of networking I. T. Teams. You don't wanna miss what he has to say. You're watching the cube. The global leader in high tech company. Okay, >>mm. Mhm, mm. Okay. Mhm. Yeah. Mhm. Yeah. >>Mhm. Yes. Yeah. Okay. We're here with thomas Shiva who is the Vice president of Product Management, A K A VP of all things data center, networking STN cloud. You name it in that category. Welcome thomas. Good to see you again. >>Hey Sam. Yes. Thanks for having me on. >>Yeah, it's our pleasure. Okay, let's get right into observe ability. When you think about observe ability, visibility, infrastructure monitoring problem resolution across the network. How does cloud change things? In other words, what are the challenges that networking teams are currently facing as they're moving to the cloud and trying to implement hybrid cloud? >>Yeah. Yeah, visibility as always is very, very important. And it's quite frankly, it's not just it's not just the networking team is actually the application team to write. And as you pointed out, the underlying impetus to what's going on here is the data center is where the data is. And I think we set us a couple years back and really what happens the applications are going to be deployed uh in different locations, right. Whether it's in a public cloud, whether it's on prayer, uh, and they are built differently right there, built as microservices, they might actually be distributed as well at the same application. And so what that really means is you need as an operator as well as actually a user better visibility. Where are my pieces and you need to be able to correlate between where the app is and what the underlying network is that is in place in these different locations. So you have actually a good knowledge while the app is running so fantastic or sometimes not. So I think that's that's really the problem statement. What what we're trying to go afterwards, observe ability. >>Okay, and let's double click on that. So a lot of customers tell me that you gotta stare at log files until your eyes bleed and you gotta bring in guys with lab coats who have phds to figure all this stuff out. So, so you just described, it's getting more complex, but at the same time you have to simplify things. So how how are you doing that, >>correct? So what we basically have done is we have this fantastic product that that is called 1000 Ice. And so what this does is basically as the name, which I think is a fantastic fantastic name. You have these sensors everywhere. Um, and you can have a good correlation on uh links between if I run from a site to aside from a site to a cloud, from a cloud to cloud and you basically can measure what is the performance of these links. And so what we're, what we're doing here is we're actually extending the footprint of these thousands agent. Right? Instead of just having uh inversion machine clouds, we are now embedding them with the Cisco network devices. Right? We announced this with the catalyst 9000 and we're extending this now to our 8000 catalyst product line for the for the SD were in products as well as to the data center products the next line. Um and so what you see is is, you know, half a saying, you have 1000 eyes, you get a million insights and you get a billion dollar of improvements uh for how your applications run. And this is really uh, the power of tying together the footprint of where the network is with the visibility, what is going on. So you actually know the application behavior that is attached to this network. >>I see. So okay. So as the cloud evolves and expands it connects your actually enabling 1000 eyes to go further, not just confined within a single data center location, but out to the network across clouds, et cetera, >>correct. Wherever the network is, you're going to have 1000 I sensor and you can't bring this together and you can quite frankly pick if you want to say, hey, I have my application in public cloud provider, a uh, domain one and I have another one domain to, I can't do monitor that link. I can also monitor have a user that has a campus location or branch location. I kind of put an agent there and then I can monitor the connectivity from that branch location all the way to the let's say corporations that data centre, our headquarter or to the cloud. And I can have these probes and just we have visibility and saying, hey, if there's a performance, I know where the issue is and then I obviously can use all the other foods that we have to address those. >>All right, let's talk about the cloud operating model. Everybody tells us it's really the change in the model that drives big numbers in terms of R. O. I. And I want you to maybe address how you're bringing automation and devops to this world of of hybrid and specifically how is Cisco enabling I. T. Organizations to move to a cloud operating model? Is that cloud definition expands? >>Yeah, no that's that's another interesting topic beyond the observe ability. So really, really what we're seeing and this is going on for uh I want to say a couple of years now, it's really this transition from operating infrastructure as a networking team more like a service like what you would expect from a cloud provider. Right? It's really around the network team offering services like a cloud provided us. And that's really what the meaning is of cloud operating model. Right? But this is infrastructure running your own data center where that's linking that infrastructure was whatever runs on the public club is operating and like a cloud service. And so we are on this journey for why? So one of the examples uh then we have removing some of the control software assets, the customers that they can deploy on prayer uh to uh an instance that they can deploy in a cloud provider and just busy, insane. She ate things there and then just run it that way. Right. And so the latest example for this is what we have our identity service engine that is now limited availability available on AWS and will become available in mid this year, both in Italy as unusual as a service. You can just go to market place, you can load it there and now you create, you can start running your policy control in a cloud, managing your access infrastructure in your data center, in your campus wherever you want to do it. And so that's just one example of how we see our customers network operations team taking advantage of a cloud operating model and basically employing their, their tools where they need them and when they need them. >>So what's the scope of, I hope I'm saying it right. Ice, right. I see. I think it's called ice. What's the scope of that like for instance, turn in effect my or even, you know, address simplify my security approach. >>Absolutely. That's now coming to what is the beauty of the product itself? Yes. What you can do is really is that there's a lot of people talking about else. How do I get to zero trust approach to networking? How do I get to a much more dynamic, flexible segmentation in my infrastructure. Again, whether this is only campus X as well as a data center and Ice help today, you can use this as a point to define your policies and then any connect from there. Right. In this particular case we would instant Ice in the cloud as a software load. You now can connect and say, hey, I want to manage and program my network infrastructure and my data center on my campus, going to the respective control over this DNA Center for campus or whether it is the A. C. I. Policy controller. And so yes, what you get as an effect out of this is a very elegant way to automatically manage in one place. What is my policy and then drive the right segmentation in your network infrastructure? >>zero. Trust that, you know, it was pre pandemic. It was kind of a buzzword. Now it's become a mandate. I wonder if we could talk about right. I mean I wonder if you talk about cloud native apps, you got all these developers that are working inside organizations. They're maintaining legacy apps. They're connecting their data to systems in the cloud there, sharing that data. I need these developers, they're rapidly advancing their skill sets. How is Cisco enabling its infrastructure to support this world of cloud? Native making infrastructure more responsive and agile for application developers? >>Yeah. So, you know, we're going to the top of his visibility, we talked about the operating model, how how our network operators actually want to use tools going forward. Now, the next step to this is it's not just the operator. How do they actually, where do they want to put these tools, how they, how they interact with these tools as well as quite frankly as how, let's say, a devops team on application team or Oclock team also wants to take advantage of the program ability of the underlying network. And this is where we're moving into this whole cloud native discussion, right? Which is really two angles, that is the cloud native way, how applications are being built. And then there is the cloud native way, how you interact with infrastructure. Right? And so what we have done is we're a putting in place the on ramps between clouds and then on top of it we're exposing for all these tools, a P I S that can be used in leverage by standard uh cloud tools or uh cloud native tools. Right. And one example or two examples we always have and again, we're on this journey for a while is both answerable uh script capabilities that exist from red hat as well as uh Ashitaka from capabilities that you can orchestrate across infrastructure to drive infrastructure, automation and what what really stands behind it is what either the networking operations team wants to do or even the ap team. They want to be able to describe the application as a code and then drive automatically or programmatically in situation of infrastructure needed for that application. And so what you see us doing is providing all these capability as an interface for all our network tools. Right. Whether it's this ice that I just mentioned, whether this is our D. C. And controllers in the data center, uh whether these are the controllers in the in the campus for all of those, we have cloud native interfaces. So operator or uh devops team can actually interact directly with that infrastructure the way they would do today with everything that lives in the cloud, with everything how they brought the application. >>This is key. You can't even have the conversation of op cloud operating model that includes and comprises on prem without programmable infrastructure. So that's that's very important. Last question, thomas our customers actually using this, they made the announcement today. There are there are there any examples of customers out there doing this? >>We do have a lot of customers out there that are moving down the past and using the D. D. Cisco high performance infrastructure, but also on the compute side as well as on an exercise one of the customers. Uh and this is like an interesting case. It's Rakuten uh record and is a large tackle provider, a mobile five G. Operator uh in Japan and expanding and is in different countries. Uh and so people something oh, cloud, you must be talking about the public cloud provider, the big the big three or four. But if you look at it, there's a lot of the tackle service providers are actually cloud providers as well and expanding very rapidly. And so we're actually very proud to work together with with Rakuten and help them building a high performance uh, data and infrastructure based on hard gig and actually phone a gig uh to drive their deployment to. It's a five G mobile cloud infrastructure, which is which is uh where the whole the whole world where traffic is going. And so it's really exciting to see this development and see the power of automation visibility uh together with the high performance infrastructure becoming reality and delivering actually services, >>you have some great points you're making there. Yes, you have the big four clouds, your enormous, but then you have a lot of actually quite large clouds. Telcos that are either approximate to those clouds or they're in places where those hyper scholars may not have a presence and building out their own infrastructure. So so that's a great case study uh thomas, hey, great having you on. Thanks so much for spending some time with us. >>Yeah, same here. I appreciate it. Thanks a lot. >>I'd like to thank Cisco and our guests today V Joy, Katie VJ, viscous James and thomas for all your insights into this evolving world of hybrid cloud, as we said at the top of the next decade will be defined by an entirely new set of rules. And it's quite possible things will evolve more quickly because the cloud is maturing and has paved the way for a new operating model where everything is delivered as a service, automation has become a mandate because we just can't keep throwing it labor at the problem anymore. And with a I so much more as possible in terms of driving operational efficiencies, simplicity and support of the workloads that are driving the digital transformation that we talk about all the time. This is Dave Volonte and I hope you've enjoyed today's program. Stay Safe, be well and we'll see you next time.

>>Hi, everyone. My name is my uncle. My uncle Poor I worked with Geo reminds you in India. We call ourselves Geo Platforms. Now on. We've been recently in the news. You've raised a lot off funding from one of the largest, most of the largest tech companies in the world. And I'm here to talk about Geos Cloud Journey, Onda Mantis Partnership. I've titled it the story often, Underdog becoming the largest telecom company in India within four years, which is really special. And we're, of course, held by the cloud. So quick disclaimer. Right. The content shared here is only for informational purposes. Um, it's only for this event. And if you want to share it outside, especially on social media platforms, we need permission from Geo Platforms limited. Okay, quick intro about myself. I am a VP of engineering a geo. I lead the Cloud Services and Platforms team with NGO Andi. I mean the geo since the beginning, since it started, and I've seen our cloud footprint grow from a handful of their models to now eight large application data centers across three regions in India. And we'll talk about how we went here. All right, Let's give you an introduction on Geo, right? Giorgio is on how we became the largest telecom campaign, India within four years from 0 to 400 million subscribers. And I think there are There are a lot of events that defined Geo and that will give you an understanding off. How do you things and what you did to overcome massive problems in India. So the slide that I want to talkto is this one and, uh, I The headline I've given is, It's the Geo is the fastest growing tech company in the world, which is not a new understatement. It's eggs, actually, quite literally true, because very few companies in the world have grown from zero to 400 million subscribers within four years paying subscribers. And I consider Geo Geos growth in three phases, which I have shown on top. The first phase we'll talk about is how geo grew in the smartphone market in India, right? And what we did to, um to really disrupt the telecom space in India in that market. Then we'll talk about the feature phone phase in India and how Geo grew there in the future for market in India. and then we'll talk about what we're doing now, which we call the Geo Platforms phase. Right. So Geo is a default four g lt. Network. Right. So there's no to geo three g networks that Joe has, Um it's a state of the art four g lt voiceover lt Network and because it was designed fresh right without any two D and three G um, legacy technologies, there were also a lot of challenges Lawn geo when we were starting up. One of the main challenges waas that all the smart phones being sold in India NGOs launching right in 2000 and 16. They did not have the voice or lt chip set embedded in the smartphone because the chips it's far costlier to embed in smartphones and India is a very price and central market. So none of the manufacturers were embedding the four g will teach upset in the smartphones. But geos are on Lee a volte in network, right for the all the network. So we faced a massive problem where we said, Look there no smartphones that can support geo. So how will we grow Geo? So in order to solve that problem, we launched our own brand of smartphones called the Life um, smartphones. And those phones were really high value devices. So there were $50 and for $50 you get you You At that time, you got a four g B storage space. A nice big display for inch display. Dual cameras, Andi. Most importantly, they had volte chip sets embedded in them. Right? And that got us our initial customers the initial for the launch customers when we launched. But more importantly, what that enabled other oh, EMS. What that forced the audience to do is that they also had to launch similar smartphones competing smartphones with voltage upset embedded in the same price range. Right. So within a few months, 3 to 4 months, um, all the other way EMS, all the other smartphone manufacturers, the Samsung's the Micromax is Micromax in India, they all had volte smartphones out in the market, right? And I think that was one key step We took off, launching our own brand of smartphone life that helped us to overcome this problem that no smartphone had. We'll teach upsets in India and then in order. So when when we were launching there were about 13 telecom companies in India. It was a very crowded space on demand. In order to gain a foothold in that market, we really made a few decisions. Ah, phew. Key product announcement that really disrupted this entire industry. Right? So, um, Geo is a default for GLT network itself. All I p network Internet protocol in everything. All data. It's an all data network and everything from voice to data to Internet traffic. Everything goes over this. I'll goes over Internet protocol, and the cost to carry voice on our smartphone network is very low, right? The bandwidth voice consumes is very low in the entire Lt band. Right? So what we did Waas In order to gain a foothold in the market, we made voice completely free, right? He said you will not pay anything for boys and across India, we will not charge any roaming charges across India. Right? So we made voice free completely and we offer the lowest data rates in the world. We could do that because we had the largest capacity or to carry data in India off all the other telecom operators. And these data rates were unheard off in the world, right? So when we launched, we offered a $2 per month or $3 per month plan with unlimited data, you could consume 10 gigabytes of data all day if you wanted to, and some of our subscriber day. Right? So that's the first phase off the overgrowth and smartphones and that really disorders. We hit 100 million subscribers in 170 days, which was very, very fast. And then after the smartphone faith, we found that India still has 500 million feature phones. And in order to grow in that market, we launched our own phone, the geo phone, and we made it free. Right? So if you take if you took a geo subscription and you carried you stayed with us for three years, we would make this phone tree for your refund. The initial deposit that you paid for this phone and this phone had also had quite a few innovations tailored for the Indian market. It had all of our digital services for free, which I will talk about soon. And for example, you could plug in. You could use a cable right on RCR HDMI cable plug into the geo phone and you could watch TV on your big screen TV from the geophones. You didn't need a separate cable subscription toe watch TV, right? So that really helped us grow. And Geo Phone is now the largest selling feature phone in India on it. 100 million feature phones in India now. So now now we're in what I call the geo platforms phase. We're growing of a geo fiber fiber to the home fiber toe the office, um, space. And we've also launched our new commerce initiatives over e commerce initiatives and were steadily building platforms that other companies can leverage other companies can use in the Jeon o'clock. Right? So this is how a small startup not a small start, but a start of nonetheless least 400 million subscribers within four years the fastest growing tech company in the world. Next, Geo also helped a systemic change in India, and this is massive. A lot of startups are building on this India stack, as people call it, and I consider this India stack has made up off three things, and the acronym I use is jam. Trinity, right. So, um, in India, systemic change happened recently because the Indian government made bank accounts free for all one billion Indians. There were no service charges to store money in bank accounts. This is called the Jonathan. The J. GenDyn Bank accounts. The J out off the jam, then India is one of the few countries in the world toe have a digital biometric identity, which can be used to verify anyone online, which is huge. So you can simply go online and say, I am my ankle poor on duh. I verify that this is indeed me who's doing this transaction. This is the A in the jam and the last M stands for Mobil's, which which were held by Geo Mobile Internet in a plus. It is also it is. It also stands for something called the U. P I. The United Unified Payments Interface. This was launched by the Indian government, where you can carry digital transactions for free. You can transfer money from one person to the to another, essentially for free for no fee, right so I can transfer one group, even Indian rupee to my friend without paying any charges. That is huge, right? So you have a country now, which, with a with a billion people who are bank accounts, money in the bank, who you can verify online, right and who can pay online without any problems through their mobile connections held by G right. So suddenly our market, our Internet market, exploded from a few million users to now 506 106 100 million mobile Internet users. So that that I think, was a massive such a systemic change that happened in India. There are some really large hail, um, numbers for this India stack, right? In one month. There were 1.6 billion nuclear transactions in the last month, which is phenomenal. So next What is the impact of geo in India before you started, we were 155th in the world in terms off mobile in terms of broadband data consumption. Right. But after geo, India went from one 55th to the first in the world in terms of broadband data, largely consumed on mobile devices were a mobile first country, right? We have a habit off skipping technology generation, so we skip fixed line broadband and basically consuming Internet on our mobile phones. On average, Geo subscribers consumed 12 gigabytes of data per month, which is one of the highest rates in the world. So Geo has a huge role to play in making India the number one country in terms off broad banded consumption and geo responsible for quite a few industry first in the telecom space and in fact, in the India space, I would say so before Geo. To get a SIM card, you had to fill a form off the physical paper form. It used to go toe Ah, local distributor. And that local distributor is to check the farm that you feel incorrectly for your SIM card and then that used to go to the head office and everything took about 48 hours or so, um, to get your SIM card. And sometimes there were problems there also with a hard biometric authentication. We enable something, uh, India enable something called E K Y C Elektronik. Know your customer? We took a fingerprint scan at our point of Sale Reliance Digital stores, and within 15 minutes we could verify within a few minutes. Within a few seconds we could verify that person is indeed my hunk, right, buying the same car, Elektronik Lee on we activated the SIM card in 15 minutes. That was a massive deal for our growth. Initially right toe onboard 100 million customers. Within our and 70 days. We couldn't have done it without be K. I see that was a massive deal for us and that is huge for any company starting a business or start up in India. We also made voice free, no roaming charges and the lowest data rates in the world. Plus, we gave a full suite of cloud services for free toe all geo customers. For example, we give goTV essentially for free. We give GOTV it'll law for free, which people, when we have a launching, told us that no one would see no one would use because the Indians like watching TV in the living rooms, um, with the family on a big screen television. But when we actually launched, they found that GOTV is one off our most used app. It's like 70,000,080 million monthly active users, and now we've basically been changing culture in India where culture is on demand. You can watch TV on the goal and you can pause it and you can resume whenever you have some free time. So really changed culture in India, India on we help people liver, digital life online. Right, So that was massive. So >>I'm now I'd like to talk about our cloud >>journey on board Animal Minorities Partnership. We've been partners that since 2014 since the beginning. So Geo has been using open stack since 2014 when we started with 14 note luster. I'll be one production environment One right? And that was I call it the first wave off our cloud where we're just understanding open stack, understanding the capabilities, understanding what it could do. Now we're in our second wave. Where were about 4000 bare metal servers in our open stack cloud multiple regions, Um, on that around 100,000 CPU cores, right. So it's a which is one of the bigger clouds in the world, I would say on almost all teams, with Ngor leveraging the cloud and soon I think we're going to hit about 10,000 Bama tools in our cloud, which is massive and just to give you a scale off our network, our in French, our data center footprint. Our network introduction is about 30 network data centers that carry just network traffic across there are there across India and we're about eight application data centers across three regions. Data Center is like a five story building filled with servers. So we're talking really significant scale in India. And we had to do this because when we were launching, there are the government regulation and try it. They've gotten regulatory authority of India, mandates that any telecom company they have to store customer data inside India and none of the other cloud providers were big enough to host our clothes. Right. So we we made all this intellectual for ourselves, and we're still growing next. I love to show you how we grown with together with Moran says we started in 2014 with the fuel deployment pipelines, right? And then we went on to the NK deployment. Pipelines are cloud started growing. We started understanding the clouds and we picked up M C p, which has really been a game changer for us in automation, right on DNA. Now we are in the latest release, ofem CPM CPI $2019 to on open stack queens, which on we've just upgraded all of our clouds or the last few months. Couple of months, 2 to 3 months. So we've done about nine production clouds and there are about 50 internal, um, teams consuming cloud. We call as our tenants, right. We have open stack clouds and we have communities clusters running on top of open stack. There are several production grade will close that run on this cloud. The Geo phone, for example, runs on our cloud private cloud Geo Cloud, which is a backup service like Google Drive and collaboration service. It runs out of a cloud. Geo adds G o g S t, which is a tax filing system for small and medium enterprises, our retail post service. There are all these production services running on our private clouds. We're also empaneled with the government off India to provide cloud services to the government to any State Department that needs cloud services. So we were empaneled by Maiti right in their ego initiative. And our clouds are also Easter. 20,000 certified 20,000 Colin one certified for software processes on 27,001 and said 27,017 slash 18 certified for security processes. Our clouds are also P our data centers Alsop a 942 be certified. So significant effort and investment have gone toe These data centers next. So this is where I think we've really valued the partnership with Morantes. Morantes has has trained us on using the concepts of get offs and in fries cold, right, an automated deployments and the tool change that come with the M C P Morantes product. Right? So, um, one of the key things that has happened from a couple of years ago to today is that the deployment time to deploy a new 100 north production cloud has decreased for us from about 55 days to do it in 2015 to now, we're down to about five days to deploy a cloud after the bear metals a racked and stacked. And the network is also the physical network is also configured, right? So after that, our automated pipelines can deploy 100 0 clock in five days flight, which is a massive deal for someone for a company that there's adding bear metals to their infrastructure so fast, right? It helps us utilize our investment, our assets really well. By the time it takes to deploy a cloud control plane for us is about 19 hours. It takes us two hours to deploy a compu track and it takes us three hours to deploy a storage rack. Right? And we really leverage the re class model off M C. P. We've configured re class model to suit almost every type of cloud that we have, right, and we've kept it fairly generous. It can be, um, Taylor to deploy any type of cloud, any type of story, nor any type of compute north. Andi. It just helps us automate our deployments by putting every configuration everything that we have in to get into using infra introduction at school, right plus M. C. P also comes with pipelines that help us run automated tests, automated validation pipelines on our cloud. We also have tempest pipelines running every few hours every three hours. If I recall correctly which run integration test on our clouds to make sure the clouds are running properly right, that that is also automated. The re class model and the pipelines helpers automate day to operations and changes as well. There are very few seventh now, compared toa a few years ago. It very rare. It's actually the exception and that may be because off mainly some user letter as opposed to a cloud problem. We also have contributed auto healing, Prometheus and Manager, and we integrate parameters and manager with our even driven automation framework. Currently, we're using Stack Storm, but you could use anyone or any event driven automation framework out there so that it indicates really well. So it helps us step away from constantly monitoring our cloud control control planes and clothes. So this has been very fruitful for us and it has actually apps killed our engineers also to use these best in class practices like get off like in France cord. So just to give you a flavor on what stacks our internal teams are running on these clouds, Um, we have a multi data center open stack cloud, and on >>top of that, >>teams use automation tools like terra form to create the environments. They also create their own Cuba these clusters and you'll see you'll see in the next slide also that we have our own community that the service platform that we built on top of open stack to give developers development teams NGO um, easy to create an easy to destroy Cuban. It is environment and sometimes leverage the Murano application catalog to deploy using heats templates to deploy their own stacks. Geo is largely a micro services driven, Um um company. So all of our applications are micro services, multiple micro services talking to each other, and the leverage develops. Two sets, like danceable Prometheus, Stack stone from for Otto Healing and driven, not commission. Big Data's tax are already there Kafka, Patches, Park Cassandra and other other tools as well. We're also now using service meshes. Almost everything now uses service mesh, sometimes use link. Erred sometimes are experimenting. This is Theo. So So this is where we are and we have multiple clients with NGO, so our products and services are available on Android IOS, our own Geo phone, Windows Macs, Web, Mobile Web based off them. So any client you can use our services and there's no lock in. It's always often with geo, so our sources have to be really good to compete in the open Internet. And last but not least, I think I love toe talk to you about our container journey. So a couple of years ago, almost every team started experimenting with containers and communities and they were demand for as a platform team. They were demanding community that the service from us a manage service. Right? So we built for us, it was much more comfortable, much more easier toe build on top of open stack with cloud FBI s as opposed to doing this on bare metal. So we built a fully managed community that a service which was, ah, self service portal, where you could click a button and get a community cluster deployed in your own tenant on Do the >>things that we did are quite interesting. We also handle some geo specific use cases. So we have because it was a >>manage service. We deployed the city notes in our own management tenant, right? We didn't give access to the customer to the city. Notes. We deployed the master control plane notes in the tenant's tenant and our customers tenant, but we didn't give them access to the Masters. We didn't give them the ssh key the workers that the our customers had full access to. And because people in Genova learning and experimenting, we gave them full admin rights to communities customers as well. So that way that really helped on board communities with NGO. And now we have, like 15 different teams running multiple communities clusters on top, off our open stack clouds. We even handle the fact that there are non profiting. I people separate non profiting I peoples and separate production 49 p pools NGO. So you could create these clusters in whatever environment that non prod environment with more open access or a prod environment with more limited access. So we had to handle these geo specific cases as well in this communities as a service. So on the whole, I think open stack because of the isolation it provides. I think it made a lot of sense for us to do communities our service on top off open stack. We even did it on bare metal, but that not many people use the Cuban, indeed a service environmental, because it is just so much easier to work with. Cloud FBI STO provision much of machines and covering these clusters. That's it from me. I think I've said a mouthful, and now I love for you toe. I'd love to have your questions. If you want to reach out to me. My email is mine dot capulet r l dot com. I'm also you can also message me on Twitter at my uncouple. So thank you. And it was a pleasure talking to you, Andre. Let let me hear your questions.

>>from Santa Clara, California In the heart of Silicon Valley, it's the queue covering altitude 2020. Brought to you by aviatrix. >>Our next customer panel got great. Another set of cloud Network architect Justin Smith, was Aura Justin broadly with Ellie Mae and omit Otri job with Cooper. But on the stage. >>Yeah, all right. Thank you. Thank you, Thank you. Yeah, >>he's got all the cliff notes from the last session. Welcome, Rinse and repeat. Yeah, we got to go under the hood a little bit and I think they nailed the what we've been reporting and we've been having a conversation around. Networking is where the action is, cause that's the end of the day. You gotta move impact from a to B. And yet workloads exchanging data. So it's really killer. So let's get started. I mean, what are you seeing as the journey of of multi cloud as you go under the hood and say, Okay, I got to implement this, have to engineer the network, make it enabling make it programmable, making 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're running an organization, which is running infrastructures, according 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 what? Your architecture first, don't wait. Architecture may not be perfect, but the best architecture that's available today and be agile to idiot and make improvements over there. >>We got to Justin's over here, so I have to be careful when I pointed Question and Justin, they both have the 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 perspective. What's your take on the journey? Justin? >>Yeah, I mean, from our first do, we started out very much focused on one cloud. Ah, and as we started acquisitions, we started doing new products to market. The need for multi cloud becomes very apparent very quickly for us. And so, you know, having 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 this 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 in the network has been a real enabler of this is that there's one network and it touches whatever cloud we wanted to touch on. It touches the data centers that we needed to touch, and it touches the customers that we needed to touch. Our job is to make sure that the services that are available in 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 dio >>before we get the architecture section, I want to ask you guys a question. 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 take it, we'll start with What do you think about that? >>Yeah, So you're gonna have workloads running in different clouds, and the workloads would have affinity to one cloud or another. But how you expose that? It's a matter of how you're gonna build your networks, how we're gonna run security, how we're gonna do egress, ingress out offered. So >>networking is the big problem. How do you suppose this? What's the solution? That's the key Pain points and problem statement. >>I mean, they get the key pain point for most companies is how do you take your traditional on premise network and then blow it out to the cloud in a way that makes sense. I p conflicts. You have space. You have public eyepiece on 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 side. 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 I t. Networking. So our job when when these all of these things are simplified into like s three, 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 GC p resource is 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 disable them. Do >>you think I do? You guys think Infrastructure's code, which I love that because that's the future it is. We saw that with Dev Ops, but I just start getting the networking. Is it getting down to the network portion where it's network as code storage and compute? Working really well is seeing all kubernetes and service meshes. Trend network is code reality is that there is still got work >>to do. It's absolutely there. I mean, you mentioned that develops and it's very real. I mean, in Cooper, we build our networks through terraform and on not only just data from building a p I so that we can consistently build we nuts and vpc all across in the same way >>you got to do it. >>Yeah, and even security groups and then on top and aviatrix comes in. We can peer the network's bridge bridge, all the different regions through court. >>Same with you guys about >>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 all my guys, that's what they focus on is bringing now what they're doing in the cloud into the data center, which is kind of opposite what it should be that's full. When it used to be. >>It's full dev ops, then >>yes, yeah, I mean, for us, it was similar on premise. Still somewhat very manual though we're moving more Norton Ninja and Terra Form concepts, but everything in the production environment, confirmation terraform code and now coming into the data center. So I just wanted to jump in on 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 architectures used to be an on Prem, and now it's shifted in the cloud it once you have your strategic architecture what what do you do? You push that everywhere. So what you used to see the beginning of cloud was pushing the architecture on Prem into cloud. Now I won't pick up on what you said The 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 so first that and then also in the journey Where are you at? From 0 to 100 of, actually in the journey to cloud Are you 50% There are you 10%. So you evacuating data centers next year? I mean, where are you guys at >>s. So there's there's two types of gravity that you typically are dealing with the migration. First is data gravity in your data set and where that data lives. And the second is the network platform that interrupts all that together in our case, the data gravity still mostly on Prem. But our network is now extending 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 halfway through the process, we're taking a handle of lift and shift. And when did that start? We started about three years ago. >>Okay, Well, for us, it's a very different story. Started from a garage 100% in the cloud. It's a business spend management platform as a software as a service, 100% in the cloud. It was like 10 years ago, right? Yes. >>Yeah. Has a riding the wave of the architecture. Just I want to ask you is or you guys mentioned Dev ops. I mean, obviously we saw the huge observe Ability way which essentially network management for the cloud. In my opinion, it's more dynamic, but this is about visibility. We heard from 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 Dev Ops down? >>Well, this this is the big challenge for all of us is 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 own. That would be data center connectivity. We now I work 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 so if you do that with their native solutions, you do lose visibility. There are areas in 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 and provide consistency while doing it. >>Great conversation. I love what you said earlier laden C band with I think availability with your SIM pop three things guys s l A and 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 wanna call Blind Spot. How are you guys looking at the interconnect between clouds? Because, you know, I can see that working from ground to cloud on cloud. But when you start dealing multi clouds, workloads, sl A'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're going to be calling each other. So it's very important to have that visibility that you can see how their data is flowing at war latency and what our ability is is there and over a Saturday meets to operate on. So it's >>so use the software dashboard, look at the Times and look at the latest in >>the old days strong So on open salon, you try to figure it out, and then your data, as you look at our >>Justin, what's your answer? That cause 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 a plan for that latency and our applications. That something is we're tracking ingress, Ally, something you start planning for. And you loosely couple these services in 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 in much better way. >>You guys are all great examples of cloud native from day one 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 a factor into all my design, design principles and everything you're doing. What? It was there a moment or was it from day one? >>Now there are 22 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 of a responsibility was to support the business, and the other is the technology. Some things are really running better in, like if you're running dot net workload or you're gonna run machine learning or yeah, so you have You would have that reference off one cloud over the other. So >>your thoughts on that >>that 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 which is so we this failure domain idea, which is which is fairly interesting. How do I solve or guarantee against a failure domain You have methodologies with, you know, back in direct, connects or interconnect with DCP. 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, AP I 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, >>that's the availability piece just in your thoughts on that comment >>s actually multi clouds become something much more recent. In the last 6 to 8 months, I'd say we always kind of had a very dramatic like movie to Amazon from our private cloud is hard enough. Why complicated further but the realities of the business. And as we started seeing, you know, improvements in Google and Azure and different technology space is the need for multi cloud becomes much more important as well. As other acquisition strategies matured. We're seeing that companies that used to be on premise that we typically acquire are now very much already on the cloud. And if they're on a cloud, I need to plug them into our ecosystem. And so that's really changed our multi cloud story >>in a big way. I'd love to get your thoughts on the cloud versus the cloud because you know you compare them. Amazon's got more features. They're rich with features. I'll see the bills. Are people using them. But Google's got a great network. Google's networks pretty damn good. And then you've got azure. What's the difference between the clouds? Who? Where they involved with a 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, then Google and vice versa. What you guys think about the different clouds? >>Yeah, so my experience, I think there is a deep approach is different in many places. Google has a different approach, very developer friendly. And you can run your workload with the your network and spend regions. I mean, but our application ready to accept Amazon is evolving. I mean, I remember 10 years back Amazon's network was a flat network. We will be launching certain words and 10.0 dot zero slash right on, and the repeat came out >>with Life is not good. >>So so the VPC concept came on multi core came out, so they are evolving as you already let's start. But because they have lived start, they saw the patron and they have some mature set up on the ground, >>and 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 a global solution. I think Google also has evangelists third to market, and so has seen what Azure did wrong. It seemed, with AWS did wrong and it's made those improvements. And I think that's one of their big >>advantage. 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 original. I agree with you completely that that is the big number one thing. But if you look at it from the outset, interestingly, the inability or the ability for Amazon to limit layer to broadcasting 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, provide resiliency and make things seamless to users. All of that disappeared on DSO because we had to accept that at the VPC level. Now we have to accept it. At the one level, Google's done a better job of being able to overcome those things and provide those traditional network facilities to us. >>Just scrape and go all day. Here is awesome So I heard. But we will get to the cloud native Naive question. So I kind of think about what's not even what clients 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 in a data center, when is the new language you're talking about? The cloud impact. So that means SD win. The old SD Wan is kind of changing the new land. How do you guys look at that? Because even think about it. What lands were for inside of premises was all about networking speed. But now, when you take the win and make essentially land, do you agree with that. And how do you view this trend? Is it good or bad or ugly? What's what's your guys take on this? >>Yeah, I think it's Ah, it's a thing that you have to work with your application architect. So if you're managing networks and if you're a sorry engineer, you need to work with them toe expose the unreliability that would bring in. So the application has to handle a lot off this the difference in the latency, ease and and the reliability it has to be worked with application there >>land way and same concept as a B S >>E. 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 talk about a p, I 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 are talking about land scale versus land scale. The tooling doesn't work the same. The scale of that tooling is much larger on the need for automation is much, much higher in a way that it wasn't a land. That's where you're seeing so much. Infrastructure is code. >>Yeah, so for me, I'll go back again to this. It's bandwidth, and it's latency, right that that define those two land versus went. But the other thing that's comes up more and more with cloud deployments is where's our security boundary? And where can I extend this secure, aware appliance or set of rules Teoh to protect what's inside of it. So for us, we're able to deliver VM ref. So our route forwarding tables for different segments wherever we're out in the world and so they're trusted to talk to each other. But if they're going to go to some place that's outside of their network, then they have to cross a security boundary, and we'll reinforce policy very heavily. So for me there is. It's not just land when it's it's how does environment get to environment more importantly, >>as a great point and security we haven't talked about yet, but that's got to be baked in from the beginning of this architecture. Thoughts on security, how you guys are dealing with it. >>Yes, start from the base. Have app, Web security built in? Have TLS have encryption on the data in transit or at rest? But as you bring the application to the cloud and they're going to go multi cloud talking toe or the Internet in some places, well, have app, Web security >>I mean our principles. Day security is a day zero every day, and so 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 security at all times. >>Yeah, one of the cool trends that are, say, just as a side note was the data in use encryption piece, which is a home or fix stuff. Interesting. Alright, 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. 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 the 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 it's someone naive about implementing all this stuff. >>So for me, it's because we are 100% cloud for us. Its main thing is ready for the change, and you you will find new building blocks coming in and the network design will evolve and change. So don't be naive and things that are static you all 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 differently, and you need to think about it early enough so that you can become cloud native and really enable your business on cloud. >>Yet for me, it's it's being open minded, right? The our industry, the network industry as a whole has been very much I'm smarter than everybody else, and we're gonna tell everybody how it's gonna be done on the way we fell into a law when it came to producing infrastructure 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 months in some cases is really important. And so, you know, it's >>being closed minded native, being open minded. >>Exactly. And it took for me. It was that was a transformative kind of, uh, 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 got one more question for you guys. So good. It could be a quick answer. Um, what's the B s language? When you bs? Meter goes up when people talk about solutions, what's the kind of jargon that you here 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? >>So I have two lines out of movies that are really like it. I say them without actually thinking them. It's like 1.21 gigawatts of your of your mind. Back to the future, right? Somebody's going to the bank and then and then Martin Ball and and Michael Keaton and Mr Mom when it goes to 22. 21 whatever it takes those two right there, if those go off in my mind where somebody's talking to me, I know they're full of baloney. >>A lot of speeds and feeds a lot of speeds and feeds a >>lot of data instead of talking about what you're actually doing in solution ing for You're talking about What does this? This This is okay, 2020 A. >>Just take any time I start seeing the cloud vendors start benchmarking against each other. Your workload is your workload. You need a benchmark yourself. Don't Don't listen to the marketing on that. That's that's >>what triggered you in the BSP. >>I think if somebody explains you're not simple, they cannot explain you in simplicity. Then then it's all >>that's a good one. All right, guys, Thanks for the great insight. Great panel around >>Applause, right? >>Yeah. Yeah,

>>from San Francisco. It's the Cube covering. Get lab commit 2020 Brought to you by get lab. >>Welcome back. I'm Stew Minutemen, and this is get lab Commit 2020 here in San Francisco. Happy to welcome to the program. First time guests and TN Who is the co founder and CEO of Matter Most in. Nice to meet you. >>Thanks. Thanks for having me. >>Alright. S O. I always love. When you get the founders, we go back to a little bit of the why. And just from our little bit of conversation, there is a connection with get lab. You have relationships, Syd, Who's the co founder and CEO of get lab? So bring us back and tell us a little bit about that. >>Yeah, thanks. So I'm you know, I'm ex Microsoft. So I came from collaboration for many years there. And then, you know what I did after Microsoft's I started my own started a sort of video game company was backed by Y Combinator and, you know, we had were doing 85. Game engine is very, very fun on. We ran the entire company off of a messaging product. Misses, You know, a little while ago and it happens that messing product got bought by a big company and that got kind neglected. It started crashing and lose data. We were super unhappy. We tried to export and they wouldn't let us export. We had 26 gigs of all information. And when we stop paying our subscription, they would pay one less for our own information. So, you know, very unhappy. And we're like, holy cats. Like what? I'm gonna d'oh! And rather than go to another platform, we actually realized about 10 million hours of people running messaging and video games. Well, why don't we kind of build this ourselves? So we kind of build a little prototype, started using ourselves internally and because, you know, Sid was this a 2015 and said was out of my Combinator, We were y commoner would invent and we started talking. I was showing him what we built and sits like. You should open source that. And he had this really compelling reason. He's like, Well, if you open source it and people like it, you can always close source it again because it's a prototype. But if you open source, it and no one cares. You should stop doing what you do. And he was great. Kind of send me like this email with all the things you need to dio to run open source business. And it was just wonderful. And it just it is a start taking off. We started getting these wonderful, amazing enterprise customers that really saw what mattered most was at the very beginning, which was You know, some people call us open source slack, but what it really is, it's a collaborates, a collaboration platform for real Time Dev ops and it release. For people who are regulated, it's gonna offer flexibility and on Prem deployment and a lot of security and customization. So that's kind of we started and get lab is we kind of started Farley. We started following get labs footsteps and you'll find today with get lab is we're we're bundled with the omnibus. So all you have to do is put what your own would you like matter most on one. Get lab reconfigure and europe running. >>Yeah, I love that. That story would love you to tease out a little bit when you hear you know, open source. You know, communications and secure might not be things that people would necessarily all put together. So help us understand a little bit the underlying architecture. This isn't just, you know, isn't messaging it, Z how is it different from things that people would be familiar with? >>Yeah, that's a great question. So how do you get more secure with open source products? And the one thing look at, I'll just give you one example. Is mobility right? So, in mobile today, if you're pushing them, if you're setting a push notification to an Iowa, sir. An android device, It has a route through, like Google or Android. Right? And whatever app that you're using to send those notifications they're going to see you're going to see your notifications. They have to, right? So you just get encryption all that stuff in order to send to Google and Andrew, you have to send it on encrypted. And you know these applications are not there, not yours. They're owned by another organization. So how do you make that private how to make it secure? So with open source communication, you get the source code. It's an extreme case like we have you know, perhaps you can views, and it's really simple in turnkey. But in the if you want to go in the full privacy, most security you have the full source code. APS. You have the full source code to the system, including what pushes the messages to your APS, and you can compiling with your own certificates. And you can set up a system where you actually have complete privacy and no third party can actually get your information. And why enterprises in many cases want that extreme privacy is because when you're doing incident response and you have information about a vulnerability or breach that could really upset many, many critical systems. If that information leaked out, you really can't. Many people don't want ever to touch 1/3 party. So that's one example of how open source lets you have that privacy and security, because you because you control everything >>all right, what we threw a little bit the speeds and feeds. How many employees do you have? How many did you share? How many customers you have, where you are with funding? >>So where we are funding is, you know, last year we announced a 20 million Siri's A and A 50 million Siri's be who went from about 40 folks the beginning the aired about 100 a t end of the year. We got over 1000 people that contribute to matter most, and what you'll find is what you'll find is every sort of get lab on the bus installations. Gonna have a matter most is gonna have the ability to sort of turn on matter most so very broad reach. It's sort of like one step away. There's lots of customers. You can see it. Get lab commit that are running matter. Most get lab together, so customers are going to include Hey, there's the I T K and Agriculture that's got six times faster deployments running. Get lab in Madame's together, you've got world line. It's got 3000 people in the system, so you've got a lot of so we're growing really quickly. And there's a lot of opportunity working with Get lab to bring get lab into mobile into sort of real times. Dev up scenarios. >>Definitely One of the themes we hear the at the show is that get labs really enabling the remote workforce, especially when you talk about the developers. It sounds like that's very much in line with what matters most is doing. >>Absolutely. Madam Mrs Moat. First, I don't actually know. We're probably in 20 plus countries, and it's it's a remote team. So we use use matter most to collaborate, and we use videoconferencing and issue tracking across a bunch of different systems. And, yeah, it's just it's remote. First, it's how it's how we work. It's very natural. >>Yeah, it just give us a little bit of the inside. How do you make sure, as a CEO that you, you know, have the culture and getting everyone on the same page when many of them, you know, you're not seeing them regularly? Some of them you've probably never met in person, so >>that's a great question. So how do you sort of maintain that culture 11? The concert that get lips pioneered is a continent boring solutions, and it's something that we've taken on as well. What's the most boring solution to preserve culture and to scale? And it's really do what get labs doing right? So get love's hand, looked up. Get lab dot com. We've got handbook that matter most dot com. It's really writing down all the things that how we operate, what our culture is and what are values are so that every person that onboard is gonna get the same experience, right? And then what happens is people think that if you're building, you're gonna have stronger culture because, you know, sort of like, you know, absorbing things. What actually happens is it's this little broken telephone and starts echoing out, and it's opposed to going one source of truth. It's everyone's interpretation. We have a handbook and you're forced to write things down. It's a very unnatural act, and when you force people to write things down, then you get that consistency and every we can go to a source of truth and say, like, This is the way we operate. >>2019 was an interesting year for open source. There were certain companies that were changing their models as toe how they do things. You started it open source to be able to get, you know, direct feedback. But how do you position and talk to people about you know, the role of open source on still being ableto have a business around that >>so open source is, I think there's a generation of open source cos there's three ways you can really make money from open source, right? You can host software, you can provide support, and service is where you can do licensing, which is an open core model. When you see his categories of companies like allowed, you see categories like elastic like Hash corporate Terra Form involved with Get Lab that have chosen the open core model. And this is really becoming sort of a standard on what we do is we fall that standard, and we know that it supports public companies and supports companies with hyper growth like get Lab. So it's a very it's becoming a model that I'm actually quite familiar to the market, and what we see is this this sort of generation, this sort of movement of okay, there was operating systems Windows Circle. Now there's now there's more servers running Lennix than Windows Server. On Azure, you seen virtual ization technology. You've seen databases all sort of go the open source way and we see that it's a natural progression of collaboration. So it's really like we believe collaboration will go the open source way we believe leading the way to do that is through open core because you can generate a sustainable, scalable business that's going to give enterprises the confidence to invest in the right platform. >>All right, in what's on deck for matter most in 2020. >>It's really we would definitely want to work with. Get lab a lot more. We really want to go from this concept of concurrent Dev ops that get labs really champion to say Real time de Bob's. So we've got Dev ops in the world that's taking months and weeks of cycle times. And bring that down to minutes. We want to take you know, all your processes that take hours and take it down to seconds. So what really people, developers air sort of clamoring for a lot is like, Well, how do we get these if I'm regulated if I have a lot of customization needs? If I'm on premise, if I'm in a private network, how do I get to mobile? How do I get quicker interactions on? We really want to support that with instant response with deficit cock use cases and with really having a complete solution that could go from all your infrastructure in your data center, too. You know, that really important person walking through the airport. And that's that's how you speed cycle times and make Deb sec cops available anywhere. And you do it securely and in do it privately. >>All right, thanks so much for meeting with us. And great to hear about matter most. >>Well, thank you. Still >>all right. Be sure to check out the cube dot net for all the coverage that we will have throughout 2020 I'm still minimum. And thanks for watching the cue.