Merge pull request #8109 from ovh/hb-reversibilite-politique

HB POL de reversbilibilité LDP + data platform

Author: Y0Coss

pages/account_and_service_management/reversibility/18-logs-data-platform-reversibility/guide.en-gb.md

@@ -0,0 +1,74 @@
+---
+title: "Reversibility Policy for the Managed Log Manager product"
+updated: 2025-07-08
+---
+
+**Objective**
+
+This document describes the reversibility policy for the Managed Log Manager product covering the OVHcloud Logs Data Platform 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**
+
+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.
+
+**Core features**
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Logs ingestion | Support of several logs' files format  | GELF, LTSV, RFC 5424, Beats, Cap'n Proto, etc | **Incoming**: direct send via shared entry point | [Mutualized inputs](/pages/manage_and_operate/observability/logs_data_platform/ingestion_mutualized_inputs)|
+| Non-standard logs ingestion | LDP also supports non-traditional formats | All formats offered by Logstash | **Incoming**: direct send via dedicated entry point | [Dedicated input-logstash](/pages/manage_and_operate/observability/logs_data_platform/ingestion_logstash_dedicated_input) |
+| Support of OpenSearch APIs | Import or Export logs through OpenSearch API  | JSON | **Incoming**: Special Index to ingest logs. <br>**Outgoing**: OpenSearch Scroll queries with pagination |[Mutualized input - OpenSearch API](/pages/manage_and_operate/observability/logs_data_platform/ingestion_opensearch_api_mutualized_input) <br> [Exposing your logs to third-party tools via the OpenSearch API](/pages/manage_and_operate/observability/logs_data_platform/integration_opensearch_api) |
+| OpenSearch Dashboards | Visualization and exploration via OpenSearch Dashboards | JSON | **Incoming**/**Outgoing**: Visualizations, Dashboards and settings via both API and User Interface | [Using OpenSearch Dashboards with Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/visualization_opensearch_dashboards) |
+| Cold Storage and Archives | Daily encrypted archives, long-term storage available 48h after logs reception | File containing GELF delivered as archive | **Incoming**: activation of the option and configuration of the stream. <br>**Outgoing**: download via Control Panel or OVHcloud API. | [Archiving your logs-cold storage](/pages/manage_and_operate/observability/logs_data_platform/archive_cold_storage) |
+
+**OVHcloud Implementation**
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Control Panel platform | User Interface in the Control Panel to create streams, dashboard, alias, index, OpenSearch dashboards or Logstash Inputs | N/A | **Incoming**: data and configurations related to the lifecycle of the service. <br> **Outgoing**: recreate configurations on another logs manager service. | [OVHcloud API](https://api.ovh.com/console/?section=%2Fdbaas%2Flogs&branch=v1) |
+| OpenSearch Index As a Service | Import or Export documents through OpenSearch API  | JSON | **Incoming**: specific names' conventions for indexes and aliases, index settings  and API restrictions. <br>**Outgoing**: OpenSearch Scroll queries with pagination | [OpenSearch Index as a Service](/pages/manage_and_operate/observability/logs_data_platform/opensearch_index) |
+| Graylog Dashboards | Configuration of dashboards and searches saved by the client on the graylog interface | JSON | **Incoming**: use of Graylog APIs or Graylog User Interface. <br>**Outgoing**: Use of Graylog APIs. | [Greylog documentation](https://go2docs.graylog.org/4-0/home.htm) |
+| Archives encryption | Systematic encryption of archives using public PGP keys provided by the client | PGP Keys | **Incoming**: PGP key registration via API or User Interface on the Control Panel. <br>**Outgoing**: Retrieving the saved keys and setting up an encryption mechanism in the target environment | [Encrypting your logs Archives](/pages/manage_and_operate/observability/logs_data_platform/archive_cold_storage_encryption) |
+
+**Specific features**
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Anti-DDoS protection| 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 | [Anti-DDoS OVHcloud](/links/security/ddos) |
+
+**List of architectures**
+
+The components of the product are accessible from the OVHcloud interface and allow to operate streams, dashboards, dedicated inputs, indexes, aliases and OpenSearch Dashboards instances.
+
+The product is divided into two service offers:
+
+- A shared infrastructure: "logs-account"
+- A dedicated cluster: "logs-enterprise"
+
+**Partner services**
+
+The OVHcloud partners concerned are listed in the [OVHcloud partners directory](/links/partner) under the "**Data center expansion and Migration**" keywords.
+
+OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services).
+
+**Cost and fees**
+
+Features described in tables are available at no cost, unless otherwise specified, and are freely usable by the customer. Visit the [Logs Data Platform product page](/links/manage-operate/ldp) to see the price list.
+
+- No additional exit fees applied.
+- Billing depends on the volume stored and the type of infrastructure mobilized (indexed/archived).
+- Any assistance or turnkey export service may incur additional costs.
+
+**Data retention after termination of the contract**
+
+OVHcloud does not guarantee the use and availability of backups to restore client's data after service termination.
+
+- Streams and OpenSearch indexes are deleted immediately once the service is removed.
+- The cold storage archives are immediately destroyed upon termination of the service
+- The client is fully responsible for data export via API or [ldp-archive-mirror](https://github.com/ovh/ldp-archive-mirror) before decommissioning the service or contract termination.

pages/account_and_service_management/reversibility/18-logs-data-platform-reversibility/guide.fr-fr.md

@@ -0,0 +1,74 @@
+---
+title: "Politique de réversibilité du produit Managed Log Manager"
+updated: 2025-07-08
+---
+
+## Objectif
+
+Ce document est la politique de réversibilité du produit Managed Log Manager couvrant l’offre commerciale Logs Data Platform d’OVHcloud.
+
+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 du produit sont réparties en trois catégories :
+
+1. Les **fonctionnalités principales** pour lesquelles nous garantissons la capacité de migration.
+1. Les **implémentation 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** |
+| --- | --- | --- | --- | --- |
+| Ingestion de logs standards | Support de plusieurs formats de fichiers de logs | GELF, LTSV, RFC 5424, Beats, Cap’n Proto, etc | **Entrant** : envoi direct via point d’entrée mutualisé. | [Mutualized inputs](/pages/manage_and_operate/observability/logs_data_platform/ingestion_mutualized_inputs) |
+| Ingestion de logs non standards | Support de formats de fichiers de logs non traditionnels | Tout format proposé par le logiciel Logstash | **Entrant** : envoi direct via un point d'entréee dédié | [Dedicated input-logstash](/pages/manage_and_operate/observability/logs_data_platform/ingestion_logstash_dedicated_input) |
+| Support de l'API OpenSearch | Import ou export des logs via OpenSearch  | JSON | **Entrant** : Indexation spéciale pour ingérer les logs. <br> **Sortant** : pagination Scroll ; ingestion externe possible | [Mutualized input - OpenSearch API](/pages/manage_and_operate/observability/logs_data_platform/ingestion_opensearch_api_mutualized_input) <br> [Exposing your logs to third-party tools via the OpenSearch API](/pages/manage_and_operate/observability/logs_data_platform/integration_opensearch_api) |
+| Tableaux de bords OpenSearch | Visualisation et exploration via OpenSearch Dashboards| JSON | **Entrant/Sortant** : Visualisations, tableaux de bord et paramètres via API et interface utilisateur. | [Using OpenSearch Dashboards with Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/visualization_opensearch_dashboards) |
+| Stockage et archivage à froid | Archivage quotidien chiffrable, conservation longue durée disponible 48h après réception des logs | Fichier contenant du GELF livré sous forme d’archive | **Entrant** : activation de l’option et configuration du stream.  <br> **Sortant** : téléchargement via l'espace client ou l'API OVHcloud. | [Archiving your logs-cold storage](/pages/manage_and_operate/observability/logs_data_platform/archive_cold_storage) |
+
+### 2 - Implémentations OVHcloud
+
+| **Fonction** | **Description** | **Formats disponibles** | **Modèle de migration** | **Documentation disponible** |
+| --- | --- | --- | --- | --- |
+| Plan de contrôle de la plateforme | Interface dans l'espace client pour créer des streams, dashboard, Alias, index OpenSearch dashboards ou inputs Logstash  | NA  | **Entrant** : Configuration des éléments liés au cycle de vie du service  <br> **Sortant** : Recréation de  la configuration sur un autre service ou plateforme de gestion de logs. | [OVHcloud API](https://api.ovh.com/console/?section=%2Fdbaas%2Flogs&branch=v1) |
+| OpenSearch Index As a Service | Import ou export de documents via l'API OpenSearch | JSON | **Entrant** : conventions de noms spécifiques pour les index et alias, paramètres d'index et restrictions API.  <br> **Sortant** : Requêtes de défilement OpenSearch avec pagination | [OpenSearch Index as a Service](/pages/manage_and_operate/observability/logs_data_platform/opensearch_index) |
+| Tableaux de bords Greylog | Configuration des tableaux de bords et des recherches sauvegardées par le client sur l’interface  Graylog  | JSON | **Entrant** : utilisation des API ou du panneau de contrôle Graylog  <br> **Sortant** : utilisation des API Graylog | [Greylog documentation](https://go2docs.graylog.org/4-0/home.htm) |
+| Chiffrement des archives | Chiffrement systématique des archives en utilisant les clés PGP publiques fournies par le client | Clés PGP | **Entrant** : Enregistrement des clés PGP via API ou l’espace client  <br> **Sortant** : récupération des clés enregistrés et mise en place d’un mécanisme de chiffrement dans l’environnement cible | [Encrypting your logs archives](/pages/manage_and_operate/observability/logs_data_platform/archive_cold_storage_encryption) |
+
+### 3 - Fonctionnalités spécifiques
+
+| **Fonction** | **Description** | **Formats disponibles** | **Modèle de migration** | **Documentation disponible** |
+| --- | --- | --- | --- | --- |
+| 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 | **Entrant** : le système anti-DDoS fait partie de notre infrastructure et est activé par défaut. Aucune action n'est requise. <br> **Sortant** : commandez et configurez un anti-DDoS chez le nouveau fournisseur. | [OVHcloud DDoS Protection](/links/security/antiddos) |
+
+## Liste des architectures
+
+Les composants du produit sont accessibles depuis l’interface OVHcloud et permettent d’opérer les flux de données, les tableaux de bord, les outils de collecte, les index, les alias et les instances OpenSearch Dashboards. 
+
+Le produit est décliné en deux offres de service : 
+
+- Une infrastructure mutualisée : « logs-account »
+- Un cluster dédié : « logs-enterprise »
+
+## Services partenaires
+
+Les partenaires OVHcloud concernés figurent dans l'annuaire des [partenaires OVHcloud](/links/partner) sous les mots-clés « **Data center expansion and Migration** ».
+
+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. Les détails de facturation sont disponibles sur la page de présentation de l’offre de service : [Présentation de l’offre](/links/manage-operate/ldp).
+
+- Aucun frais de sortie supplémentaire n'est appliqué.
+- La facturation dépend du volume stocké et du type d’infrastructure mobilisé (indexé/archivé).
+- Toute prestation d’assistance ou export clé en main peut engendrer des coûts additionnels.
+
+## Conservation des données après résiliation du contrat
+
+OVHcloud ne garantit pas l'exploitation et la disponibilité des sauvegardes pour effectuer des restaurations des données des clients après la résiliation du service. 
+Les streams et index OpenSearch sont supprimés immédiatement après suppression du service.
+
+- Les archives Cold Storage sont immédiatement détruites à la résiliation du service
+- Le client est entièrement responsable du rapatriement de ses données via API ou [ldp-archive-mirror](https://github.com/ovh/ldp-archive-mirror) avant le décommissionnement du service ou la résiliation du contrat.

pages/account_and_service_management/reversibility/18-logs-data-platform-reversibility/meta.yaml

@@ -0,0 +1,3 @@
+id: 6cf09242-d6f1-48c7-b7f5-444f055180ae
+full_slug: reversibility-log-data-platform
+reference_category: account-and-service-management-reversibility-reversibility-policies

pages/account_and_service_management/reversibility/19-data-platform-reversibility/guide.en-gb.md

@@ -0,0 +1,61 @@
+---
+title: "Reversibility Policy for the Data Unified product"
+updated: 2025-07-08
+---
+
+**Objective**
+
+This document describes the reversibility policy for the Managed Data Visualization product covering the OVHcloud Data Platform 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** |
+| --- | --- | --- | --- | --- |
+| Data Catalog | Integration of more than 60 connectors to centralize data sources | CSV, JSON, XML, Parquet, Avro, JDBC, Kafka, REST, FTP, etc. | **Inbound**: configuration of standard connectors via web interface.<br> **Outbound**: export metadata and data via API.| [Data Catalog documentation](https://docs.dataplatform.ovh.net/#/en/product/data-catalog/index) |
+| Lakehouse Manager | Unified storage based on Apache, Iceberg and Trino | Parquet, ORC, Avro, Iceberg | **Inbound**: manual configuration via a web interface   <br> **Outbound**: export via Trino, Spark, or API. | [Lakehouse Manager documentation](https://docs.dataplatform.ovh.net/#/en/product/lakehouse-manager/index) |
+| Data Processing Engine | ETL/ELT pipeline orchestration with Spark and Python. | Python, PySpark | **Inbound**: manual configuration via web interface or git repository connection. <br> **Outbound**: export workflows via Git or API. | [Data processing engine documentation](https://docs.dataplatform.ovh.net/#/en/product/dpe/index) |
+| Analytics Manager | Create dashboards with no-code or SQL (Trino) editor. | SQL, JSON | **Inbound**: manual configuration via the web interface. <br> **Outbound**: export requests/visualizations via API. | [Analytics Manager documentation](https://docs.dataplatform.ovh.net/#/en/product/am/index) |
+| Applications Services | Web application deployment and APIs (Node.js, Python, Docker). | Node.js, Python, Docker, REST | **Inbound**: manual configuration via web interface or via git repository. <br> **Outbound**: export via Git or API | [Applications services documentation](https://docs.dataplatform.ovh.net/#/en/product/app-manager/index) |
+
+### 2 - OVHcloud implementations
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Data Processing Engine | ETL/ELT pipeline orchestration with Spark and Python. | OVHcloud platform-specific format, no standards deployed | **Inbound**: Data imported from data catalog with manual or automatic configuration of jobs <br> **Outbound**: No export possible | [Data processing engine documentation](https://docs.dataplatform.ovh.net/#/en/product/dpe/index) |
+| Identity and access management | Account management and user access on the platform | NA | **Inbound**: Configuration via the web interface <br> **Outbound**: Export user accounts in CSV format | [DATAP IAM documentation](https://docs.dataplatform.ovh.net/#/en/getting-further/project-toolkit?id=user-management) |
+
+### 3 - Specific features
+
+| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
+| --- | --- | --- | --- | --- |
+| Integrated monitoring | Monitoring and centralized performance management developed by OVHcloud.| NA | **Inbound**: Default integrated tracking interface on platform <br> **Outbound**: Logs and monitoring information cannot be exported | [Control center documentation](https://docs.dataplatform.ovh.net/#/en/product/cc/index) |
+
+## List of architectures
+
+OVHcloud Unified Data Platform service is based on open-source technologies such as Trino, Apache Iceberg, and Kubernetes. It is compatible with OVHcloud Public Cloud architectures.
+
+## Partner Services
+
+The OVHcloud partners concerned are listed in the [OVHcloud partners directory](/links/partner) under the "**Data center expansion and migration**" keywords.
+
+OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services).
+
+## Costs and fees
+
+Features described in the tables are available at no cost, unless otherwise specified and are freely usable.
+
+OVHcloud uses pay-as-you-go pricing, with no egress fee. Billing is interrupted immediately when the service is canceled, allowing flexible cost control.
+
+## Data retention after service termination
+
+Once the service is canceled, all data are irreversibly deleted. It is the client’s responsibility to carry out a full backup or migration before termination.