All Posts By

Matt McNeeney

Pop to Philadelphia to learn more about Service Brokers at these awesome CF Summit talks

By | Blog

 

If you’re passing over the East Coast of the US this April, be sure to pop into Philadelphia (where it’s always sunny, apparently) to learn more about Service Brokers and how they are helping companies all over the world get access to the cloud-native services their applications need.

Registration is open now, and the schedule went live today. We’ve compiled a list of the best Open Service Broker API talks for you to bookmark before the conference kicks off on April 2nd:

 

Wednesday

11:20am: The Subtle Art of Keeping your Broker Multi-platform Compatible – Georgi Lozev, SAP

This talk will provide an overview of the different types of broker – based on their deployment model like hosted brokers, ones deployed alongside the platform and ones deployed on top of it. Then we will show you some pitfalls we came across while working on CF as a platform implementations and, last but not least, we will go over good practices and future improvements that should keep our brokers multi-platform compatible.

 

2:55pmTesting Production Environments and Verifying Open Service Broker API Compliance – Oliver Wolf & Robert Gogolok, anynines

This talk shows how a generic test suite that verifies production platform environments and OSBAPI compliance can be used for different kind of data services.

Thursday

11:45amAccessing Cloud Foundry Marketplace from your Kubernetes Cluster – Dr Nic Williams, Stark & Wayne

In this talk, we introduce the Kubernetes Service Catalog, the Open Service Broker API, and a special new service broker that bridges a CF user’s marketplace access into their own Kubernetes cluster.

 

2:00pmOne Marketplace to Rule Them All – Matt McNeeney & Sam Gunaratne, Pivotal

Come and learn how the open source Independent Services Marketplace team are building the future by inverting the relationship between platforms and backing services, and how this can drastically improve the lives of developers and operators running cloud-native platforms at scale.

 

3:20pmOpen Service Broker 101: That Extra Something – Christian Brinker, evoila

In his talk, Christian Brinker takes the audience on the journey from the reasons for the usage of service brokers via their inner structure and effects to complex production setups. He presents common pitfalls and best practices as well as giving a deep insight into the open source service broker framework of his team.

Open Service Broker v2.13 has landed

By | Blog

This week the Open Service Broker API working group released the latest version of the specification, v2.13.

This new version comes three months after the last version and includes a diverse range of new features, bug fixes and improvements. Some of the features the community are most excited about are detailed below.

More information on this release can be found in the release notes, and you can stay up to date with what the community is working on by checking out the Roadmap & Release Planning project on GitHub.

 

Schemas for configuration parameters

Many service brokers accept configuration parameters that application developers can use when provisioning service instances, updating service instances and creating service bindings. Until now, developers have had to find documentation for a specific service to understand the arbitrary key-value pairs that can be provided, and the allowed values that can be provided for each parameter. From this version onwards, service brokers can now include JSON Schemas in their catalog data that describe the parameters application developers can provide. This allows command-line and other user interfaces to perform up-front validation of parameters, and can even be used to dynamically generate forms with dropdowns, ranges and other UI elements. The example below shows how this can help provide a much better developer user experience.

An example of how JSON schemas can be used to automatically generate intuitive user interfaces

 

Improved authentication mechanisms

Platform to service broker communication currently uses Basic access authentication, but many people in the community have expressed a desire to investigate more secure and extensible mechanisms like OAuth. A change has been made to the specification in v2.13 that allows platforms to start investigating how other authentication mechanisms could be implemented and how new features could be allowed, such as providing role-based access control for application developers to use features of the underlying service.

 

New ‘Getting Started’ page

A new page has been added to the Open Service Broker API repository that contains a number of sample service brokers and libraries that the community have been working hard on. This should make it much easier for service authors to see what others are working on in the community, and provide new service authors an easy way to get started and quickly provide their services to cloud-native platforms.