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

vSphere Provider Roadmap Outline #6565

Closed
chrislovecnm opened this issue May 9, 2016 · 18 comments
Closed

vSphere Provider Roadmap Outline #6565

chrislovecnm opened this issue May 9, 2016 · 18 comments

Comments

@chrislovecnm
Copy link
Contributor

chrislovecnm commented May 9, 2016

vSphere components started

Will update what is completed:

  1. Virtual machines - mostly done
    • Update functionatlity is underway
  2. Disks - Need to double check what is doen
    • vmx attachable disks
    • cdrom iso images
  3. Misc
    • folder - update is missing
    • cdrom
  4. Finders
    • some basic finders are implemented to support object creation

Overview of vSphere components not started

  1. Base servers crud P3
    • single vsphere server (not going to be addressed)
    • cluster
      • add, update, create, no delete
  2. Datacenter P2
    • cluster and non-clustered
    • CRD are in govc ... do we have update?
  3. Datastores - P1 - some work done
    • non-ha datastores
    • ha cluster based datastores (SDRS)
    • basic file commands cp,mv,rm
    • CRD are in govc ... do we have update?
    • basic file commands
  4. Networks - P1
    • portgroups
      • CRD - no update
    • distributed virtual switch
    • firewalls
    • vnics
    • finders for "Networks" but no CUD available R only - TODO verify
  5. Resource pools - prority??
    • Full CRUD
  6. ESX Hosts - P4
    • portgroups
    • vswitch
    • storage partition
    • maintenance mode
    • host options
    • vnic
  7. Misc - P4
    • Events
    • Extensions
    • Host Info
    • Licenses
    • Logs
@chrislovecnm
Copy link
Contributor Author

@stack72 @jen20 @phinze ~ can I get a vsphere label

@rossedman
Copy link

👍 Looks good.

@thetuxkeeper
Copy link
Contributor

👍 Same here, looks good.
Some "missing" things:

  • folders have no update implemented, but supported by Rename_Task in vSphere API (haven't checked govmomi)
  • datastore files: upload (but no creation without source), rename/update, read and deletion are implemented. So file uploads should already work (vmdk, cdrom iso, ...)

@chrislovecnm
Copy link
Contributor Author

datastore files: upload (but no creation without source), rename/update, read and deletion are implemented. So file uploads should already work (vmdk, cdrom iso, ...)

I this is number 7 item one?

@thetuxkeeper
Copy link
Contributor

thetuxkeeper commented May 10, 2016

@chrislovecnm: I think it fits best to "Datastores"->"basic file commands". Since the files are always in a datastore.
And yes, also 7.1.

@chrislovecnm
Copy link
Contributor Author

@thetuxkeeper where do you want me to put the text?

@thetuxkeeper
Copy link
Contributor

I would put it to "Datastores"->"basic file commands".
And you can remove "Image Uploads" since it's covered by the datastore operations if there's nothing I'm missing.

@mrjcleaver
Copy link

@chrislovecnm - has this doc / initiative been moved elsewhere?

@chrislovecnm
Copy link
Contributor Author

@mrjcleaver the velocity of this provider has fallen ;(

@mrjcleaver
Copy link

mrjcleaver commented Oct 10, 2016

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.

#9076

@chrislovecnm
Copy link
Contributor Author

Hashicorp is also not able to do testing, but yes the PR process has been challenging.

@mrjcleaver
Copy link

Okay, well, the harder it is the less momentum the initiative will have.

@stack72
Copy link
Contributor

stack72 commented Oct 25, 2016

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

@donbecker
Copy link

@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.

@chrislovecnm
Copy link
Contributor Author

The issue is not completely up to date, the docs are fairly up to date

@donbecker
Copy link

donbecker commented Nov 29, 2016

@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?

@renaudhager
Copy link

Hi all,

Do you have a plan to support hot increase for CPU and memory ?

Thanks.

@ghost
Copy link

ghost commented Apr 10, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants