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

Arpit Agarwal edited comment on HDDS-4944 at 4/26/21, 3:24 PM:
---------------------------------------------------------------

bq. I think we couldn't compete with existing secret managers, and I think we 
shouldn't.
bq. bq. This is where the mentioned pro/con comparisons are really missing (for 
me) from the current design / available information. Those informations might 
be discussed internally, but they are unavailable for me (or I just didn't get 
it).
Weren't you involved in the original design of S3 support? Why wasn't this 
option explored then and why is it being brought up in the context of 
multi-tenancy? Ozone Manager already stores S3 secrets today, so coupling 
secret manager to the multi-tenancy is puzzling to me.


was (Author: arpitagarwal):
bq. I think we couldn't compete with existing secret managers, and I think we 
shouldn't.
bq. bq. This is where the mentioned pro/con comparisons are really missing (for 
me) from the current design / available information. Those informations might 
be discussed internally, but they are unavailable for me (or I just didn't get 
it).
Weren't you involved in the original design of S3 support? Why wasn't this 
option explored then and why is it being brought up in the context of 
multi-tenancy? Ozone Manager already stores S3 secrets today, so coupling 
secret manager to the multi-tenancy is puzzling to me.


Secret management 

> Multi-Tenant Support in Ozone
> -----------------------------
>
>                 Key: HDDS-4944
>                 URL: https://issues.apache.org/jira/browse/HDDS-4944
>             Project: Apache Ozone
>          Issue Type: New Feature
>          Components: Ozone CLI, Ozone Datanode, Ozone Manager, Ozone Recon, 
> S3, SCM, Security
>    Affects Versions: 1.2.0
>            Reporter: Prashant Pogde
>            Assignee: Prashant Pogde
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: Apache-S3-compatible-Multi-Tenant-Ozone-short.pdf.gz, 
> Ozone MultiTenant Feature _ Requirements and Abstractions-3.pdf, Ozone, 
> Multi-tenancy, S3, Kerberos....pdf, UseCaseAWSCompatibility.pdf, 
> UseCaseCephCompatibility.pdf, UseCaseConfigureMultiTenancy.png, 
> UseCaseCurrentOzoneS3BackwardCompatibility.pdf, 
> VariousActorsInteractions.png, uml_multitenant_interface_design.png
>
>
> This Jira will be used to track a new feature for Multi-Tenant support in 
> Ozone. Initially Multi-Tenant feature would be limited to ozone-users 
> accessing Ozone over S3 interface.



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

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

Reply via email to