-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Yes, the UI can be white-labeled.
2019 and 2022.
Not at this time due to MongoDB SSPL license restrictions (Server Side Public License FAQ ).
Yes.
No.
Not yet, but we are working on supporting CloudStack.
Not yet, but we are working on supporting VMWare.
Not yet, but we have plans to support it in the future.
Not yet, but we have plans to support it in the future.
No.
Self hosted in partner’s data center.
No, with the exception of Microsoft SQL Server.
There are a couple of ways to meter and charge your customer.
CCX can provide you with information as to when virtual machines are created for the database. Using this information you can come up with what to charge your customer.
A metering service in CCX is currently being developed. You will be able to use this service to calculate what to charge your customer.
Not yet.
No, databases are deployed on virtual machines.
Is customer database deployed in a global project or customer’s project (in relation to Openstack, etc., project)?
Global project.
Yes, by default CCX places database hosts in different availability zones.
Yes, but please reach out to [email protected].
You host it in your Kubernetes cluster.
A Kubernetes cluster with ingress controller (load balancer), persistent volume, a floating IP, and a registered domain.
CCX requires 1.22 or later.
No, they are independent upgrades.
No. As updates are made available by the respective database authority, they will in turn made available in CCX.
Yes, CCX uses a rolling forward upgrade mechanism.
CCX automatically takes full and incremental backups based on predefined backups schedules.
Yes.
Is the database deployed in a private network (akin to virtual a private cloud - VPC) or a globally accessible public network with appropriate firewall protection?
Global network with a firewall to restrict access.
No.
Yes, SSL is used for all inter-host and client/server communications.
Backups are stored in S3-compatible storage. All backups are encrypted by default.
The CCX UI (and API) provide a mechanism to restore from an existing backup.
Yes.
No, the database is auto-tuned by CCX.
Yes, all standby database nodes are available for Reads. The only exception to this rule being is Microsoft SQL Server.
As many as you like.
Yes.
Yes.
No.
Typically, less than 30 secs of connectivity loss to the Primary (Write) database host.
Does the CCX operator have access to an Administrator/Operator view of all the deployed clusters by CCX?
Yes, the admin UI provides this capability.
The “Query” tab in the UI allows for this.
Yes.
No.
Yes.
Some parameters are modifiable.
We do not modify the storage of an existing instance. To grow the storage or instance type, the user must add a new node. Then decommission the old one.
By adding a node with another instance type.
Yes, we have “add node”.
The Terraform provider authenticates using an OAUTH2 token created in the CCX UI. See CCX Terraform Provider .