Resources

In the Resource Config pane, you must associate load balancers with the VMs in your deployment to activate traffic. For more information, see Configure Load Balancing for TAS for VMs.

Scale down and deactivate resources (Optional)

Note The Resource Config pane has fewer VMs if you are installing Small Footprint TAS for VMs. For more information, see Differences in Small Footprint TAS for VMsTAS for VMs.

Important Small Footprint TAS for VMs does not default to a highly available configuration. It defaults to the minimum configuration. To make Small Footprint TAS for VMs highly available, scale the Compute, Router, and Database VMs to 3 instances and scale the Control VM to 2 instances.

TAS for VMs defaults to a highly available resource configuration. However, you might need to follow additional procedures to make your deployment highly available. For more information, see High availability in TAS for VMs and Scaling TAS for VMs.

If you do not want a highly available resource configuration, you must scale down your instances manually by navigating to the Resource Config section and using the drop-down menus under Instances for each job.

By default, TAS for VMs also uses an internal filestore and internal databases. If you configure TAS for VMs to use external resources, you can deactivate the corresponding system provided resources in Tanzu Operations Manager to reduce costs and administrative overhead.

To deactivate specific VMs in Tanzu Operations Manager:

1. Select Resource Config.

2. If you configured TAS for VMs to use an external S3-compatible filestore, enter 0 in Instances in the File Storage field.

3. If you selected External when configuring the UAA, System, and CredHub databases, edit these fields:

   • MySQL Proxy: Enter 0 in Instances.
   • MySQL Server: Enter 0 in Instances.
   • MySQL Monitor: Enter 0 in Instances.

4. If you deactivated TCP routing, enter 0 Instances in the TCP Router field.

5. Click Save.

Scaling down Logging and Metrics infrastructure (Optional)

Logging and metrics functionality can be provided via the legacy Loggregator architecture or the newer Shared Nothing architecture.

If you are confident that you are not using the V1 or V2 firehoses you can scale the Doppler Server and Loggregator Trafficcontroller instance groups to zero to reduce costs.

Important Before scaling dopplers and traffic controllers to zero instances, you must validate that none of the products deployed alongside TAS for VMs are using the V1 or V2 Firehoses. You should also deselect the Enable V1 Firehose and Enable V2 Firehose fields in the System Logging pane. The Deploy Metric Registrar field must also be deselected because Metric Registrar relies on the firehose. For more information about configuring these fields, see System Logging.

If you are still reliant on the Firehose for egressing metrics (but have moved to syslog for egressing application logs) you can select the Do not forward app logs to the Firehose option in the System Logging pane to reduce the required footprint of your dopplers and traffic controllers.