Jobs

Jobs List

A provisioning job represents a provisioning action in an environment. At any given time only one job can be executed on an environment. The job list in the environment shows:

• The start date and time of each job.

• The identity of the user who initiated the job.

• The action that was taken: apply, preview, or destroy.

• The status of that job:

  • credentialing (credentials are being generated and verified)

  • one of the three phases (see below)

  • succeeded

  • failed

Each job proceeds through three phases that are necessary for correct provisioning:

• Preparing aligns resources and performs venue-specific transformations.

• Previewing simulates the provisioning and looks for errors so that the job will fail as early as possible.

• Executing is the actual provisioning operation on the venue.

For example if there are 5 resources to be provisioned, all of them will be prepared, then previewed, then executed. Each of these operations is called a step. Steps run in parallel wherever possible based on the dependency tree calculated by Tuono for the combination of the blueprints and variables in the environment.

Job Overview

If you click on one of the jobs in the environment detail view, you can examine more details about that job. The overview shows you the resources that were provisioned and the state of the prepare / preview / execute operations on them. If something failed the status will be red; if something generated a warning then the status will be orange; otherwise it will be green:

Job Details

In the detail view you can see more details about the execution of the job. When changes are made to the venue, a link appears that you can use to inspect those changes at a venue-specific detail level:

If you click on the link to inspect changes, you will see a venue-specific structure in before and after form. In this example, an AWS VPC is being created, so there is no "before" form: