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

[BUG] Didn't find way to expand datastore capacity #3490

Open
HaruChebrolu opened this issue Jul 8, 2024 · 6 comments
Open

[BUG] Didn't find way to expand datastore capacity #3490

HaruChebrolu opened this issue Jul 8, 2024 · 6 comments

Comments

@HaruChebrolu
Copy link
Contributor

Describe the bug
I was unable to find a way to expand datastore capacity using govc. Please let me know if we have govc command to expand or reduce the size of datastore.

Copy link
Contributor

github-actions bot commented Jul 8, 2024

Howdy 🖐   HaruChebrolu ! 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.

@dougm
Copy link
Member

dougm commented Jul 11, 2024

We don't have that in govc. Sounds like expandVmfsDatastore or extendVmfsDatastore could be used and we have the generated govmomi methods. Don't know about reducing.

@HaruChebrolu
Copy link
Contributor Author

HaruChebrolu commented Jul 12, 2024

Sure, thanks for your response.
For reducing, can't we use shrinkVmfsDatastore. Please correct me if I am wrong
When can we expect to include the change on (3139de3) into a new release.

@dougm
Copy link
Member

dougm commented Jul 22, 2024

@HaruChebrolu your original question was on "expand datastore capacity". But based on your last comment it sounds like you're asking about vmdk capacity, rather than the datastore itself, is that right?
3139de3 is included in the 0.39 release.

@HaruChebrolu
Copy link
Contributor Author

@dougm
I am asking about increase Datastore capacity from created block devices.
Screenshot 2024-08-12 at 3 50 03 PM

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.

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