Here you will find information about Spring Cloud Services tile options, resource configuration, and lifecycle errands.
Note Tanzu Operations Manager administrators can use Role-Based Access Control (RBAC) to manage which operators can make deployment changes, view credentials, and manage user roles in Ops Manager. Therefore, your role permissions might not allow you to perform every procedure in this operator guide. For more information about roles in Ops Manager, see Understand Roles in Ops Manager.
Service Broker settings
The Spring Cloud Services (SCS) tile includes a number of settings for the service broker. You can configure these by visiting the Installation Dashboard of Ops Manager, clicking the Spring Cloud Services tile, and then navigating to the SCS Service Broker pane.
Configure service access
By default, the Config Server and Service Registry services are made available globally (i.e. to all orgs). You can configure service availability in the Spring Cloud Services tile settings, under Config Server access and Service Registry access.
For each service, select Global to make the service available to all orgs, or select None to make the service unavailable to all orgs.
Set buildpack for service instances
By default, the Spring Cloud Services service broker stages service instance backing apps using the buildpack chosen by the platform's buildpack detection; normally, this will be the highest-priority Java buildpack. To cause the broker to use a particular Java buildpack regardless of priority, you can set the name of the buildpack to use in the Spring Cloud Services tile settings, under Java Buildpack.
Enter the name of the desired Java buildpack. The broker will use the selected buildpack to stage service instance backing apps.
Select Stack for backing applications
By default, the Spring Cloud Services service broker will stages service instance backing apps using cflinuxfs4 stack. To cause the broker to use a particular stack, you can set the name of the stack to use in the Spring Cloud Services tile settings, under Stack.
Enter the name of the desired stack. The broker will use the selected stack to stage service instance backing apps.
Set service instance timeout
By default, the Spring Cloud Services service broker will wait 30 minutes before considering a service instance operation to have failed. You can specify a different timeout interval in the Spring Cloud Services tile settings, under Status change timeout.
Enter the desired number of minutes. The broker will allow the specified number of minutes for service instance operations to complete.
Set concurrent service instance upgrade
When running upgrade-all-instances errand, by default, the Spring Cloud Services service broker will upgrade 5 service instances concurrently. You can specify a different number in the Spring Cloud Services tile settings, under Concurrent Service Instance Upgrade.
Enter the desired number. The broker will use the specified number to upgrade service instances, concurrently, during upgrade-all-instances errand.
Set custom domain for service instances
By default, the Spring Cloud Services service broker assigns routes to service instances using the VMware Tanzu Application Service for VMs (TAS for VMs) application domain. You can specify a custom domain for service instance routes in the Spring Cloud Services tile settings, under Service instances domain.
Important Your custom domain must be available to the p-spring-cloud-services org. If you are installing Spring Cloud Services, you must manually create this org before configuring the custom domain in the Spring Cloud Services tile settings.
Enter the desired domain. The broker will use this domain to create routes for service instances.
Activate service keys
By default, the use of service keys is deactivated for service instances. To allow the use of service keys on service instances, select Enable off platform service key access.
Configure CredHub as a backend for config server
By default, Credhub can be used as a backend for Config Server. To prevent the use of CredHub as a backend for Config Server, unselect Enable credhub as a backend for config server.
Lifecycle errand configuration
The Spring Cloud Services tile includes two co-located lifecycle errands. You can view these in Ops Manager by visiting the Installation Dashboard, clicking the Spring Cloud Services tile, and then navigating to the Errands pane.
Spring Cloud Services includes two post-deploy errands and one pre-delete errand. These errands can be individually set to always run (On) or to never run (Off).
Important To ensure that your TAS foundation receives important updates to the tile, VMware recommends that all Spring Cloud Services lifecycle errands be set to On.
The register-brokers errand registers the Spring Cloud Services service broker, and the broker for the Config Server's mirror service, with the Cloud Controller, and makes all Spring Cloud Services service plans available to all orgs. The destroy-brokers errand deletes all orgs and spaces specific to Spring Cloud Services and deregisters the Spring Cloud Services broker and mirror service broker from the Cloud Controller.
The upgrade-all-instances errand attempts to update all SCS service instances to the latest version. A service instance upgrade will be considered failed if service instance does not start successfully after a time configured by Status Change Timeout which defaults to 30 minutes. Additionally, depending on available resources the maximum number of concurrent upgrades can be configured by the Concurrent Service Instance Upgrade option which defaults to 5.
If a service instance upgrade fails, errand will continue the upgrade of the remaining service instances. The errand execution will be considered successful if all services are upgraded successfully. If one or more service instances fail to upgrade the errand execution will be considered failed. After the errand completes, any service instance that was failed to upgrade can be upgraded via cf CLI using the following command:
$ cf update-service <SERVICE INSTANCE NAME> -c '{"upgrade": true}'
System logging configuration
To configure system logging for Spring Cloud Services, visit the Installation Dashboard, click the Spring Cloud Services tile, and then navigate to the Syslog pane.
For information about system logging in TAS for VMs, see Configuring Logging in TAS for VMs.
Mirror service resource configuration
The Spring Cloud Services Config Server relies on a "mirror service" to make mirrors of Git repositories used by Config Server service instances. You can configure the size of the persistent disk used to store these Git mirrors. In the Spring Cloud Services tile settings, navigate to the Resource Config pane.
For the spring-cloud-services job, select the desired disk size value from the dropdown under Persistent Disk Type. The default value is 10 GB. Consider setting a size equal to the disk space required to mirror all Git repositories potentially used by Config Server service instances, with some additional disk space.
