Onsi Fakhouri <ofakhouri@...>
Well done Services API! This is an awesome milestone!
On Wed, Jun 3, 2015 at 5:04 PM, Chip Childers <cchilders(a)cloudfoundry.org>
Awesome news! Long time coming, and it opens up a whole world of
additional capabilities for users.
Nice work everyone!
On Jun 4, 2015, at 9:00 AM, Shannon Coen <scoen(a)pivotal.io> wrote:
On behalf of the Services API team, including Dojo participants from IBM
and SAP, I'm pleased to announce experimental availability and published
documentation for this much-anticipated feature.
As of cf-release v208 and CLI v6.11.1, Cloud Foundry now supports an
enhanced service broker integration in support of long-running
provisioning, update, and delete operations. This significantly broadens
the supported use cases for Cloud Foundry Marketplace Services, and I can't
wait to hear what creative things the ecosystem does with it. Provision
VMs, orchestrate clusters, install software, move data... yes, your broker
can even open support tickets to have those things done manually!
This feature is currently considered experimental, as we'd like you all to
review our docs, try out the feature, and give us feedback. We very
interested to hear about any confusion in the docs or the UX, and any
sticky issues you encounter in implementation. Our goal is for our docs
enable a painless, intuitive (can we hope for joyful?) implementation
We have not bumped the broker API yet for this feature. You'll notice that
our documentation for the feature is separate from the stable API docs at
this point. Once we're confident in the design (we're relying on your
feedback!), we'll bump the broker API version, move the docs for
asynchronous operations into the stable docs, AND implement support for
asynchronous bind/create-key and unbind/delete-key.
Example broker for AWS (contributed by IBM):
Demo of the feature presented at CF Summit 2015:
Cloud Foundry expects broker responses within 60 seconds. Now a broker can
return an immediate response indicating that a provision, update, or delete
operation is in progress. Cloud Foundry then returns a similar response to
the client, and begins polling the broker for the status of the operation.
Users, via API clients, can discover the status of the operation ("in
progress", "succeeded", or "failed"), and brokers can provide user-facing
messages in response to each poll which are exposed to users (e.g. "VMs
provisioned, installing software, 30% complete").
Product Manager, Cloud Foundry
cf-dev mailing list
cf-dev mailing list