Project | LXD |
Status | Draft |
Author(s) | @monstermunchkin |
Approver(s) | @stgraber @tomp |
Release | 5.3 |
Internal ID | LX015 |
Abstract
Have LXD itself listen for VM sockets connections.
Rationale
The current state is that the lxd-agent listens on the VM socket inside of the VM once it’s up and running. This allows for requests from LXD to the VM. There’s currently no way of the VM talking to LXD.
If LXD were to listen on the vsock, the VM could send requests to it. This would e.g. enable the VM to notify LXD that it’s ready i.e. done booting.
Specification
Design
The LXD server will listen on the vsock. Clients (VMs) can connect to the vsock using their client certificate, and make requests through it. The server will be listening on port 1024 + CID (Context ID). The CID is unique for each VM, and can be retrieved from both the server and the client.
The current /dev/lxd handler in VMs will be replaced by this interface. The instance-data
file containing various information can be removed as it will not be needed anymore.
API changes
No API changes.
CLI changes
No CLI changes.
Database changes
No database changes.
Upgrade handling
No upgrade handling.
Further information
TBD