Getting started with Data Services Manager v2.1

The latest version of Data Services Manager (DSM) is now available. DSM version 2.1 delivers a new set of capabilities and functionality, including simplified deployment, MySQL Clustering, LDAP access to databases, Certificate Management, and log shipping enhancements. In this post, I will go through the deployment process of DSM version 2.1 as there are some significant differences when compared the 2.0.x user experience. Our aim is to make the whole process of deployment in 2.1 a lot easier. In future posts, I will look at the other enhancements in more detail, but for now I just want to focus on…

Data Services Manager version 2.1 now available

It gives me great pleasure to announce the availability of Data Services Manager version 2.1. The team have been working tirelessly on this release to deliver on new features and functionality. In this post, I will cover a number of the big ticket items found in this release. In later posts, I will delve into these features in more detail, so watch this space. Visit the DSM section of the Broadcom Support Portal to download the product. VMware Cloud Foundation customers are automatically entitled to DSM, and in this release we are making it even easier to stand up your…

Data Services Manager Air-Gap deployment steps

Many customers have data centres which have restricted access to the outside world, commonly referred to as air-gapped. This was well understood in the early design stages of Data Services Manager (DSM), which led to the creation of an air-gap deployment methodology. Therefore customers who could not avail of the automatic download mechanism for database templates and updates could manually populate their provider repository with manually downloaded images. However, customers who wish to deploy the current version of DSM (v2.0.3) today will also have to use the air-gap approach to add the database templates to their provider repository. This is…

Provisioning databases with Aria Automation, Cloud Consumption Interface and Data Services Manager – Part 3: CCI Config

In this series of posts, we saw in part 1 how to setup Aria Automation version 8.17. This is required for Cloud Consumption Interface support. In part 2, we saw how to enable the Cloud Consumption interface (CCI) in the Supervisor of vSphere with Tanzu. However, even though CCI is now deployed as a Supervisor Service, it is not yet completely configured to work with Aria Automation. Thus, it is still not yet possible for an Aria Automation user to interact with the Supervisor in vSphere with Tanzu to create TKG clusters or VMs using the VM Service. This is…

Provisioning databases with Aria Automation, Cloud Consumption Interface and Data Services Manager – Part 2: CCI

In the part 1 blog post, we discussed how to setup Aria Automation version 8.17 so that it could be used with Cloud Consumption Interface (CCI) to provision databases using Data Services Manager. In this post, we will look at the steps to integrate Aria Automation with CCI. There is a dependency here on vSphere 8.0U2 and vSphere with Tanzu, which we will assume has already been deployed. Thus, the main task at this point is to setup and enable the CCI Service on the Supervisor Cluster of vSphere with Tanzu. (Although I haven’t done a blog post of vSphere…

DSM + MinIO: Certificate chain obtained from endpoint is incomplete or empty

I recently worked with one of our customers to configure MinIO object storage on-premises.  The plan was to create a number of S3 compatible buckets to provide image, backup and log repositories for VMware Data Services Manager v2.0.x. For security reasons, the customer wanted to create an intermediate certificate of authority (CA), and use that to sign the leaf certificates rather than sign them with a root CA. This is common practice. However, the customer hit the above issue when trying to use the MinIO object store buckets with the leaf certs created from the intermediate cert. I decided to…

Creating a “least privileged” service account for Data Services Manager 2.0.x

Earlier this week, a customer reached out about the installation requirements for Data Services Manager 2.0.x. One of the steps in the installation documentation states the requirement for a vCenter SSO Username. The doc added that this has to be the vCenter server administrator’s SSO username. And even though these SSO admin credentials are not stored, and are in fact discarded after creating a dedicated vCenter service account for VMware Data Services Manager, the customer asked if there was a way to create a “least privileged” user for creating a DSM service account. The answer is yes. This post will…