X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/42d491072c6757a68cbc597961237a1566de4172..b4f172a329980127db895becda91543fd65b6b39:/doc/admin/spot-instances.html.textile.liquid diff --git a/doc/admin/spot-instances.html.textile.liquid b/doc/admin/spot-instances.html.textile.liquid index 07b7215029..703e70fb86 100644 --- a/doc/admin/spot-instances.html.textile.liquid +++ b/doc/admin/spot-instances.html.textile.liquid @@ -16,31 +16,57 @@ Currently Arvados supports preemptible instances using AWS and Azure spot instan h2. Configuration -To use preemptible instances, set @UsePreemptibleInstances: true@ and add entries to @InstanceTypes@ with @Preemptible: true@ to @config.yml@. 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 will likely be lower. For example: +First, configure some @InstanceTypes@ that have @Preemptible: true@. For a preemptible instance, @Price@ determines the maximum bid price; the actual price paid is dynamic and will likely be lower. + +Typically you want to add both preemptible and non-preemptible entries for each cloud provider VM type. To do this automatically, use @PreemptiblePriceFactor@ to enable a preemptible version of each listed type, using the given factor to set the maximum bid price relative to the non-preemptible price. Alternatively, you can configure preemptible instance types explicitly. For example, the following two configurations are equivalent:
Clusters: - ClusterID: + ClusterID: Containers: - UsePreemptibleInstances: true + PreemptiblePriceFactor: 0.8 InstanceTypes: m4.large: - Preemptible: false ProviderType: m4.large VCPUs: 2 RAM: 8GiB AddedScratch: 32GB Price: 0.1 - m4.large.spot: - Preemptible: true ++ +
+Clusters: + ClusterID: + InstanceTypes: + m4.large: ProviderType: m4.large VCPUs: 2 RAM: 8GiB AddedScratch: 32GB Price: 0.1 + m4.large.preemptible: + Preemptible: true + ProviderType: m4.large + VCPUs: 2 + RAM: 8GiB + AddedScratch: 32GB + Price: 0.08 ++ +Next, you can choose to enable automatic use of preemptible instances: + +
+Clusters: + ClusterID: + Containers: + AlwaysUsePreemptibleInstances: true-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 @AlwaysUsePreemptibleInstances@ is "true", child containers (workflow steps) will always select preemptible instances, regardless of user option. + +If @AlwaysUsePreemptibleInstances@ is "false" (the default) or unspecified, preemptible instance are "used when requested by the user.":{{site.baseurl}}/user/cwl/cwl-run-options.html#preemptible + +Note that regardless of the value of @AlwaysUsePreemptibleInstances@, the top level workflow runner container always runs in a reserved (non-preemptible) instance, to avoid situations where the workflow runner is killed requiring the entire to be restarted. No additional configuration is required, "arvados-dispatch-cloud":{{site.baseurl}}/install/crunch2-cloud/install-dispatch-cloud.html will now start preemptible instances where appropriate.