One of the guiding goals for Data Services Manager (DSM) 2.0 is to provide a very rich Kubernetes compliant API server for end-users and developers. We refer to this as the Gateway API. In this post, I will demonstrate the Gateway API server’s capabilities and show how it can be used to query the state of the objects that are provisioned through DSM, and also how to modify and manipulate these objects. The kubectl command line interface is used. We will use this tool to query and modify some of the infrastructure components, as well as query the existing data…
In this post, I want to demonstrate some of the key “day 2” features of Data Service Manager 2.0. Day 2 operations are typically operation that an administrator might carry out after a data service / database is already deployed and configured. This blog will discuss operations such as the ability for a DSM administrator to assign database ownership to a different DSM User. We will also see how it is possible to both clone an existing database and how to restore a new database from a backup. These operations will be done from the UI but I did want…
Data Services Manager (DSM) 2.0 continues to provides detailed monitoring and alerting, similar to what was available in DSM version 1.x. It continues to offer both email alerting as well as webhook integration to send notifications to Slack and ServiceNow. In this post, we will look at some of the changes in the User Interface for configuring webhooks. For the purposes of this post, we will examine the configuration of a webhook to send notifications to Slack. The creation of the webhook itself is identical to how it was configured in version 1.x, so there is no point in discussing…
Continuing on with my series of blog posts which examine the new features and functionality of VMware Data Services Manager version 2.0, this post will look at some of the vertical scaling (scale up) and horizontal scaling (scale out) in DSM 2.0. We start with a standalone PostgreSQL database deployment, and then focus on the scale out initially by changing the topology from a single node to a three node database cluster. In a standalone Postgres database, the Primary role and the Monitor role exist as separate Pods on the same VM. By changing the topology, the Primary and Monitor…
So far, we have seen how to create an infrastructure policy and how to configure the DSM Provider appliance. In this third post in the series, I will show you how to deploy a Data Service via Data Services Manager (DSM) 2.0. The data service in question is PostgreSQL, an open-source database which our telemetry tells us is a very popular database deployed on vSphere infrastructure by our customers. Let’s examine the steps involved in deploying PostgreSQL via the DSM UI, whilst also noting that DSM has a very rich API allowing deployment of these data services via various automation…
In part 1, we saw how to deploy the Data Services Manager (DSM) appliance. We also saw how to create our first infrastructure policy, and also create a permission which will allow a ‘data administrator’ to logon to the DSM appliance. In this second blog in the series, we will use this admin user to complete the DSM appliance setup tasks. Note that the DSM Appliance is often referred to as the Provider, and you will see this term used regularly in the UI and the logs. Once the Provider setup is completed, the ‘data administrator’ will then be able…
At VMware Explore 2023 in Barcelona, we made a big announcement about VMware Data Services Manager (DSM) version 2.0. In the upcoming series of blog posts, I will introduce you to the new features of DSM version 2.0. One major shift in focus is that DSM 2.0 is squarely aimed at the vSphere Administrator, allowing them to control which resources are consumed by the various data services deployed via Data Services Manager. Thus, in this first post, we will primarily focus on an integral feature of DSM 2.0 called Infrastructure Policies. Note: DSM version 2.0 is not yet generally available.…