quads.yml

###############################################
# This is the main configuration file for QUADS
# Configure for your environment
###############################################
#
# spare pool name. e.g. where your unused systems rest
spare_pool_name: cloud01

install_dir: /opt/quads
data_dir: .
# display name for QUADS email notifications
mail_display_name: "QUADS Scheduler"
# set header for User-Agent:
mail_user_agent: "Rufus Postman 1.1.3"
domain: example.com
log: /opt/quads/log/quads.log
quads_base_url: http://127.0.0.1:8080/

# used for reporting
# add your email here to receive copies of notification emails
report_cc: someuser@example.com, someuser@example.com, someuser@example.com, someuser@example.com

# set to true to receive notifications when:
# 1) upon cloud definition for a future workload
# 2) upon passing of validated tests
# 3) 1,3,5,7 days out from when assignment ends
email_notify: true

## email server settings
# this is for your mail relay host
# in containers we use the docker container host itself, you should
# change this to localhost if you want to use the mail relay on the localhost
# and you're not running quads in containers
email_host: 172.16.0.1

# * Note* you'll need Supybot with the notify plugin
# these setting use netcat to send messages to Supybot
irc_notify: true
ircbot_ipaddr: 192.168.0.100
ircbot_port: 5050
ircbot_channel: #yourchannel

# wordpress wiki
wp_wiki: http://wiki.example.com/xmlrpc.php
wp_username: wikiadmin
wp_password: wikipassword

# you will have to know your wordpress page ID for the main and assignment pages
wp_wiki_main_title: Lab Dashboard
wp_wiki_main_page_id: 4
wp_wiki_assignments_title: assignments
wp_wiki_assignments_page_id: 357
# these values are used for auto-generation of a VLAN wiki page markdown
# when routable public VLANs are required (--vlan)
wp_wiki_vlans_title: Public VLAN Allocations
wp_wiki_vlans_page_id: 14244
# optional management of wordpress content via git repo
wp_wiki_git_manage: false
wp_wiki_git_repo_path: /opt/quads/git/wiki

# (optional ticket system URL) in this case we're using JIRA
ticket_url: https://projects.engineering.example.com/browse
# (optional ticket queue name) this is typically the ticket queue
# name or abbreviation in the case of JIRA
ticket_queue: SCALELAB

# this is used in some of the wiki generate for the links
quads_url: http://quads.scalelab.example.com
# url for a request form if you use one
# e.g. http://scalelab.example.com
quads_request_url:

# Deadline day you'd like extension requests for assignments
# to be submitted prior to, e.g. Wednesday
quads_request_deadline_day:

# Foreman Specific Variables
# foreman URL
# set to true of foreman unavailable (useful for testing)
foreman_unavailable: true
foreman_url: http://foreman.example.com/hosts/
foreman_api_url: https://foreman.example.com/api/v2
foreman_username: admin
foreman_password: password
# more foreman settings for your OS, medium, partition table
foreman_default_os: "RHEL 7"
foreman_default_ptable: "generic-rhel7"
foreman_default_medium: "RHEL Local"

# Foreman host health checks
# by setting the Foreman host parameter: broken_state: true
# you can mark certain systems as broken and keep them from being scheduled
# e.g.  hammer host set-parameter --host host01 --name broken_state --value true
# set the following variable to true if you want this functionality
foreman_check_host_health:

# Foreman RBAC fix ignore
# variable to pass cloud names to be excluded from foreman_heal
# with values separated by pipes 'cloud32|cloud04' or singularly 'cloud02'
foreman_rbac_exclude:

# omit these hosts (used for wiki generation)
# These are typically hosts known to your foreman that you don't
# want to pull into the wiki. (this is a regexp, e.g. 'host1|host2')
exclude_hosts: cyclades|s4810|z9000|5548|foreman|c08-h30-r630|c08-h05-r930|b08-|e05-h25|zfs01

# Foreman naming convention is <rack>-<u-location>-<type>
# e.g. c01-h23-r620 is an r620 type host in rack c01 at u-location 23
racks: b09 b10 c01 c02 c03 c04 c05 c06 c07 c08 c09 c10

# this is where we place the generated instackenv.json files
json_web_path: /var/www/html/cloud
# number of days of retaining old .json files
json_retention_days: 0

