Installing and Configuring a9s BOSH for PCF

This topic describes how to install and configure a9s BOSH for Pivotal Cloud Foundry (PCF).

Prerequisites

Ensure that the following tile has been installed:

  • a9s Consul DNS for PCF v0.9.0 or later

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 completing Step 4 above. You configure the BOSH Director for a9s BOSH to enable access to your infrastructure.

The a9s BOSH for PCF Settings pane contains two types of fields:

  • BOSH Director CPI fields — These fields are specific to your infrastructure (IaaS), for example, OpenStack, AWS, or vSphere.

  • Cloud Config fields — These fields are the same for all infrastructures. However, the value structures, for example JSON configuration strings, might be different. Example values are provided for AWS and vSphere. If your infrastructure type is missing, contact anynines Support.

Note: The IaaS credentials specified in the Settings pane must have the privileges described in the Prerequisites to Deploying Operations Manager and Elastic Runtime topic.

If you are using AWS, see AWS-specific Settings.

If you are using vSphere, see vSphere-specific Settings.

BOSH Director CPI Fields

The BOSH Director CPI fields for vSphere are shown below.

Cloud-Config Fields

The Cloud Config fields are shown below.

AWS-specific Settings

This section provides information about configuring a9s BOSH for PCF with AWS.

For more BOSH AWS configuration options, see the BOSH documentation.

Value Example
AWS Access Key ID YOURAWSACCESSKEY
AWS Secret Access Key secret
AWS Default Key Name myawsname
AWS Default Security Group sg-56168731
AWS Default Region eu-west-1

Cloud Config

Cloud-config is a BOSH term. For more information, see Cloud Config in the BOSH documentation.

Availability Zones

AZs are essential for deploying highly available data services. Setting AZs allows BOSH to distribute VMs across infrastructure AZs. For more information, see AZs Block in the BOSH documentation.

Note: For the operation of a9s data services, such as a9s MongoDB for PCF, at least three infrastructure AZs need to be configured. Three are required to enable quorum-based leader election during failover-procedures.

Fields Example
Cloud properties for availability zones {availability_zone: eu-west-1a}
VM Types

The cloud properties for the VM-type settings are used in later deployments to determine the VM sizes, with respect to CPU, memory and ephemeral disk space. For more information, see VM Types Block in the BOSH documentation.

Fields Example
Cloud properties for the VM types {instance_type: t2.small, availability_zone: eu-west-1a, ephemeral_disk: {size: 2048, type: gp2}}
Disk Types

Disk types define the types of persistent disks that can be used in later deployments. In contrast to ephemeral disks, persistent disks are decoupled from the lifecycle of a VM and often store data on remote storage devices. For more information, see Disk Types Block in the BOSH documentation.

Persistent disks are used in a9s data services to store the actual data service data.

Fields Example
Cloud properties for the disk types {disk_size: 5120, cloud_properties: {type: gp2,encrypted: false}}
Network Settings

Network settings define the subnet that is used by BOSH. VMs provisioned by a9s BOSH for PCF receive IP addresses from the specified subnet. For more information, see Networks Block in the BOSH documentation.

This includes a CIDR of the IP range of the subnet, the IP of the subnet gateway, and a single IP or a range of reserved IPs. IP addresses from the reserved IP range are not assigned by BOSH to any VM.

Fields Example
Subnet IP range of this subnet for the availability zone 10.0.29.0/24
Subnet gateway IP for the availability zone 10.0.29.1
Reserved IPs for the availability zone 10.0.29.1-10.0.29.11
Cloud properties for this subnet for the availability zone {subnet: subnet-9f7489c7}

vSphere-specific Settings

This section provides information about configuring a9s BOSH for PCF with vSphere.

For more BOSH vSphere configuration options, see the BOSH documentation.

Value Example Explanation
The host of the vCenter vcenter01.example.com
vCenter user name avarteq@example.com
vCenter user password secret
Name of the datacenter avarteq Name of the datacenter.
VM folder pcf/pcf_vms Relative path to a folder where the created VMs will be stored.
Template folder pcf/pcf_templates Relative path to a folder where the stemcells will be stored.
Datastore pattern for ephemeral disks ^(ds_emc01_iscsi_c01_pcf)$ Pattern for selecting datastores for storing ephemeral disks and replicated stemcells.
Datastore pattern for persistent disks ^(ds_emc01_iscsi_c01_pcf)$ Pattern for selecting datastores for storing persistent disks.
Disk path pcf_disk Relative path to a folder where the persistent disks will be stored.
Name of the clusters in vCenter [C01, C02, C03] Expects an array of datacenters where to put the VMs

Cloud Config

Cloud-config is a BOSH term. For more information, see Cloud Config in the BOSH documentation.

Availability Zones

AZs are essential for deploying highly available data services. Setting AZs allows BOSH to distribute VMs across infrastructure AZs. For more information, see AZs Block in the BOSH documentation.

Note: For the operation of a9s data services, such as a9s MongoDB for PCF, at least three infrastructure AZs need to be configured. Three are required to enable quorum-based leader election during failover-procedures.

Fields Example
Cloud properties for availability zones {datacenters: [{name: avarteq, clusters: [C01: {resource_pool: RP_PCF_C01}]}]}
VM Types

The cloud properties for the VM-type settings are used in later deployments to determine the VM sizes, with respect to CPU, memory and ephemeral disk space. For more information, see VM Types Block in the BOSH documentation.

Fields Example
Cloud properties for the VM types {cpu: 1, ram: 2048, disk: 8192}
Disk Types

Disk types define the types of persistent disks that can be used in later deployments. In contrast to ephemeral disks, persistent disks are decoupled from the lifecycle of a VM and often store data on remote storage devices. For more information, see Disk Types Block in the BOSH documentation.

Persistent disks are used in a9s data services to store the actual data service data.

Fields Example
Cloud properties for the disk types {type: thin}
Network Settings

Network settings define the subnet that is used by BOSH. VMs provisioned by a9s BOSH for PCF receive IP addresses from the specified subnet. For more information, see Networks Block in the BOSH documentation.

This includes a CIDR of the IP range of the subnet, the IP of the subnet gateway, and a single IP or a range of reserved IPs. IP addresses from the reserved IP range are not assigned by BOSH to any VM.

Fields Example
Subnet IP range of this subnet for availability zone 172.28.4.0/24
Subnet gateway IP for availability zone 172.28.4.1
Reserved IPs for availability zone 172.28.4.1-172.28.4.11
Cloud properties for this subnet for availability zone {name: 268_C01_RZ-AT-VMWARE-STAGING-1}
Was this helpful?
What can we do to improve?
View the source for this page in GitHub