You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Luca Martini <lm...@cisco.com> on 2014/01/29 18:42:28 UTC
stratos using vmware though jclouds ?
Hello!
Did anybody try to a vmware provider in the stratos/jclouds configuration ?
I know this worked a long time ago , but does it still work ?
Thanks.
Luca
Re: stratos using vmware though jclouds ?
Posted by Melan Nimesh <me...@gmail.com>.
Hi Vinod,
Sorry for the late reply. I am working on to create jClouds branch under '
dependencies' as we discussed on "Patching jClouds to get vcloud iaas
provider work with vcloud API 1.5 or later" mail thread. I will update the
thread as progress.
Thanks,
Melan
On Wed, Feb 26, 2014 at 10:23 AM, Vinod Kamble <vi...@icloud.com>wrote:
> Hi Melan,
> Any updates on the jcloud patch ? Is it available in the master?
>
> Thanks,
> Vinod.
>
> On 21-Feb-2014, at 3:18 pm, Melan Nimesh <me...@gmail.com> wrote:
>
> Hi Vinod,
>
> I used following [1] configuration to test with vcloud iass provider
> (vcloud API 1.5). btw, we need to do some changes at jClouds level to get
> it work with vcloud API 1.5 or later, I will start a separate thread in
> this.
>
> [1]
> <iaasProvider type="vcloud" name="vCloud specific details">
>
> <className>org.apache.stratos.cloud.controller.iaases.VCloudIaas</className>
> <provider>vcloud</provider>
> <identity svns:secretAlias="elastic.scaler.vcloud.identity">user@org
> </identity>
> <credential
> svns:secretAlias="elastic.scaler.vcloud.credential">password</credential>
> <scaleUpOrder>1</scaleUpOrder>
> <scaleDownOrder>2</scaleDownOrder>
> <property name="jclouds.endpoint" value="https://<PROVIDER_URL>/api" />
> <property name="jclouds.vcloud.version.schema" value="1.5" />
> <property name="autoAssignIp" value="true" />
> <property name="loginUser" value="user" />
> <property name="loginPassword" value="password" />
> <property name="jclouds.api-version" value="1.5" />
> </iaasProvider>
>
> Thanks,
> Melan
>
>
>
>
>
> Thanks,
> Melan
>
>
> On Fri, Feb 21, 2014 at 10:43 AM, Vinod Kamble <vi...@icloud.com>wrote:
>
>> Hi Melan,
>> Can you provide your cloud-configuration.xml with vcloud iaas provider
>> configuration?
>> Thanks,
>> Vinod.
>>
>> On 13-Feb-2014, at 4:16 pm, Melan Nimesh <me...@gmail.com> wrote:
>>
>> Hi Devs,
>>
>> I was able get rid most Jclouds related issue and was able to test
>> basic functionality of Stratos with a vCloud provider which supports API
>> level 1.5. Thanks Nirmal and Udara for the given support. I will continue
>> further testing.
>>
>> Thanks,
>> Melan
>>
>>
>> On Tue, Feb 11, 2014 at 9:52 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Me too have experienced a similar issue. Headers are changed in vcloud
>>> versions.
>>>
>>>
>>> On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com>wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> I am testing vCloud integrating with a vCloud provider which supports
>>>> only for 1.5, 5.1 and 5.5 versions and I am getting following error [1]
>>>> when trying to deploy a cartridge definition. I am using latest packs (JCloud
>>>> 1.7) from master branch with JCloud patches provided by Nirmal
>>>>
>>>> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud
>>>> expecting * "**application/vnd.vmware.vcloud.orgList+xml" *for a
>>>> session request which is default for VCloud API 1.0. but API 1.5 or
>>>> later sending *"application/vnd.vmware.vcloud.session+xml**"* type of
>>>> object. I can try to modify VCloudLoginApi to support latest type, but
>>>> then we will lost API 1.0 support,
>>>>
>>>> is there any better way to do this? does JCloud supports VCloud API
>>>> 1.5 or later?
>>>>
>>>> Thanks,
>>>> Melan
>>>>
>>>>
>>>> [1]
>>>> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >>
>>>> POST https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>>>> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5
>>>> {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>>>> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw==
>>>> {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - <<
>>>> HTTP/1.1 406 Not Acceptable {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>>>> Vary: Accept-Encoding {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>>>> Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>>>> x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc=
>>>> {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>>>> Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>>>> Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure;
>>>> Path=/ {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>>>> Connection: close {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>>>> Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5
>>>> {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>>>> Content-Length: 362 {jclouds.headers}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - <<
>>>> "<?xml version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - <<
>>>> "<Error xmlns="http://www.vmware.com/vcloud/v1.5"
>>>> minorErrorCode="NOT_ACCEPTABLE" message="The request accept header is
>>>> invalid." majorErrorCode="406" xmlns:xsi="
>>>> http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
>>>> http://www.vmware.com/vcloud/v1.5
>>>> http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]"
>>>> {jclouds.wire}
>>>> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR
>>>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to
>>>> build the jclouds object for iaas of type: vcloud
>>>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
>>>> org.jclouds.vcloud.VCloudResponseException: request POST
>>>> https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code
>>>> 406, error: [majorErrorCode=406, message=The request accept header is
>>>> invalid., minorErrorCode=UNRECOGNIZED, stackTrace=null,
>>>> vendorSpecificErrorCode=NOT_ACCEPTABLE]
>>>> at
>>>> org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
>>>> at
>>>> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
>>>> at
>>>> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
>>>> at
>>>> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
>>>> at
>>>> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
>>>> at
>>>> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>>>>
>>>> [2]
>>>> public interface VCloudLoginApi extends Closeable {
>>>>
>>>> /**
>>>> * This request returns a token to use in subsequent requests. After
>>>> 30 minutes of inactivity,
>>>> * the token expires and you have to request a new token with this
>>>> call.
>>>> */
>>>> @POST
>>>> @ResponseParser(ParseLoginResponseFromHeaders.class)
>>>> @Consumes(VCloudMediaType.ORGLIST_XML)
>>>> VCloudSession login();
>>>> }
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <nirmal070125@gmail.com
>>>> > wrote:
>>>>
>>>>> Hi Melan,
>>>>>
>>>>> Yes, I've patch jClouds vCloud, let me give the patched jar, so that
>>>>> you can carry on testing.
>>>>>
>>>>> vCloud IaaS provider can be found in the Cloud Controller component.
>>>>>
>>>>>
>>>>> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com>wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> I started testing the Stratos latest packs with vcloud IaaS
>>>>>> and currently I am at initial step. I will update the thread with the
>>>>>> progress.
>>>>>>
>>>>>> I have few questions..
>>>>>> - Do we have any vcloud related jcloud patches?
>>>>>> - Where can I found sample iaasProvider configuration for vcloud ?
>>>>>>
>>>>>> Thanks,
>>>>>> Melan
>>>>>>
>>>>>>
>>>>>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com>wrote:
>>>>>>
>>>>>>> Yes Luca it should work. However we haven't tested with S4 yet.
>>>>>>>
>>>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Melan Nimesh Jayasingha
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Nirmal
>>>>>
>>>>> Nirmal Fernando.
>>>>> PPMC Member & Committer of Apache Stratos,
>>>>> Senior Software Engineer, WSO2 Inc.
>>>>>
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Melan Nimesh Jayasingha
>>>>
>>>
>>>
>>>
>>> --
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>>
>>
>>
>
>
> --
> Melan Nimesh Jayasingha
>
>
>
--
Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Vinod Kamble <vi...@icloud.com>.
Hi Melan,
Any updates on the jcloud patch ? Is it available in the master?
Thanks,
Vinod.
On 21-Feb-2014, at 3:18 pm, Melan Nimesh <me...@gmail.com> wrote:
> Hi Vinod,
>
> I used following [1] configuration to test with vcloud iass provider (vcloud API 1.5). btw, we need to do some changes at jClouds level to get it work with vcloud API 1.5 or later, I will start a separate thread in this.
>
> [1]
> <iaasProvider type="vcloud" name="vCloud specific details">
> <className>org.apache.stratos.cloud.controller.iaases.VCloudIaas</className>
> <provider>vcloud</provider>
> <identity svns:secretAlias="elastic.scaler.vcloud.identity">user@org</identity>
> <credential svns:secretAlias="elastic.scaler.vcloud.credential">password</credential>
> <scaleUpOrder>1</scaleUpOrder>
> <scaleDownOrder>2</scaleDownOrder>
> <property name="jclouds.endpoint" value="https://<PROVIDER_URL>/api" />
> <property name="jclouds.vcloud.version.schema" value="1.5" />
> <property name="autoAssignIp" value="true" />
> <property name="loginUser" value="user" />
> <property name="loginPassword" value="password" />
> <property name="jclouds.api-version" value="1.5" />
> </iaasProvider>
>
> Thanks,
> Melan
>
>
>
>
>
> Thanks,
> Melan
>
>
> On Fri, Feb 21, 2014 at 10:43 AM, Vinod Kamble <vi...@icloud.com> wrote:
> Hi Melan,
> Can you provide your cloud-configuration.xml with vcloud iaas provider configuration?
> Thanks,
> Vinod.
>
> On 13-Feb-2014, at 4:16 pm, Melan Nimesh <me...@gmail.com> wrote:
>
>> Hi Devs,
>>
>> I was able get rid most Jclouds related issue and was able to test basic functionality of Stratos with a vCloud provider which supports API level 1.5. Thanks Nirmal and Udara for the given support. I will continue further testing.
>>
>> Thanks,
>> Melan
>>
>>
>> On Tue, Feb 11, 2014 at 9:52 AM, Udara Liyanage <ud...@wso2.com> wrote:
>> Me too have experienced a similar issue. Headers are changed in vcloud versions.
>>
>>
>> On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com> wrote:
>> Hi Devs,
>>
>> I am testing vCloud integrating with a vCloud provider which supports only for 1.5, 5.1 and 5.5 versions and I am getting following error [1] when trying to deploy a cartridge definition. I am using latest packs (JCloud 1.7) from master branch with JCloud patches provided by Nirmal
>>
>> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud expecting "application/vnd.vmware.vcloud.orgList+xml" for a session request which is default for VCloud API 1.0. but API 1.5 or later sending "application/vnd.vmware.vcloud.session+xml" type of object. I can try to modify VCloudLoginApi to support latest type, but then we will lost API 1.0 support,
>>
>> is there any better way to do this? does JCloud supports VCloud API 1.5 or later?
>>
>> Thanks,
>> Melan
>>
>>
>> [1]
>> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >> POST https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5 {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw== {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - << HTTP/1.1 406 Not Acceptable {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - << Vary: Accept-Encoding {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - << Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - << x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc= {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - << Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - << Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure; Path=/ {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - << Connection: close {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - << Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5 {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - << Content-Length: 362 {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - << "<?xml version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
>> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - << "<Error xmlns="http://www.vmware.com/vcloud/v1.5" minorErrorCode="NOT_ACCEPTABLE" message="The request accept header is invalid." majorErrorCode="406" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/v1.5 http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]" {jclouds.wire}
>> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to build the jclouds object for iaas of type: vcloud {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
>> org.jclouds.vcloud.VCloudResponseException: request POST https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code 406, error: [majorErrorCode=406, message=The request accept header is invalid., minorErrorCode=UNRECOGNIZED, stackTrace=null, vendorSpecificErrorCode=NOT_ACCEPTABLE]
>> at org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
>> at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
>> at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
>> at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
>> at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
>> at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>>
>> [2]
>> public interface VCloudLoginApi extends Closeable {
>>
>> /**
>> * This request returns a token to use in subsequent requests. After 30 minutes of inactivity,
>> * the token expires and you have to request a new token with this call.
>> */
>> @POST
>> @ResponseParser(ParseLoginResponseFromHeaders.class)
>> @Consumes(VCloudMediaType.ORGLIST_XML)
>> VCloudSession login();
>> }
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com> wrote:
>> Hi Melan,
>>
>> Yes, I've patch jClouds vCloud, let me give the patched jar, so that you can carry on testing.
>>
>> vCloud IaaS provider can be found in the Cloud Controller component.
>>
>>
>> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com> wrote:
>> Hi Devs,
>>
>> I started testing the Stratos latest packs with vcloud IaaS and currently I am at initial step. I will update the thread with the progress.
>>
>> I have few questions..
>> - Do we have any vcloud related jcloud patches?
>> - Where can I found sample iaasProvider configuration for vcloud ?
>>
>> Thanks,
>> Melan
>>
>>
>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com> wrote:
>> Yes Luca it should work. However we haven't tested with S4 yet.
>>
>> Touched, not typed. Erroneous words are a feature, not a typo.
>>
>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>>
>>
>>
>> --
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>
>
>
>
> --
> Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Melan Nimesh <me...@gmail.com>.
Hi Vinod,
I used following [1] configuration to test with vcloud iass provider
(vcloud API 1.5). btw, we need to do some changes at jClouds level to get
it work with vcloud API 1.5 or later, I will start a separate thread in
this.
[1]
<iaasProvider type="vcloud" name="vCloud specific details">
<className>org.apache.stratos.cloud.controller.iaases.VCloudIaas</className>
<provider>vcloud</provider>
<identity svns:secretAlias="elastic.scaler.vcloud.identity">user@org
</identity>
<credential
svns:secretAlias="elastic.scaler.vcloud.credential">password</credential>
<scaleUpOrder>1</scaleUpOrder>
<scaleDownOrder>2</scaleDownOrder>
<property name="jclouds.endpoint" value="https://<PROVIDER_URL>/api" />
<property name="jclouds.vcloud.version.schema" value="1.5" />
<property name="autoAssignIp" value="true" />
<property name="loginUser" value="user" />
<property name="loginPassword" value="password" />
<property name="jclouds.api-version" value="1.5" />
</iaasProvider>
Thanks,
Melan
Thanks,
Melan
On Fri, Feb 21, 2014 at 10:43 AM, Vinod Kamble <vi...@icloud.com>wrote:
> Hi Melan,
> Can you provide your cloud-configuration.xml with vcloud iaas provider
> configuration?
> Thanks,
> Vinod.
>
> On 13-Feb-2014, at 4:16 pm, Melan Nimesh <me...@gmail.com> wrote:
>
> Hi Devs,
>
> I was able get rid most Jclouds related issue and was able to test
> basic functionality of Stratos with a vCloud provider which supports API
> level 1.5. Thanks Nirmal and Udara for the given support. I will continue
> further testing.
>
> Thanks,
> Melan
>
>
> On Tue, Feb 11, 2014 at 9:52 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Me too have experienced a similar issue. Headers are changed in vcloud
>> versions.
>>
>>
>> On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com>wrote:
>>
>>> Hi Devs,
>>>
>>> I am testing vCloud integrating with a vCloud provider which supports
>>> only for 1.5, 5.1 and 5.5 versions and I am getting following error [1]
>>> when trying to deploy a cartridge definition. I am using latest packs (JCloud
>>> 1.7) from master branch with JCloud patches provided by Nirmal
>>>
>>> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud
>>> expecting * "**application/vnd.vmware.vcloud.orgList+xml" *for a
>>> session request which is default for VCloud API 1.0. but API 1.5 or
>>> later sending *"application/vnd.vmware.vcloud.session+xml**"* type of
>>> object. I can try to modify VCloudLoginApi to support latest type, but
>>> then we will lost API 1.0 support,
>>>
>>> is there any better way to do this? does JCloud supports VCloud API 1.5
>>> or later?
>>>
>>> Thanks,
>>> Melan
>>>
>>>
>>> [1]
>>> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >>
>>> POST https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>>> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>>> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw==
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - <<
>>> HTTP/1.1 406 Not Acceptable {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>>> Vary: Accept-Encoding {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>>> Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>>> x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc=
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>>> Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>>> Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure;
>>> Path=/ {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>>> Connection: close {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>>> Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>>> Content-Length: 362 {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - <<
>>> "<?xml version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
>>> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - <<
>>> "<Error xmlns="http://www.vmware.com/vcloud/v1.5"
>>> minorErrorCode="NOT_ACCEPTABLE" message="The request accept header is
>>> invalid." majorErrorCode="406" xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
>>> http://www.vmware.com/vcloud/v1.5
>>> http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]"
>>> {jclouds.wire}
>>> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR
>>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to
>>> build the jclouds object for iaas of type: vcloud
>>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
>>> org.jclouds.vcloud.VCloudResponseException: request POST
>>> https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code
>>> 406, error: [majorErrorCode=406, message=The request accept header is
>>> invalid., minorErrorCode=UNRECOGNIZED, stackTrace=null,
>>> vendorSpecificErrorCode=NOT_ACCEPTABLE]
>>> at
>>> org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
>>> at
>>> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
>>> at
>>> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
>>> at
>>> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
>>> at
>>> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
>>> at
>>> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>>>
>>> [2]
>>> public interface VCloudLoginApi extends Closeable {
>>>
>>> /**
>>> * This request returns a token to use in subsequent requests. After
>>> 30 minutes of inactivity,
>>> * the token expires and you have to request a new token with this
>>> call.
>>> */
>>> @POST
>>> @ResponseParser(ParseLoginResponseFromHeaders.class)
>>> @Consumes(VCloudMediaType.ORGLIST_XML)
>>> VCloudSession login();
>>> }
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>>
>>>> Hi Melan,
>>>>
>>>> Yes, I've patch jClouds vCloud, let me give the patched jar, so that
>>>> you can carry on testing.
>>>>
>>>> vCloud IaaS provider can be found in the Cloud Controller component.
>>>>
>>>>
>>>> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com>wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> I started testing the Stratos latest packs with vcloud IaaS
>>>>> and currently I am at initial step. I will update the thread with the
>>>>> progress.
>>>>>
>>>>> I have few questions..
>>>>> - Do we have any vcloud related jcloud patches?
>>>>> - Where can I found sample iaasProvider configuration for vcloud ?
>>>>>
>>>>> Thanks,
>>>>> Melan
>>>>>
>>>>>
>>>>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com>wrote:
>>>>>
>>>>>> Yes Luca it should work. However we haven't tested with S4 yet.
>>>>>>
>>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Melan Nimesh Jayasingha
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Melan Nimesh Jayasingha
>>>
>>
>>
>>
>> --
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
>
> --
> Melan Nimesh Jayasingha
>
>
>
--
Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Vinod Kamble <vi...@icloud.com>.
Hi Melan,
Can you provide your cloud-configuration.xml with vcloud iaas provider configuration?
Thanks,
Vinod.
On 13-Feb-2014, at 4:16 pm, Melan Nimesh <me...@gmail.com> wrote:
> Hi Devs,
>
> I was able get rid most Jclouds related issue and was able to test basic functionality of Stratos with a vCloud provider which supports API level 1.5. Thanks Nirmal and Udara for the given support. I will continue further testing.
>
> Thanks,
> Melan
>
>
> On Tue, Feb 11, 2014 at 9:52 AM, Udara Liyanage <ud...@wso2.com> wrote:
> Me too have experienced a similar issue. Headers are changed in vcloud versions.
>
>
> On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com> wrote:
> Hi Devs,
>
> I am testing vCloud integrating with a vCloud provider which supports only for 1.5, 5.1 and 5.5 versions and I am getting following error [1] when trying to deploy a cartridge definition. I am using latest packs (JCloud 1.7) from master branch with JCloud patches provided by Nirmal
>
> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud expecting "application/vnd.vmware.vcloud.orgList+xml" for a session request which is default for VCloud API 1.0. but API 1.5 or later sending "application/vnd.vmware.vcloud.session+xml" type of object. I can try to modify VCloudLoginApi to support latest type, but then we will lost API 1.0 support,
>
> is there any better way to do this? does JCloud supports VCloud API 1.5 or later?
>
> Thanks,
> Melan
>
>
> [1]
> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >> POST https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5 {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw== {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - << HTTP/1.1 406 Not Acceptable {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - << Vary: Accept-Encoding {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - << Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - << x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc= {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - << Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - << Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure; Path=/ {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - << Connection: close {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - << Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5 {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - << Content-Length: 362 {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - << "<?xml version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - << "<Error xmlns="http://www.vmware.com/vcloud/v1.5" minorErrorCode="NOT_ACCEPTABLE" message="The request accept header is invalid." majorErrorCode="406" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/vcloud/v1.5 http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]" {jclouds.wire}
> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to build the jclouds object for iaas of type: vcloud {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
> org.jclouds.vcloud.VCloudResponseException: request POST https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code 406, error: [majorErrorCode=406, message=The request accept header is invalid., minorErrorCode=UNRECOGNIZED, stackTrace=null, vendorSpecificErrorCode=NOT_ACCEPTABLE]
> at org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
> at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
> at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
> at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
> at org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
> at org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>
> [2]
> public interface VCloudLoginApi extends Closeable {
>
> /**
> * This request returns a token to use in subsequent requests. After 30 minutes of inactivity,
> * the token expires and you have to request a new token with this call.
> */
> @POST
> @ResponseParser(ParseLoginResponseFromHeaders.class)
> @Consumes(VCloudMediaType.ORGLIST_XML)
> VCloudSession login();
> }
>
>
>
>
>
>
>
> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> Hi Melan,
>
> Yes, I've patch jClouds vCloud, let me give the patched jar, so that you can carry on testing.
>
> vCloud IaaS provider can be found in the Cloud Controller component.
>
>
> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com> wrote:
> Hi Devs,
>
> I started testing the Stratos latest packs with vcloud IaaS and currently I am at initial step. I will update the thread with the progress.
>
> I have few questions..
> - Do we have any vcloud related jcloud patches?
> - Where can I found sample iaasProvider configuration for vcloud ?
>
> Thanks,
> Melan
>
>
> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com> wrote:
> Yes Luca it should work. However we haven't tested with S4 yet.
>
> Touched, not typed. Erroneous words are a feature, not a typo.
>
>
>
>
> --
> Melan Nimesh Jayasingha
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> --
> Melan Nimesh Jayasingha
>
>
>
> --
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
>
>
> --
> Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Nirmal Fernando <ni...@gmail.com>.
Great progress Melan! Keep the list posted.
On Thu, Feb 13, 2014 at 4:16 PM, Melan Nimesh <me...@gmail.com> wrote:
> Hi Devs,
>
> I was able get rid most Jclouds related issue and was able to test
> basic functionality of Stratos with a vCloud provider which supports API
> level 1.5. Thanks Nirmal and Udara for the given support. I will continue
> further testing.
>
> Thanks,
> Melan
>
>
> On Tue, Feb 11, 2014 at 9:52 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Me too have experienced a similar issue. Headers are changed in vcloud
>> versions.
>>
>>
>> On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com>wrote:
>>
>>> Hi Devs,
>>>
>>> I am testing vCloud integrating with a vCloud provider which supports
>>> only for 1.5, 5.1 and 5.5 versions and I am getting following error [1]
>>> when trying to deploy a cartridge definition. I am using latest packs (JCloud
>>> 1.7) from master branch with JCloud patches provided by Nirmal
>>>
>>> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud
>>> expecting * "**application/vnd.vmware.vcloud.orgList+xml" *for a
>>> session request which is default for VCloud API 1.0. but API 1.5 or
>>> later sending *"application/vnd.vmware.vcloud.session+xml**"* type of
>>> object. I can try to modify VCloudLoginApi to support latest type, but
>>> then we will lost API 1.0 support,
>>>
>>> is there any better way to do this? does JCloud supports VCloud API 1.5
>>> or later?
>>>
>>> Thanks,
>>> Melan
>>>
>>>
>>> [1]
>>> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >>
>>> POST https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>>> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>>> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw==
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - <<
>>> HTTP/1.1 406 Not Acceptable {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>>> Vary: Accept-Encoding {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>>> Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>>> x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc=
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>>> Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>>> Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure;
>>> Path=/ {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>>> Connection: close {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>>> Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5
>>> {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>>> Content-Length: 362 {jclouds.headers}
>>> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - <<
>>> "<?xml version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
>>> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - <<
>>> "<Error xmlns="http://www.vmware.com/vcloud/v1.5"
>>> minorErrorCode="NOT_ACCEPTABLE" message="The request accept header is
>>> invalid." majorErrorCode="406" xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
>>> http://www.vmware.com/vcloud/v1.5
>>> http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]"
>>> {jclouds.wire}
>>> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR
>>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to
>>> build the jclouds object for iaas of type: vcloud
>>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
>>> org.jclouds.vcloud.VCloudResponseException: request POST
>>> https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code
>>> 406, error: [majorErrorCode=406, message=The request accept header is
>>> invalid., minorErrorCode=UNRECOGNIZED, stackTrace=null,
>>> vendorSpecificErrorCode=NOT_ACCEPTABLE]
>>> at
>>> org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
>>> at
>>> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
>>> at
>>> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
>>> at
>>> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
>>> at
>>> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
>>> at
>>> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>>>
>>> [2]
>>> public interface VCloudLoginApi extends Closeable {
>>>
>>> /**
>>> * This request returns a token to use in subsequent requests. After
>>> 30 minutes of inactivity,
>>> * the token expires and you have to request a new token with this
>>> call.
>>> */
>>> @POST
>>> @ResponseParser(ParseLoginResponseFromHeaders.class)
>>> @Consumes(VCloudMediaType.ORGLIST_XML)
>>> VCloudSession login();
>>> }
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>>
>>>> Hi Melan,
>>>>
>>>> Yes, I've patch jClouds vCloud, let me give the patched jar, so that
>>>> you can carry on testing.
>>>>
>>>> vCloud IaaS provider can be found in the Cloud Controller component.
>>>>
>>>>
>>>> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com>wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> I started testing the Stratos latest packs with vcloud IaaS
>>>>> and currently I am at initial step. I will update the thread with the
>>>>> progress.
>>>>>
>>>>> I have few questions..
>>>>> - Do we have any vcloud related jcloud patches?
>>>>> - Where can I found sample iaasProvider configuration for vcloud ?
>>>>>
>>>>> Thanks,
>>>>> Melan
>>>>>
>>>>>
>>>>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com>wrote:
>>>>>
>>>>>> Yes Luca it should work. However we haven't tested with S4 yet.
>>>>>>
>>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Melan Nimesh Jayasingha
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Nirmal
>>>>
>>>> Nirmal Fernando.
>>>> PPMC Member & Committer of Apache Stratos,
>>>> Senior Software Engineer, WSO2 Inc.
>>>>
>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>
>>>
>>>
>>>
>>> --
>>> Melan Nimesh Jayasingha
>>>
>>
>>
>>
>> --
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
>
> --
> Melan Nimesh Jayasingha
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: stratos using vmware though jclouds ?
Posted by Melan Nimesh <me...@gmail.com>.
Hi Devs,
I was able get rid most Jclouds related issue and was able to test
basic functionality of Stratos with a vCloud provider which supports API
level 1.5. Thanks Nirmal and Udara for the given support. I will continue
further testing.
Thanks,
Melan
On Tue, Feb 11, 2014 at 9:52 AM, Udara Liyanage <ud...@wso2.com> wrote:
> Me too have experienced a similar issue. Headers are changed in vcloud
> versions.
>
>
> On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com> wrote:
>
>> Hi Devs,
>>
>> I am testing vCloud integrating with a vCloud provider which supports
>> only for 1.5, 5.1 and 5.5 versions and I am getting following error [1]
>> when trying to deploy a cartridge definition. I am using latest packs (JCloud
>> 1.7) from master branch with JCloud patches provided by Nirmal
>>
>> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud
>> expecting * "**application/vnd.vmware.vcloud.orgList+xml" *for a session request
>> which is default for VCloud API 1.0. but API 1.5 or later sending
>> *"application/vnd.vmware.vcloud.session+xml**"* type of object. I can
>> try to modify VCloudLoginApi to support latest type, but then we will
>> lost API 1.0 support,
>>
>> is there any better way to do this? does JCloud supports VCloud API 1.5
>> or later?
>>
>> Thanks,
>> Melan
>>
>>
>> [1]
>> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >> POST
>> https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5
>> {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
>> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw==
>> {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - <<
>> HTTP/1.1 406 Not Acceptable {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>> Vary: Accept-Encoding {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
>> Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>> x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc=
>> {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
>> Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>> Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure;
>> Path=/ {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
>> Connection: close {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>> Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5
>> {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
>> Content-Length: 362 {jclouds.headers}
>> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - << "<?xml
>> version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
>> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - <<
>> "<Error xmlns="http://www.vmware.com/vcloud/v1.5"
>> minorErrorCode="NOT_ACCEPTABLE" message="The request accept header is
>> invalid." majorErrorCode="406" xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
>> http://www.vmware.com/vcloud/v1.5
>> http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]"
>> {jclouds.wire}
>> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR
>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to
>> build the jclouds object for iaas of type: vcloud
>> {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
>> org.jclouds.vcloud.VCloudResponseException: request POST
>> https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code 406,
>> error: [majorErrorCode=406, message=The request accept header is invalid.,
>> minorErrorCode=UNRECOGNIZED, stackTrace=null,
>> vendorSpecificErrorCode=NOT_ACCEPTABLE]
>> at
>> org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
>> at
>> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
>> at
>> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
>> at
>> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
>> at
>> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
>> at
>> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>>
>> [2]
>> public interface VCloudLoginApi extends Closeable {
>>
>> /**
>> * This request returns a token to use in subsequent requests. After
>> 30 minutes of inactivity,
>> * the token expires and you have to request a new token with this
>> call.
>> */
>> @POST
>> @ResponseParser(ParseLoginResponseFromHeaders.class)
>> @Consumes(VCloudMediaType.ORGLIST_XML)
>> VCloudSession login();
>> }
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>>
>>> Hi Melan,
>>>
>>> Yes, I've patch jClouds vCloud, let me give the patched jar, so that you
>>> can carry on testing.
>>>
>>> vCloud IaaS provider can be found in the Cloud Controller component.
>>>
>>>
>>> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com>wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> I started testing the Stratos latest packs with vcloud IaaS
>>>> and currently I am at initial step. I will update the thread with the
>>>> progress.
>>>>
>>>> I have few questions..
>>>> - Do we have any vcloud related jcloud patches?
>>>> - Where can I found sample iaasProvider configuration for vcloud ?
>>>>
>>>> Thanks,
>>>> Melan
>>>>
>>>>
>>>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com>wrote:
>>>>
>>>>> Yes Luca it should work. However we haven't tested with S4 yet.
>>>>>
>>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Melan Nimesh Jayasingha
>>>>
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>>
>
>
>
> --
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
--
Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Udara Liyanage <ud...@wso2.com>.
Me too have experienced a similar issue. Headers are changed in vcloud
versions.
On Mon, Feb 10, 2014 at 5:04 AM, Melan Nimesh <me...@gmail.com> wrote:
> Hi Devs,
>
> I am testing vCloud integrating with a vCloud provider which supports
> only for 1.5, 5.1 and 5.5 versions and I am getting following error [1]
> when trying to deploy a cartridge definition. I am using latest packs (JCloud
> 1.7) from master branch with JCloud patches provided by Nirmal
>
> I went through JCloud VCloudLoginApi's code [2] and noticed jCloud
> expecting * "**application/vnd.vmware.vcloud.orgList+xml" *for a session request
> which is default for VCloud API 1.0. but API 1.5 or later sending
> *"application/vnd.vmware.vcloud.session+xml**"* type of object. I can try
> to modify VCloudLoginApi to support latest type, but then we will lost
> API 1.0 support,
>
> is there any better way to do this? does JCloud supports VCloud API 1.5
> or later?
>
> Thanks,
> Melan
>
>
> [1]
> ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >> POST
> https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
> Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5
> {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
> Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw==
> {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - <<
> HTTP/1.1 406 Not Acceptable {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
> Vary: Accept-Encoding {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - <<
> Date: Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
> x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc=
> {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
> Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
> Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure;
> Path=/ {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
> Connection: close {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
> Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5
> {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
> Content-Length: 362 {jclouds.headers}
> TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - << "<?xml
> version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
> TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - << "<Error
> xmlns="http://www.vmware.com/vcloud/v1.5" minorErrorCode="NOT_ACCEPTABLE"
> message="The request accept header is invalid." majorErrorCode="406"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
> http://www.vmware.com/vcloud/v1.5
> http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]"
> {jclouds.wire}
> TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR
> {org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to
> build the jclouds object for iaas of type: vcloud
> {org.apache.stratos.cloud.controller.util.CloudControllerUtil}
> org.jclouds.vcloud.VCloudResponseException: request POST
> https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code 406,
> error: [majorErrorCode=406, message=The request accept header is invalid.,
> minorErrorCode=UNRECOGNIZED, stackTrace=null,
> vendorSpecificErrorCode=NOT_ACCEPTABLE]
> at
> org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
> at
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
>
> [2]
> public interface VCloudLoginApi extends Closeable {
>
> /**
> * This request returns a token to use in subsequent requests. After 30
> minutes of inactivity,
> * the token expires and you have to request a new token with this call.
> */
> @POST
> @ResponseParser(ParseLoginResponseFromHeaders.class)
> @Consumes(VCloudMediaType.ORGLIST_XML)
> VCloudSession login();
> }
>
>
>
>
>
>
>
> On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi Melan,
>>
>> Yes, I've patch jClouds vCloud, let me give the patched jar, so that you
>> can carry on testing.
>>
>> vCloud IaaS provider can be found in the Cloud Controller component.
>>
>>
>> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com>wrote:
>>
>>> Hi Devs,
>>>
>>> I started testing the Stratos latest packs with vcloud IaaS
>>> and currently I am at initial step. I will update the thread with the
>>> progress.
>>>
>>> I have few questions..
>>> - Do we have any vcloud related jcloud patches?
>>> - Where can I found sample iaasProvider configuration for vcloud ?
>>>
>>> Thanks,
>>> Melan
>>>
>>>
>>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>> Yes Luca it should work. However we haven't tested with S4 yet.
>>>>
>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>
>>>
>>>
>>>
>>> --
>>> Melan Nimesh Jayasingha
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> Melan Nimesh Jayasingha
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: stratos using vmware though jclouds ?
Posted by Melan Nimesh <me...@gmail.com>.
Hi Devs,
I am testing vCloud integrating with a vCloud provider which supports only
for 1.5, 5.1 and 5.5 versions and I am getting following error [1]
when trying to deploy a cartridge definition. I am using latest packs (JCloud
1.7) from master branch with JCloud patches provided by Nirmal
I went through JCloud VCloudLoginApi's code [2] and noticed jCloud expecting
* "**application/vnd.vmware.vcloud.orgList+xml" *for a session request
which is default for VCloud API 1.0. but API 1.5 or later sending
*"application/vnd.vmware.vcloud.session+xml**"* type of object. I can try
to modify VCloudLoginApi to support latest type, but then we will lost API
1.0 support,
is there any better way to do this? does JCloud supports VCloud API 1.5 or
later?
Thanks,
Melan
[1]
ID: [0] [CC] [2014-02-10 14:19:34,682] DEBUG {jclouds.headers} - >> POST
https://provider.url/api/sessions HTTP/1.1 {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
Accept: application/vnd.vmware.vcloud.orgList+xml;version=1.5
{jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:34,688] DEBUG {jclouds.headers} - >>
Authorization: Basic dWRhcmFzYW1wYXRo***************DEyMw==
{jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,092] DEBUG {jclouds.headers} - <<
HTTP/1.1 406 Not Acceptable {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - << Vary:
Accept-Encoding {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,093] DEBUG {jclouds.headers} - << Date:
Mon, 10 Feb 2014 08:41:45 GMT {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
x-vcloud-authorization: wxtrE+czrOIUdUmBNT**********3LHqrDh1sAc=
{jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,094] DEBUG {jclouds.headers} - <<
Set-Cookie: ROUTEID=.vcd1; path=/ {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
Set-Cookie: vcloud-token=wxtrE+czrOIUdUmBNT******8eda3LHqrDh1sAc=; Secure;
Path=/ {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,095] DEBUG {jclouds.headers} - <<
Connection: close {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
Content-Type: application/vnd.vmware.vcloud.error+xml; version=1.5
{jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,096] DEBUG {jclouds.headers} - <<
Content-Length: 362 {jclouds.headers}
TID: [0] [CC] [2014-02-10 14:19:35,105] DEBUG {jclouds.wire} - << "<?xml
version="1.0" encoding="UTF-8"?>[\n]" {jclouds.wire}
TID: [0] [CC] [2014-02-10 14:19:35,106] DEBUG {jclouds.wire} - << "<Error
xmlns="http://www.vmware.com/vcloud/v1.5" minorErrorCode="NOT_ACCEPTABLE"
message="The request accept header is invalid." majorErrorCode="406"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="
http://www.vmware.com/vcloud/v1.5
http://mycloud.stratogen.sg/api/v1.5/schema/master.xsd"></Error>[\n]"
{jclouds.wire}
TID: [0] [CC] [2014-02-10 14:19:35,176] ERROR
{org.apache.stratos.cloud.controller.util.CloudControllerUtil} - Unable to
build the jclouds object for iaas of type: vcloud
{org.apache.stratos.cloud.controller.util.CloudControllerUtil}
org.jclouds.vcloud.VCloudResponseException: request POST
https://mycloud.stratogen.sg/api/sessions HTTP/1.1 failed with code 406,
error: [majorErrorCode=406, message=The request accept header is invalid.,
minorErrorCode=UNRECOGNIZED, stackTrace=null,
vendorSpecificErrorCode=NOT_ACCEPTABLE]
at
org.jclouds.vcloud.handlers.ParseVCloudErrorFromHttpResponse.handleError(ParseVCloudErrorFromHttpResponse.java:72)
at
org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
at
org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
[2]
public interface VCloudLoginApi extends Closeable {
/**
* This request returns a token to use in subsequent requests. After 30
minutes of inactivity,
* the token expires and you have to request a new token with this call.
*/
@POST
@ResponseParser(ParseLoginResponseFromHeaders.class)
@Consumes(VCloudMediaType.ORGLIST_XML)
VCloudSession login();
}
On Mon, Feb 3, 2014 at 6:50 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi Melan,
>
> Yes, I've patch jClouds vCloud, let me give the patched jar, so that you
> can carry on testing.
>
> vCloud IaaS provider can be found in the Cloud Controller component.
>
>
> On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com> wrote:
>
>> Hi Devs,
>>
>> I started testing the Stratos latest packs with vcloud IaaS
>> and currently I am at initial step. I will update the thread with the
>> progress.
>>
>> I have few questions..
>> - Do we have any vcloud related jcloud patches?
>> - Where can I found sample iaasProvider configuration for vcloud ?
>>
>> Thanks,
>> Melan
>>
>>
>> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Yes Luca it should work. However we haven't tested with S4 yet.
>>>
>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>
>>
>>
>>
>> --
>> Melan Nimesh Jayasingha
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Melan,
Yes, I've patch jClouds vCloud, let me give the patched jar, so that you
can carry on testing.
vCloud IaaS provider can be found in the Cloud Controller component.
On Mon, Feb 3, 2014 at 10:56 AM, Melan Nimesh <me...@gmail.com> wrote:
> Hi Devs,
>
> I started testing the Stratos latest packs with vcloud IaaS
> and currently I am at initial step. I will update the thread with the
> progress.
>
> I have few questions..
> - Do we have any vcloud related jcloud patches?
> - Where can I found sample iaasProvider configuration for vcloud ?
>
> Thanks,
> Melan
>
>
> On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Yes Luca it should work. However we haven't tested with S4 yet.
>>
>> Touched, not typed. Erroneous words are a feature, not a typo.
>>
>
>
>
> --
> Melan Nimesh Jayasingha
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: stratos using vmware though jclouds ?
Posted by Melan Nimesh <me...@gmail.com>.
Hi Devs,
I started testing the Stratos latest packs with vcloud IaaS and currently I
am at initial step. I will update the thread with the progress.
I have few questions..
- Do we have any vcloud related jcloud patches?
- Where can I found sample iaasProvider configuration for vcloud ?
Thanks,
Melan
On Thu, Jan 30, 2014 at 12:33 AM, Udara Liyanage <ud...@wso2.com> wrote:
> Yes Luca it should work. However we haven't tested with S4 yet.
>
> Touched, not typed. Erroneous words are a feature, not a typo.
>
--
Melan Nimesh Jayasingha
Re: stratos using vmware though jclouds ?
Posted by Udara Liyanage <ud...@wso2.com>.
Yes Luca it should work. However we haven't tested with S4 yet.
Touched, not typed. Erroneous words are a feature, not a typo.
Re: stratos using vmware though jclouds ?
Posted by Lakmal Warusawithana <la...@wso2.com>.
Hi,
On Wed, Jan 29, 2014 at 11:12 PM, Luca Martini <lm...@cisco.com> wrote:
> Hello!
> Did anybody try to a vmware provider in the stratos/jclouds configuration ?
> I know this worked a long time ago , but does it still work ?
>
it should work, we are going to start vcloud (vmware) testing on stratos 4
now. Will provide some update on that.
Thanks.
> Luca
>
>
--
Lakmal Warusawithana
Software Architect; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/