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

Michel Sumbul edited comment on HDDS-4944 at 4/26/21, 9:20 PM:
---------------------------------------------------------------

I would like to add that in relatively large deployment, it will not be 
possible to dedicate S3G per tenant.
 At large scale, to support a throughput of 3 or 4 Tb/s (or more), the cluster 
admin will have to deploy the S3G on each datanode to use the throughput of 
every network interface, of each server, to spread the load correctly over the 
network.
 If the cluster admin need to double the number of S3G each time a new tenant 
is created, it will absolutely not be viable and a waste of resource.
 The best approach in my opinion for multitenancy at the s3g level is managing 
the umber of request/s or throughput/s


was (Author: msumbul):
I would like to add that in relatively large deployment, it will not be 
possible to dedicate S3G per tenant.
At large scale, to support a throughput of 3 or 4 Tb/s (or more), the cluster 
admin will have to deploy the S3G on each datanode to use the throughput of 
every network interface, of each server, to spread the load correctly on the 
network.
If the cluster admin need to double the number of S3G each time a new tenant is 
created, it will absolutely not be viable and a waste of resource.
The best approach in my opinion for multitenancy at the s3g level is managing 
the umber of request/s or throughput/s

> 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