[UI, enhacement] LXD Containers search tab

Bug #1796003 reported by Luis Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

Hello

Is there any way that we can get a Containers's tab (like the devices) here all containers are listed and there is alink to the respective node/machine where they are?

Currently the only way to see all the containers is in the DNS/domain name where they are registered, and when you click on them, it takes you to the Device tab, looking for the container the the device id. (and an PK# error is shown -- This is a bug) at least, if that click on the container link from the DNS would take you to the respective node where it is and its Containers tab,, that would be really helpful

Withe many containers sometimes it is very difficult to remember in which host that container is located. even though this can be queried through the command line in the device "parent" property using the device id of the container (from the broken link in the DNS tab)

BTW this was somehow also mentioned in bug # 1776056 ,, although I believe that it ent to triage as an enhancement only for editing the device/container properties (e.g. IP address) but the part from that that is related to this actual bug may be forgotten

PD: I am using the latest Ubuntu 18.04 maas version from ppa

Setting up maas-common (2.4.2-7034-g2f5deb8b8-0ubuntu1) ...
Setting up maas-region-api (2.4.2-7034-g2f5deb8b8-0ubuntu1) ...
Setting up maas-region-controller (2.4.2-7034-g2f5deb8b8-0ubuntu1) ...

Thanks

description: updated
summary: - LXD Containers search tab
+ LXD Containers search tab/broken DNS link for containers
summary: - LXD Containers search tab/broken DNS link for containers
+ LXD Containers search tab request/broken DNS link for containers
Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: LXD Containers search tab request/broken DNS link for containers

Hi Luis,

We have no current plans to create a containers tab, given that containers are not modeled in MAAS. In fact, you can register any device with a parent (which could be a container or a VM). That said, it is probably a better idea to list this in the devices section since MAAS doesn't really manage this, just provides IP addresses for them. I will, however, raise this for discussion.

That said, the behavior you describe where it takes you to the devices page, is certainly a bug as it should be taking you to the machine listing page. I do believe there's a bug already filed for this.

Hope this helps.

summary: - LXD Containers search tab request/broken DNS link for containers
+ [enhacement] LXD Containers search tab
Changed in maas:
milestone: none → next
status: New → Triaged
summary: - [enhacement] LXD Containers search tab
+ [UI, enhacement] LXD Containers search tab
Revision history for this message
Luis Rodriguez (laragones) wrote :

When I click on the DNS link for a Container, even though internally the container is a device (before it was renamed to Container), why is it these "Containers" are hidden from the devices tab? I mean if it could be just shown there with a column (for all devices - parent) that would make it relatively easy to implement (I dont know the details, sorry for the assumption)

Thanks

Revision history for this message
Luis Rodriguez (laragones) wrote :

I tried downloading the source code and trying to look into this.. but I have no idea where to look for this model/view to display the extra parent column and to disable the filter that doesn't show the container devices in the Devices tab page

Revision history for this message
Luis Rodriguez (laragones) wrote :

I undestand if there are no plans for adding a Containers tab,, I was just requesting this since I saw the new Pods tab.. but you know best regarding where containers should be displayed

What I see now is that devices without parent are displayed in the devices page, and devices with parent (e.g. VM) under the Machine/Containers tab? is this right?

Revision history for this message
Luis Rodriguez (laragones) wrote :

I put the bug and not the enhancement part in bug # 1796007

Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.