Project

General

Profile

Actions
Copy link

Feature #20520

closed

[arvados-dispatch-cloud] configurable instance initialization script

Added by Tom Clegg over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Tom Clegg
Category:
Crunch
Target version:
Development 2023-06-07
Story points:
-
Release:
Arvados 2.6.3
Release relationship:
Auto

Description

Currently a-d-c sends a bash script to new cloud instances (as "CustomData" on Azure, "UserData" on EC2) in order to stash a secret string on the instance, which is checked upon first SSH connection as an alternative to verifying the instance's SSH host key fingerprint.

This proposed feature would allow the operator to use the CustomData/UserData feature for additional instance setup tasks.

  CloudVMs:
    InstanceInitCommand: "echo ok\nexit 0\n"

This command/script, if configured, would be appended to Arvados's existing builtin bash script.

Subtasks 1 (0 open — 1 closed)

Task #20550: Review 20520-instance-init-commandResolvedTom Clegg05/25/2023Actions
Actions
Copy link
 #1

Updated by Tom Clegg over 1 year ago

  • Target version changed from Future to Development 2023-05-24 sprint
  • Assigned To set to Tom Clegg
  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by Tom Clegg over 1 year ago

  • Target version changed from Development 2023-05-24 sprint to Development 2023-06-07
Actions
Copy link
 #4

Updated by Brett Smith over 1 year ago

  • Release set to 64
Actions
Copy link
 #6

Updated by Brett Smith over 1 year ago

Tom Clegg wrote in #note-5:

20520-instance-init-command @ aec8a66deeff226db672351cd3ab803bf01a186d -- developer-run-tests: #3664

Everything here is great. Is there anywhere that makes sense to document this option and why you might use it? Maybe the "Install the cloud dispatcher" docs?

Actions
Copy link
 #7

Updated by Tom Clegg over 1 year ago

I haven't figured out where to mention this in the docs, beyond the existing catch-all "see entire config defaults file for more options". But while looking, I found and fixed
  • an unreleased mutex in the EC2 driver (Why do the docs say to install the dispatcher public key on the compute image, even though we also that automatically in both drivers? Still not sure, but here's a thing to fix...)
  • a broken link on the "compute image" page

20520-instance-init-command @ 8b1f870373af47287e916bb0ec16a3bdf09b62cb -- developer-run-tests: #3669

Actions
Copy link
 #8

Updated by Brett Smith over 1 year ago

Tom Clegg wrote in #note-7:

20520-instance-init-command @ 8b1f870373af47287e916bb0ec16a3bdf09b62cb -- developer-run-tests: #3669

Looks good to me, please merge. Thanks.

Actions
Copy link
 #9

Updated by Tom Clegg over 1 year ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF