Creating Databases for TAS for VMs
Page last updated:
Warning: VMware Tanzu Application Service for VMs (TAS for VMs) v2.9 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic provides an example procedure for creating the necessary databases on your external database instance so that you can deploy VMware Tanzu Application Service for VMs (TAS for VMs) with an external database.
Warning: Protect whichever database you use in your deployment with a password.
To create your TAS for VMs databases, do the following:
Note: Exact configurations depend on your database provider. The following procedure uses AWS RDS as an example.
ubuntuaccount key pair from your IaaS deployment to your local SSH profile so that you can access the Ops Manager VM. For example, in AWS, you add a key pair created in AWS:
$ ssh-add aws-keypair.pem
SSH in to your Ops Manager using the Ops Manager FQDN and the username
$ ssh ubuntu@OPS-MANAGER-FQDN
Log in to your MySQL database instance using the appropriate hostname and user login values configured in your IaaS account. For example, to log in to your AWS RDS instance, run the following MySQL command:
$ mysql --host=RDSHOSTNAME --user=RDSUSERNAME --password=RDSPASSWORD
Run the following MySQL commands to create databases for the eleven TAS for VMs components that require a relational database:
CREATE database ccdb; CREATE database notifications; CREATE database autoscale; CREATE database app_usage_service; CREATE database routing; CREATE database diego; CREATE database account; CREATE database nfsvolume; CREATE database networkpolicyserver; CREATE database silk; CREATE database locket; CREATE database uaa; CREATE database credhub;
exitto quit the MySQL client, and
exitagain to close your connection to the Ops Manager VM.