This would also serve our own needs in supporting the multiple microservices we would need for deploying databases. We wanted to provide the different teams supporting Astra with the ability to get their code from feature branch to production in as automated a manner as possible. When we built it, one of our primary goals was self-service. The one commonality among them, though, is the Control Plane. Each of these areas can be further broken down into other smaller services, all of which are developed and maintained by multiple teams. There are numerous other supporting services and jobs required to make it a success, including our web UI, billing process and user management. Enabling Developersĭeploying the database may be one of the most important functions of the Control Plane, even though it’s only a small part of what it takes to run Astra DB. In order to facilitate this and other functionality around Astra, we built the Astra Control Plane. Since we were building DataStax Astra DB on top of DSE, this is what we needed to accomplish. Now imagine doing that thousands of times, in a reliable manner, and at the push of a button. Maybe deploying a single DSE cluster is a little involved. Since we’re collecting metrics for monitoring, it would also be good to have a way to securely view them. Of course, there’s also ensuring your external clients can access certain ports while not being able to access others.
Then it would be good to make sure the servers can communicate with each other on the right ports. Oh wait - first you should provision a few servers for it to run on.
#Controlplane sound install
Download the tarball, run the install script and you’re done.
Jim is a senior software engineer at DataStax, focusing on Kubernetes and database orchestration.Īfter years of iterations and improvements, deploying a DataStax Enterprise (DSE) cluster is a pretty painless process.
0 kommentar(er)
