Re: vCloud version supported by jCloud

2013-10-25 Thread Andrew Phillips

vCloud 5.1, 5.5


As far as I can see, the vcloud-director labs provider was written to  
support 1.5 [1].


From what I recall, vCDC 5.x versions have backwards-compatible  
support for 1.5, so I think it would certainly be worth trying that  
provider to see what happens. But I don't think any 5.1 or 5.5  
specific features have been implemented.


Any contributions in this area, whether in the form of pull requests  
or simply testing whether the current provider can work against 5.1  
and/or 5.5 are very welcome!


ap

[1]  
https://github.com/jclouds/jclouds-labs/blob/master/vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/VCloudDirectorApiMetadata.java


Re: vCloud version supported by jCloud

2013-10-25 Thread Bk Lau
vCloud 5.1, 5.5


On Fri, Oct 25, 2013 at 4:51 PM, Andrew Phillips  wrote:

> Does anyone know what version(s) of vCloud is currently
>> working with  JCloud 1.6.3?
>>
>
> Which version(s) do you need to support?
>
> ap
>


Re: vCloud version supported by jCloud

2013-10-25 Thread Andrew Phillips

Does anyone know what version(s) of vCloud is currently
working with  JCloud 1.6.3?


Which version(s) do you need to support?

ap


vCloud version supported by jCloud

2013-10-25 Thread Bk Lau
Hi :

Does anyone know what version(s) of vCloud is currently
working with  JCloud 1.6.3?

Thanks,

/BK


Re: vCloud?

2013-09-05 Thread Radek Skokan
I'm just trying the "vcloud-director" from jclouds-labs but failing getting
the ComputeService. I am trying it the way it works for OpenStack from via
the main jclouds lib (plus I also added jclouds-labs to my CP) and

Iterable modules = ImmutableSet.of(new
SLF4JLoggingModule(), new SshjSshClientModule());

ComputeServiceContext computeContext =
ContextBuilder.newBuilder("vcloud-director")
.endpoint("https://172.16.2.152/api";) // perhaps needed to
use Properties overrides.setProperty("vcloud.endpoint", "https:///api";);
.credentials("user1@org1", "Password123")
.modules(modules)
.buildView(ComputeServiceContext.class);
compute = computeContext.getComputeService();

fails with
java.lang.IllegalArgumentException: api {id=vcloud-director, name=vCloud
Director 1.5 API, views=[], endpointName=https endpoint, identityName=User
at Organization (user@org), credentialName=Optional.of(Password),
documentation=http://www.vmware.com/support/pubs/vcd_pubs.html,
api=interface org.jclouds.vcloud.director.v1_5.user.VCloudDirectorApi,
asyncApi=*interface
org.jclouds.vcloud.director.v1_5.user.VCloudDirectorAsyncApi} not wrappable
as org.jclouds.compute.ComputeServiceContext*; context:
org.jclouds.vcloud.director.v1_5.VCloudDirectorContext, views: []

Is it because the vcloud-director provider is not integrated yet to the
ComputeServiceCtx, do I need to access it more directly?

Thanks,
R.


On Wed, Sep 4, 2013 at 10:26 PM, Andrew Phillips  wrote:

> If I understand
>> http://jclouds.incubator.**apache.org/documentation/**
>> userguide/vmware-vcloud/<http://jclouds.incubator.apache.org/documentation/userguide/vmware-vcloud/>,
>>  the
>> error message is OK as neither 1.5 nor 5.1 vCloud versions are supported.
>>
>
> Could you try the vcloud-director API, which is still in labs?
>
> https://github.com/jclouds/**jclouds-labs/tree/master/**vcloud-director<https://github.com/jclouds/jclouds-labs/tree/master/vcloud-director>
> http://search.maven.org/#**search%7Cga%7C1%7Ca%3A%**22vcloud-director%22<http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22vcloud-director%22>
>
> That should support 1.5. There are also some threads about 5.1 work,
> although that seems to be still ongoing:
>
> http://apache.markmail.org/**thread/wv3fiaqy42lwm52h<http://apache.markmail.org/thread/wv3fiaqy42lwm52h>
> https://groups.google.com/**forum/#!msg/jclouds-dev/**
> QaEb9KRoK7o/M8GQJiOr-zwJ<https://groups.google.com/forum/#!msg/jclouds-dev/QaEb9KRoK7o/M8GQJiOr-zwJ>
>
> ap
>


Re: vCloud?

2013-09-05 Thread Aled Sage

Hi Radek,

Yes that's right - the labs:vcloud-director still requires a 
ComputeService implementation unfortunately. It does have all of the 
domain model represented, allowing all the rest api calls + responses to 
be accessed through java.


Aled


On 05/09/2013 16:37, Radek Skokan wrote:
I'm just trying the "vcloud-director" from jclouds-labs but failing 
getting the ComputeService. I am trying it the way it works for 
OpenStack from via the main jclouds lib (plus I also added 
jclouds-labs to my CP) and


Iterable modules = ImmutableSet.of(new 
SLF4JLoggingModule(), new SshjSshClientModule());


ComputeServiceContext computeContext = 
ContextBuilder.newBuilder("vcloud-director")
.endpoint("https://172.16.2.152/api";) // perhaps 
needed to use Properties overrides.setProperty("vcloud.endpoint", 
"https:///api";);

