Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: v1.4

Template in scheduler/

Scheduler templates select registered hook aliases and pass their parameters. The fixed policy below illustrates the current source-selection, deployment, and per-task scheduling contracts.

position: cloud
pod-template:
image: scheduler
imagePullPolicy: Always
env:
- name: SCH_CONFIG_EXTRACTION_NAME
value: simple
- name: SCH_SCENARIO_RETRIEVAL_NAME
value: simple
- name: SCH_STARTUP_POLICY_NAME
value: fixed
- name: SCH_POLICY_RETRIEVAL_NAME
value: simple
- name: SCH_SELECTION_POLICY_NAME
value: fixed
- name: SCH_SELECTION_POLICY_PARAMETERS
value: >
{
'scope': 'all_edge_nodes',
'fixed_value': 'edgex1',
'fixed_type':'hostname'
}
- name: SCH_INITIAL_DEPLOYMENT_POLICY_NAME
value: fixed
- name: SCH_INITIAL_DEPLOYMENT_POLICY_PARAMETERS
value: >
{
'policy':{
"vehicle-detection": ["edge5"],
"pedestrian-detection": ["edge5"],
"category-identification": ["edgexn8"],
"license-plate-recognition": ["edgexn11", "edgexn12"],
"exposure-identification": ["edgexn11", "edgexn12", "edgexn8"]
}
}
- name: SCH_REDEPLOYMENT_POLICY_NAME
value: fixed
- name: SCH_REDEPLOYMENT_POLICY_PARAMETERS
value: >
{
'policy':{
"vehicle-detection": ["edge5"],
"pedestrian-detection": ["edge5"],
"category-identification": ["edgexn8"],
"license-plate-recognition": ["edgexn11", "edgexn12"],
"exposure-identification": ["edgexn11", "edgexn12", "edgexn8"]
}
}
- name: SCH_AGENT_NAME
value: fixed
- name: SCH_AGENT_PARAMETERS
value: >
{
'configuration':{
'resolution': '720p',
'fps': 10,
'encoding': 'mp4v',
'buffer_size': 4
},
'offloading':{
'pedestrian-detection':'edge5',
'exposure-identification':'edgexn12',
'vehicle-detection':'edge5',
'category-identification':'edgexn8',
'license-plate-recognition':'edgexn11'
}
}
port-open:
pos: cloud
port: 9000
file-mount:
- pos: cloud
path: 'scheduler/fixed/'

Replace the example hostnames and service map with nodes and DAG services available to the installation. Backend and Scheduler reject missing services, empty placements, and nodes outside the authorized candidate set. Deployment hooks return a complete logical service -> node list plan; they do not create Kubernetes resources or discover topology.