Deploy the MySQL resource provider on Azure Stack
Use the MySQL Server resource provider to expose MySQL databases as an Azure Stack service. The MySQL resource provider runs as a service on a Windows Server 2016 Server Core virtual machine (VM).
Only the resource provider is supported to create items on servers that host SQL or MySQL. Items created on a host server that are not created by the resource provider might result in a mismatched state.
There are several prerequisites that need to be in place before you can deploy the Azure Stack MySQL resource provider. To meet these requirements, complete the steps in this article on a computer that can access the privileged endpoint VM.
If you haven't already done so, register Azure Stack with Azure so you can download Azure marketplace items.
You must install the Azure and Azure Stack PowerShell modules on the system where you will run this installation. That system must be a Windows 10 or Windows Server 2016 image with the latest version of the .NET runtime. See Install PowerShell for Azure Stack.
Add the required Windows Server core VM to the Azure Stack marketplace by downloading the Windows Server 2016 Datacenter - Server Core image.
Download the MySQL resource provider binary and then run the self-extractor to extract the contents to a temporary directory.
To deploy the MySQL provider on a system that doesn't have Internet access, copy the mysql-connector-net-6.10.5.msi file to a local path. Provide the path name using the DependencyFilesLocalPath parameter.
The resource provider has a minimum corresponding Azure Stack build.
Minimum Azure Stack version MySQL RP version Version 1808 (1.1808.0.97) MySQL RP version 22.214.171.124 Version 1808 (1.1808.0.97) MySQL RP version 126.96.36.199 Version 1804 (1.0.180513.1) MySQL RP version 188.8.131.52
Ensure datacenter integration prerequisites are met:
Prerequisite Reference Conditional DNS forwarding is set correctly. Azure Stack datacenter integration - DNS Inbound ports for resource providers are open. Azure Stack datacenter integration - Publish endpoints PKI certificate subject and SAN are set correctly. Azure Stack deployment mandatory PKI prerequisitesAzure Stack deployment PaaS certificate prerequisites
For integrated systems installations only. You must provide the SQL PaaS PKI certificate described in the optional PaaS certificates section of Azure Stack deployment PKI requirements. Place the .pfx file in the location specified by the DependencyFilesLocalPath parameter. Do not provide a certificate for ASDK systems.
Deploy the resource provider
After you've installed all the prerequisites, you can run the DeployMySqlProvider.ps1 script to deploy the MySQL resource provider. The DeployMySqlProvider.ps1 script is extracted as part of the MySQL resource provider installation files that you downloaded for your version of Azure Stack.
Before deploying the resource provider, review the release notes to learn about new functionality, fixes, and any known issues that could affect your deployment.
To deploy the MySQL resource provider, open a new elevated PowerShell window (not PowerShell ISE) and change to the directory where you extracted the MySQL resource provider binary files. We recommend using a new PowerShell window to avoid potential problems caused by PowerShell modules that are already loaded.
Run the DeployMySqlProvider.ps1 script, which completes the following tasks:
- Uploads the certificates and other artifacts to a storage account on Azure Stack.
- Publishes gallery packages so that you can deploy MySQL databases using the gallery.
- Publishes a gallery package for deploying hosting servers.
- Deploys a VM using the Windows Server 2016 core image you downloaded, and then installs the MySQL resource provider.
- Registers a local DNS record that maps to your resource provider VM.
- Registers your resource provider with the local Azure Resource Manager for the operator account.
When the MySQL resource provider deployment starts, the system.local.mysqladapter resource group is created. It may take up to 75 minutes to finish the deployments required to this resource group.
You can specify these parameters from the command line. If you don't, or if any parameter validation fails, you're prompted to provide the required parameters.
|Parameter name||Description||Comment or default value|
|CloudAdminCredential||The credential for the cloud administrator, necessary for accessing the privileged endpoint.||Required|
|AzCredential||The credentials for the Azure Stack service admin account. Use the same credentials that you used for deploying Azure Stack.||Required|
|VMLocalCredential||The credentials for the local administrator account of the MySQL resource provider VM.||Required|
|PrivilegedEndpoint||The IP address or DNS name of the privileged endpoint.||Required|
|AzureEnvironment||The Azure environment of the service admin account used for deploying Azure Stack. Required only for Azure AD deployments. Supported environment names are AzureCloud, AzureUSGovernment, or if using a China Azure AD, AzureChinaCloud.||AzureCloud|
|DependencyFilesLocalPath||For integrated systems only, your certificate .pfx file must be placed in this directory. For disconnected environments, download mysql-connector-net-6.10.5.msi to this directory. You can optionally copy one Windows Update MSU package here.||Optional (mandatory for integrated systems or disconnected environments)|
|DefaultSSLCertificatePassword||The password for the .pfx certificate.||Required|
|MaxRetryCount||The number of times you want to retry each operation if there is a failure.||2|
|RetryDuration||The timeout interval between retries, in seconds.||120|
|Uninstall||Removes the resource provider and all associated resources (see the following notes).||No|
|DebugMode||Prevents automatic cleanup on failure.||No|
|AcceptLicense||Skips the prompt to accept the GPL license. https://www.gnu.org/licenses/old-licenses/gpl-2.0.html|
Deploy the MySQL resource provider using a custom script
To eliminate any manual configuration when deploying the resource provider, you can customize the following script. Change the default account information and passwords as needed for your Azure Stack deployment.
# Install the Azure and Azure Stack PowerShell modules as described in the prerequisites section above before running these commands. # Use the NetBIOS name for the Azure Stack domain. On the Azure Stack SDK, the default is AzureStack but could have been changed at install time. $domain = "AzureStack" # For integrated systems, use the IP address of one of the ERCS virtual machines. $privilegedEndpoint = "AzS-ERCS01" # Provide the Azure environment used for deploying Azure Stack. Required only for Azure AD deployments. Supported environment names are AzureCloud, AzureUSGovernment, or AzureChinaCloud. $AzureEnvironment = "<EnvironmentName>" # Point to the directory where the resource provider installation files were extracted. $tempDir = 'C:\TEMP\MYSQLRP' # The service admin account (can be Azure Active Directory or Active Directory Federation Services). $serviceAdmin = "firstname.lastname@example.org" $AdminPass = ConvertTo-SecureString "P@ssw0rd1" -AsPlainText -Force $AdminCreds = New-Object System.Management.Automation.PSCredential ($serviceAdmin, $AdminPass) # Set the credentials for the new resource provider VM local administrator account $vmLocalAdminPass = ConvertTo-SecureString "P@ssw0rd1" -AsPlainText -Force $vmLocalAdminCreds = New-Object System.Management.Automation.PSCredential ("mysqlrpadmin", $vmLocalAdminPass) # And the cloudadmin credential required for privileged endpoint access. $CloudAdminPass = ConvertTo-SecureString "P@ssw0rd1" -AsPlainText -Force $CloudAdminCreds = New-Object System.Management.Automation.PSCredential ("$domain\cloudadmin", $CloudAdminPass) # Clear the existing login information from the Azure PowerShell context. Clear-AzureRMContext -Scope CurrentUser -Force Clear-AzureRMContext -Scope Process -Force # Change the following as appropriate. $PfxPass = ConvertTo-SecureString "P@ssw0rd1" -AsPlainText -Force # Change to the directory folder where you extracted the installation files. Do not provide a certificate on ASDK! . $tempDir\DeployMySQLProvider.ps1 ` -AzCredential $AdminCreds ` -VMLocalCredential $vmLocalAdminCreds ` -CloudAdminCredential $cloudAdminCreds ` -PrivilegedEndpoint $privilegedEndpoint ` -AzureEnvironment $AzureEnvironment ` -DefaultSSLCertificatePassword $PfxPass ` -DependencyFilesLocalPath $tempDir\cert ` -AcceptLicense
When the resource provider installation script finishes, refresh your browser to make sure you can see the latest updates.
Verify the deployment by using the Azure Stack portal
- Sign in to the admin portal as the service administrator.
- Select Resource Groups
- Select the system.<location>.mysqladapter resource group.
- On the summary page for Resource group Overview, there should be no failed deployments.
- Finally, select Virtual machines in the admin portal to verify that the MySQL resource provider VM was successfully created and is running.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.