Multi-tenancy as a new capability. #143
Open
+309
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prasann
requested changes
Jan 20, 2025
scenarios/workload-genai/policies/multi-tenancy/multi-tenant-product1-policy.xml
Outdated
Show resolved
Hide resolved
scenarios/workload-genai/policies/multi-tenancy/multi-tenant-product1-policy.xml
Outdated
Show resolved
Hide resolved
scenarios/workload-genai/policies/multi-tenancy/multi-tenant-product1-policy.xml
Outdated
Show resolved
Hide resolved
scenarios/workload-genai/policies/multi-tenancy/multi-tenant-product2-policy.xml
Show resolved
Hide resolved
prasann
approved these changes
Jan 22, 2025
done testing. working as expected. |
…xisting rate limiter policies
RussSmi
approved these changes
Feb 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a PR for having multi-tenancy as a new capability in the GenAI Backend scenario(Scenario 3).
Following issue describes the context in more detail -
#142
As part of demonstration of multi-tenancy capability,
We are creating 2 example multi-tenancy products with reference to existing OpenAI API , we will apply a new quota policy at the product level, such that if the number of requests to APIM via that product's subscription exceed as per the defined "calls" attribute's value, then the product policy will accordingly block the subsequent requests from that subscription until the quota is refreshed based on the defined "renewal-period" and "counter-key" attribute, everything else in the existing setup stays the same.
For example-
Following 2 new products will now be created:
with their own respective quota policies.
both linked to the existing OpenAI API:
& their corresponding subscriptions:
Finally, now as part of our scripts deployment output we will get 2 additional subscriptions for our multi-tenant products for the user to test the same.
Summary of changeset in this PR:
Both Bicep and Terraform scripts have been tested and seem to be working fine without any impact.