1 |
tamasb |
2971 |
### ENVIRONMENT SPECIFIC INFORMATION ### |
2 |
|
|
### ### |
3 |
|
|
### Usually you would override these using a variables include ### |
4 |
|
|
### file, using the vars_files include in your play. These ### |
5 |
|
|
### varabales include, for example, passwords, secrets and other ### |
6 |
|
|
### environment specific information ### |
7 |
|
|
|
8 |
tamasb |
3117 |
# Trust root for the host credential. It can be provided either |
9 |
|
|
# via an rpm package or a PEM formatted file together with a |
10 |
|
|
# signing policy. The two options are not exclusive, and can |
11 |
|
|
# be used independently of eachother. |
12 |
|
|
|
13 |
|
|
# Name of the rpm package to install as trust anchor. This ca be |
14 |
|
|
# a link to an rpm or a package name from an installed repository |
15 |
|
|
hostcred_trust_anchor_package: "ca_TERENA-eScience-SSL-CA-3" |
16 |
|
|
|
17 |
|
|
# Alternatively, the trust anchor can be installed from a PEM |
18 |
|
|
# formatted certificate file accompanied by the signign policy |
19 |
|
|
#hostcred_trust_anchor_pem: "cacert.pem" |
20 |
|
|
#hostcred_trust_anchor_signing_policy: "cacert.signing_policy" |
21 |
|
|
|
22 |
tamasb |
2971 |
# NTP Server |
23 |
|
|
ntp_servers: |
24 |
|
|
- ntp1.server.com |
25 |
|
|
- ntp2.server.com |