forked from redhat-cop/agnosticd
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathsample_vars.yml
39 lines (31 loc) · 1.51 KB
/
sample_vars.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
---
# sample vars configuration file
#
# This file is passed to ansible-playbook to set key vars which need to be set
# and typically customized for a sucessful deployment.
#
# Usage: ansible-playbook main.yml -e @configs/three-tier-app/sample_vars.yml
#
# Ideally make and keep a copy OUTSIDE your repo, especially if using Cloud Credentials
# Credentials can also be set seperately i.e. ~/secrets.yml and passed in with
# a 2nd `-e` argument i.e. -e ~/secrets.yml
env_type: three-tier-app # Name of config to deploy
output_dir: /tmp/workdir # Writable working scratch directory
email: [email protected] # User info for notifications
guid: guid01 # Your Global UNIQUE Identifier
subdomain_base_suffix: .example.opentlc.com # Your domain used with guid in FQDN
# Path to your yum repos
own_repo_path: http://admin.example.com/repos/version
# Cloud specfic settings - example given here for AWS
cloud_provider: ec2 # Which AgnosticD Cloud Provider to use
aws_region: us-east-1 # AWS Region to deploy in
HostedZoneId: Z3IHLWJZOU9SRT # You will need to change this
key_name: ocpkey # Keyname must exist in AWS
# AWS Credentials. These are required (don't sync them to your fork)
#
# Alternatively consider keeping these in an external file and including:
# $ ansible-playbook main.yml -e @configs/three-tier-app/sample.yml -e @~/secret.yml
#
# aws_access_key_id:
# aws_secret_access_key:
# ...