|
1 | 1 | ---
|
2 | 2 | title: "Reversibility Policy for the Managed Search Engine Software Platform product"
|
3 |
| -updated: 2025-07-09 |
| 3 | +updated: 2025-07-11 |
4 | 4 | ---
|
5 | 5 |
|
6 |
| -##Objective |
| 6 | +## Objective |
7 | 7 |
|
8 | 8 | This document describes the reversibility policy for the Managed Search Engine Software Platform product covering the OVHcloud Managed OpenSearch offer.
|
9 | 9 |
|
10 | 10 | This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.
|
11 | 11 |
|
12 |
| -##List of features |
| 12 | +## List of features |
13 | 13 |
|
14 | 14 | Features of the product line fall into three categories:
|
15 | 15 |
|
16 | 16 | 1. **Core features** for which we guarantee migration capacity.
|
17 | 17 | 2. **OVHcloud implementations** that require adaptation to a new migration environment.
|
18 | 18 | 3. **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
|
19 | 19 |
|
20 |
| -## 1-Core features |
| 20 | +### 1. Core features |
21 | 21 |
|
22 | 22 | | **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
|
23 | 23 | | --- | --- | --- | --- | --- |
|
24 |
| -| Platform as a Service | NoSQL indexing, content search and data analysis engine fully managed by OVHcloud | JSON (S3 snapshots) | **Inbound** : source snapshot creation, migration via RFS to the platform <br>**Outbound** : export OVHcloud snapshots to any compatible OpenSearch cluster via RFS or native tools | [OpenSearch-Getting started](/pages/public_cloud/public_cloud_databases/opensearch_02_getting_Started) | |
25 |
| -| Standard REST API access | Access via OpenSearch REST API (port 9200) | JSON | **Inbound**: direct connection from existing tools and applications <br>**Outbound**: data extraction via API for migration to another cluster. | [OVH-OpenSearch API](https://eu.api.ovh.com/console/?section=%2Fcloud&branch=v1#get-/cloud/project/-serviceName-/database/opensearch) | |
26 |
| -| Manual snapshots | Create snapshots manually via API or Dashboard | JSON (S3, external storage) | **Inbound**: restoring an external snapshot. <br>**Outbound**: snapshot exportable to any OpenSearch environment. | [OVH-OpenSearch API](https://eu.api.ovh.com/console/?section=%2Fcloud&branch=v1#get-/cloud/project/-serviceName-/database/opensearch) | |
27 |
| -| Standard plugins | List of open-source plugins (ICU Analysis, Phonetic Analysis, etc.) that can be activated, deactivated and compatible with the technology | Official OpenSearch plugins | **Inbound**: Enable plugins compatible with the target version <br>**Outbound**: reuse plugins if it's are supported by the new environment | [OpenSearch - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/opensearch_01_capabilities) | |
| 24 | +| Platform as a Service | NoSQL indexing, content search and data analysis engine fully managed by OVHcloud | JSON (S3 snapshots) | **Inbound**: source snapshot creation, migration via RFS to the platform <br>**Outbound**: export OVHcloud snapshots to any compatible OpenSearch cluster via RFS or native tools | [OpenSearch - Getting started](/pages/public_cloud/public_cloud_databases/opensearch_02_getting_Started) | |
| 25 | +| Standard REST API access | Access via OpenSearch REST API (port 9200) | JSON | **Inbound**: direct connection from existing tools and applications <br>**Outbound**: data extraction via API for migration to another cluster | [OVH - OpenSearch API](https://eu.api.ovh.com/console/?section=%2Fcloud&branch=v1#get-/cloud/project/-serviceName-/database/opensearch) | |
| 26 | +| Manual snapshots | Create snapshots manually via API or Dashboard | JSON (S3, external storage) | **Inbound**: restoring an external snapshot <br>**Outbound**: snapshot exportable to any OpenSearch environment. | [OVH - OpenSearch API](https://eu.api.ovh.com/console/?section=%2Fcloud&branch=v1#get-/cloud/project/-serviceName-/database/opensearch) | |
| 27 | +| Standard plugins | List of open-source plugins (ICU Analysis, Phonetic Analysis, etc.) that can be activated, deactivated and compatible with the technology | Official OpenSearch plugins | **Inbound**: Enable plugins compatible with the target version <br>**Outbound**: reuse plugins if they are supported by the new environment | [OpenSearch - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/opensearch_01_capabilities) | |
28 | 28 |
|
29 | 29 |
|
30 |
| -## 2-OVHcloud Implementations |
| 30 | +### 2. OVHcloud Implementations |
31 | 31 |
|
32 | 32 | | **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
|
33 | 33 | | --- | --- | --- | --- | --- |
|
34 |
| -| Automatic backups managed by OVHcloud | Daily backups managed by OVHcloud (retention varies depending on the chosen offer) | OVHcloud internal snapshots | **Inbound**: Not applicable. Feature available by default and no action is required by the user of the platform <br>**Outbound**: Create a new service, restore an OVHcloud snapshot locally, then export it manually to the new environment | [Public Cloud Databases - Automatic backups ](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) | |
35 |
| -| vRack | The vRack, or virtual rack, is a private VLAN technology that enables the connection between OVHcloud services | NA | **Inbound**: <br>**Outbound**: | [Creating Public Cloud Databases V(x)LANs](/pages/public_cloud/public_cloud_databases/databases_08_vrack) | |
36 |
| -Access Control List (ACL) | Manage access rights via the OVHcloud interface | NA | **Inbound**: create rules manually in the OVHcloud interface. <br>**Outbound**: Convert ACL rules to new provider format. | [OpenSearch - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/opensearch_01_capabilities) | |
37 |
| -| Metrics | Metrics collection integrated into the OVHcloud infrastructure | Prometheus metrics | **Inbound**: send logs via a dedicated entry point <br>**Outbound** : possible export and reconfiguration needed on the new platform | [OpenSearch - Monitor your infrastructure ](/pages/public_cloud/public_cloud_databases/opensearch_200_elk_like) | |
| 34 | +| Automatic backups managed by OVHcloud | Daily backups managed by OVHcloud (retention varies depending on the chosen offer) | OVHcloud internal snapshots | **Inbound**: Not applicable. Feature available by default and no action is required by the user of the platform <br>**Outbound**: Create a new service, restore an OVHcloud snapshot locally, then export it manually to the new environment | [Public Cloud Databases - Automatic backups ](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) | |
| 35 | +| vRack | The vRack or virtual rack, is a private VLAN technology that enables the connection between OVHcloud services | NA | **Inbound**: <br>**Outbound**: | [Creating Public Cloud Databases V(x)LANs](/pages/public_cloud/public_cloud_databases/databases_08_vrack) | |
| 36 | +Access Control List (ACL) | Manage access rights via the OVHcloud interface | NA | **Inbound**: create rules manually in the OVHcloud interface <br>**Outbound**: Convert ACL rules to new provider format | [OpenSearch - Capabilities and Limitations](/pages/public_cloud/public_cloud_databases/opensearch_01_capabilities) | |
| 37 | +| Metrics | Metrics collection integrated into the OVHcloud infrastructure | Prometheus metrics | **Inbound**: send logs via a dedicated entry point <br>**Outbound**: possible export and reconfiguration needed on the new platform | [OpenSearch - Monitor your infrastructure ](/pages/public_cloud/public_cloud_databases/opensearch_200_elk_like) | |
38 | 38 |
|
39 |
| - |
40 |
| -## 3-Specific features |
| 39 | +### 3. Specific features |
41 | 40 |
|
42 | 41 | | **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
|
43 | 42 | | --- | --- | --- | --- | --- |
|
44 |
| -| Infrastructure as a code | Automated deployment via Terraform modules specific to OVHcloud | NA | **Inbound**: scripts to be adapted for other providers <br>**Outbound**: Terraform configurations need to be rewritten | [Terraform](https://registry.terraform.io/providers/ovh/latest/docs).{external} | |
45 |
| -| 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 | **Inbound**: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required <br> **Outbound**: Order and configure an anti-DDoS solution from the new provider | [Anti-DDoS OVHcloud](https://www.ovhcloud.com/en/security/anti-ddos/) | |
| 43 | +| Infrastructure as a code | Automated deployment via Terraform modules specific to OVHcloud | NA | **Inbound**: scripts to be adapted for other providers <br>**Outbound**: Terraform configurations need to be rewritten | [Terraform](https://registry.terraform.io/providers/ovh/latest/docs){.external} | |
| 44 | +| 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 | **Inbound**: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required <br> **Outbound**: Order and configure an anti-DDoS solution from the new provider | [Anti-DDoS OVHcloud](/links/security/anti-ddos) | |
| 45 | + |
| 46 | +## List of architectures |
46 | 47 |
|
47 |
| -##List of architectures |
48 | 48 | The product offers multi-node clusters (up to 3 nodes for the Business range), with data replication for high availability. Automatic sharding is managed via the number of replicas configured per index.
|
| 49 | + |
49 | 50 | Architectures include:
|
| 51 | + |
50 | 52 | - Dedicated cluster: Logical isolation of resources by project.
|
51 |
| -- vRack integration: Secure interconnection with other OVHcloud services |
52 |
| -- Vertical scalability: Node scalability (RAM, storage) via the OVHcloud interface |
| 53 | +- vRack integration: Secure interconnection with other OVHcloud services. |
| 54 | +- Vertical scalability: Node scalability (RAM, storage) via the OVHcloud interface. |
53 | 55 |
|
54 |
| -##Partner services |
| 56 | +## Partner services |
55 | 57 |
|
56 | 58 | The OVHcloud partners concerned are listed in the [OVHcloud partners directory](/links/partner) under the "**Data center expansion and Migration**" keywords.
|
57 | 59 |
|
58 | 60 | OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services).
|
59 | 61 |
|
60 |
| -##Cost and fees |
61 |
| -Features described in the tables are available at no cost, unless otherwise specified and are freely usable by the customer. |
62 |
| -By default, no extra billing is applied following the data migration. |
63 |
| -Billing stops as soon as the service is canceled. |
| 62 | +## Cost and fees |
| 63 | + |
| 64 | +Features described in the tables are available at no cost, unless otherwise specified and are freely usable by the customer. By default, no extra billing is applied following the data migration. Billing stops as soon as the service is canceled. |
| 65 | + |
| 66 | +## Data retention after contract termination |
64 | 67 |
|
65 |
| -##Data retention after contract termination |
| 68 | +Snapshots (automatic or manual ones) are irreversibly deleted and a manual export is required to preserve data. |
| 69 | +Primary instances are deleted immediately, and backups are stored by OVHcloud between 2 days and 1 month depending on the options specified in the contract. |
66 | 70 |
|
67 |
| -Snapshots (automatic or manual ones) are irreversibly deleted. A manual export is required to preserve data. |
68 |
| -Primary instances are deleted immediately, and backups are stored by OVHcloud, between 2 days and 1 month depending on the options specified in the contract. |
69 | 71 | Please note that the customer cannot rely on these backups to perform data restores. OVHcloud does not guarantee exploitation and availability of backups to perform restores of customer data after the service cancelation.
|
0 commit comments