Author: wfarner
Date: Sat Dec 12 01:46:48 2015
New Revision: 1719617
URL: http://svn.apache.org/viewvc?rev=1719617&view=rev
Log:
Update site to latest documentation.
Added:
aurora/site/source/_footer.erb
- copied, changed from r1719615, aurora/site/source/_footer.md.erb
Removed:
aurora/site/source/_footer.md.erb
Modified:
aurora/site/publish/blog/2015-upcoming-apache-aurora-meetups/index.html
aurora/site/publish/blog/aurora-0-6-0-incubating-released/index.html
aurora/site/publish/blog/aurora-0-7-0-incubating-released/index.html
aurora/site/publish/blog/aurora-0-8-0-released/index.html
aurora/site/publish/blog/aurora-0-9-0-released/index.html
aurora/site/publish/blog/aurora-at-mesoscon-seattle/index.html
aurora/site/publish/blog/feed.xml
aurora/site/publish/blog/index.html
aurora/site/publish/community/index.html
aurora/site/publish/developers/index.html
aurora/site/publish/docs/gettingstarted/index.html
aurora/site/publish/docs/howtocontribute/index.html
aurora/site/publish/documentation/latest/build-system/index.html
aurora/site/publish/documentation/latest/client-cluster-configuration/index.html
aurora/site/publish/documentation/latest/client-commands/index.html
aurora/site/publish/documentation/latest/committers/index.html
aurora/site/publish/documentation/latest/configuration-reference/index.html
aurora/site/publish/documentation/latest/configuration-tutorial/index.html
aurora/site/publish/documentation/latest/contributing/index.html
aurora/site/publish/documentation/latest/cron-jobs/index.html
aurora/site/publish/documentation/latest/deploying-aurora-scheduler/index.html
aurora/site/publish/documentation/latest/developing-aurora-client/index.html
aurora/site/publish/documentation/latest/developing-aurora-scheduler/index.html
aurora/site/publish/documentation/latest/hooks/index.html
aurora/site/publish/documentation/latest/index.html
aurora/site/publish/documentation/latest/monitoring/index.html
aurora/site/publish/documentation/latest/presentations/index.html
aurora/site/publish/documentation/latest/resources/index.html
aurora/site/publish/documentation/latest/scheduler-storage/index.html
aurora/site/publish/documentation/latest/security/index.html
aurora/site/publish/documentation/latest/sla/index.html
aurora/site/publish/documentation/latest/storage-config/index.html
aurora/site/publish/documentation/latest/storage/index.html
aurora/site/publish/documentation/latest/test-resource-generation/index.html
aurora/site/publish/documentation/latest/thrift-deprecation/index.html
aurora/site/publish/documentation/latest/tutorial/index.html
aurora/site/publish/documentation/latest/user-guide/index.html
aurora/site/publish/documentation/latest/vagrant/index.html
aurora/site/publish/downloads/index.html
aurora/site/publish/index.html
aurora/site/publish/sitemap.xml
aurora/site/source/documentation/latest.html.md
aurora/site/source/documentation/latest/client-commands.md
aurora/site/source/documentation/latest/configuration-reference.md
aurora/site/source/documentation/latest/configuration-tutorial.md
aurora/site/source/documentation/latest/contributing.md
aurora/site/source/documentation/latest/cron-jobs.md
aurora/site/source/documentation/latest/deploying-aurora-scheduler.md
aurora/site/source/documentation/latest/developing-aurora-client.md
aurora/site/source/documentation/latest/developing-aurora-scheduler.md
aurora/site/source/documentation/latest/monitoring.md
aurora/site/source/documentation/latest/security.md
aurora/site/source/documentation/latest/sla.md
aurora/site/source/documentation/latest/storage-config.md
aurora/site/source/documentation/latest/test-resource-generation.md
aurora/site/source/documentation/latest/vagrant.md
Modified:
aurora/site/publish/blog/2015-upcoming-apache-aurora-meetups/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/2015-upcoming-apache-aurora-meetups/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/2015-upcoming-apache-aurora-meetups/index.html
(original)
+++ aurora/site/publish/blog/2015-upcoming-apache-aurora-meetups/index.html Sat
Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="container-fluid">
@@ -43,7 +43,6 @@
<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>
@@ -101,7 +100,6 @@
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -126,5 +124,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/blog/aurora-0-6-0-incubating-released/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/aurora-0-6-0-incubating-released/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/aurora-0-6-0-incubating-released/index.html
(original)
+++ aurora/site/publish/blog/aurora-0-6-0-incubating-released/index.html Sat
Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="container-fluid">
@@ -43,7 +43,6 @@
<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>
@@ -127,7 +126,6 @@ responsibility of application update orc
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -152,5 +150,6 @@ responsibility of application update orc
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/blog/aurora-0-7-0-incubating-released/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/aurora-0-7-0-incubating-released/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/aurora-0-7-0-incubating-released/index.html
(original)
+++ aurora/site/publish/blog/aurora-0-7-0-incubating-released/index.html Sat
Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="container-fluid">
@@ -43,7 +43,6 @@
<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>
@@ -113,7 +112,6 @@
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -138,5 +136,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/blog/aurora-0-8-0-released/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/aurora-0-8-0-released/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/aurora-0-8-0-released/index.html (original)
+++ aurora/site/publish/blog/aurora-0-8-0-released/index.html Sat Dec 12
01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="container-fluid">
@@ -43,7 +43,6 @@
<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>
@@ -121,7 +120,6 @@
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -146,5 +144,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/blog/aurora-0-9-0-released/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/aurora-0-9-0-released/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/aurora-0-9-0-released/index.html (original)
+++ aurora/site/publish/blog/aurora-0-9-0-released/index.html Sat Dec 12
01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="container-fluid">
@@ -43,7 +43,6 @@
<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>
@@ -106,7 +105,6 @@ be enabled via the scheduler command lin
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -131,5 +129,6 @@ be enabled via the scheduler command lin
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/blog/aurora-at-mesoscon-seattle/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/aurora-at-mesoscon-seattle/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/aurora-at-mesoscon-seattle/index.html (original)
+++ aurora/site/publish/blog/aurora-at-mesoscon-seattle/index.html Sat Dec 12
01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="container-fluid">
@@ -43,7 +43,6 @@
<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>
@@ -88,7 +87,6 @@
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -113,5 +111,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/blog/feed.xml
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/feed.xml?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/feed.xml (original)
+++ aurora/site/publish/blog/feed.xml Sat Dec 12 01:46:48 2015
@@ -4,15 +4,14 @@
<id>http://aurora.apache.org/blog</id>
<link href="http://aurora.apache.org/blog"; />
<link href="http://aurora.apache.org/blog/feed.xml"; rel="self"/>
- <updated>2015-08-26T00:00:00Z</updated>
-
+ <updated>2015-08-26T00:00:00+00:00</updated>
<entry>
<id>http://aurora.apache.org/blog/aurora-at-mesoscon-seattle/</id>
<link href="/blog/aurora-at-mesoscon-seattle/" />
<title>
Recap: Aurora at MesosCon Seattle
</title>
- <updated>2015-08-26T00:00:00Z</updated>
+ <updated>2015-08-26T00:00:00+00:00</updated>
<author>
<name>Dave Lester</name>
</author>
@@ -35,14 +34,13 @@
</content>
</entry>
-
<entry>
<id>http://aurora.apache.org/blog/aurora-0-9-0-released/</id>
<link href="/blog/aurora-0-9-0-released/" />
<title>
Apache Aurora 0.9.0 Released
</title>
- <updated>2015-07-24T00:00:00Z</updated>
+ <updated>2015-07-24T00:00:00+00:00</updated>
<author>
<name>Jake Farrell</name>
</author>
@@ -83,14 +81,13 @@ be enabled via the scheduler command lin
</content>
</entry>
-
<entry>
<id>http://aurora.apache.org/blog/aurora-0-8-0-released/</id>
<link href="/blog/aurora-0-8-0-released/" />
<title>
Apache Aurora 0.8.0 Released
</title>
- <updated>2015-05-14T00:00:00Z</updated>
+ <updated>2015-05-14T00:00:00+00:00</updated>
<author>
<name>Jake Farrell</name>
</author>
@@ -146,14 +143,13 @@ be enabled via the scheduler command lin
</content>
</entry>
-
<entry>
<id>http://aurora.apache.org/blog/2015-upcoming-apache-aurora-meetups/</id>
<link href="/blog/2015-upcoming-apache-aurora-meetups/" />
<title>
Upcoming Apache Aurora Meetups in NYC and the Bay Area
</title>
- <updated>2015-03-18T00:00:00Z</updated>
+ <updated>2015-03-18T00:00:00+00:00</updated>
<author>
<name>Dave Lester</name>
</author>
@@ -189,14 +185,13 @@ be enabled via the scheduler command lin
</content>
</entry>
-
<entry>
<id>http://aurora.apache.org/blog/aurora-0-7-0-incubating-released/</id>
<link href="/blog/aurora-0-7-0-incubating-released/" />
<title>
Aurora 0.7.0-incubating Released, Adding Support for Docker Containers
</title>
- <updated>2015-02-12T00:00:00Z</updated>
+ <updated>2015-02-12T00:00:00+00:00</updated>
<author>
<name>Maxim Khutornenko</name>
</author>
@@ -244,14 +239,13 @@ be enabled via the scheduler command lin
</content>
</entry>
-
<entry>
<id>http://aurora.apache.org/blog/aurora-0-6-0-incubating-released/</id>
<link href="/blog/aurora-0-6-0-incubating-released/" />
<title>
Aurora 0.6.0-incubating Released
</title>
- <updated>2014-12-08T00:00:00Z</updated>
+ <updated>2014-12-08T00:00:00+00:00</updated>
<author>
<name>Bill Farner</name>
</author>
@@ -313,5 +307,4 @@ responsibility of application update orc
</content>
</entry>
-
</feed>
\ No newline at end of file
Modified: aurora/site/publish/blog/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/blog/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/blog/index.html (original)
+++ aurora/site/publish/blog/index.html Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="row-fluid">
@@ -43,42 +43,34 @@
<p>The Aurora blog is a place for release announcements and for
project committers to highlight features of the software.</p>
</div>
<div class="col-md-9">
-
<article>
<h2><a href="/blog/aurora-at-mesoscon-seattle/">Recap:
Aurora at MesosCon Seattle</a></h2>
<p><em>Posted by Dave Lester, August 26, 2015</em></p>
</article>
-
<article>
<h2><a href="/blog/aurora-0-9-0-released/">Apache
Aurora 0.9.0 Released</a></h2>
<p><em>Posted by Jake Farrell, July 24, 2015</em></p>
</article>
-
<article>
<h2><a href="/blog/aurora-0-8-0-released/">Apache
Aurora 0.8.0 Released</a></h2>
<p><em>Posted by Jake Farrell, May 14, 2015</em></p>
</article>
-
<article>
<h2><a
href="/blog/2015-upcoming-apache-aurora-meetups/">Upcoming Apache Aurora
Meetups in NYC and the Bay Area</a></h2>
<p><em>Posted by Dave Lester, March 18, 2015</em></p>
</article>
-
<article>
<h2><a
href="/blog/aurora-0-7-0-incubating-released/">Aurora 0.7.0-incubating
Released, Adding Support for Docker Containers</a></h2>
<p><em>Posted by Maxim Khutornenko, February 12,
2015</em></p>
</article>
-
<article>
<h2><a
href="/blog/aurora-0-6-0-incubating-released/">Aurora 0.6.0-incubating
Released</a></h2>
<p><em>Posted by Bill Farner, December 8, 2014</em></p>
</article>
-
</div>
</div>
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -103,5 +95,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/community/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/community/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/community/index.html (original)
+++ aurora/site/publish/community/index.html Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<h1 id="community">Community</h1>
@@ -80,7 +80,6 @@
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -105,5 +104,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/developers/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/developers/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/developers/index.html (original)
+++ aurora/site/publish/developers/index.html Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<h1 id="developers">Developers</h1>
@@ -54,7 +54,6 @@
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -79,5 +78,6 @@
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/docs/gettingstarted/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/docs/gettingstarted/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/docs/gettingstarted/index.html (original)
+++ aurora/site/publish/docs/gettingstarted/index.html Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<h1 id="getting-started">Getting Started</h1>
@@ -45,7 +45,6 @@ while the project moves its documentatio
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -70,5 +69,6 @@ while the project moves its documentatio
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/docs/howtocontribute/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/docs/howtocontribute/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/docs/howtocontribute/index.html (original)
+++ aurora/site/publish/docs/howtocontribute/index.html Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<h1 id="how-to-contribute">How To Contribute</h1>
@@ -51,41 +51,44 @@ Subsequent runs will cache your login cr
<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 text">./rbt post -o -g
-</pre>
+<pre class="highlight plaintext"><code>./rbt post -o -g
+</code></pre>
+
<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 text">./rbt post -o -r <RB_ID>
-</pre>
-<h2 id="merging-your-own-review-committers-">Merging Your Own Review
(Committers)</h2>
+<pre class="highlight plaintext"><code>./rbt post -o -r <RB_ID>
+</code></pre>
+
+<h2 id="merging-your-own-review-committers">Merging Your Own Review
(Committers)</h2>
<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 text">git checkout master
+<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>
-</pre>
+</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>
<h2 id="merging-someone-else-39-s-review">Merging Someone Else’s
Review</h2>
<p>Sometimes you’ll need to merge someone else’s RB. The typical
workflow for this is</p>
-<pre class="highlight text">git checkout master
+<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
-</pre>
+</code></pre>
+
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -110,5 +113,6 @@ git push origin master
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/documentation/latest/build-system/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/build-system/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/build-system/index.html (original)
+++ aurora/site/publish/documentation/latest/build-system/index.html Sat Dec 12
01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="col-md-12 documentation">
@@ -47,10 +47,10 @@
<ol>
<li><p>1 <code>BUILD</code> per 3rd level directory. For a list of current
top-level packages run:</p>
-<pre class="highlight text">% find src/main/python -maxdepth 3 -mindepth 3
-type d |\
+<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
-</pre></li>
+ 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
@@ -73,7 +73,7 @@ target. This will help our migration off
</ol>
<h2 id="annotated-example-apache-thermos-runner">Annotated example -
apache.thermos.runner</h2>
-<pre class="highlight text">% find src/main/python/apache/thermos/runner
+<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
@@ -86,59 +86,60 @@ 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',
+ name = '_runner',
# The target covers every python file under this directory and
subdirectories.
- sources = rglobs('*.py'),
+ 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',
+ '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
+# 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',
+ 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',
+ entry_point = 'apache.thermos.bin.thermos_runner',
dependencies = [
# Notice that we depend only on the single private target from this BUILD
file here.
- ':_runner',
+ ':_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',
+ name = 'runner',
dependencies = [
# Again, notice that we depend only on the single private target from this
BUILD file here.
- ':_runner',
+ ':_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(),
+ 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',
+ 'thermos_runner': ':thermos_runner',
}),
)
-</pre></div>
+</code></pre>
+
+</div>
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -163,5 +164,6 @@ python_library(
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified:
aurora/site/publish/documentation/latest/client-cluster-configuration/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/client-cluster-configuration/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
---
aurora/site/publish/documentation/latest/client-cluster-configuration/index.html
(original)
+++
aurora/site/publish/documentation/latest/client-cluster-configuration/index.html
Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="col-md-12 documentation">
@@ -152,11 +152,11 @@ URL of your VIP in a loadbalancer or a r
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">
@@ -181,5 +181,6 @@ to Aurora which will allow for more robu
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/documentation/latest/client-commands/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/client-commands/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/client-commands/index.html
(original)
+++ aurora/site/publish/documentation/latest/client-commands/index.html Sat Dec
12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="col-md-12 documentation">
@@ -114,18 +114,20 @@ environment variable is not set. The sec
<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"><span class="p">[{</span>
- <span class="s2">"name"</span><span class="err">:</span> <span
class="s2">"example"</span><span class="p">,</span>
- <span class="s2">"scheduler_uri"</span><span class="err">:</span>
<span class="s2">"localhost:55555"</span><span class="p">,</span>
+<pre class="highlight javascript"><code><span class="p">[{</span>
+ <span class="s2">"name"</span><span class="p">:</span> <span
class="s2">"example"</span><span class="p">,</span>
+ <span class="s2">"scheduler_uri"</span><span class="p">:</span> <span
class="s2">"localhost:55555"</span><span class="p">,</span>
<span class="p">}]</span>
-</pre>
+</code></pre>
+
<p>A configuration for a leader-elected scheduler would contain something
like:</p>
-<pre class="highlight javascript"><span class="p">[{</span>
- <span class="s2">"name"</span><span class="err">:</span> <span
class="s2">"example"</span><span class="p">,</span>
- <span class="s2">"zk"</span><span class="err">:</span> <span
class="s2">"192.168.33.7"</span><span class="p">,</span>
- <span class="s2">"scheduler_zk_path"</span><span
class="err">:</span> <span class="s2">"/aurora/scheduler"</span>
+<pre class="highlight javascript"><code><span class="p">[{</span>
+ <span class="s2">"name"</span><span class="p">:</span> <span
class="s2">"example"</span><span class="p">,</span>
+ <span class="s2">"zk"</span><span class="p">:</span> <span
class="s2">"192.168.33.7"</span><span class="p">,</span>
+ <span class="s2">"scheduler_zk_path"</span><span class="p">:</span> <span
class="s2">"/aurora/scheduler"</span>
<span class="p">}]</span>
-</pre>
+</code></pre>
+
<p>For more details on cluster configuration see the
<a href="/documentation/latest/client-cluster-configuration/">Client Cluster
Configuration</a> documentation.</p>
@@ -181,14 +183,16 @@ that we explain it in a devoted document
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 text">aurora job create <job key>
<configuration file>
-</pre>
+<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 text">aurora task run CLUSTER/ROLE/ENV/NAME[/INSTANCES]
<cmd>
-</pre>
+<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>
@@ -197,8 +201,9 @@ commands; i.e. anything in the <code>{{m
namespaces.</p>
<h3 id="killing-a-job">Killing a Job</h3>
-<pre class="highlight text">aurora job killall CLUSTER/ROLE/ENV/NAME
-</pre>
+<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>
@@ -209,13 +214,14 @@ 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 text">aurora update start <job key>
<configuration file>
+<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>
-</pre>
+</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
@@ -251,13 +257,14 @@ progress until the first pulse arrives.
<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>
+<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 text">aurora job update
CLUSTER/ROLE/ENV/NAME[/INSTANCES] <configuration file>
+<pre class="highlight plaintext"><code>aurora job update
CLUSTER/ROLE/ENV/NAME[/INSTANCES] <configuration file>
aurora job cancel-update CLUSTER/ROLE/ENV/NAME
-</pre>
+</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
@@ -291,19 +298,19 @@ environment, and/or name as appropriate
scheme.</li>
<li><p>Check that only these naming components have changed
with <code>aurora diff</code>.</p>
-<pre class="highlight text">aurora job diff CLUSTER/ROLE/ENV/NAME
<job_configuration>
-</pre></li>
+<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 text">aurora job create CLUSTER/ROLE/ENV/NEW_NAME
<job_configuration>
-</pre></li>
+<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 text">aurora job killall CLUSTER/ROLE/ENV/NAME
-</pre></li>
+<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>
@@ -311,8 +318,9 @@ powers that be know you no longer need t
<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 text">aurora job restart
CLUSTER/ROLE/ENV/NAME[/INSTANCES]
-</pre>
+<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>
@@ -334,8 +342,9 @@ if it contains hook definitions and acti
<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 text">aurora job diff CLUSTER/ROLE/ENV/NAME <job
configuration>
-</pre>
+<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>
@@ -346,31 +355,36 @@ is determined using <code>diff</code>, t
how to view and examine Jobs.</p>
<h3 id="listing-jobs">Listing Jobs</h3>
-<pre class="highlight text">aurora config list <job configuration>
-</pre>
+<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 text">aurora job inspect CLUSTER/ROLE/ENV/NAME <job
configuration>
-</pre>
+<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 text">aurora quota get CLUSTER/ROLE
-</pre>
+<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.</p>
+cluster. Only non-<a
href="deploying-aurora-scheduler.md#dedicated-attribute">dedicated</a>
+<a href="configuration-reference.md#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 text">vagrant@precise64:~$ aurora job create
devcluster/www-data/prod/hello /vagrant/examples/jobs/hello_world.aurora
+<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
-</pre>
+</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>
@@ -380,8 +394,9 @@ Jobs are arranged by role, typically a s
production jobs and user accounts for test or development jobs.</p>
<h3 id="getting-job-status">Getting Job Status</h3>
-<pre class="highlight text">aurora job status <job_key>
-</pre>
+<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
@@ -392,24 +407,27 @@ a mix of active tasks (running or assign
<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 text">aurora job open
[<cluster>[/<role>[/<env>/<job_name>]]]
-</pre>
+<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 text">aurora task ssh <job_key> <shard
number>
-</pre>
+<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 text">aurora task run [-e] [-t THREADS] <job_key>
-- <<command-line>>
-</pre>
+<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>
@@ -424,19 +442,20 @@ assigned to this machine</li>
<p>For example, the following type of pattern can be a powerful diagnostic
tool:</p>
-<pre class="highlight text">aurora task run -t5 cluster1/tyg/devel/seizure -- \
- 'curl -s -m1 localhost:{{thermos.ports[http]}}/vars | grep uptime'
-</pre>
+<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">
@@ -461,5 +480,6 @@ Aurora administrators.</p>
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified: aurora/site/publish/documentation/latest/committers/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/committers/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/committers/index.html (original)
+++ aurora/site/publish/documentation/latest/committers/index.html Sat Dec 12
01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="col-md-12 documentation">
@@ -60,24 +60,24 @@ and that key will need to be added to ou
<ol>
<li><p>Create a key:</p>
-<pre class="highlight text"> gpg --gen-key
-</pre></li>
+<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 text"> git clone
https://git-wip-us.apache.org/repos/asf/aurora.git
+<pre class="highlight plaintext"><code> git clone
https://git-wip-us.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>"
+ git add KEYS && git commit -m "Adding gpg key for <APACHE
ID>"
./rbt post -o -g
-</pre></li>
+</code></pre></li>
<li><p>Publish the key to an external key server:</p>
-<pre class="highlight text"> gpg --keyserver pgp.mit.edu --send-keys
<KEY ID>
-</pre></li>
+<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 text">
https://dist.apache.org/repos/dist/dev/aurora/KEYS
+<pre class="highlight plaintext"><code>
https://dist.apache.org/repos/dist/dev/aurora/KEYS
https://dist.apache.org/repos/dist/release/aurora/KEYS
-</pre></li>
+</code></pre></li>
<li><p>Add your key to git config for use with the release scripts:</p>
-<pre class="highlight text"> git config --global user.signingkey <KEY
ID>
-</pre></li>
+<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>
@@ -92,29 +92,29 @@ Version in Jira, the changelog script wi
<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 text"> ./build-support/release/release-candidate
-l m -p
-</pre></li>
+<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 text">
./build-support/release/verify-release-candidate
-</pre></li>
+<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 text"> ./build-support/release/release-candidate
-l m -r 1 -p
-</pre></li>
+<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 text"> ./build-support/release/release
-</pre></li>
+<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">
@@ -139,5 +139,6 @@ all binding votes and send the [RESULT][
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
Modified:
aurora/site/publish/documentation/latest/configuration-reference/index.html
URL:
http://svn.apache.org/viewvc/aurora/site/publish/documentation/latest/configuration-reference/index.html?rev=1719617&r1=1719616&r2=1719617&view=diff
==============================================================================
--- aurora/site/publish/documentation/latest/configuration-reference/index.html
(original)
+++ aurora/site/publish/documentation/latest/configuration-reference/index.html
Sat Dec 12 01:46:48 2015
@@ -21,12 +21,11 @@
</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">
+ <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>
@@ -34,7 +33,8 @@
</ul>
</div>
</div>
-</div>
+</div>
+
<div class="container-fluid">
<div class="container content">
<div class="col-md-12 documentation">
@@ -81,10 +81,12 @@
<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>
@@ -309,22 +311,29 @@ in which they run, use <code>constraints
<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 text"> process = Process(cmdline = "echo hello
{{name}}")
- task = Task(name = "echoes",
- processes = [process(name = "jim"), process(name =
"bob")],
- constraints = [Constraint(order = ["jim",
"bob"]))
-</pre>
+<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 text"> order(process1, process2)
-</pre>
+<pre class="highlight plaintext"><code> order(process1, process2)
+</code></pre>
+
<p>is shorthand for</p>
-<pre class="highlight text"> [Constraint(order = [process1.name(),
process2.name()])]
-</pre>
+<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
@@ -332,24 +341,25 @@ to allocate to the Task.</p>
<h4 id="max_failures">max_failures</h4>
-<p><code>max_failures</code> is the number of times processes that are part of
this
-Task can fail before the entire Task is marked for failure.</p>
+<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:</p>
-<pre class="highlight text"> template = Process(max_failures=10)
+<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",
+ name = "fail",
processes = [
- template(name = "failing", cmdline = "exit 1"),
- template(name = "succeeding", cmdline = "exit 0")
+ template(name = "failing", cmdline = "exit 1"),
+ template(name = "succeeding", cmdline = "exit 0")
],
max_failures=2)
-</pre>
-<p>The <code>failing</code> Process could fail 10 times before being marked as
-permanently failed, and the <code>succeeding</code> Process would succeed on
the
-first run. 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.</p>
+</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>
@@ -364,25 +374,26 @@ a machine with only 4 cores. You can lim
<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 text">def make_mapper(id):
+<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))
+ 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.\*")
+ return Process(name = "reducer", cmdline = "cat temp.\* | nl \>
sine\_table.txt
+ && rm -f temp.\*")
processes = map(make_mapper, range(180))
task = Task(
- name = "mapreduce",
+ name = "mapreduce",
processes = processes + [make\_reducer()],
- constraints = [Constraint(order = [mapper.name(), 'reducer']) for
mapper
+ constraints = [Constraint(order = [mapper.name(), 'reducer']) for mapper
in processes],
max_concurrency = 8)
-</pre>
+</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
@@ -428,7 +439,7 @@ ordering constraints.</p>
<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/latest/resource-isolation/">Resource Isolation
document</a> for suggested values and to understand how
+<a href="/documentation/latest/resources/">Resource Isolation document</a> for
suggested values and to understand how
resources are allocated.</p>
<table><thead>
@@ -513,7 +524,7 @@ resources are allocated.</p>
</tr>
<tr>
<td><code>update_config</code></td>
-<td style="text-align: center"><code>update_config</code> object</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>
@@ -539,11 +550,11 @@ resources are allocated.</p>
<tr>
<td><code>production</code></td>
<td style="text-align: center">Boolean</td>
-<td>Whether or not this is a production task backed by quota (Default: False).
Production jobs may preempt any non-production job, and may only be preempted
by production jobs in the same role and of higher priority. To run jobs at this
level, the job role must have the appropriate quota. To grant quota to a
particular role in production, operators use the <code>aurora_admin
set_quota</code> command.</td>
+<td>Whether or not this is a production task that may <a
href="resources.md#task-preemption">preempt</a> other tasks (Default: False).
Production job role must have the appropriate <a
href="resources.md#resource-quota">quota</a>.</td>
</tr>
<tr>
<td><code>health_check_config</code></td>
-<td style="text-align: center"><code>heath_check_config</code> object</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>
@@ -551,6 +562,16 @@ resources are allocated.</p>
<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>
@@ -563,6 +584,21 @@ Jobs without the service bit set only re
<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="deploying-aurora-scheduler.md#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>
@@ -638,14 +674,29 @@ either due to human error or machine fai
<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>max_consecutive_failures</code></td>
+<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>Maximum number of consecutive failures that tolerated before considering a
task unhealthy (Default: 0)</td>
+<td>If not zero, fail the health check if the response code differs. (Default:
0)</td>
</tr>
</tbody></table>
@@ -734,8 +785,96 @@ guarantees should they be needed.</p>
<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
@@ -777,16 +916,18 @@ constraints</em>.</p>
<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 text">constraints = {
- 'host': 'limit:2',
+<pre class="highlight plaintext"><code>constraints = {
+ 'host': 'limit:2',
}
-</pre>
+</code></pre>
+
<p>Likewise, you can use constraints to control rack diversity, e.g. at
most one task per rack:</p>
-<pre class="highlight text">constraints = {
- 'rack': 'limit:1',
+<pre class="highlight plaintext"><code>constraints = {
+ 'rack': 'limit:1',
}
-</pre>
+</code></pre>
+
<p>Use these constraints sparingly as they can dramatically reduce
Tasks’ schedulability.</p>
<h1 id="template-namespaces">Template Namespaces</h1>
@@ -857,60 +998,64 @@ to map <code>http</code> to port 12345 w
<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 text">import os
-hello_world_process = Process(name = 'hello_world', cmdline =
'echo hello world')
+<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'),
+ cluster = 'cluster1',
+ role = os.getenv('USER'),
task = hello_world_task)
jobs = [hello_world_job]
-</pre>
+</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 text">aurora job create cluster1/$USER/test/hello_world
hello_world.aurora
+<pre class="highlight plaintext"><code>aurora job create
cluster1/$USER/test/hello_world hello_world.aurora
aurora job kill cluster1/$USER/test/hello_world
-</pre>
+</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 text">include('hello_world.aurora')
+<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}}"
+ 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),
+ hello_world_template(cluster = 'cluster1', instances = 25),
+ hello_world_template(cluster = 'cluster2', instances = 15),
# staging jobs
hello_world_template(
- cluster = 'local',
+ cluster = 'local',
instances = 1,
task = hello_world(resources=staging_resources)),
]
-</pre>
+</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 text">aurora job create
cluster1/$USER/test/hello_world-cluster1 hello_world_productionized.aurora
+<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
-</pre></div>
+</code></pre>
+
+</div>
</div>
</div>
-
<div class="container-fluid section-footer buffer">
<div class="container">
<div class="row">
@@ -935,5 +1080,6 @@ aurora job kill cluster1/$USER/test/hell
</div>
</div>
</div>
+
</body>
</html>
\ No newline at end of file
