[ARVADOS] updated: 1.3.0-1811-g31858ea09
Git user
git at public.curoverse.com
Tue Oct 29 20:42:09 UTC 2019
Summary of changes:
doc/admin/spot-instances.html.textile.liquid | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
via 31858ea09539d37557241a6462504e5f11c82b1a (commit)
from a927ea97a5baeb49a4c102140b24849c03918316 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
commit 31858ea09539d37557241a6462504e5f11c82b1a
Author: Peter Amstutz <pamstutz at veritasgenetics.com>
Date: Tue Oct 29 16:41:14 2019 -0400
15660: Harmonize preemptible / spot instance terms
Better distinguish between the generic feature and AWS specifically.
Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <pamstutz at veritasgenetics.com>
diff --git a/doc/admin/spot-instances.html.textile.liquid b/doc/admin/spot-instances.html.textile.liquid
index 679761e78..4bba0e893 100644
--- a/doc/admin/spot-instances.html.textile.liquid
+++ b/doc/admin/spot-instances.html.textile.liquid
@@ -1,7 +1,7 @@
---
layout: default
navsection: admin
-title: Using AWS Spot instances
+title: Using Preemptible instances
...
{% comment %}
@@ -10,11 +10,13 @@ Copyright (C) The Arvados Authors. All rights reserved.
SPDX-License-Identifier: CC-BY-SA-3.0
{% endcomment %}
-This page describes how to set up crunch to take advantage of "Amazon's EC2 spot instances":https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-instances.html.
+This page describes how to enable preemptible instances. Preemptible instances typically offer lower cost computation with a tradeoff of lower service guarantees. If a compute node is preempted, Arvados will restart the computation on a new instance.
+
+Currently Arvados supports preemptible instances using AWS spot instances.
h2. Configuration
-To use spot instances, set @UsePreemptibleInstances: true@ and add entries to @InstanceTypes@ with @Preemptible: true@ to @config.yml at . Typically you want to add both preemptible and non-preemptible entries for each cloud provider VM type. The @Price@ for preemptible instances is the maximum bid price, the actual price paid is dynamic and may be lower. For example:
+To use preemptible instances, set @UsePreemptibleInstances: true@ and add entries to @InstanceTypes@ with @Preemptible: true@ to @config.yml at . Typically you want to add both preemptible and non-preemptible entries for each cloud provider VM type. The @Price@ for preemptible instances is the maximum bid price, the actual price paid is dynamic and may be lower. For example:
<pre>
Clusters:
@@ -38,13 +40,17 @@ Clusters:
Price: 0.1
</pre>
-When @UsePreemptibleInstances@ is enabled, child containers (workflow steps) will automatically be made preemptable. If the instance running a step is preempted, it will be restarted on a new instance. However, because preempting the workflow runner would cancel the entire workflow, the workflow runner runs in a reserved (nonpreemptable) instance.
+When @UsePreemptibleInstances@ is enabled, child containers (workflow steps) will automatically be made preemptible. Note that because preempting the workflow runner would cancel the entire workflow, the workflow runner runs in a reserved (non-preemptible) instance.
If you are using "crunch-dispatch-cloud":{{site.baseurl}}/install/install-dispatch-cloud.html no additional configuration is required.
If you are using the legacy Nodemanager, "see below":#nodemanager .
-h3. AWS Permissions
+h2. Preemptible instances on AWS
+
+For general information, see "using Amazon EC2 spot instances":https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-instances.html .
+
+h3. Permissions
When requesting spot instances, Amazon's API may return an authorization error depending on how users and permissions are set on the account. If this is the case check logs for this error:
-----------------------------------------------------------------------
hooks/post-receive
--
More information about the arvados-commits
mailing list