# Whether or not you want the QUADS host to gather and display ansible facts in
# an HTMl page, you need ansible-cmdb rpm for this functionality which can be
# got from https://github.com/fboender/ansible-cmdb/releases
gather_ansible_facts: false

# this is where we place the generated ansible configuration management database
# html
ansible_facts_web_path: /var/www/html/ansible_facts

# untouchable_hosts are hosts that should be avoided by QUADS in any way.
# use this to define hosts QUADS should never move.
untouchable_hosts: foreman.example.com c08-h30-r630.example.com

# Lab location for use with pass complexity as `{infra_location}@{ticket}`
infra_location: rdu2

# ipmi QUADS admin user/pass
# this is the IPMI account QUADS uses
ipmi_username: root
ipmi_password: password
# ipmi user account
# this is the account you create for users
# to interact with the ipmi
ipmi_cloud_username: quads
ipmi_cloud_password: password
ipmi_cloud_username_id: 4
ipmi_reset_sleep: 10

# This stores the username for connecting to junos switches
junos_username: scaleadmin

# visual web dir is where the visual HTML representation of the lab usage goes
visual_web_dir: /var/www/html/visual

# Note: for nested yaml, two spaces must be used
# for the next level of key/value pairs.
# If the value is 3 numeric values, they are RGB values
# If the first number is -1 then the 2nd value is the name
# of the image file in the visual_web_dir
visual_colors:
  cloud01: "#a9a9a9"
  cloud02: "#e6194B"
  cloud03: "#3cb44b"
  cloud04: "#ffe119"
  cloud05: "#4363d8"
  cloud06: "#f58231"
  cloud07: "#911eb4"
  cloud08: "#42d4f4"
  cloud09: "#bfef45"
  cloud10: "#f032e6"
  cloud11: "#fabebe"
  cloud12: "#469990"
  cloud13: "#e6beff"
  cloud14: "#9A6324"
  cloud15: "#fffac8"
  cloud16: "#800000"
  cloud17: "#aaffc3"
  cloud18: "#808000"
  cloud19: "#e6194B"
  cloud20: "#3cb44b"
  cloud21: "#ffe119"
  cloud22: "#4363d8"
  cloud23: "#f58231"
  cloud24: "#911eb4"
  cloud25: "#42d4f4"
  cloud26: "#bfef45"
  cloud27: "#f032e6"
  cloud28: "#fabebe"
  cloud29: "#469990"
  cloud30: "#e6beff"
  cloud31: "#9A6324"
  cloud32: "#fffac8"
  cloud33: "#800000"
  cloud34: "#aaffc3"
  cloud35: "#808000"
  cloud36: "#e6194B"
  cloud37: "#3cb44b"
  cloud38: "#ffe119"
  cloud39: "#4363d8"
  cloud40: "#f58231"
  cloud41: "#911eb4"
  cloud42: "#42d4f4"
  cloud43: "#bfef45"
  cloud44: "#f032e6"
  cloud45: "#fabebe"
  cloud46: "#469990"
  cloud47: "#e6beff"
  cloud48: "#9A6324"
  cloud49: "#fffac8"
  cloud50: "#800000"

# Do you have managed PDUs?
pdu_management: false

# Openstack variable for generation of instack env json files
# Setting this to false will prevent quads from generating and
# displaying instack env json files on quads wiki
openstack_management: false

# OpenShift variable for generation of inventory files
# Setting this to false will prevent quads from generating and
# displaying ocpinventory files on quads wiki
openshift_management: false

# Validation grace period in minutes
# This gives the validation logic some time for the hosts to complete
# provisioning. Value in minutes.
validation_grace_period: 120

# switch specific config
# sw_vlan_first - The first VLAN ID used for the first interface of cloud01
# this defaults to 1100 unless set otherwise.
sw_vlan_first: 1100

# default behavior is to change wipe back to true when all schedules expire
# Use this carefully! Setting this to False will leave "wipe" behavior alone which
# could cause issues unless you are certain what you are doing.
# In most cases, leave it commented, or set to True
default_wipe: True

# If you're using metadata model / search you want to add any system models
# here.  Please see docs/quads-host-metadata-search.md
models: R620,R630,R640,R930,R730XD,FC640,6018R,6048R,1029U-TRTP,1029U-TN10RT,1029P,5039MS,6049P