-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
vSphere Provider Roadmap Outline #6565
Comments
👍 Looks good. |
👍 Same here, looks good.
|
I this is number 7 item one? |
@chrislovecnm: I think it fits best to "Datastores"->"basic file commands". Since the files are always in a datastore. |
@thetuxkeeper where do you want me to put the text? |
I would put it to "Datastores"->"basic file commands". |
@chrislovecnm - has this doc / initiative been moved elsewhere? |
@mrjcleaver the velocity of this provider has fallen ;( |
My belief is that this happened as a consequence of it being sucked into the main repo. Now it is subject to central approval, to whom it is comparatively unimportant (vs. say AWS) therefore neglected. |
Hashicorp is also not able to do testing, but yes the PR process has been challenging. |
Okay, well, the harder it is the less momentum the initiative will have. |
FYI, I am in the process of getting an ESXi cluster setup for us to be able to run tests against - this will help at least get the tests working and allow us to be able to test PRs for functionality working as expected |
@chrislovecnm Is the roadmap in this issue updated? I haven't found another reference anywhere detailing what in vSphere is supported, and what is not. |
The issue is not completely up to date, the docs are fairly up to date |
@chrislovecnm thanks for the quick reply. With VMware now supporting OpenStack on top of ESXi, will development on the vSphere provider likely wind down / transition to the OpenStack provider? |
Hi all, Do you have a plan to support hot increase for CPU and memory ? Thanks. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
vSphere components started
Will update what is completed:
Overview of vSphere components not started
The text was updated successfully, but these errors were encountered: