Hi Andrew,
Thank you for this guidance.
I right away hit a "provider not found" issue concerning provider
"vcloud-director." I noticed in the list of extant providers (about 12
tokens from the end) an entry for "vcloud." Should I be using this one
instead?
-Paul
Exception in thread "main" java.util.NoSuchElementException: key
[vcloud-director] not in the list of providers or apis:
{providers=[aws-cloudwatch, rackspace-cloudblockstorage-us,
rackspace-cloudblockstorage-uk, rackspace-clouddns-us,
rackspace-clouddns-uk, aws-sqs, aws-sts, aws-route53, ultradns-ws, dynect,
rackspace-cloudloadbalancers-uk, rackspace-cloudloadbalancers-us,
greenhousedata-element-vcloud, aws-ec2, cloudservers-us, cloudservers-uk,
trmk-vcloudexpress, trmk-ecloud, bluelock-vcloud-zone01, gogrid,
elastichosts-lon-p, elastichosts-sat-p, elastichosts-lon-b,
openhosting-east1, serverlove-z1-man, skalicloud-sdg-my, cloudsigma-zrh,
cloudsigma-lvs, go2cloud-jhb1, softlayer, ninefold-compute,
hpcloud-compute, rackspace-cloudservers-us, rackspace-cloudservers-uk,
aws-s3, ninefold-storage, cloudonestorage, azureblob, cloudfiles-us,
cloudfiles-uk, hpcloud-objectstorage], apis=[rackspace-cloudidentity,
openstack-keystone, openstack-cinder, rackspace-clouddns, cloudwatch, sqs,
sts, route53, rackspace-cloudloadbalancers, openstack-nova,
openstack-nova-ec2, byon, ec2, cloudservers, vcloud, cloudsigma,
elasticstack, cloudstack, s3, transient, atmos, swift, swift-keystone,
cloudfiles, filesystem, stub]}
at org.jclouds.ContextBuilder.newBuilder(ContextBuilder.java:176)
at test.VcdTest.main(VcdTest.java:24)
On Mon, Nov 4, 2013 at 7:45 PM, Andrew Phillips <[email protected]> wrote:
> I would be most grateful for some guidance in how to go about using
>> jclouds to talk "directly" to VMware's VCD.
>>
>
> You should be able to instantiate a context using the "plain"
> 'vcloud-director' API, setting (at minimum) the "endpoint" property for
> your target installation:
>
> Properties overrides = new Properties();
> overrides.setProperty(..., ...);
> overrides.setProperty(..., ...);
>
> ComputeServiceContext context = ContextBuilder.newBuilder("
> vcloud-director")
> .endpoint("https://your-vloud-ip-or-host/api";)
> .credentials("user@org", "password")
> //.overrides(overrides) - only if needed
> .buildView(ComputeServiceContext.class);
>
> computeService = context.getComputeService();
> // do something with the compute service
>
> You can see some of the properties you can specific via the overrides in
> the API metadata [1]. You'll notice that providers using the vCloud
> Director API, such as Carrenza, effectively do just that in their provider
> metadata [2].
>
> What I don't know, however, is whether or how Whirr allows you to specify
> a context such as this one. One of the Whirr-savvy members of the list will
> hopefully be able to help out here!
>
> ap
>
> [1] https://github.com/jclouds/jclouds-labs/blob/master/
> vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/
> VCloudDirectorApiMetadata.java#L59
> [2] https://github.com/jclouds/jclouds-labs/blob/master/
> carrenza-vcloud-director/src/main/java/org/jclouds/
> carrenza/vcloud/director/CarrenzaVCloudDirectorProviderMetadata.java#L69
>
