Worker Model

Description

Worker model can be defined ascode. That’s mean the definition of the worker model will be in a git repository, and each time you will push something, CDS will update it.

As Code directory

A workflow is described directly on your repository inside the directory .cds/worker-models

Permission

To be able to manage a workflow you will need the permission manage-worker-model on your project

Files

*: mandatory field

Docker

name: my-worker-model-name
description: my description
osarch: linux/amd64
type: docker
spec:
  image: myregistry.org/ns/myworkermodel:1.0
  username: foo
  password: bar
  envs:
    myvar: myvalue

Fields:

• *name: Name of the worker model
• description: Description of the worker model
• *type: Type of worker model
• *osarch: OS and architecture of the model
• *spec.image: Docker image name
• spec.username: Docker registry username
• spec.password: Docker registry password. The field must be encrypted with cdsctl
• spec.envs: Additional environment variables

Openstack

name: my-worker-model-name
description: my description
type: openstack
osarch: linux/amd64
spec: 
  image: Ubuntu

Fields:

• *name: Name of the worker model
• description: Description of the worker model
• *osarch: OS and architecture of the model
• *type: Type of worker model
• *spec.image: Openstack image name

vSphere

name: my-worker-model-name
description: my description
osarch: linux/amd64
type: vsphere
spec:
  image: Ubuntu
  username: foo
  password: bar

Fields:

• *name: Name of the worker model
• description: Description of the worker model
• *osarch: OS and architecture of the model
• *type: Type of worker model
• *spec.image: vSphere template name
• *spec.username: username to use to connect to the VM
• *spec.password: password to use to connect to the VM. The field must be encrypted with cdsctl