Token

Tokens are used to register new IncusOS servers with Operations Center. The tokens are time bound by an expiration time and usage count limited by a maximum usage count.

Tokens are created by an administrator in Operations Center.

Operations Center allows to then generated pre-seeded installation images (ISO and raw) for easy bootstrapping of new IncusOS servers. The newly installed IncusOS servers will then use the token to self-register with Operations Center.

Token Seed

For each token, zero to many named seed configurations can be created. A seed configuration may contain seed configuration for installation, network settings, applications to be installed as well as seed configuration for the applications themselves.

The details about the installation seed is documented in IncusOS Installation Seed.

The seed configuration is only accepted, if it exclusively contains fields, which are part of the respective seed definition. Unknown fields are rejected.

The seed configuration for Incus (incus.yaml) and for updates (update.yaml) is managed by Operations Center itself and is therefore rejected, if provided as part of a seed configuration.

Seed Configuration (pre-seed.yaml)

The seed configuration has the following structure:

applications:
  version: "1"
  applications:
    - name: incus
    - name: debug
# install:
# ...
# migration_manager:
# ...
network:
  interfaces:
    - name: enp5s0
      hwaddr: enp5s0
      required_for_online: both
      addresses:
      - dhcp4
      - dhcp6
      - slaac
# ...
# operations_center:
# ...

Public Token Seed

A token seed configuration can be made public, which allows fetching of pre-seeded installation images without authentication.