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.
Note: If you are using a private Certificate Authority to generate SSL certificates, see Using a Private Certificate Authority below.
Download Spring Cloud Services from Pivotal Network.
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
In the left sidebar, under Spring Cloud Services, click the + button next to the version number.
When the Spring Cloud Services tile appears in the Installation Dashboard, click it. In the Settings tab, click Assign AZs and Networks.
Select the availability zones for the tile to use. In the Network section, select the network used by Pivotal Application Service (or Elastic Runtime). When finished, click Save.
Return to the Installation Dashboard.
Click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.
Click Apply Changes to install the tile.
Spring Cloud Services (SCS) 3.0.x can be installed alongside earlier versions of Spring Cloud Services, including 2.0.x. SCS 3.0.x includes only the Config Server service, which is named
p.config-server instead of
p-config-server as in 2.0.x and earlier versions. This service can run alongside the services included in 2.0.x and earlier versions. Because SCS 3.0.x includes only the Config Server service, you may wish to disable the older
p-config-server service and allow only the new
p.config-server Config Server service to be created.
Older Config Server service instances cannot be upgraded to the new
p.config-server service. Instead, you must recreate
p-config-server service instances. Most parameters used to create a
p-config-server service instance with the Cloud Foundry Command Line Interface (cf CLI), using the
cf create-service command with the
-c flag, can also be used to create a
p.config-server service instance. The following parameters are exceptions which can be used with the
p-config-server service but cannot be used with the
composite.git(see Composite Backends for information about how to configure the composite backend in the SCS 3.0.x Config Server)
composite.vault(see Composite Backends for information about how to configure the composite backend in the SCS 3.0.x Config Server)
SCS 3.0.x service instances are backwards-compatible with version 2.0.1.RELEASE of the SCS client dependencies.
If you are using a private Certificate Authority (CA) to generate SSL certificates, you must import the private CA’s certificate into the Java keystore of the BOSH VM used for the Config Server’s service broker and mirror service. Follow the below steps to do this.
Add the private CA’s certificate to the BOSH trusted certificates.
a. In the Installation Dashboard of PCF Ops Manager, navigate to the BOSH Director tile’s settings.
b. Click Security.
c. In Trusted Certificates, enter the CA’s certificate.
d. Click Save.
Ensure that the truststore on each VM has the private CA’s certificate.
a. Still in the BOSH Director tile’s settings, click Director Config.
b. Enable the Recreate all VMs checkbox.
Return to the Ops Manager Installation Dashboard and apply your changes to BOSH, PAS, and the Spring Cloud Services tile.
After you apply your changes, any new SSL certificate that is rotated into the platform should be successfully validated when used in SSL connections to platform services.