Hybrid Defined Datacenter ARM Templates Across Azure and Azure Stack with OMS Integration - Lawrance Reddy

http://www.cloudlogic.expert/single-post/2016/09/05/The-Software-Defined-Datacentre

This repo contains infrastructure as code examples of Hybrid software defined datacenters. From start to finish, these examples are layered and a stepped up approach to building complete scenarios. You are free to download this code and reuse them as you see fit. This codebase is made up of certain snippets from the Azure quickstart templates, but with completely new features and capabilities.

It is important to node that as you use these templates, it is important to understand the syntaxes and parameters required. incorrect parameters used will result in the deployment failing.

In this repository are some examples of Hybrid software defined datacenters.  You will require a valid Azure Subscription to test these deployments. You will also be requested to enter parameters for each deployment. 

These deployments will automatically configure a private network, install the servers and make the appropriate configurations as requested without further input. A total end to end experience.

Certain templates will require configuration of the location, either local for Azure Stack or the appropriate region, eg WestUS for Azure.

Where indicated below, certain features are only available for Azure.

This template deploys a network with a new active directory forest and a domain joined file server. The private network sits behind a firewall. 

This template deploys a new active directory forest with 2 domain controllers of  the same domain. A file server is  also domain joined to this network which is protected behind a firewall.

This template deploys a active directory forest with  multiple domain controllers. It also includes 2 domain  joined web servers. 

This templates creates a active directory forest with  a file  server and automatically creates a custom  share.

This template in addition to creating an active directory forest with a file server, it automatically assigns a custom user to the local users and groups.

This template in addition to creating a virtual machine, will auto create a backup vault and a custom backup policy.

This template in addition to creating a virtual machine, will auto create a backup vault a custom backup policy and will automatically enable data protection. The following define the mandatory backup policy parameters, note that syntax for the arrays need to be exact and enclosed with square brackets.

This template will build a small datacentre, comprising of 2 domain controllers, file server and web servers with a backup vault and the associated policies. DSC configuration does the automation of each tier.

This template will add to the template above by adding automatic data protection to the attached VMs. DSC configuration does the automation of each tier.

Mandatory parameters required to auto configure the backup vault and policy. change the parameters to match whether policy is daily, weekly or other. These parameters below are required for the OMS Backup configuration in Azure at runtime. It is not available for Azure Stack.

"vaultName": "vmbackupvault" "policyName":"MyPolicy"  "scheduleRunDays": ["Monday"]        "scheduleRunTimes": ["2016-09-12T09:00:00.000Z"]              "weeklyRetentionDurationCount": 2  "daysOfTheWeekForMontlyRetention":  ["First"] "weeksOfTheMonthForMonthlyRetention":  ["First"]     "monthlyRetentionDurationCount":  3 "monthsOfYear": ["January"]         "daysOfTheWeekForYearlyRetention": ["Monday"]           "weeksOfTheMonthForYearlyRetention": ["Monday"]           "yearlyRetentionDurationCount":  2 "skuName": "Standard"

Mandatory parameters required to automatically configure the backup of the VMs being protected. use  these as parameters or variables. These parameters below are required to integrate existing workloads into Azure backup. Azure Stack does not natively have Backup features or capabilities and as such these workloads will integrate into Azure Backup.

 protection container  iaasvmcontainer;iaasvmcontainerv2;my-resource-group;my-arm-vm   protectable item  vm;iaasvmcontainerv2;my-resource-group;my-arm-vm  resource ids /subscriptions/subscriptionid/resourceGroups/resourceGroupName/p  roviders/Microsoft.Compute/virtualMachines/my-arm-vm

This template will build the following, It will also complete OMS integration as well as build full site to site connectivity. That is 6 servers + 1 firewall + 1 load-balancer + different classification of storage + the operating systems + 2 domain controllers fully configured. + 2 web servers + code +2 file servers + shares + distributed name space +  backup vault + backup policy + automatic protection + performance monitoring + site to site connectivity.

The following is required for Azure Stack or Azure workloads needing OMS Log Analytic integration into an OMS workspace. The Workspace ID and Workspace Key is required to integrate workloads into Azure OMS. OMS is not natively available for Azure Stack and therefore these workloads will integrate into an existing OMS workspace.

{ "name": "Microsoft.EnterpriseCloud.Monitoring", "type": "extensions",

            "settings": {
               "workspaceId": "[parameters('workspaceId')]"
                },
                "protectedSettings": {
                    "workspaceKey": "[parameters('workspaceKey')]"