In this blog post, we will walk through the configuration steps for setting up Data Services Manager (DSM) and connecting that to VCF Automation (VCFA), allowing us to deploy a Vector Database which is a requirement for configuring VMware Private AI Services (PAIS).
Requirements:
Additional References:
I recently deployed the latest release of VMware Data Services Manager (DSM) 9.0 in my VMware Cloud Foundation (VCF) 9.0 lab to explore the new integration with VCF Automation (VCFA), allowing organizations to enable a true Database-as-a-Service (DBaaS) for their users.
While setting up the connection from VCFA to DSM, I ran into the following error:
VCFABinding CR is not ready in 50 seconds, with reason: VCFABinding CR is not ready: failed to create VCFA TM client: Get "https://auto01.vcf.lab:443/api/versions": tls: failed to verify certificate: x509: certificate signed by unknown authority
From the error message, it looks like DSM is having an issue validating the self-signed TLS certificate from VCFA, which I figured most users would be using, especially within a lab environment.
After a bit of searching around, I came to learn this was a known issue mentioned in the DSM Release Notes and it pointed to this Broadcom KB 398007, that outlined the solution but it was still missing some details.