-
Notifications
You must be signed in to change notification settings - Fork 18
/
pillar.example
150 lines (140 loc) · 7.23 KB
/
pillar.example
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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
hana:
# optional: Install required rpm packages to install SAP HANA (true by default),
# e.g. SAP Notes 2892356 and 3029056.
# This will be taken care of by `patterns-sap-hana` in SLES4SAP environments.
# If set to false, these packages must be installed manually before the formula
# execution.
# install_packages: true
# saptune solution to apply to all nodes ( by default nothing is applied)
# you can also use this to a single node if need to differ. see hana2
# Warning: only a unique solution can exist into a node.
saptune_solution: 'HANA'
# HANA installation media can be provided in one of the two methods: extracted HANA platform folder or HANA media archive
# 1. Path to an already extracted HANA platform installation media. This will have preference over hana installation media archive
software_path: '/sapmedia/HANA/51052481'
# 2. Or specify the path to the hana installation media archive
# If using hana sar archive, please also provide compatible version of sapcar executable
# The archive will be extracted to path specified at hana_extract_dir (optional, by default /sapmedia_extract/HANA)
# hana_extract_dir should be a new directory and separated from the location where the compressed files are present, to avoid conflicts in file permissions.
hana_archive_file: '/sapmedia/51053492.ZIP'
hana_extract_dir: '/sapmedia_extract/HANA'
# HANA Client packages are needed for monitoring & cost-optimized scenario. HANA Client is already included in HANA platform media unless a HANA database sar archive is used
# If the HANA archive used for installation is sar format specified above, you need to provide HANA Client in one of the two ways: extracted HANA client folder or HANA client sar archive file
# If any of the next two options are used, this HANA Client will have preference over the HANA Client coming in the HANA platform described above. If HANA platform is used, it is usually better to
# not use the HANA Client as it might bring some compatibility issue.
# 1. Path to already extracted hana client folder
#hana_client_software_path: '/sapmedia/IMDB_CLIENT'
# 2. Or specify the path to the hana client sar archive file. It will be extracted to hana_client_extract_dir path (optional, by default /sapmedia_extract/HANA_CLIENT)
hana_client_archive_file: '/sapmedia/IMDB_CLIENT20_003_144-80002090.SAR'
hana_client_extract_dir: '/sapmedia_extract/HANA_CLIENT'
#If using a sar archive for hana platform or hana client media, please provide compatible version of sapcar executable
#sapcar_exe_file: '/sapmedia/SAPCAR'
# Enable HA cluster configuration. It installs the SAPHanaSR hook.
# To use this option the primary and secondary nodes must be defined in the pillar file
ha_enabled: true
# optional: enables monitoring via hanadb_exporter (disabled by default)
# the exporter will be installed and configured in all the nodes
# you can customize the exporter configuration in each node in the dedicated sections below
monitoring_enabled: true
# HANA HA/DR provider configuration
# See https://documentation.suse.com/sbp/all/single-html/SLES4SAP-hana-sr-guide-PerfOpt-15/#cha.s4s.hana-hook for details.
# The SAPHanaSR hook is always enabled.
# enable susTkOver hook (disabled by default)
#ha_dr_sustkover_enabled: true
# enable susChkSrv hook (disabled by default)
#ha_dr_suschksrv_enabled: true
# susChkSrv action on lost, see `man 7 susChkSrv.py` (Options: stop [default], fence)
#ha_dr_suschksrv_action_on_lost: 'fence'
nodes:
- host: 'hana01'
sid: 'prd'
instance: 00
password: 'Qwerty1234'
install:
# Specify the path to local installation media here, otherwise global variable software_path will be used for installation media.
# If both of these paths are not set, hana_extract_dir path will be used for installation media,
# given that hana_archive_file package is also provided
#software_path: '/sapmedia/HANA/51052481'
root_user: 'root'
root_password: 's'
# Fetch HANA passwords from XML file
hdb_pwd_file: 'salt://passwords.xml'
# Or specify HANA system & sapadm users' passwords like below
system_user_password: 'Qwerty1234'
sapadm_password: 'Qwerty1234'
# You can also provide additional hana configuration parameters as done in the following example
# See https://help.sap.com/viewer/2c1988d620e04368aa4103bf26f17727/2.0.00/en-US/c16432a77b6144dcb75aace2b4fcacff.html
# for details on all the supported parameters
extra_parameters:
# As an example, this parameter allows to ignore some prerequisite tests
ignore: check_min_mem
# Primary SAP HANA System Replication site
primary:
name: NUREMBERG
userkey:
key_name: 'backupkey'
environment: 'hana01:30013'
user_name: 'SYSTEM'
user_password: 'Qwerty1234'
database: 'SYSTEMDB'
# Take a backup on the primary SAP HANA System Replication site (prerequisite for SR)
backup:
# Set key_name or user_name/user_password combination
key_name: 'backupkey'
# Or
user_name: 'SYSTEM'
user_password: 'Qwerty1234'
database: 'SYSTEMDB'
file: 'backup'
# hanadb_exporter configuration
# only applies when monitoring_enabled is true
exporter:
exposition_port: 9668 # Optional, 9668 by default
multi_tenant: true # Enable the exporter as multi tenant. This will create the connection with the SYSTEMDB database and all tenants
user: 'SYSTEM'
password: 'Qwerty1234'
#port: 30015 # HANA database port. If multi_tenant is set this value is 3XX13 by default where XX is the instance number
timeout: 30 # Timeout in seconds to start the connection with HANA database
- host: 'hana02'
sid: 'prd'
instance: 00
password: 'Qwerty1234'
saptune_solution: 'MAXDB'
install:
software_path: '/sapmedia/HANA/51052481'
root_user: 'root'
root_password: 's'
system_user_password: 'Qwerty1234'
sapadm_password: 'Qwerty1234'
# Secondary SAP HANA System Replication site
secondary:
name: PRAGUE
remote_host: 'hana01'
remote_instance: '00'
replication_mode: 'sync'
operation_mode: 'logreplay'
# For Active/Active HANA setup
#operation_mode: 'logreplay_readaccess'
# If primary node is not defined the password can we set here (primary node password has preference)
#primary_password: 'Qwerty1234'
# Optional timeout value in seconds to wait until the primary node
# 100 seconds by default
primary_timeout: 100
scenario_type: 'cost-optimized'
cost_optimized_parameters:
global_allocation_limit: '32100'
preload_column_tables: False
- host: hana02
sid: 'qas'
instance: 01
password: 'Qwerty1234'
install:
software_path: '/sapmedia/HANA/51052481'
root_user: 'root'
root_password: 's'
system_user_password: 'Qwerty1234'
sapadm_password: 'Qwerty1234'
exporter:
exposition_port: 9669 # Optional, 9668 by default
user: 'SYSTEM'
password: 'Qwerty1234'