Skip to content

feat: run a user-data script on the nodes - #67

Closed
m4nch0t wants to merge 1 commit into
mainfrom
feature/instance-user-data
Closed

m4nch0t wants to merge 1 commit into
mainfrom
feature/instance-user-data

Conversation

@m4nch0t

@m4nch0t m4nch0t commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

instance_user_data names a script every node runs once booted, to install a product for instance.
examples/user-data/artesca-install.sh installs ARTESCA from its AMI on one node or three, and QUICKSTART walks through spawning both.

`instance_user_data` names a script every node runs once booted, to
install a product for instance. It runs as a systemd unit of its own
rather than inside cloud-init, so the boot wait is not held by it, and
from /usr/local/libexec, where SELinux leaves it unconfined. Under the
configuration directory it ran in the domain of init, which may not
even run chage or write /etc/shadow.

The script learns where its node stands from /etc/platform-spawner/node.env.
Once the machines have booted, the nodes are handed the key of the
bastion over SSH, so that one of them can drive the others.

examples/user-data/artesca-install.sh installs ARTESCA from its AMI on
one node or three, and QUICKSTART walks through spawning both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@m4nch0t m4nch0t self-assigned this Oct 30, 2026
@m4nch0t
m4nch0t requested a review from a team as a code owner October 30, 2026 14:48
@m4nch0t m4nch0t closed this Oct 30, 2026
@m4nch0t
m4nch0t deleted the feature/instance-user-data branch October 30, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant