Page last updated:
See below for information about Spring Cloud Services tile options, resource configuration, and lifecycle errands.
Note: Ops 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.
The Spring Cloud Services (SCS) tile includes settings for various options. 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.
By default, the Config Server service is made available globally (i.e. to all orgs). You can configure the service availability in the Spring Cloud Services tile settings, under Config Server access.
Select Global to make the Config Server service available to all orgs, or select None to make the Config Server service unavailable to all orgs.
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.
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.
By default, the Spring Cloud Services service broker assigns routes to service instances using the VMware Tanzu Application Service for VMs (TAS) 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.
The Spring Cloud Services tile includes two colocated 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 one 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 Config Server service broker and the associated mirror service’s broker with the Cloud Controller and makes the Config Server service’s service plans available to all orgs. The destroy-brokers errand deletes all orgs and spaces specific to Spring Cloud Services and deregisters the Config Server and mirror service brokers from the Cloud Controller.
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.