Pivotal Knowledge Base


How to set a Bosh Deployment to a Service Instance for an On Demand Broker


  • Pivotal Cloud Foundry (PCF) versions 1.9 and above and any product with an On Demand Broker
  • Pivotal Cloud Cache versions 1.0 and above
  • RabbitMQ Tile versions 1.8 and above
  • MySQL versions 2.0 and above
  • Redis 1.8 and above


This article outlines the process for setting a Bosh deployment to a service instance for an On Demand Broker.


For information on how to get setup using Bosh, refer here.

1. Run bosh deployments. Pick out the deployment for the service instance. It will have the service instance's guid in the name. If you need to get the guid for your service instance, you can run cf service <service-name> --guid

| service-instance_f9d12a31-d455-44cd-a96e-e2bb0fdeb0bd | redis-service/0.5.0                  | bosh-vsphere-esxi-ubuntu-trusty-go_agent/3363.25 | latest       |
|                                                       | syslog-configurator/0.3.0            |                                                  |              |

2. There is no deployment manifest for this. It's in-memory on the ODB broker. To get it, run bosh download manifest service-instance_f9d12a31-d455-44cd-a96e-e2bb0fdeb0bd service-instance_f9d12a31-d455-44cd-a96e-e2bb0fdeb0bd.yml to download the manifest

Acting as user 'director' on deployment 'service-instance_f9d12a31-d455-44cd-a96e-e2bb0fdeb0bd' on 'p-bosh'
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Deployment manifest saved to 'service-instance_f9d12a31-d455-44cd-a96e-e2bb0fdeb0bd.yml'

3. Run bosh status and copy the Director's UUID

4. Edit the service instance manifest, add the line director_uuid: <uuid> after the --- at the top of the file


director_uuid: 103eb15e-c79c-400c-a025-b36d9cf45234
name: service-instance_f9d12a31-d455-44cd-a96e-e2bb0fdeb0bd
- name: redis-service

1. Point to the deployment, bosh deployment service-instance_<service-instance-guid>.yml

$ bosh deployment service-instance_<service-instance-guid>.yml
Deployment set to '/home/ubuntu/service-instance_<service-instance-guid>.yml'

2. You're now targeting the ODB deployment so you can run whatever Bosh commands you need to troubleshoot, like bosh logs or bosh ssh


In some cases, bosh download manifest will download an empty file. This happens when there is an error early on while the deployment was being set up and it means that you need to look at the ODB broker logs to figure out what happened.


Powered by Zendesk