Windows IISΒΆ

This is an example of a template which launches a stack and deploys a Windows IIS Web Server and SQL Server using Chef. This template has auto scaling and auto healing. You can download it at this link windows_iis_stack_with_chef.yaml. Refer to the Windows IIS (Chef) tutorial in this document for a detailed step by step hands on tutorial which uses this template.

####################################################################################################################################################
# This sample deploys a stack with a Microsoft IIS Server and a SQL Server. This template uses Chef run to install the software on both servers.
# This stack has auto scaling and auto healing.
####################################################################################################################################################
#
# This sample is intended for demonstrating the Blueprint function. It is not intended for "production" use and is unsupported.
# Use it at your own risk.
#
# Note: This Blueprint launches servers from public Windows machine images. You should verify that the machine images still exist before launching.
#
# To run this sample you will need a Chef Account. That Chef Account must be configured in Dell Cloud Manager and the name you defined to it in
# Dell Cloud Manager must match the "chefServer:" value defined in this template.
#
# Refer to the Dell Cloud Manager Blueprint Designer Guide for more details.
# http://blueprint-designer-guide.enstratius.com/tutorials/chef/tutorial11/overview.html
#
####################################################################################################################################################
template_author: Ewan Lyall
template_version: "1.00"
template_name: "Microsoft IIS Two Server Stack using Chef"
description: "Deploys a Windows IIS two server stack using Chef"
long_description: This blueprint deploys a stack with a Microsoft IIS Server and a SQL Server installed on separate Windows 2012 R2 servers.

imports:
  - base_types.yaml                                                   # Import the DCM base type definitions that are referenced in this template

