(upbeat music) >> Welcome back to Las Vegas Lisa Martin live here with David Nicholson. We're at AWS reinvent 2021, this an outstanding event. There's a lot of people here, tens of thousands. And this is probably one of the most important and largest hybrid tech events that we're doing this year with AWS and its massive ecosystem of partners. We're going to be covering this two live sets, two remote studios, over 100 guests on the CUBE at this re-invent and David and I are pleased to welcome Giorgio Vanzini next the vice president and global head of partners and alliances at DXC, Georgia Welcome to the program. >> Thank you for having me. >> Talk to us about what's going on at DXC, what are you in AWS doing together with what's the scoop? >> Yes Well, some exciting things are happening between AWS and DXC, which is we're really focusing on our customers that we have especially in the banking and capital markets, but also automotive. And then also we were a launch partner today with the AWS mainframe modernization right, and so we're focusing on mainframes as well. So exciting spaces for us to go collaborate and work with AWS, for our customers. >> Talk to me about some of the things you know the last 22 months have been quite challenging, quite dynamic and we've seen such a massive acceleration to the cloud. What have you seen from your perspective? Are you seeing customers in every industry that have really figured we've got to do this now because if we don't, we're going to be out of business? >> Yes, you're absolutely correct. We've seen a dramatic acceleration of people wanting or customers wanting to move to the cloud public and private, and an acceleration of assistance that they were requesting from a global systems integrator. So what we've seen is you know, part of our clouds ride strategy that we have, really understanding what does the customer need from a strategy perspective, from a business value perspective and the technology perspective, and AWS has been a great partner with us to actually accommodate all of these kinds of things and the announcements that you had today, you know, just substantiate kind of that fact as well. >> Can you double click on the Cloud Right approach, talk to us about what that is, why it's important and what are some of the outcomes that it's helping customers to generate? >> Absolutely love to Cloud Right is really DXC's strategy to take the customers on the journey from the mainframe to the cloud, and to customize this because every customer is different. They have different requirements, different environments, different business strategies. So therefore the Cloud Right approach is really customizing it for the customer. What is the right business strategy? What is the right technology strategy? And then migrating them over into the cloud as well. Keeping in mind that again, customers are specific, industries are specific. You know, data requirements are different analytics are different, you know, government requirements are different. So you need to those in mind when you transition customers over into the cloud space. >> Right, from a data residency, data sovereignty and all of the different rules and regulations that are popping up that are kind of similar to GDPR for example, that's a big challenge, but one of the things too that's happening Giorgio is that every company to be competitive these days has to become a data company, right? There's no choice, you've got to be data-driven, you've got to have a data strategy at the core of the business, otherwise there's a competitor in the rear view mirror, who's ready to take your place. >> That is absolutely correct, and so that's part of our Cloud Right strategy is understanding what are the business requirements from the customer? Understanding their competitive edge and migrating them over. Because in many instances, to your point, they have huge reams of data, petabytes of information of data, but really making sense of it, so running the analytics on it and having the business insights. So helping the customers understand that, but then also understanding of like, what are the key business requirements that they have? Which applications to migrate and which not to migrate? >> So I'm curious, you mentioned that you're a launch partner for mainframe modernization. That's sort of one slice of and very important slice of some organization's business and migration strategy to cloud. I'm curious what the DXC blend is between standardized offerings and bespoke services and how you manage that? Do you have a thought about that? Wouldn't it be great to have small, medium and large and have people click on it? >> Yes here's a T-shirt for you, which size are you? Now I'm actually glad you asked me that question because that's exactly going to the core of the Cloud Right strategy, and the Cloud Right really means that it's like, which T-shirt size is correct for you? Right. This is the question that we just addressed which is it has to be bespoke because one size does not fit all. And so understanding the customer requirements of do we need to move the data to the cloud? Or do we move to need a subset to the cloud? Do we need to move part of the business applications and which ones and in which order? Right? And so that's why I think we bring something to the table in the AWS mainframe modernization, which is unique because we have an end to end kind of approach from a planning to implementation, to execution and running as well. So I think DEX is uniquely positioned with our Cloud Right strategy. >> One of the things AWS Giorgio talks about is not being custom but being purpose-built. Talk to me about kind of compare contrast that with bespoke solutions, industry specific, obviously customers have specificities. Do you see a difference there between purpose-built under bespoke or are they aligned from your perspective? >> Yes, I do agree that a to technology layers are definitely common layers, horizontal layers, right Where I think you have bespoken limitations on the business strategy and the business rules. And so you have to understand what business is the customer really in and how to implement the business rules into the technology stack as well, and bringing it all together. So while the technology I think goes horizontal to your point right, you know, compute and storage is the same. Wherever you go the bits are the same, however how they're utilized and how you use them for your customers and your interaction is completely different from customer to customer and industry to industry, as you guys know as well. >> You know, it can be, it can be really disheartening working in this space when you think of 475 different kinds of instances and how important it is to get that right for a customer and how much they don't care. Ultimately they don't want to hear about it, they don't want to know, but they want you to get it right, so that it doesn't matter. So it's this irony of all of the work that people have to do like at DXC to make those details not matter. Any thoughts on that? Do you, are you a dejected because of that at all? >> Well, that is part of the value that we bring, right? >> David: Sure. >> To your point, absolutely the customer doesn't care in quotes, right? Just make it work for us and run it smoothly. On the other hand, we're on the hook to make sure that all the different partners that we have, that we integrate including AWS, right. Run smoothly and coherent and are up, you know, 99.999% of the time obviously right. And so the customers do care about our you know, interaction with them as well while AWS is always there. >> One of the things that we talked about a little bit ago is every industry had to pivot right. Dramatically the last 22 months or so. And we've seen every industry cloud is no longer a nice to have We've got to be able to get there, but you mentioned a focus in banking, and I think automotive, I'd love to get your perspectives on what some of the things are the opportunities that DXC sees in those particular industries, as opportunities to modernize. >> Yes, we latched on to banking and automotive because those are ripe for transition and the customers are willing to take the steps there as well. It doesn't mean that other industries are not relevant like, you know, consumer or retail or you know, technology and, and manufacturing. However, especially in automotive I think we have a unique positioning where we have the majority of the OAMs car manufacturers worldwide as customers, and when you think about AWS, you think about the utilization of the information that comes back from telematics information and customization, right. Petabytes of information that comes back from every device, which is a car and what kind of service you can provide there. So it's an industry you know, we talked about Tesla early on as well, right It's an industry that ripe for software and software updates. very similar you see a lot of things happening in the banking capital market space, where they're moving you know their customer base into new spaces as well. Just think about all the NFTs, those are happening, all the FinTech that's happening, right. So the, the banking capital markets companies have to, you know, have an evolution going on right, and assisting them in this evolution is as part of our strategy. >> So you're responsible for global partnerships and alliances DXC would be considered a large global systems integrator. The world is obviously moving in the direction of cloud. We've got the three big players AWS, and the other two I can't think of their names while I'm sitting here in Vegas right now, how do you balance what you do with those, with a variety of providers, for customers, and are you going to market primarily as DXC with the DXC relationship with the customer? Or in support of those cloud vendors that have essentially technology that if left unimplemented is essentially worthless, right I mean you, you bridge the divide between the technology and the true value of the technology, but are you the primary seat holder at the customer table, or is AWS the primary seat holder? Or is it a little of both? Long-winded question I apologize but I think you understand what I'm saying. It's an interesting world that we live in now. >> It definitely is, and if I wouldn't know you better I would say it's a trick question, but in all seriousness, we really are customer driven just like AWS as well right so, we really are trying to do the right thing for the customer. Hence our Cloud Right strategy, where we don't have a cookie cutter approach or saying just go do the following five things and you're going to be fine. We really want to look at the customer and say, what is important to you? What is the timeframe you're looking at? What is the strategic imperative that you have? What data do you have to move? You know, what system do you have to leave behind? And then do the right thing for the customer literally right. And so in this instance, absolutely you know, in my role AWS plays a huge role as you know is one of our core hyper scaler partners, a very good partner, we love AWS. And so making sure that they're always going to be there as part of that infrastructure is part of our strategy. >> You mentioned, oh sorry Dave >> No, I was just saying it makes sense. >> It does make sense in terms of being customer first, we talk with AWS, you can't kind of have an interview with, with one of their folks without talking about that. We work backwards from the customer first. This customer obsession, it sounds like from a cultural perspective, there's pretty strong alignment there with DXC. >> Exactly right, so I think from that perspective we share the same DNA where we look first to the customer and then say okay, how do we deduct what is right for the customer and implement it that way right, Because in many instances as you know, you mentioned the, the two other hyper scaler that we don't talk about, customers usually don't have a single source kind of approach, right They usually have a dual approach. And so while we have to work with that, there's preferred vendors that we engage with, right. And so clearly AWS is one of our preferred vendors that we engage with. >> Can you share an example? I'd love to know a customer that's taken the Cloud Right approach applied really kind of in a textbook way that you think really shows the value of DXC. Any customers, but even by industry if you don't want to name them, come to mind that really show the value of that approach. >> Yeah, So we, we just concluded a major migration from one of our leading insurance companies, a global big company that you know is similar with my birthplace. But what we really did is a Cloud Right approach of migrating them from their legacy mainframe and virtualized systems that they had, to a cloud approach. And in the process of doing this you know, we reduced their overall operating expenses, their cap X expenses obviously but also reduced their overall budget about 30% reduction by moving them to the cloud. Again during the Cloud Right approach of understanding what exactly to move in, which timeframe and what to leave behind right, Because in many instances, customers don't have an exit strategy. They rush to the cloud, but then leave their you know old legacy behind and like oh, what are you going to do with this? And so you need to have a comprehensive end to end system strategy of like, what do you want to leave behind? When do you want to sunset it? And when do you want to migrate certain things over as well? >> That's got to be quite challenging for I would assume a legacy historied insurance company been around for a long time, lots of data, but culturally very different than the cloud mindset. >> You bring up one of those soft skills, right. Which is the cultural aspect of talking with the customers of how do we migrate you? It's not just, and that's why I said it's not just a business decision or a technology decision. In many instances, you affect people's life as well. When you think about old systems administrators that were working on mainframes. Now if you move everything to the clouds, they become obsolete. So rescaling the workforce and having a comprehensive plan is part of the soft skills right, Where you think more comprehensive about the customer, it's not just technology it's really is the full experience right At 360 what happens to the people? How do we migrate the people? But also setting expectations with top management, for example right of saying, how is this going to change our business? What new opportunities are going to be there? So those are all the soft kind of skills as well. >> One of the things that struck me this morning during the AWS keynote is just all of the innovation that that goes on. But AWS really is a flywheel of the customer and all the opportunities that their customers create for AWS, and the opportunities then that AWS technologies create for the customers across industries I just thought that I just kind of really felt that flywheel this morning when Adam was talking about all of the things that they're revealing, you must feel the same as a partner. >> I do, and I I'm a tech geek, so I'm totally excited about this, and it you know it feeds my soul because I can remember when, you know, when we first had analytics with you know Redshift rights and then customers are coming back and going like, well could we do something that is real time? Because we have requirements in this, and then CAFCA came out right, as a new service and I'm like okay, great right, and so we're really there to embrace you know, every new service that comes out from AWS. Which is fantastic, right I mean the speed and agility that comes out with AWS and we totally embraced that for our customers. >> Awesome, Georgia thank you for joining David and me today talking about what's going on with DXC, your partnership with AWS, Cloud Right, and how you're helping customers get Cloud Right. We appreciate your insights and your time. >> Thank you, I appreciate it too, thank you. >> All right. For David Nicholson, I'm Lisa Martin. You're watching the cube, the leader in global alive tech coverage. (upbeat music)

