diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md index 26095e6c06c..5465bb79159 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md index c01c9aab144..9a569a69308 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md index ebd71894163..a95cbcdfd05 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md index ebd71894163..a95cbcdfd05 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md index a5ac98f22bd..b820f902dee 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md @@ -2095,45 +2095,6 @@ Ce groupe de permissions reprend les droits anciennement porté par le rôle nic { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md index a5ac98f22bd..b820f902dee 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md @@ -2095,45 +2095,6 @@ Ce groupe de permissions reprend les droits anciennement porté par le rôle nic { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md index 88704327e8e..6d80c14eff6 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md index e12454364a2..3082037fa1d 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md index f43dd1af7ce..21258d3f7f3 100644 --- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md +++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md @@ -2097,45 +2097,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro { "action": "publicCloudProject:apiovh:database/capabilities/get" }, - { - "action": "publicCloudProject:apiovh:database/cassandra/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/backup/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/advancedConfiguration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/capabilities/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/certificates/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/integration/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/ipRestriction/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/logs/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/maintenance/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/metric/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/node/get" - }, - { - "action": "publicCloudProject:apiovh:database/cassandra/user/get" - }, { "action": "publicCloudProject:apiovh:database/grafana/advancedConfiguration/get" }, diff --git a/pages/account_and_service_management/startup-program/06-available-products/guide.en-gb.md b/pages/account_and_service_management/startup-program/06-available-products/guide.en-gb.md index 9ba52e3f60b..8fe5b75efba 100644 --- a/pages/account_and_service_management/startup-program/06-available-products/guide.en-gb.md +++ b/pages/account_and_service_management/startup-program/06-available-products/guide.en-gb.md @@ -45,7 +45,7 @@ Here is a summary of eligible solutions: | **Storage & Backup**: Block Storage, Object Storage, Cloud Archive, Cold Archive, Snapshot, Backup | ✅ | | **Network**: Load Balancer, vRack (Free), Bandwidth, Floating IP, Gateway, Anti-DDoS | ✅ | | **Containers & Orchestration**: Managed K8s Service, Managed Rancher Service, Managed K8s Load Balancer, Managed Private Registry, Workflow Management, Image Catalog | ✅ | -| **Databases**: MySQL, PostgreSQL, MongoDB, Valkey, Cassandra | ✅ | +| **Databases**: MySQL, PostgreSQL, MongoDB, Valkey | ✅ | | **Data Analytics**: Data Processing, Kafka,Caching, Managed OpenSearch, Kafka MirrorMaker, Kafka Connect, Grafana, Logs Data Platform | ✅ | | **AI & Machine Learning**: AI Notebooks, AI Training, AI Deploy, AI Endpoints | ✅ | | **Quantum computing**: Quantum Notebooks | ✅ | diff --git a/pages/account_and_service_management/startup-program/06-available-products/guide.fr-fr.md b/pages/account_and_service_management/startup-program/06-available-products/guide.fr-fr.md index d78b315b1ce..26f6be97720 100644 --- a/pages/account_and_service_management/startup-program/06-available-products/guide.fr-fr.md +++ b/pages/account_and_service_management/startup-program/06-available-products/guide.fr-fr.md @@ -45,7 +45,7 @@ Voici un résumé des solutions éligibles : | **Storage & Backup** : Block Storage, Object Storage, Cloud Archive, Cold Archive, Snapshot, Backup | ✅ | | **Network** : Load Balancer, vRack (Free), Bande passante, Floating IP, Gateway, Anti-DDoS | ✅ | | **Containers & Orchestration** : Managed K8s Service, Managed Rancher Service, Managed K8s Load Balancer, Managed Private Registry, Workflow Management, Image Catalog | ✅ | -| **Databases** : MySQL, PostgreSQL, MongoDB, Valkey, Cassandra | ✅ | +| **Databases** : MySQL, PostgreSQL, MongoDB, Valkey | ✅ | | **Data Analytics** : Data Processing, Kafka,Caching, Managed OpenSearch, Kafka MirrorMaker, Kafka Connect, Grafana, Logs Data Platform | ✅ | | **AI & Machine Learning** : AI Notebooks, AI Training, AI Deploy, AI Endpoints | ✅ | | **Quantum computing** : Quantum Notebooks | ✅ | diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md index 1a8fbf47bbf..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md index c641f362988..e986d9d3744 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md index 9dd5a7ecd30..a1d74baada5 100644 --- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md +++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md @@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden. | C: Is consulted during the process | | I: Is informed of the results of the process | -For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster. +For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Kafka cluster. ### 1. Before subscription diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md deleted file mode 100644 index 689beb60a4a..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/de/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md deleted file mode 100644 index 805198a6f16..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/asia/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md deleted file mode 100644 index 63cdc4a20df..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-au/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md deleted file mode 100644 index 2e1fc821b15..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-ca/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md deleted file mode 100644 index 48251f34bd0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-gb/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md deleted file mode 100644 index 6cfd1e81279..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-ie/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md deleted file mode 100644 index 559f29b0e30..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-sg/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md deleted file mode 100644 index 557ad875223..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md deleted file mode 100644 index 45ba42330ff..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/es-es/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md deleted file mode 100644 index 87d7b160169..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/es/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md deleted file mode 100644 index 3386d1c88c7..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capacités et limitations (EN) -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/fr-ca/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md deleted file mode 100644 index f60396b999b..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capacités et limitations (EN) -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/fr/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md deleted file mode 100644 index c45222b80b3..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/it/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md deleted file mode 100644 index d591a05e862..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/pl/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md deleted file mode 100644 index 0ea13ded205..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Cassandra - Capabilities and Limitations -excerpt: Discover the capabilities and limitations of Public Cloud Databases for Cassandra -updated: 2025-08-25 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This page provides the technical capabilities and limitations of the Public Cloud Databases' Cassandra offer. - -We continuously improve our offers. You can follow and submit ideas to add to our roadmap at . - -## Capabilities and limitations - -### Supported regions and multi-AZ - -The Public Cloud Databases offer is available in the following regions: - -- `BHS` (Beauharnois, Canada) -- `DE` (Frankfurt, Germany) -- `GRA` (Gravelines, France) -- `SBG` (Strasbourg, France) -- `SGP` (Singapore, Singapore) -- `UK` (London, United Kingdom) -- `WAW` (Warsaw, Poland) - -Entire database instances have to be in the same region. - -### Cassandra versions - -The Public Cloud Databases offer supports the following Cassandra versions: - -- Cassandra 4.1 - -Cassandra recommends always installing and using the latest stable version. - -### Plans - -Three plans are available: - -- *Essential* -- *Business/Production* -- *Enterprise/Advanced* - -Here is an overview of the various plans' capabilities: - -| Plan | Number of nodes by default | -| --------------------- | -------------------------- | -| *Essential* | 3 | -| *Business/Production* | 3 | -| *Enterprise/Advanced* | 6 | - -Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention. - -#### Nodes and replicas - -- **Essential**: The cluster is delivered with 3 nodes by default. -- **Business/Production**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned. -- **Enterprise/Advanced**: The cluster is delivered with 6 nodes by default. Adding read replicas is planned. - -#### License type - -Each cluster is provided with the Cassandra Community (GPL) license. - -If any, license cost is included inside the service plans. You can't bring your own licenses. - -### Hardware resources - -For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/pt/public-cloud/prices/#9482). - -### Features - -#### Network - -Public as well as private networking (vRack) can be used for all the offers. - -Ingress and Egress traffic are included in the service plans and unmetered. - -The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management. - -##### Private network considerations - -Here are some considerations to take into account when using private network: - -- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first. -- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup. -- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services. -- OpenStack subnets routes announcement will not be applied to your services. -- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network. - -##### Authorised IPs - -Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable. - -#### Advanced parameters - -You can further customise your Cassandra by using advanced parameters. See the [Advanced parameters references documentation](/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references) for more information on the supported parameters. - -#### Backups - -Your services are automatically backed up daily. Backup retention is 4 days for daily backups. - -See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information. - -#### Logs and metrics - -Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide. - -- **Logs retention**: 1000 lines of logs -- **Metrics retention**: 1 calendar month - -Please note that if the database instance is deleted, logs and metrics are also automatically deleted. - -## We want your feedback! - -We would love to help answer questions and appreciate any feedback you may have. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Are you on Discord? Connect to our channel at and interact directly with the team that builds our databases service! diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/meta.yaml b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/meta.yaml deleted file mode 100755 index 5ca47b3781f..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/meta.yaml +++ /dev/null @@ -1,5 +0,0 @@ -id: ccf013e8-6988-486c-86af-b9a462ca9e35 -full_slug: public-cloud-databases-cassandra-capabilities -engine: cassandra -section: dashboard -reference_category: public-cloud-databases-cassandra-guides \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.de-de.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.de-de.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.de-de.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-asia.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-asia.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-au.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-au.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-au.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-ca.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-ca.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-gb.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-gb.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-ie.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-ie.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-sg.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-sg.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-us.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-us.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.en-us.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.es-es.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.es-es.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.es-es.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.es-us.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.es-us.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.es-us.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.fr-ca.md deleted file mode 100644 index ace4a582ac5..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.fr-ca.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configurez votre instance Cassandra pour accepter les connexions entrantes (EN) -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.fr-fr.md deleted file mode 100644 index ace4a582ac5..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.fr-fr.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configurez votre instance Cassandra pour accepter les connexions entrantes (EN) -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.it-it.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.it-it.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.it-it.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.pl-pl.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.pl-pl.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.pt-pt.md deleted file mode 100644 index c8f390c4bc0..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/guide.pt-pt.md +++ /dev/null @@ -1,91 +0,0 @@ ---- -title: Cassandra - Configure your Cassandra instance to accept incoming connections -excerpt: Find out how to configure your Cassandra instance to accept incoming connections -updated: 2025-07-07 ---- - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. - -**This guide explains how to configure your Cassandra instance to accept incoming connections.** - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- Access to the [OVHcloud Control Panel](/links/manager) -- A Cassandra database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) - -## Instructions - -### Configure your Cassandra instance to accept incoming connections - -Before making a connection, we need to verify that our Cassandra instance is correctly configured. - -Log in to your [OVHcloud Control Panel](/links/manager) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your Cassandra instance. - -#### Step 1: Verify your user roles and password - -Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user. - -> [!warning] -> Be careful! By doing so you will need to update all the places where you already use this user/password pair. -> - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -You can add more users by clicking on the button `Add user`{.action}. - -![Add user](images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png){.thumbnail} - -Enter a username then click `Create User`{.action}. - -> [!primary] -> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table. - -#### Step 2: Authorise incoming connections from the Cassandra client - -> [!warning] -> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database. - -In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database. - -Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database. - -![Add an IP](images/ip_authorize.png){.thumbnail} - -You can edit and retract database access via the `...`{.action} button in the IP table. - -> [!primary] -> -> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully. -> - -#### Collect required information - -Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section. - -![Login information tab](images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png){.thumbnail} - -Select the `Users`{.action} tab to get the username. - -![User table](images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png){.thumbnail} - -## Go further - -Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra) to find how to connect to your database with several languages. - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png deleted file mode 100644 index be919f6a4f4..00000000000 Binary files a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530081746230.png and /dev/null differ diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png deleted file mode 100644 index f3e4b2204b2..00000000000 Binary files a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530081855845.png and /dev/null differ diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png deleted file mode 100644 index 17bbc84e1f5..00000000000 Binary files a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/cassandra_02_prepare_for_incoming_connections-20220530082044838.png and /dev/null differ diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/ip_authorize.png b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/ip_authorize.png deleted file mode 100644 index 9429239b425..00000000000 Binary files a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/images/ip_authorize.png and /dev/null differ diff --git a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/meta.yaml b/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/meta.yaml deleted file mode 100755 index 61c4739be5f..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections/meta.yaml +++ /dev/null @@ -1,5 +0,0 @@ -id: f2f2c9b6-a0da-4afa-abed-6078c03c9b69 -full_slug: public-cloud-databases-cassandra-configure-instance -engine: cassandra -section: settings -reference_category: public-cloud-databases-cassandra-guides \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.de-de.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.de-de.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.de-de.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-asia.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-asia.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-au.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-au.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-au.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-ca.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-ca.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-gb.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-gb.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-ie.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-ie.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-sg.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-sg.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-us.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-us.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.en-us.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.es-es.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.es-es.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.es-es.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.es-us.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.es-us.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.es-us.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.fr-ca.md deleted file mode 100644 index 058e37fff2b..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.fr-ca.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Références des paramètres avancés (EN) -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.fr-fr.md deleted file mode 100644 index 058e37fff2b..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.fr-fr.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Références des paramètres avancés (EN) -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.it-it.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.it-it.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.it-it.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.pl-pl.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.pl-pl.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.pt-pt.md deleted file mode 100644 index 97864050877..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/guide.pt-pt.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: Cassandra - Advanced parameters references -excerpt: This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases -updated: 2025-07-07 ---- - - - -> [!warning] -> -> **Important Notice – End of Sale (EOS)** -> -> Sale of our Cassandra managed database service will end on 15 September 2025. -> -> Existing services will continue to operate until the End Of Life (EOL) on 15 December 2025. -> - -## Objective - -This guide lists all the supported advanced parameters that allow you to configure your Public Cloud Databases for Cassandra according to your use cases. - -## Requirements - -- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account -- A database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement) -- Access to your [OVHcloud Control Panel](/links/manager) or to the [OVHcloud API](https://api.ovh.com/console/) - -## Instructions - -> [!warning] -> -> The management of advanced parameters is not supported via Terraform. -> - -### Using the OVHcloud Control Panel - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-the-ovhcloud-control-panel) to find out how to change your advanced parameters from the OVHcloud Control Panel. - -### Using API - -Please refer to this [guide](/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration#using-api) to find out how to change your advanced parameters from the OVHcloud API. - -### Advanced parameters for Cassandra - -Below you can find a summary of every configuration option available for Cassandra service: - -| | | -|---|---| -| Parameter | `cassandra.batch_size_fail_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Fail any multiple-partition batch exceeding this value. 50kb (10x warn threshold) by default. | - -| | | -|---|---| -| Parameter | `cassandra.batch_size_warn_threshold_in_kb` | -| Value type | long | -| Minimum | 1 | -| Maximum | 1000000 | -| Description | Log a warning message on any multiple-partition batch size exceeding this value. 5kb per batch by default. Caution should be taken on increasing the size of this threshold as it can lead to node instability. | - -| | | -|---|---| -| Parameter | `cassandra.datacenter` | -| Value type | string | -| Minimum | | -| Maximum | | -| Description | Name of the datacenter to which nodes of this service belong. Can be set only when creating the service. | - -## Go further - -Visit our dedicated Discord channel: . Ask questions, provide feedback and interact directly with the team that builds our databases services. - -If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. - -Join our community of users on . diff --git a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/meta.yaml b/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/meta.yaml deleted file mode 100644 index 3ed3aeea491..00000000000 --- a/pages/public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references/meta.yaml +++ /dev/null @@ -1,5 +0,0 @@ -id: 4daeb713-6395-4d46-b37c-cb33ba287257 -full_slug: public-cloud-databases-cassandra-advanced-parameters-references -engine: cassandra -section: settings -reference_category: public-cloud-databases-cassandra-guides \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml index 90ddf2f57fb..b101ace107e 100755 --- a/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml @@ -2,4 +2,4 @@ id: c8c6cbfb-1855-4efb-8ff6-b865a4959ac0 full_slug: public-cloud-databases-getting-started engine: all section: onboarding -reference_category: public-cloud-databases-common-getting-started \ No newline at end of file +reference_category: public-cloud-databases-common-getting-started diff --git a/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml index 66ee7533914..a712296525f 100755 --- a/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml @@ -1,3 +1,3 @@ id: 0aec99c6-5879-48f9-8280-cd1e76a37838 full_slug: public-cloud-databases-order-api -reference_category: public-cloud-databases-common-getting-started \ No newline at end of file +reference_category: public-cloud-databases-common-getting-started diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.de-de.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-asia.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-au.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ca.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-gb.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-ie.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-sg.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.en-us.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-es.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.es-us.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md index 9bad99aac77..b98e1344a14 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-ca.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md index 9bad99aac77..b98e1344a14 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.fr-fr.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.it-it.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pl-pl.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md index 008c2636028..06e2ddbf08d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/guide.pt-pt.md @@ -12,7 +12,6 @@ Public cloud database engines are managed services, which means that they are no > > Advanced configuration is available for the following Public Cloud Databases engines : > -> - Cassandra > - MySQL > - PostgreSQL > - Valkey @@ -85,11 +84,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > MySQL >> > [!api] >> > @@ -115,11 +109,6 @@ From the resulting list, select and copy the cluster ID, also known as clusterId Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -143,11 +132,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/advancedConfiguration ->> > > MySQL >> > [!api] >> > @@ -171,11 +155,6 @@ Open the following API call and paste the corresponding inputs (serviceName, clu Open the following API call and paste the corresponding inputs (serviceName, clusterId) > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud PUT /cloud/project/{serviceName}/database/cassandra/{clusterId}/advancedConfiguration ->> > > MySQL >> > [!api] >> > diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml index 204bf9e5b84..8cc3ec94369 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml @@ -2,4 +2,4 @@ id: dbbac3da-b325-431e-bae8-857eb6f41e13 full_slug: public-cloud-databases-advanced-configuration engine: all section: settings -reference_category: public-cloud-databases-common-configuration \ No newline at end of file +reference_category: public-cloud-databases-common-configuration diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md index a0a32b764de..efbebb0bc7a 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md index a0a32b764de..efbebb0bc7a 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md index 36a7ae6f04a..e41936fdb22 100644 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md @@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes Valkey | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes -Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes ## Off-site backup diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md index b948dd047c3..7ff79593f6b 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md index b948dd047c3..7ff79593f6b 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md index 3b959f3e1a9..47df0a2f1b3 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md @@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs The Cross Service Integrations for Logs and Metrics allow you for example: -- To send Valkey or MySQL metrics or Cassandra metrics in PostgreSQL. +- To send Valkey or MySQL metrics in PostgreSQL. - To send PostgreSQL or MySQL metrics to OpenSearch. - To show metrics in Dashboards service. @@ -150,11 +150,6 @@ From the resulting list, select and copy the service identifier corresponding to Open the following API call, paste your service ID into the `serviceName` input field and click `Execute`{.action}: > [!tabs] -> Cassandra ->> > [!api] ->> > ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra ->> > > Dashboards >> > [!api] >> > @@ -203,10 +198,6 @@ Open the following API call, paste your service ID into the `serviceName` input Get integration capabilities related to your Public Cloud Databases service: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/cassandra/{clusterId}/capabilities/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/grafana/{clusterId}/capabilities/integration @@ -249,10 +240,6 @@ As a first step, you need to push your metrics or logs somewhere, in order to st For that, you need to create a new integration: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration @@ -305,10 +292,6 @@ Once done, get the `GrafanaDashboard` integration capability related to the dest Then create a second integration from your *Destination* service name: > [!tabs] -> Cassandra ->> > [!api] ->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/cassandra/{clusterId}/integration ->> > > Dashboards >> > [!api] >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/grafana/{clusterId}/integration diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.de-de.md index 2b50ae9ff88..8e6f9ff2bf9 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.de-de.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-asia.md index 0917516dbc3..f076c15ffd7 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-asia.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-au.md index 0917516dbc3..f076c15ffd7 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-au.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ca.md index 0917516dbc3..f076c15ffd7 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ca.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-gb.md index 294b82e63a3..7090a77a9ce 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-gb.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ie.md index 294b82e63a3..7090a77a9ce 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-ie.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-sg.md index 0917516dbc3..f076c15ffd7 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-sg.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-us.md index 0917516dbc3..f076c15ffd7 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.en-us.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-es.md index 2b50ae9ff88..8e6f9ff2bf9 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-es.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-us.md index 2c1c75e5de1..ea45cb83b77 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.es-us.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-ca.md index aa17228133e..73bf3313c92 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-ca.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-fr.md index d4da47945d1..630962f0f32 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.fr-fr.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.it-it.md index 2b50ae9ff88..8e6f9ff2bf9 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.it-it.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pl-pl.md index 2b50ae9ff88..8e6f9ff2bf9 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pl-pl.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pt-pt.md index 2b50ae9ff88..8e6f9ff2bf9 100644 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/guide.pt-pt.md @@ -244,8 +244,6 @@ In this guide, we explained how to deploy a MongoDB service but you can find exa >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/mysql/terraform/hello-world) > PostgreSQL >> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/postgresql/terraform/hello-world) -> Cassandra ->> [https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/cassandra/terraform/hello-world) ## Go further diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md index 1ac83bdd3fe..c970a36047f 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md index 30286ed89d9..f108c8b2765 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md index c72633a8d2b..051c2ba49f2 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md index 9753e6a0bf9..8cc99e45501 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md index 2c5f4bfd3e9..394df26bf46 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md @@ -34,7 +34,6 @@ When the disk usage increases even more and reaches a critical level (depending Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions: - `Valkey` does not store any user data on disk. Thus, it will not fill up the underlying disk storage. -- `Cassandra` turns to read-only. - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write. - `MongoDB` forbids writes but allows deletes only for the Admin users. diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.de-de.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-asia.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-au.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ca.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-gb.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-ie.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-sg.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.en-us.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-es.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.es-us.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-ca.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.fr-fr.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.it-it.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pl-pl.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md index 86e0c5e035e..9308f284ba0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/guide.pt-pt.md @@ -87,7 +87,6 @@ scrape_configs: Public Cloud Databases offer service metrics via Prometheus for the following engines: - Valkey -- Cassandra - MongoDB - MySQL - PostgreSQL diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.de-de.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md index 2e1aebbd104..0985d1f024f 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-asia.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md index 2e1aebbd104..0985d1f024f 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-au.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md index 2e1aebbd104..0985d1f024f 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ca.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-gb.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-ie.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md index 2e1aebbd104..0985d1f024f 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-sg.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md index 2e1aebbd104..0985d1f024f 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.en-us.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-es.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md index 2e1aebbd104..0985d1f024f 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.es-us.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md index 6ba226f37cf..ee78c89827b 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-ca.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md index afde950455f..af694456828 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.fr-fr.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.it-it.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pl-pl.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md index 2721957139e..e203f8b5c87 100644 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/guide.pt-pt.md @@ -60,7 +60,7 @@ If you need to restore your data using a backup, you can follow [this guide](/pa | **Source** | **Content** | **Documentation** | | --- | --- | --- | | Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | -| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Kafka service as an example `/cloud/project/{serviceName}/database/kafka/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | ## 6.API diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md index a96fad47dee..093cd849957 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md index 5d001be51df..96586a06908 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md index a96fad47dee..093cd849957 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md index a96fad47dee..093cd849957 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md index 45081f89ada..011dcfef9dc 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md index 45081f89ada..011dcfef9dc 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md index a96fad47dee..093cd849957 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md index a96fad47dee..093cd849957 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md index a96fad47dee..093cd849957 100644 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md @@ -35,22 +35,17 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_ Valkey is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.
See our [Valkey Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide. -### Cassandra - -Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.
-See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities) guide. - ## Feature Availability -| Feature | MySQL | PostgreSQL | MongoDB | Valkey | Cassandra | -|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------| -| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | ✓ | -| Read-only nodes | ✓ | ✓ | ✓ | | | -| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | | -| Database forking | ✓ | ✓ | ✓ | ✓ | ✓ | -| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | ✓ | -| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | ✓ | +| Feature | MySQL | PostgreSQL | MongoDB | Valkey | +|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------| +| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview)) | ✓ | ✓ | ✓ | ✓ | +| Automatic updates and one click upgrade | ✓ | ✓ | ✓ | ✓ | +| Read-only nodes | ✓ | ✓ | ✓ | | +| Point in Time Recovery | ✓ | ✓ | ✓ (1) | | +| Database forking | ✓ | ✓ | ✓ | ✓ | +| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓ | ✓ | ✓ | ✓ | +| Private network connectivity (vRack) | ✓ | ✓ | ✓ | ✓ | (1) depends on the plan