Model commands
The akka models commands deploy models to an inference cluster, expose them on a hostname, and record what an organization sanctions. See Serving models for the tasks these commands support, and Model descriptor for the file they apply.
Every command supports --help. Most support -o json for output consumed by another program. validate and export accept the flag and ignore it, and always print their usual format.
Model deployments
A deployment is one serving engine running one model on an accelerator.
| Command | Description |
|---|---|
|
Every deployment, with the model it serves, its KV token budget, its concurrency estimate, and whether it is ready. |
|
One deployment. When a model is not ready, this prints the reason in plain text. |
|
Wait for a deployment to become ready. The first deployment downloads the weights, so this takes several minutes. |
|
Check a descriptor offline. Reports every problem in the file at once and deploys nothing. |
|
Create or update everything the descriptor names. Safe to repeat: it updates what changed and leaves the rest alone. |
|
Run the checks that need the cluster, without persisting anything. |
|
Remove what the descriptor names, routes first. Cached weights survive. |
|
Remove what the descriptor names and the cached weights with it. |
|
Delete a single deployment by name, without a descriptor. |
|
Write everything running back out as a descriptor, routes included. Secret values are masked with |
list reports MAX CONC, the number of concurrent requests the KV cache comfortably holds at the configured context length. It is a sizing estimate rather than a limit, and nothing enforces it.
Proxying to a deployment
| Command | Description |
|---|---|
|
Open a local tunnel to one deployment on |
The tunnel reaches one model, so the model field of a request body is echoed back rather than used to choose between models.
Devices
A device is a kind of GPU the platform has in a region. Devices are inventory and cannot be created from a descriptor or from the CLI.
| Command | Description |
|---|---|
|
Every kind of GPU available in the region, with its memory, architecture, and how many cards are free. |
|
The individual cards behind one device name, and what is running on each. |
Accelerators
An accelerator claims a slice of the device inventory. A deployment is placed on an accelerator, never on a device.
| Command | Description |
|---|---|
|
Every accelerator, its device, its tenancy, and its free slots. |
|
One accelerator, stating the hardware, the tenancy, and the free slots in one line. |
|
Create an accelerator with dedicated tenancy. |
|
Create an accelerator that splits one device between |
|
Remove an accelerator, releasing the capacity it held. |
|
|
An accelerator is immutable once it exists. Applying a descriptor leaves an existing accelerator alone rather than reshaping it.
Routes
A route gives a set of deployments one hostname. Clients choose between the models on it with the model field of the request body.
| Command | Description |
|---|---|
|
Every hostname, the models on it, and whether it requires a key. |
|
One route: its endpoint, the model names it accepts, the state of each deployment, and why a route is not ready. |
routes get reports Accepts, the list of names clients may send as model. Adapter names appear there alongside the base name of the deployment that serves them.
API keys
A route refuses every request until a key authorizes it. Keys are issued per client.
| Command | Description |
|---|---|
|
Issue a key for one client. The value is shown once and cannot be read back. |
|
Which clients hold a key. Never the keys themselves. |
|
Revoke one client’s key. |
|
Deleting a route does not revoke the keys issued against it. Rebuild the route under the same name and every key ever issued to it works again. A key is only gone once |
Model governance
The same akka models noun records which models an organization sanctions and the conditions attached to them. What a model is and what is running are the same resource seen twice, so there is no separate registry listing: list and get, described in Model deployments, read that resource, and the verbs below act on the same names.
| Command | Description |
|---|---|
|
Register a model or update its metadata. |
|
Promote a candidate to active. |
|
Discourage new use of a model. |
|
End the sanction to use a model. |
|
Resolve a decision on the model that owns it. |
|
Record human sign-off closing a risk condition. |
|
Record a time-bound waiver on an open condition. |
|
Turn off a condition that does not apply. |
|
Every condition on a model and its state. |
|
Every attestation recorded against a model. |
|
Record an externally-run evaluation or report. |
|
What may be decided about this model, and how guarded each choice is. |
|
|
The singular alias model is accepted.
|
The features described in this section are an add-on to Akka Automated Operations. They are not included in the base product. |