Cloud Native Computing Foundation CloudNativeDay 2016 (Toronto), 6 Sep 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How Cloud Foundry & CNCF are Collaborating - Abby Kearns, Cloud Foundry Foundation

Description

How Cloud Foundry Foundation & Cloud Native Computing Foundation are Collaborating to Make the Cloud Foundry Service Broker API the Industry Standard.

Services are required for developers to create and run apps. A service can be a database, messaging, or API gateway. Running apps at scale requires a vast number of services. As such, services are integral to the success of a platform. For Cloud Foundry, the ability to connect to and manage Services is a crucial piece of the platform.

Within Cloud Foundry, services connect to the platform via the Service Broker API. The Cloud Foundry Service Broker API offers an elegant solution for connecting Services to a platform, and is an oft-cited piece of functionality admired by other platforms. Given increasing interest in this solution, the Cloud Foundry Foundation created a cross-foundation Working Group with the Cloud Native Computing Foundation to determine how the Cloud Foundry Service Broker API can be opened up and leveraged as an industry-standard specification for connecting services to platforms.

This talk will walk you through the vision for the Working Group, as well as the progress on a proof of concept made to date on allowing services to write against a single API, and be accessible to a variety of platforms.
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

Good afternoon so glad to see so many people are still here and warm, hopefully I'm going to talk today, just briefly about a new project that we kicked off, but first I'm going to give a bit of an intro to it. That I think it's important for the point of this project, the point of the working group and then the point of a lot of investments were starting to make in the cloud foundry community.

A

We've talked a lot this week about open source collaboration, 25 years of Linux and the value of us coming together as a community. One of the things we believe firmly at Cloud Foundry is that open source is a positive sum game to quote Robert Wright from his book nonzero, the history of civilization, is a series of positive some games that play out in larger and larger scale.

A

To make that even more simplistic, how many people can I call self instead of other.

A

The intent of that is to say the platforms can be positive, some games and that, by working together in collaborating, we can continue to innovate at a scale in a pace unachievable by a single person, a single organization or even a couple when I think about a platform and I think about what cloud foundry really takes to heart is balancing the needs of developers, users, providers and operators offering a virtuous cycle between all of those within a single technological solution.

A

The more people we can support with a platform, the greater the platform is not just the more successful but the better the technology and the better the ecosystem around that.

A

When I was thinking about the technology and thinking about other things, one of one of the fun things this week has been learning a lot about standards and specifications and the connotation that comes with those words. And so we thought a lot about the light bulb an early technological advance. And what made that interesting, notwithstanding the fact that we're all sitting here under lights and not in the dark in some creepy awkward way.

A

But the light socket is what made that interesting. The light socket was a standard we were all able to agree on and what that allowed you to do is come up with new light bulbs, the LED, the cool Phillips ones that you can turn on with Alexa and change the colors and even the shitty ikea lights. It just allowed you to innovate and change and come up with new ideas, but still have that common pluggable interface.

A

So now those light bulbs can work in any house in any country.

A

So coming back to platforms and we've talked a lot about different platforms and different aspects of the platform's. This week, platforms are able to drive or actually require more than drive, Network effects. We need those network effects to ensure that platforms continue to be successful, but also continue to drive and retain value for the users, the more people that are included in that the greater the network effects.

A

So thinking about how that can continue to drive and evolve, the usage, the utilization and the technology of the platform. A great example of that is uber. Uber is great, but you need two sides of that network for uber. You need drivers and you need writers.

A

If you have too many drivers and not enough writers, you've got a lot of people that are just hanging out when you have too many writers and not enough drivers, you've got a lot of people, they can't get a car, they get frustrated, they get annoyed and they get really annoyed when they have to pay surge pricing.

A

So when I think about Network effects- and we think about the cycle that drives those two on a platform, we think about the users, the services and the applications, you need both of those to make a successful platform.

A

So, when I talk about services, what do I mean when I think about services? I? Think about all of those technologies that exists that make your applications useful? Be it data messaging, CI, tooling? All of those services that make your application capable, useful and scalable.

A

One of the projects that we've been working on at Cloud Foundry is the service broker API and that's a service broker. Api is a technology that cloud foundry has had for many many years, it's something that's very near and dear to our heart, but it's also an area where we had an opportunity going back to where we started thinking of the larger community that we could perhaps collaborate on more.

A

So what is the service broker? Api?

A

Simply it's a contract between the platform and a service.

A

It's a very simple API that is flexible, but at its essence, really allows you to create, bind unbind and delete a service. It's super simple, but yet is such choir mint to make that platform useful for applications.

A

The service broker allows us to marry applications and services quickly effectively and debt scale.

A

So one of the things that we do, because we love to the service broker so much and turns out other people do too we created this working group and the working groups. Vision is to collaborate on ways that we can take that API make it an industry standard, set it up as a specification that allows isvs services to write against a single API and be accessible on any platform through a collaborative effort.

A

How do we take this service broker and allow it accessible use and run well on any platform, not just cloud foundry but Cooper Nettie's, open, Diaz, Red, Hat, fujitsu and any others, and your question might be.

A

Why would we want to do that and I won't make you do a trust fall, but realistically, at the end of the day, we're all in open source and and that's what we're asking to do- is trust to build the capabilities in a way that we can't singularly think of and at the end of the day, what really matters to each and every one of us is the ecosystem and the services that are available.

A

So our grand vision is to take that technology and use it to build the foundation for a marketplace, a marketplace of services that can ride and be deployed on any platform, a platform, agnostic marketplace and that's something I think together.

A

We can build out and turn into an even greater vision on how we think about services, how we think about software, how we think about deploying that software and what does that look like to all of our end users we're here this week talking about cloud native and one of the things we've asked is what makes that you know. What is that? What does that mean? And what that means is for most of our users, particularly for those that are working with companies are using the as an opportunity to become software companies.

A

It means thinking about their technology differently and, as we think about that collectively, that means greater and greater levels of abstraction and a greater opportunity to figure out ways to innovate, both inside a platform and outside a platform.

A

Cloud Foundry spent some time certifying and working really in our larger community on making sure technology was portable up across all of those platforms, but we thought why stop there?

A

Why not allow this same accessibility and share a lot of these lessons learned with other platforms and other technologies, because at the end of the day, our view and our vision is that cloud computing is ubiquitous and flexible.

A

It's portable, interoperable and our community is vibrant and growing. Those are the things we focus on a cloud foundry, but more than that, we see a human community, and this is something that we take very seriously. We want to make sure that we're pragmatic exchange ideas and experience, we're diverse and inclusive people across race, gender orientation and lifestyle and finally, we're respectful.

A

You committed a listening and thoughtful and honest conversation and perspectives, and so that's why I was excited to announce this here at lens con and cloud native day and talk about what we're doing and ask all of you to participate with me.

A

Thank you. There's any questions.