Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Region based routing (per end-user) #3524

Closed
Tracked by #3513 ...
krrishdholakia opened this issue May 8, 2024 · 6 comments · Fixed by #3536
Closed
Tracked by #3513 ...

Region based routing (per end-user) #3524

krrishdholakia opened this issue May 8, 2024 · 6 comments · Fixed by #3536

Comments

@krrishdholakia
Copy link
Contributor

krrishdholakia commented May 8, 2024

Specific users need to have all their llm api calls be within eu

Allow something like this:

curl --location 'http://0.0.0.0:4000/end_user/new' \
--header 'Authorization: Bearer sk-1234' \ # 👈 Master Key
--header 'Content-Type: application/json' \
--data '{
      "end_user_id" : "ishaan-jaff-3", <- specific customer
    
    "allowed_region": "eu" <- set region for models        

             + 

    "default_model": "azure/gpt-3.5-turbo-eu" <- all calls from this user, use this model? 

}'

# return end-user object
@krrishdholakia
Copy link
Contributor Author

Currently covers:

  • Azure
  • Vertex AI
  • Bedrock

@krrishdholakia
Copy link
Contributor Author

Expose - get_provider_region() helper function

@krrishdholakia
Copy link
Contributor Author

Expose CRUD endpoints for end-users

  • create
  • info
  • update
  • delete

@krrishdholakia
Copy link
Contributor Author

for v0 - scoping to just create + info

@krrishdholakia
Copy link
Contributor Author

Add a pre-call check to filter models by region

@krrishdholakia
Copy link
Contributor Author

How to get model region?

  • on set_client -> make a blank request to azure deployments -> the headers return the rate limits + region info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant