You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Mariangela Hills <ma...@wso2.com> on 2015/01/23 10:58:34 UTC
How come I dont get an error when adding the identical cartridge
definition twice?
I was expecting to get 409 when I added the same cartridge definition
twice, but I did not get an error. Is this meant to be this way?
*Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
application/json" -d @'tomcat.json' -k -v -u admin:admin
https://localhost:9443/api/cartridges
<https://localhost:9443/api/cartridges>*
* About to connect() to localhost port 9443 (#0)
* Trying ::1...
* connected
* Connected to localhost (::1) port 9443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using DHE-RSA-AES256-SHA
* Server certificate:
* subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
* start date: 2010-02-19 07:02:26 GMT
* expire date: 2035-02-13 07:02:26 GMT
* common name: localhost (matched)
* issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
* SSL certificate verify result: unable to get local issuer certificate
(20), continuing anyway.
* Server auth using Basic with user 'admin'
> POST /api/cartridges HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
OpenSSL/0.9.8r zlib/1.2.5
> Host: localhost:9443
> Accept: */*
> Content-Type: application/json
> Content-Length: 1166
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
*< HTTP/1.1 201 Created*
< Date: Fri, 23 Jan 2015 09:42:24 GMT
< Location: https://localhost:9443/api/cartridges/tomcat
< Content-Length: 0
< Server: WSO2 Carbon Server
<
* Connection #0 to host localhost left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
*Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
application/json" -d @'tomcat.json' -k -v -u admin:admin
https://localhost:9443/api/cartridges
<https://localhost:9443/api/cartridges>*
* About to connect() to localhost port 9443 (#0)
* Trying ::1...
* connected
* Connected to localhost (::1) port 9443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using DHE-RSA-AES256-SHA
* Server certificate:
* subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
* start date: 2010-02-19 07:02:26 GMT
* expire date: 2035-02-13 07:02:26 GMT
* common name: localhost (matched)
* issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
* SSL certificate verify result: unable to get local issuer certificate
(20), continuing anyway.
* Server auth using Basic with user 'admin'
> POST /api/cartridges HTTP/1.1
> Authorization: Basic YWRtaW46YWRtaW4=
> User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
OpenSSL/0.9.8r zlib/1.2.5
> Host: localhost:9443
> Accept: */*
> Content-Type: application/json
> Content-Length: 1166
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
*< HTTP/1.1 201 Created*
< Date: Fri, 23 Jan 2015 09:50:49 GMT
< Location: https://localhost:9443/api/cartridges/tomcat
< Content-Length: 0
< Server: WSO2 Carbon Server
<
* Connection #0 to host localhost left intact
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
Admin16s-MacBook-Air:artifacts Admin16$
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
w: http://wso2.com
<http://wso2.com/events/>
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Gayan Gunarathne <ga...@wso2.com>.
Added the CLI command for cartridge update: update-cartridge
Thanks,
Gayan
On Mon, Jan 26, 2015 at 10:23 AM, Gayan Gunarathne <ga...@wso2.com> wrote:
> Yeah. We need to add a CLI command to this as well. I will add it.
>
> Thanks,
> Gayan
>
> On Mon, Jan 26, 2015 at 10:18 AM, Mariangela Hills <ma...@wso2.com>
> wrote:
>
>> I added the API in [1]. Do we have a corresponding CLI command for this?
>> I checked the code, but I didn't come across the command.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Updating+a+Cartridge+via+REST+API
>>
>> Regards,
>> Mariangela
>>
>>
>>
>>
>> *--*
>> Mariangela Hills
>> Senior Technical Writer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>> w: http://wso2.com
>> <http://wso2.com/events/>
>>
>> On Sun, Jan 25, 2015 at 11:59 PM, Gayan Gunarathne <ga...@wso2.com>
>> wrote:
>>
>>> Now we are not allow to update the cartridge with the adding cartridge
>>> REST method. We have introduced following PUT method to update the existing
>>> cartridges.
>>>
>>>
>>> HTTP MethodResource Path
>>>
>>> PUT /
>>> <https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Describing+an+Auto-scaling+Policy+via+REST+API>cartridges
>>>
>>> Sample CURL request:
>>>
>>> curl -X PUT -H "Content-Type: application/json" -d
>>> @'<cartridge_definition_json>' -k -v -u admin:admin https://
>>> <stratos_server_ip>:9443/api/cartridges
>>>
>>> Thanks,
>>> Gayan
>>>
>>>
>>> On Fri, Jan 23, 2015 at 6:26 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> +1 Yes will add an api method to update a cartridge.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 23, 2015 at 5:18 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne <ga...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> I think we can define two REST API operations with POST and PUT http
>>>>>> methods.
>>>>>> POST to create resource and PUT to update resource.
>>>>>> (I will suggested to use PUT to update resource as we are update a
>>>>>> resource(cartridge) completely)
>>>>>>
>>>>>> +1
>>>>>
>>>>>> Thanks,
>>>>>> Gayan
>>>>>>
>>>>>>
>>>>>> On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <
>>>>>> lakmal@wso2.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I think with the terminology change "Deploy cartridge" -> "Add
>>>>>>>> cartridge" this functionality might not valid. We may need to raise an
>>>>>>>> error if the cartridge is already added with the HTTP status code 409.
>>>>>>>>
>>>>>>>>
>>>>>>> And we may need to add "update cartridge" as well.
>>>>>>>
>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> When a new cartridge with an existing name is added, it overwrites
>>>>>>>>> the existing one. So the behavior you got is the expected behavior.
>>>>>>>>>
>>>>>>>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <
>>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> I was expecting to get 409 when I added the same cartridge
>>>>>>>>>> definition twice, but I did not get an error. Is this meant to be this way?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>>>>> https://localhost:9443/api/cartridges
>>>>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>>>>> * Trying ::1...
>>>>>>>>>> * connected
>>>>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>>>>> * Server certificate:
>>>>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>>>>> * common name: localhost (matched)
>>>>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>>>>> certificate (20), continuing anyway.
>>>>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0)
>>>>>>>>>> libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
>>>>>>>>>> > Host: localhost:9443
>>>>>>>>>> > Accept: */*
>>>>>>>>>> > Content-Type: application/json
>>>>>>>>>> > Content-Length: 1166
>>>>>>>>>> > Expect: 100-continue
>>>>>>>>>> >
>>>>>>>>>> < HTTP/1.1 100 Continue
>>>>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>>>>> < Content-Length: 0
>>>>>>>>>> < Server: WSO2 Carbon Server
>>>>>>>>>> <
>>>>>>>>>> * Connection #0 to host localhost left intact
>>>>>>>>>> * Closing connection #0
>>>>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>>>>> https://localhost:9443/api/cartridges
>>>>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>>>>> * Trying ::1...
>>>>>>>>>> * connected
>>>>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>>>>> * Server certificate:
>>>>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>>>>> * common name: localhost (matched)
>>>>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>>>>> certificate (20), continuing anyway.
>>>>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0)
>>>>>>>>>> libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
>>>>>>>>>> > Host: localhost:9443
>>>>>>>>>> > Accept: */*
>>>>>>>>>> > Content-Type: application/json
>>>>>>>>>> > Content-Length: 1166
>>>>>>>>>> > Expect: 100-continue
>>>>>>>>>> >
>>>>>>>>>> < HTTP/1.1 100 Continue
>>>>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>>>>> < Content-Length: 0
>>>>>>>>>> < Server: WSO2 Carbon Server
>>>>>>>>>> <
>>>>>>>>>> * Connection #0 to host localhost left intact
>>>>>>>>>> * Closing connection #0
>>>>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Mariangela
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *--*
>>>>>>>>>> Mariangela Hills
>>>>>>>>>> Senior Technical Writer
>>>>>>>>>>
>>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>>>
>>>>>>>>>> w: http://wso2.com
>>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Udara Liyanage
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>>>> lean. enterprise. middleware
>>>>>>>>>
>>>>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>>>>> phone: +94 71 443 6897
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Lakmal Warusawithana
>>>>>>> Vice President, Apache Stratos
>>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>>> Mobile : +94714289692
>>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Gayan Gunarathne
>>>>>> Technical Lead
>>>>>> WSO2 Inc. (http://wso2.com)
>>>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Udara Liyanage
>>>>> Software Engineer
>>>>> WSO2, Inc.: http://wso2.com
>>>>> lean. enterprise. middleware
>>>>>
>>>>> web: http://udaraliyanage.wordpress.com
>>>>> phone: +94 71 443 6897
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead
>>> WSO2 Inc. (http://wso2.com)
>>> email : gayang@wso2.com | mobile : +94 766819985
>>>
>>>
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Gayan Gunarathne <ga...@wso2.com>.
Yeah. We need to add a CLI command to this as well. I will add it.
Thanks,
Gayan
On Mon, Jan 26, 2015 at 10:18 AM, Mariangela Hills <ma...@wso2.com>
wrote:
> I added the API in [1]. Do we have a corresponding CLI command for this? I
> checked the code, but I didn't come across the command.
>
> [1]
> https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Updating+a+Cartridge+via+REST+API
>
> Regards,
> Mariangela
>
>
>
>
> *--*
> Mariangela Hills
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
> w: http://wso2.com
> <http://wso2.com/events/>
>
> On Sun, Jan 25, 2015 at 11:59 PM, Gayan Gunarathne <ga...@wso2.com>
> wrote:
>
>> Now we are not allow to update the cartridge with the adding cartridge
>> REST method. We have introduced following PUT method to update the existing
>> cartridges.
>>
>>
>> HTTP MethodResource Path
>>
>> PUT /
>> <https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Describing+an+Auto-scaling+Policy+via+REST+API>cartridges
>>
>> Sample CURL request:
>>
>> curl -X PUT -H "Content-Type: application/json" -d
>> @'<cartridge_definition_json>' -k -v -u admin:admin https://
>> <stratos_server_ip>:9443/api/cartridges
>>
>> Thanks,
>> Gayan
>>
>>
>> On Fri, Jan 23, 2015 at 6:26 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> +1 Yes will add an api method to update a cartridge.
>>>
>>> Thanks
>>>
>>> On Fri, Jan 23, 2015 at 5:18 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne <ga...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> I think we can define two REST API operations with POST and PUT http
>>>>> methods.
>>>>> POST to create resource and PUT to update resource.
>>>>> (I will suggested to use PUT to update resource as we are update a
>>>>> resource(cartridge) completely)
>>>>>
>>>>> +1
>>>>
>>>>> Thanks,
>>>>> Gayan
>>>>>
>>>>>
>>>>> On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <lakmal@wso2.com
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I think with the terminology change "Deploy cartridge" -> "Add
>>>>>>> cartridge" this functionality might not valid. We may need to raise an
>>>>>>> error if the cartridge is already added with the HTTP status code 409.
>>>>>>>
>>>>>>>
>>>>>> And we may need to add "update cartridge" as well.
>>>>>>
>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> When a new cartridge with an existing name is added, it overwrites
>>>>>>>> the existing one. So the behavior you got is the expected behavior.
>>>>>>>>
>>>>>>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <
>>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> I was expecting to get 409 when I added the same cartridge
>>>>>>>>> definition twice, but I did not get an error. Is this meant to be this way?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>>>> https://localhost:9443/api/cartridges
>>>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>>>> * Trying ::1...
>>>>>>>>> * connected
>>>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>>>> * Server certificate:
>>>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>>>> * common name: localhost (matched)
>>>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>>>> certificate (20), continuing anyway.
>>>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>>>>> > Host: localhost:9443
>>>>>>>>> > Accept: */*
>>>>>>>>> > Content-Type: application/json
>>>>>>>>> > Content-Length: 1166
>>>>>>>>> > Expect: 100-continue
>>>>>>>>> >
>>>>>>>>> < HTTP/1.1 100 Continue
>>>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>>>> < Content-Length: 0
>>>>>>>>> < Server: WSO2 Carbon Server
>>>>>>>>> <
>>>>>>>>> * Connection #0 to host localhost left intact
>>>>>>>>> * Closing connection #0
>>>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>>>> https://localhost:9443/api/cartridges
>>>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>>>> * Trying ::1...
>>>>>>>>> * connected
>>>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>>>> * Server certificate:
>>>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>>>> * common name: localhost (matched)
>>>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>>>> certificate (20), continuing anyway.
>>>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>>>>> > Host: localhost:9443
>>>>>>>>> > Accept: */*
>>>>>>>>> > Content-Type: application/json
>>>>>>>>> > Content-Length: 1166
>>>>>>>>> > Expect: 100-continue
>>>>>>>>> >
>>>>>>>>> < HTTP/1.1 100 Continue
>>>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>>>> < Content-Length: 0
>>>>>>>>> < Server: WSO2 Carbon Server
>>>>>>>>> <
>>>>>>>>> * Connection #0 to host localhost left intact
>>>>>>>>> * Closing connection #0
>>>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Mariangela
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *--*
>>>>>>>>> Mariangela Hills
>>>>>>>>> Senior Technical Writer
>>>>>>>>>
>>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>>
>>>>>>>>> w: http://wso2.com
>>>>>>>>> <http://wso2.com/events/>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Udara Liyanage
>>>>>>>> Software Engineer
>>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>>> lean. enterprise. middleware
>>>>>>>>
>>>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>>>> phone: +94 71 443 6897
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lakmal Warusawithana
>>>>>> Vice President, Apache Stratos
>>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>>> Mobile : +94714289692
>>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Gayan Gunarathne
>>>>> Technical Lead
>>>>> WSO2 Inc. (http://wso2.com)
>>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Udara Liyanage
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean. enterprise. middleware
>>>>
>>>> web: http://udaraliyanage.wordpress.com
>>>> phone: +94 71 443 6897
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead
>> WSO2 Inc. (http://wso2.com)
>> email : gayang@wso2.com | mobile : +94 766819985
>>
>>
>
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Mariangela Hills <ma...@wso2.com>.
I added the API in [1]. Do we have a corresponding CLI command for this? I
checked the code, but I didn't come across the command.
[1]
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Updating+a+Cartridge+via+REST+API
Regards,
Mariangela
*--*
Mariangela Hills
Senior Technical Writer
*WSO2, Inc.*lean.enterprise.middleware.
w: http://wso2.com
<http://wso2.com/events/>
On Sun, Jan 25, 2015 at 11:59 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
> Now we are not allow to update the cartridge with the adding cartridge
> REST method. We have introduced following PUT method to update the existing
> cartridges.
>
>
> HTTP MethodResource Path
>
> PUT /
> <https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Describing+an+Auto-scaling+Policy+via+REST+API>cartridges
>
> Sample CURL request:
>
> curl -X PUT -H "Content-Type: application/json" -d
> @'<cartridge_definition_json>' -k -v -u admin:admin https://
> <stratos_server_ip>:9443/api/cartridges
>
> Thanks,
> Gayan
>
>
> On Fri, Jan 23, 2015 at 6:26 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> +1 Yes will add an api method to update a cartridge.
>>
>> Thanks
>>
>> On Fri, Jan 23, 2015 at 5:18 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>>
>>>
>>> On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne <ga...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> I think we can define two REST API operations with POST and PUT http
>>>> methods.
>>>> POST to create resource and PUT to update resource.
>>>> (I will suggested to use PUT to update resource as we are update a
>>>> resource(cartridge) completely)
>>>>
>>>> +1
>>>
>>>> Thanks,
>>>> Gayan
>>>>
>>>>
>>>> On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <la...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I think with the terminology change "Deploy cartridge" -> "Add
>>>>>> cartridge" this functionality might not valid. We may need to raise an
>>>>>> error if the cartridge is already added with the HTTP status code 409.
>>>>>>
>>>>>>
>>>>> And we may need to add "update cartridge" as well.
>>>>>
>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> When a new cartridge with an existing name is added, it overwrites
>>>>>>> the existing one. So the behavior you got is the expected behavior.
>>>>>>>
>>>>>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <
>>>>>>> mariangela@wso2.com> wrote:
>>>>>>>
>>>>>>>> I was expecting to get 409 when I added the same cartridge
>>>>>>>> definition twice, but I did not get an error. Is this meant to be this way?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>>> https://localhost:9443/api/cartridges
>>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>>> * Trying ::1...
>>>>>>>> * connected
>>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>>> * Server certificate:
>>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>>> * common name: localhost (matched)
>>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>>> certificate (20), continuing anyway.
>>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>>>> > Host: localhost:9443
>>>>>>>> > Accept: */*
>>>>>>>> > Content-Type: application/json
>>>>>>>> > Content-Length: 1166
>>>>>>>> > Expect: 100-continue
>>>>>>>> >
>>>>>>>> < HTTP/1.1 100 Continue
>>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>>> < Content-Length: 0
>>>>>>>> < Server: WSO2 Carbon Server
>>>>>>>> <
>>>>>>>> * Connection #0 to host localhost left intact
>>>>>>>> * Closing connection #0
>>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>>> https://localhost:9443/api/cartridges
>>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>>> * Trying ::1...
>>>>>>>> * connected
>>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>>> * Server certificate:
>>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>>> * common name: localhost (matched)
>>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>>> certificate (20), continuing anyway.
>>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>>>> > Host: localhost:9443
>>>>>>>> > Accept: */*
>>>>>>>> > Content-Type: application/json
>>>>>>>> > Content-Length: 1166
>>>>>>>> > Expect: 100-continue
>>>>>>>> >
>>>>>>>> < HTTP/1.1 100 Continue
>>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>>> < Content-Length: 0
>>>>>>>> < Server: WSO2 Carbon Server
>>>>>>>> <
>>>>>>>> * Connection #0 to host localhost left intact
>>>>>>>> * Closing connection #0
>>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mariangela
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *--*
>>>>>>>> Mariangela Hills
>>>>>>>> Senior Technical Writer
>>>>>>>>
>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>>
>>>>>>>> w: http://wso2.com
>>>>>>>> <http://wso2.com/events/>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Udara Liyanage
>>>>>>> Software Engineer
>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>> lean. enterprise. middleware
>>>>>>>
>>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>>> phone: +94 71 443 6897
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lakmal Warusawithana
>>>>> Vice President, Apache Stratos
>>>>> Director - Cloud Architecture; WSO2 Inc.
>>>>> Mobile : +94714289692
>>>>> Blog : http://lakmalsview.blogspot.com/
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Gayan Gunarathne
>>>> Technical Lead
>>>> WSO2 Inc. (http://wso2.com)
>>>> email : gayang@wso2.com | mobile : +94 766819985
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Gayan Gunarathne <ga...@wso2.com>.
Now we are not allow to update the cartridge with the adding cartridge REST
method. We have introduced following PUT method to update the existing
cartridges.
HTTP MethodResource Path
PUT /
<https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Describing+an+Auto-scaling+Policy+via+REST+API>cartridges
Sample CURL request:
curl -X PUT -H "Content-Type: application/json" -d
@'<cartridge_definition_json>' -k -v -u admin:admin https://
<stratos_server_ip>:9443/api/cartridges
Thanks,
Gayan
On Fri, Jan 23, 2015 at 6:26 PM, Imesh Gunaratne <im...@apache.org> wrote:
> +1 Yes will add an api method to update a cartridge.
>
> Thanks
>
> On Fri, Jan 23, 2015 at 5:18 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
>>
>>
>> On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne <ga...@wso2.com>
>> wrote:
>>
>>>
>>> I think we can define two REST API operations with POST and PUT http
>>> methods.
>>> POST to create resource and PUT to update resource.
>>> (I will suggested to use PUT to update resource as we are update a
>>> resource(cartridge) completely)
>>>
>>> +1
>>
>>> Thanks,
>>> Gayan
>>>
>>>
>>> On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <la...@wso2.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I think with the terminology change "Deploy cartridge" -> "Add
>>>>> cartridge" this functionality might not valid. We may need to raise an
>>>>> error if the cartridge is already added with the HTTP status code 409.
>>>>>
>>>>>
>>>> And we may need to add "update cartridge" as well.
>>>>
>>>>
>>>>> Thanks
>>>>>
>>>>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> When a new cartridge with an existing name is added, it overwrites
>>>>>> the existing one. So the behavior you got is the expected behavior.
>>>>>>
>>>>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <
>>>>>> mariangela@wso2.com> wrote:
>>>>>>
>>>>>>> I was expecting to get 409 when I added the same cartridge
>>>>>>> definition twice, but I did not get an error. Is this meant to be this way?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>> https://localhost:9443/api/cartridges
>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>> * Trying ::1...
>>>>>>> * connected
>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>> * Server certificate:
>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>> * common name: localhost (matched)
>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>> certificate (20), continuing anyway.
>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>>> > Host: localhost:9443
>>>>>>> > Accept: */*
>>>>>>> > Content-Type: application/json
>>>>>>> > Content-Length: 1166
>>>>>>> > Expect: 100-continue
>>>>>>> >
>>>>>>> < HTTP/1.1 100 Continue
>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>> < Content-Length: 0
>>>>>>> < Server: WSO2 Carbon Server
>>>>>>> <
>>>>>>> * Connection #0 to host localhost left intact
>>>>>>> * Closing connection #0
>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>>> https://localhost:9443/api/cartridges
>>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>>> * Trying ::1...
>>>>>>> * connected
>>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>>> * Server certificate:
>>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>>> * common name: localhost (matched)
>>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>>> certificate (20), continuing anyway.
>>>>>>> * Server auth using Basic with user 'admin'
>>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>>> > Host: localhost:9443
>>>>>>> > Accept: */*
>>>>>>> > Content-Type: application/json
>>>>>>> > Content-Length: 1166
>>>>>>> > Expect: 100-continue
>>>>>>> >
>>>>>>> < HTTP/1.1 100 Continue
>>>>>>> *< HTTP/1.1 201 Created*
>>>>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>>> < Content-Length: 0
>>>>>>> < Server: WSO2 Carbon Server
>>>>>>> <
>>>>>>> * Connection #0 to host localhost left intact
>>>>>>> * Closing connection #0
>>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mariangela
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *--*
>>>>>>> Mariangela Hills
>>>>>>> Senior Technical Writer
>>>>>>>
>>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>>
>>>>>>> w: http://wso2.com
>>>>>>> <http://wso2.com/events/>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Udara Liyanage
>>>>>> Software Engineer
>>>>>> WSO2, Inc.: http://wso2.com
>>>>>> lean. enterprise. middleware
>>>>>>
>>>>>> web: http://udaraliyanage.wordpress.com
>>>>>> phone: +94 71 443 6897
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lakmal Warusawithana
>>>> Vice President, Apache Stratos
>>>> Director - Cloud Architecture; WSO2 Inc.
>>>> Mobile : +94714289692
>>>> Blog : http://lakmalsview.blogspot.com/
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Gayan Gunarathne
>>> Technical Lead
>>> WSO2 Inc. (http://wso2.com)
>>> email : gayang@wso2.com | mobile : +94 766819985
>>>
>>>
>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Imesh Gunaratne <im...@apache.org>.
+1 Yes will add an api method to update a cartridge.
Thanks
On Fri, Jan 23, 2015 at 5:18 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
>
> On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
>>
>> I think we can define two REST API operations with POST and PUT http
>> methods.
>> POST to create resource and PUT to update resource.
>> (I will suggested to use PUT to update resource as we are update a
>> resource(cartridge) completely)
>>
>> +1
>
>> Thanks,
>> Gayan
>>
>>
>> On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <la...@wso2.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I think with the terminology change "Deploy cartridge" -> "Add
>>>> cartridge" this functionality might not valid. We may need to raise an
>>>> error if the cartridge is already added with the HTTP status code 409.
>>>>
>>>>
>>> And we may need to add "update cartridge" as well.
>>>
>>>
>>>> Thanks
>>>>
>>>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> When a new cartridge with an existing name is added, it overwrites the
>>>>> existing one. So the behavior you got is the expected behavior.
>>>>>
>>>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <mariangela@wso2.com
>>>>> > wrote:
>>>>>
>>>>>> I was expecting to get 409 when I added the same cartridge definition
>>>>>> twice, but I did not get an error. Is this meant to be this way?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>> https://localhost:9443/api/cartridges
>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>> * Trying ::1...
>>>>>> * connected
>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>> * Server certificate:
>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>> * common name: localhost (matched)
>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>> certificate (20), continuing anyway.
>>>>>> * Server auth using Basic with user 'admin'
>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>> > Host: localhost:9443
>>>>>> > Accept: */*
>>>>>> > Content-Type: application/json
>>>>>> > Content-Length: 1166
>>>>>> > Expect: 100-continue
>>>>>> >
>>>>>> < HTTP/1.1 100 Continue
>>>>>> *< HTTP/1.1 201 Created*
>>>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>> < Content-Length: 0
>>>>>> < Server: WSO2 Carbon Server
>>>>>> <
>>>>>> * Connection #0 to host localhost left intact
>>>>>> * Closing connection #0
>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>>> https://localhost:9443/api/cartridges
>>>>>> <https://localhost:9443/api/cartridges>*
>>>>>> * About to connect() to localhost port 9443 (#0)
>>>>>> * Trying ::1...
>>>>>> * connected
>>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>>> * Server certificate:
>>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>>> * common name: localhost (matched)
>>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>>> * SSL certificate verify result: unable to get local issuer
>>>>>> certificate (20), continuing anyway.
>>>>>> * Server auth using Basic with user 'admin'
>>>>>> > POST /api/cartridges HTTP/1.1
>>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>>> > Host: localhost:9443
>>>>>> > Accept: */*
>>>>>> > Content-Type: application/json
>>>>>> > Content-Length: 1166
>>>>>> > Expect: 100-continue
>>>>>> >
>>>>>> < HTTP/1.1 100 Continue
>>>>>> *< HTTP/1.1 201 Created*
>>>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>>> < Content-Length: 0
>>>>>> < Server: WSO2 Carbon Server
>>>>>> <
>>>>>> * Connection #0 to host localhost left intact
>>>>>> * Closing connection #0
>>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Mariangela
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *--*
>>>>>> Mariangela Hills
>>>>>> Senior Technical Writer
>>>>>>
>>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>>
>>>>>> w: http://wso2.com
>>>>>> <http://wso2.com/events/>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Udara Liyanage
>>>>> Software Engineer
>>>>> WSO2, Inc.: http://wso2.com
>>>>> lean. enterprise. middleware
>>>>>
>>>>> web: http://udaraliyanage.wordpress.com
>>>>> phone: +94 71 443 6897
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Vice President, Apache Stratos
>>> Director - Cloud Architecture; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>>
>> Gayan Gunarathne
>> Technical Lead
>> WSO2 Inc. (http://wso2.com)
>> email : gayang@wso2.com | mobile : +94 766819985
>>
>>
>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Udara Liyanage <ud...@wso2.com>.
On Fri, Jan 23, 2015 at 5:02 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
>
> I think we can define two REST API operations with POST and PUT http
> methods.
> POST to create resource and PUT to update resource.
> (I will suggested to use PUT to update resource as we are update a
> resource(cartridge) completely)
>
> +1
> Thanks,
> Gayan
>
>
> On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <la...@wso2.com>
> wrote:
>
>>
>>
>> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I think with the terminology change "Deploy cartridge" -> "Add
>>> cartridge" this functionality might not valid. We may need to raise an
>>> error if the cartridge is already added with the HTTP status code 409.
>>>
>>>
>> And we may need to add "update cartridge" as well.
>>
>>
>>> Thanks
>>>
>>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> When a new cartridge with an existing name is added, it overwrites the
>>>> existing one. So the behavior you got is the expected behavior.
>>>>
>>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <ma...@wso2.com>
>>>> wrote:
>>>>
>>>>> I was expecting to get 409 when I added the same cartridge definition
>>>>> twice, but I did not get an error. Is this meant to be this way?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>> https://localhost:9443/api/cartridges
>>>>> <https://localhost:9443/api/cartridges>*
>>>>> * About to connect() to localhost port 9443 (#0)
>>>>> * Trying ::1...
>>>>> * connected
>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>> * Server certificate:
>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>> * common name: localhost (matched)
>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>> * SSL certificate verify result: unable to get local issuer
>>>>> certificate (20), continuing anyway.
>>>>> * Server auth using Basic with user 'admin'
>>>>> > POST /api/cartridges HTTP/1.1
>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>> > Host: localhost:9443
>>>>> > Accept: */*
>>>>> > Content-Type: application/json
>>>>> > Content-Length: 1166
>>>>> > Expect: 100-continue
>>>>> >
>>>>> < HTTP/1.1 100 Continue
>>>>> *< HTTP/1.1 201 Created*
>>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>> < Content-Length: 0
>>>>> < Server: WSO2 Carbon Server
>>>>> <
>>>>> * Connection #0 to host localhost left intact
>>>>> * Closing connection #0
>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H
>>>>> "Content-Type: application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>>> https://localhost:9443/api/cartridges
>>>>> <https://localhost:9443/api/cartridges>*
>>>>> * About to connect() to localhost port 9443 (#0)
>>>>> * Trying ::1...
>>>>> * connected
>>>>> * Connected to localhost (::1) port 9443 (#0)
>>>>> * SSLv3, TLS handshake, Client hello (1):
>>>>> * SSLv3, TLS handshake, Server hello (2):
>>>>> * SSLv3, TLS handshake, CERT (11):
>>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>>> * SSLv3, TLS handshake, Server finished (14):
>>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>>> * SSLv3, TLS handshake, Finished (20):
>>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>>> * Server certificate:
>>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>> * start date: 2010-02-19 07:02:26 GMT
>>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>>> * common name: localhost (matched)
>>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>>> * SSL certificate verify result: unable to get local issuer
>>>>> certificate (20), continuing anyway.
>>>>> * Server auth using Basic with user 'admin'
>>>>> > POST /api/cartridges HTTP/1.1
>>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>>> > Host: localhost:9443
>>>>> > Accept: */*
>>>>> > Content-Type: application/json
>>>>> > Content-Length: 1166
>>>>> > Expect: 100-continue
>>>>> >
>>>>> < HTTP/1.1 100 Continue
>>>>> *< HTTP/1.1 201 Created*
>>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>>> < Content-Length: 0
>>>>> < Server: WSO2 Carbon Server
>>>>> <
>>>>> * Connection #0 to host localhost left intact
>>>>> * Closing connection #0
>>>>> * SSLv3, TLS alert, Client hello (1):
>>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>> Mariangela
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *--*
>>>>> Mariangela Hills
>>>>> Senior Technical Writer
>>>>>
>>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>>
>>>>> w: http://wso2.com
>>>>> <http://wso2.com/events/>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Udara Liyanage
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean. enterprise. middleware
>>>>
>>>> web: http://udaraliyanage.wordpress.com
>>>> phone: +94 71 443 6897
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Vice President, Apache Stratos
>> Director - Cloud Architecture; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Gayan Gunarathne <ga...@wso2.com>.
I think we can define two REST API operations with POST and PUT http
methods.
POST to create resource and PUT to update resource.
(I will suggested to use PUT to update resource as we are update a
resource(cartridge) completely)
Thanks,
Gayan
On Fri, Jan 23, 2015 at 4:40 PM, Lakmal Warusawithana <la...@wso2.com>
wrote:
>
>
> On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think with the terminology change "Deploy cartridge" -> "Add cartridge"
>> this functionality might not valid. We may need to raise an error if the
>> cartridge is already added with the HTTP status code 409.
>>
>>
> And we may need to add "update cartridge" as well.
>
>
>> Thanks
>>
>> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> When a new cartridge with an existing name is added, it overwrites the
>>> existing one. So the behavior you got is the expected behavior.
>>>
>>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <ma...@wso2.com>
>>> wrote:
>>>
>>>> I was expecting to get 409 when I added the same cartridge definition
>>>> twice, but I did not get an error. Is this meant to be this way?
>>>>
>>>>
>>>>
>>>>
>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
>>>> application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>> https://localhost:9443/api/cartridges
>>>> <https://localhost:9443/api/cartridges>*
>>>> * About to connect() to localhost port 9443 (#0)
>>>> * Trying ::1...
>>>> * connected
>>>> * Connected to localhost (::1) port 9443 (#0)
>>>> * SSLv3, TLS handshake, Client hello (1):
>>>> * SSLv3, TLS handshake, Server hello (2):
>>>> * SSLv3, TLS handshake, CERT (11):
>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>> * SSLv3, TLS handshake, Server finished (14):
>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>> * SSLv3, TLS handshake, Finished (20):
>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>> * SSLv3, TLS handshake, Finished (20):
>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>> * Server certificate:
>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>> * start date: 2010-02-19 07:02:26 GMT
>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>> * common name: localhost (matched)
>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>> * SSL certificate verify result: unable to get local issuer
>>>> certificate (20), continuing anyway.
>>>> * Server auth using Basic with user 'admin'
>>>> > POST /api/cartridges HTTP/1.1
>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>> > Host: localhost:9443
>>>> > Accept: */*
>>>> > Content-Type: application/json
>>>> > Content-Length: 1166
>>>> > Expect: 100-continue
>>>> >
>>>> < HTTP/1.1 100 Continue
>>>> *< HTTP/1.1 201 Created*
>>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>> < Content-Length: 0
>>>> < Server: WSO2 Carbon Server
>>>> <
>>>> * Connection #0 to host localhost left intact
>>>> * Closing connection #0
>>>> * SSLv3, TLS alert, Client hello (1):
>>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
>>>> application/json" -d @'tomcat.json' -k -v -u admin:admin
>>>> https://localhost:9443/api/cartridges
>>>> <https://localhost:9443/api/cartridges>*
>>>> * About to connect() to localhost port 9443 (#0)
>>>> * Trying ::1...
>>>> * connected
>>>> * Connected to localhost (::1) port 9443 (#0)
>>>> * SSLv3, TLS handshake, Client hello (1):
>>>> * SSLv3, TLS handshake, Server hello (2):
>>>> * SSLv3, TLS handshake, CERT (11):
>>>> * SSLv3, TLS handshake, Server key exchange (12):
>>>> * SSLv3, TLS handshake, Server finished (14):
>>>> * SSLv3, TLS handshake, Client key exchange (16):
>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>> * SSLv3, TLS handshake, Finished (20):
>>>> * SSLv3, TLS change cipher, Client hello (1):
>>>> * SSLv3, TLS handshake, Finished (20):
>>>> * SSL connection using DHE-RSA-AES256-SHA
>>>> * Server certificate:
>>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>> * start date: 2010-02-19 07:02:26 GMT
>>>> * expire date: 2035-02-13 07:02:26 GMT
>>>> * common name: localhost (matched)
>>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>>> * SSL certificate verify result: unable to get local issuer
>>>> certificate (20), continuing anyway.
>>>> * Server auth using Basic with user 'admin'
>>>> > POST /api/cartridges HTTP/1.1
>>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>>> OpenSSL/0.9.8r zlib/1.2.5
>>>> > Host: localhost:9443
>>>> > Accept: */*
>>>> > Content-Type: application/json
>>>> > Content-Length: 1166
>>>> > Expect: 100-continue
>>>> >
>>>> < HTTP/1.1 100 Continue
>>>> *< HTTP/1.1 201 Created*
>>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>>> < Content-Length: 0
>>>> < Server: WSO2 Carbon Server
>>>> <
>>>> * Connection #0 to host localhost left intact
>>>> * Closing connection #0
>>>> * SSLv3, TLS alert, Client hello (1):
>>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Mariangela
>>>>
>>>>
>>>>
>>>>
>>>> *--*
>>>> Mariangela Hills
>>>> Senior Technical Writer
>>>>
>>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>>
>>>> w: http://wso2.com
>>>> <http://wso2.com/events/>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Lakmal Warusawithana
> Vice President, Apache Stratos
> Director - Cloud Architecture; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Lakmal Warusawithana <la...@wso2.com>.
On Fri, Jan 23, 2015 at 4:17 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I think with the terminology change "Deploy cartridge" -> "Add cartridge"
> this functionality might not valid. We may need to raise an error if the
> cartridge is already added with the HTTP status code 409.
>
>
And we may need to add "update cartridge" as well.
> Thanks
>
> On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi,
>>
>> When a new cartridge with an existing name is added, it overwrites the
>> existing one. So the behavior you got is the expected behavior.
>>
>> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <ma...@wso2.com>
>> wrote:
>>
>>> I was expecting to get 409 when I added the same cartridge definition
>>> twice, but I did not get an error. Is this meant to be this way?
>>>
>>>
>>>
>>>
>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
>>> application/json" -d @'tomcat.json' -k -v -u admin:admin
>>> https://localhost:9443/api/cartridges
>>> <https://localhost:9443/api/cartridges>*
>>> * About to connect() to localhost port 9443 (#0)
>>> * Trying ::1...
>>> * connected
>>> * Connected to localhost (::1) port 9443 (#0)
>>> * SSLv3, TLS handshake, Client hello (1):
>>> * SSLv3, TLS handshake, Server hello (2):
>>> * SSLv3, TLS handshake, CERT (11):
>>> * SSLv3, TLS handshake, Server key exchange (12):
>>> * SSLv3, TLS handshake, Server finished (14):
>>> * SSLv3, TLS handshake, Client key exchange (16):
>>> * SSLv3, TLS change cipher, Client hello (1):
>>> * SSLv3, TLS handshake, Finished (20):
>>> * SSLv3, TLS change cipher, Client hello (1):
>>> * SSLv3, TLS handshake, Finished (20):
>>> * SSL connection using DHE-RSA-AES256-SHA
>>> * Server certificate:
>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>> * start date: 2010-02-19 07:02:26 GMT
>>> * expire date: 2035-02-13 07:02:26 GMT
>>> * common name: localhost (matched)
>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>> * SSL certificate verify result: unable to get local issuer
>>> certificate (20), continuing anyway.
>>> * Server auth using Basic with user 'admin'
>>> > POST /api/cartridges HTTP/1.1
>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>> OpenSSL/0.9.8r zlib/1.2.5
>>> > Host: localhost:9443
>>> > Accept: */*
>>> > Content-Type: application/json
>>> > Content-Length: 1166
>>> > Expect: 100-continue
>>> >
>>> < HTTP/1.1 100 Continue
>>> *< HTTP/1.1 201 Created*
>>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>> < Content-Length: 0
>>> < Server: WSO2 Carbon Server
>>> <
>>> * Connection #0 to host localhost left intact
>>> * Closing connection #0
>>> * SSLv3, TLS alert, Client hello (1):
>>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
>>> application/json" -d @'tomcat.json' -k -v -u admin:admin
>>> https://localhost:9443/api/cartridges
>>> <https://localhost:9443/api/cartridges>*
>>> * About to connect() to localhost port 9443 (#0)
>>> * Trying ::1...
>>> * connected
>>> * Connected to localhost (::1) port 9443 (#0)
>>> * SSLv3, TLS handshake, Client hello (1):
>>> * SSLv3, TLS handshake, Server hello (2):
>>> * SSLv3, TLS handshake, CERT (11):
>>> * SSLv3, TLS handshake, Server key exchange (12):
>>> * SSLv3, TLS handshake, Server finished (14):
>>> * SSLv3, TLS handshake, Client key exchange (16):
>>> * SSLv3, TLS change cipher, Client hello (1):
>>> * SSLv3, TLS handshake, Finished (20):
>>> * SSLv3, TLS change cipher, Client hello (1):
>>> * SSLv3, TLS handshake, Finished (20):
>>> * SSL connection using DHE-RSA-AES256-SHA
>>> * Server certificate:
>>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>> * start date: 2010-02-19 07:02:26 GMT
>>> * expire date: 2035-02-13 07:02:26 GMT
>>> * common name: localhost (matched)
>>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>>> * SSL certificate verify result: unable to get local issuer
>>> certificate (20), continuing anyway.
>>> * Server auth using Basic with user 'admin'
>>> > POST /api/cartridges HTTP/1.1
>>> > Authorization: Basic YWRtaW46YWRtaW4=
>>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>>> OpenSSL/0.9.8r zlib/1.2.5
>>> > Host: localhost:9443
>>> > Accept: */*
>>> > Content-Type: application/json
>>> > Content-Length: 1166
>>> > Expect: 100-continue
>>> >
>>> < HTTP/1.1 100 Continue
>>> *< HTTP/1.1 201 Created*
>>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>>> < Location: https://localhost:9443/api/cartridges/tomcat
>>> < Content-Length: 0
>>> < Server: WSO2 Carbon Server
>>> <
>>> * Connection #0 to host localhost left intact
>>> * Closing connection #0
>>> * SSLv3, TLS alert, Client hello (1):
>>> Admin16s-MacBook-Air:artifacts Admin16$
>>>
>>>
>>>
>>> Regards,
>>> Mariangela
>>>
>>>
>>>
>>>
>>> *--*
>>> Mariangela Hills
>>> Senior Technical Writer
>>>
>>> *WSO2, Inc.*lean.enterprise.middleware.
>>>
>>> w: http://wso2.com
>>> <http://wso2.com/events/>
>>>
>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Imesh Gunaratne <im...@apache.org>.
I think with the terminology change "Deploy cartridge" -> "Add cartridge"
this functionality might not valid. We may need to raise an error if the
cartridge is already added with the HTTP status code 409.
Thanks
On Fri, Jan 23, 2015 at 3:32 PM, Udara Liyanage <ud...@wso2.com> wrote:
> Hi,
>
> When a new cartridge with an existing name is added, it overwrites the
> existing one. So the behavior you got is the expected behavior.
>
> On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <ma...@wso2.com>
> wrote:
>
>> I was expecting to get 409 when I added the same cartridge definition
>> twice, but I did not get an error. Is this meant to be this way?
>>
>>
>>
>>
>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
>> application/json" -d @'tomcat.json' -k -v -u admin:admin
>> https://localhost:9443/api/cartridges
>> <https://localhost:9443/api/cartridges>*
>> * About to connect() to localhost port 9443 (#0)
>> * Trying ::1...
>> * connected
>> * Connected to localhost (::1) port 9443 (#0)
>> * SSLv3, TLS handshake, Client hello (1):
>> * SSLv3, TLS handshake, Server hello (2):
>> * SSLv3, TLS handshake, CERT (11):
>> * SSLv3, TLS handshake, Server key exchange (12):
>> * SSLv3, TLS handshake, Server finished (14):
>> * SSLv3, TLS handshake, Client key exchange (16):
>> * SSLv3, TLS change cipher, Client hello (1):
>> * SSLv3, TLS handshake, Finished (20):
>> * SSLv3, TLS change cipher, Client hello (1):
>> * SSLv3, TLS handshake, Finished (20):
>> * SSL connection using DHE-RSA-AES256-SHA
>> * Server certificate:
>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>> * start date: 2010-02-19 07:02:26 GMT
>> * expire date: 2035-02-13 07:02:26 GMT
>> * common name: localhost (matched)
>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>> * SSL certificate verify result: unable to get local issuer certificate
>> (20), continuing anyway.
>> * Server auth using Basic with user 'admin'
>> > POST /api/cartridges HTTP/1.1
>> > Authorization: Basic YWRtaW46YWRtaW4=
>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>> OpenSSL/0.9.8r zlib/1.2.5
>> > Host: localhost:9443
>> > Accept: */*
>> > Content-Type: application/json
>> > Content-Length: 1166
>> > Expect: 100-continue
>> >
>> < HTTP/1.1 100 Continue
>> *< HTTP/1.1 201 Created*
>> < Date: Fri, 23 Jan 2015 09:42:24 GMT
>> < Location: https://localhost:9443/api/cartridges/tomcat
>> < Content-Length: 0
>> < Server: WSO2 Carbon Server
>> <
>> * Connection #0 to host localhost left intact
>> * Closing connection #0
>> * SSLv3, TLS alert, Client hello (1):
>> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
>> application/json" -d @'tomcat.json' -k -v -u admin:admin
>> https://localhost:9443/api/cartridges
>> <https://localhost:9443/api/cartridges>*
>> * About to connect() to localhost port 9443 (#0)
>> * Trying ::1...
>> * connected
>> * Connected to localhost (::1) port 9443 (#0)
>> * SSLv3, TLS handshake, Client hello (1):
>> * SSLv3, TLS handshake, Server hello (2):
>> * SSLv3, TLS handshake, CERT (11):
>> * SSLv3, TLS handshake, Server key exchange (12):
>> * SSLv3, TLS handshake, Server finished (14):
>> * SSLv3, TLS handshake, Client key exchange (16):
>> * SSLv3, TLS change cipher, Client hello (1):
>> * SSLv3, TLS handshake, Finished (20):
>> * SSLv3, TLS change cipher, Client hello (1):
>> * SSLv3, TLS handshake, Finished (20):
>> * SSL connection using DHE-RSA-AES256-SHA
>> * Server certificate:
>> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>> * start date: 2010-02-19 07:02:26 GMT
>> * expire date: 2035-02-13 07:02:26 GMT
>> * common name: localhost (matched)
>> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
>> * SSL certificate verify result: unable to get local issuer certificate
>> (20), continuing anyway.
>> * Server auth using Basic with user 'admin'
>> > POST /api/cartridges HTTP/1.1
>> > Authorization: Basic YWRtaW46YWRtaW4=
>> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
>> OpenSSL/0.9.8r zlib/1.2.5
>> > Host: localhost:9443
>> > Accept: */*
>> > Content-Type: application/json
>> > Content-Length: 1166
>> > Expect: 100-continue
>> >
>> < HTTP/1.1 100 Continue
>> *< HTTP/1.1 201 Created*
>> < Date: Fri, 23 Jan 2015 09:50:49 GMT
>> < Location: https://localhost:9443/api/cartridges/tomcat
>> < Content-Length: 0
>> < Server: WSO2 Carbon Server
>> <
>> * Connection #0 to host localhost left intact
>> * Closing connection #0
>> * SSLv3, TLS alert, Client hello (1):
>> Admin16s-MacBook-Air:artifacts Admin16$
>>
>>
>>
>> Regards,
>> Mariangela
>>
>>
>>
>>
>> *--*
>> Mariangela Hills
>> Senior Technical Writer
>>
>> *WSO2, Inc.*lean.enterprise.middleware.
>>
>> w: http://wso2.com
>> <http://wso2.com/events/>
>>
>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: How come I dont get an error when adding the identical cartridge
definition twice?
Posted by Udara Liyanage <ud...@wso2.com>.
Hi,
When a new cartridge with an existing name is added, it overwrites the
existing one. So the behavior you got is the expected behavior.
On Fri, Jan 23, 2015 at 3:28 PM, Mariangela Hills <ma...@wso2.com>
wrote:
> I was expecting to get 409 when I added the same cartridge definition
> twice, but I did not get an error. Is this meant to be this way?
>
>
>
>
> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
> application/json" -d @'tomcat.json' -k -v -u admin:admin
> https://localhost:9443/api/cartridges
> <https://localhost:9443/api/cartridges>*
> * About to connect() to localhost port 9443 (#0)
> * Trying ::1...
> * connected
> * Connected to localhost (::1) port 9443 (#0)
> * SSLv3, TLS handshake, Client hello (1):
> * SSLv3, TLS handshake, Server hello (2):
> * SSLv3, TLS handshake, CERT (11):
> * SSLv3, TLS handshake, Server key exchange (12):
> * SSLv3, TLS handshake, Server finished (14):
> * SSLv3, TLS handshake, Client key exchange (16):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSL connection using DHE-RSA-AES256-SHA
> * Server certificate:
> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
> * start date: 2010-02-19 07:02:26 GMT
> * expire date: 2035-02-13 07:02:26 GMT
> * common name: localhost (matched)
> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
> * SSL certificate verify result: unable to get local issuer certificate
> (20), continuing anyway.
> * Server auth using Basic with user 'admin'
> > POST /api/cartridges HTTP/1.1
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
> OpenSSL/0.9.8r zlib/1.2.5
> > Host: localhost:9443
> > Accept: */*
> > Content-Type: application/json
> > Content-Length: 1166
> > Expect: 100-continue
> >
> < HTTP/1.1 100 Continue
> *< HTTP/1.1 201 Created*
> < Date: Fri, 23 Jan 2015 09:42:24 GMT
> < Location: https://localhost:9443/api/cartridges/tomcat
> < Content-Length: 0
> < Server: WSO2 Carbon Server
> <
> * Connection #0 to host localhost left intact
> * Closing connection #0
> * SSLv3, TLS alert, Client hello (1):
> *Admin16s-MacBook-Air:artifacts Admin16$ curl -X POST -H "Content-Type:
> application/json" -d @'tomcat.json' -k -v -u admin:admin
> https://localhost:9443/api/cartridges
> <https://localhost:9443/api/cartridges>*
> * About to connect() to localhost port 9443 (#0)
> * Trying ::1...
> * connected
> * Connected to localhost (::1) port 9443 (#0)
> * SSLv3, TLS handshake, Client hello (1):
> * SSLv3, TLS handshake, Server hello (2):
> * SSLv3, TLS handshake, CERT (11):
> * SSLv3, TLS handshake, Server key exchange (12):
> * SSLv3, TLS handshake, Server finished (14):
> * SSLv3, TLS handshake, Client key exchange (16):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSL connection using DHE-RSA-AES256-SHA
> * Server certificate:
> * subject: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
> * start date: 2010-02-19 07:02:26 GMT
> * expire date: 2035-02-13 07:02:26 GMT
> * common name: localhost (matched)
> * issuer: C=US; ST=CA; L=Mountain View; O=WSO2; CN=localhost
> * SSL certificate verify result: unable to get local issuer certificate
> (20), continuing anyway.
> * Server auth using Basic with user 'admin'
> > POST /api/cartridges HTTP/1.1
> > Authorization: Basic YWRtaW46YWRtaW4=
> > User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0
> OpenSSL/0.9.8r zlib/1.2.5
> > Host: localhost:9443
> > Accept: */*
> > Content-Type: application/json
> > Content-Length: 1166
> > Expect: 100-continue
> >
> < HTTP/1.1 100 Continue
> *< HTTP/1.1 201 Created*
> < Date: Fri, 23 Jan 2015 09:50:49 GMT
> < Location: https://localhost:9443/api/cartridges/tomcat
> < Content-Length: 0
> < Server: WSO2 Carbon Server
> <
> * Connection #0 to host localhost left intact
> * Closing connection #0
> * SSLv3, TLS alert, Client hello (1):
> Admin16s-MacBook-Air:artifacts Admin16$
>
>
>
> Regards,
> Mariangela
>
>
>
>
> *--*
> Mariangela Hills
> Senior Technical Writer
>
> *WSO2, Inc.*lean.enterprise.middleware.
>
> w: http://wso2.com
> <http://wso2.com/events/>
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897