Customize Template Files
Dayu composes each installation from the YAML files under template/. Clone the system repository on the cloud node and
edit a copy of this directory for the target deployment:
git clone https://github.com/dayu-autostreamer/dayu.git
cd dayu/template
The main layout is:
template/
├── base.yaml
├── scheduler_policies.yaml
├── services.yaml
├── result-visualizations.yaml
├── system-visualizations.yaml
├── scheduler/
├── processor/
├── generator/
├── controller/
├── distributor/
└── monitor/
Catalog and system files
| File | Purpose | Reference |
|---|---|---|
base.yaml | Namespace, Backend RBAC, runtime timeouts, images, mounts, datasource mode, and catalog imports. | Base Template |
scheduler_policies.yaml | Installable policy catalog and each policy's component-template dependencies. | Scheduler Policies |
services.yaml | DAG service catalog and processor-template mapping. | Services |
result-visualizations.yaml | Task-result visualization modules. | Result Visualizations |
system-visualizations.yaml | Runtime and resource visualization modules. | System Visualizations |
Component templates
Files under scheduler/, processor/, generator/, controller/, distributor/, and monitor/ are logical component
templates. Backend combines the selected policy, DAG, source, nodes, image defaults, and mounted files, then renders
immutable Sedna RuntimeService resources. These templates are no longer converted into one application
JointMultiEdgeService.
| Template | Role | Reference |
|---|---|---|
| common fields | Position, image, environment, port, cloud/edge overlays, and host-path mounts. | Common Template |
scheduler/*.yaml | Scheduler hook selection and policy parameters. | Scheduler Template |
processor/*.yaml | AI service image, processor family, queue, model parameters, and files. | Processor Template |
generator/*.yaml | Source-processing and scheduling-request hooks. | Generator Template |
controller/*.yaml | Task forwarding behavior. | Controller Template |
distributor/*.yaml | Result persistence and export service. | Distributor Template |
monitor/*.yaml | Resource and queue-state monitor sets. | Monitor Template |
Backend validates catalog references, node permissions, deployment plans, ports, mounts, and effective environment before route publication. Keep policy-specific model or profile assets under the mounted paths expected by that template.