You can integrate your brokered service more closely with VMware Tanzu Operations Manager to create a managed service and service tile for VMware Tanzu.
The next level of integration is to get your service to be deployed on VMware Tanzu Operations Manager rather than externally, on the same IaaS that your particular Cloud Foundry instance is deployed on, and by the same orchestration tool, BOSH.
This is usually one of the more involved integrations, because you configure your packaging to allow your service components to deploy BOSH onto the VMware Tanzu Operations Manager infrastructure.
When you offer your software as a managed service, it means that you do not have to learn different ways to deploy, manage, and monitor different components of your application platform.
As with the brokered service, the service has a service broker and a tile listed on VMware Tanzu Network. VMware Tanzu Network lists managed services as “for VMware Tanzu,” without “Service Broker” in the name.
To integrate your service at this level, you learn about stemcells, BOSH releases, and manifests. You can decide how your service maps to a virtual machine and how persistent storage is managed.
The Minimal Viable Product (MVP) version of a managed service is a single, shared service instance. This integration level is mostly about getting the BOSH packaging, deployment, and monitoring working correctly.
Once you have a managed service, you may decide to prioritize either on-demand provisioning of service instances, or making your single shared service instance more highly available.
When properly configured, BOSH monitors and restarts any failing processes and VMs that are part of your service deployment. To further increase availability, consider spreading your resources across multiple AZs or even regions, and replicating your persistent storage across those as well.
For BOSH to manage your service, you must create a BOSH release for it. BOSH releases explains how to do this, and how to use your already existing Docker image as a shortcut.
After you create a BOSH release for your managed service integration, you can work through Building your first tile to create your tile.
The Tile generator tool automatically creates the life cycle errands that can run after a VMware Tanzu Operations Manager tile is deployed or before it is removed. You control which errands run the next time when you click Apply Changes to redeploy.
See the Errands for how VMware Tanzu Operations Manager to control when errands run, and how to set default errand run rules in the tile.
At any level of integration, VMware recommends and supports using Concourse for continuous integration during development.