[ 
https://issues.apache.org/jira/browse/HDDS-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Doroszlai resolved HDDS-13098.
-------------------------------------
    Fix Version/s: 2.1.0
       Resolution: Implemented

> Create PicoCLI mixin to standardize datanode selection options
> --------------------------------------------------------------
>
>                 Key: HDDS-13098
>                 URL: https://issues.apache.org/jira/browse/HDDS-13098
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Assignee: Sreeja
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>
> The options to filter datanodes in commands like {{ozone admin datanode 
> usageinfo}} and {{ozone admin datanode decommission}} should be consistent. 
> Right now there are divergences among the various commands, including mixed 
> use of {{\-\-id}} or {{\-\-uuid}} to filter by datanode ID, and commands that 
> only support selection based on host name.
> Create a PicoCLI mixin that provides a standardized set of node selection 
> options that can be re-used for all relevant commands:
>  * {{--node-id}} for datanode UUID
>  ** This is consistent with ID based selection for OM and SCM commands like 
> {{{}ozone admin om decommission{}}}.
>  ** {{--id}} is confusing with the SCM service ID option that some commands 
> also take, which has the short form {{{}-id{}}}.
>  ** {{--uuid}} couples the flag to the ID generation algorithm unnecessarily.
>  * {{--hostname}} for datanode host
>  * {{--ip}} for datanode IP address
> Commands using other selection flags will need to have those flags hidden and 
> deprecated from the CLI while left in place in the code to maintain 
> compatibility.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to