Skip to content

Provide provider selection based on "region" #766

@BigLep

Description

@BigLep

Done Criteria

There are ways to select or filter SPs based on criteria, where one of the expected ways is on "region". As example, a consumer should be able express that they want their dataset to be created in the "EU".

Why Important

SP "region" location is a proxy for various things like:

  • performance (e.g., locality between client and SP)
  • data governance rules (e.g., EU GDPR)
  • availability (e.g., I want to make this data easily globally accessible, thus I want to make sure it's in "regions" around the world)

Currently, Synapse by default will select any approved SP, regardless of its geographic location.

User/Customer

TBD for which customers are directly requesting this. We do expect it will come given traditional clouds expose this primitive.

Notes

  1. This requires design before any engineering work is done. At the minimum, we would want to see a proposal for what APIs are being modified how, but we may also want to step back and think about a more general "bring-your-own SP selector" model and we document "here’s how you can do your own SP filtering based on your criteria"
  1. We don't think this is an immediate problem to solve for GA, in part because there aren't many approved SPs, and no launch partners have denoted it as blocker.
  2. In the short term, the most important to address may be China vs not-China, not a rich regional model, especially if any China SPs ever get approved as they accentuate connectivity/performance concerns for those outside China. For example, may be default exclude China but offer an opt-in / boolean for China.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    🐱 Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions