Skip to content

Registries

Registries are the network's shared records: what exists, where it is and how to find it. Most live on the management cluster. Some, such as container and asset stores, can be run by anyone and are listed in a network-wide index.

Two kinds of registry

flowchart LR
    subgraph Catalogs["Catalogs: things you can use"]
        C["Component registry"]
        CR["Container registry index"]
        AR["Assets registry index"]
        SS["Spec store"]
        TS["Template store"]
    end
    subgraph Runtime["Runtime: what is running now"]
        CL["Cluster registry"]
        BL["Block registry"]
        VD["vDAG registry<br/>(+ vDAG controllers)"]
    end
    C -->|"deployed as"| BL
    BL -->|"runs on"| CL
    BL -->|"used by"| VD

Catalogs: things you can use

Registry What it holds Service (NodePort)
Component registry Packaged components that can be deployed as blocks components-registry-svc (30112)
Container registry Index of container registries that hold block images containers-registry-svc (30109)
Assets registry Index of asset stores holding model weights, policy code and other files assets-db-registry-svc (30104)
Spec store Reusable specifications, ready to deploy spec-registry-svc (30107)
Template store Custom specification formats and their parsing policies templates-registry-svc (30106)

Runtime registries: what is running now

Registry What it holds Service (NodePort)
Cluster registry Every cluster in the network clusters-db-service (30101)
Block registry Every block running on any cluster blocks-db-svc (30100)
vDAG registry Every vDAG, and the vDAG controllers that serve them vdag-db-svc (30103)

Documented elsewhere

Registry Page
Policies (rules, executors, functions, graphs) Policies
Inference servers Inference server registry
Model layers and split runners Model splitting
Tasks Tasks DB

Common patterns

All registries follow the same conventions:

  • Create, read, update, delete through REST APIs.
  • Updates use MongoDB-style operators ($set, $push, $addToSet, ...).
  • Search uses MongoDB-style filters ($eq, $gt, $in, $regex, ...). For searches across several registries at once, use the Parser's search and filter.
  • Versioned items (components, specs, templates, policies, assets) have a URI of the form name:version-tag.

Tip

You rarely write to runtime registries directly. They are filled in by the system as you create clusters, blocks and vDAGs through the Parser. Use them to look things up.