[jira] [Updated] (HDDS-2073) Make SCMSecurityProtocol message based

2019-10-02 Thread Anu Engineer (Jira)


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

Anu Engineer updated HDDS-2073:
---
Fix Version/s: 0.5.0
   Resolution: Fixed
   Status: Resolved  (was: Patch Available)

Committed to the trunk.

> Make SCMSecurityProtocol message based
> --
>
> Key: HDDS-2073
> URL: https://issues.apache.org/jira/browse/HDDS-2073
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: SCM
>Reporter: Marton Elek
>Assignee: Marton Elek
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.5.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> We started to use a generic pattern where we have only one method in the grpc 
> service and the main message contains all the required common information 
> (eg. tracing).
> SCMSecurityProtocol.proto is not yet migrated to this approach. To make our 
> generic debug tool more powerful and unify our protocols I suggest to 
> transform this protocol as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-2073) Make SCMSecurityProtocol message based

2019-09-25 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated HDDS-2073:
-
Labels: pull-request-available  (was: )

> Make SCMSecurityProtocol message based
> --
>
> Key: HDDS-2073
> URL: https://issues.apache.org/jira/browse/HDDS-2073
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: SCM
>Reporter: Elek, Marton
>Assignee: Elek, Marton
>Priority: Major
>  Labels: pull-request-available
>
> We started to use a generic pattern where we have only one method in the grpc 
> service and the main message contains all the required common information 
> (eg. tracing).
> SCMSecurityProtocol.proto is not yet migrated to this approach. To make our 
> generic debug tool more powerful and unify our protocols I suggest to 
> transform this protocol as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-2073) Make SCMSecurityProtocol message based

2019-09-25 Thread Elek, Marton (Jira)


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

Elek, Marton updated HDDS-2073:
---
Status: Patch Available  (was: Open)

> Make SCMSecurityProtocol message based
> --
>
> Key: HDDS-2073
> URL: https://issues.apache.org/jira/browse/HDDS-2073
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: SCM
>Reporter: Elek, Marton
>Assignee: Elek, Marton
>Priority: Major
>
> We started to use a generic pattern where we have only one method in the grpc 
> service and the main message contains all the required common information 
> (eg. tracing).
> SCMSecurityProtocol.proto is not yet migrated to this approach. To make our 
> generic debug tool more powerful and unify our protocols I suggest to 
> transform this protocol as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-2073) Make SCMSecurityProtocol message based

2019-09-02 Thread Elek, Marton (Jira)


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

Elek, Marton updated HDDS-2073:
---
Description: 
We started to use a generic pattern where we have only one method in the grpc 
service and the main message contains all the required common information (eg. 
tracing).

SCMSecurityProtocol.proto is not yet migrated to this approach. To make our 
generic debug tool more powerful and unify our protocols I suggest to transform 
this protocol as well.

  was:
We started to use a generic pattern where we have only one method in the grpc 
service and the main message contains all the required common information (eg. 
tracing).

StorageContainerLocationProtocolService is not yet migrated to this approach. 
To make our generic debug tool more powerful and unify our protocols I suggest 
to transform this protocol as well.


> Make SCMSecurityProtocol message based
> --
>
> Key: HDDS-2073
> URL: https://issues.apache.org/jira/browse/HDDS-2073
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: SCM
>Reporter: Elek, Marton
>Priority: Major
>
> We started to use a generic pattern where we have only one method in the grpc 
> service and the main message contains all the required common information 
> (eg. tracing).
> SCMSecurityProtocol.proto is not yet migrated to this approach. To make our 
> generic debug tool more powerful and unify our protocols I suggest to 
> transform this protocol as well.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org