MS Azure 编辑

When creating layers in an Azure environment, use an MS Azure connector configuration. This article describes the fields included in Azure connector configuration settings. For more about connector configurations and how to add new ones, see Connector configurations.

A connector configuration contains the credentials that the appliance uses to access a specific location in Azure. Your organization can have one Azure account and several storage locations. You need a connector configuration for the appliance to access each storage location.

Note:

This connector is used for publishing layers. Do not use this connector for publishing templates.

Before you create an Azure connector configuration

This section explains:

• The Azure account information required to create this connector configuration.
• The Azure storage you need for App Layering.
• The servers that the appliance communicates with.

Required Azure account information

The Azure connector configuration requires the following information.

• Name - A name you use for a new connector configuration.
• Subscription ID - To deploy Azure virtual machines, your organization must have a subscription ID.
• Tenant ID - An Azure Active Directory instance, this GUID identifies your organization’s dedicated instance of Azure Active Directory (AD).
• Client ID - An identifier for the App Registration, which your organization has created for App Layering.
• Client Secret - The password for the Client ID you are using. If you have forgotten the Client Secret, you can create a one. Note: Client secrets are logically associated with Azure tenants, so each time you use a new subscription and Tenant ID, you must use a new Client Secret.

• Standard Azure storage (required): A storage account for Azure virtual machines (VHD files), the template file that you use to deploy Azure virtual machines, and the boot diagnostics files for the Azure virtual machines. If you specify Premium storage, which is optional, the virtual machines are stored there, and the template and boot diagnostics files remain in Standard storage.

  The storage account must already have been created in the Azure portal, and the name you enter must match the name in the portal. For details, see Set up one or more necessary storage accounts below.

• Premium storage (optional): Optional extra storage for Azure virtual machines (VHD files). Premium storage only supports page blobs and cannot be used to store the template file for deploying Azure virtual machines or the boot diagnostics files for those virtual machines. When you specify a premium storage account, the virtual machine sizes available are limited to those that support premium storage.

  The storage account must already have been created in the Azure portal, and the name you enter must match the name in the portal. For details, see Set up one or more necessary storage accounts below.

Required Azure storage account

Any account you use for App Layering must meet the following requirements:

• Must not be a classic storage account.
• Must be separate from the storage account used for the appliance.
• Must be in the Azure location where you plan to deploy virtual machines.
• Can be located in any resource group, as long as the resource group’s location is the same as the account’s location.

Required Standard storage account

One of the following types of Standard Azure storage accounts is required to create a connector configuration.

• Standard Locally Redundant storage (LRS)
• Standard Geo-Redundant storage (GRS)
• Standard Read-Access Geo-Redundant storage (RAGRS)

When creating the required Standard Storage, enable Blob Public Access for this account. Otherwise, attempts to publish images fail with the error:

"A failure occurred while creating a storage container in the Azure storage account: Public access is not permitted on this storage account."