blob: 468aab8c18161b2eaa3d9b9886ddfd833b825bef (
plain)
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
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
|
# Copyright © 2017,2019 Amdocs, AT&T , Bell Canada
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#################################################################
#
# These overrides will affect all helm charts (ie. applications)
# that are listed below and are 'enabled'.
#
#
# This is specifically for the environments which take time to
# deploy ONAP. This increase in timeouts prevents false restarting of
# the pods during startup configuration.
#
# These timers have been tuned by the ONAP integration team. They
# have been tested and validated in the ONAP integration lab (Intel/Windriver lab).
# They are however indicative and may be adapted to your environment as they
# depend on the performance of the infrastructure you are installing ONAP on.
#
# Please note that these timers must remain reasonable, in other words, if
# your infrastructure is not performant enough, extending the timers to very
# large value may not fix all installation issues on over subscribed hardware.
#
#################################################################
aai:
liveness:
initialDelaySeconds: 120
aai-champ:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
aai-data-router:
liveness:
initialDelaySeconds: 120
aai-sparky-be:
liveness:
initialDelaySeconds: 120
aai-spike:
liveness:
initialDelaySeconds: 120
aai-cassandra:
liveness:
periodSeconds: 120
readiness:
periodSeconds: 60
cassandra:
liveness:
timeoutSeconds: 30
periodSeconds: 120
readiness:
timeoutSeconds: 30
periodSeconds: 60
holmes:
holmes-rule-mgmt:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
holmes-engine-mgmt:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
dmaap:
dmaap-bus-controller:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
dmaap-dr-prov:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
mariadb:
liveness:
initialDelaySeconds: 180
periodSeconds: 60
dmaap-dr-node:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
mariadb-galera:
liveness:
initialDelaySeconds: 30
periodSeconds: 60
mariadb-galera-server:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
modeling:
mariadb-galera:
liveness:
initialDelaySeconds: 180
periodSeconds: 60
oof:
oof-has:
music:
music-cassandra:
liveness:
periodSeconds: 120
readiness:
periodSeconds: 60
sdc:
sdc-fe:
liveness:
initialDelaySeconds: 120
periodSeconds: 60
timeoutSeconds: 15
readiness:
initialDelaySeconds: 120
periodSeconds: 60
timeoutSeconds: 15
sdc-be:
liveness:
initialDelaySeconds: 120
periodSeconds: 60
timeoutSeconds: 15
readiness:
initialDelaySeconds: 120
periodSeconds: 60
timeoutSeconds: 15
sdc-cs:
liveness:
initialDelaySeconds: 120
periodSeconds: 120
readiness:
initialDelaySeconds: 120
periodSeconds: 60
sdc-es:
liveness:
initialDelaySeconds: 60
readiness:
initialDelaySeconds: 120
sdc-onboarding-be:
liveness:
initialDelaySeconds: 120
periodSeconds: 60
timeoutSeconds: 15
readiness:
initialDelaySeconds: 120
periodSeconds: 60
timeoutSeconds: 15
sdnc:
liveness:
initialDelaySeconds: 60
readiness:
initialDelaySeconds: 60
dmaap-listener:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
mariadb-galera:
liveness:
initialDelaySeconds: 180
periodSeconds: 60
sdnc-ansible-server:
readiness:
initialDelaySeconds: 120
ueb-listener:
liveness:
initialDelaySeconds: 60
readiness:
initialDelaySeconds: 60
so:
liveness:
initialDelaySeconds: 120
mariadb:
liveness:
initialDelaySeconds: 900
readiness:
initialDelaySeconds: 900
uui:
uui-server:
liveness:
initialDelaySeconds: 120
readiness:
initialDelaySeconds: 120
vfc:
mariadb-galera:
liveness:
initialDelaySeconds: 180
periodSeconds: 60
|
