MAAS UI: MAAS Instances and MAAS as LXD tenants

Machine Instances view migrated to React

As part of the rolling migration of the entire MAAS UI from angular.js to React. We have converted the Instances view to React. Getting us one step closer to our goal of migrating the entire Machine details section to React by the end of the cycle in May.

:face_with_monocle: At the moment, our team is more than interested to understand if our MAASters are using LXD to connect to a MAAS server? Tell us how you are currently using them and what do you do with these instances in MAAS. Are these information meaningful to you? What actions do you take with the information in the Instances tab? (Feel free to reply in this thread, we’d love to hear your feedback :smiley:)

MAAS as LXD tenants

Continuing our focus from the last iteration, our design team is still working on the conceptual level design for the new feature - MAAS as LXD tenants. In this feature, MAAS will be connected to LXD from the project level, instead of the server level.

From the workflow standpoint, when a LXD server is created in the CLI, users will automatically get a default project, where they can create more projects under this LXD server. Under a project, a user may compose or delete several virtual machines, which will be managed under the project level.

In MAAS, a user connects to the LXD address and there is an extra step to select which project you want to connect to, before you reach a project dashboard. At the moment, MAAS allows you to connect to one project at a time. In order to connect to multiple projects, a user needs to connect to the same LXD address and selects a different project.