ec2_name_prefix: TRAINING
ec2_security_group: insecure_all
ec2_region: us-east-1
ec2_vpc_id: "{{ ec2_regions[ec2_region].vpc }}"
ec2_vpc_subnet_id: "{{ ec2_regions[ec2_region].subnet_id }}"
ec2_key_name: "{{ ec2_regions[ec2_region].key_name }}"
ec2_exact_count: 1
ec2_wait: yes

ec2_lab_node_types:
  - name: control
    type: rhel7

  - name: node1
    type: rhel7

  - name: node2
    type: rhel7

  - name: node3
    type: rhel7

  - name: haproxy
    type: rhel7


ec2_name_prefix: TRAINING
ec2_security_group: insecure_all
ec2_region: us-east-1
ec2_vpc_id: "{{ ec2_regions[ec2_region].vpc }}"
ec2_vpc_subnet_id: "{{ ec2_regions[ec2_region].subnet_id }}"
ec2_key_name: "{{ ec2_regions[ec2_region].key_name }}"
ec2_exact_count: 1
ec2_wait: yes

ec2_lab_node_types:
  - name: control
    type: rhel7-tower

  - name: node1
    type: rhel7

  - name: node2
    type: rhel7

  - name: node3
    type: rhel7

  - name: haproxy
    type: rhel7


Change default control node to rhel7-tower
Change default control node to rhel7-tower

This creates an instance big enough to have Tower installed, but does not actually spin up an instance with Tower installed on RHEL since no such AMI exists.

It would probably be good to come up with a less confusing name for this instance since the centos7-tower type does indeed have Tower already installed.

Fixes issue #98.
