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
|
job "${job_name}" {
# The "region" parameter specifies the region in which to execute the job.
# If omitted, this inherits the default region name of "global".
# region = "global"
#
# The "datacenters" parameter specifies the list of datacenters which should
# be considered when placing this task. This must be provided.
datacenters = "${datacenters}"
# The "type" parameter controls the type of job, which impacts the scheduler's
# decision on placement. This configuration is optional and defaults to
# "service". For a full list of job types and their differences, please see
# the online documentation.
#
# https://www.nomadproject.io/docs/jobspec/schedulers
#
type = "service"
update {
# The "max_parallel" parameter specifies the maximum number of updates to
# perform in parallel. In this case, this specifies to update a single task
# at a time.
max_parallel = 1
health_check = "checks"
# The "min_healthy_time" parameter specifies the minimum time the allocation
# must be in the healthy state before it is marked as healthy and unblocks
# further allocations from being updated.
min_healthy_time = "10s"
# The "healthy_deadline" parameter specifies the deadline in which the
# allocation must be marked as healthy after which the allocation is
# automatically transitioned to unhealthy. Transitioning to unhealthy will
# fail the deployment and potentially roll back the job if "auto_revert" is
# set to true.
healthy_deadline = "3m"
# The "progress_deadline" parameter specifies the deadline in which an
# allocation must be marked as healthy. The deadline begins when the first
# allocation for the deployment is created and is reset whenever an allocation
# as part of the deployment transitions to a healthy state. If no allocation
# transitions to the healthy state before the progress deadline, the
# deployment is marked as failed.
progress_deadline = "10m"
%{ if use_canary }
# The "canary" parameter specifies that changes to the job that would result
# in destructive updates should create the specified number of canaries
# without stopping any previous allocations. Once the operator determines the
# canaries are healthy, they can be promoted which unblocks a rolling update
# of the remaining allocations at a rate of "max_parallel".
#
# Further, setting "canary" equal to the count of the task group allows
# blue/green deployments. When the job is updated, a full set of the new
# version is deployed and upon promotion the old version is stopped.
canary = 1
# Specifies if the job should auto-promote to the canary version when all
# canaries become healthy during a deployment. Defaults to false which means
# canaries must be manually updated with the nomad deployment promote
# command.
auto_promote = true
# The "auto_revert" parameter specifies if the job should auto-revert to the
# last stable job on deployment failure. A job is marked as stable if all the
# allocations as part of its deployment were marked healthy.
auto_revert = true
%{ endif }
}
# All groups in this job should be scheduled on different hosts.
constraint {
operator = "distinct_hosts"
value = "true"
}
# The "group" stanza defines a series of tasks that should be co-located on
# the same Nomad client. Any task within a group will be placed on the same
# client.
#
# https://www.nomadproject.io/docs/job-specification/group
#
group "prod-group1-minio" {
# The "count" parameter specifies the number of the task groups that should
# be running under this group. This value must be non-negative and defaults
# to 1.
count = ${group_count}
# https://www.nomadproject.io/docs/job-specification/volume
%{ if use_host_volume }
volume "prod-volume1-minio" {
type = "host"
read_only = false
source = "${host_volume}"
}
%{ endif }
# The restart stanza configures a tasks's behavior on task failure. Restarts
# happen on the client that is running the task.
#
# https://www.nomadproject.io/docs/job-specification/restart
#
restart {
interval = "30m"
attempts = 40
delay = "15s"
mode = "delay"
}
# The "task" stanza creates an individual unit of work, such as a Docker
# container, web application, or batch processing.
#
# https://www.nomadproject.io/docs/job-specification/task.html
#
task "prod-task1-minio" {
# The "driver" parameter specifies the task driver that should be used to
# run the task.
driver = "docker"
%{ if use_host_volume }
volume_mount {
volume = "prod-volume1-minio"
destination = "${data_dir}"
read_only = false
}
%{ endif }
%{ if use_vault_provider }
vault {
policies = "${vault_kv_policy_name}"
}
%{ endif }
# The "config" stanza specifies the driver configuration, which is passed
# directly to the driver to start the task. The details of configurations
# are specific to each driver, so please see specific driver
# documentation for more information.
config {
image = "${image}"
dns_servers = [ "172.17.0.1" ]
network_mode = "host"
command = "server"
args = [ "${host}:${port}${data_dir}" ]
port_map {
http = ${port}
}
privileged = false
}
# The env stanza configures a list of environment variables to populate
# the task's environment before starting.
env {
%{ if use_vault_provider }
{{ with secret "${vault_kv_path}" }}
MINIO_ACCESS_KEY = "{{ .Data.data.${vault_kv_field_access_key} }}"
MINIO_SECRET_KEY = "{{ .Data.data.${vault_kv_field_secret_key} }}"
{{ end }}
%{ else }
MINIO_ACCESS_KEY = "${access_key}"
MINIO_SECRET_KEY = "${secret_key}"
%{ endif }
${ envs }
}
# The service stanza instructs Nomad to register a service with Consul.
#
# https://www.nomadproject.io/docs/job-specification/service
#
service {
name = "${service_name}"
port = "http"
tags = [ "storage$${NOMAD_ALLOC_INDEX}" ]
check {
name = "Min.io Server HTTP Check Live"
type = "http"
port = "http"
protocol = "http"
method = "GET"
path = "/minio/health/live"
interval = "10s"
timeout = "2s"
}
check {
name = "Min.io Server HTTP Check Ready"
type = "http"
port = "http"
protocol = "http"
method = "GET"
path = "/minio/health/ready"
interval = "10s"
timeout = "2s"
}
}
# The "resources" stanza describes the requirements a task needs to
# execute. Resource requirements include memory, network, cpu, and more.
# This ensures the task will execute on a machine that contains enough
# resource capacity.
#
# https://www.nomadproject.io/docs/job-specification/resources
#
resources {
cpu = ${cpu}
memory = ${memory}
# The network stanza specifies the networking requirements for the task
# group, including the network mode and port allocations. When scheduling
# jobs in Nomad they are provisioned across your fleet of machines along
# with other jobs and services. Because you don't know in advance what host
# your job will be provisioned on, Nomad will provide your tasks with
# network configuration when they start up.
#
# https://www.nomadproject.io/docs/job-specification/network
#
network {
port "http" {
static = ${port}
}
}
}
}
}
}
|
