Installing and Configuring Crunchy PostgreSQL for PCF

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

Import the Tile to Ops Manager

  1. Download the product file from Pivotal Network.

  2. Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.

  3. Under the Import a Product button, click + next to the version number of Crunchy PostgreSQL for PCF. This adds the tile to your staging area.

Configure the Service

  1. Click the newly added Crunchy PostgreSQL tile on the Ops Manager Installation Dashboard to open the configuration panes.

    Crunchy PostgreSQL tile

  2. Configure each section as described below.

Configure AZ and Network Assignments

To make Crunchy PostgreSQL highly available, you must balance the service across multiple availability zones (AZs).

  1. Click Assign AZs and Networks.

    Assign AZs and Networks pane

  2. Choose an AZ to deploy singleton jobs. This is a private service network with a route to a public gateway.

  3. Choose AZ to balance jobs. This should be a private service network with a route to a public gateway. Crunchy Data recommends two or more AZs when possible.

  4. Choose the primary network where the On-Demand Broker will be deployed.

  5. Choose the service network that On-Demand Broker will use to deploy VMs. This is a private service network with a route to a public gateway.

  6. Click Save.

Configure Global Properties

  1. Click Global Properties.

    Global Properties

  2. Configure the VM type for Consul servers. These do not need to be big servers.

  3. Configure the size of disk to be attached to the Consul server. Crunchy Data recommends at least 10 GB.

  4. Configure the VM type for the PostgreSQL Load Balancer servers. If unsure, use the defaults.

  5. Configure the disk size for the PostgreSQL Load Balancer server. If unsure, use the defaults.

  6. Configure the VM type for the Smoke-Tests. If unsure, use the defaults.

  7. Configure the disk size for the Smoke-Tests Server. If unsure, use the defaults.

  8. Choose an AZ to deploy these services to.

  9. Click Save.

The plans made available to developers need to be configured prior to deployment. The following table can be used as a baseline when configuring the plans for use:

Plan vCPU Memory Disk
Small 4 32 GB 64 GB
Medium 8 64 GB 128 GB
Large 16 128 GB 256 GB
XLarge 32 256 GB 512 GB

Note: Do not set any PostgreSQL or pgBackrest VMs to less than 4 GB of memory.

Note: Do not set any PostgreSQL or pgBackrest VMs to fewer than 2 cores.

Configure Small Plan Properties

  1. Click Small Plan Properties.

    Small Plan Properties

  2. Configure the VM size for databases servers in the small plan. This is the size that is used when a developer requests a small database plan. For recommendations, see Recommended Sizes above.

  3. Configure the Disk size for databases servers in the small plan. This is the disk size that is used when a developer requests a small database plan. For recommendations, see Recommended Sizes above.

  4. Configure the number of PostgreSQL servers for the small plan. This is the number of PostgreSQL servers deployed. To ensure high availability, this should always be more than one. One server is always primary, the rest are additional replicas.

  5. Configure the quota of services allowed to be created with the small plan. This number prevents users from creating too many services.

  6. Click Save.

Configure Medium Plan Properties

  1. Click Medium Plan Properties.

    Medium Plan Properties

  2. Configure the VM size for databases servers in the medium plan. This is the size that is used when a developer requests a medium database plan. For recommendations, see Recommended Sizes above.

  3. Configure the Disk size for databases servers in the medium plan. This is the disk size that is used when a developer requests a medium database plan. For recommendations, see Recommended Sizes above.

  4. Configure the number of PostgreSQL servers for the medium plan. This is the number of PostgreSQL servers deployed. To ensure high availability, this should always be more than one. One server is always primary, the rest are additional replicas.

  5. Configure the quota of services allowed to be created with the medium plan. This number prevents users from creating too many services.

  6. Click Save.

Configure Large Plan Properties

  1. Click Large Plan Properties.

    Large Plan Properties

  2. Configure the VM size for databases servers in the large plan. This is the size that is used when a developer requests a large database plan. For recommendations, see Recommended Sizes above.

  3. Configure the Disk size for databases servers in the large plan. This is the disk size that is used when a developer requests a large database plan. For recommendations, see Recommended Sizes above.

  4. Configure the number of PostgreSQL servers for the large plan. This is the number of PostgreSQL servers deployed. To ensure high availability, this should always be more than one. One server is always primary, the rest are additional replicas.

  5. Configure the quota of services allowed to be created with the large plan. This number prevents users from creating too many services.

  6. Click Save.

Extra Large Plan Properties

  1. Click Extra Large Plan Properties.

    Extra Large Plan Properties

  2. Configure the VM size for databases servers in the extra-large plan. This is the size that is used when a developer requests a extra-large database plan. For recommendations, see Recommended Sizes above.

  3. Configure the Disk size for databases servers in the extra-large plan. This is the disk size that is used when a developer requests a extra-large database plan. For recommendations, see Recommended Sizes above.

  4. Configure the number of PostgreSQL servers for the extra-large plan. This is the number of PostgreSQL servers deployed. To ensure high availability, this should be more than one. One server is always primary, the rest are additional replicas.

  5. Configure the quota of services allowed to be created with the extra-large plan. This number prevents users from creating too many services.

  6. Click Save.

Configure Errands

  1. Click Errands.

    errands

  2. Configure the errands that should be run after deployment of the service. Crunchy Data recommends the defaults.

  3. Click Save.

Configure Resources

  1. Click Resource Config.

    Resource Config

  2. Review the pre-populated recommended server sizes and make any changes.

  3. Click Save.

Configure Stemcell

  1. Click Stemcell.

    Stemcell

  2. Upload the required stemcell for the service. See Bosh.io for the complete list of stemcells.

  3. Click Save.

Install the Tile

  1. Return to the Ops Manager Installation Dashboard

  2. Click Apply Changes to install the Crunchy PostgreSQL for PCF tile.

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