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

Add volume.relocate command #3164

Open
danielkucera opened this issue Jun 28, 2023 · 7 comments
Open

Add volume.relocate command #3164

danielkucera opened this issue Jun 28, 2023 · 7 comments

Comments

@danielkucera
Copy link

Is your feature request related to a problem? Please describe.
I would like to use govc for migrating CNS volumes from one datastore to another as we need to discontinue the old datastore.

Describe the solution you'd like
Add a command volume.relocate for which one needs to specify volumeId or Name and the target datastore and govc will call the RelocateVoume function and migrate the volume

Describe alternatives you've considered
I tried to write my own implementation here but I think more people can benefit if this is included in govc.
I also tried to use cloud-native-storage-self-service-manager but it's not easy to setup, it's not very mature and it is complicated so I don't trust it very much.

Additional context
This is related to #2051

@github-actions
Copy link
Contributor

Howdy 🖐   danielkucera ! Thank you for your interest in this project. We value your feedback and will respond soon.

If you want to contribute to this project, please make yourself familiar with the CONTRIBUTION guidelines.

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@danielkucera
Copy link
Author

/remove-lifecycle stale

Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@danielkucera
Copy link
Author

/remove-lifecycle stale

Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@danielkucera
Copy link
Author

/remove-lifecycle stale
this is fun

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants