| 2020-10-07 19:27:16 |
Adam Collard |
description |
The LXD team unsurprisingly has quite a few systems running LXD which are used for VM hosting.
As those host a variety of VMs for a variety of purposes, we normally use projects to separate the different uses.
In this case, we'd like to have a project for our Ceph cluster VM/containers, a project for our Jenkins managed systems and a project for our MAAS managed VMs.
Sadly the MAAS power control does not let you specify a LXD project and so MAAS can only see and interact with instances in the default project.
This should be a pretty simple addition but one that would be quite welcome by anyone running a large LXD deployment. |
The LXD team unsurprisingly has quite a few systems running LXD which are used for VM hosting.
As those host a variety of VMs for a variety of purposes, we normally use projects to separate the different uses.
In this case, we'd like to have a project for our Ceph cluster VM/containers, a project for our Jenkins managed systems and a project for our MAAS managed VMs.
Sadly the MAAS power control does not let you specify a LXD project and so MAAS can only see and interact with instances in the default project.
This should be a pretty simple addition but one that would be quite welcome by anyone running a large LXD deployment. |
|