node_types:
    ##################################################################################################################################################
    # This defines a custom node type which will be referenced (inherited from) the two server nodes types below in this template
    ##################################################################################################################################################
    base_vm:
      type: dcm.nodes.Server
      properties:                                                                # Retrieve these server launch properties from the "inputs"
        cloud: { get_input: [account_region_zone_selector, cloud] }              # Retrieve cloud from the AccountRegionSelector
        cloudAccountId: { get_input: [account_region_zone_selector, accountId] } # Retrieve the cloud account ID from the AccountRegionSelector
        region: { get_input: [account_region_zone_selector, region] }            # Retrieve region from the AccountRegionSelector
        zone: { get_input: [account_region_zone_selector, zone] }                # Retrieve zone from the AccountRegionSelector
        platform: { get_input: [product_selector, platform] }                    # Retrieve platform from the Product selector
        architecture: { get_input: [product_selector, architecture] }            # Retrieve architecture from the Product selector
        product: { get_input: [product_selector, product] }                      # Retrieve product from the Product selector
        image: { get_input: [product_selector, image] }                          # Retrieve machine from the Product selector
        serverProductId: { get_input: [product_selector, serverProductId] }      # Retrieve server product id from the Product selector
        startupScript:  |
            ###########################################################################################################################################
            # Install the Dell Cloud Manager agent, point it to the Dell Cloud Manager server and start it.
            ###########################################################################################################################################
            <powershell>

            ###########################################################################################################################################
            # Install the latest Chef Client
            ###########################################################################################################################################
            . { iwr -useb https://omnitruck.chef.io/install.ps1 } | iex; install

            ###########################################################################################################################################
            # Extract the hostname/ip address and port from the DCM variable ${dcm.callback.url}.
            ###########################################################################################################################################
            $callback_url = "${dcm.callback.url}"
            $host_port = ${callback_url}.TrimStart("wss://").TrimEnd("/agentManager").Split(":", 2)
            $host_name = ${host_port}[0]
            $port = ${host_port}[1]
            if (${port} -eq ${null}) {
              $port = 443
            }

            ###########################################################################################################################################
            # Download the DCM Windows Agent
            ###########################################################################################################################################
            Invoke-WebRequest "http://windows.stable.agent.enstratius.com/DCM.Agent.Setup-latest.msi" -OutFile "c:\windows\temp\dcm_agent.msi"

            ###########################################################################################################################################
            # Install the Windows DCM Agent.  Note: the backtick character (`) can be used to split a command in powershell into multiple lines
            ###########################################################################################################################################
            msiexec /i "c:\windows\temp\dcm_agent.msi" /log "c:\windows\temp\dcm_agent_install.log" `
            /q INSTALLFOLDER="c:\Enstratius\" INSTALL_ENVIRONMENT="Staging" SERVER_ADDRESS=${host_name} `
            SERVER_PORT=${port} CLOUD_PROVIDER="Amazon" | Out-Null

            ###########################################################################################################################################
            # Start the DCM Agent
            ###########################################################################################################################################
            start-service DCMAgent
            </powershell>

topology_template:

  inputs:                                                         # Define inputs
    ################################################################################################################################################
    # This defines the AccountRegionSelector which allows the user to select the Cloud, Region and Datacenter
    ################################################################################################################################################
    account_region_zone_selector:                                     # Define the section for the Cloud, Region and Datacenter selection boxes
      type: dcm.inputs.AccountRegionSelector                          # Input type is dcm.inputs.accountRegionSelector
      properties:
        regions:                                                      # Define the Cloud and Regions
          "Amazon":                                                   # Amazon Cloud
            "us-east-1": [ ]                                          # All data centers for the us-east-1 region
            "us-west-1": ["us-west-1a", "us-west-1c"]
            "us-west-2": ["us-west-2a", "us-west-2b", "us-west-2c"]
            "eu-west-1": ["eu-west-1a", "eu-west-1b", "eu-west-1c"]

    ################################################################################################################################################
    # This defines the Product selector which allows the user to select the server product size
    ################################################################################################################################################
    product_selector:                                             # Define the product selector so the user can select the cloud and region
      type: dcm.inputs.Product
      properties:
        accountRegionSelector: account_region_zone_selector       # This connects the AccountRegionSelector to the Product selector
        platform: WINDOWS                                         # Virtual machine images are Windows
        architecture: I64                                         # 64 bit images
        productMappings:
          "Amazon":                                               # Amazon cloud
            "us-east-1":                                          # us-east-1 Region
              image: "ami-3f0c4628"                               # The AWS machine image identitier for the Windows 2012 R2 image in this region
              products: ['t1.micro', 'm1.small', 'm1.medium']     # The virtual machine product sizes for this region
            "us-west-1":                                          # us-west-1 Region
              image: "ami-123c7472"                               # The AWS machine image identitier for the Windows 2012 R2 image in this region
              products: ['t1.micro', 'm1.small', 'm1.medium']     # The virtual machine product sizes for this region
            "us-west-2":                                          # us-west-2 Region
              image: "ami-b871aad8"                               # The AWS machine image identitier for the Windows 2012 R2 image in this region
              products: ['t1.micro', 'm1.small', 'm1.medium']     # The virtual machine product sizes for this region
            "eu-west-1":                                          # eu-west-1 Region
              image: "ami-55084526"                               # The AWS machine image identitier for the Windows 2012 R2 image in this region
              products: ['t1.micro', 'm1.small', 'm1.medium']     # The virtual machine product sizes for this region

  ##################################################################################################################################################
  # This defines the outputs which appear on the DCM console Stack Overview page
  ##################################################################################################################################################
  outputs:                                                        # Define outputs

    application_group:                                            # Create a Group
      type: dcm.outputs.DisplayGroup                              # It's a displayGroup
      properties:
        displayName: "IIS"                                        # Set the display name for the group containing the outputs which appears on the Stack Overview page

    vm_ip:                                                        # Define an output
      type: string                                                # It's a string output
      description: IP of the server                               # Set the description for the string output
      value: {get_attribute: [iis_vm, publicIpAddress]}           # Set the value to the public IP address of the IIS server running in the stack
      properties:
        displayName: Windows IIS Server                           # Set the display name (label) for the string output
        displayGroup: application_group                           # Place this output in the displayGroup named application_group

    link:                                                         # Define another output for the URL of the IIS server
      type: dcm.outputs.Uri                                       # It's a URI output
      value: http://xxxxxxxxxxxxx                                 # Set the initial value
      properties:
        host: {get_attribute: [iis_vm, publicIpAddress]}          # Set the hostname/ipaddress of the URI to the public IP address of the server running in the stack
        displayName: Windows IIS Server URL                       # Set the display name (label) for the URI output
        displayGroup: application_group                           # Place this output in the displayGroup named application_group

    tutorial_group:                                               # Create a Group
      type: dcm.outputs.DisplayGroup                              # It's a displayGroup
      properties:
        displayName: "Blueprint Designer Guide"                   # Set the display name for the group

    tutorial_link:                                                # Define an output
      type: dcm.outputs.Uri                                       # It's a URI output
      value: "http://blueprint-designer-guide.enstratius.com/tutorials/chef/tutorial11/overview.html"
      properties:
        displayName: "Tutorial Link:"                             # Set the display name (label) for the URI output
        displayGroup: tutorial_group                              # Place this output in the displayGroup named application_group

  node_templates:

    ##################################################################################################################################################
    # These node_templates define the host instances
    ##################################################################################################################################################
    sql_vm:
      type: base_vm                                                 # Define the server and inherit the properties from the custom base server node base_vm
      properties:
        name: sql
      requirements:                                                 # This virtual machine node has a requirement on the firewall
        - firewall: vm_firewall_rules
          relationship_type: tosca.relationships.DependsOn

    iis_vm:
      type: base_vm                                                 # Define the server and inherit the properties from the custom base server node base_vm
      properties:
        name: iis
      requirements:                                                 # This virtual machine node has a requirement on the firewall
        - firewall: vm_firewall_rules
          relationship_type: tosca.relationships.DependsOn
        - db: sql_vm
          relationship_type: tosca.relationships.ConnectsTo

    ###################################################################################################################################################
    # These node_templates define the chef roles that will be run on the nodes
    ###################################################################################################################################################
    chef_sql:
      type: dcm.nodes.Chef                                            # This is a Chef node to deploy iis on the iis_vm node
      properties:
        chefServer: "ACME Chef"                                       # Name of the Chef Server Account as defined in Dell Cloud Manager
        environment: "_default"                                       # The chef environment
        roles: ['ACME-IIS-SQL-Server']                                # Chef role which contains the cookbooks and recipes to deploy iis
      requirements:
        - host: sql_vm                                                # This requires (is "HostedOn") the Server defined in the template named sql_vm
          relationship_type: tosca.relationships.HostedOn

    chef_iis:
      type: dcm.nodes.Chef                                            # This is a Chef node to deploy iis on the iis_vm node
      properties:
        chefServer: "ACME Chef"                                       # Name of the Chef Server Account as defined in Dell Cloud Manager
        environment: "_default"                                       # The chef environment
        roles: ['ACME-IIS-Webserver']                                 # Chef role which contains the cookbooks and recipes to deploy iis
      requirements:
        - host: iis_vm                                                # This requires (is "HostedOn") the Server defined in the template named iis_vm
          relationship_type: tosca.relationships.HostedOn
        - db_relationship: chef_sql                                   # It also requires ("DependsOn") the database server to be created
          relationship_type: tosca.relationships.DependsOn

    ###################################################################################################################################################
    # This node_template defines a firewall which opens the HTTP port 80, SQL Port 1443 and RDP port 3389
    ###################################################################################################################################################
    vm_firewall_rules:
      type: dcm.nodes.FirewallGroup                                              # This is a firewall
      properties:                                                                # Retrieve the cloud properties from the "inputs"
        name: "acme-iis-firewall"                                                # Set the firewall name
        cloud: { get_input: [account_region_zone_selector, cloud] }              # Retrieve the cloud from the AccountRegionSelector
        cloudAccountId: { get_input: [account_region_zone_selector, accountId] } # Retrieve the cloud account ID from the AccountRegionSelector
        region: { get_input: [account_region_zone_selector, region] }            # Retrieve the region from the AccountRegionSelector
        zone: { get_input: [account_region_zone_selector, zone] }                # Retrieve the zone from the AccountRegionSelector
        rules:
          - remote_ip_prefix: 0.0.0.0/0
            port: 3389                                                           # Allow port 3389 (RDP) from Anywhere (0.0.0.0/0)
          - remote_ip_prefix: 0.0.0.0/0
            port: 80                                                             # Allow port 80 (HTTP) from Anywhere (0.0.0.0/0)
          - remote_ip_prefix: 0.0.0.0/0
            port: 1433                                                           # Allow port 1433 (SQL) from Anywhere (0.0.0.0/0)

  ###################################################################################################################################################
  # This group defines the auto scaling and auto healing policies for the Apache Web server (vm)
  ###################################################################################################################################################
  groups:
    scaling_and_healing_group:
      members: [iis_vm]                            # The policies in this group apply to the node_template named iis_vm (Windows IIS Web Server)
      properties:
        instances: 1                               # The initial number of servers to start when the stack is started
        minInstances: 1                            # The minimum number of servers
        maxInstances: 5                            # The maximum number of servers
        coolDown: 300                              # The number of seconds to wait before performing a auto scale or auto repair operation.

      policies:
        # This scale up policy will perform a scale up when the last 3 periods of idle time reported are < 20%
        scale_up_on_cpu:
          type: dcm.policy.types.BasicPolicy
          actions: [scale_up]                      # The scale_up action is defined in the actions: section of the template
          measurement: cpu_idle_time               # The cpu_idle_time label is defined in the measurements: section of the template
          criterion: less_than_20                  # The less_than_20 is a label defined in the criteria: section of the template

        # This scale down policy will perform a scale down when the last 2 periods of idle time reported are > 80%
        scale_down_on_cpu:
          type: dcm.policy.types.BasicPolicy
          actions: [scale_down]                    # The scale_down action is defined in the actions: section of the template
          measurement: cpu_idle_time               # The cpu_idle_time label is defined in the measurements: section of the template
          criterion: more_than_80                  # The more_than_80 is a label defined in the criteria: section of the template

        # When the cloud status of a resource is marked not healthy, terminate and restart it
        repair_on_status:
          type: dcm.policy.types.BasicPolicy
          measurement: cloud_reported_status
          criterion: check_fails
          actions: [repair]

      # Actions define the details of the various actions that could be taken.
      actions:
        scale_up:                                  # The scale_up action label is referenced in the policy in the actions[] statement
          type: dcm.policy.action.ScaleUpGroup
          properties:
            instances: 1                           # The number of resources to scale up on a scale_up action
            changeType: ADD                        # Add resource(s) on a scale_up action
            recordTask: RESOURCES_CHANGE           # Check to see if the scale up action would actually create a new resource,
                                                   # or a scale-down operation would actually destroy a resource before creating a task to perform the action.

        scale_down:                                # The scale_down action label is referenced in the policy in the actions[] statement
          type: dcm.policy.action.ScaleDownGroup
          properties:
            instances: 1                           # The number of resources to scale down on a scale_down action
            changeType: REMOVE                     # Remove resource(s) on a scale_down action
            recordTask: ALWAYS                     # Always attempt to perform a scale up or scale down action when the policy determines the actions should occur.
                                                   # Do not check the minInstances and maxInstances limits beforehand.

        repair:                                    # This auto healing action will terminate a degraded resource and then create a new resource
          type: dcm.policy.action.ReplaceResource

      # Measurements define the "measurements" used to determine when to perform the actions
      measurements:
        cpu_idle_time:                             # The cpu_idle_time measurements label is referenced in the policy in a measurements: statement
        # The Dell Cloud Manager agent will collect and store the last 15 samples of cpu %idle time measured in 30-second intervals
          type: dcm.policy.measurement.CpuIdle
          properties:
            period: 30                             # Take a measurement every 30 seconds
            count: 15                              # Take 15 measurements

        # You should include this measurement even if it is not used explicitly by a policy to enable UX health status.
        # The status reported by the cloud must be active, and for VMs the agent heartbeat must succeed,
        # otherwise the resource will be marked as DEGRADED
        cloud_reported_status:
          type: dcm.policy.measurement.ResourceActive

        resource_status:
          type: dcm.policy.measurement.ResourceStatus

      # Criteria specify the "criteria" which is used along with the measurements to determine when to perform the actions
      criteria:
        less_than_20:                              # The less_than_20 criteria label is referenced in the policy in a criterion: statement
          type: dcm.policy.criteria.SeriesLessThan
          properties:
            count: 3                               # 3 consecutive periods
            threshold: 20                          # Threshold is 20%

        more_than_80:                              # The more_than_80 criteria label is referenced in the policy in a criterion: statement
          type: dcm.policy.criteria.SeriesMoreThan
          properties:
            count: 2                               # 2 consecutive periods
            threshold: 80                          # Threshold is 80%

        check_fails:                               # This is the criteria for auto healing
          type: dcm.policy.criteria.False          # "False" tells the policy to perform the action in the policy if the measurement result matches "False".