a9s BOSH for PCF Use Case

Note: Before installing an a9s service tile (e.g. a9s MongoDB for PCF), the a9s BOSH for PCF and a9s Consul for PCF tile must be installed.

The a9s BOSH for Pivotal Cloud Foundry (PCF) tile is used by all a9s service tiles for on-demand provisioning and lifecycle management of dedicated virtual machines. Consequently, each service instance will run on one or more dedicated virtual machines to provide a solid isolation.

Whenever a PCF end user creates a new service instance, for example by executing:

cf create-service a9s-mongodb32 mongodb-cluster-small mydb, cf create-service a9s-postgresql94 postgresql-single-small mydb
etc.

the corresponding a9s service tile will talk to the a9s BOSH for PCF tile and create a BOSH deployment in order to provision virtual machines and to install the required software packages.

Why we decided not to use the PCF Ops Manager Director for this purpose

We want to provide the possiblity to choose between the a9s BOSH for PCF and the PCF Op Manager Director in the future. For proof of concepts this would be a useful option, because the a9s BOSH for PCF tile does not need to be installed.

Due to the missing experience with using one BOSH director only for the regular PCF tile deployments as well as for the service instance deployments, we focus our support on using the a9s BOSH for PCF tile for now.

Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub