Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2018 (Copenhagen), 4 May 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Keynote: Re-thinking Networking for Microservices - Lew Tucker, VP/CTO Cloud Computing

Description

Want to view more sessions and keep the conversations going? Join us for KubeCon + CloudNativeCon North America in Seattle, December 11 - 13, 2018 (http://bit.ly/KCCNCNA18) or in Shanghai, November 14-15 (http://bit.ly/kccncchina18)

Keynote: Re-thinking Networking for Microservices - Lew Tucker, VP/CTO Cloud Computing, Cisco Systems, Inc.

Its been said that Istio is a “network for services, not bytes.” What does that mean and what does a service mesh offer to developers and operators of microservices? We will discuss this and how Istio enables a better model for developing distributed applications in a multicloud world.

About Lew
As VP/CTO of Cloud Computing at Cisco, Lew is responsible for shaping Cisco’s strategy and products in cloud computing and leads several of the company’s open source initiatives. He also serves as a member of the OpenStack Foundation board of directors. Lew brings to the CNCF more than 25 years of experience in the high-tech industry, ranging from distributed systems and artificial intelligence to software development and parallel system architecture. Prior to joining Cisco, Lew was VP/CTO Cloud Computing at Sun Microsystems where he led the development of the Sun Cloud platform. While at Sun, Lew was also a member of the JavaSoft executive team, launched java.sun.com, and helped to bring Java into the developer ecosystem. Intrigued by the software-as-a-service model for application delivery, Lew joined Salesforce.com and led the development of Salesforce.com’s AppExchange. In the 1980’s Lew was a research director at Thinking Machines, where he developed algorithms for AI and machine vision for the massively parallel Connection Machine. Lew moved into technology following a career in Neurobiology at Cornell University Medical school and has a BA in Biology from Cornell and a Ph.D. in computer science from New York University.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.

A

Welcome everyone- it's really great to be here again and what I wanted to do is spend a little bit of time today. Rethinking what networking means for microcircuits as I. Hopefully you do know that Cisco is one of the leading providers of networking gear, powering data centers and in the internet itself. But did you really know we're also major contributors and sponsors of the leading open source communities, many of which you are seeing here today from all of the array of projects in a cloud native CN, CF and OpenStack Linux, Foundation, Cloud, Foundry and others?

A

We see their open source as a key part of Cisco strategy moving forward in the software and services and, of course, their customers are all going to the cloud. So what you know this is what prompted us to start reaching out and forming partnerships with several of the major cloud providers such as Google, and this is where we we see. Customers are going and they're trying to figure out how do they adapt their IT infrastructure for all of the new phenomenon and new services they can advantage of in the cloud itself.

A

So, of course, kubernetes plays an integral role to this, and so what we've done recently is we introduced a Cisco container platform, which is the kubernetes framework running on Cisco's, hyper flex systems, and this allows you to have a consistent environment, whether you're running kubernetes, on-premise or in the cloud, and just yesterday we also announced kubernetes support francisco cloud center and app dynamics. In this way, you can have a consistent, consistent environment for your applications in the data center or up in the cloud of your choice.

A

A lot of this is built on a lot of the underlying technologies as well, that cisco provides in terms of csr, 1000v, virtual routers, virtual switches to increase the performance and allowing these environments to stretch over more and more different application areas and, of course, well. A lot of what we're talking about in this con as a cloud native computing is really driving this fundamental shift in the way we think about building applications, we've gone from monolithic applications through hybrid applications and now into breaking applications up into a set of Micra services.

A

However, when we do this now, networking becomes an integral part of the application distributed. Computing is not easy, whereas we want an application team to focus on a very simple service. Now, all of a sudden we've introduced complexity because these services have to communicate so do we have the right model for networking that we need a new layer in the stack to may not work for the development of Micra services, and maybe it's not about stacks at all. Maybe what we really should be thinking about.

A

Is there a networking service that we need to allow this advantage to take place in terms of building micro services? So, let's take a simple example: here's just four simple services, a web server, content, server payments and order management and things get to be pretty easy. It looks very simple: we need to have kubernetes scale these up independently and we think about web serving. Of course, we know there's a lot more to that than the no code example that we saw ask Elsie make. But here you have to handle, for example, authentication.

A

You have to be able to manage connections, you have to be able to do load balancing you have a lot of things that you need now in a micro services world. However, not only is this web server have to handle all these communication issues, but so does the content server so does a payment server so does the order management server. Therefore, what was very very simple now has become very complex and much harder for these individual independent development teams to make progress when it'd be better.

A

If you could offload all of those capabilities, all of those issues of networking, essentially the experts and have them run that as a service mesh. So the idea of a service mesh is to take over all of the aspects of inter service communication, driving policy, secure services and so forth.

A

This is really radically different, and what we've done is that we've done something in computer science. Over and over again, we've abstracted away the details of service to service communications, allowing consistent policy and being able to manage now these services without changing one line of the service code.

A

This makes it much easier for IT operations as they get to deployed so I think that you'll see here and I welcome you to take a look at the number of different options you have for implementing service messages from SPO, envoy, linker, D and so forth, and an sto architecture in itself, as you get a conceptual picture of this, consists of a control plane and then a data plane where the traffic actually flows, but one of the places that we're taking it, cisco and through our contributions is stretching this notion across public and private clouds and multiple kubernetes clusters.

A

There's different proposals in the community that we are hashing out right now how to make this a seamless experience that will really allow us to extend Micra services across multiple clouds, and this I think will bring us into where we really are changing the way applications are being developed. We really want to get to a point where what we're doing is assembling ready-made battle-proven harden'd services to provide those those applications out to our users and delivered anywhere in the clouds.

A

So I welcome you to come by our booth in the showcase area and we'll talk to you about how we are enabling a micro cloud world made possible. Thank you very much.