Skip to main content
Version: v3.9.0

AI Model Catalog

A fleet model is a registry-backed artifact on the Controller, such as weights or a GGUF bundle. It is not a container. Attach it to the Edgelet nodes that should hold a copy, then bind it on the microservice.

The short map is Models and knowledge. Fields are on Model fields.

A Model and a Knowledge object may share a name. They are separate lists.

When to use it​

Use kind: Model when the artifact lives in a registry and more than one Edgelet node may need it. The registry row must exist. Aliases remote and local are valid. A new registry id is known only after get registries.

What deploy does​

potctl deploy -f model.yaml -n my-ecn

Deploy upserts by metadata.name. A missing name creates the row. The same name updates repo, revision, files, format, or the registry reference. Omit spec.uuid. The Controller decides whether linked nodes need a refresh.

model.yaml
apiVersion: datasance.com/v3
kind: Model
metadata:
  name: defect-weights
  namespace: my-ecn
spec:
  repo: org/defect-weights
  registry: remote
  format: gguf

How a microservice uses it​

Attach the model to the Edgelet node first. Then set spec.models on the microservice. Item names match metadata.name. The field shape is on Microservice fields.

bind.yaml
apiVersion: datasance.com/v3
kind: Microservice
metadata:
  name: line-monitor/reader
spec:
  models:
    items:
      - name: defect-weights

A model-only change on an existing microservice can use deploy -f --patch-model. See Microservices.

CLI​

potctl get models -n my-ecn
potctl describe model defect-weights -n my-ecn
potctl attach model defect-weights edge-01 -n my-ecn
potctl detach model defect-weights edge-01 -n my-ecn
potctl delete model defect-weights -n my-ecn

describe model includes status.linkedAgents. attach model and detach model take the model name and one or more Edgelet node names. Confirm modelStatus and activeModels with describe agent. Delete can fail while a microservice or a link still uses the model.

Edgelet-local models​

On-node model files use edgelet deploy. That path has no Controller catalog row and no attach model. See Models.

Console​

Config → AI Model Catalog lists models, edits YAML, and attaches nodes. See Catalog and templates.

Group 3See anything wrong with the document? Help us improve it!

Edit this page on GitHub!