Feature #20520
closed
[arvados-dispatch-cloud] configurable instance initialization script
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.
Updated by Tom Clegg 11 months ago
20520-instance-init-command @ 45b46550ecadf69a09390b4cefe3f16d5c1c7453 -- developer-run-tests: #3659
Updated by Tom Clegg 11 months ago
20520-instance-init-command @ aec8a66deeff226db672351cd3ab803bf01a186d -- developer-run-tests: #3664
Updated by Brett Smith 11 months 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?
Updated by Tom Clegg 11 months ago
- 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
Updated by Brett Smith 11 months ago
Tom Clegg wrote in #note-7:
20520-instance-init-command @ 8b1f870373af47287e916bb0ec16a3bdf09b62cb -- developer-run-tests: #3669
Looks good to me, please merge. Thanks.