concerted-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijayakumar Ramdoss (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONCERTED-3) Concerted API defining
Date Tue, 20 Oct 2015 12:42:27 GMT

    [ https://issues.apache.org/jira/browse/CONCERTED-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965045#comment-14965045
] 

Vijayakumar Ramdoss commented on CONCERTED-3:
---------------------------------------------

As per Gaurav, Can we start with below set of the REST APIs to access the system,

Server nodes API
	The Server Nodes REST API manages nodes in a cluster.
Views API
	The Views REST API is used to query the data.
Logs API
	The logs REST API retrieving the log and diagnostic information.
User API
	The read-only user can be created.



> Concerted API defining
> ----------------------
>
>                 Key: CONCERTED-3
>                 URL: https://issues.apache.org/jira/browse/CONCERTED-3
>             Project: Apache Concerted
>          Issue Type: New Feature
>            Reporter: Atri Sharma
>            Assignee: Atri Sharma
>
> A decision needs to be taken on Concerted's API that will be exposed to clients.
> The API should be allowing direct access to resource managers, transaction manager, lock
manager(?) etc
> The API will help define development policy and process for adding a new resource manager
or component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message