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 <[email protected]> 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 <[email protected]> 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 <[email protected]>: >> >>> 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 >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > 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 [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
