-
Notifications
You must be signed in to change notification settings - Fork 0
/
example-edge-node-docker-cfg.yaml
274 lines (251 loc) · 9.62 KB
/
example-edge-node-docker-cfg.yaml
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
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
---
#########################################################################################
# Metrics framework configuration
metrics:
# HTTP hosting server configuration
service:
# HTTP server binding interface
listenOn: 0.0.0.0
# HTTP server binding port
appPort: 4001
# Connection timeout configurations in seconds
timeoutSecs:
# Maximum duration for reading the entire request, including the body in seconds.
# A zero or negative value means there will be no timeout.
read: 60
# Maximum duration before timing out writes of the response in seconds. A zero
# or negative value means there will be no timeout.
write: 60
# Maximum amount of time to wait for the next request when keep-alives are enabled
# in seconds. If IdleTimeout is zero, the value of ReadTimeout is used. If both
# are zero, there is no timeout.
idle: 300
# Prometheus metrics endpoint
metricsEndpoint: /metrics
# Max number of metrics requests in parallel to support
maxRequests: 4
# Metrics framework features to enable
features:
# Whether to enable Golang application metrics
enableAppMetrics: false
# Whether to enable HTTP request metrics
enableHTTPMetrics: true
# Whether to enable PubSub metrics
enablePubSubMetrics: true
#########################################################################################
# Video source being monitored
videoSource:
# video source system entry name (as recorded by the system control node)
name: "test-video"
# interval in secs between video source status report to system controller
statusReportIntInSec: 60
#########################################################################################
# Local video cache configuration
cache:
# Cache entry retention check interval in secs
retentionCheckIntInSec: 60
#########################################################################################
# Video source monitor configuration
monitor:
# Playlist receiver REST API configuration
api:
# HTTP hosting server configuration
service:
# HTTP server binding interface
listenOn: 0.0.0.0
# HTTP server binding port
appPort: 9080
# Connection timeout configurations in seconds
timeoutSecs:
# Maximum duration for reading the entire request, including the body in seconds.
# A zero or negative value means there will be no timeout.
read: 60
# Maximum duration before timing out writes of the response in seconds. A zero
# or negative value means there will be no timeout.
write: 60
# Maximum amount of time to wait for the next request when keep-alives are enabled
# in seconds. If IdleTimeout is zero, the value of ReadTimeout is used. If both
# are zero, there is no timeout.
idle: 300
# API endpoint settings
apis:
# Endpoint parameters
endPoint:
# Endpoint path prefix for the APIs
pathPrefix: /
# Request logging parameters
requestLogging:
# Output request logs at this level
logLevel: debug
# HTTP header containing the API request ID
requestIDHeader: X-Request-ID
# List of headers to not include in logging metadata
skipHeaders:
- "WWW-Authenticate"
- "Authorization"
- "Proxy-Authenticate"
- "Proxy-Authorization"
# User can optionally set video segment URI prefix to read segments from.
#
# If this is set, that information does not need to be provided when calling
# POST /v1/playlist
#
# NOTE: This is required on certain versions of ffmpeg (i.e. when -headers does not work)
#defaultSegmentURIPrefix: /path/to/segment/storage/dir
# Tracking window is the duration in time a video segment is tracked. After observing
# a new segment, that segment is remembered for the duration of a tracking window, and
# forgotten after that.
trackingWindow: 60
# Number of worker threads in the video segment reader
segmentReaderWorkerCount: 4
#########################################################################################
# Video Segment Forwarding - supports
# * Live stream proxy
# * Video recording
forwarder:
# Support video recording video segment forwarding to object store
recording:
# Max number of segments to forward in parallel
maxInFlightSegments: 4
# Recording storage config
storage:
# Storage bucket to place all the recording video segments in
bucket: livemix
# Prefix used when defining the object key to store a segment with
objectPrefix: recording-sessions
# S3 object store config
s3:
# S3 server endpoint
endpoint: minio:9000
# Whether to TLS when connecting
useTLS: false
# Support live stream video proxy through the system control node
live:
# Max number of segments to forward in parallel
maxInFlightSegments: 4
# HTTP forwarder target config
remote:
# URL to send new segments to
targetURL: http://livemix-ctrl-node:8081/v1/new-segment
# HTTP Client configuration
#
# The actual client is [resty](https://github.com/go-resty/resty)
client:
# Client retry configuration. See https://github.com/go-resty/resty#retries for details
retry:
# Max number of retry attempts.
maxAttempts: 5
# Wait time before the first wait retry
initialWaitTimeInSec: 5
# Max wait time
maxWaitTimeInSec: 30
#########################################################################################
# Local Live VOD server configuration
vod:
# REST API configuration
api:
# HTTP hosting server configuration
service:
# HTTP server binding interface
listenOn: 0.0.0.0
# HTTP server binding port
appPort: 9081
# Connection timeout configurations in seconds
timeoutSecs:
# Maximum duration for reading the entire request, including the body in seconds.
# A zero or negative value means there will be no timeout.
read: 60
# Maximum duration before timing out writes of the response in seconds. A zero
# or negative value means there will be no timeout.
write: 60
# Maximum amount of time to wait for the next request when keep-alives are enabled
# in seconds. If IdleTimeout is zero, the value of ReadTimeout is used. If both
# are zero, there is no timeout.
idle: 300
# API endpoint settings
apis:
# Endpoint parameters
endPoint:
# Endpoint path prefix for the APIs
pathPrefix: /
# Request logging parameters
requestLogging:
# Output request logs at this level
logLevel: debug
# HTTP header containing the API request ID
requestIDHeader: X-Request-ID
# List of headers to not include in logging metadata
skipHeaders:
- "WWW-Authenticate"
- "Authorization"
- "Proxy-Authenticate"
- "Proxy-Authorization"
# Number of video segments to include when building a live VOD playlist.
liveVODSegmentCount: 2
#########################################################################################
# Local REST API configuration for basic information retrieval
api:
# HTTP hosting server configuration
service:
# HTTP server binding interface
listenOn: 0.0.0.0
# HTTP server binding port
appPort: 9082
# Connection timeout configurations in seconds
timeoutSecs:
# Maximum duration for reading the entire request, including the body in seconds.
# A zero or negative value means there will be no timeout.
read: 60
# Maximum duration before timing out writes of the response in seconds. A zero
# or negative value means there will be no timeout.
write: 60
# Maximum amount of time to wait for the next request when keep-alives are enabled
# in seconds. If IdleTimeout is zero, the value of ReadTimeout is used. If both
# are zero, there is no timeout.
idle: 300
# API endpoint settings
apis:
# Endpoint parameters
endPoint:
# Endpoint path prefix for the APIs
pathPrefix: /
# Request logging parameters
requestLogging:
# Output request logs at this level
logLevel: warn
# HTTP header containing the API request ID
requestIDHeader: X-Request-ID
# List of headers to not include in logging metadata
skipHeaders:
- "WWW-Authenticate"
- "Authorization"
- "Proxy-Authenticate"
- "Proxy-Authorization"
#########################################################################################
# Edge Node PubSub request-response client configuration
requestResponse:
# GCP project to operate in
gcpProject: development
# Number of support workers to spawn to process inbound requests
supportWorkerCount: 2
# Outbound request timeout enforcement check interval in secs
requestTimeoutEnforceIntInSec: 60
# PubSub topic this client listen on for inbound request
self:
# Pubsub topic to subscribe to
topic: local-dev-edge-node
# Message retention within the subscription in secs
msgTTL: 600
# PubSub topic for reaching system control
systemControlTopic: local-dev-ctrl-node
# Max duration for outbound request in secs
outboundRequestDurationInSec: 30
#########################################################################################
# System broadcast channel configuration
broadcast:
# Broadcast PubSub settings
pubsub:
# Broadcast channel PubSub topic
topic: local-dev-system-events
# Message retention within the subscription in secs
msgTTL: 600