Skip to content

Commit fd216c6

Browse files
authored
Update guide.en-gb.md
1 parent c0be45c commit fd216c6

File tree

1 file changed

+12
-11
lines changed
  • pages/account_and_service_management/reversibility/20-ai-notebook-reversbility

1 file changed

+12
-11
lines changed
Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Reversibility Policy for the Notebook Interface product"
3-
updated: 2025-07-03
3+
updated: 2025-07-07
44
---
55

66
## Objective
@@ -9,51 +9,52 @@ This document describes the reversibility policy for the Notebook Interface prod
99

1010
This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers.
1111

12-
**List of features**
12+
## List of features
1313

1414
Features of the product line fall into three categories:
1515

1616
1. **Core features** for which we guarantee migration capacity.
1717
2. **OVHcloud implementations** that require adaptation to a new migration environment.
1818
3. **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
1919

20-
### Core features
20+
### 1. Core features
2121

2222
| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
2323
| --- | --- | --- | --- | --- |
2424
| Import and export Notebooks | Store notebooks in standard Jupyter (.ipynb) or VS Code Notebook formats including import and export without adaptation | (.ipynb), Python, CSV, TXT | **Inbound**: Direct download of .ipynb files or conversion via Jupyter/VS Code. <br>**Outgoing**: Direct export of .ipynb notebooks, reusable on any Jupyter or other compatible environment. |[Using data in a notebook via the OVHcloud Control Panel](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui) |
2525
| Support for standard AI frameworks | Pre-installation of environments such as TensorFlow, PyTorch, Scikit-learn, MXNet, Hugging Face, etc. | Notebooks, Python scripts | **Inbound**: import notebooks/scripts using these frameworks. <br>**Outbound**: export notebooks/scripts, which can be reused on any platform supporting these frameworks. | [Tutorial - Using Tensorboard in a notebook](/pages/public_cloud/ai_machine_learning/notebook_tuto_02_tensorboard) |
26-
| Manage custom environments | Install libraries and dependencies via pip/conda, specific to each notebook | YAML (environments), requirements.txt | **Inbound**: Recreating the environment via requirements.txt/environment.yml files. <br>**Outbound**: Manually export from the package list, adapt, and reinstall on the target environment | [Features, Capabilities and Limits](/pages/public_cloud/ai_machine_learning/notebook_guide_capabilities) |
26+
| Manage custom environments | Install libraries and dependencies via pip/conda, specific to each notebook | YAML (environments), requirements.txt | **Inbound**: Recreating the environment via requirements.txt/environment.yml files. <br>**Outbound**: Manually export from the package list, adapt, and reinstall on the target environment | [Features, Capabilities and Limits](/pages/public_cloud/ai_machine_learning/notebook_guide_capabilities) |
2727
| VS Code Integration | Visual Studio Code edition support for Notebooks | Notebooks, Python scripts | **Inbound**: possible import, but requires adaptation of environment if target does not support VS Code. <br>**Outbound**: export notebooks/scripts, possibly adjust VS Code configuration on target environment | [Features, Capabilities and Limits](/pages/public_cloud/ai_machine_learning/notebook_guide_capabilities) |
2828

29-
### OVHcloud Implementations
29+
### 2. OVHcloud Implementations
3030

3131
| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
3232
| --- | --- | --- | --- | --- |
3333
| Compatibility with S3 Object Storage | User data are synchronized on an OVHcloud Object Storage S3 once the Notebook has been stopped/deleted. S3 storage can be done with an OVHcloud product or outside of OVHcloud infrastructure.| S3 (objects, files) | **Inbound**: import data via S3 Object Storage or direct download. <br>**Outbound**: export files/datasets via S3 Object Storage, which can be reused on any other S3-compatible storage | [Features, Capabilities, and Limits](/pages/public_cloud/ai_machine_learning/notebook_guide_capabilities) <br> [Object Storage product reversibility policy ](/pages/account_and_service_management/reversibility/16-object-storage-reversibility) |
34-
| User access management | Access management via the OVHcloud interface, non-standard version | NA | **Inbound**: Manual configuration of accesses on the interface <br>**Outbound** adapt rights management according to the target tool (JupyterHub, VS Code Live Share, etc.). | [Use data in a notebook via the OVHcloud Control Panel](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui) |
34+
| User access management | Access management via the OVHcloud interface, non-standard version | NA | **Inbound**: Manual configuration of accesses on the interface <br>**Outbound**: adapt rights management according to the target tool (JupyterHub, VS Code Live Share, etc.). | [Use data in a notebook via the OVHcloud Control Panel](/pages/public_cloud/ai_machine_learning/notebook_guide_data_ui) |
3535

36-
### Specific features
36+
### 3. Specific features
3737

3838
| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** |
3939
| --- | --- | --- | --- | --- |
4040
| OVHcloud API, CLI and Python SDK | Notebook management, automation and migration via OVHcloud’s own REST API, CLI AI and Python SDK. | JSON, YAML, Python | **Inbound**: Tools and management interfaces available by default <br>**Outbound**: APIs and CLIs will depend on the target environments and may require adaptation. | [AI Notebooks - Getting started](/pages/public_cloud/ai_machine_learning/notebook_guide_introduction_definition) |
4141
| 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/) |
4242

43-
**List of architectures**
43+
## List of architectures
4444

4545
OVHcloud’s service offer includes managed Jupyter and Visual Studio Code environments, with on-demand CPU/GPU resource allocation.
4646
Notebooks are isolated by user and project, with a persistent storage on an S3-compatible Object Storage service. The main AI frameworks (TensorFlow, PyTorch, Scikit-learn, MXNet, Hugging Face) are preinstalled with native integration of data science tools (Matplotlib, Seaborn, Pandas). The architecture supports notebook shutdowns and restarts, automatic data synchronization and multi-user management.
4747

48-
**Partner services**
48+
## Partner services
4949

5050
The OVHcloud partners concerned are listed in the [OVHcloud partners directory](/links/partner) under the "**Data center expansion and Migration**" keywords.
5151

5252
OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services).
5353

54-
**Cost and fees**
54+
### Cost and fees
55+
5556
Billing is based on 'pay-as-you-go'. There is no specific fees applied on service termination. Stopping or deleting a notebook will stop billing for computing resources. The associated storage (Object Storage) remains billed until data are deleted. Notebooks and data must be exported before deleting and canceling the service.
5657

57-
**Data retention after contract termination**
58+
### Data retention after contract termination
5859

5960
After deleting a notebook, OVHcloud automatically synchronizes user data on an S3-compatible Object Storage. Notebooks and files remain accessible on this storage space until the user deletes it manually. Once data has been deleted from this space, it cannot be restored.Therefore, it's imperative to export all the necessary data before decommissioning the service.

0 commit comments

Comments
 (0)