Configuring Your Zone¶
This step entails the creation of your Occam configuration files. The configuration files use hiera - a key/value lookup tool for configuration data - built to make Puppet better and let you set node-specific data without repeating yourself. Hiera loads the hierarchy from the hiera.yaml config file.
Occam’s hiera lookup table has the following precedence:
| Hiera Precedence | Usage | 
|---|---|
| local/secrets/ | This used as the password file. The password file is an encryted gpg file. | 
| local/fqdns/%{::fqdn} | This is where the network interface definitions for the ops and ctrl nodes are stored. | 
| local/zones/ | This is where the deployment target information is stored. | 
| local/hostgroups/%{::hostgroup} | This is used to define the dns and dhcp for the target deployment. | 
| users/users_occam | Managed users and groups definitions. | 
| occam | Occamengine specific configurations. | 
Note: The following represent example hiera files. They may be used as a reference. You can name your zone anything.
Secrets¶
Example secrets file: secrets/zone1.yaml
fqdn¶
Example ops node file: ops1.zone1.example.com.yaml
Example ctrl node file: ctrl1.zone1.example.com.yaml
Example monit node file: monit1.zone1.example.com.yaml
Users¶
Example users file: users.yaml
Occam¶
Example occam file: occam.yaml