Hello DoJo!!
We have in our organization recently deployed a DMS with a 3 DMAs nodes, 3 nodes Cassandra cluster and 3 nodes OpenSearch cluster over our corporate VMWare virtualization platform.
We would like to install locally a DMA Community Edition with Cassandra and OpenSearch, for learning purposes. I have several questions about this. By the way, DaaS and STaaS are not a possible option.
Should this DMA be included in our current DMS or should we create a dedicated DMS? Our initial idea was to create a new dedicated DMS for this DMA Community Edition.
If we create a new DMS. Is it possible use our already deployed production Cassandra and OpenSearch cluster for it? Even if it's possible, is it a good idea?
If that's not possible, what would be the most suitable on-premise/self-managed architecture for a DM Community Edition with Cassandra and OpenSearch?
Best regards,
Fernando Ejarque
Hi Fernando,
In addition to what Jordy said, i want to comment on your question:
If we create a new DMS. Is it possible use our already deployed production Cassandra and OpenSearch cluster for it? Even if it's possible, is it a good idea?
It is possible to use the same database clusters for several DataMiner systems simultaneously. In this case, you need to make sure that your Production and Test DataMiner systems use different database prefixes (see Configuring the general database settings | DataMiner Docs).
However, such setup is not ideal for sharing the database between the Production and the Test DataMiner system:
- In case of a configuration mistake, e.g. identical database prefixes used by both the Test and the Production systems, the data generated by the Test system may corrupt the Production data.
- A test running out of hand in the Test environment may cause a database outage, which will affect the Production system.
Therefore, although sharing the database between DataMiner systems is possible, creating an isolated database for a test DataMiner system is a safer approach.
Hi Fernando,
Let's first evaluate which license type would be the best fit in your situation.
Please note that a community edition license has some limitations: only for a standalone system, only community support is possible, and there is a monthly service limit to take into account.
Have you also considered a Staging license or a time-limited (demo) license? Here we don't have the aforementioned limitations, but only that such a license cannot be integrated into a regular DMS.