[UI, enhancement] Allow editing devices with parents

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

Bug Description

From the Subnets page
I can see the LXD containers with the respective IP address

For example, in http://10.3.4.10:5240/MAAS/#/subnet/1
I am able to see the following entry:
10.3.5.207
Static
public-hadoopdn1
eth0
Device
aibladmin
Sun, 10 Jun. 2018 13:57:51

There is no link to the actual Machine/containers tab (is it the correct behavior?

Second, from the DNS tab, for example http://10.3.4.10:5240/MAAS/#/domain/0
I can see the entry:

public-hadoopnn
A
(default)
10.3.5.199

And public-hadoopnn is highlighted, there is a link that I can follow, but when I follow the link, it redirects me to the devices page instead of the Machine/Containers page

http://10.3.4.10:5240/MAAS/#/device/ts7ft3

Error occurredReload
No item with pk: ts7ft3

The device (LXD container) is shown in
http://10.3.4.10:5240/MAAS/#/machine/7afcyh
selecting the containers tab. And I can't edit the IP assignment mode (aka, static, DHCP, etc)

And of course it shows an error, because teh "Device" doesnt exist in the devices page, but in the Machine/Containers page

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

This is not LXD specific. If I add a device with parent as a machine (e.g. a KVM), it is specified in the containers tab also.

When I click on the DNS specific item, it redirects to the device page, but it is not found there,

When I click on a device that was added without parent from DNS, it redirects to the device page.

The other issues also apply not only to LXD but also to devices with parent. devices with parent are shown in the containers tab, and you can't modify the IP address.

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

This is also problematic, since once a device is added as child (specifying the parent).. the device can't be deleted.

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

Finally,
Maybe devices with a parent, should be listed as they are now in the containers tab, but also on the devices tab. so that you can search, delete, modify IP address, etc. with an extra colum in the devices page indicating the parent. Like this you can know where a child device is located (in which machine containers tab)

Also, from the Machine/Containers tab, the device should be a link to the devices page. Like this both the DNS link and the Containers page link to the device list will work.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Luis,

Devices with a parent are not meant to be added in the devices page, nor are meant to be edited from MAAS directly. These devices with parent were added for situations where Juju or LXD want to track devices in MAAS, and they themselves, can update such values over the API.

At the moment, we dont have plans to make this a feature where users can themselves manage devices with parents over the web UI.

summary: - LXD/MAAS Integration failure in DNS (and no link in Subnet)
+ [UI] Allow editing devices with parents
Revision history for this message
Andres Rodriguez (andreserl) wrote : Re: [UI] Allow editing devices with parents

Also, please note that if LXD/Juju adds devices to MAAS, these should never be managed by the user, but rather, any changes should be done via LXD or Juju.

Changed in maas:
importance: Undecided → Medium
status: New → Triaged
summary: - [UI] Allow editing devices with parents
+ [UI, enhancement] Allow editing devices with parents
Changed in maas:
milestone: none → next
Revision history for this message
Luis Rodriguez (laragones) wrote :

OK.. Editing is fine, understood that this is an added feature, should be done on LXD/Juju.
But what about search and the broken links?

When I am DNS and click on the child device, it tries to reach the device at the devices page, instead of redirecting to the Machine/Containers tab and shows an error that the device is not found

Second, with MAAS UI I can't search where a particular device (through DNS) is located, since they are not displayed in the devices page. this is kind of annoying that I have to go machine by machine looking for the respective device I want. Through the API I can get the parent of the device and then put it in the link.

Maybe if you display them in the devices page (disabled for editing) and add a parent column I can search the respective device and link to the respective node where it is located.

Thanks

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

I mean.. Right now I have to go to DNS page, search manually in the page for the particular "Device" name. If the link would work, I would get the Machine/Container tab page instead of the broken Devices link.

But wouldn't it be better to be able to see the devices in the Devices page, and use the search facility already available? At the end if you query the devices through the API they are there, the only difference is that the parent property is not null. If you can display this parent property in an extra column that would make it easier to find Juju/LXD devices where they are really located. And this is more of a functionality issue in the UI and not of LXD/Juju

Manually I can query for the device using the API, get the parent property and put it in the browser link
e.g.
http://10.3.4.10:5240/MAAS/#/machine/x7xehg

where "x7xehg" is the parent property of the device.

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

Also.. Thinking about it. if MAAS is providing DHCP/DNS, MAAS should be able to control/assign DHCP and modify the child devices settings related to this. At the end LXD/Juju are not typically used for setting DHCP if you are using a common unmanaged bridge. you would have to be aware of the DHCP pool, which LXD/Juju are not if they are using MAAS.

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

I added bug # 1796003 related to some of the original description here. related to the fact that container's link in the DNS tab is broken and not the actual enhancement part that would allow to edit the IP address of the container.

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

Bug attachments

Remote bug watches

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