Mender web interface

[Ron]

Is it possible to change which items are displayed in the devices tab in the mender web interface?

 

All of our devices are same 'Device type' and the ID is not helpful in finding a specific device. Ideally I'd like to be able to arbitrarily add columns,  but would at least be able to change ID or 'Device type' to hostname (or MAC addr).

 thanks,

  -ron

[Eystein Måløy Stenberg]

Hi Ron,

Good timing, take a look at the "Custom device identity attribute"
section of the Mender 1.6 beta blog:
https://mender.io/blog/mender-1-6-beta-easier-device-integration

Does this help?

Spoiler alert, 1.6 final will likely be released next week. :)

> --
> You received this message because you are subscribed to the Google
> Groups "Mender List mender.io" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mender+un...@lists.mender.io
> <mailto:mender+un...@lists.mender.io>.
> To post to this group, send email to men...@lists.mender.io
> <mailto:men...@lists.mender.io>.
> Visit this group at
> https://groups.google.com/a/lists.mender.io/group/mender/.

--

Eystein

[Ron]

This looks perfect, will check it out.

 thanks,

   -ron

[Dell Green]

Does this only work for Production mode and not demo mode, as I have installed 1.6.0 of the server and it only gives me the option to choose between device id and mac address. However i have a device connected and authorised that provides several custom device identity attributes which don't show up in the global list.

[Michael]

Do you still have a demo/virtual device in the device list? If so could you try removing the demo device and test again?

The reasoning - for this first iteration of the feature the UI takes the identity attributes for one device, and assumes your other devices have the same set attributes available. (It was going to be heavy work to loop through large numbers of devices to get a list of common identity attributes, and it seems that you would usually use the same identity attributes for your devices, so in order to introduce this feature quickly we worked on that assumption.) So if you have a demo device that differs from your "real" devices, it may be that the UI is only offering you the choice of attributes from the demo one. We'll improve on this in upcoming releases!

Michael

[Dell Green]

I don't have the demo device in my list, i rejected the qemu demo device, it is still listed in the rejected devices list.

I have restarted server, is it cached internally that needs cleaning? or is it stilling picking it up from the demo device in the rejected list?

Do i need to disable the client device docker service?

[Michael]

I think you might need to decommission the demo device, the UI is still picking it up from the rejected list.

I've been thinking about this - even when improving this functionality in future in order to be more thorough about grabbing the available identity attributes, it will always have to offer for selection only the attributes devices have in common. Otherwise you could end up with blank device ID values. 

For example, demo device has ID and mac address and your new devices have ID, mac address and custom_id_attr. If you selected custom_id_attr as the default device ID while the demo device was still in the system (even if rejected), the device identity column would be empty for this device and any others that don't have the custom_id_attr identity attribute.

[Dell Green]

many thanks, yep decommissioning the device sorted the problem. :)

Given that one could have several/many different devices/products with different device identity attribute schemes, does it make sense to try and apply the custom device identity column globally?

Maybe it makes more sense in groups of the same device identity scheme in device groups? 

Maybe a device group is auto-generated for each device identity  attribute scheme?

[Eystein Måløy Stenberg]

Awesome!

Mender assumes you pick a device identity scheme and use that
consistently, all the requirements are here:
https://docs.mender.io/1.6/client-configuration/identity

I would call this an edge case, as the demo device would not necessarily
use the same identity scheme as you decide on for your devices. So maybe
a quick fix is to use a real device if it exists and fall back to a demo
device if not?

On 26/09/18 06:45, 'Dell Green' via Mender List mender.io wrote:
> many thanks, yep decommissioning the device sorted the problem. :)
>
> Given that one could have several/many different devices/products with
> different device identity attribute schemes, does it make sense to try
> and apply the custom device identity column globally?
> Maybe it makes more sense in groups of the same device identity scheme
> in device groups?
> Maybe a device group is auto-generated for each device identity
> attribute scheme?
>
>
>
> On Wednesday, 26 September 2018 13:59:45 UTC+1, Michael wrote:
>
> I think you might need to decommission the demo device, the UI is
> still picking it up from the rejected list.
>
> I've been thinking about this - even when improving this
> functionality in future in order to be more thorough about grabbing
> the available identity attributes, it will always have to offer for
> selection only the attributes devices have in common. Otherwise you
> could end up with blank device ID values.

> For example, demo device has /ID/ and /mac address/ and your new
> devices have /ID/, /mac address/ and /custom_id_attr. /If you
> selected /custom_id_attr /as the default device ID while the demo

> device was still in the system (even if rejected), the device
> identity column would be empty for this device and any others that

> don't have the /custom_id_attr /identity attribute.

>
> On Monday, September 24, 2018 at 3:46:11 PM UTC+2, Dell Green wrote:
>
> I don't have the demo device in my list, i rejected the qemu
> demo device, it is still listed in the rejected devices list.
> I have restarted server, is it cached internally that needs
> cleaning? or is it stilling picking it up from the demo device
> in the rejected list?
> Do i need to disable the client device docker service?
>
>
> On Monday, 24 September 2018 14:33:45 UTC+1, Michael wrote:
>
> Do you still have a demo/virtual device in the device list?
> If so could you try removing the demo device and test again?
>
> The reasoning - for this first iteration of the feature the

> UI takes the identity attributes for /one/ device, and

> > Groups "Mender List mender.io <http://mender.io>"

> group.
> > To unsubscribe from this group and stop receiving
> emails from it, send
> > an email to mender+un...@lists.mender.io
> > <mailto:mender+un...@lists.mender.io>.
> > To post to this group, send email to
> men...@lists.mender.io
> > <mailto:men...@lists.mender.io>.
> > Visit this group at
> >
> https://groups.google.com/a/lists.mender.io/group/mender/

> <https://groups.google.com/a/lists.mender.io/group/mender/>.
>
>
> --
>
> Eystein

[Dell Green]

I also disabled the client service in the 'up' script for now until I change to production mode :)