LATEST VERSION: 2.0 - RELEASE NOTES
Spring Cloud Services v1.5

Installing Spring Cloud® Services for Pivotal Cloud Foundry

Page last updated:

Ensure that you have or have completed all items listed in Requirements. Then follow the below steps to install Spring Cloud Services.

Important: Spring Cloud Services requires either MySQL for PCF v2 (recommended) or MySQL for PCF v1. Install one of these products before installing Spring Cloud Services.

Installation Steps

  1. Download Spring Cloud Services from Pivotal Network.

  2. In the Installation Dashboard of Pivotal Cloud Foundry (PCF) Operations Manager, click Import a Product on the left sidebar to upload the Spring Cloud Services .pivotal file.

  3. Hover over Spring Cloud Services in the Available Products list and click the Add » button.

  4. When the Spring Cloud Services tile appears in the Installation Dashboard, click it. In the Settings tab, click Assign AZs and Networks.

    Azs and networks

    Select the availability zones for the tile to use. In the Network section, select the PAS (or ERT) network.

  5. Still in the Settings tab, click Spring Cloud Services to configure settings for Spring Cloud Services.

    Settings

    The Service instance limit setting sets the maximum number of service instances that the Spring Cloud Services service broker will allow to be provisioned (the default value is 100). This setting’s value is also used to determine the memory quota for the org in which service instances are deployed; that org’s quota will be equal to 1.5G times the configured service instance limit. The App push timeout setting is the number of minutes the broker allows for a service instance backing application to start. The Buildpack setting is the name of the Java buildpack that the Spring Cloud Services service broker will use to provision service instances (if this setting is left empty, the broker will use the default Java buildpack to provision service instances).

    The Do not validate that SSL certificates are properly configured checkbox, if checked, disables only the validation that Spring Cloud Services performs by default on the Pivotal Cloud Foundry® Pivotal Application Service (PAS) SSL certificate. It does not disable SSL certificate validation for application instances running on the Pivotal Cloud Foundry ® platform.

    WARNING: Disabling Spring Cloud Services’ validation of the PAS SSL certificate is an extreme action that should not be taken unless absolutely necessary, and can cause unexpected behavior across your installation of Spring Cloud Services. Do not disable this validation unless you are completely certain that you must do so.

    Service settings

    The Persistence store service and Persistence store service plan settings set the service and service plan for the service broker’s MySQL database. This must be a service that provides a MySQL-compatible database (to use MySQL for PCF v2 for the persistence store service, enter p.mysql, or to use MySQL for PCF v1, enter p-mysql). The Message bus service and Message bus service plan settings set the service and service plan for the broker’s message bus.

    These settings should be configured only during the Spring Cloud Services tile installation process. If you have already completed the tile installation process, do not alter these settings.

    WARNING: Configuring the service broker’s dependent services after installing the tile can cause corruption or loss of the broker’s service instance data.

  6. If you wish to use CredHub to secure service instance credentials, enable the Secure service instance credentials checkbox.

    Important: To use CredHub with Spring Cloud Services, you must be using Pivotal Application Service (PAS) 2.0 or later, have configured the Runtime CredHub, and have at least one job instance configured in the PAS tile’s Resource Config settings tab.

    Secure si credentials

  7. Return to the Installation Dashboard and click Apply changes on the right sidebar to install the tile.

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