Extend the listing possibility
Extend the listing possibility
Descriptive title for this enhancement
Hello,
With the new Ipam plugin I thought we could find some use to extend the listing possibility.
Example we have the following LDIF
cn=demo-dev,ou=servers,ou=systems
createTimestamp 2020-04-09 20:29:00
modifyTimestamp 2020-04-10 04:33:42
cn demo-dev
fdMode unlocked
objectClass fdServer
objectClass ipHost
objectClass ieee802Device
ipHostNumber 192.168.10.25
ipHostNumber 192.168.10.34
macAddress ff:ff:ff:ff:ff:fd
macAddress ff:ff:ff:ff:ff:fe
cn=eth0
createTimestamp 2020-04-10 04:19:38
modifyTimestamp 2020-04-10 04:46:47
objectClass fdNetworkInterface
cn eth0
macAddress ff:ff:ff:ff:ff:fe
ipHostNumber 192.168.10.25
fdNetworkInterfaceVlanId 42
fdNetworkInterfaceVlanTag the_lvan
fdNetworkInterfaceSubnetDN cn=test-192,ou=ipam,dc=demo-fusiondirectory,dc=org
cn=eth1
createTimestamp 2020-04-10 04:33:15
modifyTimestamp 2020-04-10 04:33:15
objectClass fdNetworkInterface
cn eth1
macAddress ff:ff:ff:ff:ff:fd
fdNetworkInterfaceVlanTag 234
ipHostNumber 192.168.10.34
cn=eth2
createTimestamp 2020-04-10 04:56:11
modifyTimestamp 2020-04-10 04:56:11
objectClass fdNetworkInterface
cn eth2
macAddress ff:ff:ff:ff:ff:fc
fdNetworkInterfaceSubnetDN cn=test-192,ou=ipam,dc=demo-fusiondirectory,dc=org
ipHostNumber 192.168.1.1We can only use attributs from the root object in the listing.
Actual behavior
Example, if I want the "cn" as Column it only show me "demo-dev"
Expected behavior
I would want to display the cn from eth1, so at first we need the possibility to search through sub objects and finaly a way to "filter" what we want.
Example show me the "cn" attribute for the objects with a dn that match my filter "cn=eth1" or something similar.
Step by step description of new behaviour
- Adding attribute + filter to the listing
- Test if we see the right element
Benefits
It will help making more complex listing information.
We could imagine something like showing only the IP of an interface or showing in one column the cn and another one the ip
Possible Drawbacks
none
Activity
assigned to @bmortier
By bmortier on 2020-04-10T11:51:18 (imported from GitLab)
assigned to @MCMic and unassigned @bmortier
By bmortier on 2020-05-05T07:31:44 (imported from GitLab)
added PJ2002-0330 label
changed milestone to %FusionDirectory 1.4
By bmortier on 2020-05-05T07:32:57 (imported from GitLab)
@jswaelens I do not understand what you want. You’re mixing filtering and showing in a column in your description.
I do not see any obvious way to either make this appear in the UI or how to do this on the technical side. An LDAP search does not return subnodes so that would mean doing an additional search for each node at least.
Most likely if this is really needed it will have to be done with specific filter elements or column classes for IPAM plugin.
The exact need is listing interfaces names in a column?
By Côme Chilliet on 2020-05-06T09:41:52 (imported from GitLab)
yes the addition of the network interface concept in systems make us wonder how to get this information in the listing.
when only the system plugin is installed we me able to see
- name of the interface
- mac addresses
when ipam is installed
- vlan
- vlan tag
- subnet
so we may need to new filter element for column ?
Cheers
By bmortier on 2020-05-06T09:41:52 (imported from GitLab)
added fusiondirectory-core network-radius labels
mentioned in commit 5123d078
By Côme Chilliet on 2020-06-03T08:44:55 (imported from GitLab)
mentioned in commit e9eac42a
By Côme Chilliet on 2020-06-03T08:44:55 (imported from GitLab)
added To Be Tested label
assigned to @bmortier and unassigned @cchilliet
By bmortier on 2020-08-19T15:29:34 (imported from GitLab)
