Re: [Architecture] Operations Center RestAPI
Dear Chaya, is there a pointer to the REST API? I would be interested in its URIs, HTTP methods used on each URI, header fields supported, status codes returned... Thanks! Best regards, Frank 2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2.com: Hi all, After the last review,we came up with a data model for the API. I have attached an initial model of the design and currently the OperationsCenter Rest API is implemented with this new model and following are the new improvements in internal API part. Execute restart command as a cluster wide operation in *round-robin * fashion. - GRACEFUL_RESTART - FORCE_RESTART Execute shut down command on the cluster - GRACEFUL_SHUTDOWN - FORCE_SHUTDOWN Thank you. Regards, Chaya Chaya Sandamali Software Engineering Intern WSo2 Inc Mobile: +94714905772 LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/ ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Operations Center RestAPI
Hi Chaya,
Do we really need OCServer/services/oc-server/external/
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
part
in the URL? In a RESTFull API, every such path element should represent a
resource and also should be nouns.
You can use the /api as the root context, it's how GitHub API designed too.
I suggest /api/clusters instead of /
OCServer/services/oc-server/external/oc/clusters/
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
On Wed, Mar 18, 2015 at 5:44 PM, Chaya Sandamali ch...@wso2.com wrote:
Dear Frank,
With OC portal[1] you can view the topology of the cluster .
(admin/admin). We have currently following URIs with external API.
GET
- [2] - view all cluster data
- [3] - view details of a specific cluster
- [4] - view all server data of a specific cluster
- [5] - view specific sever details
PUT
- [6] -execute cluster wide commands
- [7]- execute commands on a specific server
[1] http://192.168.57.22:9763/sso/login.jag
[2]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
[3]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}
[4]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes
[5]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{nodes-id}
[6]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/commands/{command-id}
[7]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
On Wed, Mar 18, 2015 at 4:48 PM, Frank Leymann fr...@wso2.com wrote:
Dear Chaya,
is there a pointer to the REST API? I would be interested in its URIs,
HTTP methods used on each URI, header fields supported, status codes
returned...
Thanks!
Best regards,
Frank
2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2.com:
Hi all,
After the last review,we came up with a data model for the API. I have
attached an initial model of the design and currently the OperationsCenter
Rest API is implemented with this new model and following are the new
improvements in internal API part.
Execute restart command as a cluster wide operation in *round-robin *
fashion.
- GRACEFUL_RESTART
- FORCE_RESTART
Execute shut down command on the cluster
- GRACEFUL_SHUTDOWN
- FORCE_SHUTDOWN
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Operations Center RestAPI
Dear Frank,
With OC portal[1] you can view the topology of the cluster . (admin/admin).
We have currently following URIs with external API.
GET
- [2] - view all cluster data
- [3] - view details of a specific cluster
- [4] - view all server data of a specific cluster
- [5] - view specific sever details
PUT
- [6] -execute cluster wide commands
- [7]- execute commands on a specific server
[1] http://192.168.57.22:9763/sso/login.jag
[2]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
[3]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}
[4]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes
[5]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{nodes-id}
[6]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/commands/{command-id}
[7]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
On Wed, Mar 18, 2015 at 4:48 PM, Frank Leymann fr...@wso2.com wrote:
Dear Chaya,
is there a pointer to the REST API? I would be interested in its URIs,
HTTP methods used on each URI, header fields supported, status codes
returned...
Thanks!
Best regards,
Frank
2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2.com:
Hi all,
After the last review,we came up with a data model for the API. I have
attached an initial model of the design and currently the OperationsCenter
Rest API is implemented with this new model and following are the new
improvements in internal API part.
Execute restart command as a cluster wide operation in *round-robin *
fashion.
- GRACEFUL_RESTART
- FORCE_RESTART
Execute shut down command on the cluster
- GRACEFUL_SHUTDOWN
- FORCE_SHUTDOWN
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Operations Center RestAPI
Hi Nirmal,
Thank you for the feedback. We are developing OC API as two separate parts
as internal and external where the internal API handles communication
between OC Agent(I am working with internal api) and external API for
communicating with the front end(Cooray is working on this) . So in order
to have a separation of our work we temporarily used the above URIs and
after integrating this we are planning to use a naming convention as you
suggested.
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
On Wed, Mar 18, 2015 at 6:06 PM, Nirmal Fernando nir...@wso2.com wrote:
Hi Chaya,
Do we really need OCServer/services/oc-server/external/
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
part
in the URL? In a RESTFull API, every such path element should represent a
resource and also should be nouns.
You can use the /api as the root context, it's how GitHub API designed too.
I suggest /api/clusters instead of /
OCServer/services/oc-server/external/oc/clusters/
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
On Wed, Mar 18, 2015 at 5:44 PM, Chaya Sandamali ch...@wso2.com wrote:
Dear Frank,
With OC portal[1] you can view the topology of the cluster .
(admin/admin). We have currently following URIs with external API.
GET
- [2] - view all cluster data
- [3] - view details of a specific cluster
- [4] - view all server data of a specific cluster
- [5] - view specific sever details
PUT
- [6] -execute cluster wide commands
- [7]- execute commands on a specific server
[1] http://192.168.57.22:9763/sso/login.jag
[2]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
[3]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}
[4]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes
[5]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{nodes-id}
[6]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/commands/{command-id}
[7]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
On Wed, Mar 18, 2015 at 4:48 PM, Frank Leymann fr...@wso2.com wrote:
Dear Chaya,
is there a pointer to the REST API? I would be interested in its URIs,
HTTP methods used on each URI, header fields supported, status codes
returned...
Thanks!
Best regards,
Frank
2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2.com:
Hi all,
After the last review,we came up with a data model for the API. I have
attached an initial model of the design and currently the OperationsCenter
Rest API is implemented with this new model and following are the new
improvements in internal API part.
Execute restart command as a cluster wide operation in *round-robin *
fashion.
- GRACEFUL_RESTART
- FORCE_RESTART
Execute shut down command on the cluster
- GRACEFUL_SHUTDOWN
- FORCE_SHUTDOWN
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Operations Center RestAPI
Cool.
On Thu, Mar 19, 2015 at 9:42 AM, Chaya Sandamali ch...@wso2.com wrote:
Hi Nirmal,
Thank you for the feedback. We are developing OC API as two separate parts
as internal and external where the internal API handles communication
between OC Agent(I am working with internal api) and external API for
communicating with the front end(Cooray is working on this) . So in order
to have a separation of our work we temporarily used the above URIs and
after integrating this we are planning to use a naming convention as you
suggested.
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
On Wed, Mar 18, 2015 at 6:06 PM, Nirmal Fernando nir...@wso2.com wrote:
Hi Chaya,
Do we really need OCServer/services/oc-server/external/
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
part
in the URL? In a RESTFull API, every such path element should represent a
resource and also should be nouns.
You can use the /api as the root context, it's how GitHub API designed
too.
I suggest /api/clusters instead of /
OCServer/services/oc-server/external/oc/clusters/
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
On Wed, Mar 18, 2015 at 5:44 PM, Chaya Sandamali ch...@wso2.com wrote:
Dear Frank,
With OC portal[1] you can view the topology of the cluster .
(admin/admin). We have currently following URIs with external API.
GET
- [2] - view all cluster data
- [3] - view details of a specific cluster
- [4] - view all server data of a specific cluster
- [5] - view specific sever details
PUT
- [6] -execute cluster wide commands
- [7]- execute commands on a specific server
[1] http://192.168.57.22:9763/sso/login.jag
[2]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/
[3]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}
[4]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes
[5]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{nodes-id}
[6]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/commands/{command-id}
[7]
http://192.168.57.22:9783/OCServer/services/oc-server/external/oc/clusters/{cluster-id}/nodes/{node-id}/commands/{command-id}
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
On Wed, Mar 18, 2015 at 4:48 PM, Frank Leymann fr...@wso2.com wrote:
Dear Chaya,
is there a pointer to the REST API? I would be interested in its URIs,
HTTP methods used on each URI, header fields supported, status codes
returned...
Thanks!
Best regards,
Frank
2015-03-18 9:28 GMT+01:00 Chaya Sandamali ch...@wso2.com:
Hi all,
After the last review,we came up with a data model for the API. I have
attached an initial model of the design and currently the OperationsCenter
Rest API is implemented with this new model and following are the new
improvements in internal API part.
Execute restart command as a cluster wide operation in *round-robin *
fashion.
- GRACEFUL_RESTART
- FORCE_RESTART
Execute shut down command on the cluster
- GRACEFUL_SHUTDOWN
- FORCE_SHUTDOWN
Thank you.
Regards,
Chaya
Chaya Sandamali
Software Engineering Intern
WSo2 Inc
Mobile: +94714905772
LinkedIn: http://lk.linkedin.com/pub/chaya-sandamali/90/694/a59/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Distributed cache support for ESB
Hi Maninda, Yes, we going to support distributed caching between ESB nodes in a single cluster. This cache supports both local mode distributed mode. If (Axis2) clustering is enabled, the cache works as a distributed cache. It is simply using a Hazelcast distributed map per cache. If clustering is not enabled, then the same caching implementation works as a local cache. you can find find further details from[1] [1]. http://blog.afkham.org/2013/11/wso2-multi-tenant-cache-jsr-107-jcache.html Thanks. On Wed, Mar 18, 2015 at 11:27 AM, Maninda Edirisooriya mani...@wso2.com wrote: Are we going to support distributed caching between ESB nodes in a single cluster? Then what about using Hazelcast distributed caching? *Maninda Edirisooriya* Senior Software Engineer *WSO2, Inc.*lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *E-mail* : mani...@wso2.com *Skype* : @manindae *Twitter* : @maninda On Wed, Mar 18, 2015 at 6:52 AM, Vijitha Ekanayake vijit...@wso2.com wrote: Hi all, Current implementation of ESB cache mediator does not support for distributed caching and it uses org.wso2.carbon.caching.core implementation which ships with carbon-qos to provide caching functionalities. Since carbon-qos has already deprecated we need to use better alternative to provide caching in ESB. For that I’m going to implement cache mediator using javax.cache API and use similar synapse configurations currently used. To generate request hash values, I'm going to use REQUESTHASHGenerator instead of currently used DOMHASHGenerator as REQUESTHASHGenerator has implemented to overcome some limitation of the DOMHASHGenerator. cache will be kept in following manner key : requeshHash (request hash of the message) value : CachableResponse (Object which stored the backend response) Any suggestions are appreciated. Thanks. -- Vijitha Ekanayake Software Engineer*, *WSO2, Inc.; http://wso2.com/ Mobile : +94 777 24 73 39 | +94 718 74 44 08 lean.enterprise.middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Vijitha Ekanayake Software Engineer*, *WSO2, Inc.; http://wso2.com/ Mobile : +94 777 24 73 39 | +94 718 74 44 08 lean.enterprise.middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