.credentials("user1@org1", "Password123")
.modules(modules)
.buildView(ComputeServiceContext.class);
compute = computeContext.getComputeService();

fails with
java.lang.IllegalArgumentException: api {id=vcloud-director, 
name=vCloud Director 1.5 API, views=[], endpointName=https endpoint, 
identityName=User at Organization (user@org), 
credentialName=Optional.of(Password), 
documentation=http://www.vmware.com/support/pubs/vcd_pubs.html, 
api=interface org.jclouds.vcloud.director.v1_5.user.VCloudDirectorApi, 
asyncApi=*interface 
org.jclouds.vcloud.director.v1_5.user.VCloudDirectorAsyncApi} not 
wrappable as org.jclouds.compute.ComputeServiceContext*; context: 
org.jclouds.vcloud.director.v1_5.VCloudDirectorContext, views: []


Is it because the vcloud-director provider is not integrated yet to 
the ComputeServiceCtx, do I need to access it more directly?


Thanks,
R.


On Wed, Sep 4, 2013 at 10:26 PM, Andrew Phillips <mailto:andr...@apache.org>> wrote:


If I understand

http://jclouds.incubator.apache.org/documentation/userguide/vmware-vcloud/,
 the
error message is OK as neither 1.5 nor 5.1 vCloud versions are
supported.


Could you try the vcloud-director API, which is still in labs?

https://github.com/jclouds/jclouds-labs/tree/master/vcloud-director
http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22vcloud-director%22

That should support 1.5. There are also some threads about 5.1
work, although that seems to be still ongoing:

http://apache.markmail.org/thread/wv3fiaqy42lwm52h
https://groups.google.com/forum/#!msg/jclouds-dev/QaEb9KRoK7o/M8GQJiOr-zwJ

<https://groups.google.com/forum/#%21msg/jclouds-dev/QaEb9KRoK7o/M8GQJiOr-zwJ>

ap






Re: vCloud?

2013-09-04 Thread Andrew Phillips

If I understand
http://jclouds.incubator.apache.org/documentation/userguide/vmware-vcloud/,   
the

error message is OK as neither 1.5 nor 5.1 vCloud versions are supported.


Could you try the vcloud-director API, which is still in labs?

https://github.com/jclouds/jclouds-labs/tree/master/vcloud-director
http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22vcloud-director%22

That should support 1.5. There are also some threads about 5.1 work,  
although that seems to be still ongoing:


http://apache.markmail.org/thread/wv3fiaqy42lwm52h
https://groups.google.com/forum/#!msg/jclouds-dev/QaEb9KRoK7o/M8GQJiOr-zwJ

ap


vCloud?

2013-09-04 Thread Radek Skokan
Hi guys,

I am trying to connect to VM Ware vCloud installed in my env., the current
version (5.1) and when creating the compute context I am getting

java.lang.IllegalStateException: version 1.0 not present in: {1.5=
https://172.16.2.152/api/sessions, 5.1=https://172.16.2.152/api/sessions}

If I understand
http://jclouds.incubator.apache.org/documentation/userguide/vmware-vcloud/, the
error message is OK as neither 1.5 nor 5.1 vCloud versions are supported.

This leads me to a non-technical question: does it pays off to use jclouds
for interfacing with vCloud (plus possibly OpenStack)? Is there anybody
using it for "pure" VM Ware vCloud?

Thanks,
Radek


Re: vmware vcloud 5.1 support

2013-08-11 Thread Andrea Turli
Hi Deepak,

you need to checkout https://github.com/jclouds/jclouds-labs as
vcloud-director is still under labs.
This is the documentation available on the official jclouds website
http://jclouds.incubator.apache.org/documentation/userguide/vmware-vcloud-director/
This version supports vcloud-director 1.5. I think the main issue to
support 5.1 is to have a stable free vcloud-director 5.1 env where to live
test the provider.

Hope this helps,
Andrea


On Mon, Aug 12, 2013 at 6:34 AM, Deepak Gupta  wrote:

> Hi, I have just started using jclouds and not able to see any information
> regarding vmware vcloud director 5.1 support . Can somebody pls. confirm
> that this is supported and if no then has anybody already tried it and what
> changes are required to get this supported, as I have taken jclouds from
> GIT but it is giving error like vcloud is not in the list of providers .
>
> Regards,
> Deepak
>


vmware vcloud 5.1 support

2013-08-11 Thread Deepak Gupta
Hi, I have just started using jclouds and not able to see any information
regarding vmware vcloud director 5.1 support . Can somebody pls. confirm
that this is supported and if no then has anybody already tried it and what
changes are required to get this supported, as I have taken jclouds from
GIT but it is giving error like vcloud is not in the list of providers .

Regards,
Deepak


VMware Vcloud 5.1 support

2013-08-11 Thread Deepak Gupta
Hi, I have just started using jclouds and not able to see any information
regarding vmware vcloud director 5.1 support . Can somebody pls. confirm
that this is supported and if no then has anybody already tried it and what
changes are required to get this supported, as I have taken jclouds from
GIT but it is giving error like vcloud is not in the list of providers .

Regards,
Deepak