Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enterprise File Storage - Migration of a service from on cluster to another in the same Fabric #249

Open
martinovh opened this issue Jan 6, 2025 · 0 comments
Assignees
Labels
Enterprise File Storage Manage file storage volume, reserved IOPS and bandwidth performance per TiB, based on NetApp ONTAP

Comments

@martinovh
Copy link
Collaborator

martinovh commented Jan 6, 2025

User story

As an OVHcloud customer using multiple EFS
I want to be able to move my service from a cluster to another one in the same fabric so that I can easily migrate between EFS generations and ease my upscale

Follow, Vote and give your Feedback

You can follow this task with the notification on the right tab.
Ask us anything here in the comments below, and vote with emojis for most requested items !
👍 to vote for this issue

Discuss on Discord

Feel free to discuss with us on https://discord.gg/ovhcloud

@martinovh martinovh moved this to Prioritized in Cloud Roadmap & Changelog Jan 6, 2025
@martinovh martinovh changed the title EFS - Migration of a service from on cluster to another in the same Fabric Enterprise File Storage - Migration of a service from on cluster to another in the same Fabric Jan 9, 2025
@martinovh martinovh added the Enterprise File Storage Manage file storage volume, reserved IOPS and bandwidth performance per TiB, based on NetApp ONTAP label Jan 10, 2025
@martinovh martinovh self-assigned this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enterprise File Storage Manage file storage volume, reserved IOPS and bandwidth performance per TiB, based on NetApp ONTAP
Projects
Status: Prioritized
Development

No branches or pull requests

1 participant