Hi Corey
I've read the "How to Contribute" guide and "Core Concepts." I understand usually one project is copied, but I don't know if I should start from the vcloud or vcloud-director projects. Also I don't know if it would be better to create a new provider or modify one of the existing vcloud providers. And I'd appreciate any other relevant advice.
Great to hear you're interested in working on the vCloud provider! Thanks also for reading up first. As regards what the best way is to get started, the others on this list who have worked on the vcloud, vcloud-director and (open PR [1]) vsphere providers may be better placed to advise.
In general, I suspect it will depend on how significant the changes are between what is supported in the current provider(s), and what we are looking to do here (I'm guessing 5.x will be the new target version)?
If the current vcloud-director provider turns out to be the closest match, that may be a good one to use as a base, since the implementation of ComputeService on top of the underlying APIs is something we should also be able to adapt from other providers.
One thing to look out for is that we have generally moved away from "expect" tests for the integration tests towards using a mock webserver. Whatever we decide to use as a base, we should bear that in mind.
Another pattern that may or may not be relevant to the vCloud version we're talking about here are *optional* APIs that will only be available in some installations. The OpenStack APIs have some examples of how that works.
Looking forward to seeing this come along! Please don't hesitate to open PRs early, even if they're still WIP. That's often an easy way to discuss approaches and general code style.
Hope that helps! ap [1] https://github.com/jclouds/jclouds-labs/pull/61
