968e67547a
- Revised "What is Nomad" copy - Added "Key Features" section with links to task drivers & device plugins with lift-and-shift from README - Added "Who Uses Nomad" section with users, talks, blog posts - Removed Hadoop YARN, Docker Swarm, HTCondor from comparisons - Revamped Guides section - Inserted "Installing Nomad", "Upgrading", "Integrations" as persistent in Guides navbar - Split Installing Nomad into two paths for users (one for Sandbox with "Quickstart", one for Production) - Surfaced "Upgrading" and "Integrations" section from documentation - Changed "Job Lifecycle" section into "Deploying & Managing Applications" - Reworked "Operations" into "Operating Nomad" - Reworked "Security" into "Securing Nomad" - Segmented Namespaces, Resource Quotas, Sentinel into "Governance & Policy" subsection - Reworked "Spark integration" into its own "Analytical Workloads" section
39 lines
1.2 KiB
Markdown
39 lines
1.2 KiB
Markdown
---
|
|
layout: "guides"
|
|
page_title: "Job Lifecycle"
|
|
sidebar_current: "guides-operating-a-job"
|
|
description: |-
|
|
Learn how to deploy and manage a Nomad Job.
|
|
---
|
|
|
|
# Deploying & Managing Applications
|
|
|
|
Developers deploy and manage their applications in Nomad via jobs.
|
|
|
|
This section provides some best practices and guidance for operating jobs under
|
|
Nomad. Please navigate the appropriate sub-sections for more information.
|
|
|
|
## Deploying
|
|
|
|
The general flow for operating a job in Nomad is:
|
|
|
|
1. Author the job file according to the [job specification](/docs/job-specification/index.html)
|
|
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
|
|
|
|
## Updating
|
|
|
|
When updating a job, there are a number of built-in update strategies 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 file defines the update strategy (blue-green, rolling updates,
|
|
etc.), the workflow remains the same regardless of whether this is an initial
|
|
deployment or a long-running job.
|