KannarFr edited a comment on issue #5723: Quota, retention (macro management) on tenant level. URL: https://github.com/apache/pulsar/issues/5723#issuecomment-559078228 Here is the mailing discussion start - Status: Draft - Author: [Alexandre DUVAL](https://github.com/kannarfr) ([@KannarFR](https://twitter.com/kannarfr)) - Pull request: - Mailing list discussion: - Release: ## Motivation Pulsar quotas, retentions and other policies are defined on namespaces level and only enforced at topic level. It would be great to have global policies on tenant level which can be overriden if policies are lower in namespaces level. The main goal is to provide a tenant for external users and a the way to define namespaces and so on with tenant level policies defined by the tenant provider. ## Proposed changes The tenant's adminRoles property would be used to define the tenant's level policies. Then we will need to add a tenant userRoles which should be able to create namespaces and everything in the tenant that does not exceed the tenants level policies. Then the namespaces policies should inherit from tenant policies with a global verifier for all namespaces to not exceed tenant policies. It wouldn't be too difficult for retention and storage part. We would have to just check periodically on the already supplied brokers load report and get the overall namespace/tenant quota. If quotas exceed, then block producers only (not sure delete exceeded data because of the async block part is a good idea). As said @merlimat, implement rate limiting quotas at tenant or namespace level would be more tricky. WDYT? @merlimat is it ok to be sent on the mailing list?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
