...
When running DHCP servers, the following keys are needed:
| Key | Description | How to create | Data-type | Used by: |
|---|---|---|---|---|
| profile::dhcp::omapi::key | The omapi key used to update the DHCP servers | String | role::bootstrap, role::dhcp | |
| profile::dhcp::omapi::name | The omapi key name | main_key | String | role::bootstrap, role::dhcp |
| profile::dhcp::searchdomain | The default search-domain handed to DHCP clients | String | role::bootstrap, role::dhcp | |
| profile::dns::resolvers | The DNS resolvers for clients to use | List | role::bootstrap, role::dhcp |
profile::dhcp::omapi::key: '<omapi-key>'
profile::dhcp::omapi::name: '<omapi-key-name>'
profile::dhcp::searchdomain: '<default-search-domain>'
- profile::dns::resolvers:
- '<IP-of-DNS-resolver 1>'
- '<IP-of-DNS-resolver 2>'
'<ip-addres-DNS1>' '<ip-address-DNS2>' | List of strings | role::bootstrap, role::dhcp |
DNS DNS server
If you are hosting a DNS server the following keys are needed:
...
profile::dashboard::api: 'http://%{hiera('profile::dashboard::name::v4only')}'
profile::dashboard::datadir: '/var/lib/machineadmin'
profile::dashboard::database::type: 'mysql'
profile::dashboard::database::name: '<mysql-database-name>'
profile::dashboard::database::user: '<mysql-database-user>'
profile::dashboard::database::pass: '<mysql-database-password>'
profile::dashboard::database::host: "%{hiera('profile::haproxy::management::ip')}"
profile::dashboard::database::grant: "%"
profile::dashboard::django::secret: '<pwgen -1 -y -s 50>'
profile::dashboard::ldap::url: 'ldaps://<ldaps-server>:636'
profile::dashboard::ldap::search_base: '<LDAP Search base>'
profile::dashboard::ldap::domain: '<LDAP domain>'
profile::dashboard::name: '<Main dashboard hostname (A and AAAA can be defined for this name)>'
profile::dashboard::name::v4only: '<v4-only dashboard hostname (Should only have an A record defined>'
...