Bug #15660

[doc] update aws spot instance doc page for a-d-c

Added by Ward Vandewege over 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
-
Start date:
10/29/2019
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto


Subtasks

Task #15753: Review 15660-aws-spot-docIn ProgressPeter Amstutz

Associated revisions

Revision cceeee64
Added by Peter Amstutz about 2 years ago

Merge branch '15660-aws-spot-doc' refs #15660

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <>

History

#1 Updated by Ward Vandewege over 2 years ago

  • Description updated (diff)

#2 Updated by Tom Morris over 2 years ago

  • Target version changed from To Be Groomed to 2019-11-06 Sprint

#3 Updated by Peter Amstutz about 2 years ago

  • Assigned To set to Peter Amstutz

#4 Updated by Peter Amstutz about 2 years ago

15660-aws-spot-doc @ 6bec4e92eb3362fb0dabba0d642c33c97cc3742e

Reorganize page to focus on InstanceTypes in config.yml

#5 Updated by Peter Amstutz about 2 years ago

  • Status changed from New to Resolved

#6 Updated by Peter Amstutz about 2 years ago

  • Status changed from Resolved to In Progress

#7 Updated by Tom Clegg about 2 years ago

preemptable → preemptible (and nonpreemptable → non-preemptible / regular / normal (GCE) / on-demand (AWS))

I think it's worth picking one term ("preemptible" or "spot") and sticking to it, only mentioning the other one as a synonym once early on, rather than using them interchangeably throughout. Probably "preemptible" since it's more generic and that's how it appears in our configs/logs.

Nit: I think it just adds information noise to use the term Crunch here -- maybe "how to set up crunch to take advantage" could just be "how to set up Arvados to take advantage"? If we do stick with crunch it seems like it should be capitalized for readability.

I notice we're referring to node manager as "legacy" even though arvados-dispatch-cloud still has an "experimental" warning -- but #13908 is on the map for 1.5, so I added #15775 and #15776 as blockers for that to make sure we bring the a-d-c/nodemanager pages up to speed with this one.

#8 Updated by Peter Amstutz about 2 years ago

  • Target version deleted (2019-11-06 Sprint)

Tom Clegg wrote:

preemptable → preemptible (and nonpreemptable → non-preemptible / regular / normal (GCE) / on-demand (AWS))

Fixed.

I think it's worth picking one term ("preemptible" or "spot") and sticking to it, only mentioning the other one as a synonym once early on, rather than using them interchangeably throughout. Probably "preemptible" since it's more generic and that's how it appears in our configs/logs.

Reworked the text a bit to use "preemptible" when talking about the general Arvados feature and "spot" when talking about AWS specifically.

Nit: I think it just adds information noise to use the term Crunch here -- maybe "how to set up crunch to take advantage" could just be "how to set up Arvados to take advantage"? If we do stick with crunch it seems like it should be capitalized for readability.

Too many words. Cut the sentence down to just "how to enable preemptible instances".

I notice we're referring to node manager as "legacy" even though arvados-dispatch-cloud still has an "experimental" warning -- but #13908 is on the map for 1.5, so I added #15775 and #15776 as blockers for that to make sure we bring the a-d-c/nodemanager pages up to speed with this one.

Sounds good to me.

#9 Updated by Tom Clegg about 2 years ago

LGTM, thanks

#10 Updated by Peter Amstutz about 2 years ago

  • Status changed from In Progress to Resolved

#11 Updated by Peter Amstutz almost 2 years ago

  • Release set to 22

Also available in: Atom PDF