Igniters,
I'd like to propose a new internal cluster management API that will simplify new cluster management commands creation and expose new commands to CLI, REST, JMX Ignite interfaces without any additional actions from the engineer adding a new command. This main goal of the IEP is supposed to be available after the implementation of the 1-st phase. From my point of view, the implementation will also provide some additional features like auto ASCII-docs generation which can be achieved with minor code changes. Please, take a look at the IEP-81 [1] with a detailed explanation of my proposal. Below you can find some crucial points from it. = Current Limitations = - The same commands through CLI, REST, JMX APIs don't have the same input arguments and use different subsystems for command execution; - A new command that is added must be manually exposed to all the Ignite APIs (new implementation required for each new command being added); - New commands can't be added via Ignite Plugins and exposed to API; - The own binary protocol is used (GridClient) for command executions instead of the ignite thin client (IgniteClient); - Security and role model: a user have to add compute tasks permissions the same time as adding permissions for the process he intended to use. - New commands can't be added or executed at runtime = Crutial Impelemntation Notes = 1. Create a one for all proxy compute task gate that will accept a map of parameters for preparing management command based on input parameters and executing it on ignite nodes. For instance: IgniteClient.compute().execute(ProxyManagementTask.class.getName(), attrs); Map: baseline.add=execute baseline.add.projection=SINGLE baseline.add.nodes=[consistendtId3, consistendeId4] 2. Create a CommandRegisty that will contain all available commanded on the local ignite node. Commands will be added by command scanners e.g. AnnotationCommandScanner, PackageCommandScanner, URICommandScanner as well as registered manually at runtime by calling `add` method on command registry. The CommandRegistry will also be available for the thin clients in a standalone mode. 3. Prepare a command parsers for REST, JMX, CLI interfaces that will use command registry and calling the proxy management task right away with correct task input parameters. 4. Check the API [2] for commands that may be executed only on a single node (the same as the VisorOneNodeTask) or on all nodes e.g. collecting some information from each node and reducing it on a originating node. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-81+Cluster+Management+API [2] https://cwiki.apache.org/confluence/display/IGNITE/IEP-81+Cluster+Management+API#IEP81ClusterManagementAPI-CommandInterface
