Infrastructure & Pillar Examples

# Preface
#
# Customers will be able to log into our GUI and create any number of "Infrastrcutures". 
# They can then add any number of "Sites" to those infrastructures. We will be using the 
# "Infrastructure ID" as part of the naming convention for the minion IDs to keep track of
# what servers belong to what customer account.

# Example: Customer creates an Infrastrcture called "My Infrastructure" that get's a unique 
# id assigned to in my GUI as "123". There will also be another Infrastructure below (Inf ID: 456)
# as an example of how the Pillar Data is mapped.

# Supposed Infrastructure Map (ie. a 2 web node setup)
# Node Naming Convention - inf-<inf-id>-<role>-<role-num>
webserver
  - inf-123-webserver-1 # These 3 belong to one Inf
  - inf-123-webserver-2
  - inf-123-loadbalancer-1
  
  - inf-456-webserver-1 # These 3 belong to another Inf
  - inf-456-webserver-2
  - inf-456-loadbalancer-1
  
# Supposed Pillar Strucutre
'inf-123*':
  sites:
    somesite.com:
      multisite: False
      other_values: etc
    someothersite.com:
      multisite: True
      other_values: etc
      
'inf-456*':
  sites:
    anothersite.com:
      multisite: False
      other_values: etc
    yetanothersite.com:
      multisite: True
      other_values: etc