ovh · Y0Coss · Jun 20, 2025 · Jun 16, 2025 · Jun 16, 2025 · Jun 16, 2025
diff --git a/links/public-cloud/dashboards b/links/public-cloud/dashboards
@@ -0,0 +1,16 @@
+- [de-de](https://www.ovhcloud.com/de/public-cloud/grafana/)
+- [en-asia](https://www.ovhcloud.com/asia/public-cloud/grafana/)
+- [en-au](https://www.ovhcloud.com/en-au/public-cloud/grafana/)
+- [en-ca](https://www.ovhcloud.com/en-ca/public-cloud/grafana/)
+- [en-gb](https://www.ovhcloud.com/en-gb/public-cloud/grafana/)
+- [en-ie](https://www.ovhcloud.com/en-ie/public-cloud/grafana/)
+- [en-in](https://www.ovhcloud.com/en-in/public-cloud/grafana/)
+- [en-sg](https://www.ovhcloud.com/en-sg/public-cloud/grafana/)
+- [en-us](https://www.ovhcloud.com/en/public-cloud/grafana/)
+- [es-es](https://www.ovhcloud.com/es-es/public-cloud/grafana/)
+- [es-us](https://www.ovhcloud.com/es/public-cloud/grafana/)
+- [fr-ca](https://www.ovhcloud.com/fr-ca/public-cloud/grafana/)
+- [fr-fr](https://www.ovhcloud.com/fr/public-cloud/grafana/)
+- [it-it](https://www.ovhcloud.com/it/public-cloud/grafana/)
+- [pl-pl](https://www.ovhcloud.com/pl/public-cloud/grafana/)
+- [pt-pt](https://www.ovhcloud.com/pt/public-cloud/grafana/)
diff --git a/...ccount_and_service_management/reversibility/14-reversibility-mdb/guide.en-gb.md b/...ccount_and_service_management/reversibility/14-reversibility-mdb/guide.en-gb.md
@@ -0,0 +1,62 @@
+---
+title: "Reversibility Policy for the Managed Message Broker product"
+updated: 2025-06-19
+---
+
+## Objective
+
+This document describes the reversibility policy of the Managed Message Broker product covering the OVHcloud Managed Kafka offer.
+
+This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.
+
+## List of features
+
+The features of the Managed Document Database product line fall into three categories:
+
+1. **Core features** for which we guarantee migration capacity.
+1. **OVHcloud implementations** that require adaptation to a new migration environment.
+1. **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
+
+### 1 - Core features
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| High-availability message streaming | Reliable and distributed transmission of real-time data. | Avro, JSON, Protocol, Text | **Incoming**: Loading via Kafka producers . <br> **Outgoing**: Export via Kafka consumers or replay tools. | [Kafka - Capabilities and limitations](/pages/public_cloud/public_cloud_databases/kafka_01_capabilities)|
+| Open-source Kafka compatibility | Use the standard Apache Kafka engine without modification. | Native Kafka (standard API) | **Incoming**: Direct integration with existing Kafka tools.<br> **Outgoing**: Standard Kafka export|[Kafka getting started documentation](https://kafka.apache.org/documentation/){.external} |
+| Partitioning and replication | Manage partitions and replicas for fault tolerance | N/A | **Incoming**: Configure partitions/replicas on import. <br> **Outbound**: Export and deploy to another cluster. | [Kafka - Capabilities and limitations](/pages/public_cloud/public_cloud_databases/kafka_01_capabilities) |
+| Configuring data retention | Custom message retention duration setting | NA | **Incoming**: Adjusting parameters. <br> **Outgoing**: Migration limited to messages that are still stored. | [Kafka - Advanced settings references](/pages/public_cloud/public_cloud_databases/kafka_03_advanced_parameters_references)|
+| Data Schema Registry | Central repository for storing data schemas | Karapace Native Format | **Inbound**: NA.<br> **Outbound**: NA. | [Schema registry](/pages/public_cloud/public_cloud_databases/kafka_01_capabilities)|
+
+### 2 - OVHcloud implementations
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| OVHcloud Dashboard | Manage topics, ACLs and monitor via web interface. | N/A | **Incoming**: Initial configuration via API and web interface.<br> **Outbound**: Administration interrupted after termination. Reproduce configurations manually in target environment | [Dashboards - Capabilities and limitations](/pages/public_cloud/public_cloud_databases/grafana_01_capabilities)<br> [Dashboards - Advanced settings references](/pages/public_cloud/public_cloud_databases/grafana_03_advanced_parameters_references)|
+| Integrated monitoring | Performance dashboards integrated into the OVHcloud interface. | N/A | **Inbound**: Metrics Configuration.<br> **Outbound**: Configuration to recreate in the target environment. | [Analytics - Kafka](/products/public-cloud-data-analytics-kafka) |
+| Network Security (ACL) | IP filtering and SSL/SASL authentication. | IP, SASL/SSL | **Incoming**: Rule configuration. <br> **Outbound**: Export ACLs to replicate. | [Kafka - Getting started](/pages/public_cloud/public_cloud_databases/kafka_02_getting_started)|
+
+### 3 - Specific features
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| OVHcloud private network (vRack) | Connect to other OVHcloud services via a private network. | N/A | **Incoming**: vRack configuration. <br> **Outgoing**: Non-transferable feature. | [vRack](/pages/public_cloud/public_cloud_databases/databases_08_vrack) |
+| Anti-DDoS | Anti-DDoS is a set of tools and mechanisms designed to absorb denial of service attacks. It includes traffic analysis, "clean-up" via a specialized network, and mitigation using VAC technology developed by OVHcloud. | N/A | **Incoming**: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required.<br> **Outgoing**: Order and configure an anti-DDoS solution from the new provider. | [OVHcloud DDoS Protection](/links/security/antiddos) |
+
+## List of architectures
+
+The Managed Kafka service is based on a distributed architecture with Kafka brokers distributed across several availability zones. High availability is ensured via partition replication, with integrated monitoring for message flow stability. Two architecture plans are offered: a Business plan based on three nodes and an Enterprise plan based on six nodes.
+
+## Partner Services
+
+The OVHcloud partners concerned are listed in the [OVHcloud partners directory ](/links/partner) under the "**cloud migration**" keywords.
+
+OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services).
+
+## Costs and fees
+
+The features described in the tables are available at no cost, unless otherwise specified, and are freely usable by the customer.
+The service is billed according to the resources used: the selected instance and the storage. No cancellation fee will be applied, but you will need to export the data before cancelling/decommissioning the service.
+
+## Data retention after termination of contract
+
+After the service has been cancelled, all Kafka messages and configurations are permanently deleted. The customer must perform a full export before termination, as OVHcloud does not store any data.
diff --git a/...ccount_and_service_management/reversibility/14-reversibility-mdb/guide.fr-fr.md b/...ccount_and_service_management/reversibility/14-reversibility-mdb/guide.fr-fr.md
@@ -0,0 +1,62 @@
+---
+title: "Politique de réversibilité du produit Managed Message Broker"
+updated: 2025-06-19
+---
+
+## Objectif
+
+Ce document décrit la politique de réversibilité de la gamme de produits Managed Message Broker couvrant l'offre OVHcloud Managed Kafka.
+
+Cette politique vise à mettre en œuvre les principes généraux de réversibilité et notre conformité avec le Code de conduite SWIPO IaaS pour les fournisseurs de cloud.
+
+## Liste des fonctionnalités
+
+Les fonctionnalités de la gamme de produits Managed Document Database sont réparties en trois catégories :
+
+1. Les **Ffonctionnalités principales** pour lesquelles nous garantissons la capacité de migration.
+1. Les **implémentations OVHcloud** qui nécessitent une adaptation à un nouvel environnement de migration.
+1. Les **fonctionnalités spécifiques** qui ne peuvent pas être garanties pour la migration car elles sont liées à l'environnement OVHcloud ou impliquent des développements personnalisés.
+
+### 1 - Fonctionnalités principales
+
+| **Fonction** | **Description** | **Formats disponibles** | **Modèle de migration** | **Documentation disponible** |
+| --- | --- | --- | --- | --- |
+| Streaming de messages à haute disponibilité | Transmission fiable et distribuée de données en temps réel. | Avro, JSON, Protobuf, Texte | **Entrant** : chargement via producteurs Kafka. <br> **Sortant** : export via consommateurs Kafka ou outils de replay. | [Kafka - Capacités et limitations](/pages/public_cloud/public_cloud_databases/kafka_01_capabilities)|
+| Compatibilité Kafka open-source | Utilisation du moteur Apache Kafka standard sans modification. | Natif Kafka (API standard) | **Entrant** : intégration directe avec outils Kafka existants. <br> **Sortant** : export standard Kafka|[Kafka documentation - Getting started](https://kafka.apache.org/documentation/){.external} |
+| Partitionnement et réplication | Gestion des partitions et répliques pour la tolérance aux pannes | N/A | **Entrant** : configurer les partitions/réplicas à l'import.<br> **Sortant** : Export et déploiement sur un autre cluster. | [Kafka - Capacités et limitations](/pages/public_cloud/public_cloud_databases/kafka_01_capabilities) |
+| Configuration de la rétention des données | Définition personnalisée de la durée de rétention des messages | NA | **Entrant** : ajustement des paramètres.<br> **Sortant** : migration limitée aux messages encore stockés. | [Kafka - Références des paramètres avancés](/pages/public_cloud/public_cloud_databases/kafka_03_advanced_parameters_references)|
+| Registre des schémas de données | Dépôt central pour stocker les schémas de données | Format natif Karapace | **Entrant** : NA. <br> **Sortant** : NA. | [Schema registry](/pages/public_cloud/public_cloud_databases/kafka_01_capabilities)|
+
+### 2 - Implémentations OVHcloud
+
+| **Fonction** | **Description** | **Formats disponibles** | **Modèle de migration** | **Documentation disponible** |
+| --- | --- | --- | --- | --- |
+| OVHcloud Dashboard | Gestion des topics, ACL et monitoring via interface web. | N/A | **Entrant** : configuration initiale via API et l'interface web. <br> **Sortant** : administration interrompue après résiliation. Reproduire les configurations manuellement dans l’environnement cible | [Dashboards - Capacités et limitations](/pages/public_cloud/public_cloud_databases/grafana_01_capabilities) <br> [Dashboards - Références des paramètres avancés ](/pages/public_cloud/public_cloud_databases/grafana_03_advanced_parameters_references)|
+| Monitoring intégré | Tableaux de bord de performances intégrés à l’interface OVHcloud. | N/A | **Entrant** : configuration des métriques <br> **Sortant** : : configuration à recréer dans l’environnement cible | [Analytics - Kafka](/products/public-cloud-data-analytics-kafka)|
+| Sécurité réseau (ACL) | Filtrage IP et authentification SASL/SSL. | IP, SASL/SSL | **Entrant** : configuration des règles. <br> **Sortant** : export des ACL à répliquer. | [Kafka-Premiers pas](/pages/public_cloud/public_cloud_databases/kafka_02_getting_started)|
+
+### 3 - Fonctionnalités spécifiques
+
+| **Fonction** | **Description** | **Formats disponibles** | **Modèle de migration** | **Documentation disponible** |
+| --- | --- | --- | --- | --- |
+| Réseau privé OVHcloud (vRack) | Connexion avec d’autres services OVHcloud en réseau privé. | N/A | **Entrant** : Configuration du vRack. <br> **Sortant** : Fonctionnalité non transférable. | [vRack](/pages/public_cloud/public_cloud_databases/databases_08_vrack) |
+| Anti-DDoS | L’anti-DDoS est un ensemble d’outils et de mécanismes conçus pour absorber les attaques par déni de service. Il comprend l'analyse du trafic, le « nettoyage » via un réseau spécialisé et la mitigation grâce à la technologie VAC développée par OVHcloud. | N/A | **Entrante** : le système anti-DDoS fait partie de notre infrastructure et est activé par défaut. Aucune action n'est requise. <br> **Sortante** : commandez et configurez un anti-DDoS chez le nouveau fournisseur. | [OVHcloud DDoS Protection](/links/security/antiddos) |
+
+## Liste des architectures
+
+Le service Managed Kafka repose sur une architecture distribuée avec des brokers Kafka répartis entre plusieurs zones de disponibilité. La haute disponibilité est assurée via la réplication des partitions, avec un monitoring intégré pour la stabilité des flux de messages. Deux plans d’architecture sont proposés : un plan Business reposant sur trois nœuds et un plan Enterprise reposant sur six nœuds.
+
+## Services partenaires
+
+Les partenaires OVHcloud concernés figurent dans l'annuaire des [partenaires OVHcloud](/links/partner) sous les mots-clés « **migration vers le cloud** ».
+
+OVHcloud dispose également d’un service dédié : [OVHcloud Professional Services](/links/professional-services).
+
+## Coûts et frais
+
+Les fonctionnalités décrites dans les tableaux sont disponibles sans coûts ni frais, sauf mentions contraires, et sont librement utilisables par le client.
+Le service est facturé selon les ressources utilisées : l’instance sélectionnée et le stockage. Aucun frais de résiliation n’est appliqué, mais il est impératif d’exporter les données avant résiliation/décommissionnement du service.
+
+## Conservation des données après résiliation du contrat
+
+Après résiliation du service, tous les messages et configurations Kafka sont supprimés de manière définitive. Le client doit effectuer une exportation complète avant résiliation, OVHcloud ne conservant aucune donnée.
diff --git a/pages/account_and_service_management/reversibility/14-reversibility-mdb/meta.yaml b/pages/account_and_service_management/reversibility/14-reversibility-mdb/meta.yaml
@@ -0,0 +1,3 @@
+id: f243c4d1-87d5-4971-9cdf-5b4d1f41a0ac
+full_slug: reversibility-public-cloud-databases-message-broker
+reference_category: account-and-service-management-reversibility-reversibility-policies
diff --git a/...management/reversibility/15-reversibility-obs-data-visualization/guide.en-gb.md b/...management/reversibility/15-reversibility-obs-data-visualization/guide.en-gb.md
@@ -0,0 +1,70 @@
+---
+title: "Reversibility Policy for the Managed Data Visualization product"
+updated: 2025-06-19
+---
+
+## Objective
+
+This document describes the reversibility policy for the Managed Data Visualization product covering the OVHcloud Managed Grafana offer.
+
+This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.
+
+## List of features
+
+The features of the product line fall into three categories:
+
+1. **Core features** for which we guarantee migration capacity.
+1. **OVHcloud implementations** that require adaptation to a new migration environment.
+1. **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
+
+### 1 - Core features
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Platform As A Service | Platform for implementing dynamic dashboards and graphics. | JSON, YAML | **Incoming**: Direct connection via API to import dashboards/configurations. <br> **Outbound**: Export resources via REST API to any compatible Grafana environment. | [Offer presentation](/links/public-cloud/dashboards) |
+| Standard plugins | Open-source plugins (Prometheus, Loki, etc.) that can be activated. | Official Grafana plugins | **Incoming**: Enable plugins compatible with the target version. <br> **Outgoing**: Reusable plugins if supported by the new environment. |[Grafana Plugins](https://grafana.com/grafana/plugins/all-plugins/){.external}|
+| Dhasboards and alerts | Manual creation of dashboards and alert rules via the Grafana interface | JSON | **Inbound**: Import JSON files via API or interface. <br> **Outgoing**: Export dashboards/alerts to JSON for migration. | [Dashboards - Capabilities and limitations](/pages/public_cloud/public_cloud_databases/grafana_01_capabilities) |
+| Manual backups | Manual backup generation via external tools (e.g. grr) | JSON, SQLite | **Incoming**: Restoring from a JSON or SQLite file. <br> **Outgoing**: Manually exporting data for migration outside of an OVHcloud hosting environment. | [Grafana documentation](/products/public-cloud-data-analytics-grafana) |
+
+### 2 - OVHcloud implementations
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| OVHcloud private network (vRack) | The vRack, or virtual rack, is a private VLAN technology that enables the connection between OVHcloud services | N/A | **Inbound**: Network Connection Configuration <br> **Outbound**: Note the network architecture and reproduce it with VLANs | [vRack](/pages/public_cloud/public_cloud_databases/databases_08_vrack) |
+| Logs traceability | Log storage in OVHcloud Managed OpenSearch | JSON (OpenSearch) | **Incoming**: NA <br> **Outgoing**: Manually export logs via OpenSearch API, then re-index into the target environment. | [Using Grafana with Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/visualization_grafana)|
+| Automatic backups | Backups managed by OVHcloud, that cannot be exported directly outside the ecosystem. | Internal snapshots | **Incoming**: Not applicable for direct import. <br> **Outgoing**: Requires a restore on an OVHcloud instance, then manual export (SQL dump) to migrate to another environment. | [Public Cloud Databases - Automatic backups](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) |
+
+
+### 3 - Specific features
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Infrastructure As a Code | Automated deployment via Terraform modules specific to OVHcloud | N/A | **Incoming**: Scripts to be adapted for other providers.<br> **Outbound**: Terraform configurations need to be rewritten. | [Terraform](https://registry.terraform.io/providers/ovh/ovh/latest/docs) |
+| Anti-DDoS | Anti-DDoS is a set of tools and mechanisms designed to absorb denial of service attacks. It includes traffic analysis, "clean-up" via a specialized network, and mitigation using VAC technology developed by OVHcloud. | N/A | **Incoming**: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required. <br> **Outgoing**: Order and configure an anti-DDoS solution from the new provider. | [OVHcloud DDoS Protection](/links/security/antiddos) |
+
+## List of architectures
+
+Managed Grafana service offer is deployed in single-node mode (essential plan). Integration with other OVHcloud services (OpenSearch, databases) is native via vRack.Architectures include:
+
+- Vertical scalability: Increase resources (CPU/RAM) via the OVHcloud interface.
+- Cross-service integration: Centralize logs and metrics in managed OpenSearch.
+
+## Partner Services
+
+The OVHcloud partners concerned are listed in the [OVHcloud partners directory](/links/partner) under the "**cloud migration**" keywords.
+
+OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services).
+
+## Costs and fees
+
+No termination fee: No extra billing linked to the default data migration. Billing stops as soon as the service is terminated.
+Features described in the tables are available at no cost, unless otherwise specified, and are freely usable by the customer.
+
+## Retention of data after termination of contract
+
+> [!warning]
+>
+> OVHcloud does not guarantee the use and availability of backups to restore customer data after termination of the service.
+
+OVHcloud does not store any data after deleting a Managed Data Visualization cluster.
+Automatic and manual snapshots are irreversibly deleted. A manual export is required to preserve the data.