This guide is for people who want to author service tiles for Tanzu Operations Manager using the On-Demand Services SDK for Tanzu.
Tanzu Application Service is now called Tanzu Platform for Cloud Foundry. The current version of Tanzu Platform for Cloud Foundry is 10.0.
Operators make software services such as databases available to developers by using the Tanzu Operations Manager Installation Dashboard to install service tiles.
On-demand services enable you to provision instances flexibly. The operator does not pre-allocate a block of VMs for the instance pool, and they can specify an allowable range rather than fixed settings for instance resource levels. When a developer creates an on-demand service instance, they then provision it at creation time.
The On-Demand Services SDK provides a generic, on-demand broker (ODB). This simplifies broker and tile authoring, and is the standard approach for both VMware internal services teams and VMware partner independent software vendors (ISVs) to develop on-demand services for Tanzu Platform for Cloud Foundry. For more information about service brokers and how the on-demand broker works, see About On-Demand Brokers.
Product snapshot
The following table provides version and version-support information about the On-Demand Services SDK.
| Element | Details |
|---|---|
| Version | 0.45.3 |
| Compatible Tanzu Operations Manager version(s) | 3.0 |
| Compatible Tanzu Application Service version(s) | 4.0, 5.0, 6.0 |
| Compatible Tanzu Platform for Cloud Foundry version(s) | 10.0 |
| IaaS support | AWS, Azure, GCP, OpenStack, and vSphere |
On-Demand Services SDK is compatible with all releases of Tanzu Operations Manager 2.5 and later, and Tanzu Application Service 2.5 and later. Only supported versions of these apps are shown in the table.
Key features
The benefits of provisioning service instances with resources on-demand are:
- Operators can scale resource consumption in line with need, without having to plan for pre-provisioning.
- App developers get more control over resources and do not have to acquire them through the operator.
The benefits of using ODB to develop on-demand services are:
- ODB reduces the amount of code service developers have to write by abstracting away functionality common to most single-tenant on-demand service brokers.
- ODB uses BOSH to deploy service instances, so anything that is BOSH-deployable can integrate with Cloud Foundry’s services Marketplace.
ODB uses the following BOSH features:
- Dynamic IP management
- Availability zones
- Globally-defined resources (Cloud Config), which enable manifests that are portable across BOSH Cloud Provider Interfaces (CPIs), and are substantially smaller than old-style manifests
- Links between deployed BOSH instances consuming information from other instances, such as IP addresses
Prerequisites for deploying brokers that use ODB
For information about minimum versions of Cloud Foundry and BOSH, see Software Requirements.
Content feedback and comments