This is the third blog post in a series which describe how to get started with VMware Data Services Manager (DSM), a VMware solution that offers on-demand provisioning and automated management of databases on vSphere environments. In a previous installment, the deployment and configuration of the Provider appliance was discussed. In a follow up post, the steps to provision and configure an Agent were described. In this final installment related to the deployment of DSM, the addition of users is covered. So far the only user we have been dealing with is the Provider Admin. In this post, we will…

After a successful deployment and configuration of the Provider appliance in my most recent post of VMware Data Service Manager, it is now time to turn our attention to the Agent appliance. This component is responsible for initiating operations on a particular vSphere cluster. An Agent can only be part of a single vSphere cluster. However, multiple agents, which are provisioned across many vSphere clusters, can all be managed from a single Provider UI. Just like the Provider appliance, the Agent is also delivered as a .OVA which is available for download from both VMware Tanzu Network and VMware Customer…

In a recent post, I highlighted how VMware Data Services Manager (DSM) is designed to help vSphere Administrators control and manage the deployment of many disparate databases on their vSphere infrastructure. At the same time, I discussed how DSM is also designed to provide self-service to developers when they need to quickly provision a new database. This avoids the often prolonged ticketing system to engage IT to roll out the database on behalf of developers. In this post, I am going to take a more practical look at DSM, with a goal of rolling out the ‘Provider’ part of the…