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

Feature Request - Azure Support for DMS Installer #155

Open
andricDu opened this issue Aug 12, 2021 · 1 comment
Open

Feature Request - Azure Support for DMS Installer #155

andricDu opened this issue Aug 12, 2021 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@andricDu
Copy link

As Score supports using Azure as the backing object store, the DMS installer should be able to provide the option for running against an Azure storage account.

Detailed Description

  • Even though Song/Score can run in Azure and utilize the capabilities of blob storage in Azure, the DMS installer does not provide a way for end users configuring their installation to point it to an azure storage account.
  • This would be useful as it would allow users who are already using Azure to use the DMS
  • @prbatero from Microsoft suggested they could even point users looking for DMS-like solutions to Overture.bio

Possible Implementation

  • Implement a question in installer asking if users would like S3 or Azure Storage for Score
    • In the case of azure storage, they will need to provide storage account, an account secret, and the access policies for reads and writes to be assigned the Shared Access Signatures (Azure equivalent to S3 Presigned URL)
  • Update documentation to reflect these new options and what they refer to
@andricDu andricDu added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Aug 12, 2021
@b-f-chan
Copy link
Contributor

Thanks @andricDu. Regarding the params you mentioned above, would the DMS installer need to use the Create Container operation in the Azure Blob Service REST API?

The request headers accept an account name, a signature (which seems is the storage account key/secret), and level of access. But I'm not sure if it's the exact endpoint you were referring to:

https://docs.microsoft.com/en-us/rest/api/storageservices/create-container

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants