Download to read offline
![Azure Templates can:
• Repeated deployment and consistent
state.
• Simplify Orchestration
• Simplify Roll-back
• Provide unified management and
Update Support.
Azure Templates are:
• Source file, checked-in
• Able to specify resources and
dependencies (VMs, WebSites, DBs) and
connections (config, LB sets)
• Based on parametrized input/output
SQL - A Website
Virtual
Machines
SQL-A
Website
[SQL CONFIG] VM (2x)
DEPENDS ON SQLDEPENDS ON SQL
SQL CONFIG](https://image.slidesharecdn.com/20180421nilfrangab-180502111601/75/My-most-complex-ARM-template-Story-from-the-trenches-7-2048.jpg)
Uploaded byNills Franssens
My most complex ARM template - Story from the trenches
Azure templates can be used to repeatedly deploy resources like VMs, databases and websites in Azure with consistent configuration and connectivity. Templates define the infrastructure and dependencies through parameters and can simplify orchestration, rollbacks and updates. They are JSON files that specify all the resources, properties, and connection details needed to deploy a solution.
More Related Content
Similar to My most complex ARM template - Story from the trenches
My most complex ARM template - Story from the trenches
- 2.
- 5.
- 7. Azure Templates can: •Repeated deployment and consistent state. • Simplify Orchestration • Simplify Roll-back • Provide unified management and Update Support. Azure Templates are: • Source file, checked-in • Able to specify resources and dependencies (VMs, WebSites, DBs) and connections (config, LB sets) • Based on parametrized input/output SQL - A Website Virtual Machines SQL-A Website [SQL CONFIG] VM (2x) DEPENDS ON SQLDEPENDS ON SQL SQL CONFIG
- 8. Simplest structure andelements:
- 9. Note: Parameters areoptional. However, without parameters, your template would always deploy the same resources with the same names, locations, and properties.
- 11.
- 12. Example A valuereturned in the Outputs section.
- 13.
- 20. Qlikdeploy.json Storage account Landscape deploy Commonsettings: - Username - PW - ADJOINpw - Location - vnetID - Subnetref - Storage account - Template URLs - Images - DNSname Unique Parameters: - - environment (dev/test/prod) (COPYINDEX) - Qlikinfo (per env) - Machine sizes - PIP/LB/Avset name - Start ID landscapedeploy.jso n Load balancer private VM deploy Common settings: - Username - PW - ADJOINpw - Location - vnetID - Subnetref - Storage account - Template URLs - Images - DNSname Unique Parameters: - Qlikinfo (per env) (COPYINDEX) - Vmname - Lbid - Lbbackend - Avsetid - Imageid - storageaccountkey VMdeploy.json NIC VM AVSET Load balancer Common Settings Unique settings - Lbname - Pipid - Frontendipid - Lbpoolid - Lbprobeid - subnetref Load balancer public PIP (if PROD) Test/dev private Prod public Nprinting vmnoavsetlb Central/proxy vmavsetlb
- 22.
- 23.