llmgw status, start, stop and restart for this machine's services
There was no command to stop or start llmgw on a machine (issue #3). These act on the llmgw units the machine has - mirror, server, agent - or those named, in dependency order, saying what each did. stop leaves a node's engines serving unless --engines. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
2f595f5999
commit
05aa21c4d4
5 files changed
+249
No files matched your search
@@ -2294,6 +2294,21 @@ A cluster set up online becomes offline the same way: `bundle import` on the
|
||||
mirror and control plane, then the `offline:` block in `server.yaml` and a
|
||||
restart.
|
||||
|
||||
## Stopping and starting a machine
|
||||
|
||||
```
|
||||
sudo llmgw status # each llmgw service here, and whether it runs
|
||||
sudo llmgw stop # agent, control plane, mirror — whichever this machine has
|
||||
sudo llmgw start
|
||||
sudo llmgw restart agent # or name one: server, agent, mirror
|
||||
```
|
||||
|
||||
Stopping a node's agent leaves its engines serving — the agent takes them
|
||||
over again when it starts — unless `llmgw stop --engines` stops them too, and
|
||||
the control plane then places their replicas elsewhere. Stopping the leading
|
||||
control plane hands over to a standby within seconds. The whole cluster's
|
||||
state is `llmgw ctl status`.
|
||||
|
||||
## Removing llmgw from a machine
|
||||
|
||||
```
|
||||
|
||||
Reference in new issue
Block a user