mirror of
https://github.com/kemko/nomad.git
synced 2026-01-06 10:25:42 +03:00
53b083b8c5
* Move commands from docs to its own root-level directory * temporarily use modified dev-portal branch with nomad ia changes * explicitly clone nomad ia exp branch * retrigger build, fixed dev-portal broken build * architecture, concepts and get started individual pages * fix get started section destinations * reference section * update repo comment in website-build.sh to show branch * docs nav file update capitalization * update capitalization to force deploy * remove nomad-vs-kubernetes dir; move content to what is nomad pg * job section * Nomad operations category, deploy section * operations category, govern section * operations - manage * operations/scale; concepts scheduling fix * networking * monitor * secure section * remote auth-methods folder and move up pages to sso; linkcheck * Fix install2deploy redirects * fix architecture redirects * Job section: Add missing section index pages * Add section index pages so breadcrumbs build correctly * concepts/index fix front matter indentation * move task driver plugin config to new deploy section * Finish adding full URL to tutorials links in nav * change SSO to Authentication in nav and file system * Docs NomadIA: Move tutorials into NomadIA branch (#26132) * Move governance and policy from tutorials to docs * Move tutorials content to job-declare section * run jobs section * stateful workloads * advanced job scheduling * deploy section * manage section * monitor section * secure/acl and secure/authorization * fix example that contains an unseal key in real format * remove images from sso-vault * secure/traffic * secure/workload-identities * vault-acl change unseal key and root token in command output sample * remove lines from sample output * fix front matter * move nomad pack tutorials to tools * search/replace /nomad/tutorials links * update acl overview with content from deleted architecture/acl * fix spelling mistake * linkcheck - fix broken links * fix link to Nomad variables tutorial * fix link to Prometheus tutorial * move who uses Nomad to use cases page; move spec/config shortcuts add dividers * Move Consul out of Integrations; move namespaces to govern * move integrations/vault to secure/vault; delete integrations * move ref arch to docs; rename Deploy Nomad back to Install Nomad * address feedback * linkcheck fixes * Fixed raw_exec redirect * add info from /nomad/tutorials/manage-jobs/jobs * update page content with newer tutorial * link updates for architecture sub-folders * Add redirects for removed section index pages. Fix links. * fix broken links from linkcheck * Revert to use dev-portal main branch instead of nomadIA branch * build workaround: add intro-nav-data.json with single entry * fix content-check error * add intro directory to get around Vercel build error * workound for emtpry directory * remove mdx from /intro/ to fix content-check and git snafu * Add intro index.mdx so Vercel build should work --------- Co-authored-by: Tu Nguyen <im2nguyen@gmail.com>
47 lines
1.8 KiB
Plaintext
47 lines
1.8 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Run Nomad jobs
|
|
description: |-
|
|
This section provides guidance for running Nomad jobs. Inspect job, access logs for troubleshooting, collect resource utilization metrics, and create job versions.
|
|
---
|
|
|
|
# Run Nomad jobs
|
|
|
|
This section provides guidance for running Nomad jobs. Inspect job, access logs
|
|
for troubleshooting, collect resource utilization metrics, and create job
|
|
versions.
|
|
|
|
The following list is the general flow for operating a job in Nomad:
|
|
|
|
1. Declare the job according to the [job specification](/nomad/docs/job-specification).
|
|
1. Plan and review the changes with a Nomad server.
|
|
1. Submit the job file to a Nomad server.
|
|
1. (Optional) Review job status and logs.
|
|
|
|
Refer to [Create and submit a job](/nomad/docs/job-declare/create-job) to learn
|
|
how to create a job specification, review the job plan, and submit the job.
|
|
|
|
## Run a job
|
|
|
|
Execute the [`nomad job run` command](/nomad/commands/job/run) to run your job.
|
|
|
|
Now that the job is scheduled, it may or may not be running. You need to inspect
|
|
the allocation status and logs to make sure the job started correctly. Refer to
|
|
the section on [inspecting state](/nomad/docs/job-run/inspect)
|
|
details ways to examine this job's state.
|
|
|
|
## Update a running job
|
|
|
|
When updating a job, there are a number of [built-in update
|
|
strategies](/nomad/docs/job-declare/strategy) which may be defined in the job
|
|
file. The general flow for updating an existing job in Nomad is:
|
|
|
|
1. Modify the existing job file with the desired changes.
|
|
1. Plan and review the changes with a Nomad server.
|
|
1. Submit the job file to a Nomad server.
|
|
1. (Optional) Review job status and logs.
|
|
|
|
Because the job specification defines the deployment strategy, the workflow
|
|
remains the same regardless of whether this is an initial deployment or a
|
|
long-running job.
|