pvc-ansible/group_vars/default/base.yml

159 lines
5.4 KiB
YAML
Raw Normal View History

---
# The name of the Ansible cluster group, used to set file paths and determine hosts in the cluster
# This should match the lowest-level group in the Ansible `hosts` file that defines this cluster
cluster_group: default
2020-01-06 11:33:47 -05:00
# Local timezone for the cluster
timezone_location: Canada/Eastern
# Cluster domain for node FQDNs
local_domain: upstream.local
2021-10-11 14:41:29 -04:00
# DNS recursive servers and search domains for nodes
recursive_dns_servers:
- 8.8.8.8
- 8.8.4.4
recursive_dns_search_domains:
- "{{ local_domain }}"
2021-06-29 17:48:55 -04:00
# Cluster hardware model, used in pvc_user_configuration and grub_configuration below
cluster_hardware: default
# Debian package repository URL
2021-04-08 14:15:11 -04:00
debian_main_repository: http://ftp.debian.org/debian
debian_security_repository: http://security.debian.org
debian_pvc_repository: https://repo.parallelvirtualcluster.org/debian
# Root user password
# > Use pwgen to generate
root_password: ""
2021-06-29 17:48:55 -04:00
# GRUB configuration
# > Generally this is a good default, though some systems use console 1 for serial-over-IPMI
# consoles, so set this based on your actual hardware.
grub:
serial_console:
"default":
console: 0
# IPMI configuration
# > For the "pvc" user password, use pwgen to generate.
# > Set the "pvc"user with permissions in IPMI to reboot the host as this user will be use for
# any fencing operations.
# > Set the IP networking to match your expected IPMI configuration.
ipmi:
users:
admin:
username: "root"
password: "{{ root_password }}"
pvc:
username: "host"
password: ""
hosts:
2021-06-06 00:53:14 -04:00
"pvchv1": # Use the inventory hostname here
2021-06-06 00:41:34 -04:00
hostname: pvchv1-lom # A valid short name (e.g. from /etc/hosts) or an FQDN must be
# used here; PVC connects to this *hostname* for fencing.
address: 192.168.100.101
netmask: 255.255.255.0
gateway: 192.168.100.1
2021-06-06 00:53:14 -04:00
"pvchv2": # Use the inventory hostname here
2021-06-06 00:41:34 -04:00
hostname: pvchv2-lom # A valid short name (e.g. from /etc/hosts) or an FQDN must be
# used here; PVC connects to this *hostname* for fencing.
address: 192.168.100.102
netmask: 255.255.255.0
gateway: 192.168.100.1
2021-06-06 00:53:14 -04:00
"pvchv3": # Use the inventory hostname here
2021-06-06 00:41:34 -04:00
hostname: pvchv3-lom # A valid short name (e.g. from /etc/hosts) or an FQDN must be
# used here; PVC connects to this *hostname* for fencing.
address: 192.168.100.103
netmask: 255.255.255.0
gateway: 192.168.100.1
# IPMI user configuration
# > Adjust this based on the specific hardware you are using; the cluster_hardware variable is
# used as the key in this dictionary.
# > If you run multiple clusters with different hardware, it may be prudent to move this to an
# 'all' group_vars file instead.
ipmi_user_configuration:
"default":
channel: 1
admin:
id: 1
role: 0x4 # ADMINISTRATOR
username: "{{ ipmi['users']['admin']['username'] }}"
password: "{{ ipmi['users']['admin']['password'] }}"
pvc:
id: 2
role: 0x4 # ADMINISTRATOR
username: "{{ ipmi['users']['pvc']['username'] }}"
password: "{{ ipmi['users']['pvc']['password'] }}"
# Log rotation configuration
logrotate_keepcount: 7
logrotate_interval: daily
# Root email name (usually "root")
username_email_root: root
# Hosts entries
hosts:
- name: test
ip: 127.0.0.1
# Administrative shell users for the cluster
admin_users:
- name: "myuser"
uid: 500
keys:
- "ssh-ed25519 MyKey 2019-06"
2021-06-05 02:06:36 -04:00
# Backup user SSH user keys, for remote backups separate from administrative users (e.g. rsync)
# > Uncomment to activate this functionality.
#backup_keys:
# - "ssh-ed25519 MyKey 2019-06"
# Node network definitions (used by /etc/network/interfaces and PVC)
# > The "type" can be one of three NIC types: "nic" for raw NIC devices, "bond" for ifenslave bonds,
# or "vlan" for vLAN interfaces. The PVC role will write out an interfaces file matching these specs.
# > Three names are reserved for the PVC-specific interfaces: upstream, cluster, and storage; others
# may be used at will to describe the other devices.
# > All devices should be using the newer device name format (i.e. enp1s0f0 instead of eth0).
# > In this example configuration, the "upstream" device is an LACP bond of the first two onboard NICs,
# with the two other PVC networks being vLANs on top of this device.
# > Usually, the Upstream network provides Internet connectivity for nodes in the cluster, and all
# nodes are part of it regardless of function for this reason; an optional, advanced, configuration
# will have only coordinators in the upstream network, however this configuration is out of the scope
# of this role.
networks:
"upstream":
device: "bondU"
type: "bond"
bond_mode: "802.3ad"
bond_devices:
- "enp1s0f0"
- "enp1s0f1"
mtu: 1500
domain: "{{ local_domain }}"
2019-12-24 14:15:14 -05:00
netmask: "24"
subnet: "192.168.100.0"
floating_ip: "192.168.100.10"
gateway_ip: "192.168.100.1"
"cluster":
device: "vlan1001"
type: "vlan"
raw_device: "bondU"
mtu: 1500
domain: "pvc-cluster.local"
2019-12-24 14:15:14 -05:00
netmask: "24"
subnet: "10.0.0.0"
floating_ip: "10.0.0.254"
"storage":
device: "vlan1002"
type: "vlan"
raw_device: "bondU"
mtu: 1500
domain: "pvc-storage.local"
2019-12-24 14:15:14 -05:00
netmask: "24"
subnet: "10.0.1.0"
floating_ip: "10.0.1.254"