Quick start ARM templates that deploy on Microsoft Azure Stack
Перейти к файлу
sumantshiv 83fd264285 Availability set with multiple VMs quick start template. (#230)
* Multiple VMs Availability set quick start template - initial checkin.

* Add Parameters json file.

* Added Metadat json and readme files

* CR feedback addressed.
2017-05-22 16:23:07 -07:00
100-Blank-Template Added a blank starter template (#159) 2016-09-22 16:26:25 -07:00
101-availabilityset-multiplevm-create Availability set with multiple VMs quick start template. (#230) 2017-05-22 16:23:07 -07:00
101-create-dnszones Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-create-nsg 101 create nsg (#166) 2016-10-04 14:16:41 -07:00
101-create-storage-account Vikasnav patch 1 (#189) 2016-11-02 12:58:59 -07:00
101-create-vnet-full Updated apiVersions and removed DNS ref (#168) 2016-10-04 14:45:30 -07:00
101-create-vnet-nsg-only Updated apiVersions and removed DNS ref (#169) 2016-10-04 14:46:27 -07:00
101-create-vnet-only Push changes from develop to master (#155) 2016-09-21 13:33:28 -07:00
101-mysqladapter-add-hosting-server Template for MySql Hosting Server and Database creation template (#231) 2017-05-22 16:22:34 -07:00
101-mysqladapter-create-database Template for MySql Hosting Server and Database creation template (#231) 2017-05-22 16:22:34 -07:00
101-sqladapter-add-hosting-server SQL Adapter RP 101 templates (#223) 2017-04-11 17:15:09 -07:00
101-sqladapter-create-database SQL Adapter RP 101 templates (#223) 2017-04-11 17:15:09 -07:00
101-vm-apply-extension-multiple Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-create-from-customimage Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-linux-apply-extension-customscript Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-linux-apply-extension-docker Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-linux-apply-extension-vmaccess Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-linux-create Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
101-vm-windows-apply-extension-bginfo Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-windows-apply-extension-customscript-cmd Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-windows-apply-extension-customscript-pscmd Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-windows-apply-extension-customscript-sf Fix artifact location. (#227) 2017-05-11 09:50:43 -07:00
101-vm-windows-create Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vm-windows-create-with-extension-diagnostic Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
101-vmss-linux-vm Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
101-vmss-windows-vm VMSS Template for Linux extension and large scale. (#221) 2017-03-29 16:42:46 -07:00
201-vm-linux-comprehensive Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
201-vm-ubuntu-apply-extension-ospatching Changing name of templates to match the pattern 101/201/301-PrimaryResourceName-Linux/Windows-WhatTheTemplateDoes (#225) 2017-05-09 11:05:08 -07:00
201-vm-windows-comprehensive Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
201-vmss-linux-existing-vnet Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
201-vmss-linux-extension Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
201-vmss-linux-vm-largescale Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
201-vmss-scalein-scaleout-existing Fixed names of templates machine the functionality. (#222) 2017-04-12 11:18:46 -07:00
201-vmss-windows-customimage VMSS Template for Linux extension and large scale. (#221) 2017-03-29 16:42:46 -07:00
201-vmss-windows-extension Bug fix for 11699409: [MAS][Workload]deployment<201-vmss-windows-extention> failed, because of (404) not found (#229) 2017-05-16 22:25:05 -07:00
201-vmss-windows-vm-largescale VMSS Template for Linux extension and large scale. (#221) 2017-03-29 16:42:46 -07:00
MicrosoftMonitoringAgent-ext-win Vikasnav patch 1 (#189) 2016-11-02 12:58:59 -07:00
ad-join-domain-ext-win Vikasnav patch 1 (#189) 2016-11-02 12:58:59 -07:00
ad-non-ha Update Default for storage account (#200) 2017-02-23 10:56:09 -08:00
anti-malware-ext-win Vikasnav patch 1 (#189) 2016-11-02 12:58:59 -07:00
bootstorm-vm-boot-time Perf test enchancements (#228) 2017-05-13 12:38:14 -07:00
docker-swarm-ubuntu Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
exchange-2016-non-ha Add metadata.json to all the files 2016-09-22 16:56:49 -07:00
iostorm-vm-iops-latency Perf test enchancements (#228) 2017-05-13 12:38:14 -07:00
jetstress-2013-exchange-loadtest Add report.html for Jetstress 2017-02-08 17:27:10 -08:00
mesos-windows-jumpbox Updating to Linux Ubuntu 16.04. (#226) 2017-05-10 19:20:28 -07:00
mysql-standalone-server-windows Template to create MySQL server of selected version on Windows Server 2017-03-27 12:09:31 -07:00
rds-deployment-existing-ad Add public IP dependencies (#196) 2017-01-27 14:23:16 -08:00
sharepoint-2013-non-ha Update Default for storage account (#200) 2017-02-23 10:56:09 -08:00
sharepoint-2013-non-ha-loadtest Add metadata.json to all the files 2016-09-22 16:56:49 -07:00
sharepoint-2013-sample-loadtest Push changes from develop to master (#164) 2016-09-27 12:05:37 -07:00
sql-2014-non-ha Update Default for storage account (#200) 2017-02-23 10:56:09 -08:00
sql-2014-standalone DSC resources fix 2017-03-29 10:07:51 -07:00
vmaccess-ext-win Vikasnav patch 1 (#189) 2016-11-02 12:58:59 -07:00
vs2013-tcta Update Default for storage account (#200) 2017-02-23 10:56:09 -08:00
README.md TP references 2017-04-13 23:10:28 +02:00
Sample README.md Updated sample based on azure-quickstart 2016-07-05 15:11:46 +02:00

README.md

Microsoft Azure Stack Quickstart Templates

This repository contains Azure Resource Manager deployment templates that have been tested on Microsoft Azure Stack TP3 Refresh.

What repository?

The primary Azure Resource Manager templates repository on GitHub is the azure-quickstart-templates. You can find the repository here https://github.com/Azure/azure-quickstart-templates

Over time many GitHub users have contributed to the repository, resulting in a huge collection of more than 400 deployment templates. This repository is a great starting point to get a better understanding of how you can deploy various kinds of environment to Microsoft Azure. If you scroll through the templates in the azure-quickstart-templates repository, you will notice that there are templates that reference services (resource providers) that are not part of Microsoft Azure Stack TP3 Refresh, such as ExpressRoute or CDN.

To ensure the successful deployment of templates to both Microsoft Azure and Microsoft Azure Stack TP3 Refresh, this temporary GitHub repository AzureStack-quickstart-templates was created. This repository contains samples to test your Microsoft Azure Stack TP3 Refresh environment. Over time, some templates from this temporary repository will be moved to the azure-quickstart-templates repository and this temporary AzureStack-quickstart-templates repository will be depreacated.

If you want to contribute your Azure Resource Manager templates to GitHub, you should make your contribution to the azure-quickstart-templates repository.

Contribution Guide and best practices

The azure-quickstart-templates repository contains a contribution guide and best practices. When you perform a pull-request to the repository, Microsoft will evaluate the code in your pull request based on the guidelines in these documents.

Familiarizing yourself with these documentes, improves the contribution experience.

The contribution guide also explains how to ensure that your deployment template complies with the requirements for it to show up on the gallery in the public Microsoft Azure website.

Azure Resource Manager limitations in Microsoft Azure Stack TP3 Refresh

You can use all kind of template functions within your deployment template. You can find a description of these template functions here: https://azure.microsoft.com/en-us/documentation/articles/resource-group-template-functions/

To ensure that the templates that you create will deploy to both Microsoft Azure and Microsoft Azure Stack TP3 Refresh, you must be aware of a couple of limitations related to Azure Resource Manager in the Microsoft Azure Stack TP3 Refresh. Some functions of Azure Resource Manager are not yet available in this Technical Preview release of Microsoft Azure Stack.

The following template functions are not available in Microsoft Azure Stack Technical Preview yet.

  • skip
  • take

API Versions for Resource Providers

Each resource provider in Microsoft Azure has its own API version. Microsoft Azure Stack TP3 Refresh supports the current API versions for the available resource providers, with some minor exceptions. To ensure your template will succesfully deploy to both Microsoft Azure and Microsoft Azure Stack TP3 Refresh, use the latest API versions that are available in Microsoft Azure Stack TP3 Refresh for all resources in your template. To retrieve a list of the available API versions connect to your Microsoft Azure Stack TP3 Refresh environment by following the Authenticate PowerShell with Microsoft Azure Stack procedure described in this article.

https://azure.microsoft.com/en-us/documentation/articles/azure-stack-deploy-template-powershell/

When you are connected to your environment, you can retrieve a list of the available resource providers and the supported API versions by running the following PowerShell cmdlet

Get-AzureRmResourceProvider | Select ProviderNamespace -Expand ResourceTypes | FT Providernamespace, ResourceTypeName, ApiVersions

This cmdlet can also be used for Microsoft Azure.

Validate existing deployment templates

You can verify if an existing deployment template is valid for a given environment with the Test-AzureRmResourceGroupDeployment PowerShell cmdlet. After connecting to your environment in a PowerShell session run the following PowerShell cmdlet

Test-AzureRmResourceGroupDeployment -ResourceGroupName ExampleGroup -TemplateFile c:\Templates\azuredeploy.json

Please note that this cmdlet does not verify the resource provider specific properties for the resources within the template. This cmdlet can be used for Microsoft Azure and Microsoft Azure Stack TP3 Refresh.

Next steps

Start with creating deployment templates in your own repository. Make sure they deploy to both Microsoft Azure and Microsoft Azure Stack TP3 Refresh, they are in line with the guidelines in the azure-quickstart-templates contribution guide and the guidelines described here. Fork the azure-quickstart-templates repository, add or update and send pull requests to the azure-quickstart-templates. If your templates comply with the requirments they will even show up in the gallery on the public Microsoft Azure website.