Otter Documentation

Jobs & Scheduling Changes

Jobs allows you to remediate configuration drift and run orchestration plans, either on-demand, at a scheduled time, or on a recurring basis. They can help to minimize downtime and can be set to run when convenient or most appropriate for your enterprises. Jobs give you the control of when, where, and how your infrastructure changes.

Jobs ultimately target Servers, and can do so either directly (by specifying a list of servers), or indirectly (by specifying Server Roles and/or Environments). And just as there are two types of plans, there are effectively the same two types of jobs:

  • Configuration Job - remediates configuration drift by bringing the targeted servers to their desired configuration
  • Orchestration Job - runs a specified orchestration plan against the targeted servers

Either type of jobs can be run immediately (for example, test servers in unexpected drift), at scheduled times in the future (planned changes to a production server), or on a recurring basis (adding more servers at known peak times).

Configuration Jobs

When there is configuration drift on a server or role (and you have permission to create a configuration job), you can simply click the Remdiate Drift button to schedule a configuration job.

Remediation Job in Otter

You can also create a configuration job by clicking on [Jobs] > [Create Job], or create a recurring configuration job (such as updating production servers onces a week) by [Jobs] > [Recuring] > [Create Recurring Job].

Orchestration Jobs

Orchestration jobs are created on the jobs page, and require the selection of an orchestration plan and servers to run against.

Orchestration Job in Otter

Job Templates

You can also define a job template under [Admin] > [Job Templates]; these can be used to pre-populate fields in an orchestration job, and also allow for jobs to be triggered using the Job Orchestration API.

Job Templates in Otter

Simulation Job Runs

You can run a job in a simulation mode, which will run all of the steps in any plan without making any changes to the targeted servers. When a simulation is run Otter, will still follow the logic you define in your plan, and log all of the things it's doing, and will log the changes that would have been made if the job was running normally. This can be helpful when running jobs against unknown servers, remediating unexpected drift, or performing changes on high value servers.

Simulation Job in Otter

Simulating a job can help ensure future accuracy by finding any errors that might have occurred in a plan, without effecting current configurations.