2 # The "region" parameter specifies the region in which to execute the job.
3 # If omitted, this inherits the default region name of "global".
6 # The "datacenters" parameter specifies the list of datacenters which should
7 # be considered when placing this task. This must be provided.
8 datacenters = "${datacenters}"
10 # The "type" parameter controls the type of job, which impacts the scheduler's
11 # decision on placement. This configuration is optional and defaults to
12 # "service". For a full list of job types and their differences, please see
13 # the online documentation.
15 # For more information, please see the online documentation at:
17 # https://www.nomadproject.io/docs/jobspec/schedulers.html
22 # The "max_parallel" parameter specifies the maximum number of updates to
23 # perform in parallel. In this case, this specifies to update a single task
27 # The "min_healthy_time" parameter specifies the minimum time the allocation
28 # must be in the healthy state before it is marked as healthy and unblocks
29 # further allocations from being updated.
30 min_healthy_time = "10s"
32 # The "healthy_deadline" parameter specifies the deadline in which the
33 # allocation must be marked as healthy after which the allocation is
34 # automatically transitioned to unhealthy. Transitioning to unhealthy will
35 # fail the deployment and potentially roll back the job if "auto_revert" is
37 healthy_deadline = "3m"
39 # The "progress_deadline" parameter specifies the deadline in which an
40 # allocation must be marked as healthy. The deadline begins when the first
41 # allocation for the deployment is created and is reset whenever an allocation
42 # as part of the deployment transitions to a healthy state. If no allocation
43 # transitions to the healthy state before the progress deadline, the
44 # deployment is marked as failed.
45 progress_deadline = "10m"
47 # The "auto_revert" parameter specifies if the job should auto-revert to the
48 # last stable job on deployment failure. A job is marked as stable if all the
49 # allocations as part of its deployment were marked healthy.
52 # The "canary" parameter specifies that changes to the job that would result
53 # in destructive updates should create the specified number of canaries
54 # without stopping any previous allocations. Once the operator determines the
55 # canaries are healthy, they can be promoted which unblocks a rolling update
56 # of the remaining allocations at a rate of "max_parallel".
58 # Further, setting "canary" equal to the count of the task group allows
59 # blue/green deployments. When the job is updated, a full set of the new
60 # version is deployed and upon promotion the old version is stopped.
64 # The reschedule stanza specifies the group's rescheduling strategy. If
65 # specified at the job level, the configuration will apply to all groups
66 # within the job. If the reschedule stanza is present on both the job and the
67 # group, they are merged with the group stanza taking the highest precedence
71 delay_function = "constant"
75 # The "group" stanza defines a series of tasks that should be co-located on
76 # the same Nomad client. Any task within a group will be placed on the same
79 # For more information and examples on the "group" stanza, please see
80 # the online documentation at:
82 # https://www.nomadproject.io/docs/job-specification/group.html
84 group "prod-group1-nginx" {
85 # The "count" parameter specifies the number of the task groups that should
86 # be running under this group. This value must be non-negative and defaults
90 # The restart stanza configures a tasks's behavior on task failure. Restarts
91 # happen on the client that is running the task.
99 # The "task" stanza creates an individual unit of work, such as a Docker
100 # container, web application, or batch processing.
102 # For more information and examples on the "task" stanza, please see
103 # the online documentation at:
105 # https://www.nomadproject.io/docs/job-specification/task.html
107 task "prod-task1-nginx" {
108 # The "driver" parameter specifies the task driver that should be used to
112 # The "config" stanza specifies the driver configuration, which is passed
113 # directly to the driver to start the task. The details of configurations
114 # are specific to each driver, so please see specific driver
115 # documentation for more information.
117 image = "nginx:stable"
118 dns_servers = [ "$${attr.unique.network.ip-address}" ]
124 "/etc/consul.d/ssl/consul.pem:/etc/ssl/certs/nginx-cert.pem",
125 "/etc/consul.d/ssl/consul-key.pem:/etc/ssl/private/nginx-key.pem",
126 "custom/upstream.conf:/etc/nginx/conf.d/upstream.conf",
127 "custom/logs.conf:/etc/nginx/conf.d/logs.conf",
128 "custom/docs.conf:/etc/nginx/conf.d/docs.conf"
132 # The "template" stanza instructs Nomad to manage a template, such as
133 # a configuration file or script. This template can optionally pull data
134 # from Consul or Vault to populate runtime configuration data.
136 # For more information and examples on the "template" stanza, please see
137 # the online documentation at:
139 # https://www.nomadproject.io/docs/job-specification/template.html
144 server storage0.storage.service.consul:9000;
145 server storage1.storage.service.consul:9000;
146 server storage2.storage.service.consul:9000;
147 server storage3.storage.service.consul:9000;
150 destination = "custom/upstream.conf"
155 listen 443 ssl default_server;
156 server_name logs.nginx.service.consul;
157 keepalive_timeout 70;
158 ssl_session_cache shared:SSL:10m;
159 ssl_session_timeout 10m;
160 ssl_protocols TLSv1.2;
161 ssl_prefer_server_ciphers on;
162 ssl_ciphers "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384";
163 ssl_certificate /etc/ssl/certs/nginx-cert.pem;
164 ssl_certificate_key /etc/ssl/private/nginx-key.pem;
166 chunked_transfer_encoding off;
167 proxy_connect_timeout 300;
168 proxy_http_version 1.1;
169 proxy_set_header Host $host:$server_port;
170 proxy_set_header Connection "";
171 proxy_pass http://storage/logs.fd.io/;
172 server_name_in_redirect off;
174 location ~ (.*html.gz)$ {
175 add_header Content-Encoding gzip;
176 add_header Content-Type text/html;
177 chunked_transfer_encoding off;
178 proxy_connect_timeout 300;
179 proxy_http_version 1.1;
180 proxy_set_header Host $host:$server_port;
181 proxy_set_header Connection "";
182 proxy_pass http://storage/logs.fd.io/$1;
183 server_name_in_redirect off;
185 location ~ (.*txt.gz|.*log.gz)$ {
186 add_header Content-Encoding gzip;
187 add_header Content-Type text/plain;
188 chunked_transfer_encoding off;
189 proxy_connect_timeout 300;
190 proxy_http_version 1.1;
191 proxy_set_header Host $host:$server_port;
192 proxy_set_header Connection "";
193 proxy_pass http://storage/logs.fd.io/$1;
194 server_name_in_redirect off;
196 location ~ (.*xml.gz)$ {
197 add_header Content-Encoding gzip;
198 add_header Content-Type application/xml;
199 chunked_transfer_encoding off;
200 proxy_connect_timeout 300;
201 proxy_http_version 1.1;
202 proxy_set_header Host $host:$server_port;
203 proxy_set_header Connection "";
204 proxy_pass http://storage/logs.fd.io/$1;
205 server_name_in_redirect off;
209 destination = "custom/logs.conf"
215 server_name docs.nginx.service.consul;
216 keepalive_timeout 70;
217 ssl_session_cache shared:SSL:10m;
218 ssl_session_timeout 10m;
219 ssl_protocols TLSv1.2;
220 ssl_prefer_server_ciphers on;
221 ssl_ciphers "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384";
222 ssl_certificate /etc/ssl/certs/nginx-cert.pem;
223 ssl_certificate_key /etc/ssl/private/nginx-key.pem;
225 chunked_transfer_encoding off;
226 proxy_connect_timeout 300;
227 proxy_http_version 1.1;
228 proxy_set_header Host $host:$server_port;
229 proxy_set_header Connection "";
230 proxy_pass http://storage/docs.fd.io/;
231 server_name_in_redirect off;
235 destination = "custom/docs.conf"
238 # The service stanza instructs Nomad to register a service with Consul.
240 # For more information and examples on the "task" stanza, please see
241 # the online documentation at:
243 # https://www.nomadproject.io/docs/job-specification/service.html
248 tags = [ "docs", "logs" ]
251 # The "resources" stanza describes the requirements a task needs to
252 # execute. Resource requirements include memory, network, cpu, and more.
253 # This ensures the task will execute on a machine that contains enough
256 # For more information and examples on the "resources" stanza, please see
257 # the online documentation at:
259 # https://www.nomadproject.io/docs/job-specification/resources.html