Image Title

Search Results for Devops Infrastructure:

Aparna Sinha & Chen Goldberg, Google | Google Cloud Next 2019


 

>> Announcer: Live from San Francisco, it's the Cube, covering Google Cloud Next '19. Brought to you by Google Cloud and its ecosystem partners. >> Welcome back everyone live here in San Francisco at Moscone, this is the Cube's live coverage of Google Next 2019, #googlenext19. I'm John Furrier with Stu Miniman, as well as David Vellante, who has been co-host, he's out there getting stories and getting all the scoop. We are here with two great guests, Cube alumni's, Aparna Sinha, the Group Product Manager at Google, and Chen Goldberg, director of Engineering, Google. Both the architects of the big wave that we're riding. Containers, kubernetes, and anthos. Guys, great to see you, thanks for coming on again. >> Aparna: Thanks for having us, great to be here. >> Chen: Thank you. >> So, you were smirking last night when we saw each other at the press gathering, knowing what was coming. I watched the keynote, it was awesome. I didn't get a chance to see the spotlight session you guys just had, but Anthos, obviously the rebranding and the additional integration points for making things run end to end, this is our dream come true, Devops Infrastructure as Code is happening, we've been talking about this for a while, you guys are behind it all, give us the update. >> So we've been hard at work over the last eight months since our last Next. Can you believe that it's only been eight months? Last year we were here announcing GK On Prem. This year we've rebranded CSP to Anthos and enlarged it and we've moved it to GA. So that's the big announcement. In our spotlight we actually walked through all the pieces and gave three live demos, as well as had two customers on stage and really the big difference in the eight months is while we're moving to GA now we've been working throughout this time with a set of customers. We saw unprecedented demand for what we announced last year and we've had that privilege of working with customers to build the product, which is what's unique really. So we had two of those folks up on stage talking about the transformation that Anthos is creating in their companies. >> I want to get to the customer focus a little bit later, but I want to just get it out on the record while you're here, because there's not a lot of time on stage other than the great demo Jennifer Lynn did. What actually is the difference, what's the new things, because obviously its a rebrand, some people might say, "Oh, they're just rebranding the announcement from last year", what were the new things, what are the new elements of Anthos, why is it important, what does it mean, what's under the covers, tell us what's new. >> Chen: So, first of all lets talk about, "What is Anthos?" Anthos is a Google opinionated solution that lets you right once, deploy anywhere. Really, the key thing about Anthos is choice. What we've been hearing from our customers, how much they appreciate choice in their journey to the cloud and modernization in general. The main thing that we have announced is that everything we have announced last year is GA. So talking about GKE On Prem, Anthos config management and our marketplace and the control plane from managing multiple classes, all of that has moved to GA. when thinking about choice, we've added new capabilities and one choice that customers are thinking about, "Do I need to choose a single cloud provider?" I had a discussion just yesterday with one of the customers and they said that when they exclude a cloud provider from their strategy, they're actually blocking their own innovation and that might get even a bigger risk for them. So we know that customers are adopting a multi cloud strategy. The big announcement here is that we are moving towards, or maybe we are even leaning more into multi cloud, we already had other solutions that we were talking about and definitely with Kubernetes and Istio talking about open API's, but we are leaning in towards multi cloud strategy, so that would be one. The second thing that talks about choice, is "How do we start?" One thing we are hearing from our customers is the importance that they want to innovate with what they have. So Anthos migrate, lets them take their existing applications, package applications that are running today on VM's and onboard to Anthos automatically and see value. So those are the top two announcements and I think the third one would be around all the partnerships, which is part of the people we've been working with in eight months. >> That's awesome. >> Stu: I'm sorry, the migrate piece, that's not GA yet, am I understanding? >> No, it's moving to beta. >> So Stu, you and I have been talking about applications, Renaissance, multi cloud, obviously is a reality for enterprises. Now you've got the hybrid model, this is kind of in the main themes of what this all means with anthem. So its holistically looking at the cloud, as you said, not just Google Cloud. This is a key nuance, its kind of embedded in the announcement, but its not just Google Cloud. >> That's right and I think in that sense, Anthos is a game changer, its not just an incremental improvement to something that's existing for customers. Its not like its just something faster or cheaper or adds more features, its actually something that allows them to do something they couldn't do before, which is, have a consistent platform that they can use to write once and deploy their workloads anywhere, On Prem, in GCP and that we had, but expanding that to any cloud, not just Google Cloud. >> I want to get your guys' thoughts here because you've got the brain and trust inside Google Cloud, because I've been talking on the cube about this and publicly. There seems to be confusion around what multi cloud means, and a company is an enterprise, there's a lot of things going on in the enterprise, so certainly the enterprise will have multiple workloads. There's certain situations that some people say, "Hey, this workload would be great on this cloud, this workload would be great on that cloud." So its not about having a cloud for cloud's sake. "We have to standardize on Google, we have to standardize on Amazon." Instead, what I hear, and I want to get your thoughts and reaction to is, I'd like to have a workload that has data, highly addressable, really low latency for this workload, and a cloud for this workload, but together its multi cloud, this seems to be a trend, do you guys agree with that? Is that something that you're seeing, is that the main message here? It's not so much standardized on the cloud, but have multiple clouds, pick the right cloud for the job, kind of philosophy. What's your thoughts, this is kind of a philosophical question. >> So this is exactly what we are hearing from our customers about their multicloud strategy and exactly what you are saying. This is actually for most of them is a reality, either because they have been organically building things in the cloud or they want to get to multiple geographies, and it's not only a cloud vendor, we need to remember that On Prem is where most of their workloads are still running and where they still need to innovate or when you talk about retail or banks, they have their branches and their stores where they need to have compute at. Really, services are spread all over. Now the question is, this kind of situation creates a lot of risk for our customers. Security risk and talent fragmentation, which are related, so how can I manage all of those environments? >> The risk is multi cloud, or one cloud? >> So multi cloud actually increases the risk even further, so they already have a multicloud reality. That's their strategy forward, but how can they mitigate risk with that reality? We are talking about kubernetes gave you portability of workloads, but how can you do portability of skills and making sure that your talent can really focus where it matters and not be spread too thin, so this is one example that I think Anthos is really unique about using it from our hosted control plane on GCP. >> So let the workloads decide what's best for the workloads and let the clouds naturally use kubernetes. >> Yeah, I mean one thing I've seen in our customer base is, you know the line of business wants to innovate and they want to use the best service for whatever it is that they're doing and the different clouds have different types of services, they have different strengths. So, you don't want centralized IT to say, "Hey, no actually you can't do that, you have to follow this policy." We've seen many examples where centralized IT is taking months to approve cloud services and they've got a backlong of hundreds of services that they need to approve. That's really slowing down innovation, and, "why is that happening?" Because you don't have a consistent platform that you can run and use across clouds. Like you said, kubernetes actually solves that and so that's why were introducing Anthos based on kubernetes, so that you don't have that risk, you don't have that fragmentation and you can innovate faster. >> Lets do one more question and with compounds to complexity is old procurement rules might slow it down. I've got to buy this. So the old baggage on procurement standards, Its kind of a moving train. >> Yeah, I mean enterprise has its policies, we've been talking to some of they largest banks, we had HSBC on stage with us, we had (mumbles), which is one of the largest grocers, we have kohls, these companies have policies and they have compliance requirements and these are very valid compliance requirements and they need to be adhered to. Its just, how can you speed that process up, and if you have a platform that actually spans environments, it doesn't look different in each environment, you can imagine that simplifies the process, it simplifies the approval process because the platform's already pre-approved and then new services as they come online, if they follow a certain pattern, they're kubernetes approved services, then it's much easier to approve them and it's much easier to unlock that productivity without increasing risk. >> If I could poke on that just a little bit (mumbles) approved services isn't a term I've heard yet. There are dozens of providers that have kubernetes, Anthos I know is different but if I go out there and use kubernetes from a different cloud provider or a different service provider. Kubernetes is not a magic layer, everybody builds lots of stuff on top of that and a concern is if I just have a platform that spans all of these environments. There's skillset challenges and do I also get a least common denominator. Cloud is not a utility, GCP is very different from the other clouds, how do I balance that and how do I make sure that I'm actually being able to get the most out of why I choose a specific platform or cloud. >> That's where Anthos is that layer that actually is more than kubernetes. We have, in Anthos, an opinionated platform from google that utilizes kubernetes but it isn't just pure kubernetes, as you would experience it from the open source with the fragmentation, we're working with certified kubernetes distributions and we've got this marketplace where the applications that are in the marketplace have been tested and certified and are supported by a set of partners as well as by Google Cloud to run on these different distributions that you connect and register with Anthos. >> To give maybe another perspective of that, what we have seen with kubernetes is that customers do appreciate that consistency. They have been demanding, for example, that all kubernetes distribution will be conformed. We had that announcement when we were on stage today about consistency and how we can integrate PKS into Anthos. I think what customers are telling us, they don't want us to innovate in that layer. So they appreciate us using open API's and using sensibility which is predefined and actually allows that interoperability of services and this is something that is really in the foundation of Anthos. >> Well you guys have done a great job, we've been following the progress from day one and watching the foundation of Google Enterprise. You guys have been big contributors, congratulations to your work, it's great to see the progress and it seems to be, the train's moving faster on the tracks, so congratulations. I guess my final question for you guys is, boil down Anthos. To the folks watching that are in IT, they're trying to solve some problems, a lot of people realize and wake up, "wow I've got multiple clouds." That's not (mumbles), that's reality. They see billing statements from multiple vendors how they still want maybe hybrid, what does Anthos mean to those people? What is it about, what is it? I'm trying to get bumper sticker. What's the bottom line, what is Anthos? >> So Anthos gives you a choice without the risk. That means that they can choose an existing service or a new green field service to use, On Prem or in the cloud. Containerized or uncontainerized, and they can build on top of that at their own pace. So that's the choice and they can mitigate risk by giving those tools to manage that consistently. The other thing I would say for something that we are not talking a lot about because we are focusing about technology and requirements and constraints is what we hear about our customers that Anthos is good for the engineering teams, and what we hear our customers say, that because they are choosing this technology, their talent is appreciating that they can use the best and latest technology and their skills are portable to other areas as well and they can attract the best talent. That to me is a very big value for us that are looking to do digital transformation. >> I'll take a crack at it as well, so Anthos is Google's opinionated solution for hybrid and multi cloud and it is like Chen said, something that mitigates risk and gives users choice so that they're not locked in to a particular cloud and instead, they can build once and deploy anywhere. From a technical standpoint, it's three things. There's a multi cluster, multi cloud, management plane, that's hosted in Google Cloud. Number two, there's a service management layer which actually bridges your monolithic, migrated services with your green field services that are containerized and treats them all as services that you can secure, manage, and control, and then number three, we have an awesome marketplace from which you can deploy Google Services, you can also deploy partner services, and you can deploy them into anywhere that Anthos is registered and can run. >> So Anthos embraces the cloud, all clouds, all services. >> Anthos embraces the user and it puts the user first. >> Does this benefits, good choice, lock in options, negotiating contracts, developers love it, ... Guys congratulations, thanks for the insight, love the explanation of Anthos, thanks for sharing, appreciate it. (mumbles) Thanks for coming on, cube coverage here live in San Fransisco, we're breaking it down, Google Next 19, day one of three days, there'll be live cube coverage. We have all the leaders, google executives, all the engineers, coming on to explain to us what's happening, thanks for watching, stay with us for more after this short break. (funky music)

