merge develop

Author: OvhValentin

links/public-cloud/data-platform

@@ -0,0 +1,16 @@
+- [de-de](https://www.ovhcloud.com/de/public-cloud/data-platform/)
+- [en-asia](https://www.ovhcloud.com/asia/public-cloud/data-platform/)
+- [en-au](https://www.ovhcloud.com/en-au/public-cloud/data-platform/)
+- [en-ca](https://www.ovhcloud.com/en-ca/public-cloud/data-platform/)
+- [en-gb](https://www.ovhcloud.com/en-gb/public-cloud/data-platform/)
+- [en-ie](https://www.ovhcloud.com/en-ie/public-cloud/data-platform/)
+- [en-in](https://www.ovhcloud.com/en-in/public-cloud/data-platform/)
+- [en-sg](https://www.ovhcloud.com/en-sg/public-cloud/data-platform/)
+- [en-us](https://www.ovhcloud.com/en/public-cloud/data-platform/)
+- [es-es](https://www.ovhcloud.com/es-es/public-cloud/data-platform/)
+- [es-us](https://www.ovhcloud.com/es/public-cloud/data-platform/)
+- [fr-ca](https://www.ovhcloud.com/fr-ca/public-cloud/data-platform/)
+- [fr-fr](https://www.ovhcloud.com/fr/public-cloud/data-platform/)
+- [it-it](https://www.ovhcloud.com/it/public-cloud/data-platform/)
+- [pl-pl](https://www.ovhcloud.com/pl/public-cloud/data-platform/)
+- [pt-pt](https://www.ovhcloud.com/pt/public-cloud/data-platform/)

pages/index.md

@@ -590,14 +590,13 @@
                 + [Introducing Horizon](public_cloud/public_cloud_cross_functional/introducing_horizon)
                 + [Access and security settings in Horizon](public_cloud/public_cloud_cross_functional/access_and_security_in_horizon)
             + [Managing from OpenStack](public-cloud-cross-functional-openstack)
-                + [Preparing an environment for using the OpenStack API](public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api)
-                + [Changing an OpenStack user password in Horizon](public_cloud/public_cloud_cross_functional/change_openstack_user_password_in_horizon)
-                + [Setting OpenStack environment variables](public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables)
-                + [Using OpenStack Tokens](public_cloud/public_cloud_cross_functional/using_openstack_tokens_for_multiple_calls)
-                + [Managing tokens](public_cloud/public_cloud_cross_functional/managing_tokens)
+                + [Preparing an environment for using the OpenStack API](public_cloud/compute/prepare_the_environment_for_using_the_openstack_api)
+                + [Setting OpenStack environment variables](public_cloud/compute/loading_openstack_environment_variables)
+                + [Using OpenStack Tokens](public_cloud/compute/using_openstack_tokens_for_multiple_calls)
+                + [Managing tokens](public_cloud/compute/managing_tokens)
                 + [Authenticate on Openstack API with service account](manage_and_operate/iam/authenticate-api-openstack-with-service-account)
-                + [Creating and deleting OpenStack users](public_cloud/public_cloud_cross_functional/create_and_delete_a_user)
-                + [Managing firewall rules and port security on networks using OpenStack CLI](public_cloud/public_cloud_cross_functional/security_group_private_network)
+                + [Managing OpenStack users](public_cloud/compute/create_and_delete_a_user)
+                + [Managing firewall rules and port security on networks using OpenStack CLI](public_cloud/compute/security_group_private_network)
         + [Infrastructure](public-cloud-cross-functional-infrastructure)
             + [Comparison and resilience of Deployment Modes - Understanding 3-AZ / 1-AZ / Local Zones](public_cloud/public_cloud_cross_functional/deployment_modes_comparison_resilience_details)
             + [3-AZ resilience - Mechanisms and reference architectures](public_cloud/public_cloud_cross_functional/3az_ref_architecture)
@@ -949,6 +948,7 @@
                 + [Using Private Registry with OVHcloud Managed Kubernetes](public_cloud/containers_orchestration/managed_private_registry/using-private-registry-with-kubernetes)
                 + [Managing Helm charts in the OVHcloud Managed Private Registry](public_cloud/containers_orchestration/managed_private_registry/using-helm-charts)
                 + [Deploying a Helm chart from your private registry in Kubernetes](public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes)
+                + [Configuring Proxy Cache on an OVHcloud Managed Private Registry](public_cloud/containers_orchestration/managed_private_registry/configure-proxy-cache)
                 + [Migrate Helm Charts from Chartmuseum to OCI](public_cloud/containers_orchestration/managed_private_registry/migrate-helm-charts-from-chartmuseum-to-oci)
                 + [Scanning Docker images for vulnerabilities with OVHcloud Managed Private Registry](public_cloud/containers_orchestration/managed_private_registry/scan-docker-images-vulnerabilities)
                 + [Sign OCI artifacts with Cosign on OVHcloud Managed Private Registry](public_cloud/containers_orchestration/managed_private_registry/sign-artifacts-with-cosign)
@@ -1692,6 +1692,7 @@
             + [Object Storage - Encrypt your server-side objects with SSE-C](storage_and_backup/object_storage/s3_encrypt_your_objects_with_sse_c)
             + [Object Storage - Optimise the sending of your files to Object Storage](storage_and_backup/object_storage/s3_optimise_the_sending_of_your_files)
             + [Object Storage - Optimising Performance](storage_and_backup/object_storage/s3_performance_optimization)
+            + [Object Storage - Smart Storage Management with Lifecycle Rules](storage_and_backup/object_storage/s3_bucket_lifecycle)
             + [Object Storage - Managing object immutability with Object Lock (WORM)](storage_and_backup/object_storage/s3_managing_object_lock)
             + [Object Storage - Servers Access Logging](storage_and_backup/object_storage/s3_server_access_logging)
             + [Object Storage - Bucket ACL](storage_and_backup/object_storage/s3_bucket_acl)
@@ -1794,7 +1795,6 @@
     + [Backup and disaster recovery solutions](products/storage-backup-and-disaster-recovery-solution)
         + [Veeam](storage-backup-and-disaster-recovery-solution-veeam)
             + [Setting up Veeam Backup & Replication](storage_and_backup/backup_and_disaster_recovery_solutions/veeam/veeam_veeam_backup_replication)
-            + [Veeam Cloud Connect](storage_and_backup/backup_and_disaster_recovery_solutions/veeam/veeam_veeam_cloud_connect)
             + [Veeam Cloud Connect - How to migrate data from Veeam Cloud Connect to Object Storage](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/veeam-cloud-connect-migration)
             + [VMware Cloud Director - Veeam Backup Data Protection](hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd-backup)
             + [Preparing a Bare Metal Server backup with Veeam Enterprise](bare_metal_cloud/dedicated_servers/veeam-enterprise-server-backup-preparation)

pages/public_cloud/compute/share_images_between_projects/guide.de-de.md

@@ -1,33 +1,32 @@
 ---
 title: Image zwischen Public Cloud Projekten teilen
 excerpt: Erfahren Sie hier, wie Sie ein Image mit OpenStack zwischen Public Cloud Projekten teilen können
-updated: 2023-08-07
+updated: 2025-04-01
 ---
 
-> [!primary]
-> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite.
->
-
 ## Ziel
 
 Es kann vorkommen, dass Sie ein Image eines [Instanz Backups](/pages/public_cloud/compute/save_an_instance) oder ein Image eines [Volume Backups](/pages/public_cloud/compute/volume-backup) für mehrere Public Cloud Projekte freigeben müssen.
 
 Mit OpenStack können Sie ein Image für mehrere Projekte freigeben, auch wenn diese nicht zum selben Account gehören.
+
 Diese Funktion bietet viele Möglichkeiten, birgt aber auch Risiken. Es ist also wichtig, die Prinzipien zu verstehen.
 
 Wenn Sie z.B. ein Image aus Projekt A für Projekt B freigeben möchten (unter demselben oder einem anderen Account), gelten die folgenden Regeln:
 
+- Ein Image kamm nur innerhalb einer Region freigegeben werden. Ein in Projekt A in der Region GRA11 erstelltes Image ist beispielsweise nur für Projekt B in derselben Region (GRA11) verfügbar.
 - Das Image bleibt physisch an Projekt A angehängt. Das Projekt B verfügt nur über eine Zugriffsberechtigung (*access authorization*) für dieses Image.
 - Wenn Projekt A den Zugriff auf das Image unterdrückt (Löschen der ACL, Löschen des Images, Löschen des Projekts aufgrund ausstehender Zahlungen, etc.), funktionieren Instanzen, die von diesem Image aus in Projekt B ausgeführt werden, möglicherweise wegen Problemen bei Migration oder Rebuild nicht mehr.
 
 Daher ist es wichtig, diese Punkte in Betracht zu ziehen, bevor Sie diese Konfigurationen anwenden.
+
 Weitere Informationen finden Sie in der offiziellen [OpenStack Dokumentation](https://docs.openstack.org/image-guide/share-images.html){.external}.
 
 **Diese Anleitung erklärt, wie Sie ein Image für ein anderes Projekt freigeben und dabei die Image-Konfiguration und den Image-Status beibehalten.**
 
 ## Voraussetzungen
 
-- Sie sind mit der Vorgehensweise zur [Vorbereitung der Umgebung für die Verwendung der OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api) vertraut (empfohlen).
+- Sie haben [Ihre Umgebung für die Verwendung der OpenStack API vorbereitet](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
 - Sie haben eine [Public Cloud Instanz](https://www.ovhcloud.com/de/public-cloud/) in Ihrem Account erstellt.
 - Sie haben einen [OpenStack User erstellt](/pages/public_cloud/public_cloud_cross_functional/create_and_delete_a_user).
 
@@ -56,9 +55,16 @@ $ openstack image list --private
 $ openstack image set --shared <Image_UUID>
 ```
 
+Sie können den folgenden Befehl ausführen, um die Images aufzulisten, die für ein anderes Projekt freigegeben werden können:
+
+```bash
+$ openstack image list --shared
+9a0fbdc5-****-****-****-8d404a1313ba 	pfsense
+```
+
 ### Hinzufügen eines Projekts zu einem Image
 
-Im nächsten Schritt fügen Sie die UUID eines anderen Projekts als Member des Image hinzu. In unserem Beispiel unten fügen wir die UUID von Projekt B hinzu.
+Im nächsten Schritt fügen Sie die UUID eines anderen Projekts als *Member* des Image hinzu. In unserem Beispiel unten fügen wir die UUID von Projekt B hinzu.
 
 ```bash
 $ openstack image add project 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba <UUID_Project_B>
@@ -127,6 +133,8 @@ $ openstack image show 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Überprüfen der Member des Image
 
+Um alle Projekte anzuzeigen, die über das Quell-Projekt (in diesem Fall Projekt A) Zugriff auf das Image haben, können Sie diesen Befehl ausführen:
+
 ```bash
 $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 +--------------------------------------+----------------------------------+----------+
@@ -137,14 +145,16 @@ $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 +--------------------------------------+----------------------------------+----------+
 ```
 
-### Entfernen eines Members aus einem Image oder Aufheben der Freigabe eines Images
+### Entfernen eines *Members* aus einem Image oder Aufheben der Freigabe eines Images
+
+Im Quell-Projekt (Projekt A) können Sie ein *Member* der Freigabe löschen:
 
 ```bash
 $ openstack image remove project <image> <UUID_Project_To_Delete>
 ```
 
 ## Weiterführende Informationen
 
-[Backup einer Instanz von einem Rechenzentrum in ein anderes übertragen](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)
+[Backup einer Instanz von einer Region in eine andere übertragen](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)
 
-Für den Austausch mit unserer User Community gehen Sie auf <https://community.ovh.com/en/>.
+Treten Sie unserer [User Community](/links/community) bei.

pages/public_cloud/compute/share_images_between_projects/guide.en-asia.md

@@ -1,7 +1,7 @@
 ---
 title: Sharing images between Public Cloud projects
 excerpt: Find out how to share images between Public Cloud projects using OpenStack
-updated: 2023-07-27
+updated: 2025-04-01
 ---
 
 ## Objective
@@ -14,6 +14,7 @@ This feature offers many possibilities, but it also has its risks. It is therefo
 
 For example, if we want to share an image from Project A with Project B (in the same or different account), the following rules apply:
 
+- Images can only be shared within the same region. For example, an image created in Project A in the GRA11 region will only be available for Project B within the same GRA11 region.
 - The image remains physically attached to Project A. Project B only has "access authorization" to this image.
 - If Project A removes access to the image (like ACL, image deletion or if the project is deleted for unpaid invoices, etc.), the instances running from this image on Project B may not work anymore due to migration or rebuild issues.
 
@@ -59,6 +60,13 @@ $ openstack image list --private
 $ openstack image set --shared <Image_UUID>
 ```
 
+You can run the following command to list your images that can be shared with another project:
+
+```bash
+$ openstack image list --shared
+9a0fbdc5-****-****-****-8d404a1313ba 	pfsense
+```
+
 ### Add a project to an image
 
 The next step is to add the UUID of a different project as a member of the image. In our example below, we add the UUID of "Project B" to the image.
@@ -130,6 +138,8 @@ $ openstack image show 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Verify all the members of an image
 
+To see all the projects which have access to the image, from the source project (in this case project A), you can run this command:
+
 ```bash
 $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 +--------------------------------------+----------------------------------+----------+
@@ -142,6 +152,8 @@ $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Delete a member of an image or unshare an image
 
+In the source project (project A), you can delete a member of the share:
+
 ```bash
 $ openstack image remove project <image> <UUID_Project_To_Delete>
 ```

pages/public_cloud/compute/share_images_between_projects/guide.en-au.md

@@ -1,7 +1,7 @@
 ---
 title: Sharing images between Public Cloud projects
 excerpt: Find out how to share images between Public Cloud projects using OpenStack
-updated: 2023-07-27
+updated: 2025-04-01
 ---
 
 ## Objective
@@ -14,6 +14,7 @@ This feature offers many possibilities, but it also has its risks. It is therefo
 
 For example, if we want to share an image from Project A with Project B (in the same or different account), the following rules apply:
 
+- Images can only be shared within the same region. For example, an image created in Project A in the GRA11 region will only be available for Project B within the same GRA11 region.
 - The image remains physically attached to Project A. Project B only has "access authorization" to this image.
 - If Project A removes access to the image (like ACL, image deletion or if the project is deleted for unpaid invoices, etc.), the instances running from this image on Project B may not work anymore due to migration or rebuild issues.
 
@@ -59,6 +60,13 @@ $ openstack image list --private
 $ openstack image set --shared <Image_UUID>
 ```
 
+You can run the following command to list your images that can be shared with another project:
+
+```bash
+$ openstack image list --shared
+9a0fbdc5-****-****-****-8d404a1313ba 	pfsense
+```
+
 ### Add a project to an image
 
 The next step is to add the UUID of a different project as a member of the image. In our example below, we add the UUID of "Project B" to the image.
@@ -130,6 +138,8 @@ $ openstack image show 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Verify all the members of an image
 
+To see all the projects which have access to the image, from the source project (in this case project A), you can run this command:
+
 ```bash
 $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 +--------------------------------------+----------------------------------+----------+
@@ -142,6 +152,8 @@ $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Delete a member of an image or unshare an image
 
+In the source project (project A), you can delete a member of the share:
+
 ```bash
 $ openstack image remove project <image> <UUID_Project_To_Delete>
 ```

pages/public_cloud/compute/share_images_between_projects/guide.en-ca.md

@@ -1,7 +1,7 @@
 ---
 title: Sharing images between Public Cloud projects
 excerpt: Find out how to share images between Public Cloud projects using OpenStack
-updated: 2023-07-27
+updated: 2025-04-01
 ---
 
 ## Objective
@@ -14,6 +14,7 @@ This feature offers many possibilities, but it also has its risks. It is therefo
 
 For example, if we want to share an image from Project A with Project B (in the same or different account), the following rules apply:
 
+- Images can only be shared within the same region. For example, an image created in Project A in the GRA11 region will only be available for Project B within the same GRA11 region.
 - The image remains physically attached to Project A. Project B only has "access authorization" to this image.
 - If Project A removes access to the image (like ACL, image deletion or if the project is deleted for unpaid invoices, etc.), the instances running from this image on Project B may not work anymore due to migration or rebuild issues.
 
@@ -59,6 +60,13 @@ $ openstack image list --private
 $ openstack image set --shared <Image_UUID>
 ```
 
+You can run the following command to list your images that can be shared with another project:
+
+```bash
+$ openstack image list --shared
+9a0fbdc5-****-****-****-8d404a1313ba 	pfsense
+```
+
 ### Add a project to an image
 
 The next step is to add the UUID of a different project as a member of the image. In our example below, we add the UUID of "Project B" to the image.
@@ -130,6 +138,8 @@ $ openstack image show 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Verify all the members of an image
 
+To see all the projects which have access to the image, from the source project (in this case project A), you can run this command:
+
 ```bash
 $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 +--------------------------------------+----------------------------------+----------+
@@ -142,6 +152,8 @@ $ openstack image member list 9a0fbdc5-1f4a-4a1c-ad46-8d404a1313ba
 
 ### Delete a member of an image or unshare an image
 
+In the source project (project A), you can delete a member of the share:
+
 ```bash
 $ openstack image remove project <image> <UUID_Project_To_Delete>
 ```