Run or exclude specific job types
3 minute read
This is controlled by environment variables CBJE_INCLUDE_JOB_TYPES and CBJE_EXCLUDE_JOB_TYPES. Each accepts a comma-separated list of job types, using the type names in the table below.
Set the variables
| Variable | Effect |
|---|---|
CBJE_INCLUDE_JOB_TYPES |
The job engine runs only jobs of the listed types. |
CBJE_EXCLUDE_JOB_TYPES |
The job engine runs everything except jobs of the listed types. |
Jobs of an excluded type stay PENDING until another job engine claims them. If no other job engine runs them, they never run.
Set these variables in /etc/supervisord.d/jobengine.conf. Quote the value, because Supervisor also separates variables with commas.
environment=PATH=/usr/local/bin:/bin:/usr/bin,CBJE_INCLUDE_JOB_TYPES="provision,expire,decom"
Reload Supervisor to apply the setting: supervisorctl reload.
A name that is not a job type prevents the job engine from starting, and it reports that the specified type is invalid. Check the job engine log after a reload.
Find a job’s type
The Type filter on the Jobs list shows every type with the number of jobs of that type. To read the type of a specific job, open shell_plus on the appliance:
sudo su -
/opt/cloudbolt/manage.py shell_plus
Then ask for the job by its ID, which is the number at the end of the heading on the job’s detail page:
Job.objects.get(pk=JOB_ID).type
Job types
The left column is the variable value to use. The right column is the display name in the UI.
| Job type | Shown as |
|---|---|
provision |
Provision Server |
decom |
Delete Server |
healthcheck |
Health Check |
expire |
Expire |
import_parameters |
Import Parameters |
import_images |
Import Images for Resource Handler |
import_ipam_networks |
Import IPAM Networks |
servermodification |
Server Modification |
deploy_blueprint |
Deploy Blueprint |
install_pod |
Install Container Object |
installapplications |
Install Applications |
uninstallapplications |
Uninstall Applications |
syncvms |
Synchronize VMs from Resource Handlers |
sync_svrs_from_pe |
Synchronize servers from Provision Engines |
functionaltest |
Continuous Infrastructure Testing |
runautomations |
Execute Rules |
runautomationactions |
Execute Rule Actions |
sync_users_from_ldap |
Synchronize users from an LDAP server |
run_flow |
Orchestration Flow |
install_apps_with_connector |
Install Applications with Configuration Manager |
manage_nics |
Manage NICs |
orchestration_hook |
Orchestration Action |
delete_snapshots |
Delete Snapshots |
action |
Action |
run_policy_action |
Run Policy Action |
apply_personality |
Apply Personality |
procedure |
Procedure |
create_child_rh |
Create Child Resource Handlers |
create_cross_account_access_iam_role |
Create Cross Account Access IAM Role |
import_regions_for_ou_account_rh |
Import Regions For Organization Accounts Resource Handler |
create_subscription_rh |
Create Subscription Resource Handlers |
sync_rh_environments |
Sync Resource Handler Regions |
sync_rh_ssh_key_pairs |
Sync Resource Handler SSH Key Pairs |
sync_rh_security_groups |
Sync Resource Handler Security Groups |
sync_rh_networks |
Sync Resource Handler Networks |
sync_rh_datastores |
Sync Resource Handler Datastores |
sync_rh_metadata |
Sync Resource Handler Metadata |
sync_container_orchestrators_resources |
Sync Container Orchestrator Resources |
import_multiple_selected_contents |
Import Multiple Selected Contents in CMP |
satelliterequest |
Satellite Fulfillment Request |
flowcontrol_verify_paused |
Flow Control Verify Paused Orders/Jobs |
sourcecodereposync |
Source Code Repository Sync |
Related
- Job engine: How jobs move through the engine and the settings that control the workers.
- Job engine troubleshooting: What to check when one type of job looks stuck.