Thanks for the sample service brokers, this is very useful.
I'm wondering what would be the recommended way to implement a service broker that dynamically instanciates nodes as to be trutly elastic and not require manual capacity adjustments to cope with increased demand. For a CF operator, installing such service would gets the same effect as installing a "service cartridge" in other paas such as openshift. Any one has experience with such elastic services that could be shared ?
Ideally such elastic service would be able to run on both public and private CF instances.
I was thinking this service broker would
dynamically instanciate nodes running as cf apps using the CC API e.g. through vcap-java. Nodes would run a custom buildpack that installs and configure the JMS server. Potentially, this buildpack could invoke puppet/chef recipes to ease the setup (sad that bosh infrastructure can't be leveraged here)
An alternative for private CF instance that was discussed a while ago was bosh dynamic pools [1] any news on this since then?
As a proof-of-concept, I was thinking of a JMS service (i.e. the service node offer JMS services to other apps).
[1]
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/jYohaSSDevQ/discussion