Installing and Configuring a9s BOSH for PCF on VMware vSphere

Prerequisites

Ensure that the following tile has been installed:

Install and Configure a9s BOSH for PCF

Complete the following steps to download, install, configure, and deploy a9s BOSH for PCF.

  1. Download the product file from the Pivotal Network.

  2. Navigate to the Pivotal Cloud Foundry Operations Manager (Ops Manager) Installation Dashboard and click Import a Product to upload the product file.

  3. Click Add next to the uploaded a9s BOSH for PCF tile in the Ops Manager Available Products view to add it to your staging area.

  4. Click the newly added tile and review and configure the fields in the Settings pane. For information about the fields, see About Configuring a9s BOSH for PCF below.

  5. Click Apply Changes to deploy the service.

About Configuring a9s BOSH for PCF

Read this section for help to complete Step 4 above.

IaaS Settings Section

In the IaaS Settings of the a9s BOSH for PCF tile you have to choose vShpere. Once vSphere is selected, the following configuration options must be provided:

Value Description Example
vCenter Host The Hostname of the vSphere API
vCenter Username You have to provide a user with the same permissions as the user you have configured in the PCF Ops Manager Director (you can also use the same user). A closer description on the required user permissions can be found here.
vCenter Password The password belonging to the user provided above.
Datacenter Name The name of the datacenter in vSphere to which the a9s service instances should be deployed.
VM Folder The name of the folder created to hold VMs. … Folders will be automatically created under the chosen datacenter. See https://bosh.io/docs/init-vsphere.html for more information. a9s_vms
Template Folder The name of the folder created to hold stemcells. Folders will be automatically created under the chosen datacenter. See https://bosh.io/docs/init-vsphere.html for more information. a9s_templates
Datastore pattern for persistent Disks A regex matching the names of potential datastores the Director will use for storing VMs and associated persistent disks. See https://bosh.io/docs/init-vsphere.html for more information. ^(s1ǀs2ǀs3)$
Datastore pattern for Ephemeral Disks Often the same as Datastore pattern for persistent Disks ^(s1ǀs2ǀs3)$
Disk Path The name of the VMs folder. Disk folder will be automatically created in the chosen datastore. See https://bosh.io/docs/init-vsphere.html for more information. a9s_disk
Name of the clusters in vCenter A JSON formatted array with the names of the vSphere clusters that should be used to provision VMs for service instances. Each cluster must exist in the chosen datacenter. [C01,C02,C03]

Cloud Config Section

Cloud Config is a BOSH term and refers to your infrastructure specific configuration. It encapuslates all specifics so that BOSH can use the same deployment manifests across different IaaS installations.

To create the Cloud Config YAML, you can use the a9s Cloud Config Wizard (see: https://cloud-config.anynines.com/). It provides you a graphical user interface for the specification of all configuration values to ensure you don’t miss anything and that you have a proper YAML structure.

Note: Ensure that you have specified a network with the name service-instances, two disk types named small and big and two VM types named small and big.

The big VM and disk types will be used for the creation of service instances when a big service plan should be used, such as mongodb-cluster-big or postgresql-cluster-big. The small VM and disk types will be used for the small service plans, such as mongodb-cluster-small or postgresql-cluster-small.

Note: To reduce the risk that a data service instance experiences a split brain situation, ensure you have configured three availability zones.

Errands Section

Find a description about the errands of the a9s BOSH for tile here.

Create a pull request or raise an issue on the source for this page in GitHub