2016-11-18 16:40:16 -05:00
---
2016-11-19 08:26:25 -05:00
layout: doc-full
2016-11-18 16:40:16 -05:00
title: Management API
permalink: /doc/mgmt1/
2017-04-09 19:41:46 -04:00
redirect_from:
- /doc/mgmt/
2016-11-18 16:40:16 -05:00
---
# Management API
*(This page is the current draft of the proposal. It is not implemented yet.)*
The API should be implemented as a set of qrexec calls. This is to make it easy
to set the policy using current mechanism.
## The calls
2017-03-09 10:39:29 -05:00
| call | dest | argument | inside | return | note |
| ------------------------------------- | --------- | --------- | ----------------------------------------- | --------------------------------------------------------- | ---- |
| `mgmt.vmclass.List` | `dom0` | - | - | `<class>\n` |
2017-03-09 19:08:34 -05:00
| `mgmt.vm.List` | `dom0|<vm>` | - | - | `<name> class=<class> state=<state>\n` |
2017-03-09 10:39:29 -05:00
| `mgmt.vm.Create.<class>` | `dom0` | template | `name=<name> label=<label>` | - |
2017-04-29 17:17:49 -04:00
| `mgmt.vm.CreateInPool.<class>` | `dom0` | template | `name=<name> label=<label> ` < br /> `pool=< pool > pool:< volume > =< pool > ` | - | either use `pool=` to put all volumes there, < br /> or `pool:<volume>=` for individual volumes - both forms are not allowed at the same time
2017-03-09 10:39:29 -05:00
| `mgmt.vm.CreateTemplate` | `dom0` | name | `root.img` | - |
| `mgmt.vm.Clone` | vm | - | `name=<name>` | - |
2017-04-29 17:17:49 -04:00
| `mgmt.vm.CloneInPool` | vm | - | `name=<name> ` < br /> `pool=< pool > pool:< volume > =< pool > ` | - | same as for `mgmt.vm.CreateInPool`
2017-03-09 10:39:29 -05:00
| `mgmt.vm.Remove` | vm | - | - | - |
| `mgmt.label.List` | `dom0` | - | - | `<property>\n` |
| `mgmt.label.Create` | `dom0` | label | `0xRRGGBB` | - |
| `mgmt.label.Get` | `dom0` | label | - | `0xRRGGBB` |
2017-04-15 07:59:22 -04:00
| `mgmt.label.Index` | `dom0` | label | - | `<label-index>` |
2017-03-09 10:39:29 -05:00
| `mgmt.label.Remove` | `dom0` | label | - | - |
| `mgmt.property.List` | `dom0` | - | - | `<property>\n` |
2017-04-29 17:17:49 -04:00
| `mgmt.property.Get` | `dom0` | property | - | `default={yes|no} ` < br /> `type={str|int|bool|vm|label} < value > ` |
2017-03-09 10:39:29 -05:00
| `mgmt.property.Help` | `dom0` | property | - | `help` |
| `mgmt.property.HelpRst` | `dom0` | property | - | `help.rst` |
| `mgmt.property.Reset` | `dom0` | property | - | - |
| `mgmt.property.Set` | `dom0` | property | value | - |
| `mgmt.vm.property.List` | vm | - | - | `<property>\n` |
| `mgmt.vm.property.Get` | vm | property | - | `default={yes|no} <value>` |
| `mgmt.vm.property.Help` | vm | property | - | `help` |
| `mgmt.vm.property.HelpRst` | vm | property | - | `help.rst` |
| `mgmt.vm.property.Reset` | vm | property | - | - |
| `mgmt.vm.property.Set` | vm | property | value | - |
| `mgmt.vm.feature.List` | vm | - | - | `<feature>\n` |
| `mgmt.vm.feature.Get` | vm | feature | - | value |
| `mgmt.vm.feature.CheckWithTemplate` | vm | feature | - | value |
| `mgmt.vm.feature.Remove` | vm | feature | - | - |
| `mgmt.vm.feature.Set` | vm | feature | value | - |
2017-04-09 19:40:24 -04:00
| `mgmt.vm.tag.List` | vm | - | - | `<tag>\n` |
2017-03-09 10:39:29 -05:00
| `mgmt.vm.tag.Get` | vm | tag | - | `0` or `1` | retcode? |
| `mgmt.vm.tag.Remove` | vm | tag | - | - |
| `mgmt.vm.tag.Set` | vm | tag | - | - |
2017-04-30 20:48:23 -04:00
| `mgmt.vm.firewall.Get` | vm | - | - | `<rule>\n` | rules syntax as in [firewall interface ](/doc/vm-interface/#firewall-rules-in-4x ) with addition of `expire=` and `comment=` options; `comment=` (if present) must be the last option
| `mgmt.vm.firewall.Set` | vm | - | `<rule>\n` | - | set firewall rules, see `mgmt.vm.firewall.Get` for syntax
2017-03-09 10:39:29 -05:00
| `mgmt.vm.firewall.Flush` | vm | - | - | - |
2017-04-30 20:48:23 -04:00
| `mgmt.vm.firewall.SetPolicy` | vm | - | `accept|drop` | - |
| `mgmt.vm.firewall.GetPolicy` | vm | - | - | `accept|drop` |
| `mgmt.vm.firewall.Reload` | vm | - | - | - | force reload firewall without changing any rule
2017-04-30 20:52:50 -04:00
| `mgmt.vm.device.<class>.Attach` | vm | device | options | - | `device` is in form `<backend-name>+<device-ident>` < br /> optional options given in `key=value` format, separated with spaces; < br /> options can include `persistent=yes` to "persistently" attach the device (default is temporary)
| `mgmt.vm.device.<class>.Detach` | vm | device | - | - | `device` is in form `<backend-name>+<device-ident>`
2017-04-28 19:55:18 -04:00
| `mgmt.vm.device.<class>.List` | vm | - | - | `<device> <options>\n` |
2017-04-30 20:52:50 -04:00
| `mgmt.vm.device.<class>.Available` | vm | device-ident | - | `<device-ident> <properties> description=<desc>\n` | optional service argument may be used to get info about a single device, < br /> optional (device class specific) properties are in `key=value` form, < br /> `description` must be the last one and is the only one allowed to contain spaces; < br /> options can include `persistent=yes` for "persistently" attached devices (default is temporary)
2017-03-09 10:39:29 -05:00
| `mgmt.vm.microphone.Attach` | vm | - | - | - |
| `mgmt.vm.microphone.Detach` | vm | - | - | - |
| `mgmt.pool.List` | `dom0` | - | - | `<pool>\n` |
| `mgmt.pool.ListDrivers` | `dom0` | - | - | `<pool-driver> <property> ...\n` | Properties allowed in `mgmt.pool.Add`
| `mgmt.pool.Info` | `dom0` | pool | - | `<property>=<value>\n` |
2017-03-09 19:08:34 -05:00
| `mgmt.pool.Add` | `dom0` | driver | `<property>=<value>\n` | - |
2017-03-09 10:39:29 -05:00
| `mgmt.pool.Remove` | `dom0` | pool | - | - |
| `mgmt.pool.volume.List` | `dom0` | pool | - | volume id |
| `mgmt.pool.volume.Info` | `dom0` | pool | vid | `<property>=<value>\n` |
| `mgmt.pool.volume.ListSnapshots` | `dom0` | pool | vid | `<snapshot>\n` |
| `mgmt.pool.volume.Snapshot` | `dom0` | pool | vid | snapshot |
| `mgmt.pool.volume.Revert` | `dom0` | pool | `<vid> <snapshot>` | - |
| `mgmt.pool.volume.Resize` | `dom0` | pool | `<vid> <size_in_bytes>` | - |
2017-04-28 19:51:24 -04:00
| `mgmt.pool.volume.Import` | `dom0` | pool | `<vid>\n<raw volume data>` | - |
2017-03-09 10:39:29 -05:00
| `mgmt.vm.volume.List` | vm | - | - | `<volume>\n` | `<volume>` is per-VM volume name, `<vid>` is pool-unique volume id
| `mgmt.vm.volume.Info` | vm | volume | - | `<property>=<value>\n` |
| `mgmt.vm.volume.ListSnapshots` | vm | volume | - | snapshot | duplicate of `mgmt.pool.volume.` , but with other call params |
| `mgmt.vm.volume.Snapshot` | vm | volume | - | snapshot | id. |
| `mgmt.vm.volume.Revert` | vm | volume | snapshot | - | id. |
| `mgmt.vm.volume.Resize` | vm | volume | size_in_bytes | - | id. |
2017-04-28 19:51:24 -04:00
| `mgmt.vm.volume.Import` | vm | volume | raw volume data | - | id. |
2017-03-09 10:39:29 -05:00
| `mgmt.vm.Start` | vm | - | - | - |
| `mgmt.vm.Shutdown` | vm | - | - | - |
| `mgmt.vm.Pause` | vm | - | - | - |
| `mgmt.vm.Unpause` | vm | - | - | - |
| `mgmt.vm.Kill` | vm | - | - | - |
| `mgmt.backup.Execute` | `dom0` | config i | - | - | config in `/etc/qubes/backup/<id>.conf` |
| `mgmt.backup.Info` | `dom0` | ? | content? | ? |
| `mgmt.backup.Restore` | `dom0` | ? | content | ? |
2017-04-09 19:40:24 -04:00
| `mgmt.Events` | `dom0|vm` | - | - | events |
2016-11-18 16:40:16 -05:00
2017-03-03 17:13:14 -05:00
Volume properties:
2017-04-29 17:17:49 -04:00
2017-03-03 17:13:14 -05:00
- `pool`
- `vid`
- `size`
- `usage`
- `rw`
- `internal`
- `source`
- `save_on_stop`
- `snap_on_start`
2017-02-20 13:38:33 -05:00
## Returned messages
2017-02-26 21:10:49 -05:00
First byte of a message is a message type. This is 8 bit non-zero integer.
Values start at 0x30 (48, `'0'` , zero digit in ASCII) for readability in hexdump.
Next byte must be 0x00 (a separator).
2017-02-20 13:38:33 -05:00
This alternatively can be thought of as zero-terminated string containing
single ASCII digit.
### OK (0)
```
30 00 < content >
```
Server will close the connection after delivering single message.
### EVENT (1)
```
31 00 < subject > 00 < event > 00 ( < key > 00 < value > 00 )* 00
```
Events are returned as stream of messages in selected API calls. Normally server
will not close the connection.
A method yielding events will not ever return a `OK` or `EXCEPTION` message.
2017-04-15 07:59:22 -04:00
When calling such method, it will produce an artificial event
`connection-established` just after connection, to help avoiding race
conditions during event handler registration.
2017-02-20 13:38:33 -05:00
### EXCEPTION (2)
```
32 00 < type > 00 ( < traceback > )? 00 < format string > 00 ( < field > 00 )*
```
Server will close the connection.
Traceback may be empty, can be enabled server-side as part of debug mode.
Delimiting zero-byte is always present.
Fields are should substituted into `%` -style format string, possibly after
client-side translation, to form final message to be displayed unto user. Server
does not by itself support translation.
2016-11-18 16:40:16 -05:00
## Tags
2016-11-19 04:34:24 -05:00
- `created-by-<vm>`
- `managed-by-<vm>`
- `backup-<id>`
2016-11-18 16:40:16 -05:00
2016-11-24 09:10:41 -05:00
## General notes
- there is no provision for `qvm-run` , but there already exists `qubes.VMShell` call
2017-04-30 20:52:50 -04:00
- generally actions `*.List` return a list of objects and have "object
identifier" as first word in a row. Such action can be also called with "object
identifier" in argument to get only a single entry (in the same format).
2016-11-24 09:10:41 -05:00
2016-11-18 16:40:16 -05:00
## TODO
- something to configure/update policy
2016-11-24 09:10:41 -05:00
- notifications
- how to constrain the events?
- how to pass the parameters? maybe XML, since this is trusted anyway and
parser may be complicated
- how to constrain the possible values for `mgmt.vm.property.Set` etc, like
"you can change `netvm` , but you have to pick from this set"; this currently
can be done by writing an extension
- a call for executing `*.desktop` file from `/usr/share/applications` , for use
with appmenus without giving access to `qubes.VMShell` ; currently this can be
done by writing custom qrexec calls
- maybe some generator for `.desktop` for appmenus, which would wrap calls in
`qrexec-client-vm`
2017-03-09 10:39:29 -05:00
<!-- vim: set ts=4 sts=4 sw=4 et : -->
