Integrate with Azure Blob Store
ModelOp Center seamlessly integrates with existing Azure Blob Store instances to allow enterprises to leverage existing IT investments in their data platforms.
Table of Contents
Introduction
ModelOp Center provides the ability to integrate with Azure Blob Storage as an external file repository. In other words, when models are imported or assets are uploaded they can be placed in an Azure Blob Storage container.
Azure Blob Storage Overview
Three main components need to be configured to enable the Azure Blob Storage service:
The profile
The external-file-repo-config
BucketInfoList details
The profile
The azure-blob-storage-client profile must be active to make Azure configuration available (note, you may need to add to other active profiles as shown below). Furthermore, you can use mixtures of Azure/S3 and allow different groups to use different stores by configuring the BucketInfoList detail (see below).
spring:
profiles:
active: minio-s3-client,azure-blob-storage-client,aws-s3-client,secured,jwt
The External File Repo Config
Specify the connection settings used by Azure Blob Storage
Property | Details |
|---|---|
| Default Storage Account Name used when there is no match under stored credentials |
| Default Storage Account Key used when there is no match under stored credentials |
| Default Storage Bucket Name used when there is no match under stored credentials |
| Storage Account Name used when there is a path match |
| Storage Account Key used when there is a path match. Note: When using |
| Path used to determine if there is a match for a preferred credential. Values greater in length are checked first against the bucket + “/” + path values of the bucket detail (explained below). Leaving as an empty value catches all values. |
| Alternate Auth Type, default value is |
| (Optional) Port value used in the connection, used for meta data only with Azure |
| (Optional) Secure value used in the connection, used for meta data only with Azure |
| (Optional) Location value used in the connection, used for meta data only with Azure |
| ClientID value, used with Username/Password authentication |
| Username value, used with Username/Password authentication. |
external-file-repo-config:
azure:
azure-defaultStorageAccountName: ****ACCOUNT NAME HERE****
azure-defaultStorageAccountKey: ****KEY HERE****
azure-defaultBucket: modelop
azure-credentials:
storedCredentials:
- storageAccountName: ****ACCOUNT NAME HERE****
storageAccountKey: ****KEY HERE****
path:
//authenticationType: // NOT REQUIRED Username/Password Auth only
//clientId: // NOT REQUIRED Username/Password Auth only
//username: // NOT REQUIRED Username/Password Auth only
s3:
...
BucketList Info Details
When using both S3 and Azure repository you must specify what groups are associated with what storage type, make sure the storageType property is specified in the bucketInfoList detail. If this is not specified, the value will fallback to the default group value, and finally to use the S3_REPOSITORY. Note that only one group can be used per repository. If the same group is specified for several buckeInfoLists the first one will be selected each time.
model-manage:
...
buckets:
bucketInfoList:
- group: modelop
bucket: modelop
path:
storageType: S3_REPOSITORY
- group: azureGroup <== NOTE: Indicates groups associated with Azure storage
bucket: modelop
path:
storageType: AZURE_REPOSITORY <== NOTE: Azure storage type indicated here