jschoubben
f118344246
75 endpoints across 50 modules, named from what each one is for rather than by a rule: mail's seven protocol ports are smtp, imaps, submission and the rest; unifi's nine are inform, stun, discovery, the two portal ports and syslog; minio's two are s3 and console; the resolver's two are dns-udp and dns-tcp. And 35 route contributions name the endpoint they serve instead of repeating its port. A route and a listen both carried a port and nothing said they were the same thing; now one of them does. gitea's path-level deny rule names neither, because it is a rule about a name rather than an endpoint. novox/hq ADR 0138. The words shipped a release ahead in mesh-controller #138 and #139, and the control plane running today is built from that merge — checked before this was written, because an unknown manifest key is refused and a catalogue using one against an older control plane would stop resolving.
50 lines
975 B
JSON
50 lines
975 B
JSON
{
|
|
"module": "ollama",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"provides": [
|
|
{
|
|
"name": "model-access",
|
|
"scope": "node"
|
|
}
|
|
],
|
|
"listens": [
|
|
{
|
|
"name": "api",
|
|
"port": 11434,
|
|
"protocol": "tcp",
|
|
"from": "machine",
|
|
"why": "consumers on this machine reaching the local model server's OpenAI-compatible API"
|
|
}
|
|
],
|
|
"serves": {
|
|
"model-access": {
|
|
"port": 11434,
|
|
"model": "llama3.2"
|
|
}
|
|
},
|
|
"resources": [
|
|
{
|
|
"id": "state",
|
|
"type": "directory",
|
|
"path": "/services/ollama",
|
|
"mode": "0700"
|
|
},
|
|
{
|
|
"id": "server",
|
|
"type": "container",
|
|
"name": "ollama",
|
|
"image": "ollama/ollama@sha256:32931b46719f673c05fdbaa81ccb26da18ea4a1c57590a754874ab28ba269eb2",
|
|
"network": "host",
|
|
"env": {
|
|
"OLLAMA_HOST": "0.0.0.0:11434"
|
|
},
|
|
"volumes": [
|
|
"/services/ollama:/root/.ollama"
|
|
]
|
|
}
|
|
]
|
|
}
|