(calm and chill electronic music) (moves into upbeat and energetic electronic music) >> Announcer: Live from Austin Texas, it's theCUBE. Covering DockerCon 2017. Brought to you by Docker and support from its ecosystem partners. >> Welcome back. I'm Stu Miniman with my co-host and singer and, you know, lyricist everyone once in a while, Jim Kobielus. >> Partner in crime. >> And happy to bring back to the program Giorgio Regni, who is the CTO of Scality. So good to see you again. >> Hey. Hi Jim, Hi Stu. Very nice to see you again. >> So Giorgio, I interviewed you at Amazon Reinvent. So we talked about where you fit in the cloud environment. So here at DockerCon, you bring us up to space. You're a software defined storage company, where do containers and Docker fit into the offering that you have? >> Absolutely. So with software defined storage for the enterprise, one of our goal is to simplify storage operations because it's hard to actually build a verified scale system, how can we make it easier for our customers to use, right? And one other thing that containers give us is the ability to easily package your software and deploy it anywhere. For example, we have options. Where do you want your interface to be for storage? Should it be on the client side, should it be on the server side, should it be somewhere else? With container, it's very easy to automate. And one container can do a lot of things, right? So, it's pretty easy. >> Yeah. And talk about how scalability fits into your environment. My understanding is you work with Docker Swarm, do you also work with Kubernetes? Where does that fit in? >> So we talk about an announcement we made today. Just before I do that, just a quick. So the container, we follow the imagable container design. So when you have a container, you can kill it any point in time, right? And another container will take over. So there's nothing in our architecture that's a single point of failure. So with Docker, it's very easy to do. Which we did before, but Docker simplifies all these operation aspect for us. >> Alright. And so the announcement is, did you also do Kubernetes then, or is it just the Docker Swarm right now, or? >> Yeah, so there is a container automation war. We haven't picked a side yet. >> Okay. (Giorgio chuckles) >> Yeah, absolutely. Talk to us about your customers. How much is it a pull for them, asking you about containers? How much? Is it just something your building it to your architecture because it makes sense going forward? >> So we work with very large enterprises. They don't know what the other department is doing. So sometimes you talk to a storage team and they try to tell you we never deploy containers. But then if you talk inside a company, you will see that another group has deployed containers for the last two years in production, and they actually have a support contract with Docker, they have an enterprise deployment. And so you have to find out is there Docker experience. And 99% of the time, there is Docker experience. >> Stu: It reminds me of Linux a lot. >> Yes, exactly. >> You know, 15, 10 or 15 years ago, you talked to a big group, "Are you doing Linux?" and they got no, and they're like "Wait, "Bob's been doing Linux a bunch." And we are doing it and everything. (Giorgio chuckles) So yeah, absolutely. >> Giorgio: It is the same thing, yeah. >> And this been such a huge explosion of what's been happening. You know, I've talked to some of the vendors here that have been working with containers for, you know, eight, 10 years almost. But with Docker, it's really helped, ya know, just bring it to the masses. So, yeah, can you maybe speak to how its changing your environment as CTO, how it influences your vision of the future? >> Yeah, so as a CTO, it allows us to go from the development platform of a laptop of developers to via simple one server deployment for our open source versions, but can start on any VM or any one machine, down to a distributed system with thousands of servers and hundreds of petabytes. And it's all the same container. So the flexibility is huge. And for continuous delivery, continuous integration platforms that we have, being able to use the exact same code from a laptop workstation to the actual deployment improves quality a lot. >> Alright. And Giorgio, the keynotes today talked about a lot of open source things there, there's the Moby Project, there's Linux kit. You know, are you guys involved in any of the open source? How are your customers, you know, embracing open source these days? >> So Dockers, we're using a lot of software. We can not take everything and bring it to enterprise. You know it's not, we're a software company that sells products, so we don't actually also own platform. It's our customers. So we need to go a little bit slower. So Docker is faster than ever with these new features. But that means that official (mumbles) that was released last year, like Swarm, now is ready to be used in production for all customers. And so that brings me back to the announcement from today. So the last time we talked in Las Vegas our open source was new and we had $50,000. Now we have $250,000. So in less than six months I think its four month and a half we added $200,000. And one of our reasons for that is that it's so easy to use it with Docker. And then people in the community were telling us that they need to be deployed in a, you know, a (mumbles) fashion, so being able to lose a machine and continue having the storage working, which makes sense, but not at the scale of a wing. Not at a scale of our multi petabyte systems. So something in the middle. And so we tried to look at developing our own automation, our own fault tolerance, and we said "Wait a minute. Docker is doing that." They built Docker Swarm, that does exactly what we wanted to do. So can we use that? So our videos from today is you can actually deploy our storage system using Docker Swarm, so if you come online, it will automatically be fault tolerant. If you lose a machine, it will start from another machine. And it all works, load balance automatically. And with security as well because communication can be unencrypted. So it's all of these benefits. By just using Swarm, we don't have to code anything. So we'll follow up on that. >> Giorgio, Solomon talked about this morning. Docker will be where you want it to be. So you know, on premise, in the public cloud, around. You talk a little bit, you know, your software, the breath of support you have. We talked to you at AWS, think you guys support Azure. What's driving you to certain environments, what are your customers doing, and what is that breathe that you guys offer? >> So a lot of things that Solomon said resonate with our customers. So one things is that you don't want to be stuck with one platform. You want the liberty to be able to pick and choose and change. And so storage is very sticky, so if you have a petabyte somewhere, it's going to be hard to move. But what you can be sure is the next year, it's going to be two petabyte. So when the extension comes in, you want to be able to select your hardware vendor for private, but also for public. What about if you could decide the next four petabyte go on Google Cloud Compute and the next five petabyte go on Azure so that you're not stuck with any of them. And so what we are realizing, but first we need to talk about that, is the ability to deploy your SV service, so our objects, your service, and target within some instance multiple storage backend. And it can be local, so local volumes, drives on your machine, very simple stuff. Maybe even a NFS, ZFS mount point works as well. It can be public using AWS. And we're adding Azure and Google Cloud Compute. So the same S3 code base can actually give you different location, and the location can be hybrid, local, private, public, you name it. >> Another key focus that Docker talked about, especially in the open source community, is security. Can you can speak to how security fits into your environment? Anything in your announcement that enhances the security pieces? >> Yes. So there is a lot of key management to be done. So access keys, identification key, SSL keys. And each vendor is going to build their own. They're trying to think about their own ways to actually store this sensitive information. With Docker, we haven't done it yet, but what Solomon said, there wasn't any keys there. What about if you use Docker as your security identification provider, so it takes one shop for everything else? And this is something I am going to look at. We haven't implemented it yet, but I'm going to look at it. The other thing that was said, I think it was in it, but that is portability. So we developed our own identification engine called Volt, which actually implements via Amazon IM interface, so an identity and access management. So it's pretty standard. But if you use Volt, the same identification taken for local will work on AWS. It will also work on Azure and also work on Google Cloud. So as an IT admin, I can just use mine to deactivate, connect it to a security Volt. And if a user leaves a company I can just delete it from a directory and it will disappear from all the clouds in one big portable transparent way. So yeah, this is kind of the things we look at as well. >> Jim: With multi level access control and roll based. >> So groups, roll based-- >> The delegations and so forth? >> The delegation is in there as well. So it's a big bet. Last year we decided to implement IM, which nobody else has done. And it pays off a lot because a lot of our customers are banks, insurance companies, and they need that level of security. Alright? It's a big advantage. >> Now Giorgio, one of the big things that's been talked about for the last six months or so is how things like IoT are really going to drive edge computing. I think back to the early days of object storage and I am curious how that whole development fits into what you're doing and how you think about storage. >> So we're looking at IoT very closely. There's a lot of volumes, but with volumes arrived after the data has been crunched, you got some sort of consolidation, right? And the object storage is perfect for material. So lets say we daily start a VH with very precise granularity. Then it get compressed into some kind of time service data. And this keeps very well in object storage. For the edge storage itself, I don't think there is a solution today. And there's no standard as well. So I'm looking at this and seeing what was going to happen. But I think object storage are great for for storing all of the archive but not good for the real time IoT data. But I'm still looking into what standards are going on in the archives. >> You have federated object storage for the fog, ya know, and the IoT. >> It's both a database type workload and object storage, so it's fascinating. But there's no answer yet. I don't think so, unless you guys tell me you've seen it. (laughs) >> Jim: I'm not aware of it. >> Okay Giorgio, so you've got the announcement. What other things can you tell us Scality, what's going on this week? Have you had any customer conversations this week yet that have stood out to you? >> Yes, we have a few partners at DockerCon, so it's great to be able to meet them here. I'm also looking at automation. So Docker Swarm is one, Swarm kit, but there's also Kubernetes and Mesosphere. They are all here this week, so I'm going to talk to them. And HP, which is one of our partners, is here too, so we're going to talk about this as well. And I need to find some time to understand the security model we talked about. >> Alright, well Giorgio, we really appreciate all the updates here. Want to give you a final word on what's exciting you. You talked about some of the partner things, but anything else you would want people to take away from this show? >> Yes. So I think the hybrid model for storage makes a lot of sense because you don't want to be stuck to a provider. And I was just going to say that in a few months, so in June, we're going to make a big announcement. And that will show that with Scality, you can leverage any cloud and automatically like manage your data on multiple providers. And we're going to give a hint of that next week at NAB. Where I'll be presenting a large customer of some of the prototypes that we've been working on. >> Well Giorgio Regni, really appreciate you to talk to you again. We'll be back, wrapping up day one of Docker Con 2017. You're watching theCUBE. (calm and chill electronic music) >> Thanks for watching theCUBE.

>>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.