If you have one or more Tanzu Platform for Cloud Foundry (formerly known as Tanzu Application Service or TAS) foundations, you can attach them to Tanzu Platform hub as data sources. Doing so allows you to view your Tanzu Cloud Foundry foundation alongside other resources in your Tanzu Platform hub-managed infrastructure.
When you attach a Tanzu Cloud Foundry foundation as data source in Tanzu Platform, SBOM and Spring properties data are automatically collected and sent to Tanzu Platform. You can view the collected data on Tanzu Platform hub in Applications > Business Applications and manage the applications on Tanzu Platform. However, you must configure your Spring applications and micrometer libraries to ensure that Git properties and metrics are discoverable. For more information, see Configure your Spring applications for application management in Tanzu Platform. For more information about managing your applications in Tanzu Platform, see Managing your applications in Tanzu Platform.
NoteThe SBOM and Spring properties data are captured by the droplet exporter job running on the HUB TAS Agent Bosh VM. In larger foundations, you may need to increase the CPU and Ephemeral Disk size of the HUB TAS Agent Bosh VM.
Attaching a Tanzu Cloud Foundry foundation requires the following steps:
Download and install the Tanzu Platform hub collector tile in Tanzu Operations Manager.
Collect data from the BOSH Director VM by creating new UAA client credentials.
Create a Tanzu Cloud Foundry Foundation collector in Tanzu Platform hub, then enter the provided credentials in the Tanzu Platform hub collector on Tanzu Operations Manager to establish a connection between the Tanzu Platform hub Collector tile and Tanzu Platform hub.
While you can perform some of these actions in a different order, this guide is constructed to take you through all available configuration steps in Tanzu Operations Manager before creating a Tanzu Cloud Foundry Foundation collector in Tanzu Platform hub.
NoteEach Tanzu Platform hub collector-Tanzu Cloud Foundry Foundation collector pair can support one Tanzu Cloud Foundry foundation. If you have multiple Tanzu Cloud Foundry foundations, you must add and configure a Tanzu Cloud Foundry-Hub collector per foundation.
Do the following to install the Tanzu Platform hub collector tile in the Tanzu Operations Manager Installation Dashboard:
Go to the Tanzu Platform hub page on VMware Tanzu Network.
From the Releases dropdown, select the version of the tile you want to install.
Click the name of the tile you want to install to download the .pivotal file for the tile.
Navigate to the Tanzu Operations Manager Installation Dashboard.
Click Import a Product.
Select the .pivotal
file that you downloaded from VMware Tanzu Network.
Click Open. If the tile is successfully uploaded, it appears in the product list beneath the Import a Product button.
Once the upload is complete, click the + icon next to the tile listing to add the tile to your staging area.
Click the Tanzu Hub Collector tile.
Under Place singleton jobs in AZ, select the first AZ. Tanzu Operations Manager runs any job with a single instance in this AZ.
Under Balance other jobs in AZs, select one or more other AZs. Tanzu Operations Manager balances instances of jobs with more than one instance across the AZs that you specify.
From the Network dropdown, select a subnet on which to install the collector.
ImportantMake sure that you select a subnet that has access to the TAS VMs. See Configuring BOSH Director for your IaaS.
For more information, see the Tanzu Operations Manager documentation.
The Tanzu Platform hub collector works by accessing the BOSH director VM and viewing information about deployments, then exporting that information to Tanzu Platform hub. This requires creating a new UAA client for the Tanzu Platform hub collector, the details for which differ depending on the authentication settings of your Tanzu Operations Manager to deployment.
To begin, select an authentication method and follow the instructions.
From the Tanzu Operations Manager Installation Dashboard, click the BOSH Director tile.
Select the Status tab.
Record the IP address in the IPs column of the BOSH Director row.
Select the Credentials tab.
In the Bosh Commandline Credentials row of the BOSH Director section, click Link to Credential.
Record the values for BOSH_CLIENT
and BOSH_CLIENT_SECRET
. Use these to log in to the UAA client in a later step.
For more information about internal authentication settings for your Tanzu Operations Manager deployment, see the Tanzu Operations Manager documentation.
Click the user account menu in the upper-right corner of the Tanzu Operations Manager Installation Dashboard.
Click Settings .
Select SAML Settings.
Click the Provision an Admin Client in the BOSH UAA checkbox.
Click Enable SAML Authentication.
Return to the Tanzu Operations Manager Installation Dashboard.
Click the BOSH Director tile.
Select the Status tab.
Record the IP address in the IPs column of the BOSH Director row.
Select the Credentials tab.
In the Uaa Bosh Client Credentials row of the BOSH Director section, click Link to Credential.
Record the value of password
. This value is the secret for Uaa Bosh Client Credentials.
For more information about SAML authentication settings for your Tanzu Operations deployment, see the Tanzu Operations Manager documentation
Click the user account menu in the upper-right corner of the Tanzu Operations Manager Installation Dashboard.
Click Settings .
Select LDAP Settings.
Click the Provision an Admin Client in the BOSH UAA checkbox.
Click Enable LDAP Authentication.
Return to the Tanzu Operations Manager Installation Dashboard.
Click the BOSH Director tile.
Select the Status tab.
Record the IP address in the IPs column of the BOSH Director row.
Select the Credentials tab.
In the Uaa Bosh Client Credentials row of the BOSH Director section, click Link to Credential.
Record the value of password
. This value is the secret for Uaa Bosh Client Credentials.
For more information about LDAP authentication settings for your Tanzu Operations deployment, see the Tanzu Operations Manager documentation
Once you have the credentials for your authentication method, you can connect to the Tanzu Operations Manager VM:
Establish an SSH connection with the Tanzu Operations Manager VM by following the procedure in the Tanzu Operations Manager documentation.
Target the UAA instance for the BOSH Director by running:
uaac target https://BOSH-DIRECTOR-IP:8443
Where BOSH-DIRECTOR-IP
is the IP address for the BOSH Director VM that you recorded from the Status tab in the BOSH Director tile in a previous step.
Log in to the UAA instance by running:
uaac token client get
When prompted, enter the credentials you recorded in the previous step for client and secret.
Create a UAA client for the Tanzu Platform hub collector by running:
uaac client add hub-tas-collector \
--secret 'CLIENT-SECRET' \
--authorized_grant_types client_credentials,refresh_token \
--authorities bosh.read \
--scope bosh.read
Where:
CLIENT-SECRET
is the secret you want to set for the UAA client.Return to the Tanzu Operations Manager Installation Dashboard.
Click the Tanzu Hub Collector tile.
Click Collector Configuration.
For BOSH UAA client credentials, enter hub-tas-collector
for the username and the secret for the UAA client you just created.
If your deployment of Tanzu Operations Manager uses a self-signed certification, click the Skip TLS Verification when Querying Ops Manager API checkbox. Otherwise you can leave it blank.
For Link TAS Entities to IAAS Entity Collection, click Disable.
For Log level, enter info
.
For HTTP Proxy Configuration if you need to egress entities through an HTTP proxy on your network, then select Enable and configure the fields for your proxy server.
Click Save.
With the Tanzu Platform hub collector in Tanzu Operations Manager mostly configured, you must also create Tanzu Cloud Foundry Foundation collector in Tanzu Platform hub. The process is similar to attaching a Kubernetes cluster.
In Tanzu Platform hub, select Setup & Configure > Foundation Management.
Click Add New.
Enter a name for your foundation. It’s a best practice use the same name as your Tanzu Operations Manager.
Click Next.
Select a method for configuring the Tanzu Cloud Foundry foundation collector.
Copy all the configuration details to a text file as a back-up during this procedure.
Log in to Tanzu Operations Manager while keeping the Tanzu Platform hub page open.
From Tanzu Operations Manager, select the tile for your Tanzu Platform hub collector.
Click Tanzu Hub Configuration.
Enter the configuration details copied from Tanzu Platform hub in the matching fields for Tanzu Operations Manager.
Click Save.
Download the provided YAML file and rename it to your preference.
Open your preferred CLI shell on an environment where the Tanzu Operations Manager CLI is installed.
Upload the YAML file to the host, then run this command to configure the collector:
$ om configure-product -c <filename>.yaml
Go back to the Tanzu Platform hub page and click Complete.
To verify your stemcell version and apply all changes:
Click Stemcell Library. For more information about using the Stemcell Library, see Importing and managing stemcells.
Verify and, if necessary, import a new stemcell version.
From the Tanzu Operations Manager Installation Dashboard, click Review Pending Changes.
Click Apply Changes.
Return to Tanzu Platform hub and click Complete. Once configuration is complete, you should see your Tanzu Cloud Foundry foundation listed with a Pending status. It may take up to 20 minutes for Tanzu Operations Manager and Tanzu Platform hub to begin communicating, at which point the status should change to Ready.
You can view your Tanzu Cloud Foundry Foundation by going to Infrastructure > Foundations in Tanzu Platform hub and find it in the list of Foundations on the dashboard.
To send TAS logs to Tanzu Platform, do the following setup in Tanzu Ops Manager. After you have done the following configurations, you can view the logs in Tanzu Platform hub.
To view the TAS Platform logs, on Tanzu Platform hub, go to Infrastructure > Foundations.
To view application logs, on Tanzu Platform hub, go to Applications > Apps and microservices.
On the Ops Manager Installation Dashboard, do the following:
telegraf.hub-collector.service.internal
.6515
.TCP protocol
.Follow these steps for TAS 5 and above versions deployed in a secure environment. If the deployment is in a non-secure environment, see Configure Application Logs for version below TAS 5 versions.
Click the Credentials tab:
Escape newline characters from credential values.
printf -- <private_key_pem>
printf -- <cert_pem>
syslog-tls://telegraf.hub-collector.service.internal:6514
.Certificate Authority
is the Ops Manager root CA.Client Certificate
is the cert_pem of the CF Hub Collector Syslog mTLS credential.PRIVATE_KEY_PEM
is the private_key_pem of the CF Hub Collector Syslog mTLS credential.Follow these steps for versions below TAS 5 and for deployments in non-secure environments. Use these steps for TAS 5 and above versions if the deployment is in a non-secure environment.
syslog://telegraf.hub-collector.service.internal:6514
.When you connect a Cloud Foundry foundation, alerts are automatically deployed for the foundation. To see the alerts that are deployed, on Tanzu Platform hub, in the left navigation pane, go to Setup & Configuration > Alert Management.
You can enable or disable the alert, configure the trigger conditions, and set the notification target.
For information about setting up a notification target, see Add alert notifications.