From de41f3db4ebbcf8a1cf398f43daee0abd863f8e6 Mon Sep 17 00:00:00 2001 From: Baptiste Jonglez Date: Thu, 29 Dec 2022 14:22:28 +0100 Subject: [PATCH] Document how to run jobs --- doc/architecture.md | 19 +++++++++++++++++++ doc/onboarding.md | 2 +- 2 files changed, 20 insertions(+), 1 deletion(-) diff --git a/doc/architecture.md b/doc/architecture.md index 53032c2..36f3798 100644 --- a/doc/architecture.md +++ b/doc/architecture.md @@ -143,6 +143,25 @@ $ nomad operator scheduler get-config --json ### Launching services +To launch a service, e.g. `app/core`, use `nomad plan` first: + +``` +cd cluster/staging/app/core/deploy +nomad plan core-system.hcl +``` + +If the diff looks fine, then you can run the job for real +(the index is printed in the output of `nomad plan`): + +``` +nomad job run -check-index NNN core-system.hcl +``` + +There may be several jobs in the same directory, for instance +`core-system.hcl` and `core-service.hcl`. + +### Which services to launch + Stuff should be started in this order: 1. `app/core` diff --git a/doc/onboarding.md b/doc/onboarding.md index b3bd264..585ec84 100644 --- a/doc/onboarding.md +++ b/doc/onboarding.md @@ -12,7 +12,7 @@ Basically: - Finally, the new administrator must choose a password to operate over SSH with `./passwd prod rick` where `rick` is the target username -## How to operate a node (conncet to Nomad and Consul) +## How to operate a node (connect to Nomad and Consul) Edit your `~/.ssh/config` file with content such as the following: