-
Notifications
You must be signed in to change notification settings - Fork 536
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
Move Storage Urls from Tenant Metadata to Service Level #9849
Move Storage Urls from Tenant Metadata to Service Level #9849
Conversation
server/routerlicious/packages/routerlicious-base/src/riddler/runnerFactory.ts
Outdated
Show resolved
Hide resolved
server/routerlicious/packages/routerlicious-base/src/riddler/runnerFactory.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we are changing/introducing some configurations in the config.json from Historian and Routerlicious, we will probably also have to update the configmaps for Kubernetes:
Routerlicious:
https://github.com/microsoft/FluidFramework/blob/main/server/routerlicious/kubernetes/routerlicious/templates/fluid-configmap.yaml
server/historian/packages/historian-base/src/services/restGitService.ts
Outdated
Show resolved
Hide resolved
server/routerlicious/packages/routerlicious-base/src/alfred/runnerFactory.ts
Outdated
Show resolved
Hide resolved
server/routerlicious/kubernetes/routerlicious/templates/fluid-configmap.yaml
Outdated
Show resolved
Hide resolved
server/routerlicious/kubernetes/routerlicious/templates/fluid-configmap.yaml
Outdated
Show resolved
Hide resolved
Resolve Conflicts: # server/historian/packages/historian-base/src/routes/utils.ts # server/routerlicious/packages/services/src/tenant.ts
We are going to map the storage.internalHistorianUrl, and storage.url to each service/cluster, instead of let them be the attributes from the tenant metadata.
Previously, these two urls are based on each tenant. The drawback is that one tenant can be shared by different clusters. These clusters might use different storage.internalHistorianUrls and storage.urls. Thus, the tenant metadata can only store one pair of these urls which cannot satisfy all of the clusters.