About Data Management for VMware Tanzu
Data Management for VMware Tanzu (DMS) enables Enterprise organizations to host their own Database-as-a-Service offering on VMware-based infrastructure.
The following table identifies the supported component versions for Data Management for VMware Tanzu version 1.0.x:
|Data Management for VMware Tanzu Version
||VMware vSphere Version
7.0 update 2
7.0 update 2
||10.15.0, 11.10.0, 12.7.0
Upgrading to 1.0.x
If you have configured a Tanzu Net Token, Data Management for VMware Tanzu will automatically download a new release and upgrade the control plane software and templates in your installation.
If you deployed Data Management for VMware Tanzu in an air-gapped environment, you must download the new DMS release and manually populate the templates and software updates in the Provider Repo.
Release Date: August 12, 2021
New Database Versions Supported
Data Management for VMware Tanzu 1.0.1 includes support for these new PostgreSQL versions:
Starting with version 1.0.1, VMware distributes the Data Management for VMware Tanzu Provider and Agent virtual appliance
.ovas and the Air-gap Environment Repository on VMware Customer Connect in addition to distributing this software on VMware Tanzu Network.
Data Management for VMware Tanzu 1.0.1 resolves these issues:
Promote Replica fails for PostgreSQL 10 and 11
Due to a file permission error, promoting a Replica to Primary fails when the database Service Instance was deployed with PostgreSQL 10.x or 11.x.
Template publishing occasionally fails
Publishing a template occasionally fails when the Provider Repo is located in AWS S3.
Release Date: July 19, 2021
This is the first release of Data Management for VMware Tanzu.
Data Management for VMware Tanzu version 1.0.0 includes the following:
Simplified Database Provisioning and Management for Users:
- Provision and manage MySQL and PostgreSQL database instances from a simple, intuitive graphical user interface.
- Provision single node and high availability deployment of database instances in just a few clicks.
- Define daily backup window for automated scheduled backups, or take a backup on-demand.
- Define distinct retention policies on multiple storage endpoints to store backups for different levels of Recovery Time Objectives (RTO).
- Fully restore, or perform a point-in-time recovery of, data from database backups and transaction logs.
- Define a weekly maintenance window for automated updates of database server software and security patching, or update the database server on-demand.
- Generate a log bundle from an impaired database instance for further troubleshooting and root cause analysis.
- Monitor the health of individual database instances using metrics on resource utilization, database activity, and usage.
Tailored Managed Data Services Offering for Providers:
- Group users with common access to infrastructure resources into organizations.
- Share common infrastructure across multiple organizations.
- Use templates to curate and manage the database versions that are available for new database provisioning.
- Restrict instance creation and scaling to predefined Instance Plans, and scale the resources any time as necessary.
- Store database backups to any S3-compatible object storage (AWS S3, MinIO, Dell ECS etc.).
Centralized Control Plane Management for Providers:
- Install, deploy, and register the DMS control plane on vSphere infrastructure using the graphical installer interface.
- Deploy the control plane with high availability.
- Enable LDAP-based authentication for the Data Management for VMware Tanzu installation.
- View the alerts that DMS automatically raises when it detects connectivity issues that would impact normal operation of the control plane.
- Examine the audit log of operations performed on the control plane.
- Generate a log bundle for the Provider VM for further troubleshooting and root cause analysis.
- Data Management for VMware Tanzu periodically checks for software updates on the control plane; view and apply these updates.
- Monitor MySQL and PostgreSQL database instances across multiple vSphere clusters from the control plane.
Centralized Infrastructure Management:
- Monitor the health of individual Agent VMs using metrics that DMS generates for resource utilization and the health of Agent services.
- View the preemptive and active alerts that DMS raises when the normal operation of an Agent running on an Onboarded Cluster is impacted in a way that would affect provisioning and management operations.
- Use an aggregated view of alerts to monitor the overall health across all Agent VMs, identifying those agents that require attention.
- Generate a log bundle from an impaired Agent VM for further troubleshooting and root cause analysis.
- Rely on the automatic software updates that Data Management for VMware Tanzu automatically applies on the Agent VM.
Known Issues and Limitations
Data Management for VMware Tanzu 1.0.x has these known issues and limitations:
- You cannot define multiple networks when you onboard new infrastructure to DMS.
- You cannot update infrastructure configuration after you have deployed any database instances.
- You cannot remove infrastructure from DMS after you have deployed any database instances, even if you delete all of the instances.
- When organizations share infrastructure:
- There is no CPU, network, or storage isolation between their workloads.
- All database instances running on shared infrastructure must have a common sub-domain.
Organizations and Users:
- You cannot remove an organization after you create it.
- You cannot remove a local user from DMS after the user has created any database instances. Current workaround:
- Revoke the user's access to DMS by resetting the user's password.
- Have the Organization Administrator manage the user's database instances, backups, and logs.
- All DMS user management is performed by the Provider Administrator user. Organization Administrators do not manage users, nor can they even view the users in their organization.
- A user is permitted to modify only certain configuration properties after a database instance is successfully provisioned.
- You cannot change the database server administrative password from the console or API after the instance has been provisioned.
- You must change this password using a database client.
- When you change this password, the new password is not reflected in DMS.
- If you update a Custom CA after database creation, you must update the CA on each individual database instance.
- All failover operations (promote Standby Provider to Primary, Promote Read Replica to Primary) are automated, but require user intervention.