Published Date : Apr 9 2019

SUMMARY :

Brought to you by Google Cloud Both the architects of the big wave that we're riding. and the additional integration points and really the big difference in the eight months is What actually is the difference, is the importance that they want to innovate in the main themes of what this all means with anthem. that allows them to do something they couldn't do before, is that the main message here? and exactly what you are saying. So multi cloud actually increases the risk So let the workloads decide based on kubernetes, so that you don't have that risk, So the old baggage on procurement standards, and they need to be adhered to. and how do I make sure that I'm actually that are in the marketplace have been tested and certified and actually allows that interoperability of services and it seems to be, the train's So that's the choice and they can mitigate risk so that they're not locked in to a particular cloud all the engineers, coming on to explain to us

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
David VellantePERSON

0.99+

AparnaPERSON

0.99+

Stu MinimanPERSON

0.99+

San FransiscoLOCATION

0.99+

HSBCORGANIZATION

0.99+

Chen GoldbergPERSON

0.99+

GoogleORGANIZATION

0.99+

John FurrierPERSON

0.99+

ChenPERSON

0.99+

twoQUANTITY

0.99+

Aparna SinhaPERSON

0.99+

Last yearDATE

0.99+

last yearDATE

0.99+

GALOCATION

0.99+

San FranciscoLOCATION

