You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@aurora.apache.org by re...@apache.org on 2019/12/28 00:00:51 UTC
[aurora-website] branch asf-staging updated: Attempt 2 at
publishing on staging site.
This is an automated email from the ASF dual-hosted git repository.
renan pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/aurora-website.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new f2acc2f Attempt 2 at publishing on staging site.
f2acc2f is described below
commit f2acc2fc7c75f7a95b8906ac4ededd7c155205b2
Author: Renan DelValle <re...@apache.org>
AuthorDate: Fri Dec 27 16:00:32 2019 -0800
Attempt 2 at publishing on staging site.
---
...ex.html => 2015-upcoming-apache-aurora-meetups} | 0
...ing-apache-aurora-meetups20191213-22326-1geefad | 129 --
.../index.html => aurora-0-10-0-released} | 0
.../aurora-0-10-0-released20191213-22326-d3z1yj | 149 --
.../index.html => aurora-0-11-0-released} | 0
.../aurora-0-11-0-released20191213-22326-1k740o2 | 163 ---
...0191213-22326-sw4i8y => aurora-0-12-0-released} | 0
content/blog/aurora-0-12-0-released/index.html | 197 ---
.../index.html => aurora-0-13-0-released} | 0
.../aurora-0-13-0-released20191213-22326-168trse | 212 ---
...0191213-22326-q9lipk => aurora-0-14-0-released} | 0
content/blog/aurora-0-14-0-released/index.html | 185 ---
.../index.html => aurora-0-15-0-released} | 0
.../aurora-0-15-0-released20191213-22326-14f0t8a | 136 --
.../index.html => aurora-0-16-0-released} | 0
.../aurora-0-16-0-released20191213-22326-189kqdn | 194 ---
.../index.html => aurora-0-17-0-released} | 0
.../aurora-0-17-0-released20191213-22326-1keg4c7 | 192 ---
.../index.html => aurora-0-18-0-released} | 0
.../aurora-0-18-0-released20191213-22326-8qqrbc | 181 ---
.../index.html => aurora-0-18-1-released} | 0
.../aurora-0-18-1-released20191213-22326-p7jfh1 | 106 --
.../index.html => aurora-0-19-0-released} | 0
.../aurora-0-19-0-released20191213-22326-oooa38 | 176 ---
.../index.html => aurora-0-19-1-released} | 0
.../aurora-0-19-1-released20191213-22326-12sow2g | 105 --
.../index.html => aurora-0-20-0-released} | 0
.../aurora-0-20-0-released20191213-22326-d1tttf | 158 ---
...0191213-22326-jzol5l => aurora-0-21-0-released} | 0
content/blog/aurora-0-21-0-released/index.html | 172 ---
...index.html => aurora-0-6-0-incubating-released} | 0
...0-6-0-incubating-released20191213-22326-18841qy | 172 ---
...index.html => aurora-0-7-0-incubating-released} | 0
...-0-7-0-incubating-released20191213-22326-itj8tl | 155 --
.../index.html => aurora-0-8-0-released} | 0
.../aurora-0-8-0-released20191213-22326-135gtuq | 171 ---
...0191213-22326-12jw75q => aurora-0-9-0-released} | 0
content/blog/aurora-0-9-0-released/index.html | 153 --
.../index.html => aurora-at-mesoscon-seattle} | 0
...aurora-at-mesoscon-seattle20191213-22326-y4rct3 | 118 --
...ld-system20191213-22326-gy4wq1 => build-system} | 0
.../documentation/0.10.0/build-system/index.html | 250 ----
...3-22326-pf49ml => client-cluster-configuration} | 0
.../0.10.0/client-cluster-configuration/index.html | 267 ----
...mmands20191213-22326-dtt4z4 => client-commands} | 0
.../0.10.0/client-commands/index.html | 566 --------
...committers20191213-22326-1vzfde6 => committers} | 0
content/documentation/0.10.0/committers/index.html | 225 ---
...191213-22326-hnazkj => configuration-reference} | 0
.../0.10.0/configuration-reference/index.html | 1166 ---------------
...0191213-22326-h4oaaw => configuration-tutorial} | 0
.../0.10.0/configuration-tutorial/index.html | 1139 ---------------
...ributing20191213-22326-14dul7n => contributing} | 0
.../documentation/0.10.0/contributing/index.html | 240 ----
.../cron-jobs20191213-22326-1v30koc => cron-jobs} | 0
content/documentation/0.10.0/cron-jobs/index.html | 303 ----
...213-22326-k828qq => deploying-aurora-scheduler} | 0
.../0.10.0/deploying-aurora-scheduler/index.html | 544 -------
...d-hooks20191213-22326-15t75xs => command-hooks} | 0
.../0.10.0/design/command-hooks/index.html | 257 ----
...1213-22326-1tjw7ai => developing-aurora-client} | 0
.../0.10.0/developing-aurora-client/index.html | 244 ----
...3-22326-16q3w3d => developing-aurora-scheduler} | 0
.../0.10.0/developing-aurora-scheduler/index.html | 282 ----
.../{hooks/hooks20191213-22326-102myk9 => hooks} | 0
content/documentation/0.10.0/hooks/index.html | 434 ------
...installing20191213-22326-1kd5day => installing} | 0
content/documentation/0.10.0/installing/index.html | 467 ------
...monitoring20191213-22326-1shq4s5 => monitoring} | 0
content/documentation/0.10.0/monitoring/index.html | 349 -----
...tations20191213-22326-12ef2p5 => presentations} | 0
.../documentation/0.10.0/presentations/index.html | 205 ---
.../resources20191213-22326-7ejl74 => resources} | 0
content/documentation/0.10.0/resources/index.html | 321 -----
...rage20191213-22326-xhd5vi => scheduler-storage} | 0
.../0.10.0/scheduler-storage/index.html | 201 ---
.../security20191213-22326-5t6j0g => security} | 0
content/documentation/0.10.0/security/index.html | 420 ------
.../0.10.0/{sla/sla20191213-22326-fpd0n1 => sla} | 0
content/documentation/0.10.0/sla/index.html | 350 -----
.../storage20191213-22326-1lxts3k => storage} | 0
...-config20191213-22326-vy2jh5 => storage-config} | 0
.../documentation/0.10.0/storage-config/index.html | 318 -----
content/documentation/0.10.0/storage/index.html | 250 ----
...1213-22326-1esuk0z => test-resource-generation} | 0
.../0.10.0/test-resource-generation/index.html | 180 ---
...ion20191213-22326-xx0rsc => thrift-deprecation} | 0
.../0.10.0/thrift-deprecation/index.html | 209 ---
.../tutorial20191213-22326-yoeulk => tutorial} | 0
content/documentation/0.10.0/tutorial/index.html | 421 ------
...user-guide20191213-22326-1qtc9np => user-guide} | 0
content/documentation/0.10.0/user-guide/index.html | 542 -------
.../vagrant20191213-22326-eu4qyf => vagrant} | 0
content/documentation/0.10.0/vagrant/index.html | 280 ----
...ld-system20191213-22326-1j7iqb => build-system} | 0
.../documentation/0.11.0/build-system/index.html | 250 ----
...-22326-1xbafm1 => client-cluster-configuration} | 0
.../0.11.0/client-cluster-configuration/index.html | 266 ----
...mmands20191213-22326-u3xhuk => client-commands} | 0
.../0.11.0/client-commands/index.html | 534 -------
...committers20191213-22326-1gcqo1n => committers} | 0
content/documentation/0.11.0/committers/index.html | 225 ---
...191213-22326-wylxcj => configuration-reference} | 0
.../0.11.0/configuration-reference/index.html | 1305 -----------------
...0191213-22326-hzvokc => configuration-tutorial} | 0
.../0.11.0/configuration-tutorial/index.html | 1142 ---------------
.../cron-jobs20191213-22326-5lx1vh => cron-jobs} | 0
content/documentation/0.11.0/cron-jobs/index.html | 303 ----
...213-22326-i9hhsm => deploying-aurora-scheduler} | 0
.../0.11.0/deploying-aurora-scheduler/index.html | 559 --------
...d-hooks20191213-22326-1ollwe3 => command-hooks} | 0
.../0.11.0/design/command-hooks/index.html | 257 ----
...91213-22326-ih66m1 => developing-aurora-client} | 0
.../0.11.0/developing-aurora-client/index.html | 246 ----
...3-22326-1t6n9fq => developing-aurora-scheduler} | 0
.../0.11.0/developing-aurora-scheduler/index.html | 309 ----
.../{hooks/hooks20191213-22326-1p73fuo => hooks} | 0
content/documentation/0.11.0/hooks/index.html | 424 ------
...installing20191213-22326-1s5z6iv => installing} | 0
content/documentation/0.11.0/installing/index.html | 469 ------
...monitoring20191213-22326-1yvodle => monitoring} | 0
content/documentation/0.11.0/monitoring/index.html | 349 -----
...ntations20191213-22326-k86xqe => presentations} | 0
.../documentation/0.11.0/presentations/index.html | 205 ---
.../resources20191213-22326-osivm0 => resources} | 0
content/documentation/0.11.0/resources/index.html | 321 -----
...rage20191213-22326-3cz9k1 => scheduler-storage} | 0
.../0.11.0/scheduler-storage/index.html | 201 ---
.../security20191213-22326-1h6c40h => security} | 0
content/documentation/0.11.0/security/index.html | 420 ------
.../0.11.0/{sla/sla20191213-22326-15oiihs => sla} | 0
content/documentation/0.11.0/sla/index.html | 350 -----
.../storage20191213-22326-ojybt6 => storage} | 0
...config20191213-22326-1v1yo3x => storage-config} | 0
.../documentation/0.11.0/storage-config/index.html | 318 -----
content/documentation/0.11.0/storage/index.html | 250 ----
...91213-22326-4pn3q4 => test-resource-generation} | 0
.../0.11.0/test-resource-generation/index.html | 180 ---
...ion20191213-22326-i2ho7s => thrift-deprecation} | 0
.../0.11.0/thrift-deprecation/index.html | 209 ---
.../{tools/tools20191213-22326-1txi78j => tools} | 0
content/documentation/0.11.0/tools/index.html | 179 ---
.../tutorial20191213-22326-xk28ca => tutorial} | 0
content/documentation/0.11.0/tutorial/index.html | 421 ------
.../user-guide20191213-22326-2bdd9e => user-guide} | 0
content/documentation/0.11.0/user-guide/index.html | 542 -------
.../vagrant20191213-22326-7al32g => vagrant} | 0
content/documentation/0.11.0/vagrant/index.html | 280 ----
...d-system20191213-22326-11vbfdt => build-system} | 0
.../documentation/0.12.0/build-system/index.html | 250 ----
...3-22326-18gxam => client-cluster-configuration} | 0
.../0.12.0/client-cluster-configuration/index.html | 266 ----
...mmands20191213-22326-ygfobx => client-commands} | 0
.../0.12.0/client-commands/index.html | 534 -------
.../committers20191213-22326-7v6ck3 => committers} | 0
content/documentation/0.12.0/committers/index.html | 227 ---
...91213-22326-1k3a6hq => configuration-reference} | 0
.../0.12.0/configuration-reference/index.html | 1302 -----------------
...0191213-22326-lwo0on => configuration-tutorial} | 0
.../0.12.0/configuration-tutorial/index.html | 1142 ---------------
.../cron-jobs20191213-22326-1jkl9la => cron-jobs} | 0
content/documentation/0.12.0/cron-jobs/index.html | 303 ----
...13-22326-1enme9f => deploying-aurora-scheduler} | 0
.../0.12.0/deploying-aurora-scheduler/index.html | 592 --------
...ents20191213-22326-15cdmmi => design-documents} | 0
.../0.12.0/design-documents/index.html | 173 ---
...d-hooks20191213-22326-1v3uf4r => command-hooks} | 0
.../0.12.0/design/command-hooks/index.html | 257 ----
...91213-22326-jogtip => developing-aurora-client} | 0
.../0.12.0/developing-aurora-client/index.html | 246 ----
...13-22326-jnv858 => developing-aurora-scheduler} | 0
.../0.12.0/developing-aurora-scheduler/index.html | 309 ----
.../{hooks/hooks20191213-22326-103hp52 => hooks} | 0
content/documentation/0.12.0/hooks/index.html | 424 ------
.../installing20191213-22326-ptjqpz => installing} | 0
content/documentation/0.12.0/installing/index.html | 474 -------
...monitoring20191213-22326-1y4qips => monitoring} | 0
content/documentation/0.12.0/monitoring/index.html | 349 -----
...ntations20191213-22326-4j6oi5 => presentations} | 0
.../documentation/0.12.0/presentations/index.html | 235 ---
.../resources20191213-22326-6ka610 => resources} | 0
content/documentation/0.12.0/resources/index.html | 321 -----
.../security20191213-22326-1oq5jf7 => security} | 0
content/documentation/0.12.0/security/index.html | 428 ------
.../0.12.0/{sla/sla20191213-22326-188soi9 => sla} | 0
content/documentation/0.12.0/sla/index.html | 350 -----
.../storage20191213-22326-u58pvh => storage} | 0
...config20191213-22326-1m6ck8p => storage-config} | 0
.../documentation/0.12.0/storage-config/index.html | 318 -----
content/documentation/0.12.0/storage/index.html | 250 ----
...1213-22326-151awc9 => test-resource-generation} | 0
.../0.12.0/test-resource-generation/index.html | 180 ---
...on20191213-22326-10nvgj5 => thrift-deprecation} | 0
.../0.12.0/thrift-deprecation/index.html | 209 ---
.../{tools/tools20191213-22326-4yb9jl => tools} | 0
content/documentation/0.12.0/tools/index.html | 179 ---
.../tutorial20191213-22326-s2gqf7 => tutorial} | 0
content/documentation/0.12.0/tutorial/index.html | 413 ------
...user-guide20191213-22326-1mum76v => user-guide} | 0
content/documentation/0.12.0/user-guide/index.html | 542 -------
.../vagrant20191213-22326-72emqu => vagrant} | 0
content/documentation/0.12.0/vagrant/index.html | 280 ----
...ntations20191213-22326-n34f67 => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-1bd4tf5 => tools} | 0
.../0.13.0/additional-resources/tools/index.html | 186 ---
...tributing20191213-22326-ltmpk4 => contributing} | 0
.../documentation/0.13.0/contributing/index.html | 249 ----
.../client20191213-22326-1w493ac => client} | 0
.../0.13.0/development/client/index.html | 234 ---
...guide20191213-22326-60sbfm => committers-guide} | 0
.../0.13.0/development/committers-guide/index.html | 231 ---
...igration20191213-22326-1umwahs => db-migration} | 0
.../0.13.0/development/db-migration/index.html | 186 ---
...ents20191213-22326-1o93thi => design-documents} | 0
.../0.13.0/development/design-documents/index.html | 175 ---
...nd-hooks20191213-22326-1qomp8 => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-1fkgx1e => scheduler} | 0
.../0.13.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-1c87r4l => thermos} | 0
.../0.13.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-1nhfhmp => thrift} | 0
.../0.13.0/development/thrift/index.html | 208 ---
.../{ui/ui20191213-22326-1btnq72 => ui} | 0
.../documentation/0.13.0/development/ui/index.html | 198 ---
...nstraints20191213-22326-19y674w => constraints} | 0
.../0.13.0/features/constraints/index.html | 268 ----
...containers20191213-22326-1gvz8mr => containers} | 0
.../0.13.0/features/containers/index.html | 192 ---
.../cron-jobs20191213-22326-idvjlb => cron-jobs} | 0
.../0.13.0/features/cron-jobs/index.html | 293 ----
...b-updates20191213-22326-1w8zytw => job-updates} | 0
.../0.13.0/features/job-updates/index.html | 260 ----
...titenancy20191213-22326-h2iw1l => multitenancy} | 0
.../0.13.0/features/multitenancy/index.html | 215 ---
...ion20191213-22326-ipvh35 => resource-isolation} | 0
.../0.13.0/features/resource-isolation/index.html | 317 -----
...very20191213-22326-r4ni3g => service-discovery} | 0
.../0.13.0/features/service-discovery/index.html | 204 ---
.../services20191213-22326-w57iag => services} | 0
.../0.13.0/features/services/index.html | 243 ----
...a-metrics20191213-22326-1o86j5u => sla-metrics} | 0
.../0.13.0/features/sla-metrics/index.html | 350 -----
.../overview20191213-22326-jbeyd => overview} | 0
.../0.13.0/getting-started/overview/index.html | 259 ----
.../tutorial20191213-22326-igyofz => tutorial} | 0
.../0.13.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-1x1gb1n => vagrant} | 0
.../0.13.0/getting-started/vagrant/index.html | 280 ----
...restore20191213-22326-z3r4t3 => backup-restore} | 0
.../0.13.0/operations/backup-restore/index.html | 254 ----
...uration20191213-22326-17kp7a2 => configuration} | 0
.../0.13.0/operations/configuration/index.html | 361 -----
...tallation20191213-22326-7njndn => installation} | 0
.../0.13.0/operations/installation/index.html | 491 -------
.../monitoring20191213-22326-wq0nf3 => monitoring} | 0
.../0.13.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-e7lfrd => security} | 0
.../0.13.0/operations/security/index.html | 490 -------
.../storage20191213-22326-4rnnl9 => storage} | 0
.../0.13.0/operations/storage/index.html | 258 ----
...-22326-128sfz2 => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 286 ----
...mmands20191213-22326-k71lpr => client-commands} | 0
.../0.13.0/reference/client-commands/index.html | 484 -------
...ent-hooks20191213-22326-3ao55s => client-hooks} | 0
.../0.13.0/reference/client-hooks/index.html | 415 ------
...guration20191213-22326-dwappf => configuration} | 0
...3-22326-onbari => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...1213-22326-11g8o1u => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-13q8lsc => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 670 ---------
.../0.13.0/reference/configuration/index.html | 1171 ---------------
...191213-22326-tgzc5v => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 376 -----
...s20191213-22326-1ep59io => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...fecycle20191213-22326-otr25l => task-lifecycle} | 0
.../0.13.0/reference/task-lifecycle/index.html | 300 ----
...tations20191213-22326-1c85z54 => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-v4s2ew => tools} | 0
.../0.14.0/additional-resources/tools/index.html | 186 ---
...tributing20191213-22326-yimnwa => contributing} | 0
.../documentation/0.14.0/contributing/index.html | 249 ----
.../{client/client20191213-22326-u6iuk0 => client} | 0
.../0.14.0/development/client/index.html | 234 ---
...guide20191213-22326-ajq94c => committers-guide} | 0
.../0.14.0/development/committers-guide/index.html | 231 ---
...igration20191213-22326-1ajw2jy => db-migration} | 0
.../0.14.0/development/db-migration/index.html | 187 ---
...ments20191213-22326-gfz8jo => design-documents} | 0
.../0.14.0/development/design-documents/index.html | 176 ---
...d-hooks20191213-22326-1259a35 => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-18r6a8h => scheduler} | 0
.../0.14.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-1wcop89 => thermos} | 0
.../0.14.0/development/thermos/index.html | 273 ----
.../{thrift/thrift20191213-22326-czi18p => thrift} | 0
.../0.14.0/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-byyhzw => ui} | 0
.../documentation/0.14.0/development/ui/index.html | 198 ---
...nstraints20191213-22326-1qruz33 => constraints} | 0
.../0.14.0/features/constraints/index.html | 268 ----
...containers20191213-22326-12114lw => containers} | 0
.../0.14.0/features/containers/index.html | 207 ---
.../cron-jobs20191213-22326-pdbmp8 => cron-jobs} | 0
.../0.14.0/features/cron-jobs/index.html | 293 ----
...ob-updates20191213-22326-pesx18 => job-updates} | 0
.../0.14.0/features/job-updates/index.html | 260 ----
...itenancy20191213-22326-1c1elcz => multitenancy} | 0
.../0.14.0/features/multitenancy/index.html | 215 ---
...on20191213-22326-1d1pdiq => resource-isolation} | 0
.../0.14.0/features/resource-isolation/index.html | 330 -----
...ery20191213-22326-1ga1qa2 => service-discovery} | 0
.../0.14.0/features/service-discovery/index.html | 202 ---
.../services20191213-22326-1a9os11 => services} | 0
.../0.14.0/features/services/index.html | 243 ----
...a-metrics20191213-22326-184qbqt => sla-metrics} | 0
.../0.14.0/features/sla-metrics/index.html | 350 -----
.../webhooks20191213-22326-60aajm => webhooks} | 0
.../0.14.0/features/webhooks/index.html | 230 ---
.../overview20191213-22326-qja63b => overview} | 0
.../0.14.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-11k7zbe => tutorial} | 0
.../0.14.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-byley0 => vagrant} | 0
.../0.14.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1cybz9f => backup-restore} | 0
.../0.14.0/operations/backup-restore/index.html | 254 ----
...uration20191213-22326-1ygetgi => configuration} | 0
.../0.14.0/operations/configuration/index.html | 552 --------
...allation20191213-22326-1k533sm => installation} | 0
.../0.14.0/operations/installation/index.html | 491 -------
...monitoring20191213-22326-1uym1l3 => monitoring} | 0
.../0.14.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-1yr2s70 => security} | 0
.../0.14.0/operations/security/index.html | 490 -------
.../storage20191213-22326-1f7px3f => storage} | 0
.../0.14.0/operations/storage/index.html | 258 ----
...3-22326-murrqr => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 286 ----
...mands20191213-22326-1lgy3du => client-commands} | 0
.../0.14.0/reference/client-commands/index.html | 484 -------
...nt-hooks20191213-22326-1leowrs => client-hooks} | 0
.../0.14.0/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1qsaj2s => configuration} | 0
...-22326-1bhk7hk => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...1213-22326-13ci9qt => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...0191213-22326-nmczcm => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 670 ---------
.../0.14.0/reference/configuration/index.html | 1250 ----------------
...91213-22326-1a1ppge => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 386 -----
...ts20191213-22326-290p1u => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...fecycle20191213-22326-ujt7ju => task-lifecycle} | 0
.../0.14.0/reference/task-lifecycle/index.html | 300 ----
...tations20191213-22326-1ig24td => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-sodey2 => tools} | 0
.../0.15.0/additional-resources/tools/index.html | 186 ---
...ributing20191213-22326-1iuggbg => contributing} | 0
.../documentation/0.15.0/contributing/index.html | 249 ----
.../client20191213-22326-12dfbru => client} | 0
.../0.15.0/development/client/index.html | 234 ---
...guide20191213-22326-edlln7 => committers-guide} | 0
.../0.15.0/development/committers-guide/index.html | 231 ---
...igration20191213-22326-19k1uz1 => db-migration} | 0
.../0.15.0/development/db-migration/index.html | 187 ---
...uments20191213-22326-vuxoa => design-documents} | 0
.../0.15.0/development/design-documents/index.html | 176 ---
...nd-hooks20191213-22326-silbrb => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-5xk6es => scheduler} | 0
.../0.15.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-1ignspf => thermos} | 0
.../0.15.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-1bdke6h => thrift} | 0
.../0.15.0/development/thrift/index.html | 208 ---
.../{ui/ui20191213-22326-1rvldhb => ui} | 0
.../documentation/0.15.0/development/ui/index.html | 198 ---
...onstraints20191213-22326-n5zapy => constraints} | 0
.../0.15.0/features/constraints/index.html | 268 ----
.../containers20191213-22326-21bv9s => containers} | 0
.../0.15.0/features/containers/index.html | 207 ---
.../cron-jobs20191213-22326-9zid5e => cron-jobs} | 0
.../0.15.0/features/cron-jobs/index.html | 293 ----
...b-updates20191213-22326-179glrz => job-updates} | 0
.../0.15.0/features/job-updates/index.html | 260 ----
...fetcher20191213-22326-1fokm2e => mesos-fetcher} | 0
.../0.15.0/features/mesos-fetcher/index.html | 213 ---
...titenancy20191213-22326-clx3zy => multitenancy} | 0
.../0.15.0/features/multitenancy/index.html | 215 ---
...ion20191213-22326-aoqmsq => resource-isolation} | 0
.../0.15.0/features/resource-isolation/index.html | 330 -----
...ery20191213-22326-1lwjc7p => service-discovery} | 0
.../0.15.0/features/service-discovery/index.html | 202 ---
.../services20191213-22326-1yk5p9x => services} | 0
.../0.15.0/features/services/index.html | 243 ----
...a-metrics20191213-22326-1ptkgz6 => sla-metrics} | 0
.../0.15.0/features/sla-metrics/index.html | 350 -----
.../webhooks20191213-22326-inv2e0 => webhooks} | 0
.../0.15.0/features/webhooks/index.html | 230 ---
.../overview20191213-22326-1wik05r => overview} | 0
.../0.15.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-15ob7ih => tutorial} | 0
.../0.15.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-1ummo5h => vagrant} | 0
.../0.15.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1we4zl3 => backup-restore} | 0
.../0.15.0/operations/backup-restore/index.html | 254 ----
...guration20191213-22326-q1rc1e => configuration} | 0
.../0.15.0/operations/configuration/index.html | 552 --------
...allation20191213-22326-1fr38ju => installation} | 0
.../0.15.0/operations/installation/index.html | 491 -------
...monitoring20191213-22326-1endn7o => monitoring} | 0
.../0.15.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-am9ke4 => security} | 0
.../0.15.0/operations/security/index.html | 490 -------
.../storage20191213-22326-1lpifeu => storage} | 0
.../0.15.0/operations/storage/index.html | 258 ----
...-22326-14x0gtx => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 286 ----
...mands20191213-22326-1k44svx => client-commands} | 0
.../0.15.0/reference/client-commands/index.html | 484 -------
...nt-hooks20191213-22326-1epz5m1 => client-hooks} | 0
.../0.15.0/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1oo46co => configuration} | 0
...-22326-1c8r9pg => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...91213-22326-ibnexf => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-15fmx0r => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 670 ---------
.../0.15.0/reference/configuration/index.html | 1260 -----------------
...91213-22326-151jvla => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 386 -----
...s20191213-22326-1p57ng9 => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...fecycle20191213-22326-bu3oy7 => task-lifecycle} | 0
.../0.15.0/reference/task-lifecycle/index.html | 300 ----
...entations20191213-22326-f2fhl => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-44ntq2 => tools} | 0
.../0.16.0/additional-resources/tools/index.html | 191 ---
...ributing20191213-22326-1c2vsim => contributing} | 0
.../documentation/0.16.0/contributing/index.html | 251 ----
.../client20191213-22326-1t7jzxf => client} | 0
.../0.16.0/development/client/index.html | 234 ---
...uide20191213-22326-1askwag => committers-guide} | 0
.../0.16.0/development/committers-guide/index.html | 252 ----
...igration20191213-22326-1pw2bc7 => db-migration} | 0
.../0.16.0/development/db-migration/index.html | 187 ---
...ents20191213-22326-13exiig => design-documents} | 0
.../0.16.0/development/design-documents/index.html | 177 ---
...nd-hooks20191213-22326-voj7kb => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-1cesrq6 => scheduler} | 0
.../0.16.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-ce393k => thermos} | 0
.../0.16.0/development/thermos/index.html | 273 ----
.../{thrift/thrift20191213-22326-52jzii => thrift} | 0
.../0.16.0/development/thrift/index.html | 208 ---
.../{ui/ui20191213-22326-19gurs2 => ui} | 0
.../documentation/0.16.0/development/ui/index.html | 198 ---
...onstraints20191213-22326-61jfom => constraints} | 0
.../0.16.0/features/constraints/index.html | 268 ----
.../containers20191213-22326-wrgqgw => containers} | 0
.../0.16.0/features/containers/index.html | 256 ----
.../cron-jobs20191213-22326-1r6jdce => cron-jobs} | 0
.../0.16.0/features/cron-jobs/index.html | 293 ----
...tors20191213-22326-1um66cj => custom-executors} | 0
.../0.16.0/features/custom-executors/index.html | 397 ------
...ob-updates20191213-22326-2axojn => job-updates} | 0
.../0.16.0/features/job-updates/index.html | 260 ----
...-fetcher20191213-22326-h2u22w => mesos-fetcher} | 0
.../0.16.0/features/mesos-fetcher/index.html | 213 ---
...itenancy20191213-22326-1hoo2wz => multitenancy} | 0
.../0.16.0/features/multitenancy/index.html | 234 ---
...on20191213-22326-1u6o3pn => resource-isolation} | 0
.../0.16.0/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-1fyf19k => service-discovery} | 0
.../0.16.0/features/service-discovery/index.html | 202 ---
.../services20191213-22326-8vwlf2 => services} | 0
.../0.16.0/features/services/index.html | 243 ----
...a-metrics20191213-22326-160azbx => sla-metrics} | 0
.../0.16.0/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-19sysda => webhooks} | 0
.../0.16.0/features/webhooks/index.html | 230 ---
.../overview20191213-22326-sn9jqg => overview} | 0
.../0.16.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-1pc77rh => tutorial} | 0
.../0.16.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-164ddu3 => vagrant} | 0
.../0.16.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1age6y6 => backup-restore} | 0
.../0.16.0/operations/backup-restore/index.html | 254 ----
...uration20191213-22326-11be2vb => configuration} | 0
.../0.16.0/operations/configuration/index.html | 427 ------
...allation20191213-22326-1oochy6 => installation} | 0
.../0.16.0/operations/installation/index.html | 479 -------
.../monitoring20191213-22326-uyzuur => monitoring} | 0
.../0.16.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-pbnmip => security} | 0
.../0.16.0/operations/security/index.html | 490 -------
.../storage20191213-22326-1gz4m0e => storage} | 0
.../0.16.0/operations/storage/index.html | 258 ----
...3-22326-c2c1kn => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 286 ----
...mmands20191213-22326-animxx => client-commands} | 0
.../0.16.0/reference/client-commands/index.html | 484 -------
...ent-hooks20191213-22326-mxeeyt => client-hooks} | 0
.../0.16.0/reference/client-hooks/index.html | 415 ------
...guration20191213-22326-z0idog => configuration} | 0
...3-22326-7423ud => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...91213-22326-8dosoa => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-1pihyon => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 670 ---------
.../0.16.0/reference/configuration/index.html | 1254 ----------------
...91213-22326-1trikco => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 400 ------
...s20191213-22326-1lbst39 => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...ifecycle20191213-22326-bv2tb => task-lifecycle} | 0
.../0.16.0/reference/task-lifecycle/index.html | 300 ----
...tations20191213-22326-16dmx8q => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-xi5j6x => tools} | 0
.../0.17.0/additional-resources/tools/index.html | 191 ---
...tributing20191213-22326-i0o09c => contributing} | 0
.../documentation/0.17.0/contributing/index.html | 251 ----
.../client20191213-22326-1y22ycj => client} | 0
.../0.17.0/development/client/index.html | 300 ----
...uide20191213-22326-1cyyas2 => committers-guide} | 0
.../0.17.0/development/committers-guide/index.html | 252 ----
...igration20191213-22326-1x7n09h => db-migration} | 0
.../0.17.0/development/db-migration/index.html | 187 ---
...ments20191213-22326-whkn7a => design-documents} | 0
.../0.17.0/development/design-documents/index.html | 177 ---
...d-hooks20191213-22326-1l8g0id => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-v0vq23 => scheduler} | 0
.../0.17.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-uuv6nk => thermos} | 0
.../0.17.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-1knldzm => thrift} | 0
.../0.17.0/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-gbg6yc => ui} | 0
.../documentation/0.17.0/development/ui/index.html | 198 ---
...onstraints20191213-22326-o3outm => constraints} | 0
.../0.17.0/features/constraints/index.html | 268 ----
.../containers20191213-22326-xksb3v => containers} | 0
.../0.17.0/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-25jc92 => cron-jobs} | 0
.../0.17.0/features/cron-jobs/index.html | 293 ----
...utors20191213-22326-vn4c2g => custom-executors} | 0
.../0.17.0/features/custom-executors/index.html | 397 ------
...ob-updates20191213-22326-54k6mn => job-updates} | 0
.../0.17.0/features/job-updates/index.html | 259 ----
...fetcher20191213-22326-1lkuhk1 => mesos-fetcher} | 0
.../0.17.0/features/mesos-fetcher/index.html | 213 ---
...itenancy20191213-22326-1jmuee7 => multitenancy} | 0
.../0.17.0/features/multitenancy/index.html | 234 ---
...ion20191213-22326-e7h3ha => resource-isolation} | 0
.../0.17.0/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-13toyrb => service-discovery} | 0
.../0.17.0/features/service-discovery/index.html | 202 ---
.../services20191213-22326-1mbjrdx => services} | 0
.../0.17.0/features/services/index.html | 260 ----
...a-metrics20191213-22326-1ufvdyb => sla-metrics} | 0
.../0.17.0/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-bxfsnj => webhooks} | 0
.../0.17.0/features/webhooks/index.html | 230 ---
.../overview20191213-22326-1icqf63 => overview} | 0
.../0.17.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-1edrg56 => tutorial} | 0
.../0.17.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-239nxo => vagrant} | 0
.../0.17.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1wk3eci => backup-restore} | 0
.../0.17.0/operations/backup-restore/index.html | 254 ----
...guration20191213-22326-yga88n => configuration} | 0
.../0.17.0/operations/configuration/index.html | 427 ------
...tallation20191213-22326-vtfdnb => installation} | 0
.../0.17.0/operations/installation/index.html | 479 -------
.../monitoring20191213-22326-dj3lrq => monitoring} | 0
.../0.17.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-bmog6z => security} | 0
.../0.17.0/operations/security/index.html | 509 -------
.../storage20191213-22326-173ly2w => storage} | 0
.../0.17.0/operations/storage/index.html | 258 ----
...3-22326-6kzlxw => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mmands20191213-22326-jgg324 => client-commands} | 0
.../0.17.0/reference/client-commands/index.html | 484 -------
...ent-hooks20191213-22326-fkxox1 => client-hooks} | 0
.../0.17.0/reference/client-hooks/index.html | 415 ------
...guration20191213-22326-uf67bc => configuration} | 0
...3-22326-r05zm9 => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...1213-22326-128e5kk => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-155d543 => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.17.0/reference/configuration/index.html | 1259 -----------------
...91213-22326-1ogjt25 => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 416 ------
...s20191213-22326-1b5rt9g => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...ecycle20191213-22326-19mxv45 => task-lifecycle} | 0
.../0.17.0/reference/task-lifecycle/index.html | 302 ----
...ntations20191213-22326-rohjgj => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-b0phqy => tools} | 0
.../0.18.0/additional-resources/tools/index.html | 191 ---
...ributing20191213-22326-1xn89o6 => contributing} | 0
.../documentation/0.18.0/contributing/index.html | 251 ----
.../{client/client20191213-22326-mc92vk => client} | 0
.../0.18.0/development/client/index.html | 300 ----
...guide20191213-22326-k8099b => committers-guide} | 0
.../0.18.0/development/committers-guide/index.html | 252 ----
...migration20191213-22326-9cedbb => db-migration} | 0
.../0.18.0/development/db-migration/index.html | 187 ---
...ments20191213-22326-q54zqh => design-documents} | 0
.../0.18.0/development/design-documents/index.html | 178 ---
...nd-hooks20191213-22326-nyy22q => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-6gut0n => scheduler} | 0
.../0.18.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-1af2p6m => thermos} | 0
.../0.18.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-1jy2m01 => thrift} | 0
.../0.18.0/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-m3ipt3 => ui} | 0
.../documentation/0.18.0/development/ui/index.html | 198 ---
...nstraints20191213-22326-1jeffc5 => constraints} | 0
.../0.18.0/features/constraints/index.html | 268 ----
.../containers20191213-22326-1w2n01 => containers} | 0
.../0.18.0/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-tkfni5 => cron-jobs} | 0
.../0.18.0/features/cron-jobs/index.html | 293 ----
...utors20191213-22326-8lb0km => custom-executors} | 0
.../0.18.0/features/custom-executors/index.html | 395 ------
...ob-updates20191213-22326-c56adi => job-updates} | 0
.../0.18.0/features/job-updates/index.html | 259 ----
...fetcher20191213-22326-1fkbwj8 => mesos-fetcher} | 0
.../0.18.0/features/mesos-fetcher/index.html | 213 ---
...itenancy20191213-22326-10wjqwb => multitenancy} | 0
.../0.18.0/features/multitenancy/index.html | 234 ---
...on20191213-22326-1atqqm9 => resource-isolation} | 0
.../0.18.0/features/resource-isolation/index.html | 332 -----
...very20191213-22326-yh1o0r => service-discovery} | 0
.../0.18.0/features/service-discovery/index.html | 202 ---
.../services20191213-22326-4417zb => services} | 0
.../0.18.0/features/services/index.html | 260 ----
...a-metrics20191213-22326-1eu5qw4 => sla-metrics} | 0
.../0.18.0/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-aab3fk => webhooks} | 0
.../0.18.0/features/webhooks/index.html | 229 ---
.../overview20191213-22326-7rtxmj => overview} | 0
.../0.18.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-13nzona => tutorial} | 0
.../0.18.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-1yzkqjv => vagrant} | 0
.../0.18.0/getting-started/vagrant/index.html | 299 ----
...restore20191213-22326-ncfdqq => backup-restore} | 0
.../0.18.0/operations/backup-restore/index.html | 254 ----
...uration20191213-22326-1bje04i => configuration} | 0
.../0.18.0/operations/configuration/index.html | 517 -------
...allation20191213-22326-1f6a61f => installation} | 0
.../0.18.0/operations/installation/index.html | 418 ------
...monitoring20191213-22326-1kg2y30 => monitoring} | 0
.../0.18.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-66hdm0 => security} | 0
.../0.18.0/operations/security/index.html | 509 -------
.../storage20191213-22326-1ouwmds => storage} | 0
.../0.18.0/operations/storage/index.html | 257 ----
...ooting20191213-22326-qm7bjb => troubleshooting} | 0
.../0.18.0/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-379xbs => upgrades} | 0
.../0.18.0/operations/upgrades/index.html | 197 ---
...3-22326-sg8z97 => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mmands20191213-22326-7tyrae => client-commands} | 0
.../0.18.0/reference/client-commands/index.html | 497 -------
...ent-hooks20191213-22326-960ff2 => client-hooks} | 0
.../0.18.0/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1mcx45o => configuration} | 0
...-22326-173wkjw => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...91213-22326-xoel6h => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-1mo0500 => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.18.0/reference/configuration/index.html | 1290 -----------------
...0191213-22326-vhclra => observer-configuration} | 0
.../reference/observer-configuration/index.html | 241 ----
...191213-22326-s7czcj => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 420 ------
...s20191213-22326-15m4zmg => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...ecycle20191213-22326-18c6ybc => task-lifecycle} | 0
.../0.18.0/reference/task-lifecycle/index.html | 302 ----
...ntations20191213-22326-cmew1l => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-1da8sl4 => tools} | 0
.../0.18.1/additional-resources/tools/index.html | 191 ---
...tributing20191213-22326-mtbv4n => contributing} | 0
.../documentation/0.18.1/contributing/index.html | 251 ----
.../client20191213-22326-18vaokd => client} | 0
.../0.18.1/development/client/index.html | 300 ----
...uide20191213-22326-1ab21d3 => committers-guide} | 0
.../0.18.1/development/committers-guide/index.html | 252 ----
...igration20191213-22326-1xjlwgp => db-migration} | 0
.../0.18.1/development/db-migration/index.html | 187 ---
...ents20191213-22326-1bvsclw => design-documents} | 0
.../0.18.1/development/design-documents/index.html | 178 ---
...d-hooks20191213-22326-1l1h15b => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-hds6u4 => scheduler} | 0
.../0.18.1/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-zy6zya => thermos} | 0
.../0.18.1/development/thermos/index.html | 273 ----
.../{thrift/thrift20191213-22326-gh094k => thrift} | 0
.../0.18.1/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-g7zhqz => ui} | 0
.../documentation/0.18.1/development/ui/index.html | 198 ---
...nstraints20191213-22326-1e99p8p => constraints} | 0
.../0.18.1/features/constraints/index.html | 268 ----
...containers20191213-22326-1x5zfal => containers} | 0
.../0.18.1/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-12q49xz => cron-jobs} | 0
.../0.18.1/features/cron-jobs/index.html | 293 ----
...tors20191213-22326-1c84cen => custom-executors} | 0
.../0.18.1/features/custom-executors/index.html | 395 ------
...b-updates20191213-22326-1qr1g1b => job-updates} | 0
.../0.18.1/features/job-updates/index.html | 259 ----
...fetcher20191213-22326-1tcqt8a => mesos-fetcher} | 0
.../0.18.1/features/mesos-fetcher/index.html | 213 ---
...titenancy20191213-22326-85kuem => multitenancy} | 0
.../0.18.1/features/multitenancy/index.html | 234 ---
...on20191213-22326-1dzs8zd => resource-isolation} | 0
.../0.18.1/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-1r76bqz => service-discovery} | 0
.../0.18.1/features/service-discovery/index.html | 202 ---
.../services20191213-22326-1wm2y6f => services} | 0
.../0.18.1/features/services/index.html | 260 ----
...la-metrics20191213-22326-cclav7 => sla-metrics} | 0
.../0.18.1/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-44qqf => webhooks} | 0
.../0.18.1/features/webhooks/index.html | 229 ---
.../overview20191213-22326-3bg6eq => overview} | 0
.../0.18.1/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-necjo2 => tutorial} | 0
.../0.18.1/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-19u3ugj => vagrant} | 0
.../0.18.1/getting-started/vagrant/index.html | 299 ----
...restore20191213-22326-fpjrcx => backup-restore} | 0
.../0.18.1/operations/backup-restore/index.html | 254 ----
...guration20191213-22326-gbnioe => configuration} | 0
.../0.18.1/operations/configuration/index.html | 517 -------
...tallation20191213-22326-xltt1a => installation} | 0
.../0.18.1/operations/installation/index.html | 418 ------
...monitoring20191213-22326-1x54sc9 => monitoring} | 0
.../0.18.1/operations/monitoring/index.html | 349 -----
.../security20191213-22326-d6iw3m => security} | 0
.../0.18.1/operations/security/index.html | 509 -------
.../storage20191213-22326-kvqfbc => storage} | 0
.../0.18.1/operations/storage/index.html | 257 ----
...oting20191213-22326-1doxazt => troubleshooting} | 0
.../0.18.1/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-1tm7pp2 => upgrades} | 0
.../0.18.1/operations/upgrades/index.html | 197 ---
...-22326-1msyr2g => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mmands20191213-22326-8yj9eg => client-commands} | 0
.../0.18.1/reference/client-commands/index.html | 497 -------
...ent-hooks20191213-22326-g5xu2o => client-hooks} | 0
.../0.18.1/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1649vcf => configuration} | 0
...-22326-166tat8 => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...91213-22326-cflnep => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...0191213-22326-kfs6vp => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.18.1/reference/configuration/index.html | 1290 -----------------
...0191213-22326-2qinbn => observer-configuration} | 0
.../reference/observer-configuration/index.html | 241 ----
...191213-22326-gdrd1b => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 420 ------
...s20191213-22326-1d2tffv => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...fecycle20191213-22326-cu1l5c => task-lifecycle} | 0
.../0.18.1/reference/task-lifecycle/index.html | 302 ----
...tations20191213-22326-151zu04 => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-ljq9rf => tools} | 0
.../0.19.0/additional-resources/tools/index.html | 191 ---
...tributing20191213-22326-xiozqn => contributing} | 0
.../documentation/0.19.0/contributing/index.html | 251 ----
.../{client/client20191213-22326-3qsysg => client} | 0
.../0.19.0/development/client/index.html | 300 ----
...guide20191213-22326-zjp1o6 => committers-guide} | 0
.../0.19.0/development/committers-guide/index.html | 255 ----
...migration20191213-22326-jfgbjn => db-migration} | 0
.../0.19.0/development/db-migration/index.html | 187 ---
...ents20191213-22326-1y44mcj => design-documents} | 0
.../0.19.0/development/design-documents/index.html | 178 ---
...nd-hooks20191213-22326-i1hx3y => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-gjivfm => scheduler} | 0
.../0.19.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-pcauws => thermos} | 0
.../0.19.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-19ula70 => thrift} | 0
.../0.19.0/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-g41sw3 => ui} | 0
.../documentation/0.19.0/development/ui/index.html | 198 ---
...nstraints20191213-22326-18sffqz => constraints} | 0
.../0.19.0/features/constraints/index.html | 268 ----
...containers20191213-22326-1d0xclz => containers} | 0
.../0.19.0/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-1ehk273 => cron-jobs} | 0
.../0.19.0/features/cron-jobs/index.html | 293 ----
...utors20191213-22326-2widpg => custom-executors} | 0
.../0.19.0/features/custom-executors/index.html | 395 ------
...b-updates20191213-22326-1yxvwvf => job-updates} | 0
.../0.19.0/features/job-updates/index.html | 259 ----
...fetcher20191213-22326-1w5jayz => mesos-fetcher} | 0
.../0.19.0/features/mesos-fetcher/index.html | 213 ---
...itenancy20191213-22326-1b12869 => multitenancy} | 0
.../0.19.0/features/multitenancy/index.html | 235 ---
...on20191213-22326-1rvgqq6 => resource-isolation} | 0
.../0.19.0/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-19ykryh => service-discovery} | 0
.../0.19.0/features/service-discovery/index.html | 202 ---
.../services20191213-22326-vs66l1 => services} | 0
.../0.19.0/features/services/index.html | 260 ----
...a-metrics20191213-22326-17ox9bm => sla-metrics} | 0
.../0.19.0/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-vu2isg => webhooks} | 0
.../0.19.0/features/webhooks/index.html | 257 ----
.../overview20191213-22326-17m1ljq => overview} | 0
.../0.19.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-1v6hm57 => tutorial} | 0
.../0.19.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-1grabwu => vagrant} | 0
.../0.19.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1obkktc => backup-restore} | 0
.../0.19.0/operations/backup-restore/index.html | 254 ----
...uration20191213-22326-12s09y9 => configuration} | 0
.../0.19.0/operations/configuration/index.html | 517 -------
...tallation20191213-22326-i4lma7 => installation} | 0
.../0.19.0/operations/installation/index.html | 418 ------
...monitoring20191213-22326-1x3p5of => monitoring} | 0
.../0.19.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-ij8t30 => security} | 0
.../0.19.0/operations/security/index.html | 509 -------
.../storage20191213-22326-pa8hm9 => storage} | 0
.../0.19.0/operations/storage/index.html | 257 ----
...oting20191213-22326-11vrs8n => troubleshooting} | 0
.../0.19.0/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-1mv1v83 => upgrades} | 0
.../0.19.0/operations/upgrades/index.html | 197 ---
...3-22326-da0v0l => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mands20191213-22326-17hb07f => client-commands} | 0
.../0.19.0/reference/client-commands/index.html | 497 -------
...nt-hooks20191213-22326-1wl5p9b => client-hooks} | 0
.../0.19.0/reference/client-hooks/index.html | 415 ------
...guration20191213-22326-viccex => configuration} | 0
...3-22326-39ttid => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...191213-22326-m1x9f => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...0191213-22326-yn6acc => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.19.0/reference/configuration/index.html | 1303 -----------------
...191213-22326-14tk5m7 => observer-configuration} | 0
.../reference/observer-configuration/index.html | 241 ----
...91213-22326-1aggaue => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 404 ------
...s20191213-22326-187s2oi => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...ecycle20191213-22326-1cabanj => task-lifecycle} | 0
.../0.19.0/reference/task-lifecycle/index.html | 304 ----
...ntations20191213-22326-a9vaxb => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-17mvga1 => tools} | 0
.../0.19.1/additional-resources/tools/index.html | 191 ---
...tributing20191213-22326-zot857 => contributing} | 0
.../documentation/0.19.1/contributing/index.html | 251 ----
.../{client/client20191213-22326-wd96cj => client} | 0
.../0.19.1/development/client/index.html | 300 ----
...uide20191213-22326-1i5gcuv => committers-guide} | 0
.../0.19.1/development/committers-guide/index.html | 255 ----
...migration20191213-22326-8imlvk => db-migration} | 0
.../0.19.1/development/db-migration/index.html | 187 ---
...ents20191213-22326-1688pu9 => design-documents} | 0
.../0.19.1/development/design-documents/index.html | 178 ---
...d-hooks20191213-22326-161op0n => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-a3rm8o => scheduler} | 0
.../0.19.1/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-o8kc1y => thermos} | 0
.../0.19.1/development/thermos/index.html | 273 ----
.../thrift20191213-22326-1edpmx1 => thrift} | 0
.../0.19.1/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-pcq4is => ui} | 0
.../documentation/0.19.1/development/ui/index.html | 198 ---
...nstraints20191213-22326-1v4ntw1 => constraints} | 0
.../0.19.1/features/constraints/index.html | 268 ----
.../containers20191213-22326-dsmne => containers} | 0
.../0.19.1/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-77ysgs => cron-jobs} | 0
.../0.19.1/features/cron-jobs/index.html | 293 ----
...utors20191213-22326-sj3343 => custom-executors} | 0
.../0.19.1/features/custom-executors/index.html | 395 ------
...b-updates20191213-22326-1rcxj2v => job-updates} | 0
.../0.19.1/features/job-updates/index.html | 259 ----
...fetcher20191213-22326-1jztz5c => mesos-fetcher} | 0
.../0.19.1/features/mesos-fetcher/index.html | 213 ---
...titenancy20191213-22326-fv5h3m => multitenancy} | 0
.../0.19.1/features/multitenancy/index.html | 235 ---
...on20191213-22326-1uvgho7 => resource-isolation} | 0
.../0.19.1/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-1yyrxua => service-discovery} | 0
.../0.19.1/features/service-discovery/index.html | 202 ---
.../services20191213-22326-c92xiz => services} | 0
.../0.19.1/features/services/index.html | 260 ----
...a-metrics20191213-22326-1agojgd => sla-metrics} | 0
.../0.19.1/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-12c41a6 => webhooks} | 0
.../0.19.1/features/webhooks/index.html | 257 ----
.../overview20191213-22326-ucruyl => overview} | 0
.../0.19.1/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-1k2tefc => tutorial} | 0
.../0.19.1/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-36rya3 => vagrant} | 0
.../0.19.1/getting-started/vagrant/index.html | 299 ----
...-restore20191213-22326-w3jre => backup-restore} | 0
.../0.19.1/operations/backup-restore/index.html | 254 ----
...uration20191213-22326-1u78vdn => configuration} | 0
.../0.19.1/operations/configuration/index.html | 517 -------
...allation20191213-22326-1o8486u => installation} | 0
.../0.19.1/operations/installation/index.html | 418 ------
...monitoring20191213-22326-1g380p0 => monitoring} | 0
.../0.19.1/operations/monitoring/index.html | 349 -----
.../security20191213-22326-n40p8p => security} | 0
.../0.19.1/operations/security/index.html | 509 -------
.../storage20191213-22326-zeljme => storage} | 0
.../0.19.1/operations/storage/index.html | 257 ----
...oting20191213-22326-1vebcle => troubleshooting} | 0
.../0.19.1/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-hybph7 => upgrades} | 0
.../0.19.1/operations/upgrades/index.html | 197 ---
...-22326-1s9m705 => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mands20191213-22326-1u2di5u => client-commands} | 0
.../0.19.1/reference/client-commands/index.html | 497 -------
...ent-hooks20191213-22326-1amdxx => client-hooks} | 0
.../0.19.1/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1ttcfrm => configuration} | 0
...-22326-1b9vm4h => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...91213-22326-aut8p2 => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-1flc7ob => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.19.1/reference/configuration/index.html | 1303 -----------------
...191213-22326-11bx6c7 => observer-configuration} | 0
.../reference/observer-configuration/index.html | 241 ----
...91213-22326-1f37lrf => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 404 ------
...s20191213-22326-1c86unv => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...fecycle20191213-22326-9ebam1 => task-lifecycle} | 0
.../0.19.1/reference/task-lifecycle/index.html | 304 ----
...tations20191213-22326-16g0xv3 => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-7aw4mh => tools} | 0
.../0.20.0/additional-resources/tools/index.html | 191 ---
...ributing20191213-22326-18r4w07 => contributing} | 0
.../documentation/0.20.0/contributing/index.html | 251 ----
.../client20191213-22326-1vxtkee => client} | 0
.../0.20.0/development/client/index.html | 300 ----
...uide20191213-22326-1qfdab2 => committers-guide} | 0
.../0.20.0/development/committers-guide/index.html | 255 ----
...migration20191213-22326-hai0c3 => db-migration} | 0
.../0.20.0/development/db-migration/index.html | 187 ---
...ments20191213-22326-hunvna => design-documents} | 0
.../0.20.0/development/design-documents/index.html | 178 ---
...nd-hooks20191213-22326-or06o2 => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-1de5s5k => scheduler} | 0
.../0.20.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-16rs64s => thermos} | 0
.../0.20.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-18guah3 => thrift} | 0
.../0.20.0/development/thrift/index.html | 208 ---
.../development/{ui/ui20191213-22326-9wfmzm => ui} | 0
.../documentation/0.20.0/development/ui/index.html | 198 ---
...onstraints20191213-22326-3f13pm => constraints} | 0
.../0.20.0/features/constraints/index.html | 268 ----
...containers20191213-22326-116q1jo => containers} | 0
.../0.20.0/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-10fxgjv => cron-jobs} | 0
.../0.20.0/features/cron-jobs/index.html | 293 ----
...tors20191213-22326-1wqxlyp => custom-executors} | 0
.../0.20.0/features/custom-executors/index.html | 406 ------
...b-updates20191213-22326-1gvkedj => job-updates} | 0
.../0.20.0/features/job-updates/index.html | 259 ----
...s-fetcher20191213-22326-exef7 => mesos-fetcher} | 0
.../0.20.0/features/mesos-fetcher/index.html | 213 ---
...titenancy20191213-22326-p6xj8y => multitenancy} | 0
.../0.20.0/features/multitenancy/index.html | 235 ---
...on20191213-22326-14obgwv => resource-isolation} | 0
.../0.20.0/features/resource-isolation/index.html | 332 -----
...very20191213-22326-941jtf => service-discovery} | 0
.../0.20.0/features/service-discovery/index.html | 203 ---
.../services20191213-22326-mzo1he => services} | 0
.../0.20.0/features/services/index.html | 260 ----
...a-metrics20191213-22326-1mlwr18 => sla-metrics} | 0
.../0.20.0/features/sla-metrics/index.html | 392 -----
.../webhooks20191213-22326-1pw7a6e => webhooks} | 0
.../0.20.0/features/webhooks/index.html | 257 ----
.../overview20191213-22326-11tlot0 => overview} | 0
.../0.20.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-wtnphj => tutorial} | 0
.../0.20.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-6s1r9p => vagrant} | 0
.../0.20.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1rdezww => backup-restore} | 0
.../0.20.0/operations/backup-restore/index.html | 254 ----
...guration20191213-22326-sw2si1 => configuration} | 0
.../0.20.0/operations/configuration/index.html | 517 -------
...allation20191213-22326-1dsq7p1 => installation} | 0
.../0.20.0/operations/installation/index.html | 418 ------
...monitoring20191213-22326-1j1dwsh => monitoring} | 0
.../0.20.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-sgka8j => security} | 0
.../0.20.0/operations/security/index.html | 509 -------
.../storage20191213-22326-bno8w9 => storage} | 0
.../0.20.0/operations/storage/index.html | 257 ----
...ooting20191213-22326-bapxjf => troubleshooting} | 0
.../0.20.0/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-h73at6 => upgrades} | 0
.../0.20.0/operations/upgrades/index.html | 197 ---
...-22326-1hp2k7x => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mands20191213-22326-1obdbpr => client-commands} | 0
.../0.20.0/reference/client-commands/index.html | 497 -------
...ent-hooks20191213-22326-26b4ba => client-hooks} | 0
.../0.20.0/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1j6p0a4 => configuration} | 0
...3-22326-kbw0df => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...1213-22326-1xb3xlo => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-17wndyp => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.20.0/reference/configuration/index.html | 1385 ------------------
...191213-22326-1x9lvpb => observer-configuration} | 0
.../reference/observer-configuration/index.html | 255 ----
...191213-22326-2n2m41 => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 408 ------
...ts20191213-22326-mt9485 => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...ifecycle20191213-22326-zmxmj => task-lifecycle} | 0
.../0.20.0/reference/task-lifecycle/index.html | 328 -----
...ntations20191213-22326-os8l22 => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-uhqtdv => tools} | 0
.../0.21.0/additional-resources/tools/index.html | 191 ---
...tributing20191213-22326-bcz7fg => contributing} | 0
.../documentation/0.21.0/contributing/index.html | 251 ----
.../client20191213-22326-1j4mt6m => client} | 0
.../0.21.0/development/client/index.html | 300 ----
...guide20191213-22326-p586x4 => committers-guide} | 0
.../0.21.0/development/committers-guide/index.html | 255 ----
...migration20191213-22326-7ygfaj => db-migration} | 0
.../0.21.0/development/db-migration/index.html | 187 ---
...ents20191213-22326-1ks6iog => design-documents} | 0
.../0.21.0/development/design-documents/index.html | 178 ---
...nd-hooks20191213-22326-bdtwuo => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-uyv2so => scheduler} | 0
.../0.21.0/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-1yy85xw => thermos} | 0
.../0.21.0/development/thermos/index.html | 273 ----
.../thrift20191213-22326-1gkjvyh => thrift} | 0
.../0.21.0/development/thrift/index.html | 208 ---
.../{ui/ui20191213-22326-1xkl7lu => ui} | 0
.../documentation/0.21.0/development/ui/index.html | 198 ---
...onstraints20191213-22326-evtq9x => constraints} | 0
.../0.21.0/features/constraints/index.html | 268 ----
...containers20191213-22326-16657wh => containers} | 0
.../0.21.0/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-1bnkdke => cron-jobs} | 0
.../0.21.0/features/cron-jobs/index.html | 293 ----
...tors20191213-22326-1jp7c9z => custom-executors} | 0
.../0.21.0/features/custom-executors/index.html | 406 ------
...b-updates20191213-22326-13mp29a => job-updates} | 0
.../0.21.0/features/job-updates/index.html | 270 ----
...-fetcher20191213-22326-8sgfjd => mesos-fetcher} | 0
.../0.21.0/features/mesos-fetcher/index.html | 213 ---
...itenancy20191213-22326-10wsh1y => multitenancy} | 0
.../0.21.0/features/multitenancy/index.html | 235 ---
...ion20191213-22326-vgvocr => resource-isolation} | 0
.../0.21.0/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-1maqsp0 => service-discovery} | 0
.../0.21.0/features/service-discovery/index.html | 203 ---
.../services20191213-22326-2c41u => services} | 0
.../0.21.0/features/services/index.html | 260 ----
...a-metrics20191213-22326-11j05rr => sla-metrics} | 0
.../0.21.0/features/sla-metrics/index.html | 392 -----
...ents20191213-22326-1eab64v => sla-requirements} | 0
.../0.21.0/features/sla-requirements/index.html | 334 -----
.../webhooks20191213-22326-athqzc => webhooks} | 0
.../0.21.0/features/webhooks/index.html | 257 ----
.../overview20191213-22326-26cb40 => overview} | 0
.../0.21.0/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-t8pqba => tutorial} | 0
.../0.21.0/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-11hsur7 => vagrant} | 0
.../0.21.0/getting-started/vagrant/index.html | 299 ----
...estore20191213-22326-1n201zp => backup-restore} | 0
.../0.21.0/operations/backup-restore/index.html | 237 ----
...uration20191213-22326-1fagwsd => configuration} | 0
.../0.21.0/operations/configuration/index.html | 557 --------
...allation20191213-22326-162k7s5 => installation} | 0
.../0.21.0/operations/installation/index.html | 418 ------
...monitoring20191213-22326-15tg02f => monitoring} | 0
.../0.21.0/operations/monitoring/index.html | 349 -----
.../security20191213-22326-1lsvv90 => security} | 0
.../0.21.0/operations/security/index.html | 509 -------
.../storage20191213-22326-18navnr => storage} | 0
.../0.21.0/operations/storage/index.html | 257 ----
...oting20191213-22326-1legm6e => troubleshooting} | 0
.../0.21.0/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-x0kklz => upgrades} | 0
.../0.21.0/operations/upgrades/index.html | 197 ---
...3-22326-vge2bz => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mmands20191213-22326-6i0k6r => client-commands} | 0
.../0.21.0/reference/client-commands/index.html | 497 -------
...ent-hooks20191213-22326-7w9ann => client-hooks} | 0
.../0.21.0/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-1jzqekk => configuration} | 0
...3-22326-gmvh9v => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...91213-22326-82ca0j => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...0191213-22326-ye732r => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../0.21.0/reference/configuration/index.html | 1494 --------------------
...191213-22326-16sboab => observer-configuration} | 0
.../reference/observer-configuration/index.html | 255 ----
...91213-22326-1qsmhs4 => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 424 ------
...s20191213-22326-12v4qp9 => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...fecycle20191213-22326-odu6am => task-lifecycle} | 0
.../0.21.0/reference/task-lifecycle/index.html | 328 -----
...mands20191213-22326-1aie412 => client-commands} | 0
.../0.5.0-incubating/client-commands/index.html | 652 ---------
.../clientv220191213-22326-trq6oi => clientv2} | 0
.../0.5.0-incubating/clientv2/index.html | 578 --------
.../committers20191213-22326-5onrd6 => committers} | 0
.../0.5.0-incubating/committers/index.html | 198 ---
...91213-22326-1u5sjob => configuration-reference} | 0
.../configuration-reference/index.html | 928 ------------
...0191213-22326-ysle20 => configuration-tutorial} | 0
.../configuration-tutorial/index.html | 1303 -----------------
...ributing20191213-22326-11tffek => contributing} | 0
.../0.5.0-incubating/contributing/index.html | 201 ---
...213-22326-hdv3k6 => deploying-aurora-scheduler} | 0
.../deploying-aurora-scheduler/index.html | 300 ----
...d-hooks20191213-22326-1im9faf => command-hooks} | 0
.../design/command-hooks/index.html | 419 ------
...91213-22326-4ivad2 => developing-aurora-client} | 0
.../developing-aurora-client/index.html | 280 ----
...13-22326-ac4p3l => developing-aurora-scheduler} | 0
.../developing-aurora-scheduler/index.html | 259 ----
.../{hooks/hooks20191213-22326-obj7ix => hooks} | 0
.../0.5.0-incubating/hooks/index.html | 424 ------
...ion20191213-22326-xxwpb6 => resource-isolation} | 0
.../0.5.0-incubating/resource-isolation/index.html | 304 ----
.../{sla/sla20191213-22326-7y7erl => sla} | 0
.../documentation/0.5.0-incubating/sla/index.html | 349 -----
.../tutorial20191213-22326-zyn2kv => tutorial} | 0
.../0.5.0-incubating/tutorial/index.html | 421 ------
...user-guide20191213-22326-1hqme02 => user-guide} | 0
.../0.5.0-incubating/user-guide/index.html | 521 -------
.../vagrant20191213-22326-1iscppu => vagrant} | 0
.../0.5.0-incubating/vagrant/index.html | 207 ---
...3-22326-xi5jzw => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 267 ----
...mmands20191213-22326-mj007x => client-commands} | 0
.../0.6.0-incubating/client-commands/index.html | 689 ---------
.../clientv220191213-22326-mlsarp => clientv2} | 0
.../0.6.0-incubating/clientv2/index.html | 578 --------
...committers20191213-22326-1j0kxur => committers} | 0
.../0.6.0-incubating/committers/index.html | 225 ---
...191213-22326-2jrutt => configuration-reference} | 0
.../configuration-reference/index.html | 974 -------------
...191213-22326-1cr0mz8 => configuration-tutorial} | 0
.../configuration-tutorial/index.html | 1346 ------------------
...ributing20191213-22326-1dkqhev => contributing} | 0
.../0.6.0-incubating/contributing/index.html | 222 ---
.../cron-jobs20191213-22326-1m22zv7 => cron-jobs} | 0
.../0.6.0-incubating/cron-jobs/index.html | 302 ----
...13-22326-1kkktz0 => deploying-aurora-scheduler} | 0
.../deploying-aurora-scheduler/index.html | 466 ------
...nd-hooks20191213-22326-8q8p92 => command-hooks} | 0
.../design/command-hooks/index.html | 419 ------
...1213-22326-10pwbm4 => developing-aurora-client} | 0
.../developing-aurora-client/index.html | 288 ----
...3-22326-1rvfswy => developing-aurora-scheduler} | 0
.../developing-aurora-scheduler/index.html | 259 ----
.../{hooks/hooks20191213-22326-4qnypm => hooks} | 0
.../0.6.0-incubating/hooks/index.html | 424 ------
...monitoring20191213-22326-1kvjr4b => monitoring} | 0
.../0.6.0-incubating/monitoring/index.html | 401 ------
...on20191213-22326-1a48hxv => resource-isolation} | 0
.../0.6.0-incubating/resource-isolation/index.html | 304 ----
...rage20191213-22326-4phawi => scheduler-storage} | 0
.../0.6.0-incubating/scheduler-storage/index.html | 201 ---
.../{sla/sla20191213-22326-ca00fh => sla} | 0
.../documentation/0.6.0-incubating/sla/index.html | 349 -----
.../storage20191213-22326-17ed6ke => storage} | 0
...config20191213-22326-1nuk8q7 => storage-config} | 0
.../0.6.0-incubating/storage-config/index.html | 318 -----
.../0.6.0-incubating/storage/index.html | 250 ----
...1213-22326-13hw2m8 => test-resource-generation} | 0
.../test-resource-generation/index.html | 181 ---
.../tutorial20191213-22326-p6vxk => tutorial} | 0
.../0.6.0-incubating/tutorial/index.html | 421 ------
...user-guide20191213-22326-1auag14 => user-guide} | 0
.../0.6.0-incubating/user-guide/index.html | 550 -------
.../vagrant20191213-22326-kb6yrj => vagrant} | 0
.../0.6.0-incubating/vagrant/index.html | 207 ---
...-22326-1l7aq51 => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 267 ----
...mands20191213-22326-10s53ob => client-commands} | 0
.../0.7.0-incubating/client-commands/index.html | 545 -------
...committers20191213-22326-17cyss6 => committers} | 0
.../0.7.0-incubating/committers/index.html | 225 ---
...191213-22326-ycxy6x => configuration-reference} | 0
.../configuration-reference/index.html | 1017 -------------
...0191213-22326-mn6n10 => configuration-tutorial} | 0
.../configuration-tutorial/index.html | 1323 -----------------
...tributing20191213-22326-iwigui => contributing} | 0
.../0.7.0-incubating/contributing/index.html | 232 ---
.../cron-jobs20191213-22326-1582qn2 => cron-jobs} | 0
.../0.7.0-incubating/cron-jobs/index.html | 303 ----
...213-22326-x0facg => deploying-aurora-scheduler} | 0
.../deploying-aurora-scheduler/index.html | 485 -------
...nd-hooks20191213-22326-u3h32v => command-hooks} | 0
.../design/command-hooks/index.html | 257 ----
...91213-22326-ep3pt2 => developing-aurora-client} | 0
.../developing-aurora-client/index.html | 240 ----
...13-22326-87aifc => developing-aurora-scheduler} | 0
.../developing-aurora-scheduler/index.html | 259 ----
.../{hooks/hooks20191213-22326-98i3sf => hooks} | 0
.../0.7.0-incubating/hooks/index.html | 424 ------
...monitoring20191213-22326-1hklc0o => monitoring} | 0
.../0.7.0-incubating/monitoring/index.html | 401 ------
...ion20191213-22326-bv971k => resource-isolation} | 0
.../0.7.0-incubating/resource-isolation/index.html | 304 ----
...age20191213-22326-1ts7a62 => scheduler-storage} | 0
.../0.7.0-incubating/scheduler-storage/index.html | 201 ---
.../{sla/sla20191213-22326-1m5zybv => sla} | 0
.../documentation/0.7.0-incubating/sla/index.html | 349 -----
.../storage20191213-22326-1lq9e7n => storage} | 0
...-config20191213-22326-i2z6qc => storage-config} | 0
.../0.7.0-incubating/storage-config/index.html | 318 -----
.../0.7.0-incubating/storage/index.html | 250 ----
...91213-22326-5twatr => test-resource-generation} | 0
.../test-resource-generation/index.html | 181 ---
.../tutorial20191213-22326-ypoj5q => tutorial} | 0
.../0.7.0-incubating/tutorial/index.html | 421 ------
...user-guide20191213-22326-13185k6 => user-guide} | 0
.../0.7.0-incubating/user-guide/index.html | 542 -------
.../vagrant20191213-22326-cyed9m => vagrant} | 0
.../0.7.0-incubating/vagrant/index.html | 210 ---
...3-22326-ep49kw => client-cluster-configuration} | 0
.../0.8.0/client-cluster-configuration/index.html | 267 ----
...mands20191213-22326-1yfz2hd => client-commands} | 0
.../documentation/0.8.0/client-commands/index.html | 565 --------
.../committers20191213-22326-n4k05d => committers} | 0
content/documentation/0.8.0/committers/index.html | 225 ---
...91213-22326-1r2xlvl => configuration-reference} | 0
.../0.8.0/configuration-reference/index.html | 1032 --------------
...0191213-22326-jytpnx => configuration-tutorial} | 0
.../0.8.0/configuration-tutorial/index.html | 1324 -----------------
...tributing20191213-22326-v1219q => contributing} | 0
.../documentation/0.8.0/contributing/index.html | 232 ---
.../cron-jobs20191213-22326-132jewb => cron-jobs} | 0
content/documentation/0.8.0/cron-jobs/index.html | 303 ----
...13-22326-1t1dg0t => deploying-aurora-scheduler} | 0
.../0.8.0/deploying-aurora-scheduler/index.html | 497 -------
...nd-hooks20191213-22326-h1bu41 => command-hooks} | 0
.../0.8.0/design/command-hooks/index.html | 257 ----
...91213-22326-eyca4x => developing-aurora-client} | 0
.../0.8.0/developing-aurora-client/index.html | 244 ----
...13-22326-i6rv3v => developing-aurora-scheduler} | 0
.../0.8.0/developing-aurora-scheduler/index.html | 263 ----
.../{hooks/hooks20191213-22326-px6wev => hooks} | 0
content/documentation/0.8.0/hooks/index.html | 434 ------
.../monitoring20191213-22326-8efsko => monitoring} | 0
content/documentation/0.8.0/monitoring/index.html | 349 -----
...ion20191213-22326-u0lpjj => resource-isolation} | 0
.../0.8.0/resource-isolation/index.html | 304 ----
...age20191213-22326-10ekbpx => scheduler-storage} | 0
.../0.8.0/scheduler-storage/index.html | 201 ---
.../security20191213-22326-1x18hyt => security} | 0
content/documentation/0.8.0/security/index.html | 420 ------
.../0.8.0/{sla/sla20191213-22326-g3c1q7 => sla} | 0
content/documentation/0.8.0/sla/index.html | 349 -----
.../storage20191213-22326-1pft9xc => storage} | 0
...config20191213-22326-1lfhc2e => storage-config} | 0
.../documentation/0.8.0/storage-config/index.html | 318 -----
content/documentation/0.8.0/storage/index.html | 250 ----
...91213-22326-gng37z => test-resource-generation} | 0
.../0.8.0/test-resource-generation/index.html | 181 ---
...ion20191213-22326-jmhibt => thrift-deprecation} | 0
.../0.8.0/thrift-deprecation/index.html | 209 ---
.../tutorial20191213-22326-np63yp => tutorial} | 0
content/documentation/0.8.0/tutorial/index.html | 421 ------
...user-guide20191213-22326-1tof2ki => user-guide} | 0
content/documentation/0.8.0/user-guide/index.html | 542 -------
.../vagrant20191213-22326-x921f3 => vagrant} | 0
content/documentation/0.8.0/vagrant/index.html | 280 ----
...-22326-1f4c3o9 => client-cluster-configuration} | 0
.../0.9.0/client-cluster-configuration/index.html | 267 ----
...mmands20191213-22326-p27u6v => client-commands} | 0
.../documentation/0.9.0/client-commands/index.html | 565 --------
...committers20191213-22326-1ye2o0b => committers} | 0
content/documentation/0.9.0/committers/index.html | 225 ---
...91213-22326-1ehbr4x => configuration-reference} | 0
.../0.9.0/configuration-reference/index.html | 1112 ---------------
...191213-22326-1vi83tk => configuration-tutorial} | 0
.../0.9.0/configuration-tutorial/index.html | 1324 -----------------
...ributing20191213-22326-162kon6 => contributing} | 0
.../documentation/0.9.0/contributing/index.html | 232 ---
.../cron-jobs20191213-22326-qw4v39 => cron-jobs} | 0
content/documentation/0.9.0/cron-jobs/index.html | 303 ----
...13-22326-1frnz68 => deploying-aurora-scheduler} | 0
.../0.9.0/deploying-aurora-scheduler/index.html | 497 -------
...nd-hooks20191213-22326-q6e9ak => command-hooks} | 0
.../0.9.0/design/command-hooks/index.html | 257 ----
...1213-22326-1nw14zq => developing-aurora-client} | 0
.../0.9.0/developing-aurora-client/index.html | 244 ----
...13-22326-en6ffj => developing-aurora-scheduler} | 0
.../0.9.0/developing-aurora-scheduler/index.html | 263 ----
.../{hooks/hooks20191213-22326-15f8z39 => hooks} | 0
content/documentation/0.9.0/hooks/index.html | 434 ------
.../monitoring20191213-22326-yphx8l => monitoring} | 0
content/documentation/0.9.0/monitoring/index.html | 349 -----
...ntations20191213-22326-kaxmcu => presentations} | 0
.../documentation/0.9.0/presentations/index.html | 205 ---
...on20191213-22326-172d1gj => resource-isolation} | 0
.../0.9.0/resource-isolation/index.html | 304 ----
...rage20191213-22326-f9xuza => scheduler-storage} | 0
.../0.9.0/scheduler-storage/index.html | 201 ---
.../security20191213-22326-ftpiwa => security} | 0
content/documentation/0.9.0/security/index.html | 420 ------
.../0.9.0/{sla/sla20191213-22326-99mobw => sla} | 0
content/documentation/0.9.0/sla/index.html | 350 -----
.../storage20191213-22326-2p501l => storage} | 0
...config20191213-22326-1xo6vj5 => storage-config} | 0
.../documentation/0.9.0/storage-config/index.html | 318 -----
content/documentation/0.9.0/storage/index.html | 250 ----
...1213-22326-1ghfryj => test-resource-generation} | 0
.../0.9.0/test-resource-generation/index.html | 180 ---
...on20191213-22326-15nc83b => thrift-deprecation} | 0
.../0.9.0/thrift-deprecation/index.html | 209 ---
.../tutorial20191213-22326-1040ogr => tutorial} | 0
content/documentation/0.9.0/tutorial/index.html | 421 ------
.../user-guide20191213-22326-knqjze => user-guide} | 0
content/documentation/0.9.0/user-guide/index.html | 542 -------
.../vagrant20191213-22326-x848zt => vagrant} | 0
content/documentation/0.9.0/vagrant/index.html | 280 ----
...ntations20191213-22326-8gp04o => presentations} | 0
.../additional-resources/presentations/index.html | 235 ---
.../{tools/tools20191213-22326-cviofe => tools} | 0
.../latest/additional-resources/tools/index.html | 191 ---
...tributing20191213-22326-b2zbuf => contributing} | 0
.../documentation/latest/contributing/index.html | 251 ----
.../client20191213-22326-1nupzl9 => client} | 0
.../latest/development/client/index.html | 300 ----
...guide20191213-22326-ar1ms2 => committers-guide} | 0
.../latest/development/committers-guide/index.html | 255 ----
...migration20191213-22326-m80x3w => db-migration} | 0
.../latest/development/db-migration/index.html | 187 ---
...ents20191213-22326-1jopuay => design-documents} | 0
.../latest/development/design-documents/index.html | 178 ---
...nd-hooks20191213-22326-kdudva => command-hooks} | 0
.../development/design/command-hooks/index.html | 257 ----
.../scheduler20191213-22326-1t7w5oa => scheduler} | 0
.../latest/development/scheduler/index.html | 262 ----
.../thermos20191213-22326-14687t8 => thermos} | 0
.../latest/development/thermos/index.html | 273 ----
.../{thrift/thrift20191213-22326-2s0lc5 => thrift} | 0
.../latest/development/thrift/index.html | 208 ---
.../{ui/ui20191213-22326-1ubr358 => ui} | 0
.../documentation/latest/development/ui/index.html | 198 ---
...nstraints20191213-22326-1ibwixj => constraints} | 0
.../latest/features/constraints/index.html | 268 ----
.../containers20191213-22326-cfzklr => containers} | 0
.../latest/features/containers/index.html | 280 ----
.../cron-jobs20191213-22326-58z0iq => cron-jobs} | 0
.../latest/features/cron-jobs/index.html | 293 ----
...tors20191213-22326-1caugai => custom-executors} | 0
.../latest/features/custom-executors/index.html | 406 ------
...ob-updates20191213-22326-2n6ybr => job-updates} | 0
.../latest/features/job-updates/index.html | 270 ----
...fetcher20191213-22326-1eor435 => mesos-fetcher} | 0
.../latest/features/mesos-fetcher/index.html | 213 ---
...itenancy20191213-22326-1gqt108 => multitenancy} | 0
.../latest/features/multitenancy/index.html | 235 ---
...ion20191213-22326-3cs3ku => resource-isolation} | 0
.../latest/features/resource-isolation/index.html | 332 -----
...ery20191213-22326-1jgzkg8 => service-discovery} | 0
.../latest/features/service-discovery/index.html | 203 ---
.../services20191213-22326-1afjsxg => services} | 0
.../latest/features/services/index.html | 260 ----
...sla-metrics20191213-22326-xf7sj => sla-metrics} | 0
.../latest/features/sla-metrics/index.html | 392 -----
...ents20191213-22326-1s3bm7s => sla-requirements} | 0
.../latest/features/sla-requirements/index.html | 334 -----
.../webhooks20191213-22326-1qkqx71 => webhooks} | 0
.../latest/features/webhooks/index.html | 257 ----
.../overview20191213-22326-1i6lwgb => overview} | 0
.../latest/getting-started/overview/index.html | 261 ----
.../tutorial20191213-22326-1la2r9 => tutorial} | 0
.../latest/getting-started/tutorial/index.html | 411 ------
.../vagrant20191213-22326-1x0gzv8 => vagrant} | 0
.../latest/getting-started/vagrant/index.html | 299 ----
...restore20191213-22326-axhiyq => backup-restore} | 0
.../latest/operations/backup-restore/index.html | 237 ----
...guration20191213-22326-l9rie6 => configuration} | 0
.../latest/operations/configuration/index.html | 557 --------
...allation20191213-22326-1ubyy95 => installation} | 0
.../latest/operations/installation/index.html | 418 ------
.../monitoring20191213-22326-ovc3ft => monitoring} | 0
.../latest/operations/monitoring/index.html | 349 -----
.../security20191213-22326-1jwzf9x => security} | 0
.../latest/operations/security/index.html | 509 -------
.../storage20191213-22326-1soisim => storage} | 0
.../latest/operations/storage/index.html | 257 ----
...oting20191213-22326-13j2iqy => troubleshooting} | 0
.../latest/operations/troubleshooting/index.html | 269 ----
.../upgrades20191213-22326-93cmb => upgrades} | 0
.../latest/operations/upgrades/index.html | 197 ---
...3-22326-ey64xv => client-cluster-configuration} | 0
.../client-cluster-configuration/index.html | 296 ----
...mmands20191213-22326-2y917f => client-commands} | 0
.../latest/reference/client-commands/index.html | 497 -------
...nt-hooks20191213-22326-1ucbrnb => client-hooks} | 0
.../latest/reference/client-hooks/index.html | 415 ------
...uration20191213-22326-19ljr3y => configuration} | 0
...-22326-1pewj6g => configuration-best-practices} | 0
.../configuration-best-practices/index.html | 333 -----
...1213-22326-1lqxvte => configuration-templating} | 0
.../reference/configuration-templating/index.html | 456 ------
...191213-22326-1h588tp => configuration-tutorial} | 0
.../reference/configuration-tutorial/index.html | 690 ---------
.../latest/reference/configuration/index.html | 1494 --------------------
...191213-22326-1bsgfd8 => observer-configuration} | 0
.../reference/observer-configuration/index.html | 255 ----
...191213-22326-t3tvee => scheduler-configuration} | 0
.../reference/scheduler-configuration/index.html | 424 ------
...ts20191213-22326-v1sre6 => scheduler-endpoints} | 0
.../reference/scheduler-endpoints/index.html | 176 ---
...ecycle20191213-22326-1hkej3z => task-lifecycle} | 0
.../latest/reference/task-lifecycle/index.html | 328 -----
content/sitemap.xml | 52 +-
data/downloads.yml | 40 +
data/mailing_lists.yml | 20 +
1491 files changed, 86 insertions(+), 254477 deletions(-)
diff --git a/content/blog/2015-upcoming-apache-aurora-meetups/index.html b/content/blog/2015-upcoming-apache-aurora-meetups
similarity index 100%
rename from content/blog/2015-upcoming-apache-aurora-meetups/index.html
rename to content/blog/2015-upcoming-apache-aurora-meetups
diff --git a/content/blog/2015-upcoming-apache-aurora-meetups/2015-upcoming-apache-aurora-meetups20191213-22326-1geefad b/content/blog/2015-upcoming-apache-aurora-meetups/2015-upcoming-apache-aurora-meetups20191213-22326-1geefad
deleted file mode 100644
index 4c548be..0000000
--- a/content/blog/2015-upcoming-apache-aurora-meetups/2015-upcoming-apache-aurora-meetups20191213-22326-1geefad
+++ /dev/null
@@ -1,129 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Dave Lester</strong></p>
- <p><a href="http://twitter.com/davelester">@davelester</a></p>
- </span>
- </span>
- <p><em>Posted March 18, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>Upcoming Apache Aurora Meetups in NYC and the Bay Area</h1>
-
- <p>Meetups are opportunities to bring together members of an open source community to learn about the project, share best practices, and meet one another; naturally we’re excited to see a growing number of events featuring Apache Aurora, and we hope you’ll join us at a meetup near you!</p>
-
-<p>There are two upcoming Apache Aurora meetups on our radar:</p>
-
-<ul>
-<li>New York City, March 25th, 2015 - <a href="http://www.meetup.com/Apache-Mesos-NYC-Meetup/events/220801840/">NYC MUG, Apache Aurora meetup</a></li>
-<li>Bay Area, April 30th, 2015 - <a href="http://www.meetup.com/Bay-Area-Apache-Aurora-Users-Group/events/221219480/">Bay Area Apache Aurora Users meetup, From Monolith to Microservices w/ Aurora</a></li>
-</ul>
-
-<h2 id="apache-aurora-users-groups">Apache Aurora Users Groups</h2>
-
-<p>Live in San Francisco or the surrounding Bay Area? Join the recently-established <a href="http://www.meetup.com/Bay-Area-Apache-Aurora-Users-Group/">Bay Area Apache Aurora Users Group</a>, which will be home to future Apache Aurora meetups, in addition to the existing <a href="www.meetup.com/Bay-Area-Mesos-User-Group/">Apache Mesos User Group</a>.</p>
-
-<p>If you’re interested in establishing an Apache Aurora Users Group in a city near you or you’re hosting an Apache Aurora talk, please let us know on the project mailing list (<a href="mailto:dev@aurora.apache.org">dev@aurora.apache.org</a>) or IRC (#aurora on freenode.net) and we’ll help you promote your events.</p>
-
-<h2 id="recent-meetup-videos">Recent Meetup Videos</h2>
-
-<p>On February 19th, the Bay Area Apache Mesos User Group hosted a meetup on Apache Aurora, and videos from the two talks are now online. Check them out:</p>
-
-<p><em>Using Apache Aurora + Docker to migrate to a microservice architecture by Steve Niemitz (TellApart)</em></p>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/ZZXtXLvTXAE" frameborder="0" allowfullscreen></iframe>
-
-<p><em>Running Apache Aurora and Mesos at Twitter by Joe Smith (Twitter)</em></p>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/E4lxX6epM_U" frameborder="0" allowfullscreen></iframe>
-
-<p>Hope to see you at a future meetup!</p>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-10-0-released/index.html b/content/blog/aurora-0-10-0-released
similarity index 100%
rename from content/blog/aurora-0-10-0-released/index.html
rename to content/blog/aurora-0-10-0-released
diff --git a/content/blog/aurora-0-10-0-released/aurora-0-10-0-released20191213-22326-d3z1yj b/content/blog/aurora-0-10-0-released/aurora-0-10-0-released20191213-22326-d3z1yj
deleted file mode 100644
index 5216a4a..0000000
--- a/content/blog/aurora-0-10-0-released/aurora-0-10-0-released20191213-22326-d3z1yj
+++ /dev/null
@@ -1,149 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Bill Farner</strong></p>
- <p><a href="http://twitter.com/wfarner">@wfarner</a></p>
- </span>
- </span>
- <p><em>Posted December 12, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.10.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.10.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Upgraded Mesos to 0.23.0. Note: the Aurora executor now requires openssl runtime dependencies that
-were not previously required. You will need libcurl available on every Mesos slave (or Docker
-container) to successfully launch the Aurora executor. See
-<a href="https://github.com/apache/mesos/blob/ebcf8cc2f2f6c236f6e9315447c247e6348141e1/docs/getting-started.md">https://github.com/apache/mesos/blob/ebcf8cc2f2f6c236f6e9315447c247e6348141e1/docs/getting-started.md</a>
-for more details on Mesos runtime dependencies.</li>
-<li>Resource quota is no longer consumed by production jobs with a dedicated constraint (AURORA-1457).</li>
-<li>In the scheduler API, the <code>ConfigGroup.instanceIds</code> field has been deprecated, please use
-<code>ConfigGroup.instances</code> instead.</li>
-<li>In the scheduler API, all <code>SessionKey</code> arguments are now ignored by the scheduler as it has been
-replaced by <a href="/documentation/0.10.0/security/">security features</a> added in 0.8.0.</li>
-<li>The <code>--root</code> argument has been removed from the Thermos observer.</li>
-</ul>
-
-<p>Full release notes are available in the release <a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.10.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 19 contributors who made Apache Aurora 0.10.0 possible:</p>
-
-<ul>
-<li>Andrew Jorgensen</li>
-<li>Bill Farner</li>
-<li>Brian Brazil</li>
-<li>David Robinson</li>
-<li>Dmitriy Shirchenko</li>
-<li>Jake Farrell</li>
-<li>Jeffrey Schroeder</li>
-<li>Joe Smith</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Kevin Sweeney</li>
-<li>Mauricio Garavaglia</li>
-<li>Maxim Khutornenko</li>
-<li>Stephan Erb</li>
-<li>Steve Niemitz</li>
-<li>Thorhallur Sverrisson</li>
-<li>Zameer Manji</li>
-<li>Zane Silver</li>
-<li>Jake Farrell</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-11-0-released/index.html b/content/blog/aurora-0-11-0-released
similarity index 100%
rename from content/blog/aurora-0-11-0-released/index.html
rename to content/blog/aurora-0-11-0-released
diff --git a/content/blog/aurora-0-11-0-released/aurora-0-11-0-released20191213-22326-1k740o2 b/content/blog/aurora-0-11-0-released/aurora-0-11-0-released20191213-22326-1k740o2
deleted file mode 100644
index 244585f..0000000
--- a/content/blog/aurora-0-11-0-released/aurora-0-11-0-released20191213-22326-1k740o2
+++ /dev/null
@@ -1,163 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Bill Farner</strong></p>
- <p><a href="http://twitter.com/wfarner">@wfarner</a></p>
- </span>
- </span>
- <p><em>Posted December 23, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.11.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.11.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<p><strong>New/updated</strong></p>
-
-<ul>
-<li>Added built-in support for
-<a href="/documentation/0.11.0/configuration-reference/#logger">log rotation</a> of task stderr/stdout.</li>
-<li>Added support for performing task health checks using a
-<a href="/documentation/0.11.0/configuration-reference/#healthcheckconfig-objects">shell command</a>.</li>
-<li>Added support for accepting an executor configuration in JSON via scheduler command line argument
-<code>--custom_executor_config</code> which will override all other the command line arguments and default
-values pertaining to the executor.</li>
-<li>Added a new scheduler flag <code>--framework_announce_principal</code> to support use of authorization and
-rate limiting in Mesos.</li>
-<li>Upgraded Mesos to 0.24.1.</li>
-</ul>
-
-<p><strong>Deprecations and removals</strong></p>
-
-<ul>
-<li>The client-side updater has been removed, along with the CLI commands that used it:
-<code>aurora job update</code> and <code>aurora job cancel-update</code>. Users are encouraged to take
-advantage of scheduler-driven updates (see <code>aurora update -h</code> for usage), which has been a
-stable feature for several releases.</li>
-<li>To support configuration of shell-based health checkers, the <code>HealthCheckConfig</code> schema has been
-restructured to more cleanly allow configuring varied types of health checkers. The following
-fields from <code>HealthCheckConfig</code> are now deprecated: <code>endpoint</code>, <code>expected_response</code>,
-<code>expected_response_code</code> in favor of setting them as part of an <code>HttpHealthChecker</code>.</li>
-<li>In the scheduler API, the field <code>JobUpdateSettings.maxWaitToInstanceRunningMs</code>
-(<code>UpdateConfig.restart_threshold</code> in client-side configuration) is now deprecated.
-This setting was brittle in practice, and is ignored by the 0.11.0 scheduler.</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.11.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The
-community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 13 contributors who made Apache Aurora 0.11.0 possible:</p>
-
-<ul>
-<li>Bill Farner</li>
-<li>Chris Bannister</li>
-<li>Dmitriy Shirchenko</li>
-<li>George Sirois</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Kevin Sweeney</li>
-<li>Maxim Khutornenko</li>
-<li>Paul Cavallaro</li>
-<li>R.B. Boyer</li>
-<li>Renan DelValle</li>
-<li>Tengfei Mu</li>
-<li>Zameer Manji</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-12-0-released/aurora-0-12-0-released20191213-22326-sw4i8y b/content/blog/aurora-0-12-0-released
similarity index 100%
rename from content/blog/aurora-0-12-0-released/aurora-0-12-0-released20191213-22326-sw4i8y
rename to content/blog/aurora-0-12-0-released
diff --git a/content/blog/aurora-0-12-0-released/index.html b/content/blog/aurora-0-12-0-released/index.html
deleted file mode 100644
index a1db987..0000000
--- a/content/blog/aurora-0-12-0-released/index.html
+++ /dev/null
@@ -1,197 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Bill Farner</strong></p>
- <p><a href="http://twitter.com/wfarner">@wfarner</a></p>
- </span>
- </span>
- <p><em>Posted March 3, 2016</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.12.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.12.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Upgraded Mesos to 0.25.0.</li>
-<li>Upgraded the scheduler ZooKeeper client from 3.3.4 to 3.4.6.</li>
-<li>Added support for configuring Mesos role by passing <code>-mesos_role</code> to Aurora scheduler at start time.
-This enables resource reservation for Aurora when running in a shared Mesos cluster.</li>
-<li>Aurora task metadata is now mapped to Mesos task labels. Labels are prefixed with
-<code>org.apache.aurora.metadata.</code> to prevent clashes with other, external label sources.</li>
-<li>Added new scheduler flag <code>-default_docker_parameters</code> to allow a cluster operator to specify a
-universal set of parameters that should be used for every container that does not have parameters
-explicitly configured at the job level.</li>
-<li>Added support for jobs to specify arbitrary ZooKeeper paths for service registration. See
-<a href="https://github.com/apache/aurora/blob/master/docs/configuration-reference.md#announcer-objects">here</a>
-for details.</li>
-<li>Log destination is configurable for the thermos runner. See the configuration reference for details
-on how to configure destination per-process. Command line options may also be passed through the
-scheduler in order to configure the global default behavior.</li>
-<li>Env variables can be passed through to task processes by passing <code>--preserve_env</code>
-to thermos.</li>
-<li>Changed scheduler logging to use logback.
-Operators wishing to customize logging may do so with standard logback configuration as described
-<a href="http://logback.qos.ch/manual/configuration.html">here</a></li>
-<li>When using <code>--read-json</code>, <code>aurora</code> can now load multiple jobs from one json file,
-similar to the usual pystachio structure: <code>{"jobs": [job1, job2, ...]}</code>. The
-older single-job json format is also still supported.</li>
-<li><code>aurora config list</code> command now supports <code>--read-json</code></li>
-<li>Added scheduler command line argument <code>-shiro_after_auth_filter</code>. Optionally specify a class
-implementing javax.servlet.Filter that will be included in the Filter chain following the Shiro
-auth filters.</li>
-<li>The <code>addInstances</code> thrift RPC does now increase job instance count (scale out) based on the
-task template pointed by instance <code>key</code>.</li>
-</ul>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>Deprecated <code>AddInstancesConfig</code> argument in <code>addInstances</code> thrift RPC.</li>
-<li>Deprecated <code>TaskQuery</code> argument in <code>killTasks</code> thrift RPC to disallow killing tasks across
-multiple roles. The new safer approach is using <code>JobKey</code> with <code>instances</code> instead.</li>
-<li>Removed the deprecated field ‘ConfigGroup.instanceIds’ from the API.</li>
-<li>Removed the following deprecated <code>HealthCheckConfig</code> client-side configuration fields: <code>endpoint</code>,
-<code>expected_response</code>, <code>expected_response_code</code>. These are now set exclusively in like-named fields
-of <code>HttpHealthChecker.</code></li>
-<li>Removed the deprecated 'JobUpdateSettings.maxWaitToInstanceRunningMs’ thrift api field (
-UpdateConfig.restart_threshold in client-side configuration). This aspect of job restarts is now
-controlled exclusively via the client with <code>aurora job restart --restart-threshold=[seconds]</code>.</li>
-<li>Deprecated executor flag <code>--announcer-enable</code>. Enabling the announcer previously required both flags
-<code>--announcer-enable</code> and <code>--announcer-ensemble</code>, but now only <code>--announcer-ensemble</code> must be set.
-<code>--announcer-enable</code> is a no-op flag now and will be removed in future version.</li>
-<li>Removed scheduler command line arguments:
-
-<ul>
-<li><code>-enable_cors_support</code>. Enabling CORS is now implicit by setting the argument
-<code>-enable_cors_for</code>.</li>
-<li><code>-deduplicate_snapshots</code> and <code>-deflate_snapshots</code>. These features are good to always enable.</li>
-<li><code>-enable_job_updates</code> and <code>-enable_job_creation</code></li>
-<li><code>-extra_modules</code></li>
-<li><code>-logtostderr</code>, <code>-alsologtostderr</code>, <code>-vlog</code>, <code>-vmodule</code>, and <code>-use_glog_formatter</code>. Removed
-in favor of the new logback configuration.</li>
-</ul></li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.12.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The
-community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 17 contributors who made Apache Aurora 0.12.0 possible:</p>
-
-<ul>
-<li>Amol Deshmukh</li>
-<li>Anant Vyas</li>
-<li>Benjamin Staffin</li>
-<li>Bill Farner</li>
-<li>Dmitriy Shirchenko</li>
-<li>George Sirois</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Kasisnu Singh</li>
-<li>Kunal Thakar</li>
-<li>Martin Hrabovcin</li>
-<li>Mauricio Garavaglia</li>
-<li>Maxim Khutornenko</li>
-<li>Stephan Erb</li>
-<li>Tony Dong</li>
-<li>Zameer Manji</li>
-<li>Zhitao Li</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-13-0-released/index.html b/content/blog/aurora-0-13-0-released
similarity index 100%
rename from content/blog/aurora-0-13-0-released/index.html
rename to content/blog/aurora-0-13-0-released
diff --git a/content/blog/aurora-0-13-0-released/aurora-0-13-0-released20191213-22326-168trse b/content/blog/aurora-0-13-0-released/aurora-0-13-0-released20191213-22326-168trse
deleted file mode 100644
index 4c13089..0000000
--- a/content/blog/aurora-0-13-0-released/aurora-0-13-0-released20191213-22326-168trse
+++ /dev/null
@@ -1,212 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Jake Farrell</strong></p>
- <p><a href="http://twitter.com/eatfresh">@eatfresh</a></p>
- </span>
- </span>
- <p><em>Posted April 14, 2016</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.13.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.13.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Upgraded Mesos to 0.26.0</li>
-<li>Added a new health endpoint (/leaderhealth) which can be used for load balancer health
-checks to always forward requests to the leading scheduler.</li>
-<li>Added a new <code>aurora job add</code> client command to scale out an existing job.</li>
-<li>Upgraded the scheduler ZooKeeper client from 3.4.6 to 3.4.8.</li>
-<li>Added support for dedicated constraints not exclusive to a particular role.
-See <a href="/documentation/0.13.0/features/constraints#dedicated-attribute">here</a> for more details.</li>
-<li>Added a new argument <code>--announcer-hostname</code> to thermos executor to override hostname in service
-registry endpoint. See <a href="/documentation/0.13.0/reference/configuration#announcer-objects">here</a> for details.</li>
-<li>Descheduling a cron job that was not actually scheduled will no longer return an error.</li>
-<li>Added a new argument <code>-thermos_home_in_sandbox</code> to the scheduler for optionally changing
-HOME to the sandbox during thermos executor/runner execution. This is useful in cases
-where the root filesystem inside of the container is read-only, as it moves PEX extraction into
-the sandbox. See <a href="/documentation/0.13.0/operations/configuration#docker-containers">here</a>
-for more detail.</li>
-<li>Support for ZooKeeper authentication in the executor announcer. See
-<a href="/documentation/0.13.0/operations/security#announcer-authentication">here</a> for details.</li>
-<li>Scheduler H2 in-memory database is now using
-<a href="http://www.h2database.com/html/mvstore.html">MVStore</a>
-In addition, scheduler thrift snapshots are now supporting full DB dumps for faster restarts.</li>
-<li>Added scheduler argument <code>-require_docker_use_executor</code> that indicates whether the scheduler
-should accept tasks that use the Docker containerizer without an executor (experimental).</li>
-<li>Jobs referencing invalid tier name will be rejected by the scheduler.</li>
-<li>Added a new scheduler argument <code>--populate_discovery_info</code>. If set to true, Aurora will start
-to populate DiscoveryInfo field on TaskInfo of Mesos. This could be used for alternative
-service discovery solution like Mesos-DNS.</li>
-<li>Added support for automatic schema upgrades and downgrades when restoring a snapshot that contains
-a DB dump.</li>
-</ul>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>Removed deprecated (now redundant) fields:
-
-<ul>
-<li><code>Identity.role</code></li>
-<li><code>TaskConfig.environment</code></li>
-<li><code>TaskConfig.jobName</code></li>
-<li><code>TaskQuery.owner</code></li>
-</ul></li>
-<li>Removed deprecated <code>AddInstancesConfig</code> parameter to <code>addInstances</code> RPC.</li>
-<li>Removed deprecated executor argument <code>-announcer-enable</code>, which was a no-op in 0.12.0.</li>
-<li>Removed deprecated API constructs related to Locks:
-
-<ul>
-<li>removed RPCs that managed locks
-
-<ul>
-<li><code>acquireLock</code></li>
-<li><code>releaseLock</code></li>
-<li><code>getLocks</code></li>
-</ul></li>
-<li>removed <code>Lock</code> parameters to RPCs
-
-<ul>
-<li><code>createJob</code></li>
-<li><code>scheduleCronJob</code></li>
-<li><code>descheduleCronJob</code></li>
-<li><code>restartShards</code></li>
-<li><code>killTasks</code></li>
-<li><code>addInstances</code></li>
-<li><code>replaceCronTemplate</code></li>
-</ul></li>
-</ul></li>
-<li>Task ID strings are no longer prefixed by a timestamp.</li>
-<li>Changes to the way the scheduler reads command line arguments
-
-<ul>
-<li>Removed support for reading command line argument values from files.</li>
-<li>Removed support for specifying command line argument names with fully-qualified class names.</li>
-</ul></li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git;a=blob;f=CHANGELOG;h=7afa22f58052be26d37f85df4c8406c0bf79a57e;hb=refs/heads/master">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The
-community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 18 contributors who made Apache Aurora 0.13.0 possible:</p>
-
-<ul>
-<li>Amol Deshmukh</li>
-<li>Ashwin Murthy</li>
-<li>Benjamin Staffin</li>
-<li>Bill Farner</li>
-<li>Dmitriy Shirchenko</li>
-<li>Florian Pfeiffer</li>
-<li>George Sirois</li>
-<li>Jake Farrell</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Krish</li>
-<li>Kunal Thakar</li>
-<li>Maxim Khutornenko</li>
-<li>Se Choi</li>
-<li>Stephan Erb</li>
-<li>Tony Dong</li>
-<li>Zameer Manji</li>
-<li>Zhitao Li</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-14-0-released/aurora-0-14-0-released20191213-22326-q9lipk b/content/blog/aurora-0-14-0-released
similarity index 100%
rename from content/blog/aurora-0-14-0-released/aurora-0-14-0-released20191213-22326-q9lipk
rename to content/blog/aurora-0-14-0-released
diff --git a/content/blog/aurora-0-14-0-released/index.html b/content/blog/aurora-0-14-0-released/index.html
deleted file mode 100644
index 4079bfe..0000000
--- a/content/blog/aurora-0-14-0-released/index.html
+++ /dev/null
@@ -1,185 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Stephan Erb</strong></p>
- <p><a href="http://twitter.com/ErbStephan">@ErbStephan</a></p>
- </span>
- </span>
- <p><em>Posted June 14, 2016</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.14.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.14.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Upgraded Mesos to 0.27.2</li>
-<li>Added a new optional <a href="https://curator.apache.org/">Apache Curator</a> backend for performing
-scheduler leader election. You can enable this with the new <code>-zk_use_curator</code> scheduler argument.</li>
-<li>Adding –nosetuid-health-checks flag to control whether the executor runs health checks as the
-job’s role’s user.</li>
-<li>New scheduler command line argument <code>-offer_filter_duration</code> to control the time after which we
-expect Mesos to re-offer unused resources. A short duration improves scheduling performance in
-smaller clusters, but might lead to resource starvation for other frameworks if you run multiple
-ones in your cluster. Uses the Mesos default of 5s.</li>
-<li>New scheduler command line option <code>-framework_name</code> to change the name used for registering
-the Aurora framework with Mesos. The current default value is ‘TwitterScheduler’.</li>
-<li>Added experimental support for launching tasks using filesystem images and the Mesos <a href="https://github.com/apache/mesos/blob/master/docs/container-image.md">unified
-containerizer</a>. See that
-linked documentation for details on configuring Mesos to use the unified containerizer. Note that
-earlier versions of Mesos do not fully support the unified containerizer. Mesos 0.28.x or later is
-recommended for anyone adopting task images via the Mesos containerizer.</li>
-<li>Upgraded to pystachio 0.8.1 to pick up support for the new <a href="https://github.com/wickman/pystachio/blob/v0.8.1/README.md#choices">Choice type</a>.</li>
-<li>The <code>container</code> property of a <code>Job</code> is now a Choice of either a <code>Container</code> holder, or a direct
-reference to either a <code>Docker</code> or <code>Mesos</code> container.</li>
-<li>New scheduler command line argument <code>-ip</code> to control what ip address to bind the schedulers http
-server to.</li>
-<li>Added experimental support for Mesos GPU resource. This feature will be available in Mesos 1.0
-and is disabled by default. Use <code>-allow_gpu_resource</code> flag to enable it. Once this feature is
-enabled, creating jobs with GPU resource will make scheduler snapshot backwards incompatible.
-For further further details, please see the full release notes.</li>
-<li>Experimental support for a webhook feature which POSTs all task state changes to a user defined
-endpoint.</li>
-<li>Added support for specifying the default tier name in tier configuration file (<code>tiers.json</code>). The
-<code>default</code> property is required and is initialized with the <code>preemptible</code> tier (<code>preemptible</code> tier
-tasks can be preempted but their resources cannot be revoked).</li>
-</ul>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>Deprecated <code>--restart-threshold</code> option in the <code>aurora job restart</code> command to match the job
-updater behavior. This option has no effect now and will be removed in the future release.</li>
-<li>Deprecated <code>-framework_name</code> default argument 'TwitterScheduler’. In a future release this
-will change to 'aurora’. Please be aware that depending on your usage of Mesos, this will
-be a backward incompatible change. For details, see MESOS-703.</li>
-<li>The <code>-thermos_observer_root</code> command line arg has been removed from the scheduler. This was a
-relic from the time when executor checkpoints were written globally, rather than into a task’s
-sandbox.</li>
-<li>Setting the <code>container</code> property of a <code>Job</code> to a <code>Container</code> holder is deprecated in favor of
-setting it directly to the appropriate (i.e. <code>Docker</code> or <code>Mesos</code>) container type.</li>
-<li>Deprecated <code>numCpus</code>, <code>ramMb</code> and <code>diskMb</code> fields in <code>TaskConfig</code> and <code>ResourceAggregate</code> thrift
-structs. Use <code>set<Resource> resources</code> to specify task resources or quota values.</li>
-<li>The endpoint <code>/slaves</code> is deprecated. Please use <code>/agents</code> instead.</li>
-<li>Deprecated <code>production</code> field in <code>TaskConfig</code> thrift struct. Use <code>tier</code> field to specify task
-scheduling and resource handling behavior.</li>
-<li>The scheduler <code>resources_*_ram_gb</code> and <code>resources_*_disk_gb</code> metrics have been renamed to
-<code>resources_*_ram_mb</code> and <code>resources_*_disk_mb</code> respectively. Note the unit change: GB -> MB.</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.14.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The
-community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 11 contributors who made Apache Aurora 0.14.0 possible:</p>
-
-<ul>
-<li>Chris Bannister</li>
-<li>Dmitriy Shirchenko</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Maxim Khutornenko</li>
-<li>Mehrdad Nurolahzade</li>
-<li>Raymond Khalife</li>
-<li>Renan DelValle</li>
-<li>Stephan Erb</li>
-<li>Zameer Manji</li>
-<li>se choi</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-15-0-released/index.html b/content/blog/aurora-0-15-0-released
similarity index 100%
rename from content/blog/aurora-0-15-0-released/index.html
rename to content/blog/aurora-0-15-0-released
diff --git a/content/blog/aurora-0-15-0-released/aurora-0-15-0-released20191213-22326-14f0t8a b/content/blog/aurora-0-15-0-released/aurora-0-15-0-released20191213-22326-14f0t8a
deleted file mode 100644
index b674522..0000000
--- a/content/blog/aurora-0-15-0-released/aurora-0-15-0-released20191213-22326-14f0t8a
+++ /dev/null
@@ -1,136 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Maxim Khutornenko</strong></p>
- <p><a href="http://twitter.com/hutorrr">@hutorrr</a></p>
- </span>
- </span>
- <p><em>Posted July 6, 2016</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.15.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.15.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. The main scope of this release is to catch up
-with Mesos release cadence. As such, no major development or deprecation changes were accepted.
-Here are some highlights in this release:</p>
-
-<ul>
-<li>New scheduler commandline argument <code>-enable_mesos_fetcher</code> to allow job submissions
-to contain URIs which will be passed to the Mesos Fetcher and subsequently downloaded into
-the sandbox. Please note that enabling job submissions to download resources from arbitrary
-URIs may have security implications.</li>
-<li>Upgraded Mesos to 0.28.2.</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.15.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 8 contributors who made Apache Aurora 0.15.0 possible:</p>
-
-<ul>
-<li>Benjamin Staffin</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Martin Hrabovcin</li>
-<li>Maxim Khutornenko</li>
-<li>Mehrdad Nurolahzade</li>
-<li>Renan DelValle</li>
-<li>Stephan Erb</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-16-0-released/index.html b/content/blog/aurora-0-16-0-released
similarity index 100%
rename from content/blog/aurora-0-16-0-released/index.html
rename to content/blog/aurora-0-16-0-released
diff --git a/content/blog/aurora-0-16-0-released/aurora-0-16-0-released20191213-22326-189kqdn b/content/blog/aurora-0-16-0-released/aurora-0-16-0-released20191213-22326-189kqdn
deleted file mode 100644
index 18f200f..0000000
--- a/content/blog/aurora-0-16-0-released/aurora-0-16-0-released20191213-22326-189kqdn
+++ /dev/null
@@ -1,194 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Joshua Cohen</strong></p>
- <p><a href="http://twitter.com/heyjoshua">@heyjoshua</a></p>
- </span>
- </span>
- <p><em>Posted September 28, 2016</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.16.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.16.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Upgraded Mesos to 1.0.0. Note: as part of this upgrade we have switched from depending on
-the mesos.native egg for Thermos in favor of the stripped down mesos.executor egg. This means
-users launching Docker tasks with the Mesos DockerContainerizer are no longer required to use
-images that include all of Mesos’s dependencies.</li>
-<li>Scheduler command line behavior has been modified to warn users of the deprecation of <code>production</code>
-attribute in <code>Job</code> thrift struct. The scheduler is queried for tier configurations and the user’s
-choice of <code>tier</code> and <code>production</code> attributes is revised, if necessary. If <code>tier</code> is already set,
-the <code>production</code> attribute might be adjusted to match the <code>tier</code> selection. Otherwise, <code>tier</code> is
-selected based on the value of <code>production</code> attribute. If a matching tier is not found, the
-<code>default</code> tier from tier configuration file (<code>tiers.json</code>) is used.</li>
-<li>The <code>/offers</code> endpoint has been modified to display attributes of resource offers as received
-from Mesos. This has affected rendering of some of the existing attributes. Furthermore, it now
-dumps additional offer attributes including <a href="http://mesos.apache.org/documentation/latest/reservation/">reservations</a>
-and <a href="http://mesos.apache.org/documentation/latest/persistent-volume/">persistent volumes</a>.</li>
-<li>The scheduler API now accepts both thrift JSON and binary thrift. If a request is sent without a
-<code>Content-Type</code> header, or a <code>Content-Type</code> header of <code>application/x-thrift</code> or <code>application/json</code>
-or <code>application/vnd.apache.thrift.json</code> the request is treated as thrift JSON. If a request is
-sent with a <code>Content-Type</code> header of <code>application/vnd.apache.thrift.binary</code> the request is treated
-as binary thrift. If the <code>Accept</code> header of the request is <code>application/vnd.apache.thrift.binary</code>
-then the response will be binary thrift. Any other value for <code>Accept</code> will result in thrift JSON.</li>
-<li>Scheduler is now able to launch jobs using more than one executor at a time. To use this feature
-the <code>-custom_executor_config</code> flag must point to a JSON file which contains at least one valid
-executor configuration as detailed in the <a href="docs/features/custom-executors.md">configuration</a>
-documentation.</li>
-<li>Add rollback API to the scheduler and new client command to support rolling back
-active update jobs to their initial state.</li>
-<li><a name="zk_use_curator_upgrade"></a> The scheduler flag <code>-zk_use_curator</code> now defaults to <code>true</code>
-and care should be taken when upgrading from a configuration that does not pass the flag. The
-scheduler upgrade should be performed by bringing all schedulers down, and then bringing upgraded
-schedulers up. A rolling upgrade would result in no leading scheduler for the duration of the
-roll which could be confusing to monitor and debug.</li>
-<li>A new command <code>aurora_admin reconcile_tasks</code> is now available on the Aurora admin client that can trigger
-implicit and explicit task reconciliations.</li>
-<li>Add a new MTTS (Median Time To Starting) metric in addition to MTTA and MTTR.</li>
-<li>In addition to CPU resources, RAM resources can now be treated as revocable via the scheduler
-commandline flag <code>-enable_revocable_ram</code>.</li>
-<li>Introduce UpdateMetadata fields in JobUpdateRequest to allow clients to store metadata on update.</li>
-<li>Changed cronSchedule field inside of JobConfiguration schema to be optional for compatibility with Go.</li>
-<li>Update default value of command line option <code>-framework_name</code> to ‘Aurora’.</li>
-<li>Tasks launched with filesystem images and the Mesos unified containerizer are now fully isolated from
-the host’s filesystem. As such they are no longer required to include any of the executor’s
-dependencies (e.g. Python 2.7) within the task’s filesystem.</li>
-</ul>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>The job configuration flag <code>production</code> is now deprecated. To achieve the same scheduling behavior
-that <code>production=true</code> used to provide, users should elect a <code>tier</code> for the job with attributes
-<code>preemptible=false</code> and <code>revocable=false</code>. For example, the <code>preferred</code> tier in the default tier
-configuration file (<code>tiers.json</code>) matches the above criteria.</li>
-<li>The <code>ExecutorInfo.source</code> field is deprecated and has been replaced with a label named <code>source</code>.
-It will be removed from Mesos in a future release.</li>
-<li>The scheduler flag <code>-zk_use_curator</code> has been deprecated. If you have never set the flag and are
-upgrading you should take care as described in the <a href="#zk_use_curator_upgrade">note</a> above.</li>
-<li>The <code>key</code> argument of <code>getJobUpdateDetails</code> has been deprecated. Use the <code>query</code> argument instead.</li>
-<li>The –release-threshold option on <code>aurora job restart</code> has been removed.</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.16.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 16 contributors who made Apache Aurora 0.16.0 possible:</p>
-
-<ul>
-<li>David McLaughlin</li>
-<li>David Robinson</li>
-<li>Dmitriy Shirchenko</li>
-<li>Igor Morozov</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Kai Huang</li>
-<li>Karthik Anantha Padmanabhan</li>
-<li>Maxim Khutornenko</li>
-<li>Mehrdad Nurolahzade</li>
-<li>Renan DelValle</li>
-<li>Santhosh Kumar Shanmugham</li>
-<li>Stephan Erb</li>
-<li>Tarun Gogineni</li>
-<li>Zameer Manji</li>
-<li>Zhitao Li</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-17-0-released/index.html b/content/blog/aurora-0-17-0-released
similarity index 100%
rename from content/blog/aurora-0-17-0-released/index.html
rename to content/blog/aurora-0-17-0-released
diff --git a/content/blog/aurora-0-17-0-released/aurora-0-17-0-released20191213-22326-1keg4c7 b/content/blog/aurora-0-17-0-released/aurora-0-17-0-released20191213-22326-1keg4c7
deleted file mode 100644
index afa8ba1..0000000
--- a/content/blog/aurora-0-17-0-released/aurora-0-17-0-released20191213-22326-1keg4c7
+++ /dev/null
@@ -1,192 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Stephan Erb</strong></p>
- <p><a href="http://twitter.com/ErbStephan">@ErbStephan</a></p>
- </span>
- </span>
- <p><em>Posted February 6, 2017</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.17.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.17.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release.</p>
-
-<p>Major new features:</p>
-
-<ul>
-<li>Use the <code>RUNNING</code> state of a task to indicate it is healthy and behaving as expected.
-A service will remain in <code>STARTING</code> state until a configurable amount of consecutive health checks
-have passed. Job updates can therefore rely purely on health checks rather than <code>watch_secs</code>
-timeout when deciding an individial instance update state, by setting <code>watch_secs</code> to 0.</li>
-<li>The Aurora Scheduler API supports volume mounts per task for the Mesos
-Containerizer if the scheduler is running with the <code>-allow_container_volumes</code>
-flag.</li>
-<li>Resolve docker tags to concrete identifiers for DockerContainerizer, so that job configuration
-is immutable across restarts. The feature introduces a new <code>{{docker.image[name][tag]}}</code> binder that
-can be used in the Aurora job configuration to resolve a docker image specified by its <code>name:tag</code>
-to a concrete identifier specified by its <code>registry/name@digest</code>. It requires version 2 of the
-Docker Registry.</li>
-</ul>
-
-<p>Performance improvements:</p>
-
-<ul>
-<li>Scheduling performance has been improved by scheduling multiple tasks per scheduling round.</li>
-<li>Preemption slot search logic is modified to improve its performance.
-
-<ul>
-<li>Multiple reservations are made per task group per round.</li>
-<li>Multiple reservations are evaluated per round.</li>
-</ul></li>
-<li>The default logging output has been changed to remove line numbers and inner class information in
-exchange for faster logging.</li>
-<li>The Aurora client is now using the Thrift binary protocol to communicate with the scheduler.</li>
-<li>Added a new flag <code>--snapshot_hydrate_stores</code> that controls which H2-backed stores to write fully
-hydrated into the Scheduler snapshot. Can lead to significantly lower snapshot times for large
-clusters if you set this flag to an empty list. Old behavior is preserved by default, but see
-org.apache.aurora.scheduler.storage.log.SnapshotStoreImpl for which stores we currently have
-duplicate writes for.</li>
-<li>New scheduler metrics are added to facilitate monitoring and performance studies (AURORA-1832).</li>
-</ul>
-
-<p>Additional changes:</p>
-
-<ul>
-<li>Upgraded Mesos to 1.1.0.</li>
-<li>A task’s tier is now mapped to a label on the Mesos <code>TaskInfo</code> proto.</li>
-<li>Introduce a new <code>--ip</code> option to bind the Thermos observer to a specific rather than all
-interfaces.</li>
-<li>Fix error that prevents the scheduler from being launched with <code>-enable_revocable_ram</code>.</li>
-<li>The executor will send SIGTERM to processes that self daemonize via double forking.</li>
-<li>Support the deployment of the Aurora scheduler behind HTTPS-enabled reverse proxies: By launching
-scheduler via <code>-serverset_endpoint_name=https</code> you can ensure the Aurora client will correctly
-discover HTTPS support via the ZooKeeper-based discovery mechanism.</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.17.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 22 contributors who made Apache Aurora 0.17.0 possible:</p>
-
-<ul>
-<li>Andrew Jorgensen</li>
-<li>Bing-Qian Luan</li>
-<li>David McLaughlin</li>
-<li>Dmitriy Shirchenko</li>
-<li>Jake Smullin</li>
-<li>Jing Chen</li>
-<li>John Sirois</li>
-<li>Joshua Cohen</li>
-<li>Justin Pinkul</li>
-<li>Kai Huang</li>
-<li>Maxim Khutornenko</li>
-<li>Mehrdad Nurolahzade</li>
-<li>Nicolás Donatucci</li>
-<li>Pierre Cheynier</li>
-<li>Pradyumna Kaushik</li>
-<li>Renan DelValle</li>
-<li>Reza Motamedi</li>
-<li>Rogier Dikkes</li>
-<li>Santhosh Kumar Shanmugham</li>
-<li>Stephan Erb</li>
-<li>Steve Niemitz</li>
-<li>Zameer Manji</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-18-0-released/index.html b/content/blog/aurora-0-18-0-released
similarity index 100%
rename from content/blog/aurora-0-18-0-released/index.html
rename to content/blog/aurora-0-18-0-released
diff --git a/content/blog/aurora-0-18-0-released/aurora-0-18-0-released20191213-22326-8qqrbc b/content/blog/aurora-0-18-0-released/aurora-0-18-0-released20191213-22326-8qqrbc
deleted file mode 100644
index d977e3a..0000000
--- a/content/blog/aurora-0-18-0-released/aurora-0-18-0-released20191213-22326-8qqrbc
+++ /dev/null
@@ -1,181 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Santhosh Kumar Shanmugham</strong></p>
- <p><a href="http://twitter.com/santhk">@santhk</a></p>
- </span>
- </span>
- <p><em>Posted June 20, 2017</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.18.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.18.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release.</p>
-
-<p>Major new features:</p>
-
-<ul>
-<li>Added the <code>-mesos_driver</code> flag to the scheduler with three possible options:
-<code>SCHEDULER_DRIVER</code>, <code>V0_MESOS</code>, <code>V1_MESOS</code>. The first uses the original driver
-and the latter two use two new drivers from <code>libmesos</code>. <code>V0_MESOS</code> uses the
-<code>SCHEDULER_DRIVER</code> under the hood and <code>V1_MESOS</code> uses a new HTTP API aware
-driver. Users that want to use the HTTP API should use <code>V1_MESOS</code>.
-Performance sensitive users should stick with the <code>SCHEDULER_DRIVER</code> or
-<code>V0_MESOS</code> drivers.</li>
-<li>Add observer command line options to control the resource collection interval
-for observed tasks. See <a href="docs/reference/observer-configuration.md">here</a> for details.</li>
-<li>Added support for reserving agents during job updates, which can substantially reduce update times
-in clusters with high contention for resources. Disabled by default, but can be enabled with
-<code>enable_update_affinity</code> option, and the reservation timeout can be controlled via
-<code>update_affinity_reservation_hold_time</code>.</li>
-<li>Add <code>task scp</code> command to the CLI client for easy transferring of files to/from/between task
-instances. See <a href="docs/reference/client-commands.md#scping-with-task-machines">here</a> for details.
-Currently only fully supported for Mesos containers (you can copy files from the Docker container
-sandbox but you cannot send files to it).</li>
-<li>Added ability to inject your own scheduling logic, via a lazy Guice module binding. This is an
-alpha-level feature and not subject to backwards compatibility considerations. You can specify
-your custom modules using the <code>task_assigner_modules</code> and <code>preemption_slot_finder_modules</code> options.</li>
-<li>Added support for resource bin-packing via the <code>-offer_order</code> option. You can choose from <code>CPU</code>,
-<code>MEMORY</code>, <code>DISK</code>, <code>RANDOM</code> or <code>REVOCABLE_CPU</code>. You can also compose secondary sorts by combining
-orders together: e.g. to bin-pack by CPU and MEMORY you could supply <code>CPU,MEMORY</code>. The current
-default is <code>RANDOM</code>, which has the strong advantage that users can (usually) relocate their tasks
-due to noisy neighbors or machine issues with a task restart. When you have deterministic
-bin-packing, they may always end up on the same agent. So be careful enabling this without proper
-monitoring and remediation of host failures.</li>
-<li>Modified job update behavior to create new instances, then update existing instances, and then
-kill unwanted instances. Previously, a job update would modify each instance in the order of
-their instance ID.</li>
-<li>Added ability to whitelist TaskStateChanges in the webhook configuration file. You can specify
-a list of desired TaskStateChanges(represented by their task statuses) to be sent to a configured
-endpoint.</li>
-<li>Add message parameter to <code>killTasks</code> RPC.</li>
-<li>Add <code>prune_tasks</code> endpoint to <code>aurora_admin</code>. See <code>aurora_admin prune_tasks -h</code> for usage information.</li>
-<li>Add support for per-task volume mounts for Mesos containers to the Aurora config DSL.</li>
-</ul>
-
-<p>Additional changes:</p>
-
-<ul>
-<li>Update to Mesos 1.2.0. Please upgrade Aurora to 0.18 before upgrading Mesos to 1.2.0 if you rely
-on Mesos filesystem images.</li>
-</ul>
-
-<p><strong>NOTE: In this release, the Aurora client will need to be updated before the scheduler
-can be deployed.</strong></p>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.18.0">CHANGELOG</a>.</p>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues,
-please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 12 contributors who made Apache Aurora 0.18.0 possible:</p>
-
-<ul>
-<li>Abhishek Jain</li>
-<li>Charles Raimbert</li>
-<li>Cody Gibb</li>
-<li>David McLaughlin</li>
-<li>Kai Huang</li>
-<li>Mehrdad Nurolahzade</li>
-<li>Nicolás Donatucci</li>
-<li>Reza Motamedi</li>
-<li>Santhosh Kumar Shanmugham</li>
-<li>Stephan Erb</li>
-<li>Takuya Kuwahara</li>
-<li>Zameer Manji</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-18-1-released/index.html b/content/blog/aurora-0-18-1-released
similarity index 100%
rename from content/blog/aurora-0-18-1-released/index.html
rename to content/blog/aurora-0-18-1-released
diff --git a/content/blog/aurora-0-18-1-released/aurora-0-18-1-released20191213-22326-p7jfh1 b/content/blog/aurora-0-18-1-released/aurora-0-18-1-released20191213-22326-p7jfh1
deleted file mode 100644
index 5e6dac7..0000000
--- a/content/blog/aurora-0-18-1-released/aurora-0-18-1-released20191213-22326-p7jfh1
+++ /dev/null
@@ -1,106 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Bill Farner</strong></p>
- </span>
- </span>
- <p><em>Posted November 1, 2017</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.18.1 Released</h1>
-
- <p>The latest Apache Aurora release, 0.18.1, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. This is a patch release to
-update the Shiro library to version 1.2.5.</p>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.18.1">CHANGELOG</a>.</p>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-19-0-released/index.html b/content/blog/aurora-0-19-0-released
similarity index 100%
rename from content/blog/aurora-0-19-0-released/index.html
rename to content/blog/aurora-0-19-0-released
diff --git a/content/blog/aurora-0-19-0-released/aurora-0-19-0-released20191213-22326-oooa38 b/content/blog/aurora-0-19-0-released/aurora-0-19-0-released20191213-22326-oooa38
deleted file mode 100644
index ac525d5..0000000
--- a/content/blog/aurora-0-19-0-released/aurora-0-19-0-released20191213-22326-oooa38
+++ /dev/null
@@ -1,176 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Bill Farner</strong></p>
- </span>
- </span>
- <p><em>Posted November 10, 2017</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.19.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.19.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Added the ability to configure the executor’s stop timeout, which is the maximum amount of time
-the executor will wait during a graceful shutdown sequence before continuing the ‘Forceful
-Termination’ process (see
-<a href="http://aurora.apache.org/documentation/latest/reference/task-lifecycle/">here</a> for details).</li>
-<li>Added the ability to configure the wait period after calling the graceful shutdown endpoint and
-the shutdown endpoint using the <code>graceful_shutdown_wait_secs</code> and <code>shutdown_wait_secs</code> fields in
-<code>HttpLifecycleConfig</code> respectively. Previously, the executor would only wait 5 seconds between
-steps (adding up to a total of 10 seconds as there are 2 steps). The overall waiting period is
-bounded by the executor’s stop timeout, which can be configured using the executor’s
-<code>stop_timeout_in_secs</code> flag.</li>
-<li>Added the <code>thrift_method_interceptor_modules</code> scheduler flag that lets cluster operators inject
-custom Thrift method interceptors.</li>
-<li>Increase default ZooKeeper session timeout from 4 to 15 seconds.</li>
-<li>Added option <code>-zk_connection_timeout</code> to control the connection timeout of ZooKeeper connections.</li>
-<li>Added scheduler command line argument <code>-hold_offers_forever</code>, suitable for use in clusters where
-Aurora is the only framework. This setting disables other options such as <code>-min_offer_hold_time</code>,
-and allows the scheduler to more efficiently cache scheduling attempts.</li>
-<li>The scheduler no longer uses an internal H2 database for storage.</li>
-<li>There is a new Scheduler UI which, in addition to the facelift, provides the ability to inject your
-own custom UI components.</li>
-</ul>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>Removed the deprecated command line argument <code>-zk_use_curator</code>, removing the choice to use the
-legacy ZooKeeper client.</li>
-<li>Removed the <code>rewriteConfigs</code> thrift API call in the scheduler. This was a last-ditch mechanism
-to modify scheduler state on the fly. It was considered extremely risky to use since its
-inception, and is safer to abandon due to its lack of use and likelihood for code rot.</li>
-<li>Removed the Job environment validation from the command line client. Validation was moved to the
-the scheduler side through the <code>allowed_job_environments</code> option. By default allowing any of
-<code>devel</code>, <code>test</code>, <code>production</code>, and any value matching the regular expression <code>staging[0-9]*</code>.</li>
-<li>Removed scheduler command line arguments related to the internal H2 database, which is no longer
-used:
-
-<ul>
-<li><code>-use_beta_db_task_store</code></li>
-<li><code>-enable_db_metrics</code></li>
-<li><code>-slow_query_log_threshold</code></li>
-<li><code>-db_row_gc_interval</code></li>
-<li><code>-db_lock_timeout</code></li>
-<li><code>-db_max_active_connection_count</code></li>
-<li><code>-db_max_idle_connection_count</code></li>
-<li><code>-snapshot_hydrate_stores</code></li>
-<li><code>-enable_h2_console</code></li>
-</ul></li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.19.0">CHANGELOG</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 14 contributors who made Apache Aurora 0.19.0 possible:</p>
-
-<ul>
-<li>Bill Farner</li>
-<li>David McLaughlin</li>
-<li>Derek Slager</li>
-<li>Jordan Ly</li>
-<li>Kai Huang</li>
-<li>Keisuke Nishimoto</li>
-<li>Mauricio Garavaglia</li>
-<li>Renan DelValle</li>
-<li>Reza Motamedi</li>
-<li>Robert Allen</li>
-<li>Ruben D. Porras</li>
-<li>Santhosh Kumar Shanmugham</li>
-<li>Stephan Erb</li>
-<li>Zameer Manji</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-19-1-released/index.html b/content/blog/aurora-0-19-1-released
similarity index 100%
rename from content/blog/aurora-0-19-1-released/index.html
rename to content/blog/aurora-0-19-1-released
diff --git a/content/blog/aurora-0-19-1-released/aurora-0-19-1-released20191213-22326-12sow2g b/content/blog/aurora-0-19-1-released/aurora-0-19-1-released20191213-22326-12sow2g
deleted file mode 100644
index ef29298..0000000
--- a/content/blog/aurora-0-19-1-released/aurora-0-19-1-released20191213-22326-12sow2g
+++ /dev/null
@@ -1,105 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Renan DelValle</strong></p>
- </span>
- </span>
- <p><em>Posted February 11, 2018</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.19.1 Released</h1>
-
- <p>The latest Apache Aurora release, 0.19.1, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.19.1">CHANGELOG</a>.</p>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-20-0-released/index.html b/content/blog/aurora-0-20-0-released
similarity index 100%
rename from content/blog/aurora-0-20-0-released/index.html
rename to content/blog/aurora-0-20-0-released
diff --git a/content/blog/aurora-0-20-0-released/aurora-0-20-0-released20191213-22326-d1tttf b/content/blog/aurora-0-20-0-released/aurora-0-20-0-released20191213-22326-d1tttf
deleted file mode 100644
index 351e8fc..0000000
--- a/content/blog/aurora-0-20-0-released/aurora-0-20-0-released20191213-22326-d1tttf
+++ /dev/null
@@ -1,158 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Renan DelValle</strong></p>
- </span>
- </span>
- <p><em>Posted April 3, 2018</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.20.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.20.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Updated to Mesos 1.4.0.</li>
-<li>Added experimental support for the Mesos partition-aware APIs. The key idea is a new ScheduleStatus
-PARTITIONED that represents a task in an unknown state. Users of Aurora can have per-job policies
-of whether or not to reschedule and how long to wait for the partition to heal. Backwards
-compatibility with existing behavior (i.e. transition to LOST immediately on a partition) is
-maintained. The support is experimental due to bugs found in Mesos that would cause issues in
-a production cluster. For that reason, the functionality is behind a new flag <code>-partition_aware</code>
-that is disabled by default. When Mesos support is improved and the new behavior is vetted in
-production clusters, we’ll enable this by default.</li>
-<li>Added the ability to inject custom offer holding and scheduling logic via the <code>-offer_set_module</code>
-scheduler flag. To take advantage of this feature, you will need to implement the <code>OfferSet</code>
-interface.</li>
-<li>Added <code>executor_config</code> field to the Job object of the DSL which will populate
-<code>JobConfiguration.TaskConfig.ExecutorConfig</code>. This allows for using custom executors defined
-through the <code>--custom_executor_config</code> scheduler flag. See our
-<a href="https://aurora.apache.org/documentation/0.20.0/features/custom-executors/">custom-executors</a> documentation for more information.</li>
-<li>Added support in Thermos Observer for delegating disk usage monitoring to Mesos agent. The feature
-can be enabled via <code>--enable_mesos_disk_collector</code> flag, in which case Observer will use the
-agent’s containers HTTP API to query the amount of used bytes for each container. Note that disk
-isolation should be enabled in Mesos agent. This feature is not compatible with authentication
-enabled agents.</li>
-</ul>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>Removed the ability to recover from SQL-based backups and snapshots. An 0.20.0 scheduler
-will not be able to recover backups or replicated log data created prior to 0.19.0.</li>
-<li>Removed task level resource fields (<code>numCpus</code>, <code>ramMb</code>, <code>diskMb</code>, <code>requestedPorts</code>).</li>
-<li>Removed the <code>-offer_order_modules</code> scheduler flag related to custom injectable offer orderings,
-since this will now be subsumed under custom <code>OfferSet</code> implementations (see the comment above):</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.20.0">CHANGELOG</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 12 contributors who made Apache Aurora 0.20.0 possible:</p>
-
-<ul>
-<li>Jing Chen</li>
-<li>Franck Cuny</li>
-<li>Renan DelValle</li>
-<li>Nicolás Donatucci</li>
-<li>Stephan Erb</li>
-<li>Bill Farner</li>
-<li>Juan Manuel Fresia</li>
-<li>Jordan Ly</li>
-<li>David McLaughlin</li>
-<li>Reza Motamedi</li>
-<li>Ruben D. Porras</li>
-<li>John Sirois</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-21-0-released/aurora-0-21-0-released20191213-22326-jzol5l b/content/blog/aurora-0-21-0-released
similarity index 100%
rename from content/blog/aurora-0-21-0-released/aurora-0-21-0-released20191213-22326-jzol5l
rename to content/blog/aurora-0-21-0-released
diff --git a/content/blog/aurora-0-21-0-released/index.html b/content/blog/aurora-0-21-0-released/index.html
deleted file mode 100644
index 2d966e3..0000000
--- a/content/blog/aurora-0-21-0-released/index.html
+++ /dev/null
@@ -1,172 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Renan DelValle</strong></p>
- </span>
- </span>
- <p><em>Posted September 10, 2018</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.21.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.21.0, is now available for
-<a href="http://aurora.apache.org/downloads/">download</a>. Here are some highlights in this release:</p>
-
-<ul>
-<li>Updated to Mesos 1.5.0.</li>
-<li><p>Introduce ability for tasks to specify custom SLA requirements via the new <code>SlaPolicy</code> structs.
-There are 3 different SLA Policies that are currently supported - <code>CountSlaPolicy</code>,
-<code>PercentageSlaPolicy</code> and <code>CoordinatorSlaPolicy</code>. SLA policies based on count and percentage
-express the required number of <code>RUNNING</code> instances as either a count or percentage in addition to
-allowing the duration-window for which these requirements have to be satisfied. For applications
-that need more control over how SLA is determined, a custom SLA calculator can be configured a.k.a
-Coordinator. Any action that can affect SLA, will first check with the Coordinator before
-proceeding.</p>
-
-<p><strong>IMPORTANT: The storage changes required for this feature will make scheduler
-snapshot backwards incompatible. Scheduler will be unable to read snapshot if rolled back to
-previous version. If rollback is absolutely necessary, perform the following steps:</strong></p>
-
-<ol>
-<li>Stop all host maintenance requests via <code>aurora_admin host_activate</code>.</li>
-<li>Ensure a new snapshot is created by running <code>aurora_admin scheduler_snapshot <cluster></code></li>
-<li>Rollback to previous version</li>
-</ol></li>
-</ul>
-
-<p>Note: The <code>Coordinator</code> interface required for the <code>CoordinatorSlaPolicy</code> is experimental at
- this juncture and is bound to change in the future.
-- Introduced ability for updates to be ‘SLA-aware’, or only update instances if it is within SLA,
- using the new <code>sla_aware</code> field in <code>UpdateConfig</code>. See the bullet point above for an explanation
- of custom SLA requirements.</p>
-
-<p><strong>NOTE</strong>: SLA-aware updates will use the desired config’s SLA, not the existing config.</p>
-
-<p>Three additional scheduler options have been added to support this feature:</p>
-<pre class="highlight plaintext"><code>1. `max_update_action_batch_size (default: 300)`: the number of update actions to process in a
-batch.
-2. `sla_aware_kill_retry_min_delay (default: 1mins)`: the minimum amount of time to wait before
-retrying an SLA-aware kill (using a truncated binary backoff).
-3. `sla_aware_kill_retry_max_delay (default: 5mins)`: the maximum amount of time to wait before
-retrying an SLA-aware kill (using a truncated binary backoff).
-</code></pre>
-
-<p>Deprecations and removals:</p>
-
-<ul>
-<li>Deprecated the <code>aurora_admin host_drain</code> command used for maintenance. With this release the SLA
-computations are moved to the scheduler and it is no longer required for the client to compute
-SLAs and watch the drains. The scheduler persists any host maintenance request and performs
-SLA-aware drain of the tasks, before marking the host as <code>DRAINED</code>. So maintenance requests
-survive across scheduler fail-overs. Use the newly introduced <code>aurora_admin sla_host_drain</code>
-to skip the SLA computations on the admin client.</li>
-<li>Removed resource fields (<code>numCpus</code>, <code>ramMb</code>, <code>diskMb</code>) from ResourceAggregate.</li>
-</ul>
-
-<p>Full release notes are available in the release
-<a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.21.0">CHANGELOG</a>.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 9 contributors who made Apache Aurora 0.21.0 possible:</p>
-
-<ul>
-<li>Jing Chen</li>
-<li>Renan DelValle</li>
-<li>Stephan Erb</li>
-<li>Jordan Ly</li>
-<li>David McLaughlin</li>
-<li>John Sirois</li>
-<li>Sameer Parekh</li>
-<li>Reza Motamedi</li>
-<li>Ezequiel Torres Feyuk</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-6-0-incubating-released/index.html b/content/blog/aurora-0-6-0-incubating-released
similarity index 100%
rename from content/blog/aurora-0-6-0-incubating-released/index.html
rename to content/blog/aurora-0-6-0-incubating-released
diff --git a/content/blog/aurora-0-6-0-incubating-released/aurora-0-6-0-incubating-released20191213-22326-18841qy b/content/blog/aurora-0-6-0-incubating-released/aurora-0-6-0-incubating-released20191213-22326-18841qy
deleted file mode 100644
index 4d0bba3..0000000
--- a/content/blog/aurora-0-6-0-incubating-released/aurora-0-6-0-incubating-released20191213-22326-18841qy
+++ /dev/null
@@ -1,172 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Bill Farner</strong></p>
- <p><a href="http://twitter.com/wfarner">@wfarner</a></p>
- </span>
- </span>
- <p><em>Posted December 8, 2014</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.6.0-incubating Released</h1>
-
- <p>The latest Apache Aurora release, 0.6.0-incubating, is now available for download. This version marks the second Aurora release since becoming part of the <a href="http://incubator.apache.org">Apache Incubator</a>, and includes the following features and improvements:</p>
-
-<ul>
-<li>Introduced highly-available, scheduler-driven job updates in beta (<a href="https://issues.apache.org/jira/browse/AURORA-610">AURORA-610</a>)</li>
-<li>Improvements to the Aurora web UI, including visualization of job updates</li>
-<li>Added automatic service registration in ZooKeeper (<a href="https://issues.apache.org/jira/browse/AURORA-587">AURORA-587</a>)</li>
-<li>Updates to Aurora client version two, deprecation of v1 coming in future release</li>
-<li>Lots of new <a href="http://aurora.apache.org/documentation/0.6.0-incubating/">documentation</a>. Documentation now includes pages for <a href="http://aurora.apache.org/documentation/0.6.0-incubating/deploying-aurora-scheduler/">deploying the Aurora scheduler</a>, <a href="http://aurora.apache.org/documentation/0.6.0-incubating/cron-jobs/">cron jobs</a>, <a href="http://aurora.apache.org/documentation/0.6.0-incubating/sla/">SLA measurement</a>, <a href="http://aurora.apache.org/docu [...]
-</ul>
-
-<p>Full release notes are available in the release <a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.6.0-incubating">CHANGELOG</a>.</p>
-
-<h2 id="highly-available-scheduler-driven-updates">Highly-available, scheduler-driven updates</h2>
-
-<p>Rolling updates of services is a crucial feature in Aurora. As such, we
-want to take great care when changing its behavior. Previously, Aurora operated
-by delegating this functionality to the client (or any API client, for that
-matter). In this version, the scheduler can take over the
-responsibility of application update orchestration. Further details were discussed on the <a href="http://mail-archives.apache.org/mod_mbox/aurora-dev/201407.mbox/%3CCAGRA8uMxwVDokp_iHXhNru2gd-x_nM%2BDYAurpfAO6wuX7%3DnHFw%40mail.gmail.com%3E">Aurora mailing list</a>.</p>
-
-<h2 id="aurora-web-ui-improvements">Aurora Web UI Improvements</h2>
-
-<p>Since the scheduler can now orchestrate job updates, it has awareness of the progress and outcome of updates. This means you can see a progress bar for in-flight updates, and the history of updates for your jobs. Additionally, the performance of the UI was improved, especially for large roles and jobs <a href="https://issues.apache.org/jira/browse/AURORA-458">AURORA-458</a>.</p>
-
-<h2 id="service-announcement-and-management">Service Announcement and Management</h2>
-
-<p>Job configurations can now supply an <a href="http://aurora.apache.org/documentation/0.6.0-incubating/configuration-reference/#announcer-objects"><code>announce</code> parameter</a>, which is meant to be a way to opt-in for registration in a service discovery system. This has been implemented in the Aurora executor, and will automatically announce tasks via ZooKeeper.</p>
-
-<h2 id="aurora-client-improvements">Aurora Client Improvements</h2>
-
-<p>Progress was made in features to v2 of the <a href="http://aurora.apache.org/documentation/0.6.0-incubating/client-commands/">Aurora client</a>. We will support version 1 and version 2 for 0.6.0, with version 1 to be removed in 0.7.0.</p>
-
-<h2 id="improved-project-documentation">Improved Project Documentation</h2>
-
-<p>New documentation pages including:</p>
-
-<ul>
-<li><a href="http://aurora.apache.org/documentation/0.6.0-incubating/deploying-aurora-scheduler/">Deploying the Aurora scheduler</a></li>
-<li><a href="http://aurora.apache.org/documentation/0.6.0-incubating/cron-jobs/">Cron jobs</a></li>
-<li><a href="http://aurora.apache.org/documentation/0.6.0-incubating/sla/">SLA measurement</a></li>
-<li><a href="http://aurora.apache.org/documentation/0.6.0-incubating/storage/">Storage</a></li>
-<li><a href="http://aurora.apache.org/documentation/0.6.0-incubating/storage-config/">Storage configuration and measurement</a></li>
-<li><a href="http://aurora.apache.org/documentation/0.6.0-incubating/monitoring/">Monitoring</a></li>
-</ul>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://aurora.apache.org/community">user mailing list and IRC</a>. The community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 16 contributors who made 0.6.0-incubating possible:</p>
-
-<ul>
-<li>Bill Farner</li>
-<li>Maxim Khutornenko</li>
-<li>Kevin Sweeney</li>
-<li>Mark Chu-Carroll</li>
-<li>Joshua Cohen</li>
-<li>Zameer Manji</li>
-<li>David McLaughlin</li>
-<li>Brian Wickman</li>
-<li>Joe Smith</li>
-<li>Jake Farrell</li>
-<li>Matthew Jeffryes</li>
-<li>Dominic Hamon</li>
-<li>Bjoern Metzdorf</li>
-<li>Joseph Glanville</li>
-<li>David Robinson</li>
-<li>David Pan</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-7-0-incubating-released/index.html b/content/blog/aurora-0-7-0-incubating-released
similarity index 100%
rename from content/blog/aurora-0-7-0-incubating-released/index.html
rename to content/blog/aurora-0-7-0-incubating-released
diff --git a/content/blog/aurora-0-7-0-incubating-released/aurora-0-7-0-incubating-released20191213-22326-itj8tl b/content/blog/aurora-0-7-0-incubating-released/aurora-0-7-0-incubating-released20191213-22326-itj8tl
deleted file mode 100644
index b940765..0000000
--- a/content/blog/aurora-0-7-0-incubating-released/aurora-0-7-0-incubating-released20191213-22326-itj8tl
+++ /dev/null
@@ -1,155 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Maxim Khutornenko</strong></p>
- <p><a href="http://twitter.com/hutorrr">@hutorrr</a></p>
- </span>
- </span>
- <p><em>Posted February 12, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.7.0-incubating Released, Adding Support for Docker Containers</h1>
-
- <p>The latest Apache Aurora release, 0.7.0-incubating, is now <a href="http://aurora.apache.org/downloads/">available for download</a>. This version marks the third Aurora release since becoming part of the Apache Incubator, and includes the following features, improvements, and announcements:</p>
-
-<ul>
-<li>Beta support for running Docker containers</li>
-<li>Official support for the Aurora command-line client v2</li>
-<li>Performance improvements for running Aurora at scale</li>
-<li>Progress made toward Apache Incubator graduation</li>
-</ul>
-
-<p>Full release notes are available in the release <a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.7.0-incubating">CHANGELOG</a>.</p>
-
-<h2 id="docker-support-within-aurora">Docker support within Aurora</h2>
-
-<p>Docker has quickly become a popular technology for packaging and managing applications, making it simple to create a snapshot of your app and ship it to different machines in your datacenter. In the Aurora 0.7.0 release, we’ve added a container abstraction that supports Docker out of the box (and potentially future container technologies that may emerge), allowing you to specify a Docker image and schedule it to run within your Aurora cluster.</p>
-
-<p>This feature is marked as experimental in its first release, but we hope to see companies running it in production and helping improve it moving forward. Native Docker support within the Mesos core was added in the <a href="http://mesos.apache.org/blog/mesos-0-20-0-released/">Mesos 0.20.0 release</a>.</p>
-
-<h2 id="official-support-for-command-line-client-v2">Official support for command-line client v2</h2>
-
-<p>Over several releases, Aurora has included a new command-line client version two, rewritten from the ground-up to be simpler and easier to use. In the Aurora 0.7.0 release, we now provide official support for version two of the client, and have fully removed the original version. The previous client version was deprecated in the 0.6.0-incubating release.</p>
-
-<p>We’ve also made the client even-easier to use, by improving the help output that you receive. You can simply type <code>aurora -h</code> for a full list of available commands and helpful guidance. We’ve also documented <a href="http://aurora.apache.org/documentation/0.7.0-incubating/client-commands/">usage of the client commands</a> to provide helpful information about managing jobs.</p>
-
-<h2 id="performance-improvements">Performance Improvements</h2>
-
-<p>Performance is continually an area of focus and improvement for the Aurora team, with production Aurora clusters measuring tens of thousands of machines and tens-to-hundreds of thousands of tasks. Two specific improvements were made in this release that make signficant improvements on large clusters, including <a href="https://issues.apache.org/jira/browse/AURORA-121">AURORA-121</a> which made task pre-emption more efficient, and <a href="https://issues.apache.org/jira/browse/AURORA-9 [...]
-
-<h2 id="progress-toward-becoming-top-level-project">Progress toward becoming Top-Level Project</h2>
-
-<p>As the Apache Aurora project continues to grow in adopters and contributors, we’ve begun conversations regarding next-steps toward graduating from the Apache Incubator. A graduation resolution is expected to be presented to the Aurora community on the developer mailing list (<a href="mailto:dev@aurora.apache.org">dev@aurora.apache.org</a>, you can subscribe by emailing <a href="mailto:dev-subscribe@aurora.apache.org">dev-subscribe@aurora.apache.org</a>) in the coming weeks and voted o [...]
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://aurora.apache.org/community">user mailing list and IRC</a>. The community also holds weekly IRC meetings at 11AM Pacific every Monday that we encourage you to join. If you’re using Aurora, we’d love to hear from you on how to make it better.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 13 contributors who made 0.7.0-incubating possible:</p>
-
-<ul>
-<li>Bill Farner</li>
-<li>Brian Wickman</li>
-<li>Dave Lester</li>
-<li>David McLaughlin</li>
-<li>Florian Pfeiffer</li>
-<li>Issam EL ATIF</li>
-<li>Jake Farrell</li>
-<li>Jeffrey Schroeder</li>
-<li>Joshua Cohen</li>
-<li>Kevin Sweeney</li>
-<li>Maxim Khutornenko</li>
-<li>Steve Niemitz</li>
-<li>Zameer Manji</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-8-0-released/index.html b/content/blog/aurora-0-8-0-released
similarity index 100%
rename from content/blog/aurora-0-8-0-released/index.html
rename to content/blog/aurora-0-8-0-released
diff --git a/content/blog/aurora-0-8-0-released/aurora-0-8-0-released20191213-22326-135gtuq b/content/blog/aurora-0-8-0-released/aurora-0-8-0-released20191213-22326-135gtuq
deleted file mode 100644
index 76fd00b..0000000
--- a/content/blog/aurora-0-8-0-released/aurora-0-8-0-released20191213-22326-135gtuq
+++ /dev/null
@@ -1,171 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Jake Farrell</strong></p>
- <p><a href="http://twitter.com/eatfresh">@eatfresh</a></p>
- </span>
- </span>
- <p><em>Posted May 14, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.8.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.8.0, is now available for <a href="http://aurora.apache.org/downloads/">download</a>. This version marks the first Aurora release since becoming a top-level project at the Apache Software Foundation, and includes the following features, improvements, and announcements:</p>
-
-<ul>
-<li>Added support for external update coordination</li>
-<li>Security for scheduler operations, using Apache Shiro</li>
-<li>Scheduler performance improvements</li>
-<li>0.8.0 deprecations</li>
-</ul>
-
-<p>Full release notes are available in the release <a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.8.0">CHANGELOG</a>.</p>
-
-<h2 id="support-for-external-update-coordination">Support for external update coordination</h2>
-
-<p>With the introduction of scheduler-driven job update orchestration, Aurora now optionally supports an inverted dependency model where the updater can willingly pause job update progress upon reaching certain checkpoints and wait for the client/external service to explicitly “ack” on it. Further details are outlined in the <a href="http://aurora.apache.org/documentation/0.8.0/client-commands/#coordinated-job-updates">coordinated job updates</a> documentation.</p>
-
-<p>This feature may also be useful for building external update coordination services where Aurora service job upgrades are controlled by application specific health tracking systems, throttling individual job updates based on the internal health/traffic metrics.</p>
-
-<h2 id="security-for-scheduler-operations-using-apache-shiro">Security for scheduler operations, using Apache Shiro</h2>
-
-<p>Aurora now uses <a href="http://shiro.apache.org">Apache Shiro</a> to manage security for scheduler operations, including authenticated write access (HTTP Basic Auth or Kerberos), and fine-grained ACLs for scheduler RPCs.</p>
-
-<p>Further details are outlined in the <a href="http://aurora.apache.org/documentation/0.8.0/security/">security documentation</a>.</p>
-
-<h2 id="scheduler-performance-improvements">Scheduler performance improvements</h2>
-
-<p>Performance is continually an area of focus and improvement for the Aurora team, with production Aurora clusters measuring tens of thousands of machines and tens-to-hundreds of thousands of tasks. Two specific <a href="https://issues.apache.org/jira/browse/AURORA-999">scheduler performance improvements</a> were a focus of the 0.8.0 release, including <a href="https://issues.apache.org/jira/browse/AURORA-1219">improved preemption efficiency</a>, and creating a <a href="https://issues.a [...]
-
-<h2 id="0-8-0-deprecations">0.8.0 deprecations</h2>
-
-<p>The latest Aurora release includes the <a href="https://issues.apache.org/jira/browse/AURORA-905">several removals and deprecations</a>, including:</p>
-
-<ul>
-<li><a href="https://issues.apache.org/jira/browse/AURORA-975">AURORA-975</a>, Removing populatedDEPRECATED from PopulateJobResult</li>
-<li><a href="https://issues.apache.org/jira/browse/AURORA-1190">AURORA-1190</a>, Added a deprecation warning when the client-side updater is used; will be removed in 0.9.0</li>
-<li><a href="https://issues.apache.org/jira/browse/AURORA-1240">AURORA-1240</a>, Added a deprecation warning for restart_theshold setting</li>
-<li><a href="https://issues.apache.org/jira/browse/AURORA-1189">AURORA-1189</a>, Added a warning in the scheduler when the JVM version is < 1.8</li>
-<li>Removal of the custom security API in favor of integration with Apache Shiro</li>
-</ul>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 21 contributors who made Apache Aurora 0.8.0 possible:</p>
-
-<ul>
-<li>Ben Mahler</li>
-<li>Bhuvan Arumugam</li>
-<li>Bill Farner</li>
-<li>Brian Brazil</li>
-<li>Brian Wickman</li>
-<li>Dave Lester</li>
-<li>David Robinson</li>
-<li>Florian Pfeiffer</li>
-<li>Jake Farrell</li>
-<li>Joe Smith</li>
-<li>Joshua Cohen</li>
-<li>Kevin Sweeney</li>
-<li>Maxim Khutornenko</li>
-<li>Ricardo Cervera-Navarro</li>
-<li>Sanyogeeta Lawande</li>
-<li>Stephan Erb</li>
-<li>Steve Niemitz</li>
-<li>Thorhallur Sverrisson</li>
-<li>Tony Dong</li>
-<li>Zameer Manji</li>
-<li>Zeke Harris</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-0-9-0-released/aurora-0-9-0-released20191213-22326-12jw75q b/content/blog/aurora-0-9-0-released
similarity index 100%
rename from content/blog/aurora-0-9-0-released/aurora-0-9-0-released20191213-22326-12jw75q
rename to content/blog/aurora-0-9-0-released
diff --git a/content/blog/aurora-0-9-0-released/index.html b/content/blog/aurora-0-9-0-released/index.html
deleted file mode 100644
index 20cd5ef..0000000
--- a/content/blog/aurora-0-9-0-released/index.html
+++ /dev/null
@@ -1,153 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Jake Farrell</strong></p>
- <p><a href="http://twitter.com/eatfresh">@eatfresh</a></p>
- </span>
- </span>
- <p><em>Posted July 24, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>0.9.0 Released</h1>
-
- <p>The latest Apache Aurora release, 0.9.0, is now available for <a href="http://aurora.apache.org/downloads/">download</a>. This version includes many new features and improvements including:</p>
-
-<ul>
-<li>Now requires JRE 8 or greater.</li>
-<li>GC executor is fully replaced by the task state reconciliation (AURORA-1047).</li>
-<li>The scheduler command line argument ‘enable<em>legacy</em>constraints’ has been
-removed, and the scheduler no longer automatically injects 'host’ and 'rack’
-constraints for production services. (AURORA-1074)</li>
-<li>SLA metrics for non-production jobs have been disabled by default. They can
-be enabled via the scheduler command line. Metric names have changed from
-’…nonprod<em>ms’ to “…ms</em>nonprod” (AURORA-1350).</li>
-</ul>
-
-<p>Full release notes are available in the release <a href="https://gitbox.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=refs/tags/rel/0.9.0">CHANGELOG</a>.</p>
-
-<h2 id="0-9-0-deprecations">0.9.0 deprecations</h2>
-
-<p>The latest Aurora release includes the <a href="https://issues.apache.org/jira/browse/AURORA-1079">several removals and deprecations</a>, including:</p>
-
-<ul>
-<li>AURORA-1074 - Remove the “enable<em>legacy</em>constraints” flag.</li>
-<li>AURORA-1139 - Remove backwards compatibility shims from JobUpdateKey introduction</li>
-</ul>
-
-<h2 id="getting-involved">Getting Involved</h2>
-
-<p>We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the <a href="https://aurora.apache.org/community/">user mailing list and IRC</a>. The community also holds weekly IRC meetings at 11AM Pacific every Monday that you are welcome to join.</p>
-
-<h2 id="thanks">Thanks</h2>
-
-<p>Thanks to the 18 contributors who made Apache Aurora 0.9.0 possible:</p>
-
-<ul>
-<li>Bill Farner</li>
-<li>Jake Farrell</li>
-<li>Kevin Sweeney</li>
-<li>Joe Smith</li>
-<li>Andrew Jorgensen</li>
-<li>Steve Salevan</li>
-<li>Brian Wickman</li>
-<li>Brian Brazil</li>
-<li>Stephan Erb</li>
-<li>Zameer Manji</li>
-<li>Maxim Khutornenko</li>
-<li>David McLaughlin</li>
-<li>Michael Leinartas</li>
-<li>Benjamin Staffin</li>
-<li>Dave Lester</li>
-<li>Jeffrey Schroeder</li>
-<li>Will Swank</li>
-<li>Ben Mahler</li>
-</ul>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/blog/aurora-at-mesoscon-seattle/index.html b/content/blog/aurora-at-mesoscon-seattle
similarity index 100%
rename from content/blog/aurora-at-mesoscon-seattle/index.html
rename to content/blog/aurora-at-mesoscon-seattle
diff --git a/content/blog/aurora-at-mesoscon-seattle/aurora-at-mesoscon-seattle20191213-22326-y4rct3 b/content/blog/aurora-at-mesoscon-seattle/aurora-at-mesoscon-seattle20191213-22326-y4rct3
deleted file mode 100644
index cf7d39b..0000000
--- a/content/blog/aurora-at-mesoscon-seattle/aurora-at-mesoscon-seattle20191213-22326-y4rct3
+++ /dev/null
@@ -1,118 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="container-fluid">
-
-<div class="row">
-<div class="col-md-3 buffer">
- <div class="meta">
- <span class="author">
- <span class="author_contact">
- <p><strong>Dave Lester</strong></p>
- <p><a href="http://twitter.com/davelester">@davelester</a></p>
- </span>
- </span>
- <p><em>Posted August 26, 2015</em></p>
- </div>
-
- <div class="share">
- <span class="social-share-button"><a href="https://twitter.com/share" class="twitter-share-button" data-via="ApacheAurora">Tweet</a></span>
-
- <span><script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script></span>
-
- <script src="//platform.linkedin.com/in.js" type="text/javascript">
- lang: en_US
- </script>
- <script type="IN/Share" data-counter="right"></script>
- </div>
-</div>
-
-<div class="post col-md-9">
- <h1>Recap: Aurora at MesosCon Seattle</h1>
-
- <p>Last week was the second-ever #MesosCon in Seattle, WA and the Apache Aurora project was represented in several talks by committers and adopters. Check them out! We look forward to participating in future Mesos community events.</p>
-
-<p></p>
-
-<h2 id="mesoscon-presentations">MesosCon Presentations</h2>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/nNrh-gdu9m4" frameborder="0" allowfullscreen></iframe>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/ZHABassUOlo" frameborder="0" allowfullscreen></iframe>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/y1hi7K1lPkk" frameborder="0" allowfullscreen></iframe>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/ZQenXkoG_7o" frameborder="0" allowfullscreen></iframe>
-
-<h2 id="hackathon-winners-and-demos">Hackathon Winners and Demos</h2>
-
-<p>Congrats to the Paypal team, who won second place at the MesosCon hackathon for their <a href="https://github.com/mohitsoni/compose-executor">Docker Compose Executor</a>. The team <a href="https://www.youtube.com/watch?v=KES1Ud4MtDE&t=10m33s">demonstrated this project onstage</a>, running by Apache Aurora.</p>
-
-</div>
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/build-system/build-system20191213-22326-gy4wq1 b/content/documentation/0.10.0/build-system
similarity index 100%
rename from content/documentation/0.10.0/build-system/build-system20191213-22326-gy4wq1
rename to content/documentation/0.10.0/build-system
diff --git a/content/documentation/0.10.0/build-system/index.html b/content/documentation/0.10.0/build-system/index.html
deleted file mode 100644
index 365af8a..0000000
--- a/content/documentation/0.10.0/build-system/index.html
+++ /dev/null
@@ -1,250 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/build-system/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<p>The Python components of Aurora are built using <a href="https://pantsbuild.github.io">Pants</a>.</p>
-
-<h1 id="python-build-conventions">Python Build Conventions</h1>
-
-<p>The Python code is laid out according to the following conventions: </p>
-
-<ol>
-<li><p>1 <code>BUILD</code> per 3rd level directory. For a list of current top-level packages run:</p>
-<pre class="highlight plaintext"><code>% find src/main/python -maxdepth 3 -mindepth 3 -type d |\
-while read dname; do echo $dname |\
- sed 's@src/main/python/\(.*\)/\(.*\)/\(.*\).*@\1.\2.\3@'; done
-</code></pre></li>
-<li><p>Each <code>BUILD</code> file exports 1
-<a href="https://pantsbuild.github.io/build_dictionary.html#bdict_python_library"><code>python_library</code></a>
-that provides a
-<a href="https://pantsbuild.github.io/build_dictionary.html#setup_py"><code>setup_py</code></a>
-containing each
-<a href="https://pantsbuild.github.io/build_dictionary.html#python_binary"><code>python_binary</code></a>
-in the <code>BUILD</code> file, named the same as the directory it’s in so that it can be referenced
-without a ’:’ character. The <code>sources</code> field in the <code>python_library</code> will almost always be
-<code>rglobs('*.py')</code>.</p></li>
-<li><p>Other BUILD files may only depend on this single public <code>python_library</code>
-target. Any other target is considered a private implementation detail and
-should be prefixed with an <code>_</code>.</p></li>
-<li><p><code>python_binary</code> targets are always named the same as the exported console script.</p></li>
-<li><p><code>python_binary</code> targets must have identical <code>dependencies</code> to the <code>python_library</code> exported
-by the package and must use <code>entry_point</code>.</p>
-
-<p>The means a PEX file generated by pants will contain exactly the same files that will be
-available on the <code>PYTHONPATH</code> in the case of <code>pip install</code> of the corresponding library
-target. This will help our migration off of Pants in the future.</p></li>
-</ol>
-
-<h2 id="annotated-example-apache-thermos-runner">Annotated example - apache.thermos.runner</h2>
-<pre class="highlight plaintext"><code>% find src/main/python/apache/thermos/runner
-src/main/python/apache/thermos/runner
-src/main/python/apache/thermos/runner/__init__.py
-src/main/python/apache/thermos/runner/thermos_runner.py
-src/main/python/apache/thermos/runner/BUILD
-% cat src/main/python/apache/thermos/runner/BUILD
-# License boilerplate omitted
-import os
-
-
-# Private target so that a setup_py can exist without a circular dependency. Only targets within
-# this file should depend on this.
-python_library(
- name = '_runner',
- # The target covers every python file under this directory and subdirectories.
- sources = rglobs('*.py'),
- dependencies = [
- '3rdparty/python:twitter.common.app',
- '3rdparty/python:twitter.common.log',
- # Source dependencies are always referenced without a ':'.
- 'src/main/python/apache/thermos/common',
- 'src/main/python/apache/thermos/config',
- 'src/main/python/apache/thermos/core',
- ],
-)
-
-# Binary target for thermos_runner.pex. Nothing should depend on this - it's only used as an
-# argument to ./pants binary.
-python_binary(
- name = 'thermos_runner',
- # Use entry_point, not source so the files used here are the same ones tests see.
- entry_point = 'apache.thermos.bin.thermos_runner',
- dependencies = [
- # Notice that we depend only on the single private target from this BUILD file here.
- ':_runner',
- ],
-)
-
-# The public library that everyone importing the runner symbols uses.
-# The test targets and any other dependent source code should depend on this.
-python_library(
- name = 'runner',
- dependencies = [
- # Again, notice that we depend only on the single private target from this BUILD file here.
- ':_runner',
- ],
- # We always provide a setup_py. This will cause any dependee libraries to automatically
- # reference this library in their requirements.txt rather than copy the source files into their
- # sdist.
- provides = setup_py(
- # Conventionally named and versioned.
- name = 'apache.thermos.runner',
- version = open(os.path.join(get_buildroot(), '.auroraversion')).read().strip().upper(),
- ).with_binaries({
- # Every binary in this file should also be repeated here.
- # Always use the dict-form of .with_binaries so that commands with dashes in their names are
- # supported.
- # The console script name is always the same as the PEX with .pex stripped.
- 'thermos_runner': ':thermos_runner',
- }),
-)
-</code></pre>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/client-cluster-configuration/client-cluster-configuration20191213-22326-pf49ml b/content/documentation/0.10.0/client-cluster-configuration
similarity index 100%
rename from content/documentation/0.10.0/client-cluster-configuration/client-cluster-configuration20191213-22326-pf49ml
rename to content/documentation/0.10.0/client-cluster-configuration
diff --git a/content/documentation/0.10.0/client-cluster-configuration/index.html b/content/documentation/0.10.0/client-cluster-configuration/index.html
deleted file mode 100644
index d188463..0000000
--- a/content/documentation/0.10.0/client-cluster-configuration/index.html
+++ /dev/null
@@ -1,267 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/client-cluster-configuration/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="client-cluster-configuration">Client Cluster Configuration</h1>
-
-<p>A cluster configuration file is used by the Aurora client to describe the Aurora clusters with
-which it can communicate. Ultimately this allows client users to reference clusters with short names
-like us-east and eu. The following properties may be set:</p>
-
-<table><thead>
-<tr>
-<th style="text-align: left"><strong>Property</strong></th>
-<th style="text-align: left"><strong>Type</strong></th>
-<th style="text-align: left"><strong>Description</strong></th>
-</tr>
-</thead><tbody>
-<tr>
-<td style="text-align: left"><strong>name</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">Cluster name (Required)</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>slave_root</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">Path to mesos slave work dir (Required)</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>slave<em>run</em>directory</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">Name of mesos slave run dir (Required)</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>zk</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">Hostname of ZooKeeper instance used to resolve Aurora schedulers.</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>zk_port</strong></td>
-<td style="text-align: left">Integer</td>
-<td style="text-align: left">Port of ZooKeeper instance used to locate Aurora schedulers (Default: 2181)</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>scheduler<em>zk</em>path</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">ZooKeeper path under which scheduler instances are registered.</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>scheduler_uri</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">URI of Aurora scheduler instance.</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>proxy_url</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">Used by the client to format URLs for display.</td>
-</tr>
-<tr>
-<td style="text-align: left"><strong>auth_mechanism</strong></td>
-<td style="text-align: left">String</td>
-<td style="text-align: left">The authentication mechanism to use when communicating with the scheduler. (Default: UNAUTHENTICATED)</td>
-</tr>
-</tbody></table>
-
-<h4 id="name">name</h4>
-
-<p>The name of the Aurora cluster represented by this entry. This name will be the <code>cluster</code> portion of
-any job keys identifying jobs running within the cluster.</p>
-
-<h4 id="slave_root">slave_root</h4>
-
-<p>The path on the mesos slaves where executing tasks can be found. It is used in combination with the
-<code>slave_run_directory</code> property by <code>aurora task run</code> and <code>aurora task ssh</code> to change into the sandbox
-directory after connecting to the host. This value should match the value passed to <code>mesos-slave</code>
-as <code>-work_dir</code>.</p>
-
-<h4 id="slaverundirectory">slave<em>run</em>directory</h4>
-
-<p>The name of the directory where the task run can be found. This is used in combination with the
-<code>slave_root</code> property by <code>aurora task run</code> and <code>aurora task ssh</code> to change into the sandbox
-directory after connecting to the host. This should almost always be set to <code>latest</code>.</p>
-
-<h4 id="zk">zk</h4>
-
-<p>The hostname of the ZooKeeper instance used to resolve the Aurora scheduler. Aurora uses ZooKeeper
-to elect a leader. The client will connect to this ZooKeeper instance to determine the current
-leader. This host should match the host passed to the scheduler as <code>-zk_endpoints</code>.</p>
-
-<h4 id="zk_port">zk_port</h4>
-
-<p>The port on which the ZooKeeper instance is running. If not set this will default to the standard
-ZooKeeper port of 2181. This port should match the port in the host passed to the scheduler as
-<code>-zk_endpoints</code>.</p>
-
-<h4 id="schedulerzkpath">scheduler<em>zk</em>path</h4>
-
-<p>The path on the ZooKeeper instance under which the Aurora serverset is registered. This value should
-match the value passed to the scheduler as <code>-serverset_path</code>.</p>
-
-<h4 id="scheduler_uri">scheduler_uri</h4>
-
-<p>The URI of the scheduler. This would be used in place of the ZooKeeper related configuration above
-in circumstances where direct communication with a single scheduler is needed (e.g. testing
-environments). It is strongly advised to <strong>never</strong> use this property for production deploys.</p>
-
-<h4 id="proxy_url">proxy_url</h4>
-
-<p>Instead of using the hostname of the leading scheduler as the base url, if <code>proxy_url</code> is set, its
-value will be used instead. In that scenario the value for <code>proxy_url</code> would be, for example, the
-URL of your VIP in a loadbalancer or a roundrobin DNS name.</p>
-
-<h4 id="auth_mechanism">auth_mechanism</h4>
-
-<p>The identifier of an authentication mechanism that the client should use when communicating with the
-scheduler. Support for values other than <code>UNAUTHENTICATED</code> is currently not available, however work
-is <a href="https://issues.apache.org/jira/browse/AURORA-720">in progress</a> to add federated authentication
-to Aurora which will allow for more robust configuration of client/scheduler authentication.</p>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/client-commands/client-commands20191213-22326-dtt4z4 b/content/documentation/0.10.0/client-commands
similarity index 100%
rename from content/documentation/0.10.0/client-commands/client-commands20191213-22326-dtt4z4
rename to content/documentation/0.10.0/client-commands
diff --git a/content/documentation/0.10.0/client-commands/index.html b/content/documentation/0.10.0/client-commands/index.html
deleted file mode 100644
index 51272fe..0000000
--- a/content/documentation/0.10.0/client-commands/index.html
+++ /dev/null
@@ -1,566 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/client-commands/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="aurora-client-commands">Aurora Client Commands</h1>
-
-<ul>
-<li><a href="#introduction">Introduction</a></li>
-<li><a href="#cluster-configuration">Cluster Configuration</a></li>
-<li><a href="#job-keys">Job Keys</a></li>
-<li><a href="#modifying-aurora-client-commands">Modifying Aurora Client Commands</a></li>
-<li><a href="#regular-jobs">Regular Jobs</a>
-
-<ul>
-<li><a href="#creating-and-running-a-job">Creating and Running a Job</a></li>
-<li><a href="#running-a-command-on-a-running-job">Running a Command On a Running Job</a></li>
-<li><a href="#killing-a-job">Killing a Job</a></li>
-<li><a href="#updating-a-job">Updating a Job</a>
-
-<ul>
-<li><a href="#coordinated-job-updates">Coordinated job updates</a></li>
-<li><a href="#client-orchestrated-updates-deprecated">Client-orchestrated updates (deprecated)</a></li>
-</ul></li>
-<li><a href="#renaming-a-job">Renaming a Job</a></li>
-<li><a href="#restarting-jobs">Restarting Jobs</a></li>
-</ul></li>
-<li><a href="#cron-jobs">Cron Jobs</a></li>
-<li><a href="#comparing-jobs">Comparing Jobs</a></li>
-<li><a href="#viewingexamining-jobs">Viewing/Examining Jobs</a>
-
-<ul>
-<li><a href="#listing-jobs">Listing Jobs</a></li>
-<li><a href="#inspecting-a-job">Inspecting a Job</a></li>
-<li><a href="#versions">Versions</a></li>
-<li><a href="#checking-your-quota">Checking Your Quota</a></li>
-<li><a href="#finding-a-job-on-web-ui">Finding a Job on Web UI</a></li>
-<li><a href="#getting-job-status">Getting Job Status</a></li>
-<li><a href="#opening-the-web-ui">Opening the Web UI</a></li>
-<li><a href="#sshing-to-a-specific-task-machine">SSHing to a Specific Task Machine</a></li>
-<li><a href="#templating-command-arguments">Templating Command Arguments</a></li>
-</ul></li>
-</ul>
-
-<h2 id="introduction">Introduction</h2>
-
-<p>Once you have written an <code>.aurora</code> configuration file that describes
-your Job and its parameters and functionality, you interact with Aurora
-using Aurora Client commands. This document describes all of these commands
-and how and when to use them. All Aurora Client commands start with
-<code>aurora</code>, followed by the name of the specific command and its
-arguments.</p>
-
-<p><em>Job keys</em> are a very common argument to Aurora commands, as well as the
-gateway to useful information about a Job. Before using Aurora, you
-should read the next section which describes them in detail. The section
-after that briefly describes how you can modify the behavior of certain
-Aurora Client commands, linking to a detailed document about how to do
-that.</p>
-
-<p>This is followed by the Regular Jobs section, which describes the basic
-Client commands for creating, running, and manipulating Aurora Jobs.
-After that are sections on Comparing Jobs and Viewing/Examining Jobs. In
-other words, various commands for getting information and metadata about
-Aurora Jobs.</p>
-
-<h2 id="cluster-configuration">Cluster Configuration</h2>
-
-<p>The client must be able to find a configuration file that specifies available clusters. This file
-declares shorthand names for clusters, which are in turn referenced by job configuration files
-and client commands.</p>
-
-<p>The client will load at most two configuration files, making both of their defined clusters
-available. The first is intended to be a system-installed cluster, using the path specified in
-the environment variable <code>AURORA_CONFIG_ROOT</code>, defaulting to <code>/etc/aurora/clusters.json</code> if the
-environment variable is not set. The second is a user-installed file, located at
-<code>~/.aurora/clusters.json</code>.</p>
-
-<p>A cluster configuration is formatted as JSON. The simplest cluster configuration is one that
-communicates with a single (non-leader-elected) scheduler. For example:</p>
-<pre class="highlight javascript"><code><span style="background-color: #f8f8f8">[{</span>
- <span style="color: #d14">"name"</span><span style="background-color: #f8f8f8">:</span> <span style="color: #d14">"example"</span><span style="background-color: #f8f8f8">,</span>
- <span style="color: #d14">"scheduler_uri"</span><span style="background-color: #f8f8f8">:</span> <span style="color: #d14">"localhost:55555"</span><span style="background-color: #f8f8f8">,</span>
-<span style="background-color: #f8f8f8">}]</span>
-</code></pre>
-
-<p>A configuration for a leader-elected scheduler would contain something like:</p>
-<pre class="highlight javascript"><code><span style="background-color: #f8f8f8">[{</span>
- <span style="color: #d14">"name"</span><span style="background-color: #f8f8f8">:</span> <span style="color: #d14">"example"</span><span style="background-color: #f8f8f8">,</span>
- <span style="color: #d14">"zk"</span><span style="background-color: #f8f8f8">:</span> <span style="color: #d14">"192.168.33.7"</span><span style="background-color: #f8f8f8">,</span>
- <span style="color: #d14">"scheduler_zk_path"</span><span style="background-color: #f8f8f8">:</span> <span style="color: #d14">"/aurora/scheduler"</span>
-<span style="background-color: #f8f8f8">}]</span>
-</code></pre>
-
-<p>For more details on cluster configuration see the
-<a href="/documentation/0.10.0/client-cluster-configuration/">Client Cluster Configuration</a> documentation.</p>
-
-<h2 id="job-keys">Job Keys</h2>
-
-<p>A job key is a unique system-wide identifier for an Aurora-managed
-Job, for example <code>cluster1/web-team/test/experiment204</code>. It is a 4-tuple
-consisting of, in order, <em>cluster</em>, <em>role</em>, <em>environment</em>, and
-<em>jobname</em>, separated by /s. Cluster is the name of an Aurora
-cluster. Role is the Unix service account under which the Job
-runs. Environment is a namespace component like <code>devel</code>, <code>test</code>,
-<code>prod</code>, or <code>stagingN.</code> Jobname is the Job’s name.</p>
-
-<p>The combination of all four values uniquely specifies the Job. If any
-one value is different from that of another job key, the two job keys
-refer to different Jobs. For example, job key
-<code>cluster1/tyg/prod/workhorse</code> is different from
-<code>cluster1/tyg/prod/workcamel</code> is different from
-<code>cluster2/tyg/prod/workhorse</code> is different from
-<code>cluster2/foo/prod/workhorse</code> is different from
-<code>cluster1/tyg/test/workhorse.</code></p>
-
-<p>Role names are user accounts existing on the slave machines. If you don’t know what accounts
-are available, contact your sysadmin.</p>
-
-<p>Environment names are namespaces; you can count on <code>prod</code>, <code>devel</code> and <code>test</code> existing.</p>
-
-<h2 id="modifying-aurora-client-commands">Modifying Aurora Client Commands</h2>
-
-<p>For certain Aurora Client commands, you can define hook methods that run
-either before or after an action that takes place during the command’s
-execution, as well as based on whether the action finished successfully or failed
-during execution. Basically, a hook is code that lets you extend the
-command’s actions. The hook executes on the client side, specifically on
-the machine executing Aurora commands.</p>
-
-<p>Hooks can be associated with these Aurora Client commands.</p>
-
-<ul>
-<li><code>job cancel-update</code></li>
-<li><code>job create</code></li>
-<li><code>job kill</code></li>
-<li><code>job restart</code></li>
-<li><code>job update</code></li>
-</ul>
-
-<p>The process for writing and activating them is complex enough
-that we explain it in a devoted document, <a href="/documentation/0.10.0/hooks/">Hooks for Aurora Client API</a>.</p>
-
-<h2 id="regular-jobs">Regular Jobs</h2>
-
-<p>This section covers Aurora commands related to running, killing,
-renaming, updating, and restarting a basic Aurora Job.</p>
-
-<h3 id="creating-and-running-a-job">Creating and Running a Job</h3>
-<pre class="highlight plaintext"><code>aurora job create <job key> <configuration file>
-</code></pre>
-
-<p>Creates and then runs a Job with the specified job key based on a <code>.aurora</code> configuration file.
-The configuration file may also contain and activate hook definitions.</p>
-
-<h3 id="running-a-command-on-a-running-job">Running a Command On a Running Job</h3>
-<pre class="highlight plaintext"><code>aurora task run CLUSTER/ROLE/ENV/NAME[/INSTANCES] <cmd>
-</code></pre>
-
-<p>Runs a shell command on all machines currently hosting shards of a
-single Job.</p>
-
-<p><code>run</code> supports the same command line wildcards used to populate a Job’s
-commands; i.e. anything in the <code>{{mesos.*}}</code> and <code>{{thermos.*}}</code>
-namespaces.</p>
-
-<h3 id="killing-a-job">Killing a Job</h3>
-<pre class="highlight plaintext"><code>aurora job killall CLUSTER/ROLE/ENV/NAME
-</code></pre>
-
-<p>Kills all Tasks associated with the specified Job, blocking until all
-are terminated. Defaults to killing all instances in the Job.</p>
-
-<p>The <code><configuration file></code> argument for <code>kill</code> is optional. Use it only
-if it contains hook definitions and activations that affect the
-kill command.</p>
-
-<h3 id="updating-a-job">Updating a Job</h3>
-
-<p>There are several sub-commands to manage job updates:</p>
-<pre class="highlight plaintext"><code>aurora update start <job key> <configuration file>
-aurora update info <job key>
-aurora update pause <job key>
-aurora update resume <job key>
-aurora update abort <job key>
-aurora update list <cluster>
-</code></pre>
-
-<p>When you <code>start</code> a job update, the command will return once it has sent the
-instructions to the scheduler. At that point, you may view detailed
-progress for the update with the <code>info</code> subcommand, in addition to viewing
-graphical progress in the web browser. You may also get a full listing of
-in-progress updates in a cluster with <code>list</code>.</p>
-
-<p>Once an update has been started, you can <code>pause</code> to keep the update but halt
-progress. This can be useful for doing things like debug a partially-updated
-job to determine whether you would like to proceed. You can <code>resume</code> to
-proceed.</p>
-
-<p>You may <code>abort</code> a job update regardless of the state it is in. This will
-instruct the scheduler to completely abandon the job update and leave the job
-in the current (possibly partially-updated) state.</p>
-
-<h4 id="coordinated-job-updates">Coordinated job updates</h4>
-
-<p>Some Aurora services may benefit from having more control over updates by explicitly
-acknowledging (“heartbeating”) job update progress. This may be helpful for mission-critical
-service updates where explicit job health monitoring is vital during the entire job update
-lifecycle. Such job updates would rely on an external service (or a custom client) periodically
-pulsing an active coordinated job update via a
-<a href="https://github.com/apache/aurora/blob/#{git_tag}/api/src/main/thrift/org/apache/aurora/gen/api.thrift">pulseJobUpdate RPC</a>).</p>
-
-<p>A coordinated update is defined by setting a positive
-<a href="/documentation/0.10.0/configuration-reference/#updateconfig-objects">pulse<em>interval</em>secs</a> value in job configuration
-file. If no pulses are received within specified interval the update will be blocked. A blocked
-update is unable to continue rolling forward (or rolling back) but retains its active status.
-It may only be unblocked by a fresh <code>pulseJobUpdate</code> call.</p>
-
-<p>NOTE: A coordinated update starts in <code>ROLL_FORWARD_AWAITING_PULSE</code> state and will not make any
-progress until the first pulse arrives. However, a paused update (<code>ROLL_FORWARD_PAUSED</code> or
-<code>ROLL_BACK_PAUSED</code>) is still considered active and upon resuming will immediately make progress
-provided the pulse interval has not expired.</p>
-
-<h4 id="client-orchestrated-updates-deprecated">Client-orchestrated updates (deprecated)</h4>
-
-<p><em>Note: This feature is deprecated and will be removed in 0.9.0.
-Please use aurora update instead.</em></p>
-<pre class="highlight plaintext"><code>aurora job update CLUSTER/ROLE/ENV/NAME[/INSTANCES] <configuration file>
-aurora job cancel-update CLUSTER/ROLE/ENV/NAME
-</code></pre>
-
-<p>Given a running job, does a rolling update to reflect a new
-configuration version. Only updates Tasks in the Job with a changed
-configuration. You can further restrict the operated on Tasks by specifying
-specific instances that should be updated.</p>
-
-<p>You may want to run <code>aurora job diff</code> beforehand to validate which Tasks
-have different configurations.</p>
-
-<p>Updating jobs are locked to be sure the update finishes without
-disruption. If the update abnormally terminates, the lock may stay
-around and cause failure of subsequent update attempts.
- <code>aurora job cancel-update</code>unlocks the Job specified by
-its <code>job_key</code> argument. Be sure you don’t issue <code>job cancel-update</code> when
-another user is working with the specified Job.</p>
-
-<p>The <code><configuration file></code> argument for <code>job cancel-update</code> is optional. Use
-it only if it contains hook definitions and activations that affect the
-<code>cancel_update</code> command. The <code><configuration file></code> argument for
-<code>update</code> is required, but in addition to a new configuration it can be
-used to define and activate hooks for <code>job update</code>.</p>
-
-<h3 id="renaming-a-job">Renaming a Job</h3>
-
-<p>Renaming is a tricky operation as downstream clients must be informed of
-the new name. A conservative approach
-to renaming suitable for production services is:</p>
-
-<ol>
-<li> Modify the Aurora configuration file to change the role,
-environment, and/or name as appropriate to the standardized naming
-scheme.</li>
-<li><p>Check that only these naming components have changed
-with <code>aurora diff</code>.</p>
-<pre class="highlight plaintext"><code>aurora job diff CLUSTER/ROLE/ENV/NAME <job_configuration>
-</code></pre></li>
-<li><p>Create the (identical) job at the new key. You may need to request a
-temporary quota increase.</p>
-<pre class="highlight plaintext"><code>aurora job create CLUSTER/ROLE/ENV/NEW_NAME <job_configuration>
-</code></pre></li>
-<li><p>Migrate all clients over to the new job key. Update all links and
-dashboards. Ensure that both job keys run identical versions of the
-code while in this state.</p></li>
-<li><p>After verifying that all clients have successfully moved over, kill
-the old job.</p>
-<pre class="highlight plaintext"><code>aurora job killall CLUSTER/ROLE/ENV/NAME
-</code></pre></li>
-<li><p>If you received a temporary quota increase, be sure to let the
-powers that be know you no longer need the additional capacity.</p></li>
-</ol>
-
-<h3 id="restarting-jobs">Restarting Jobs</h3>
-
-<p><code>restart</code> restarts all of a job key identified Job’s shards:</p>
-<pre class="highlight plaintext"><code>aurora job restart CLUSTER/ROLE/ENV/NAME[/INSTANCES]
-</code></pre>
-
-<p>Restarts are controlled on the client side, so aborting
-the <code>job restart</code> command halts the restart operation.</p>
-
-<p><strong>Note</strong>: <code>job restart</code> only applies its command line arguments and does not
-use or is affected by <code>update.config</code>. Restarting
-does <strong><em>not</em></strong> involve a configuration change. To update the
-configuration, use <code>update.config</code>.</p>
-
-<p>The <code>--config</code> argument for restart is optional. Use it only
-if it contains hook definitions and activations that affect the
-<code>job restart</code> command.</p>
-
-<h2 id="cron-jobs">Cron Jobs</h2>
-
-<p>You can manage cron jobs using the <code>aurora cron</code> command. Please see
-<a href="/documentation/0.10.0/cron-jobs/">cron-jobs.md</a> for more details.</p>
-
-<p>You will see various commands and options relating to cron jobs in
-<code>aurora -h</code> and similar. Ignore them, as they’re not yet implemented.</p>
-
-<h2 id="comparing-jobs">Comparing Jobs</h2>
-<pre class="highlight plaintext"><code>aurora job diff CLUSTER/ROLE/ENV/NAME <job configuration>
-</code></pre>
-
-<p>Compares a job configuration against a running job. By default the diff
-is determined using <code>diff</code>, though you may choose an alternate
- diff program by specifying the <code>DIFF_VIEWER</code> environment variable.</p>
-
-<h2 id="viewing-examining-jobs">Viewing/Examining Jobs</h2>
-
-<p>Above we discussed creating, killing, and updating Jobs. Here we discuss
-how to view and examine Jobs.</p>
-
-<h3 id="listing-jobs">Listing Jobs</h3>
-<pre class="highlight plaintext"><code>aurora config list <job configuration>
-</code></pre>
-
-<p>Lists all Jobs registered with the Aurora scheduler in the named cluster for the named role.</p>
-
-<h3 id="inspecting-a-job">Inspecting a Job</h3>
-<pre class="highlight plaintext"><code>aurora job inspect CLUSTER/ROLE/ENV/NAME <job configuration>
-</code></pre>
-
-<p><code>inspect</code> verifies that its specified job can be parsed from a
-configuration file, and displays the parsed configuration.</p>
-
-<h3 id="checking-your-quota">Checking Your Quota</h3>
-<pre class="highlight plaintext"><code>aurora quota get CLUSTER/ROLE
-</code></pre>
-
-<p>Prints the production quota allocated to the role’s value at the given
-cluster. Only non-<a href="/documentation/0.10.0/deploying-aurora-scheduler/#dedicated-attribute">dedicated</a>
-<a href="/documentation/0.10.0/configuration-reference/#job-objects">production</a> jobs consume quota.</p>
-
-<h3 id="finding-a-job-on-web-ui">Finding a Job on Web UI</h3>
-
-<p>When you create a job, part of the output response contains a URL that goes
-to the job’s scheduler UI page. For example:</p>
-<pre class="highlight plaintext"><code>vagrant@precise64:~$ aurora job create devcluster/www-data/prod/hello /vagrant/examples/jobs/hello_world.aurora
-INFO] Creating job hello
-INFO] Response from scheduler: OK (message: 1 new tasks pending for job www-data/prod/hello)
-INFO] Job url: http://precise64:8081/scheduler/www-data/prod/hello
-</code></pre>
-
-<p>You can go to the scheduler UI page for this job via <code>http://precise64:8081/scheduler/www-data/prod/hello</code>
-You can go to the overall scheduler UI page by going to the part of that URL that ends at <code>scheduler</code>; <code>http://precise64:8081/scheduler</code></p>
-
-<p>Once you click through to a role page, you see Jobs arranged
-separately by pending jobs, active jobs and finished jobs.
-Jobs are arranged by role, typically a service account for
-production jobs and user accounts for test or development jobs.</p>
-
-<h3 id="getting-job-status">Getting Job Status</h3>
-<pre class="highlight plaintext"><code>aurora job status <job_key>
-</code></pre>
-
-<p>Returns the status of recent tasks associated with the
-<code>job_key</code> specified Job in its supplied cluster. Typically this includes
-a mix of active tasks (running or assigned) and inactive tasks
-(successful, failed, and lost.)</p>
-
-<h3 id="opening-the-web-ui">Opening the Web UI</h3>
-
-<p>Use the Job’s web UI scheduler URL or the <code>aurora status</code> command to find out on which
-machines individual tasks are scheduled. You can open the web UI via the
-<code>open</code> command line command if invoked from your machine:</p>
-<pre class="highlight plaintext"><code>aurora job open [<cluster>[/<role>[/<env>/<job_name>]]]
-</code></pre>
-
-<p>If only the cluster is specified, it goes directly to that cluster’s
-scheduler main page. If the role is specified, it goes to the top-level
-role page. If the full job key is specified, it goes directly to the job
-page where you can inspect individual tasks.</p>
-
-<h3 id="sshing-to-a-specific-task-machine">SSHing to a Specific Task Machine</h3>
-<pre class="highlight plaintext"><code>aurora task ssh <job_key> <shard number>
-</code></pre>
-
-<p>You can have the Aurora client ssh directly to the machine that has been
-assigned a particular Job/shard number. This may be useful for quickly
-diagnosing issues such as performance issues or abnormal behavior on a
-particular machine.</p>
-
-<h3 id="templating-command-arguments">Templating Command Arguments</h3>
-<pre class="highlight plaintext"><code>aurora task run [-e] [-t THREADS] <job_key> -- <<command-line>>
-</code></pre>
-
-<p>Given a job specification, run the supplied command on all hosts and
-return the output. You may use the standard Mustache templating rules:</p>
-
-<ul>
-<li><code>{{thermos.ports[name]}}</code> substitutes the specific named port of the
-task assigned to this machine</li>
-<li><code>{{mesos.instance}}</code> substitutes the shard id of the job’s task
-assigned to this machine</li>
-<li><code>{{thermos.task_id}}</code> substitutes the task id of the job’s task
-assigned to this machine</li>
-</ul>
-
-<p>For example, the following type of pattern can be a powerful diagnostic
-tool:</p>
-<pre class="highlight plaintext"><code>aurora task run -t5 cluster1/tyg/devel/seizure -- \
- 'curl -s -m1 localhost:{{thermos.ports[http]}}/vars | grep uptime'
-</code></pre>
-
-<p>By default, the command runs in the Task’s sandbox. The <code>-e</code> option can
-run the command in the executor’s sandbox. This is mostly useful for
-Aurora administrators.</p>
-
-<p>You can parallelize the runs by using the <code>-t</code> option.</p>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/committers/committers20191213-22326-1vzfde6 b/content/documentation/0.10.0/committers
similarity index 100%
rename from content/documentation/0.10.0/committers/committers20191213-22326-1vzfde6
rename to content/documentation/0.10.0/committers
diff --git a/content/documentation/0.10.0/committers/index.html b/content/documentation/0.10.0/committers/index.html
deleted file mode 100644
index ecfafdb..0000000
--- a/content/documentation/0.10.0/committers/index.html
+++ /dev/null
@@ -1,225 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/committers/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h2 id="setting-up-your-email-account">Setting up your email account</h2>
-
-<p>Once your Apache ID has been set up you can configure your account and add ssh keys and setup an
-email forwarding address at</p>
-
-<p><a href="http://id.apache.org">http://id.apache.org</a></p>
-
-<p>Additional instructions for setting up your new committer email can be found at</p>
-
-<p><a href="http://www.apache.org/dev/user-email.html">http://www.apache.org/dev/user-email.html</a></p>
-
-<p>The recommended setup is to configure all services (mailing lists, JIRA, ReviewBoard) to send
-emails to your @apache.org email address.</p>
-
-<h2 id="creating-a-gpg-key-for-releases">Creating a gpg key for releases</h2>
-
-<p>In order to create a release candidate you will need a gpg key published to an external key server
-and that key will need to be added to our KEYS file as well.</p>
-
-<ol>
-<li><p>Create a key:</p>
-<pre class="highlight plaintext"><code> gpg --gen-key
-</code></pre></li>
-<li><p>Add your gpg key to the Apache Aurora KEYS file:</p>
-<pre class="highlight plaintext"><code> git clone https://gitbox.apache.org/repos/asf/aurora.git
- (gpg --list-sigs <KEY ID> && gpg --armor --export <KEY ID>) >> KEYS
- git add KEYS && git commit -m "Adding gpg key for <APACHE ID>"
- ./rbt post -o -g
-</code></pre></li>
-<li><p>Publish the key to an external key server:</p>
-<pre class="highlight plaintext"><code> gpg --keyserver pgp.mit.edu --send-keys <KEY ID>
-</code></pre></li>
-<li><p>Update the changes to the KEYS file to the Apache Aurora svn dist locations listed below:</p>
-<pre class="highlight plaintext"><code> https://dist.apache.org/repos/dist/dev/aurora/KEYS
- https://dist.apache.org/repos/dist/release/aurora/KEYS
-</code></pre></li>
-<li><p>Add your key to git config for use with the release scripts:</p>
-<pre class="highlight plaintext"><code> git config --global user.signingkey <KEY ID>
-</code></pre></li>
-</ol>
-
-<h2 id="creating-a-release">Creating a release</h2>
-
-<p>The following will guide you through the steps to create a release candidate, vote, and finally an
-official Apache Aurora release. Before starting your gpg key should be in the KEYS file and you
-must have access to commit to the dist.a.o repositories.</p>
-
-<ol>
-<li><p>Ensure that all issues resolved for this release candidate are tagged with the correct Fix
-Version in Jira, the changelog script will use this to generate the CHANGELOG in step #2.</p></li>
-<li><p>Create a release candidate. This will automatically update the CHANGELOG and commit it, create a
-branch and update the current version within the trunk. To create a minor version update and publish
-it run</p>
-<pre class="highlight plaintext"><code> ./build-support/release/release-candidate -l m -p
-</code></pre></li>
-<li><p>Update, if necessary, the draft email created from the <code>release-candidate</code> script in step #2 and
-send the [VOTE] email to the dev@ and private@ mailing lists. You can verify the release signature
-and checksums by running</p>
-<pre class="highlight plaintext"><code> ./build-support/release/verify-release-candidate
-</code></pre></li>
-<li><p>Wait for the vote to complete. If the vote fails address any issues and go back to step #1 and
-run again, this time you will use the -r flag to increment the release candidate version. This will
-automatically clean up the release candidate rc0 branch and source distribution.</p>
-<pre class="highlight plaintext"><code> ./build-support/release/release-candidate -l m -r 1 -p
-</code></pre></li>
-<li><p>Once the vote has successfully passed create the release</p>
-<pre class="highlight plaintext"><code> ./build-support/release/release
-</code></pre></li>
-<li><p>Update the draft email created fom the <code>release</code> script in step #5 to include the Apache ID’s for
-all binding votes and send the [RESULT][VOTE] email to the dev@ and private@ mailing lists.</p></li>
-</ol>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/configuration-reference/configuration-reference20191213-22326-hnazkj b/content/documentation/0.10.0/configuration-reference
similarity index 100%
rename from content/documentation/0.10.0/configuration-reference/configuration-reference20191213-22326-hnazkj
rename to content/documentation/0.10.0/configuration-reference
diff --git a/content/documentation/0.10.0/configuration-reference/index.html b/content/documentation/0.10.0/configuration-reference/index.html
deleted file mode 100644
index 32557ec..0000000
--- a/content/documentation/0.10.0/configuration-reference/index.html
+++ /dev/null
@@ -1,1166 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/configuration-reference/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="aurora-thermos-configuration-reference">Aurora + Thermos Configuration Reference</h1>
-
-<ul>
-<li><a href="#aurora--thermos-configuration-reference">Aurora + Thermos Configuration Reference</a></li>
-<li><a href="#introduction">Introduction</a></li>
-<li><a href="#process-schema">Process Schema</a>
-
-<ul>
-<li><a href="#process-objects">Process Objects</a>
-
-<ul>
-<li><a href="#name">name</a></li>
-<li><a href="#cmdline">cmdline</a></li>
-<li><a href="#max_failures">max_failures</a></li>
-<li><a href="#daemon">daemon</a></li>
-<li><a href="#ephemeral">ephemeral</a></li>
-<li><a href="#min_duration">min_duration</a></li>
-<li><a href="#final">final</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#task-schema">Task Schema</a>
-
-<ul>
-<li><a href="#task-object">Task Object</a>
-
-<ul>
-<li><a href="#name-1">name</a></li>
-<li><a href="#processes">processes</a></li>
-<li><a href="#constraints">constraints</a></li>
-<li><a href="#resources">resources</a></li>
-<li><a href="#max_failures-1">max_failures</a></li>
-<li><a href="#max_concurrency">max_concurrency</a></li>
-<li><a href="#finalization_wait">finalization_wait</a></li>
-</ul></li>
-<li><a href="#constraint-object">Constraint Object</a></li>
-<li><a href="#resource-object">Resource Object</a></li>
-</ul></li>
-<li><a href="#job-schema">Job Schema</a>
-
-<ul>
-<li><a href="#job-objects">Job Objects</a></li>
-<li><a href="#services">Services</a></li>
-<li><a href="#revocable-jobs">Revocable Jobs</a></li>
-<li><a href="#updateconfig-objects">UpdateConfig Objects</a></li>
-<li><a href="#healthcheckconfig-objects">HealthCheckConfig Objects</a></li>
-<li><a href="#announcer-objects">Announcer Objects</a></li>
-<li><a href="#container">Container Objects</a></li>
-<li><a href="#lifecycleconfig-objects">LifecycleConfig Objects</a></li>
-</ul></li>
-<li><a href="#specifying-scheduling-constraints">Specifying Scheduling Constraints</a></li>
-<li><a href="#template-namespaces">Template Namespaces</a>
-
-<ul>
-<li><a href="#mesos-namespace">mesos Namespace</a></li>
-<li><a href="#thermos-namespace">thermos Namespace</a></li>
-</ul></li>
-<li><a href="#basic-examples">Basic Examples</a>
-
-<ul>
-<li><a href="#hello_worldaurora">hello_world.aurora</a></li>
-<li><a href="#environment-tailoring">Environment Tailoring</a>
-
-<ul>
-<li><a href="#hello_world_productionizedaurora">hello<em>world</em>productionized.aurora</a></li>
-</ul></li>
-</ul></li>
-</ul>
-
-<h1 id="introduction">Introduction</h1>
-
-<p>Don’t know where to start? The Aurora configuration schema is very
-powerful, and configurations can become quite complex for advanced use
-cases.</p>
-
-<p>For examples of simple configurations to get something up and running
-quickly, check out the <a href="/documentation/0.10.0/tutorial/">Tutorial</a>. When you feel comfortable with the basics, move
-on to the <a href="/documentation/0.10.0/configuration-tutorial/">Configuration Tutorial</a> for more in-depth coverage of
-configuration design.</p>
-
-<p>For additional basic configuration examples, see <a href="#BasicExamples">the end of this document</a>.</p>
-
-<h1 id="process-schema">Process Schema</h1>
-
-<p>Process objects consist of required <code>name</code> and <code>cmdline</code> attributes. You can customize Process
-behavior with its optional attributes. Remember, Processes are handled by Thermos.</p>
-
-<h3 id="process-objects">Process Objects</h3>
-
-<table><thead>
-<tr>
-<th><strong>Attribute Name</strong></th>
-<th style="text-align: center"><strong>Type</strong></th>
-<th><strong>Description</strong></th>
-</tr>
-</thead><tbody>
-<tr>
-<td><strong>name</strong></td>
-<td style="text-align: center">String</td>
-<td>Process name (Required)</td>
-</tr>
-<tr>
-<td><strong>cmdline</strong></td>
-<td style="text-align: center">String</td>
-<td>Command line (Required)</td>
-</tr>
-<tr>
-<td><strong>max_failures</strong></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum process failures (Default: 1)</td>
-</tr>
-<tr>
-<td><strong>daemon</strong></td>
-<td style="text-align: center">Boolean</td>
-<td>When True, this is a daemon process. (Default: False)</td>
-</tr>
-<tr>
-<td><strong>ephemeral</strong></td>
-<td style="text-align: center">Boolean</td>
-<td>When True, this is an ephemeral process. (Default: False)</td>
-</tr>
-<tr>
-<td><strong>min_duration</strong></td>
-<td style="text-align: center">Integer</td>
-<td>Minimum duration between process restarts in seconds. (Default: 15)</td>
-</tr>
-<tr>
-<td><strong>final</strong></td>
-<td style="text-align: center">Boolean</td>
-<td>When True, this process is a finalizing one that should run last. (Default: False)</td>
-</tr>
-</tbody></table>
-
-<h4 id="name">name</h4>
-
-<p>The name is any valid UNIX filename string (specifically no
-slashes, NULLs or leading periods). Within a Task object, each Process name
-must be unique.</p>
-
-<h4 id="cmdline">cmdline</h4>
-
-<p>The command line run by the process. The command line is invoked in a bash
-subshell, so can involve fully-blown bash scripts. However, nothing is
-supplied for command-line arguments so <code>$*</code> is unspecified.</p>
-
-<h4 id="max_failures">max_failures</h4>
-
-<p>The maximum number of failures (non-zero exit statuses) this process can
-have before being marked permanently failed and not retried. If a
-process permanently fails, Thermos looks at the failure limit of the task
-containing the process (usually 1) to determine if the task has
-failed as well.</p>
-
-<p>Setting <code>max_failures</code> to 0 makes the process retry
-indefinitely until it achieves a successful (zero) exit status.
-It retries at most once every <code>min_duration</code> seconds to prevent
-an effective denial of service attack on the coordinating Thermos scheduler.</p>
-
-<h4 id="daemon">daemon</h4>
-
-<p>By default, Thermos processes are non-daemon. If <code>daemon</code> is set to True, a
-successful (zero) exit status does not prevent future process runs.
-Instead, the process reinvokes after <code>min_duration</code> seconds.
-However, the maximum failure limit still applies. A combination of
-<code>daemon=True</code> and <code>max_failures=0</code> causes a process to retry
-indefinitely regardless of exit status. This should be avoided
-for very short-lived processes because of the accumulation of
-checkpointed state for each process run. When running in Mesos
-specifically, <code>max_failures</code> is capped at 100.</p>
-
-<h4 id="ephemeral">ephemeral</h4>
-
-<p>By default, Thermos processes are non-ephemeral. If <code>ephemeral</code> is set to
-True, the process’ status is not used to determine if its containing task
-has completed. For example, consider a task with a non-ephemeral
-webserver process and an ephemeral logsaver process
-that periodically checkpoints its log files to a centralized data store.
-The task is considered finished once the webserver process has
-completed, regardless of the logsaver’s current status.</p>
-
-<h4 id="min_duration">min_duration</h4>
-
-<p>Processes may succeed or fail multiple times during a single task’s
-duration. Each of these is called a <em>process run</em>. <code>min_duration</code> is
-the minimum number of seconds the scheduler waits before running the
-same process.</p>
-
-<h4 id="final">final</h4>
-
-<p>Processes can be grouped into two classes: ordinary processes and
-finalizing processes. By default, Thermos processes are ordinary. They
-run as long as the task is considered healthy (i.e., no failure
-limits have been reached.) But once all regular Thermos processes
-finish or the task reaches a certain failure threshold, it
-moves into a “finalization” stage and runs all finalizing
-processes. These are typically processes necessary for cleaning up the
-task, such as log checkpointers, or perhaps e-mail notifications that
-the task completed.</p>
-
-<p>Finalizing processes may not depend upon ordinary processes or
-vice-versa, however finalizing processes may depend upon other
-finalizing processes and otherwise run as a typical process
-schedule.</p>
-
-<h1 id="task-schema">Task Schema</h1>
-
-<p>Tasks fundamentally consist of a <code>name</code> and a list of Process objects stored as the
-value of the <code>processes</code> attribute. Processes can be further constrained with
-<code>constraints</code>. By default, <code>name</code>’s value inherits from the first Process in the
-<code>processes</code> list, so for simple <code>Task</code> objects with one Process, <code>name</code>
-can be omitted. In Mesos, <code>resources</code> is also required.</p>
-
-<h3 id="task-object">Task Object</h3>
-
-<table><thead>
-<tr>
-<th><strong>param</strong></th>
-<th style="text-align: center"><strong>type</strong></th>
-<th><strong>description</strong></th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>name</code></td>
-<td style="text-align: center">String</td>
-<td>Process name (Required) (Default: <code>processes0.name</code>)</td>
-</tr>
-<tr>
-<td><code>processes</code></td>
-<td style="text-align: center">List of <code>Process</code> objects</td>
-<td>List of <code>Process</code> objects bound to this task. (Required)</td>
-</tr>
-<tr>
-<td><code>constraints</code></td>
-<td style="text-align: center">List of <code>Constraint</code> objects</td>
-<td>List of <code>Constraint</code> objects constraining processes.</td>
-</tr>
-<tr>
-<td><code>resources</code></td>
-<td style="text-align: center"><code>Resource</code> object</td>
-<td>Resource footprint. (Required)</td>
-</tr>
-<tr>
-<td><code>max_failures</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum process failures before being considered failed (Default: 1)</td>
-</tr>
-<tr>
-<td><code>max_concurrency</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of concurrent processes (Default: 0, unlimited concurrency.)</td>
-</tr>
-<tr>
-<td><code>finalization_wait</code></td>
-<td style="text-align: center">Integer</td>
-<td>Amount of time allocated for finalizing processes, in seconds. (Default: 30)</td>
-</tr>
-</tbody></table>
-
-<h4 id="name">name</h4>
-
-<p><code>name</code> is a string denoting the name of this task. It defaults to the name of the first Process in
-the list of Processes associated with the <code>processes</code> attribute.</p>
-
-<h4 id="processes">processes</h4>
-
-<p><code>processes</code> is an unordered list of <code>Process</code> objects. To constrain the order
-in which they run, use <code>constraints</code>.</p>
-
-<h5 id="constraints">constraints</h5>
-
-<p>A list of <code>Constraint</code> objects. Currently it supports only one type,
-the <code>order</code> constraint. <code>order</code> is a list of process names
-that should run in the order given. For example,</p>
-<pre class="highlight plaintext"><code> process = Process(cmdline = "echo hello {{name}}")
- task = Task(name = "echoes",
- processes = [process(name = "jim"), process(name = "bob")],
- constraints = [Constraint(order = ["jim", "bob"]))
-</code></pre>
-
-<p>Constraints can be supplied ad-hoc and in duplicate. Not all
-Processes need be constrained, however Tasks with cycles are
-rejected by the Thermos scheduler.</p>
-
-<p>Use the <code>order</code> function as shorthand to generate <code>Constraint</code> lists.
-The following:</p>
-<pre class="highlight plaintext"><code> order(process1, process2)
-</code></pre>
-
-<p>is shorthand for</p>
-<pre class="highlight plaintext"><code> [Constraint(order = [process1.name(), process2.name()])]
-</code></pre>
-
-<p>The <code>order</code> function accepts Process name strings <code>('foo', 'bar')</code> or the processes
-themselves, e.g. <code>foo=Process(name='foo', ...)</code>, <code>bar=Process(name='bar', ...)</code>,
-<code>constraints=order(foo, bar)</code>.</p>
-
-<h4 id="resources">resources</h4>
-
-<p>Takes a <code>Resource</code> object, which specifies the amounts of CPU, memory, and disk space resources
-to allocate to the Task.</p>
-
-<h4 id="max_failures">max_failures</h4>
-
-<p><code>max_failures</code> is the number of failed processes needed for the <code>Task</code> to be
-marked as failed.</p>
-
-<p>For example, assume a Task has two Processes and a <code>max_failures</code> value of <code>2</code>:</p>
-<pre class="highlight plaintext"><code> template = Process(max_failures=10)
- task = Task(
- name = "fail",
- processes = [
- template(name = "failing", cmdline = "exit 1"),
- template(name = "succeeding", cmdline = "exit 0")
- ],
- max_failures=2)
-</code></pre>
-
-<p>The <code>failing</code> Process could fail 10 times before being marked as permanently
-failed, and the <code>succeeding</code> Process could succeed on the first run. However,
-the task would succeed despite only allowing for two failed processes. To be more
-specific, there would be 10 failed process runs yet 1 failed process. Both processes
-would have to fail for the Task to fail.</p>
-
-<h4 id="max_concurrency">max_concurrency</h4>
-
-<p>For Tasks with a number of expensive but otherwise independent
-processes, you may want to limit the amount of concurrency
-the Thermos scheduler provides rather than artificially constraining
-it via <code>order</code> constraints. For example, a test framework may
-generate a task with 100 test run processes, but wants to run it on
-a machine with only 4 cores. You can limit the amount of parallelism to
-4 by setting <code>max_concurrency=4</code> in your task configuration.</p>
-
-<p>For example, the following task spawns 180 Processes (“mappers”)
-to compute individual elements of a 180 degree sine table, all dependent
-upon one final Process (“reducer”) to tabulate the results:</p>
-<pre class="highlight plaintext"><code>def make_mapper(id):
- return Process(
- name = "mapper%03d" % id,
- cmdline = "echo 'scale=50;s(%d\*4\*a(1)/180)' | bc -l >
- temp.sine_table.%03d" % (id, id))
-
-def make_reducer():
- return Process(name = "reducer", cmdline = "cat temp.\* | nl \> sine\_table.txt
- && rm -f temp.\*")
-
-processes = map(make_mapper, range(180))
-
-task = Task(
- name = "mapreduce",
- processes = processes + [make\_reducer()],
- constraints = [Constraint(order = [mapper.name(), 'reducer']) for mapper
- in processes],
- max_concurrency = 8)
-</code></pre>
-
-<h4 id="finalization_wait">finalization_wait</h4>
-
-<p>Tasks have three active stages: <code>ACTIVE</code>, <code>CLEANING</code>, and <code>FINALIZING</code>. The
-<code>ACTIVE</code> stage is when ordinary processes run. This stage lasts as
-long as Processes are running and the Task is healthy. The moment either
-all Processes have finished successfully or the Task has reached a
-maximum Process failure limit, it goes into <code>CLEANING</code> stage and send
-SIGTERMs to all currently running Processes and their process trees.
-Once all Processes have terminated, the Task goes into <code>FINALIZING</code> stage
-and invokes the schedule of all Processes with the “final” attribute set to True.</p>
-
-<p>This whole process from the end of <code>ACTIVE</code> stage to the end of <code>FINALIZING</code>
-must happen within <code>finalization_wait</code> seconds. If it does not
-finish during that time, all remaining Processes are sent SIGKILLs
-(or if they depend upon uncompleted Processes, are
-never invoked.)</p>
-
-<p>Client applications with higher priority may force a shorter
-finalization wait (e.g. through parameters to <code>thermos kill</code>), so this
-is mostly a best-effort signal.</p>
-
-<h3 id="constraint-object">Constraint Object</h3>
-
-<p>Current constraint objects only support a single ordering constraint, <code>order</code>,
-which specifies its processes run sequentially in the order given. By
-default, all processes run in parallel when bound to a <code>Task</code> without
-ordering constraints.</p>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>order</td>
-<td style="text-align: center">List of String</td>
-<td>List of processes by name (String) that should be run serially.</td>
-</tr>
-</tbody></table>
-
-<h3 id="resource-object">Resource Object</h3>
-
-<p>Specifies the amount of CPU, Ram, and disk resources the task needs. See the
-<a href="/documentation/0.10.0/resources/">Resource Isolation document</a> for suggested values and to understand how
-resources are allocated.</p>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>cpu</code></td>
-<td style="text-align: center">Float</td>
-<td>Fractional number of cores required by the task.</td>
-</tr>
-<tr>
-<td><code>ram</code></td>
-<td style="text-align: center">Integer</td>
-<td>Bytes of RAM required by the task.</td>
-</tr>
-<tr>
-<td><code>disk</code></td>
-<td style="text-align: center">Integer</td>
-<td>Bytes of disk required by the task.</td>
-</tr>
-</tbody></table>
-
-<h1 id="job-schema">Job Schema</h1>
-
-<h3 id="job-objects">Job Objects</h3>
-
-<table><thead>
-<tr>
-<th>name</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>task</code></td>
-<td style="text-align: center">Task</td>
-<td>The Task object to bind to this job. Required.</td>
-</tr>
-<tr>
-<td><code>name</code></td>
-<td style="text-align: center">String</td>
-<td>Job name. (Default: inherited from the task attribute’s name)</td>
-</tr>
-<tr>
-<td><code>role</code></td>
-<td style="text-align: center">String</td>
-<td>Job role account. Required.</td>
-</tr>
-<tr>
-<td><code>cluster</code></td>
-<td style="text-align: center">String</td>
-<td>Cluster in which this job is scheduled. Required.</td>
-</tr>
-<tr>
-<td><code>environment</code></td>
-<td style="text-align: center">String</td>
-<td>Job environment, default <code>devel</code>. Must be one of <code>prod</code>, <code>devel</code>, <code>test</code> or <code>staging<number></code>.</td>
-</tr>
-<tr>
-<td><code>contact</code></td>
-<td style="text-align: center">String</td>
-<td>Best email address to reach the owner of the job. For production jobs, this is usually a team mailing list.</td>
-</tr>
-<tr>
-<td><code>instances</code></td>
-<td style="text-align: center">Integer</td>
-<td>Number of instances (sometimes referred to as replicas or shards) of the task to create. (Default: 1)</td>
-</tr>
-<tr>
-<td><code>cron_schedule</code></td>
-<td style="text-align: center">String</td>
-<td>Cron schedule in cron format. May only be used with non-service jobs. See <a href="/documentation/0.10.0/cron-jobs/">Cron Jobs</a> for more information. Default: None (not a cron job.)</td>
-</tr>
-<tr>
-<td><code>cron_collision_policy</code></td>
-<td style="text-align: center">String</td>
-<td>Policy to use when a cron job is triggered while a previous run is still active. KILL<em>EXISTING Kill the previous run, and schedule the new run CANCEL</em>NEW Let the previous run continue, and cancel the new run. (Default: KILL_EXISTING)</td>
-</tr>
-<tr>
-<td><code>update_config</code></td>
-<td style="text-align: center"><code>UpdateConfig</code> object</td>
-<td>Parameters for controlling the rate and policy of rolling updates.</td>
-</tr>
-<tr>
-<td><code>constraints</code></td>
-<td style="text-align: center">dict</td>
-<td>Scheduling constraints for the tasks. See the section on the <a href="#Specifying-Scheduling-Constraints">constraint specification language</a></td>
-</tr>
-<tr>
-<td><code>service</code></td>
-<td style="text-align: center">Boolean</td>
-<td>If True, restart tasks regardless of success or failure. (Default: False)</td>
-</tr>
-<tr>
-<td><code>max_task_failures</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of failures after which the task is considered to have failed (Default: 1) Set to -1 to allow for infinite failures</td>
-</tr>
-<tr>
-<td><code>priority</code></td>
-<td style="text-align: center">Integer</td>
-<td>Preemption priority to give the task (Default 0). Tasks with higher priorities may preempt tasks at lower priorities.</td>
-</tr>
-<tr>
-<td><code>production</code></td>
-<td style="text-align: center">Boolean</td>
-<td>Whether or not this is a production task that may <a href="/documentation/0.10.0/resources/#task-preemption">preempt</a> other tasks (Default: False). Production job role must have the appropriate <a href="/documentation/0.10.0/resources/#resource-quota">quota</a>.</td>
-</tr>
-<tr>
-<td><code>health_check_config</code></td>
-<td style="text-align: center"><code>HealthCheckConfig</code> object</td>
-<td>Parameters for controlling a task’s health checks via HTTP. Only used if a health port was assigned with a command line wildcard.</td>
-</tr>
-<tr>
-<td><code>container</code></td>
-<td style="text-align: center"><code>Container</code> object</td>
-<td>An optional container to run all processes inside of.</td>
-</tr>
-<tr>
-<td><code>lifecycle</code></td>
-<td style="text-align: center"><code>LifecycleConfig</code> object</td>
-<td>An optional task lifecycle configuration that dictates commands to be executed on startup/teardown. HTTP lifecycle is enabled by default if the “health” port is requested. See <a href="#lifecycleconfig-objects">LifecycleConfig Objects</a> for more information.</td>
-</tr>
-<tr>
-<td><code>tier</code></td>
-<td style="text-align: center">String</td>
-<td>Task tier type. When set to <code>revocable</code> requires the task to run with Mesos revocable resources. This is work <a href="https://issues.apache.org/jira/browse/AURORA-1343">in progress</a> and is currently only supported for the revocable tasks. The ultimate goal is to simplify task configuration by hiding various configuration knobs behind a task tier definition. See AURORA-1343 and AURORA-1443 for more details.</td>
-</tr>
-</tbody></table>
-
-<h3 id="services">Services</h3>
-
-<p>Jobs with the <code>service</code> flag set to True are called Services. The <code>Service</code>
-alias can be used as shorthand for <code>Job</code> with <code>service=True</code>.
-Services are differentiated from non-service Jobs in that tasks
-always restart on completion, whether successful or unsuccessful.
-Jobs without the service bit set only restart up to
-<code>max_task_failures</code> times and only if they terminated unsuccessfully
-either due to human error or machine failure.</p>
-
-<h3 id="revocable-jobs">Revocable Jobs</h3>
-
-<p><strong>WARNING</strong>: This feature is currently in alpha status. Do not use it in production clusters!</p>
-
-<p>Mesos <a href="http://mesos.apache.org/documentation/latest/oversubscription/">supports a concept of revocable tasks</a>
-by oversubscribing machine resources by the amount deemed safe to not affect the existing
-non-revocable tasks. Aurora now supports revocable jobs via a <code>tier</code> setting set to <code>revocable</code>
-value.</p>
-
-<p>More implementation details in this <a href="https://issues.apache.org/jira/browse/AURORA-1343">ticket</a>.</p>
-
-<p>Scheduler must be <a href="/documentation/0.10.0/deploying-aurora-scheduler/#configuring-resource-oversubscription">configured</a>
-to receive revocable offers from Mesos and accept revocable jobs. If not configured properly
-revocable tasks will never get assigned to hosts and will stay in PENDING.</p>
-
-<h3 id="updateconfig-objects">UpdateConfig Objects</h3>
-
-<p>Parameters for controlling the rate and policy of rolling updates.</p>
-
-<table><thead>
-<tr>
-<th>object</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>batch_size</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of shards to be updated in one iteration (Default: 1)</td>
-</tr>
-<tr>
-<td><code>restart_threshold</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of seconds before a shard must move into the <code>RUNNING</code> state before considered a failure (Default: 60)</td>
-</tr>
-<tr>
-<td><code>watch_secs</code></td>
-<td style="text-align: center">Integer</td>
-<td>Minimum number of seconds a shard must remain in <code>RUNNING</code> state before considered a success (Default: 45)</td>
-</tr>
-<tr>
-<td><code>max_per_shard_failures</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of restarts per shard during update. Increments total failure count when this limit is exceeded. (Default: 0)</td>
-</tr>
-<tr>
-<td><code>max_total_failures</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of shard failures to be tolerated in total during an update. Cannot be greater than or equal to the total number of tasks in a job. (Default: 0)</td>
-</tr>
-<tr>
-<td><code>rollback_on_failure</code></td>
-<td style="text-align: center">boolean</td>
-<td>When False, prevents auto rollback of a failed update (Default: True)</td>
-</tr>
-<tr>
-<td><code>wait_for_batch_completion</code></td>
-<td style="text-align: center">boolean</td>
-<td>When True, all threads from a given batch will be blocked from picking up new instances until the entire batch is updated. This essentially simulates the legacy sequential updater algorithm. (Default: False)</td>
-</tr>
-<tr>
-<td><code>pulse_interval_secs</code></td>
-<td style="text-align: center">Integer</td>
-<td>Indicates a <a href="/documentation/0.10.0/client-commands/#coordinated-job-updates">coordinated update</a>. If no pulses are received within the provided interval the update will be blocked. Beta-updater only. Will fail on submission when used with client updater. (Default: None)</td>
-</tr>
-</tbody></table>
-
-<h3 id="healthcheckconfig-objects">HealthCheckConfig Objects</h3>
-
-<p>Parameters for controlling a task’s health checks via HTTP.</p>
-
-<table><thead>
-<tr>
-<th>object</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>initial_interval_secs</code></td>
-<td style="text-align: center">Integer</td>
-<td>Initial delay for performing an HTTP health check. (Default: 15)</td>
-</tr>
-<tr>
-<td><code>interval_secs</code></td>
-<td style="text-align: center">Integer</td>
-<td>Interval on which to check the task’s health via HTTP. (Default: 10)</td>
-</tr>
-<tr>
-<td><code>max_consecutive_failures</code></td>
-<td style="text-align: center">Integer</td>
-<td>Maximum number of consecutive failures that tolerated before considering a task unhealthy (Default: 0)</td>
-</tr>
-<tr>
-<td><code>timeout_secs</code></td>
-<td style="text-align: center">Integer</td>
-<td>HTTP request timeout. (Default: 1)</td>
-</tr>
-<tr>
-<td><code>endpoint</code></td>
-<td style="text-align: center">String</td>
-<td>HTTP endpoint to check (Default: /health)</td>
-</tr>
-<tr>
-<td><code>expected_response</code></td>
-<td style="text-align: center">String</td>
-<td>If not empty, fail the health check if the response differs. Case insensitive. (Default: ok)</td>
-</tr>
-<tr>
-<td><code>expected_response_code</code></td>
-<td style="text-align: center">Integer</td>
-<td>If not zero, fail the health check if the response code differs. (Default: 0)</td>
-</tr>
-</tbody></table>
-
-<h3 id="announcer-objects">Announcer Objects</h3>
-
-<p>If the <code>announce</code> field in the Job configuration is set, each task will be
-registered in the ServerSet <code>/aurora/role/environment/jobname</code> in the
-zookeeper ensemble configured by the executor. If no Announcer object is specified,
-no announcement will take place. For more information about ServerSets, see the <a href="/documentation/0.10.0/user-guide/">User Guide</a>.</p>
-
-<table><thead>
-<tr>
-<th>object</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>primary_port</code></td>
-<td style="text-align: center">String</td>
-<td>Which named port to register as the primary endpoint in the ServerSet (Default: <code>http</code>)</td>
-</tr>
-<tr>
-<td><code>portmap</code></td>
-<td style="text-align: center">dict</td>
-<td>A mapping of additional endpoints to announced in the ServerSet (Default: <code>{ 'aurora': '{{primary_port}}' }</code>)</td>
-</tr>
-</tbody></table>
-
-<h3 id="port-aliasing-with-the-announcer-portmap">Port aliasing with the Announcer <code>portmap</code></h3>
-
-<p>The primary endpoint registered in the ServerSet is the one allocated to the port
-specified by the <code>primary_port</code> in the <code>Announcer</code> object, by default
-the <code>http</code> port. This port can be referenced from anywhere within a configuration
-as <code>{{thermos.ports[http]}}</code>.</p>
-
-<p>Without the port map, each named port would be allocated a unique port number.
-The <code>portmap</code> allows two different named ports to be aliased together. The default
-<code>portmap</code> aliases the <code>aurora</code> port (i.e. <code>{{thermos.ports[aurora]}}</code>) to
-the <code>http</code> port. Even though the two ports can be referenced independently,
-only one port is allocated by Mesos. Any port referenced in a <code>Process</code> object
-but which is not in the portmap will be allocated dynamically by Mesos and announced as well.</p>
-
-<p>It is possible to use the portmap to alias names to static port numbers, e.g.
-<code>{'http': 80, 'https': 443, 'aurora': 'http'}</code>. In this case, referencing
-<code>{{thermos.ports[aurora]}}</code> would look up <code>{{thermos.ports[http]}}</code> then
-find a static port 80. No port would be requested of or allocated by Mesos.</p>
-
-<p>Static ports should be used cautiously as Aurora does nothing to prevent two
-tasks with the same static port allocations from being co-scheduled.
-External constraints such as slave attributes should be used to enforce such
-guarantees should they be needed.</p>
-
-<h3 id="container-object">Container Object</h3>
-
-<p><em>Note: The only container type currently supported is “docker”. Docker support is currently EXPERIMENTAL.</em>
-<em>Note: In order to correctly execute processes inside a job, the Docker container must have python 2.7 installed.</em></p>
-
-<p>Describes the container the job’s processes will run inside.</p>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>docker</code></td>
-<td style="text-align: center">Docker</td>
-<td>A docker container to use.</td>
-</tr>
-</tbody></table>
-
-<h3 id="docker-object">Docker Object</h3>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>image</code></td>
-<td style="text-align: center">String</td>
-<td>The name of the docker image to execute. If the image does not exist locally it will be pulled with <code>docker pull</code>.</td>
-</tr>
-<tr>
-<td><code>parameters</code></td>
-<td style="text-align: center">List(Parameter)</td>
-<td>Additional parameters to pass to the docker containerizer.</td>
-</tr>
-</tbody></table>
-
-<h3 id="docker-parameter-object">Docker Parameter Object</h3>
-
-<p>Docker CLI parameters. This needs to be enabled by the scheduler <code>enable_docker_parameters</code> option.
-See <a href="https://docs.docker.com/reference/commandline/run/">Docker Command Line Reference</a> for valid parameters. </p>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>name</code></td>
-<td style="text-align: center">String</td>
-<td>The name of the docker parameter. E.g. volume</td>
-</tr>
-<tr>
-<td><code>value</code></td>
-<td style="text-align: center">String</td>
-<td>The value of the parameter. E.g. /usr/local/bin:/usr/bin:rw</td>
-</tr>
-</tbody></table>
-
-<h3 id="lifecycleconfig-objects">LifecycleConfig Objects</h3>
-
-<p><em>Note: The only lifecycle configuration supported is the HTTP lifecycle via the HTTPLifecycleConfig.</em></p>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>http</code></td>
-<td style="text-align: center">HTTPLifecycleConfig</td>
-<td>Configure the lifecycle manager to send lifecycle commands to the task via HTTP.</td>
-</tr>
-</tbody></table>
-
-<h3 id="httplifecycleconfig-objects">HTTPLifecycleConfig Objects</h3>
-
-<table><thead>
-<tr>
-<th>param</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>port</code></td>
-<td style="text-align: center">String</td>
-<td>The named port to send POST commands (Default: health)</td>
-</tr>
-<tr>
-<td><code>graceful_shutdown_endpoint</code></td>
-<td style="text-align: center">String</td>
-<td>Endpoint to hit to indicate that a task should gracefully shutdown. (Default: /quitquitquit)</td>
-</tr>
-<tr>
-<td><code>shutdown_endpoint</code></td>
-<td style="text-align: center">String</td>
-<td>Endpoint to hit to give a task its final warning before being killed. (Default: /abortabortabort)</td>
-</tr>
-</tbody></table>
-
-<h4 id="gracefulshutdownendpoint">graceful<em>shutdown</em>endpoint</h4>
-
-<p>If the Job is listening on the port as specified by the HTTPLifecycleConfig
-(default: <code>health</code>), a HTTP POST request will be sent over localhost to this
-endpoint to request that the task gracefully shut itself down. This is a
-courtesy call before the <code>shutdown_endpoint</code> is invoked a fixed amount of
-time later.</p>
-
-<h4 id="shutdown_endpoint">shutdown_endpoint</h4>
-
-<p>If the Job is listening on the port as specified by the HTTPLifecycleConfig
-(default: <code>health</code>), a HTTP POST request will be sent over localhost to this
-endpoint to request as a final warning before being shut down. If the task
-does not shut down on its own after this, it will be forcefully killed</p>
-
-<h1 id="specifying-scheduling-constraints">Specifying Scheduling Constraints</h1>
-
-<p>Most users will not need to specify constraints explicitly, as the
-scheduler automatically inserts reasonable defaults that attempt to
-ensure reliability without impacting schedulability. For example, the
-scheduler inserts a <code>host: limit:1</code> constraint, ensuring
-that your shards run on different physical machines. Please do not
-set this field unless you are sure of what you are doing.</p>
-
-<p>In the <code>Job</code> object there is a map <code>constraints</code> from String to String
-allowing the user to tailor the schedulability of tasks within the job.</p>
-
-<p>Each slave in the cluster is assigned a set of string-valued
-key/value pairs called attributes. For example, consider the host
-<code>cluster1-aaa-03-sr2</code> and its following attributes (given in key:value
-format): <code>host:cluster1-aaa-03-sr2</code> and <code>rack:aaa</code>.</p>
-
-<p>The constraint map’s key value is the attribute name in which we
-constrain Tasks within our Job. The value is how we constrain them.
-There are two types of constraints: <em>limit constraints</em> and <em>value
-constraints</em>.</p>
-
-<table><thead>
-<tr>
-<th>constraint</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>Limit</td>
-<td>A string that specifies a limit for a constraint. Starts with <code>'limit:</code> followed by an Integer and closing single quote, such as <code>'limit:1'</code>.</td>
-</tr>
-<tr>
-<td>Value</td>
-<td>A string that specifies a value for a constraint. To include a list of values, separate the values using commas. To negate the values of a constraint, start with a <code>!</code> <code>.</code></td>
-</tr>
-</tbody></table>
-
-<p>You can also control machine diversity using constraints. The below
-constraint ensures that no more than two instances of your job may run
-on a single host. Think of this as a “group by” limit.</p>
-<pre class="highlight plaintext"><code>constraints = {
- 'host': 'limit:2',
-}
-</code></pre>
-
-<p>Likewise, you can use constraints to control rack diversity, e.g. at
-most one task per rack:</p>
-<pre class="highlight plaintext"><code>constraints = {
- 'rack': 'limit:1',
-}
-</code></pre>
-
-<p>Use these constraints sparingly as they can dramatically reduce Tasks’ schedulability.</p>
-
-<h1 id="template-namespaces">Template Namespaces</h1>
-
-<p>Currently, a few Pystachio namespaces have special semantics. Using them
-in your configuration allow you to tailor application behavior
-through environment introspection or interact in special ways with the
-Aurora client or Aurora-provided services.</p>
-
-<h3 id="mesos-namespace">mesos Namespace</h3>
-
-<p>The <code>mesos</code> namespace contains the <code>instance</code> variable that can be used
-to distinguish between Task replicas.</p>
-
-<table><thead>
-<tr>
-<th>variable name</th>
-<th style="text-align: center">type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td><code>instance</code></td>
-<td style="text-align: center">Integer</td>
-<td>The instance number of the created task. A job with 5 replicas has instance numbers 0, 1, 2, 3, and 4.</td>
-</tr>
-</tbody></table>
-
-<h3 id="thermos-namespace">thermos Namespace</h3>
-
-<p>The <code>thermos</code> namespace contains variables that work directly on the
-Thermos platform in addition to Aurora. This namespace is fully
-compatible with Tasks invoked via the <code>thermos</code> CLI.</p>
-
-<table><thead>
-<tr>
-<th style="text-align: center">variable</th>
-<th>type</th>
-<th>description</th>
-</tr>
-</thead><tbody>
-<tr>
-<td style="text-align: center"><code>ports</code></td>
-<td>map of string to Integer</td>
-<td>A map of names to port numbers</td>
-</tr>
-<tr>
-<td style="text-align: center"><code>task_id</code></td>
-<td>string</td>
-<td>The task ID assigned to this task.</td>
-</tr>
-</tbody></table>
-
-<p>The <code>thermos.ports</code> namespace is automatically populated by Aurora when
-invoking tasks on Mesos. When running the <code>thermos</code> command directly,
-these ports must be explicitly mapped with the <code>-P</code> option.</p>
-
-<p>For example, if ’{{<code>thermos.ports[http]</code>}}’ is specified in a <code>Process</code>
-configuration, it is automatically extracted and auto-populated by
-Aurora, but must be specified with, for example, <code>thermos -P http:12345</code>
-to map <code>http</code> to port 12345 when running via the CLI.</p>
-
-<h1 id="basic-examples">Basic Examples</h1>
-
-<p>These are provided to give a basic understanding of simple Aurora jobs.</p>
-
-<h3 id="hello_world-aurora">hello_world.aurora</h3>
-
-<p>Put the following in a file named <code>hello_world.aurora</code>, substituting your own values
-for values such as <code>cluster</code>s.</p>
-<pre class="highlight plaintext"><code>import os
-hello_world_process = Process(name = 'hello_world', cmdline = 'echo hello world')
-
-hello_world_task = Task(
- resources = Resources(cpu = 0.1, ram = 16 * MB, disk = 16 * MB),
- processes = [hello_world_process])
-
-hello_world_job = Job(
- cluster = 'cluster1',
- role = os.getenv('USER'),
- task = hello_world_task)
-
-jobs = [hello_world_job]
-</code></pre>
-
-<p>Then issue the following commands to create and kill the job, using your own values for the job key.</p>
-<pre class="highlight plaintext"><code>aurora job create cluster1/$USER/test/hello_world hello_world.aurora
-
-aurora job kill cluster1/$USER/test/hello_world
-</code></pre>
-
-<h3 id="environment-tailoring">Environment Tailoring</h3>
-
-<h4 id="helloworldproductionized-aurora">hello<em>world</em>productionized.aurora</h4>
-
-<p>Put the following in a file named <code>hello_world_productionized.aurora</code>, substituting your own values
-for values such as <code>cluster</code>s.</p>
-<pre class="highlight plaintext"><code>include('hello_world.aurora')
-
-production_resources = Resources(cpu = 1.0, ram = 512 * MB, disk = 2 * GB)
-staging_resources = Resources(cpu = 0.1, ram = 32 * MB, disk = 512 * MB)
-hello_world_template = hello_world(
- name = "hello_world-{{cluster}}"
- task = hello_world(resources=production_resources))
-
-jobs = [
- # production jobs
- hello_world_template(cluster = 'cluster1', instances = 25),
- hello_world_template(cluster = 'cluster2', instances = 15),
-
- # staging jobs
- hello_world_template(
- cluster = 'local',
- instances = 1,
- task = hello_world(resources=staging_resources)),
-]
-</code></pre>
-
-<p>Then issue the following commands to create and kill the job, using your own values for the job key</p>
-<pre class="highlight plaintext"><code>aurora job create cluster1/$USER/test/hello_world-cluster1 hello_world_productionized.aurora
-
-aurora job kill cluster1/$USER/test/hello_world-cluster1
-</code></pre>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/configuration-tutorial/configuration-tutorial20191213-22326-h4oaaw b/content/documentation/0.10.0/configuration-tutorial
similarity index 100%
rename from content/documentation/0.10.0/configuration-tutorial/configuration-tutorial20191213-22326-h4oaaw
rename to content/documentation/0.10.0/configuration-tutorial
diff --git a/content/documentation/0.10.0/configuration-tutorial/index.html b/content/documentation/0.10.0/configuration-tutorial/index.html
deleted file mode 100644
index 32b9e73..0000000
--- a/content/documentation/0.10.0/configuration-tutorial/index.html
+++ /dev/null
@@ -1,1139 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/configuration-tutorial/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="aurora-configuration-tutorial">Aurora Configuration Tutorial</h1>
-
-<p>How to write Aurora configuration files, including feature descriptions
-and best practices. When writing a configuration file, make use of
-<code>aurora job inspect</code>. It takes the same job key and configuration file
-arguments as <code>aurora job create</code> or <code>aurora job update</code>. It first ensures the
-configuration parses, then outputs it in human-readable form.</p>
-
-<p>You should read this after going through the general <a href="/documentation/0.10.0/tutorial/">Aurora Tutorial</a>.</p>
-
-<ul>
-<li><a href="#aurora-configuration-tutorial">Aurora Configuration Tutorial</a>
-
-<ul>
-<li><a href="#the-basics">The Basics</a>
-
-<ul>
-<li><a href="#use-bottom-to-top-object-ordering">Use Bottom-To-Top Object Ordering</a></li>
-</ul></li>
-<li><a href="#an-example-configuration-file">An Example Configuration File</a></li>
-<li><a href="#defining-process-objects">Defining Process Objects</a></li>
-<li><a href="#getting-your-code-into-the-sandbox">Getting Your Code Into The Sandbox</a></li>
-<li><a href="#defining-task-objects">Defining Task Objects</a>
-
-<ul>
-<li><a href="#sequentialtask-running-processes-in-parallel-or-sequentially">SequentialTask: Running Processes in Parallel or Sequentially</a></li>
-<li><a href="#simpletask">SimpleTask</a></li>
-<li><a href="#combining-tasks">Combining tasks</a></li>
-</ul></li>
-<li><a href="#defining-job-objects">Defining Job Objects</a></li>
-<li><a href="#the-jobs-list">The jobs List</a></li>
-<li><a href="#templating">Templating</a>
-
-<ul>
-<li><a href="#templating-1-binding-in-pystachio">Templating 1: Binding in Pystachio</a></li>
-<li><a href="#structurals-in-pystachio--aurora">Structurals in Pystachio / Aurora</a>
-
-<ul>
-<li><a href="#mustaches-within-structurals">Mustaches Within Structurals</a></li>
-</ul></li>
-<li><a href="#templating-2-structurals-are-factories">Templating 2: Structurals Are Factories</a>
-
-<ul>
-<li><a href="#a-second-way-of-templating">A Second Way of Templating</a></li>
-</ul></li>
-<li><a href="#advanced-binding">Advanced Binding</a>
-
-<ul>
-<li><a href="#bind-syntax">Bind Syntax</a></li>
-<li><a href="#binding-complex-objects">Binding Complex Objects</a>
-
-<ul>
-<li><a href="#lists"></a></li>
-<li><a href="#maps"></a></li>
-<li><a href="#structurals"></a></li>
-</ul></li>
-</ul></li>
-<li><a href="#structural-binding">Structural Binding</a></li>
-</ul></li>
-<li><a href="#configuration-file-writing-tips-and-best-practices">Configuration File Writing Tips And Best Practices</a>
-
-<ul>
-<li><a href="#use-as-few-aurora-files-as-possible">Use As Few .aurora Files As Possible</a></li>
-<li><a href="#avoid-boilerplate">Avoid Boilerplate</a></li>
-<li><a href="#thermos-uses-bash-but-thermos-is-not-bash">Thermos Uses bash, But Thermos Is Not bash</a>
-
-<ul>
-<li><a href="#bad">Bad</a></li>
-<li><a href="#good">Good</a></li>
-</ul></li>
-<li><a href="#rarely-use-functions-in-your-configurations">Rarely Use Functions In Your Configurations</a>
-
-<ul>
-<li><a href="#bad-1">Bad</a></li>
-<li><a href="#good-1">Good</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
-
-<h2 id="the-basics">The Basics</h2>
-
-<p>To run a job on Aurora, you must specify a configuration file that tells
-Aurora what it needs to know to schedule the job, what Mesos needs to
-run the tasks the job is made up of, and what Thermos needs to run the
-processes that make up the tasks. This file must have
-a<code>.aurora</code> suffix.</p>
-
-<p>A configuration file defines a collection of objects, along with parameter
-values for their attributes. An Aurora configuration file contains the
-following three types of objects:</p>
-
-<ul>
-<li>Job</li>
-<li>Task</li>
-<li>Process</li>
-</ul>
-
-<p>A configuration also specifies a list of <code>Job</code> objects assigned
-to the variable <code>jobs</code>.</p>
-
-<ul>
-<li>jobs (list of defined Jobs to run)</li>
-</ul>
-
-<p>The <code>.aurora</code> file format is just Python. However, <code>Job</code>, <code>Task</code>,
-<code>Process</code>, and other classes are defined by a type-checked dictionary
-templating library called <em>Pystachio</em>, a powerful tool for
-configuration specification and reuse. Pystachio objects are tailored
-via {{}} surrounded templates.</p>
-
-<p>When writing your <code>.aurora</code> file, you may use any Pystachio datatypes, as
-well as any objects shown in the <a href="/documentation/0.10.0/configuration-reference/"><em>Aurora+Thermos Configuration
-Reference</em></a>, without <code>import</code> statements - the
-Aurora config loader injects them automatically. Other than that, an <code>.aurora</code>
-file works like any other Python script.</p>
-
-<p><a href="/documentation/0.10.0/configuration-reference/"><em>Aurora+Thermos Configuration Reference</em></a>
-has a full reference of all Aurora/Thermos defined Pystachio objects.</p>
-
-<h3 id="use-bottom-to-top-object-ordering">Use Bottom-To-Top Object Ordering</h3>
-
-<p>A well-structured configuration starts with structural templates (if
-any). Structural templates encapsulate in their attributes all the
-differences between Jobs in the configuration that are not directly
-manipulated at the <code>Job</code> level, but typically at the <code>Process</code> or <code>Task</code>
-level. For example, if certain processes are invoked with slightly
-different settings or input.</p>
-
-<p>After structural templates, define, in order, <code>Process</code>es, <code>Task</code>s, and
-<code>Job</code>s.</p>
-
-<p>Structural template names should be <em>UpperCamelCased</em> and their
-instantiations are typically <em>UPPER_SNAKE_CASED</em>. <code>Process</code>, <code>Task</code>,
-and <code>Job</code> names are typically <em>lower_snake_cased</em>. Indentation is typically 2
-spaces.</p>
-
-<h2 id="an-example-configuration-file">An Example Configuration File</h2>
-
-<p>The following is a typical configuration file. Don’t worry if there are
-parts you don’t understand yet, but you may want to refer back to this
-as you read about its individual parts. Note that names surrounded by
-curly braces {{}} are template variables, which the system replaces with
-bound values for the variables.</p>
-<pre class="highlight plaintext"><code># --- templates here ---
-class Profile(Struct):
- package_version = Default(String, 'live')
- java_binary = Default(String, '/usr/lib/jvm/java-1.7.0-openjdk/bin/java')
- extra_jvm_options = Default(String, '')
- parent_environment = Default(String, 'prod')
- parent_serverset = Default(String,
- '/foocorp/service/bird/{{parent_environment}}/bird')
-
-# --- processes here ---
-main = Process(
- name = 'application',
- cmdline = '{{profile.java_binary}} -server -Xmx1792m '
- '{{profile.extra_jvm_options}} '
- '-jar application.jar '
- '-upstreamService {{profile.parent_serverset}}'
-)
-
-# --- tasks ---
-base_task = SequentialTask(
- name = 'application',
- processes = [
- Process(
- name = 'fetch',
- cmdline = 'curl -O
- https://packages.foocorp.com/{{profile.package_version}}/application.jar'),
- ]
-)
-
- # not always necessary but often useful to have separate task
- # resource classes
- staging_task = base_task(resources =
- Resources(cpu = 1.0,
- ram = 2048*MB,
- disk = 1*GB))
-production_task = base_task(resources =
- Resources(cpu = 4.0,
- ram = 2560*MB,
- disk = 10*GB))
-
-# --- job template ---
-job_template = Job(
- name = 'application',
- role = 'myteam',
- contact = 'myteam-team@foocorp.com',
- instances = 20,
- service = True,
- task = production_task
-)
-
-# -- profile instantiations (if any) ---
-PRODUCTION = Profile()
-STAGING = Profile(
- extra_jvm_options = '-Xloggc:gc.log',
- parent_environment = 'staging'
-)
-
-# -- job instantiations --
-jobs = [
- job_template(cluster = 'cluster1', environment = 'prod')
- .bind(profile = PRODUCTION),
-
- job_template(cluster = 'cluster2', environment = 'prod')
- .bind(profile = PRODUCTION),
-
- job_template(cluster = 'cluster1',
- environment = 'staging',
- service = False,
- task = staging_task,
- instances = 2)
- .bind(profile = STAGING),
-]
-</code></pre>
-
-<h2 id="defining-process-objects">Defining Process Objects</h2>
-
-<p>Processes are handled by the Thermos system. A process is a single
-executable step run as a part of an Aurora task, which consists of a
-bash-executable statement.</p>
-
-<p>The key (and required) <code>Process</code> attributes are:</p>
-
-<ul>
-<li> <code>name</code>: Any string which is a valid Unix filename (no slashes,
-NULLs, or leading periods). The <code>name</code> value must be unique relative
-to other Processes in a <code>Task</code>.</li>
-<li> <code>cmdline</code>: A command line run in a bash subshell, so you can use
-bash scripts. Nothing is supplied for command-line arguments,
-so <code>$*</code> is unspecified.</li>
-</ul>
-
-<p>Many tiny processes make managing configurations more difficult. For
-example, the following is a bad way to define processes.</p>
-<pre class="highlight plaintext"><code>copy = Process(
- name = 'copy',
- cmdline = 'curl -O https://packages.foocorp.com/app.zip'
-)
-unpack = Process(
- name = 'unpack',
- cmdline = 'unzip app.zip'
-)
-remove = Process(
- name = 'remove',
- cmdline = 'rm -f app.zip'
-)
-run = Process(
- name = 'app',
- cmdline = 'java -jar app.jar'
-)
-run_task = Task(
- processes = [copy, unpack, remove, run],
- constraints = order(copy, unpack, remove, run)
-)
-</code></pre>
-
-<p>Since <code>cmdline</code> runs in a bash subshell, you can chain commands
-with <code>&&</code> or <code>||</code>.</p>
-
-<p>When defining a <code>Task</code> that is just a list of Processes run in a
-particular order, use <code>SequentialTask</code>, as described in the <a href="#Task"><em>Defining</em>
-<code>Task</code> <em>Objects</em></a> section. The following simplifies and combines the
-above multiple <code>Process</code> definitions into just two.</p>
-<pre class="highlight plaintext"><code>stage = Process(
- name = 'stage',
- cmdline = 'curl -O https://packages.foocorp.com/app.zip && '
- 'unzip app.zip && rm -f app.zip')
-
-run = Process(name = 'app', cmdline = 'java -jar app.jar')
-
-run_task = SequentialTask(processes = [stage, run])
-</code></pre>
-
-<p><code>Process</code> also has optional attributes to customize its behaviour. Details can be found in the <a href="/documentation/0.10.0/configuration-reference/#process-objects"><em>Aurora+Thermos Configuration Reference</em></a>.</p>
-
-<h2 id="getting-your-code-into-the-sandbox">Getting Your Code Into The Sandbox</h2>
-
-<p>When using Aurora, you need to get your executable code into its “sandbox”, specifically
-the Task sandbox where the code executes for the Processes that make up that Task.</p>
-
-<p>Each Task has a sandbox created when the Task starts and garbage
-collected when it finishes. All of a Task’s processes run in its
-sandbox, so processes can share state by using a shared current
-working directory.</p>
-
-<p>Typically, you save this code somewhere. You then need to define a Process
-in your <code>.aurora</code> configuration file that fetches the code from that somewhere
-to where the slave can see it. For a public cloud, that can be anywhere public on
-the Internet, such as S3. For a private cloud internal storage, you need to put in
-on an accessible HDFS cluster or similar storage.</p>
-
-<p>The template for this Process is:</p>
-<pre class="highlight plaintext"><code><name> = Process(
- name = '<name>'
- cmdline = '<command to copy and extract code archive into current working directory>'
-)
-</code></pre>
-
-<p>Note: Be sure the extracted code archive has an executable.</p>
-
-<h2 id="defining-task-objects">Defining Task Objects</h2>
-
-<p>Tasks are handled by Mesos. A task is a collection of processes that
-runs in a shared sandbox. It’s the fundamental unit Aurora uses to
-schedule the datacenter; essentially what Aurora does is find places
-in the cluster to run tasks.</p>
-
-<p>The key (and required) parts of a Task are:</p>
-
-<ul>
-<li><p><code>name</code>: A string giving the Task’s name. By default, if a Task is
-not given a name, it inherits the first name in its Process list.</p></li>
-<li><p><code>processes</code>: An unordered list of Process objects bound to the Task.
-The value of the optional <code>constraints</code> attribute affects the
-contents as a whole. Currently, the only constraint, <code>order</code>, determines if
-the processes run in parallel or sequentially.</p></li>
-<li><p><code>resources</code>: A <code>Resource</code> object defining the Task’s resource
- footprint. A <code>Resource</code> object has three attributes:
- - <code>cpu</code>: A Float, the fractional number of cores the Task
- requires.
- - <code>ram</code>: An Integer, RAM bytes the Task requires.
- - <code>disk</code>: An integer, disk bytes the Task requires.</p></li>
-</ul>
-
-<p>A basic Task definition looks like:</p>
-<pre class="highlight plaintext"><code>Task(
- name="hello_world",
- processes=[Process(name = "hello_world", cmdline = "echo hello world")],
- resources=Resources(cpu = 1.0,
- ram = 1*GB,
- disk = 1*GB))
-</code></pre>
-
-<p>A Task has optional attributes to customize its behaviour. Details can be found in the <a href="/documentation/0.10.0/configuration-reference/#task-object"><em>Aurora+Thermos Configuration Reference</em></a></p>
-
-<h3 id="sequentialtask-running-processes-in-parallel-or-sequentially">SequentialTask: Running Processes in Parallel or Sequentially</h3>
-
-<p>By default, a Task with several Processes runs them in parallel. There
-are two ways to run Processes sequentially:</p>
-
-<ul>
-<li><p>Include an <code>order</code> constraint in the Task definition’s <code>constraints</code>
-attribute whose arguments specify the processes’ run order:</p>
-<pre class="highlight plaintext"><code>Task( ... processes=[process1, process2, process3],
- constraints = order(process1, process2, process3), ...)
-</code></pre></li>
-<li><p>Use <code>SequentialTask</code> instead of <code>Task</code>; it automatically runs
-processes in the order specified in the <code>processes</code> attribute. No
-<code>constraint</code> parameter is needed:</p>
-<pre class="highlight plaintext"><code>SequentialTask( ... processes=[process1, process2, process3] ...)
-</code></pre></li>
-</ul>
-
-<h3 id="simpletask">SimpleTask</h3>
-
-<p>For quickly creating simple tasks, use the <code>SimpleTask</code> helper. It
-creates a basic task from a provided name and command line using a
-default set of resources. For example, in a .<code>aurora</code> configuration
-file:</p>
-<pre class="highlight plaintext"><code>SimpleTask(name="hello_world", command="echo hello world")
-</code></pre>
-
-<p>is equivalent to</p>
-<pre class="highlight plaintext"><code>Task(name="hello_world",
- processes=[Process(name = "hello_world", cmdline = "echo hello world")],
- resources=Resources(cpu = 1.0,
- ram = 1*GB,
- disk = 1*GB))
-</code></pre>
-
-<p>The simplest idiomatic Job configuration thus becomes:</p>
-<pre class="highlight plaintext"><code>import os
-hello_world_job = Job(
- task=SimpleTask(name="hello_world", command="echo hello world"),
- role=os.getenv('USER'),
- cluster="cluster1")
-</code></pre>
-
-<p>When written to <code>hello_world.aurora</code>, you invoke it with a simple
-<code>aurora job create cluster1/$USER/test/hello_world hello_world.aurora</code>.</p>
-
-<h3 id="combining-tasks">Combining tasks</h3>
-
-<p><code>Tasks.concat</code>(synonym,<code>concat_tasks</code>) and
-<code>Tasks.combine</code>(synonym,<code>combine_tasks</code>) merge multiple Task definitions
-into a single Task. It may be easier to define complex Jobs
-as smaller constituent Tasks. But since a Job only includes a single
-Task, the subtasks must be combined before using them in a Job.
-Smaller Tasks can also be reused between Jobs, instead of having to
-repeat their definition for multiple Jobs.</p>
-
-<p>With both methods, the merged Task takes the first Task’s name. The
-difference between the two is the result Task’s process ordering.</p>
-
-<ul>
-<li><p><code>Tasks.combine</code> runs its subtasks’ processes in no particular order.
-The new Task’s resource consumption is the sum of all its subtasks’
-consumption.</p></li>
-<li><p><code>Tasks.concat</code> runs its subtasks in the order supplied, with each
-subtask’s processes run serially between tasks. It is analogous to
-the <code>order</code> constraint helper, except at the Task level instead of
-the Process level. The new Task’s resource consumption is the
-maximum value specified by any subtask for each Resource attribute
-(cpu, ram and disk).</p></li>
-</ul>
-
-<p>For example, given the following:</p>
-<pre class="highlight plaintext"><code>setup_task = Task(
- ...
- processes=[download_interpreter, update_zookeeper],
- # It is important to note that {{Tasks.concat}} has
- # no effect on the ordering of the processes within a task;
- # hence the necessity of the {{order}} statement below
- # (otherwise, the order in which {{download_interpreter}}
- # and {{update_zookeeper}} run will be non-deterministic)
- constraints=order(download_interpreter, update_zookeeper),
- ...
-)
-
-run_task = SequentialTask(
- ...
- processes=[download_application, start_application],
- ...
-)
-
-combined_task = Tasks.concat(setup_task, run_task)
-</code></pre>
-
-<p>The <code>Tasks.concat</code> command merges the two Tasks into a single Task and
-ensures all processes in <code>setup_task</code> run before the processes
-in <code>run_task</code>. Conceptually, the task is reduced to:</p>
-<pre class="highlight plaintext"><code>task = Task(
- ...
- processes=[download_interpreter, update_zookeeper,
- download_application, start_application],
- constraints=order(download_interpreter, update_zookeeper,
- download_application, start_application),
- ...
-)
-</code></pre>
-
-<p>In the case of <code>Tasks.combine</code>, the two schedules run in parallel:</p>
-<pre class="highlight plaintext"><code>task = Task(
- ...
- processes=[download_interpreter, update_zookeeper,
- download_application, start_application],
- constraints=order(download_interpreter, update_zookeeper) +
- order(download_application, start_application),
- ...
-)
-</code></pre>
-
-<p>In the latter case, each of the two sequences may operate in parallel.
-Of course, this may not be the intended behavior (for example, if
-the <code>start_application</code> Process implicitly relies
-upon <code>download_interpreter</code>). Make sure you understand the difference
-between using one or the other.</p>
-
-<h2 id="defining-job-objects">Defining Job Objects</h2>
-
-<p>A job is a group of identical tasks that Aurora can run in a Mesos cluster.</p>
-
-<p>A <code>Job</code> object is defined by the values of several attributes, some
-required and some optional. The required attributes are:</p>
-
-<ul>
-<li><p><code>task</code>: Task object to bind to this job. Note that a Job can
-only take a single Task.</p></li>
-<li><p><code>role</code>: Job’s role account; in other words, the user account to run
-the job as on a Mesos cluster machine. A common value is
-<code>os.getenv('USER')</code>; using a Python command to get the user who
-submits the job request. The other common value is the service
-account that runs the job, e.g. <code>www-data</code>.</p></li>
-<li><p><code>environment</code>: Job’s environment, typical values
-are <code>devel</code>, <code>test</code>, or <code>prod</code>.</p></li>
-<li><p><code>cluster</code>: Aurora cluster to schedule the job in, defined in
-<code>/etc/aurora/clusters.json</code> or <code>~/.clusters.json</code>. You can specify
-jobs where the only difference is the <code>cluster</code>, then at run time
-only run the Job whose job key includes your desired cluster’s name.</p></li>
-</ul>
-
-<p>You usually see a <code>name</code> parameter. By default, <code>name</code> inherits its
-value from the Job’s associated Task object, but you can override this
-default. For these four parameters, a Job definition might look like:</p>
-<pre class="highlight plaintext"><code>foo_job = Job( name = 'foo', cluster = 'cluster1',
- role = os.getenv('USER'), environment = 'prod',
- task = foo_task)
-</code></pre>
-
-<p>In addition to the required attributes, there are several optional
-attributes. Details can be found in the <a href="/documentation/0.10.0/configuration-reference/#job-objects">Aurora+Thermos Configuration Reference</a>.</p>
-
-<h2 id="the-jobs-list">The jobs List</h2>
-
-<p>At the end of your <code>.aurora</code> file, you need to specify a list of the
-file’s defined Jobs to run in the order listed. For example, the
-following runs first <code>job1</code>, then <code>job2</code>, then <code>job3</code>.</p>
-
-<p>jobs = [job1, job2, job3]</p>
-
-<h2 id="templating">Templating</h2>
-
-<p>The <code>.aurora</code> file format is just Python. However, <code>Job</code>, <code>Task</code>,
-<code>Process</code>, and other classes are defined by a templating library called
-<em>Pystachio</em>, a powerful tool for configuration specification and reuse.</p>
-
-<p><a href="/documentation/0.10.0/configuration-reference/">Aurora+Thermos Configuration Reference</a>
-has a full reference of all Aurora/Thermos defined Pystachio objects.</p>
-
-<p>When writing your <code>.aurora</code> file, you may use any Pystachio datatypes, as
-well as any objects shown in the <em>Aurora+Thermos Configuration
-Reference</em> without <code>import</code> statements - the Aurora config loader
-injects them automatically. Other than that the <code>.aurora</code> format
-works like any other Python script.</p>
-
-<h3 id="templating-1-binding-in-pystachio">Templating 1: Binding in Pystachio</h3>
-
-<p>Pystachio uses the visually distinctive {{}} to indicate template
-variables. These are often called “mustache variables” after the
-similarly appearing variables in the Mustache templating system and
-because the curly braces resemble mustaches.</p>
-
-<p>If you are familiar with the Mustache system, templates in Pystachio
-have significant differences. They have no nesting, joining, or
-inheritance semantics. On the other hand, when evaluated, templates
-are evaluated iteratively, so this affords some level of indirection.</p>
-
-<p>Let’s start with the simplest template; text with one
-variable, in this case <code>name</code>;</p>
-<pre class="highlight plaintext"><code>Hello {{name}}
-</code></pre>
-
-<p>If we evaluate this as is, we’d get back:</p>
-<pre class="highlight plaintext"><code>Hello
-</code></pre>
-
-<p>If a template variable doesn’t have a value, when evaluated it’s
-replaced with nothing. If we add a binding to give it a value:</p>
-<pre class="highlight json"><code><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"name"</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="color: #d14">"Tom"</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">}</span><span style="color: #bbbbbb">
-</span></code></pre>
-
-<p>We’d get back:</p>
-<pre class="highlight plaintext"><code>Hello Tom
-</code></pre>
-
-<p>Every Pystachio object has an associated <code>.bind</code> method that can bind
-values to {{}} variables. Bindings are not immediately evaluated.
-Instead, they are evaluated only when the interpolated value of the
-object is necessary, e.g. for performing equality or serializing a
-message over the wire.</p>
-
-<p>Objects with and without mustache templated variables behave
-differently:</p>
-<pre class="highlight plaintext"><code>>>> Float(1.5)
-Float(1.5)
-
->>> Float('{{x}}.5')
-Float({{x}}.5)
-
->>> Float('{{x}}.5').bind(x = 1)
-Float(1.5)
-
->>> Float('{{x}}.5').bind(x = 1) == Float(1.5)
-True
-
->>> contextual_object = String('{{metavar{{number}}}}').bind(
-... metavar1 = "first", metavar2 = "second")
-
->>> contextual_object
-String({{metavar{{number}}}})
-
->>> contextual_object.bind(number = 1)
-String(first)
-
->>> contextual_object.bind(number = 2)
-String(second)
-</code></pre>
-
-<p>You usually bind simple key to value pairs, but you can also bind three
-other objects: lists, dictionaries, and structurals. These will be
-described in detail later.</p>
-
-<h3 id="structurals-in-pystachio-aurora">Structurals in Pystachio / Aurora</h3>
-
-<p>Most Aurora/Thermos users don’t ever (knowingly) interact with <code>String</code>,
-<code>Float</code>, or <code>Integer</code> Pystashio objects directly. Instead they interact
-with derived structural (<code>Struct</code>) objects that are collections of
-fundamental and structural objects. The structural object components are
-called <em>attributes</em>. Aurora’s most used structural objects are <code>Job</code>,
-<code>Task</code>, and <code>Process</code>:</p>
-<pre class="highlight plaintext"><code>class Process(Struct):
- cmdline = Required(String)
- name = Required(String)
- max_failures = Default(Integer, 1)
- daemon = Default(Boolean, False)
- ephemeral = Default(Boolean, False)
- min_duration = Default(Integer, 5)
- final = Default(Boolean, False)
-</code></pre>
-
-<p>Construct default objects by following the object’s type with (). If you
-want an attribute to have a value different from its default, include
-the attribute name and value inside the parentheses.</p>
-<pre class="highlight plaintext"><code>>>> Process()
-Process(daemon=False, max_failures=1, ephemeral=False,
- min_duration=5, final=False)
-</code></pre>
-
-<p>Attribute values can be template variables, which then receive specific
-values when creating the object.</p>
-<pre class="highlight plaintext"><code>>>> Process(cmdline = 'echo {{message}}')
-Process(daemon=False, max_failures=1, ephemeral=False, min_duration=5,
- cmdline=echo {{message}}, final=False)
-
->>> Process(cmdline = 'echo {{message}}').bind(message = 'hello world')
-Process(daemon=False, max_failures=1, ephemeral=False, min_duration=5,
- cmdline=echo hello world, final=False)
-</code></pre>
-
-<p>A powerful binding property is that all of an object’s children inherit its
-bindings:</p>
-<pre class="highlight plaintext"><code>>>> List(Process)([
-... Process(name = '{{prefix}}_one'),
-... Process(name = '{{prefix}}_two')
-... ]).bind(prefix = 'hello')
-ProcessList(
- Process(daemon=False, name=hello_one, max_failures=1, ephemeral=False, min_duration=5, final=False),
- Process(daemon=False, name=hello_two, max_failures=1, ephemeral=False, min_duration=5, final=False)
- )
-</code></pre>
-
-<p>Remember that an Aurora Job contains Tasks which contain Processes. A
-Job level binding is inherited by its Tasks and all their Processes.
-Similarly a Task level binding is available to that Task and its
-Processes but is <em>not</em> visible at the Job level (inheritance is a
-one-way street.)</p>
-
-<h4 id="mustaches-within-structurals">Mustaches Within Structurals</h4>
-
-<p>When you define a <code>Struct</code> schema, one powerful, but confusing, feature
-is that all of that structure’s attributes are Mustache variables within
-the enclosing scope <em>once they have been populated</em>.</p>
-
-<p>For example, when <code>Process</code> is defined above, all its attributes such as
-{{<code>name</code>}}, {{<code>cmdline</code>}}, {{<code>max_failures</code>}} etc., are all immediately
-defined as Mustache variables, implicitly bound into the <code>Process</code>, and
-inherit all child objects once they are defined.</p>
-
-<p>Thus, you can do the following:</p>
-<pre class="highlight plaintext"><code>>>> Process(name = "installer", cmdline = "echo {{name}} is running")
-Process(daemon=False, name=installer, max_failures=1, ephemeral=False, min_duration=5,
- cmdline=echo installer is running, final=False)
-</code></pre>
-
-<p>WARNING: This binding only takes place in one direction. For example,
-the following does NOT work and does not set the <code>Process</code> <code>name</code>
-attribute’s value.</p>
-<pre class="highlight plaintext"><code>>>> Process().bind(name = "installer")
-Process(daemon=False, max_failures=1, ephemeral=False, min_duration=5, final=False)
-</code></pre>
-
-<p>The following is also not possible and results in an infinite loop that
-attempts to resolve <code>Process.name</code>.</p>
-<pre class="highlight plaintext"><code>>>> Process(name = '{{name}}').bind(name = 'installer')
-</code></pre>
-
-<p>Do not confuse Structural attributes with bound Mustache variables.
-Attributes are implicitly converted to Mustache variables but not vice
-versa.</p>
-
-<h3 id="templating-2-structurals-are-factories">Templating 2: Structurals Are Factories</h3>
-
-<h4 id="a-second-way-of-templating">A Second Way of Templating</h4>
-
-<p>A second templating method is both as powerful as the aforementioned and
-often confused with it. This method is due to automatic conversion of
-Struct attributes to Mustache variables as described above.</p>
-
-<p>Suppose you create a Process object:</p>
-<pre class="highlight plaintext"><code>>>> p = Process(name = "process_one", cmdline = "echo hello world")
-
->>> p
-Process(daemon=False, name=process_one, max_failures=1, ephemeral=False, min_duration=5,
- cmdline=echo hello world, final=False)
-</code></pre>
-
-<p>This <code>Process</code> object, “<code>p</code>”, can be used wherever a <code>Process</code> object is
-needed. It can also be reused by changing the value(s) of its
-attribute(s). Here we change its <code>name</code> attribute from <code>process_one</code> to
-<code>process_two</code>.</p>
-<pre class="highlight plaintext"><code>>>> p(name = "process_two")
-Process(daemon=False, name=process_two, max_failures=1, ephemeral=False, min_duration=5,
- cmdline=echo hello world, final=False)
-</code></pre>
-
-<p>Template creation is a common use for this technique:</p>
-<pre class="highlight plaintext"><code>>>> Daemon = Process(daemon = True)
->>> logrotate = Daemon(name = 'logrotate', cmdline = './logrotate conf/logrotate.conf')
->>> mysql = Daemon(name = 'mysql', cmdline = 'bin/mysqld --safe-mode')
-</code></pre>
-
-<h3 id="advanced-binding">Advanced Binding</h3>
-
-<p>As described above, <code>.bind()</code> binds simple strings or numbers to
-Mustache variables. In addition to Structural types formed by combining
-atomic types, Pystachio has two container types; <code>List</code> and <code>Map</code> which
-can also be bound via <code>.bind()</code>.</p>
-
-<h4 id="bind-syntax">Bind Syntax</h4>
-
-<p>The <code>bind()</code> function can take Python dictionaries or <code>kwargs</code>
-interchangeably (when “<code>kwargs</code>” is in a function definition, <code>kwargs</code>
-receives a Python dictionary containing all keyword arguments after the
-formal parameter list).</p>
-<pre class="highlight plaintext"><code>>>> String('{{foo}}').bind(foo = 'bar') == String('{{foo}}').bind({'foo': 'bar'})
-True
-</code></pre>
-
-<p>Bindings done “closer” to the object in question take precedence:</p>
-<pre class="highlight plaintext"><code>>>> p = Process(name = '{{context}}_process')
->>> t = Task().bind(context = 'global')
->>> t(processes = [p, p.bind(context = 'local')])
-Task(processes=ProcessList(
- Process(daemon=False, name=global_process, max_failures=1, ephemeral=False, final=False,
- min_duration=5),
- Process(daemon=False, name=local_process, max_failures=1, ephemeral=False, final=False,
- min_duration=5)
-))
-</code></pre>
-
-<h4 id="binding-complex-objects">Binding Complex Objects</h4>
-
-<h5 id="lists">Lists</h5>
-<pre class="highlight plaintext"><code>>>> fibonacci = List(Integer)([1, 1, 2, 3, 5, 8, 13])
->>> String('{{fib[4]}}').bind(fib = fibonacci)
-String(5)
-</code></pre>
-
-<h5 id="maps">Maps</h5>
-<pre class="highlight plaintext"><code>>>> first_names = Map(String, String)({'Kent': 'Clark', 'Wayne': 'Bruce', 'Prince': 'Diana'})
->>> String('{{first[Kent]}}').bind(first = first_names)
-String(Clark)
-</code></pre>
-
-<h5 id="structurals">Structurals</h5>
-<pre class="highlight plaintext"><code>>>> String('{{p.cmdline}}').bind(p = Process(cmdline = "echo hello world"))
-String(echo hello world)
-</code></pre>
-
-<h3 id="structural-binding">Structural Binding</h3>
-
-<p>Use structural templates when binding more than two or three individual
-values at the Job or Task level. For fewer than two or three, standard
-key to string binding is sufficient.</p>
-
-<p>Structural binding is a very powerful pattern and is most useful in
-Aurora/Thermos for doing Structural configuration. For example, you can
-define a job profile. The following profile uses <code>HDFS</code>, the Hadoop
-Distributed File System, to designate a file’s location. <code>HDFS</code> does
-not come with Aurora, so you’ll need to either install it separately
-or change the way the dataset is designated.</p>
-<pre class="highlight plaintext"><code>class Profile(Struct):
- version = Required(String)
- environment = Required(String)
- dataset = Default(String, hdfs://home/aurora/data/{{environment}}')
-
-PRODUCTION = Profile(version = 'live', environment = 'prod')
-DEVEL = Profile(version = 'latest',
- environment = 'devel',
- dataset = 'hdfs://home/aurora/data/test')
-TEST = Profile(version = 'latest', environment = 'test')
-
-JOB_TEMPLATE = Job(
- name = 'application',
- role = 'myteam',
- cluster = 'cluster1',
- environment = '{{profile.environment}}',
- task = SequentialTask(
- name = 'task',
- resources = Resources(cpu = 2, ram = 4*GB, disk = 8*GB),
- processes = [
- Process(name = 'main', cmdline = 'java -jar application.jar -hdfsPath
- {{profile.dataset}}')
- ]
- )
- )
-
-jobs = [
- JOB_TEMPLATE(instances = 100).bind(profile = PRODUCTION),
- JOB_TEMPLATE.bind(profile = DEVEL),
- JOB_TEMPLATE.bind(profile = TEST),
- ]
-</code></pre>
-
-<p>In this case, a custom structural “Profile” is created to self-document
-the configuration to some degree. This also allows some schema
-“type-checking”, and for default self-substitution, e.g. in
-<code>Profile.dataset</code> above.</p>
-
-<p>So rather than a <code>.bind()</code> with a half-dozen substituted variables, you
-can bind a single object that has sensible defaults stored in a single
-place.</p>
-
-<h2 id="configuration-file-writing-tips-and-best-practices">Configuration File Writing Tips And Best Practices</h2>
-
-<h3 id="use-as-few-aurora-files-as-possible">Use As Few .aurora Files As Possible</h3>
-
-<p>When creating your <code>.aurora</code> configuration, try to keep all versions of
-a particular job within the same <code>.aurora</code> file. For example, if you
-have separate jobs for <code>cluster1</code>, <code>cluster1</code> staging, <code>cluster1</code>
-testing, and<code>cluster2</code>, keep them as close together as possible.</p>
-
-<p>Constructs shared across multiple jobs owned by your team (e.g.
-team-level defaults or structural templates) can be split into separate
-<code>.aurora</code>files and included via the <code>include</code> directive.</p>
-
-<h3 id="avoid-boilerplate">Avoid Boilerplate</h3>
-
-<p>If you see repetition or find yourself copy and pasting any parts of
-your configuration, it’s likely an opportunity for templating. Take the
-example below:</p>
-
-<p><code>redundant.aurora</code> contains:</p>
-<pre class="highlight plaintext"><code>download = Process(
- name = 'download',
- cmdline = 'wget http://www.python.org/ftp/python/2.7.3/Python-2.7.3.tar.bz2',
- max_failures = 5,
- min_duration = 1)
-
-unpack = Process(
- name = 'unpack',
- cmdline = 'rm -rf Python-2.7.3 && tar xzf Python-2.7.3.tar.bz2',
- max_failures = 5,
- min_duration = 1)
-
-build = Process(
- name = 'build',
- cmdline = 'pushd Python-2.7.3 && ./configure && make && popd',
- max_failures = 1)
-
-email = Process(
- name = 'email',
- cmdline = 'echo Success | mail feynman@tmc.com',
- max_failures = 5,
- min_duration = 1)
-
-build_python = Task(
- name = 'build_python',
- processes = [download, unpack, build, email],
- constraints = [Constraint(order = ['download', 'unpack', 'build', 'email'])])
-</code></pre>
-
-<p>As you’ll notice, there’s a lot of repetition in the <code>Process</code>
-definitions. For example, almost every process sets a <code>max_failures</code>
-limit to 5 and a <code>min_duration</code> to 1. This is an opportunity for factoring
-into a common process template.</p>
-
-<p>Furthermore, the Python version is repeated everywhere. This can be
-bound via structural templating as described in the <a href="#AdvancedBinding">Advanced Binding</a>
-section.</p>
-
-<p><code>less_redundant.aurora</code> contains:</p>
-<pre class="highlight plaintext"><code>class Python(Struct):
- version = Required(String)
- base = Default(String, 'Python-{{version}}')
- package = Default(String, '{{base}}.tar.bz2')
-
-ReliableProcess = Process(
- max_failures = 5,
- min_duration = 1)
-
-download = ReliableProcess(
- name = 'download',
- cmdline = 'wget http://www.python.org/ftp/python/{{python.version}}/{{python.package}}')
-
-unpack = ReliableProcess(
- name = 'unpack',
- cmdline = 'rm -rf {{python.base}} && tar xzf {{python.package}}')
-
-build = ReliableProcess(
- name = 'build',
- cmdline = 'pushd {{python.base}} && ./configure && make && popd',
- max_failures = 1)
-
-email = ReliableProcess(
- name = 'email',
- cmdline = 'echo Success | mail {{role}}@foocorp.com')
-
-build_python = SequentialTask(
- name = 'build_python',
- processes = [download, unpack, build, email]).bind(python = Python(version = "2.7.3"))
-</code></pre>
-
-<h3 id="thermos-uses-bash-but-thermos-is-not-bash">Thermos Uses bash, But Thermos Is Not bash</h3>
-
-<h4 id="bad">Bad</h4>
-
-<p>Many tiny Processes makes for harder to manage configurations.</p>
-<pre class="highlight plaintext"><code>copy = Process(
- name = 'copy',
- cmdline = 'rcp user@my_machine:my_application .'
- )
-
- unpack = Process(
- name = 'unpack',
- cmdline = 'unzip app.zip'
- )
-
- remove = Process(
- name = 'remove',
- cmdline = 'rm -f app.zip'
- )
-
- run = Process(
- name = 'app',
- cmdline = 'java -jar app.jar'
- )
-
- run_task = Task(
- processes = [copy, unpack, remove, run],
- constraints = order(copy, unpack, remove, run)
- )
-</code></pre>
-
-<h4 id="good">Good</h4>
-
-<p>Each <code>cmdline</code> runs in a bash subshell, so you have the full power of
-bash. Chaining commands with <code>&&</code> or <code>||</code> is almost always the right
-thing to do.</p>
-
-<p>Also for Tasks that are simply a list of processes that run one after
-another, consider using the <code>SequentialTask</code> helper which applies a
-linear ordering constraint for you.</p>
-<pre class="highlight plaintext"><code>stage = Process(
- name = 'stage',
- cmdline = 'rcp user@my_machine:my_application . && unzip app.zip && rm -f app.zip')
-
-run = Process(name = 'app', cmdline = 'java -jar app.jar')
-
-run_task = SequentialTask(processes = [stage, run])
-</code></pre>
-
-<h3 id="rarely-use-functions-in-your-configurations">Rarely Use Functions In Your Configurations</h3>
-
-<p>90% of the time you define a function in a <code>.aurora</code> file, you’re
-probably Doing It Wrong™.</p>
-
-<h4 id="bad">Bad</h4>
-<pre class="highlight plaintext"><code>def get_my_task(name, user, cpu, ram, disk):
- return Task(
- name = name,
- user = user,
- processes = [STAGE_PROCESS, RUN_PROCESS],
- constraints = order(STAGE_PROCESS, RUN_PROCESS),
- resources = Resources(cpu = cpu, ram = ram, disk = disk)
- )
-
- task_one = get_my_task('task_one', 'feynman', 1.0, 32*MB, 1*GB)
- task_two = get_my_task('task_two', 'feynman', 2.0, 64*MB, 1*GB)
-</code></pre>
-
-<h4 id="good">Good</h4>
-
-<p>This one is more idiomatic. Forced keyword arguments prevents accidents,
-e.g. constructing a task with “32*MB” when you mean 32MB of ram and not
-disk. Less proliferation of task-construction techniques means
-easier-to-read, quicker-to-understand, and a more composable
-configuration.</p>
-<pre class="highlight plaintext"><code>TASK_TEMPLATE = SequentialTask(
- user = 'wickman',
- processes = [STAGE_PROCESS, RUN_PROCESS],
-)
-
-task_one = TASK_TEMPLATE(
- name = 'task_one',
- resources = Resources(cpu = 1.0, ram = 32*MB, disk = 1*GB) )
-
-task_two = TASK_TEMPLATE(
- name = 'task_two',
- resources = Resources(cpu = 2.0, ram = 64*MB, disk = 1*GB)
-)
-</code></pre>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/contributing/contributing20191213-22326-14dul7n b/content/documentation/0.10.0/contributing
similarity index 100%
rename from content/documentation/0.10.0/contributing/contributing20191213-22326-14dul7n
rename to content/documentation/0.10.0/contributing
diff --git a/content/documentation/0.10.0/contributing/index.html b/content/documentation/0.10.0/contributing/index.html
deleted file mode 100644
index 190d01b..0000000
--- a/content/documentation/0.10.0/contributing/index.html
+++ /dev/null
@@ -1,240 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/contributing/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h2 id="get-the-source-code">Get the Source Code</h2>
-
-<p>First things first, you’ll need the source! The Aurora source is available from Apache git:</p>
-<pre class="highlight plaintext"><code>git clone https://gitbox.apache.org/repos/asf/aurora
-</code></pre>
-
-<h2 id="read-the-style-guides">Read the Style Guides</h2>
-
-<p>Aurora’s codebase is primarily Java and Python and conforms to the Twitter Commons styleguides for
-both languages.</p>
-
-<ul>
-<li><a href="https://github.com/twitter/commons/blob/master/src/java/com/twitter/common/styleguide.md">Java Style Guide</a></li>
-<li><a href="https://github.com/twitter/commons/blob/master/src/python/twitter/common/styleguide.md">Python Style Guide</a></li>
-</ul>
-
-<h2 id="find-something-to-do">Find Something to Do</h2>
-
-<p>There are issues in <a href="https://issues.apache.org/jira/browse/AURORA">Jira</a> with the
-<a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20AURORA%20AND%20labels%20%3D%20newbie%20and%20resolution%3Dunresolved">“newbie” label</a>
-that are good starting places for new Aurora contributors; pick one of these and dive in! Once
-you’ve got a patch, the next step is to post a review.</p>
-
-<h2 id="getting-your-reviewboard-account">Getting your ReviewBoard Account</h2>
-
-<p>Go to <a href="https://reviews.apache.org">https://reviews.apache.org</a> and create an account.</p>
-
-<h2 id="setting-up-your-reviewboard-environment">Setting up your ReviewBoard Environment</h2>
-
-<p>Run <code>./rbt status</code>. The first time this runs it will bootstrap and you will be asked to login.
-Subsequent runs will cache your login credentials.</p>
-
-<h2 id="submitting-a-patch-for-review">Submitting a Patch for Review</h2>
-
-<p>Post a review with <code>rbt</code>, fill out the fields in your browser and hit Publish.</p>
-<pre class="highlight plaintext"><code>./rbt post -o
-</code></pre>
-
-<p>If you’re unsure about who to add as a reviewer, you can default to adding Bill Farner (wfarner) and
-Joshua Cohen (jcohen). They will take care of finding an appropriate reviewer for the patch.</p>
-
-<p>Once you’ve done this, you probably want to mark the associated Jira issue as Reviewable.</p>
-
-<h2 id="updating-an-existing-review">Updating an Existing Review</h2>
-
-<p>Incorporate review feedback, make some more commits, update your existing review, fill out the
-fields in your browser and hit Publish.</p>
-<pre class="highlight plaintext"><code>./rbt post -o -r <RB_ID>
-</code></pre>
-
-<h2 id="getting-your-review-merged">Getting Your Review Merged</h2>
-
-<p>If you’re not an Aurora committer, one of the committers will merge your change in as described
-below. Generally, the last reviewer to give the review a ‘Ship It!’ will be responsible.</p>
-
-<h3 id="merging-your-own-review-committers">Merging Your Own Review (Committers)</h3>
-
-<p>Once you have shipits from the right committers, merge your changes in a single commit and mark
-the review as submitted. The typical workflow is:</p>
-<pre class="highlight plaintext"><code>git checkout master
-git pull origin master
-./rbt patch -c <RB_ID> # Verify the automatically-generated commit message looks sane,
- # editing if necessary.
-git show master # Verify everything looks sane
-git push origin master
-./rbt close <RB_ID>
-</code></pre>
-
-<p>Note that even if you’re developing using feature branches you will not use <code>git merge</code> - each
-commit will be an atomic change accompanied by a ReviewBoard entry.</p>
-
-<h3 id="merging-someone-else-39-s-review">Merging Someone Else’s Review</h3>
-
-<p>Sometimes you’ll need to merge someone else’s RB. The typical workflow for this is</p>
-<pre class="highlight plaintext"><code>git checkout master
-git pull origin master
-./rbt patch -c <RB_ID>
-git show master # Verify everything looks sane, author is correct
-git push origin master
-</code></pre>
-
-<h2 id="cleaning-up">Cleaning Up</h2>
-
-<p>Your patch has landed, congratulations! The last thing you’ll want to do before moving on to your
-next fix is to clean up your Jira and Reviewboard. The former of which should be marked as
-“Resolved” while the latter should be marked as “Submitted”.</p>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/cron-jobs/cron-jobs20191213-22326-1v30koc b/content/documentation/0.10.0/cron-jobs
similarity index 100%
rename from content/documentation/0.10.0/cron-jobs/cron-jobs20191213-22326-1v30koc
rename to content/documentation/0.10.0/cron-jobs
diff --git a/content/documentation/0.10.0/cron-jobs/index.html b/content/documentation/0.10.0/cron-jobs/index.html
deleted file mode 100644
index 729f4de..0000000
--- a/content/documentation/0.10.0/cron-jobs/index.html
+++ /dev/null
@@ -1,303 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/cron-jobs/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="cron-jobs">Cron Jobs</h1>
-
-<p>Aurora supports execution of scheduled jobs on a Mesos cluster using cron-style syntax.</p>
-
-<ul>
-<li><a href="#overview">Overview</a></li>
-<li><a href="#collision-policies">Collision Policies</a>
-
-<ul>
-<li><a href="#kill_existing">KILL_EXISTING</a></li>
-<li><a href="#cancel_new">CANCEL_NEW</a></li>
-</ul></li>
-<li><a href="#failure-recovery">Failure recovery</a></li>
-<li><a href="#interacting-with-cron-jobs-via-the-aurora-cli">Interacting with cron jobs via the Aurora CLI</a>
-
-<ul>
-<li><a href="#cron-schedule">cron schedule</a></li>
-<li><a href="#cron-deschedule">cron deschedule</a></li>
-<li><a href="#cron-start">cron start</a></li>
-<li><a href="#job-killall-job-restart-job-kill">job killall, job restart, job kill</a></li>
-</ul></li>
-<li><a href="#technical-note-about-syntax">Technical Note About Syntax</a></li>
-<li><a href="#caveats">Caveats</a>
-
-<ul>
-<li><a href="#failovers">Failovers</a></li>
-<li><a href="#collision-policy-is-best-effort">Collision policy is best-effort</a></li>
-<li><a href="#timezone-configuration">Timezone Configuration</a></li>
-</ul></li>
-</ul>
-
-<h2 id="overview">Overview</h2>
-
-<p>A job is identified as a cron job by the presence of a
-<code>cron_schedule</code> attribute containing a cron-style schedule in the
-<a href="/documentation/0.10.0/configuration-reference/#job-objects"><code>Job</code></a> object. Examples of cron schedules
-include “every 5 minutes” (<code>*/5 * * * *</code>), “Fridays at 17:00” (<code>* 17 * * FRI</code>), and
-“the 1st and 15th day of the month at 03:00” (<code>0 3 1,15 *</code>).</p>
-
-<p>Example (available in the <a href="/documentation/0.10.0/vagrant/">Vagrant environment</a>):</p>
-<pre class="highlight plaintext"><code>$ cat /vagrant/examples/job/cron_hello_world.aurora
-# cron_hello_world.aurora
-# A cron job that runs every 5 minutes.
-jobs = [
- Job(
- cluster = 'devcluster',
- role = 'www-data',
- environment = 'test',
- name = 'cron_hello_world',
- cron_schedule = '*/5 * * * *',
- task = SimpleTask(
- 'cron_hello_world',
- 'echo "Hello world from cron, the time is now $(date --rfc-822)"'),
- ),
-]
-</code></pre>
-
-<h2 id="collision-policies">Collision Policies</h2>
-
-<p>The <code>cron_collision_policy</code> field specifies the scheduler’s behavior when a new cron job is
-triggered while an older run hasn’t finished. The scheduler has two policies available,
-<a href="#kill_existing">KILL_EXISTING</a> and <a href="#cancel_new">CANCEL_NEW</a>.</p>
-
-<h3 id="kill_existing">KILL_EXISTING</h3>
-
-<p>The default policy - on a collision the old instances are killed and a instances with the current
-configuration are started.</p>
-
-<h3 id="cancel_new">CANCEL_NEW</h3>
-
-<p>On a collision the new run is cancelled.</p>
-
-<p>Note that the use of this flag is likely a code smell - interrupted cron jobs should be able
-to recover their progress on a subsequent invocation, otherwise they risk having their work queue
-grow faster than they can process it.</p>
-
-<h2 id="failure-recovery">Failure recovery</h2>
-
-<p>Unlike with services, which aurora will always re-execute regardless of exit status, instances of
-cron jobs retry according to the <code>max_task_failures</code> attribute of the
-<a href="/documentation/0.10.0/configuration-reference/#task-objects">Task</a> object. To get “run-until-success” semantics,
-set <code>max_task_failures</code> to <code>-1</code>.</p>
-
-<h2 id="interacting-with-cron-jobs-via-the-aurora-cli">Interacting with cron jobs via the Aurora CLI</h2>
-
-<p>Most interaction with cron jobs takes place using the <code>cron</code> subcommand. See <code>aurora cron -h</code>
-for up-to-date usage instructions.</p>
-
-<h3 id="cron-schedule">cron schedule</h3>
-
-<p>Schedules a new cron job on the Aurora cluster for later runs or replaces the existing cron template
-with a new one. Only future runs will be affected, any existing active tasks are left intact.</p>
-<pre class="highlight plaintext"><code>$ aurora cron schedule devcluster/www-data/test/cron_hello_world /vagrant/examples/jobs/cron_hello_world.aurora
-</code></pre>
-
-<h3 id="cron-deschedule">cron deschedule</h3>
-
-<p>Deschedules a cron job, preventing future runs but allowing current runs to complete.</p>
-<pre class="highlight plaintext"><code>$ aurora cron deschedule devcluster/www-data/test/cron_hello_world
-</code></pre>
-
-<h3 id="cron-start">cron start</h3>
-
-<p>Start a cron job immediately, outside of its normal cron schedule.</p>
-<pre class="highlight plaintext"><code>$ aurora cron start devcluster/www-data/test/cron_hello_world
-</code></pre>
-
-<h3 id="job-killall-job-restart-job-kill">job killall, job restart, job kill</h3>
-
-<p>Cron jobs create instances running on the cluster that you can interact with like normal Aurora
-tasks with <code>job kill</code> and <code>job restart</code>.</p>
-
-<h2 id="technical-note-about-syntax">Technical Note About Syntax</h2>
-
-<p><code>cron_schedule</code> uses a restricted subset of BSD crontab syntax. While the
-execution engine currently uses Quartz, the schedule parsing is custom, a subset of FreeBSD
-<a href="http://www.freebsd.org/cgi/man.cgi?crontab(5)">crontab(5)</a> syntax. See
-<a href="https://github.com/apache/aurora/blob/master/src/main/java/org/apache/aurora/scheduler/cron/CrontabEntry.java#L106-L124">the source</a>
-for details.</p>
-
-<h2 id="caveats">Caveats</h2>
-
-<h3 id="failovers">Failovers</h3>
-
-<p>No failover recovery. Aurora does not record the latest minute it fired
-triggers for across failovers. Therefore it’s possible to miss triggers
-on failover. Note that this behavior may change in the future.</p>
-
-<p>It’s necessary to sync time between schedulers with something like <code>ntpd</code>.
-Clock skew could cause double or missed triggers in the case of a failover.</p>
-
-<h3 id="collision-policy-is-best-effort">Collision policy is best-effort</h3>
-
-<p>Aurora aims to always have <em>at least one copy</em> of a given instance running at a time - it’s
-an AP system, meaning it chooses Availability and Partition Tolerance at the expense of
-Consistency.</p>
-
-<p>If your collision policy was <code>CANCEL_NEW</code> and a task has terminated but
-Aurora has not noticed this Aurora will go ahead and create your new
-task.</p>
-
-<p>If your collision policy was <code>KILL_EXISTING</code> and a task was marked <code>LOST</code>
-but not yet GCed Aurora will go ahead and create your new task without
-attempting to kill the old one (outside the GC interval).</p>
-
-<h3 id="timezone-configuration">Timezone Configuration</h3>
-
-<p>Cron timezone is configured indepdendently of JVM timezone with the <code>-cron_timezone</code> flag and
-defaults to UTC.</p>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/deploying-aurora-scheduler/deploying-aurora-scheduler20191213-22326-k828qq b/content/documentation/0.10.0/deploying-aurora-scheduler
similarity index 100%
rename from content/documentation/0.10.0/deploying-aurora-scheduler/deploying-aurora-scheduler20191213-22326-k828qq
rename to content/documentation/0.10.0/deploying-aurora-scheduler
diff --git a/content/documentation/0.10.0/deploying-aurora-scheduler/index.html b/content/documentation/0.10.0/deploying-aurora-scheduler/index.html
deleted file mode 100644
index c6c7065..0000000
--- a/content/documentation/0.10.0/deploying-aurora-scheduler/index.html
+++ /dev/null
@@ -1,544 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/deploying-aurora-scheduler/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="deploying-the-aurora-scheduler">Deploying the Aurora Scheduler</h1>
-
-<p>When setting up your cluster, you will install the scheduler on a small number (usually 3 or 5) of
-machines. This guide helps you get the scheduler set up and troubleshoot some common hurdles.</p>
-
-<ul>
-<li><a href="#installing-aurora">Installing Aurora</a>
-
-<ul>
-<li><a href="#creating-the-distribution-zip-file-optional">Creating the Distribution .zip File (Optional)</a></li>
-<li><a href="#installing-aurora-1">Installing Aurora</a></li>
-</ul></li>
-<li><a href="#configuring-aurora">Configuring Aurora</a>
-
-<ul>
-<li><a href="#a-note-on-configuration">A Note on Configuration</a></li>
-<li><a href="#replicated-log-configuration">Replicated Log Configuration</a></li>
-<li><a href="#initializing-the-replicated-log">Initializing the Replicated Log</a></li>
-<li><a href="#storage-performance-considerations">Storage Performance Considerations</a></li>
-<li><a href="#network-considerations">Network considerations</a></li>
-<li><a href="#considerations-for-running-jobs-in-docker">Considerations for running jobs in docker</a></li>
-<li><a href="#security-considerations">Security Considerations</a></li>
-<li><a href="#configuring-resource-oversubscription">Configuring Resource Oversubscription</a></li>
-</ul></li>
-<li><a href="#running-aurora">Running Aurora</a>
-
-<ul>
-<li><a href="#maintaining-an-aurora-installation">Maintaining an Aurora Installation</a></li>
-<li><a href="#monitoring">Monitoring</a></li>
-<li><a href="#running-stateful-services">Running stateful services</a></li>
-<li><a href="#dedicated-attribute">Dedicated attribute</a>
-
-<ul>
-<li><a href="#syntax">Syntax</a></li>
-<li><a href="#example">Example</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#best-practices">Best practices</a>
-
-<ul>
-<li><a href="#diversity">Diversity</a></li>
-</ul></li>
-<li><a href="#common-problems">Common problems</a>
-
-<ul>
-<li><a href="#replicated-log-not-initialized">Replicated log not initialized</a></li>
-<li><a href="#symptoms">Symptoms</a></li>
-<li><a href="#solution">Solution</a></li>
-<li><a href="#scheduler-not-registered">Scheduler not registered</a></li>
-<li><a href="#symptoms-1">Symptoms</a></li>
-<li><a href="#solution-1">Solution</a></li>
-</ul></li>
-<li><a href="#changing-scheduler-quorum-size">Changing Scheduler Quorum Size</a>
-
-<ul>
-<li><a href="#preparation">Preparation</a></li>
-<li><a href="#adding-new-schedulers">Adding New Schedulers</a></li>
-</ul></li>
-</ul>
-
-<h2 id="installing-aurora">Installing Aurora</h2>
-
-<p>The Aurora scheduler is a standalone Java server. As part of the build process it creates a bundle
-of all its dependencies, with the notable exceptions of the JVM and libmesos. Each target server
-should have a JVM (Java 7 or higher) and libmesos (0.23.0) installed.</p>
-
-<h3 id="creating-the-distribution-zip-file-optional">Creating the Distribution .zip File (Optional)</h3>
-
-<p>To create a distribution for installation you will need build tools installed. On Ubuntu this can be
-done with <code>sudo apt-get install build-essential default-jdk</code>.</p>
-<pre class="highlight plaintext"><code>git clone http://gitbox.apache.org/repos/asf/aurora.git
-cd aurora
-./gradlew distZip
-</code></pre>
-
-<p>Copy the generated <code>dist/distributions/aurora-scheduler-*.zip</code> to each node that will run a scheduler.</p>
-
-<h3 id="installing-aurora">Installing Aurora</h3>
-
-<p>Extract the aurora-scheduler zip file. The example configurations assume it is extracted to
-<code>/usr/local/aurora-scheduler</code>.</p>
-<pre class="highlight plaintext"><code>sudo unzip dist/distributions/aurora-scheduler-*.zip -d /usr/local
-sudo ln -nfs "$(ls -dt /usr/local/aurora-scheduler-* | head -1)" /usr/local/aurora-scheduler
-</code></pre>
-
-<h2 id="configuring-aurora">Configuring Aurora</h2>
-
-<h3 id="a-note-on-configuration">A Note on Configuration</h3>
-
-<p>Like Mesos, Aurora uses command-line flags for runtime configuration. As such the Aurora
-“configuration file” is typically a <code>scheduler.sh</code> shell script of the form.</p>
-<pre class="highlight shell"><code><span style="color: #999988;font-style: italic">#!/bin/bash</span>
-<span style="color: #008080">AURORA_HOME</span><span style="color: #000000;font-weight: bold">=</span>/usr/local/aurora-scheduler
-
-<span style="color: #999988;font-style: italic"># Flags controlling the JVM.</span>
-<span style="color: #008080">JAVA_OPTS</span><span style="color: #000000;font-weight: bold">=(</span>
- -Xmx2g
- -Xms2g
- <span style="color: #999988;font-style: italic"># GC tuning, etc.</span>
-<span style="color: #000000;font-weight: bold">)</span>
-
-<span style="color: #999988;font-style: italic"># Flags controlling the scheduler.</span>
-<span style="color: #008080">AURORA_FLAGS</span><span style="color: #000000;font-weight: bold">=(</span>
- -http_port<span style="color: #000000;font-weight: bold">=</span>8081
- <span style="color: #999988;font-style: italic"># Log configuration, etc.</span>
-<span style="color: #000000;font-weight: bold">)</span>
-
-<span style="color: #999988;font-style: italic"># Environment variables controlling libmesos</span>
-<span style="color: #0086B3">export </span><span style="color: #008080">JAVA_HOME</span><span style="color: #000000;font-weight: bold">=</span>...
-<span style="color: #0086B3">export </span><span style="color: #008080">GLOG_v</span><span style="color: #000000;font-weight: bold">=</span>1
-<span style="color: #0086B3">export </span><span style="color: #008080">LIBPROCESS_PORT</span><span style="color: #000000;font-weight: bold">=</span>8083
-
-<span style="color: #008080">JAVA_OPTS</span><span style="color: #000000;font-weight: bold">=</span><span style="color: #d14">"</span><span style="color: #000000;font-weight: bold">${</span><span style="color: #008080">JAVA_OPTS</span><span style="background-color: #f8f8f8">[*]</span><span style="color: #000000;font-weight: bold">}</span><span style="color: #d14">"</span> <span style="color: #0086B3">exec</span> <span style="color: #d14">"</span><span style="color: #008080">$AURORA_HOME< [...]
-</code></pre>
-
-<p>That way Aurora’s current flags are visible in <code>ps</code> and in the <code>/vars</code> admin endpoint.</p>
-
-<p>Examples are available under <code>examples/scheduler/</code>. For a list of available Aurora flags and their
-documentation run</p>
-<pre class="highlight plaintext"><code>/usr/local/aurora-scheduler/bin/aurora-scheduler -help
-</code></pre>
-
-<h3 id="replicated-log-configuration">Replicated Log Configuration</h3>
-
-<p>All Aurora state is persisted to a replicated log. This includes all jobs Aurora is running
-including where in the cluster they are being run and the configuration for running them, as
-well as other information such as metadata needed to reconnect to the Mesos master, resource
-quotas, and any other locks in place.</p>
-
-<p>Aurora schedulers use ZooKeeper to discover log replicas and elect a leader. Only one scheduler is
-leader at a given time - the other schedulers follow log writes and prepare to take over as leader
-but do not communicate with the Mesos master. Either 3 or 5 schedulers are recommended in a
-production deployment depending on failure tolerance and they must have persistent storage.</p>
-
-<p>In a cluster with <code>N</code> schedulers, the flag <code>-native_log_quorum_size</code> should be set to
-<code>floor(N/2) + 1</code>. So in a cluster with 1 scheduler it should be set to <code>1</code>, in a cluster with 3 it
-should be set to <code>2</code>, and in a cluster of 5 it should be set to <code>3</code>.</p>
-
-<table><thead>
-<tr>
-<th>Number of schedulers (N)</th>
-<th><code>-native_log_quorum_size</code> setting (<code>floor(N/2) + 1</code>)</th>
-</tr>
-</thead><tbody>
-<tr>
-<td>1</td>
-<td>1</td>
-</tr>
-<tr>
-<td>3</td>
-<td>2</td>
-</tr>
-<tr>
-<td>5</td>
-<td>3</td>
-</tr>
-<tr>
-<td>7</td>
-<td>4</td>
-</tr>
-</tbody></table>
-
-<p><em>Incorrectly setting this flag will cause data corruption to occur!</em></p>
-
-<p>See <a href="/documentation/0.10.0/storage-config/#scheduler-storage-configuration-flags">this document</a> for more replicated
-log and storage configuration options.</p>
-
-<h2 id="initializing-the-replicated-log">Initializing the Replicated Log</h2>
-
-<p>Before you start Aurora you will also need to initialize the log on a majority of the masters.</p>
-<pre class="highlight plaintext"><code>mesos-log initialize --path="/path/to/native/log"
-</code></pre>
-
-<p>The <code>--path</code> flag should match the <code>--native_log_file_path</code> flag to the scheduler.
-Failing to do this will result the following message when you try to start the scheduler.</p>
-<pre class="highlight plaintext"><code>Replica in EMPTY status received a broadcasted recover request
-</code></pre>
-
-<h3 id="storage-performance-considerations">Storage Performance Considerations</h3>
-
-<p>See <a href="/documentation/0.10.0/scheduler-storage/">this document</a> for scheduler storage performance considerations.</p>
-
-<h3 id="network-considerations">Network considerations</h3>
-
-<p>The Aurora scheduler listens on 2 ports - an HTTP port used for client RPCs and a web UI,
-and a libprocess (HTTP+Protobuf) port used to communicate with the Mesos master and for the log
-replication protocol. These can be left unconfigured (the scheduler publishes all selected ports
-to ZooKeeper) or explicitly set in the startup script as follows:</p>
-<pre class="highlight plaintext"><code># ...
-AURORA_FLAGS=(
- # ...
- -http_port=8081
- # ...
-)
-# ...
-export LIBPROCESS_PORT=8083
-# ...
-</code></pre>
-
-<h3 id="considerations-for-running-jobs-in-docker-containers">Considerations for running jobs in docker containers</h3>
-
-<p><em>Note: Docker support is currently EXPERIMENTAL.</em></p>
-
-<p>In order for Aurora to launch jobs using docker containers, a few extra configuration options
-must be set. The <a href="http://mesos.apache.org/documentation/latest/docker-containerizer/">docker containerizer</a>
-must be enabled on the mesos slaves by launching them with the <code>--containerizers=docker,mesos</code> option.</p>
-
-<p>By default, Aurora will configure Mesos to copy the file specified in <code>-thermos_executor_path</code>
-into the container’s sandbox. If using a wrapper script to launch the thermos executor,
-specify the path to the wrapper in that argument. In addition, the path to the executor pex itself
-must be included in the <code>-thermos_executor_resources</code> option. Doing so will ensure that both the
-wrapper script and executor are correctly copied into the sandbox. Finally, ensure the wrapper
-script does not access resources outside of the sandbox, as when the script is run from within a
-docker container those resources will not exist.</p>
-
-<p>A scheduler flag, <code>-global_container_mounts</code> allows mounting paths from the host (i.e., the slave)
-into all containers on that host. The format is a comma seperated list of host<em>path:container</em>path[:mode]
-tuples. For example <code>-global_container_mounts=/opt/secret_keys_dir:/mnt/secret_keys_dir:ro</code> mounts
-<code>/opt/secret_keys_dir</code> from the slaves into all launched containers. Valid modes are <code>ro</code> and <code>rw</code>.</p>
-
-<p>In order to correctly execute processes inside a job, the docker container must have python 2.7
-installed.</p>
-
-<h2 id="running-aurora">Running Aurora</h2>
-
-<p>Configure a supervisor like <a href="http://mmonit.com/monit/">Monit</a> or
-<a href="http://supervisord.org/">supervisord</a> to run the created <code>scheduler.sh</code> file and restart it
-whenever it fails. Aurora expects to be restarted by an external process when it fails. Aurora
-supports an active health checking protocol on its admin HTTP interface - if a <code>GET /health</code> times
-out or returns anything other than <code>200 OK</code> the scheduler process is unhealthy and should be
-restarted.</p>
-
-<p>For example, monit can be configured with</p>
-<pre class="highlight plaintext"><code>if failed port 8081 send "GET /health HTTP/1.0\r\n" expect "OK\n" with timeout 2 seconds for 10 cycles then restart
-</code></pre>
-
-<p>assuming you set <code>-http_port=8081</code>.</p>
-
-<h2 id="security-considerations">Security Considerations</h2>
-
-<p>See <a href="/documentation/0.10.0/security/">security.md</a>.</p>
-
-<h2 id="configuring-resource-oversubscription">Configuring Resource Oversubscription</h2>
-
-<p><strong>WARNING</strong>: This feature is currently in alpha status. Do not use it in production clusters!
-See <a href="/documentation/0.10.0/configuration-reference/#revocable-jobs">this document</a> for more feature details.</p>
-
-<p>Set these scheduler flag to allow receiving revocable Mesos offers:</p>
-<pre class="highlight plaintext"><code>-receive_revocable_resources=true
-</code></pre>
-
-<p>Specify a tier configuration file path:</p>
-<pre class="highlight plaintext"><code>-tier_config=path/to/tiers/config.json
-</code></pre>
-
-<p>Example <a href="https://github.com/apache/aurora/blob/#{git_tag}/src/test/resources/org/apache/aurora/scheduler/tiers-example.json">tier configuration file</a>).</p>
-
-<h3 id="maintaining-an-aurora-installation">Maintaining an Aurora Installation</h3>
-
-<h3 id="monitoring">Monitoring</h3>
-
-<p>Please see our dedicated <a href="/documentation/0.10.0/monitoring/">monitoring guide</a> for in-depth discussion on monitoring.</p>
-
-<h3 id="running-stateful-services">Running stateful services</h3>
-
-<p>Aurora is best suited to run stateless applications, but it also accommodates for stateful services
-like databases, or services that otherwise need to always run on the same machines.</p>
-
-<h4 id="dedicated-attribute">Dedicated attribute</h4>
-
-<p>The Mesos slave has the <code>--attributes</code> command line argument which can be used to mark a slave with
-static attributes (not to be confused with <code>--resources</code>, which are dynamic and accounted).</p>
-
-<p>Aurora makes these attributes available for matching with scheduling
-<a href="/documentation/0.10.0/configuration-reference/#specifying-scheduling-constraints">constraints</a>. Most of these
-constraints are arbitrary and available for custom use. There is one exception, though: the
-<code>dedicated</code> attribute. Aurora treats this specially, and only allows matching jobs to run on these
-machines, and will only schedule matching jobs on these machines.</p>
-
-<p>See the <a href="/documentation/0.10.0/resources/#resource-quota">section</a> about resource quotas to learn how quotas apply to
-dedicated jobs.</p>
-
-<h5 id="syntax">Syntax</h5>
-
-<p>The dedicated attribute has semantic meaning. The format is <code>$role(/.*)?</code>. When a job is created,
-the scheduler requires that the <code>$role</code> component matches the <code>role</code> field in the job
-configuration, and will reject the job creation otherwise. The remainder of the attribute is
-free-form. We’ve developed the idiom of formatting this attribute as <code>$role/$job</code>, but do not
-enforce this.</p>
-
-<h5 id="example">Example</h5>
-
-<p>Consider the following slave command line:</p>
-<pre class="highlight plaintext"><code>mesos-slave --attributes="dedicated:db_team/redis" ...
-</code></pre>
-
-<p>And this job configuration:</p>
-<pre class="highlight plaintext"><code>Service(
- name = 'redis',
- role = 'db_team',
- constraints = {
- 'dedicated': 'db_team/redis'
- }
- ...
-)
-</code></pre>
-
-<p>The job configuration is indicating that it should only be scheduled on slaves with the attribute
-<code>dedicated:db_team/redis</code>. Additionally, Aurora will prevent any tasks that do <em>not</em> have that
-constraint from running on those slaves.</p>
-
-<h2 id="best-practices">Best practices</h2>
-
-<h3 id="diversity">Diversity</h3>
-
-<p>Data centers are often organized with hierarchical failure domains. Common failure domains
-include hosts, racks, rows, and PDUs. If you have this information available, it is wise to tag
-the mesos-slave with them as
-<a href="https://mesos.apache.org/documentation/attributes-resources/">attributes</a>.</p>
-
-<p>When it comes time to schedule jobs, Aurora will automatically spread them across the failure
-domains as specified in the
-<a href="/documentation/0.10.0/configuration-reference/#specifying-scheduling-constraints">job configuration</a>.</p>
-
-<p>Note: in virtualized environments like EC2, the only attribute that usually makes sense for this
-purpose is <code>host</code>.</p>
-
-<h2 id="common-problems">Common problems</h2>
-
-<p>So you’ve started your first cluster and are running into some issues? We’ve collected some common
-stumbling blocks and solutions here to help get you moving.</p>
-
-<h3 id="replicated-log-not-initialized">Replicated log not initialized</h3>
-
-<h4 id="symptoms">Symptoms</h4>
-
-<ul>
-<li>Scheduler RPCs and web interface claim <code>Storage is not READY</code></li>
-<li>Scheduler log repeatedly prints messages like</li>
-</ul>
-<pre class="highlight plaintext"><code> I1016 16:12:27.234133 26081 replica.cpp:638] Replica in EMPTY status
- received a broadcasted recover request
- I1016 16:12:27.234256 26084 recover.cpp:188] Received a recover response
- from a replica in EMPTY status
-</code></pre>
-
-<h4 id="solution">Solution</h4>
-
-<p>When you create a new cluster, you need to inform a quorum of schedulers that they are safe to
-consider their database to be empty by <a href="#initializing-the-replicated-log">initializing</a> the
-replicated log. This is done to prevent the scheduler from modifying the cluster state in the event
-of multiple simultaneous disk failures or, more likely, misconfiguration of the replicated log path.</p>
-
-<h3 id="scheduler-not-registered">Scheduler not registered</h3>
-
-<h4 id="symptoms">Symptoms</h4>
-
-<p>Scheduler log contains</p>
-<pre class="highlight plaintext"><code>Framework has not been registered within the tolerated delay.
-</code></pre>
-
-<h4 id="solution">Solution</h4>
-
-<p>Double-check that the scheduler is configured correctly to reach the master. If you are registering
-the master in ZooKeeper, make sure command line argument to the master:</p>
-<pre class="highlight plaintext"><code>--zk=zk://$ZK_HOST:2181/mesos/master
-</code></pre>
-
-<p>is the same as the one on the scheduler:</p>
-<pre class="highlight plaintext"><code>-mesos_master_address=zk://$ZK_HOST:2181/mesos/master
-</code></pre>
-
-<h2 id="changing-scheduler-quorum-size">Changing Scheduler Quorum Size</h2>
-
-<p>Special care needs to be taken when changing the size of the Aurora scheduler quorum.
-Since Aurora uses a Mesos replicated log, similar steps need to be followed as when
-<a href="http://mesos.apache.org/documentation/latest/operational-guide">changing the mesos quorum size</a>.</p>
-
-<h3 id="preparation">Preparation</h3>
-
-<p>Increase <a href="/documentation/0.10.0/storage-config/#-native_log_quorum_size">-native<em>log</em>quorum_size</a> on each
-existing scheduler and restart them. When updating from 3 to 5 schedulers, the quorum size
-would grow from 2 to 3.</p>
-
-<h3 id="adding-new-schedulers">Adding New Schedulers</h3>
-
-<p>Start the new schedulers with <code>-native_log_quorum_size</code> set to the new value. Failing to
-first increase the quorum size on running schedulers can in some cases result in corruption
-or truncating of the replicated log used by Aurora. In that case, see the documentation on
-<a href="/documentation/0.10.0/storage-config/#recovering-from-a-scheduler-backup">recovering from backup</a>.</p>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/design/command-hooks/command-hooks20191213-22326-15t75xs b/content/documentation/0.10.0/design/command-hooks
similarity index 100%
rename from content/documentation/0.10.0/design/command-hooks/command-hooks20191213-22326-15t75xs
rename to content/documentation/0.10.0/design/command-hooks
diff --git a/content/documentation/0.10.0/design/command-hooks/index.html b/content/documentation/0.10.0/design/command-hooks/index.html
deleted file mode 100644
index 4ce929d..0000000
--- a/content/documentation/0.10.0/design/command-hooks/index.html
+++ /dev/null
@@ -1,257 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.1/css/bootstrap.min.css">
- <link href="/assets/css/main.css" rel="stylesheet">
- <!-- Analytics -->
- <script type="text/javascript">
- var _gaq = _gaq || [];
- _gaq.push(['_setAccount', 'UA-45879646-1']);
- _gaq.push(['_setDomainName', 'apache.org']);
- _gaq.push(['_trackPageview']);
-
- (function() {
- var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
- ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
- var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
- })();
- </script>
- </head>
- <body>
- <div class="container-fluid section-header">
- <div class="container">
- <div class="nav nav-bar">
- <a href="/"><img src="/assets/img/aurora_logo_dkbkg.svg" width="300" alt="Transparent Apache Aurora logo with dark background"/></a>
- <ul class="nav navbar-nav navbar-right">
- <li><a href="/documentation/latest/">Documentation</a></li>
- <li><a href="/community/">Community</a></li>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/blog/">Blog</a></li>
- </ul>
- </div>
- </div>
-</div>
-
- <div class="container-fluid">
- <div class="container content">
- <div class="col-md-12 documentation">
-<h5 class="page-header text-uppercase">Documentation
-<select onChange="window.location.href='/documentation/' + this.value + '/design/command-hooks/'"
- value="0.10.0">
- <option value="0.21.0"
- >
- 0.21.0
- (latest)
- </option>
- <option value="0.20.0"
- >
- 0.20.0
- </option>
- <option value="0.19.1"
- >
- 0.19.1
- </option>
- <option value="0.19.0"
- >
- 0.19.0
- </option>
- <option value="0.18.1"
- >
- 0.18.1
- </option>
- <option value="0.18.0"
- >
- 0.18.0
- </option>
- <option value="0.17.0"
- >
- 0.17.0
- </option>
- <option value="0.16.0"
- >
- 0.16.0
- </option>
- <option value="0.15.0"
- >
- 0.15.0
- </option>
- <option value="0.14.0"
- >
- 0.14.0
- </option>
- <option value="0.13.0"
- >
- 0.13.0
- </option>
- <option value="0.12.0"
- >
- 0.12.0
- </option>
- <option value="0.11.0"
- >
- 0.11.0
- </option>
- <option value="0.10.0"
- selected="selected">
- 0.10.0
- </option>
- <option value="0.9.0"
- >
- 0.9.0
- </option>
- <option value="0.8.0"
- >
- 0.8.0
- </option>
- <option value="0.7.0-incubating"
- >
- 0.7.0-incubating
- </option>
- <option value="0.6.0-incubating"
- >
- 0.6.0-incubating
- </option>
- <option value="0.5.0-incubating"
- >
- 0.5.0-incubating
- </option>
-</select>
-</h5>
-<h1 id="command-hooks-for-the-aurora-client">Command Hooks for the Aurora Client</h1>
-
-<h2 id="introduction-motivation">Introduction/Motivation</h2>
-
-<p>We’ve got hooks in the client that surround API calls. These are
-pretty awkward, because they don’t correlate with user actions. For
-example, suppose we wanted a policy that said users weren’t allowed to
-kill all instances of a production job at once.</p>
-
-<p>Right now, all that we could hook would be the “killJob” api call. But
-kill (at least in newer versions of the client) normally runs in
-batches. If a user called killall, what we would see on the API level
-is a series of “killJob” calls, each of which specified a batch of
-instances. We woudn’t be able to distinguish between really killing
-all instances of a job (which is forbidden under this policy), and
-carefully killing in batches (which is permitted.) In each case, the
-hook would just see a series of API calls, and couldn’t find out what
-the actual command being executed was!</p>
-
-<p>For most policy enforcement, what we really want to be able to do is
-look at and vet the commands that a user is performing, not the API
-calls that the client uses to implement those commands.</p>
-
-<p>So I propose that we add a new kind of hooks, which surround noun/verb
-commands. A hook will register itself to handle a collection of (noun,
-verb) pairs. Whenever any of those noun/verb commands are invoked, the
-hooks methods will be called around the execution of the verb. A
-pre-hook will have the ability to reject a command, preventing the
-verb from being executed.</p>
-
-<h2 id="registering-hooks">Registering Hooks</h2>
-
-<p>These hooks will be registered via configuration plugins. A configuration plugin
-can register hooks using an API. Hooks registered this way are, effectively,
-hardwired into the client executable.</p>
-
-<p>The order of execution of hooks is unspecified: they may be called in
-any order. There is no way to guarantee that one hook will execute
-before some other hook.</p>
-
-<h3 id="global-hooks">Global Hooks</h3>
-
-<p>Commands registered by the python call are called <em>global</em> hooks,
-because they will run for all configurations, whether or not they
-specify any hooks in the configuration file.</p>
-
-<p>In the implementation, hooks are registered in the module
-<code>apache.aurora.client.cli.command_hooks</code>, using the class
-<code>GlobalCommandHookRegistry</code>. A global hook can be registered by calling
-<code>GlobalCommandHookRegistry.register_command_hook</code> in a configuration plugin.</p>
-
-<h3 id="the-api">The API</h3>
-<pre class="highlight objective_c"><code><span style="background-color: #f8f8f8">class</span> <span style="background-color: #f8f8f8">CommandHook</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">object</span><span style="background-color: #f8f8f8">)</span>
- <span style="color: #000000;font-weight: bold">@property</span>
- <span style="background-color: #f8f8f8">def</span> <span style="background-color: #f8f8f8">name</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">self</span><span style="background-color: #f8f8f8">)</span><span style="color: #000000;font-weight: bold">:</span>
- <span style="color: #d14">"""Returns a name for the hook."</span>
-
- <span style="background-color: #f8f8f8">def</span> <span style="background-color: #f8f8f8">get_nouns</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">self</span><span style="background-color: #f8f8f8">)</span><span style="color: #000000;font-weight: bold">:</span>
- <span style="color: #d14">"""Return the nouns that have verbs that should invoke this hook."""</span>
-
- <span style="background-color: #f8f8f8">def</span> <span style="background-color: #f8f8f8">get_verbs</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">self</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f8f8f8">noun</span><span style="background-color: #f8f8f8">)</span><span style="color: #000000;font-weight: bold">:</span>
- <span style="color: #d14">"""Return the verbs for a particular noun that should invoke his hook."""</span>
-
- <span style="color: #a61717;background-color: #e3d2d2">@abstractmethod</span>
- <span style="background-color: #f8f8f8">def</span> <span style="background-color: #f8f8f8">pre_command</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">self</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f8f8f8">noun</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f8f8f8">verb</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f [...]
- <span style="color: #d14">"""Execute a hook before invoking a verb.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * noun: the noun being invoked.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * verb: the verb being invoked.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * context: the context object that will be used to invoke the verb.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> The options object will be initialized before calling the hook</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * commandline: the original argv collection used to invoke the client.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> Returns: True if the command should be allowed to proceed; False if the command</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> should be rejected.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> """</span>
-
- <span style="background-color: #f8f8f8">def</span> <span style="background-color: #f8f8f8">post_command</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">self</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f8f8f8">noun</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f8f8f8">verb</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: # [...]
- <span style="color: #d14">"""Execute a hook after invoking a verb.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * noun: the noun being invoked.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * verb: the verb being invoked.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * context: the context object that will be used to invoke the verb.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> The options object will be initialized before calling the hook</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * commandline: the original argv collection used to invoke the client.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> * result: the result code returned by the verb.</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> Returns: nothing</span><span style="color: #a61717;background-color: #e3d2d2">
-</span><span style="color: #d14"> """</span>
-
-<span style="background-color: #f8f8f8">class</span> <span style="background-color: #f8f8f8">GlobalCommandHookRegistry</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">object</span><span style="background-color: #f8f8f8">)</span><span style="color: #000000;font-weight: bold">:</span>
- <span style="color: #a61717;background-color: #e3d2d2">@classmethod</span>
- <span style="background-color: #f8f8f8">def</span> <span style="background-color: #f8f8f8">register_command_hook</span><span style="background-color: #f8f8f8">(</span><span style="background-color: #f8f8f8">self</span><span style="background-color: #f8f8f8">,</span> <span style="background-color: #f8f8f8">hook</span><span style="background-color: #f8f8f8">)</span><span style="color: #000000;font-weight: bold">:</span>
- <span style="background-color: #f8f8f8">pass</span>
-</code></pre>
-
-<h3 id="skipping-hooks">Skipping Hooks</h3>
-
-<p>To skip a hook, a user uses a command-line option, <code>--skip-hooks</code>. The option can either
-specify specific hooks to skip, or “all”:</p>
-
-<ul>
-<li><code>aurora --skip-hooks=all job create east/bozo/devel/myjob</code> will create a job
-without running any hooks.</li>
-<li><code>aurora --skip-hooks=test,iq create east/bozo/devel/myjob</code> will create a job,
-and will skip only the hooks named “test” and “iq”.</li>
-</ul>
-
-</div>
-
- </div>
- </div>
- <div class="container-fluid section-footer buffer">
- <div class="container">
- <div class="row">
- <div class="col-md-2 col-md-offset-1"><h3>Quick Links</h3>
- <ul>
- <li><a href="/downloads/">Downloads</a></li>
- <li><a href="/community/">Mailing Lists</a></li>
- <li><a href="http://issues.apache.org/jira/browse/AURORA">Issue Tracking</a></li>
- <li><a href="/documentation/latest/contributing/">How To Contribute</a></li>
- </ul>
- </div>
- <div class="col-md-2"><h3>The ASF</h3>
- <ul>
- <li><a href="http://www.apache.org/licenses/">License</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
- <li><a href="http://www.apache.org/security/">Security</a></li>
- </ul>
- </div>
- <div class="col-md-6">
- <p class="disclaimer">© 2014-2017 <a href="http://www.apache.org/">Apache Software Foundation</a>. Licensed under the <a href="http://www.apache.org/licenses/">Apache License v2.0</a>. The <a href="https://www.flickr.com/photos/trondk/12706051375/">Aurora Borealis IX photo</a> displayed on the homepage is available under a <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">Creative Commons BY-NC-ND 2.0 license</a>. Apache, Apache Aurora, and the Apache feather logo are [...]
- </div>
- </div>
- </div>
-
- </body>
-</html>
diff --git a/content/documentation/0.10.0/developing-aurora-client/developing-aurora-client20191213-22326-1tjw7ai b/content/documentation/0.10.0/developing-aurora-client
similarity index 100%
rename from content/documentation/0.10.0/developing-aurora-client/developing-aurora-client20191213-22326-1tjw7ai
rename to content/documentation/0.10.0/developing-aurora-client
diff --git a/content/documentation/0.10.0/developing-aurora-client/index.html b/content/documentation/0.10.0/developing-aurora-client/index.html
deleted file mode 100644
index 91bcc1d..0000000
--- a/content/documentation/0.10.0/developing-aurora-client/index.html
+++ /dev/null
@@ -1,244 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta name="viewport" content="width=device-width, initial-scale=1">
- <title>Apache Aurora</title>
... 253604 lines suppressed ...