0.99+

Jennifer LynnPERSON

0.99+

AmazonORGANIZATION

0.99+

eight monthsQUANTITY

0.99+

yesterdayDATE

0.99+

three live demosQUANTITY

0.99+

googleORGANIZATION

0.99+

two customersQUANTITY

0.99+

StuPERSON

0.99+

oneQUANTITY

0.99+

AnthosORGANIZATION

0.99+

This yearDATE

0.99+

three daysQUANTITY

0.98+

hundredsQUANTITY

0.98+

three thingsQUANTITY

0.98+

todayDATE

0.98+

MosconeLOCATION

0.98+

BothQUANTITY

0.98+

last nightDATE

0.97+

AnthosTITLE

0.96+

third oneQUANTITY

0.96+

one exampleQUANTITY

0.96+

Google CloudTITLE

0.96+

one more questionQUANTITY

0.95+

second thingQUANTITY

0.95+

two great guestsQUANTITY

0.95+

two announcementsQUANTITY

0.95+

one choiceQUANTITY

0.95+

KubernetesORGANIZATION

0.94+

each environmentQUANTITY

0.93+

Devops InfrastructureORGANIZATION

0.92+

dozens of providersQUANTITY

0.92+

one thingQUANTITY

0.91+

one cloudQUANTITY

0.89+

Number twoQUANTITY

0.89+

Google Cloud Next '19TITLE

0.88+

CubeORGANIZATION

0.87+

day oneQUANTITY

0.87+

Google ServicesORGANIZATION

0.84+

firstQUANTITY

0.81+

number threeQUANTITY

0.77+