add an option to migrate the ip and mac adress to the new interface format into fusiondirectory-setup
add an option to migrate the ip and mac adress to the new interface format into fusiondirectory-setup
Descriptive title for this enhancement
add an option to migrate the ip and mac adress to the new interface format into fusiondirectory-setup
Actual behavior
there is no concept of network interface, attributes are stored in the system object directly
Expected behavior
Step by step description of new behaviour
- read all systems
- migrate the ipHost and macAdress attribute in a interface object
- create a default named interface object
Benefits
ease of migration to 1.4 for systems
Possible Drawbacks
various object to migrate
Applicable Issues
all systems object migration
Activity
changed milestone to %FusionDirectory 1.4
By bmortier on 2020-04-23T16:01:30 (imported from GitLab)
added PJ2002-0330 label
added fusiondirectory-setup label
added network-radius label
mentioned in issue fd-plugins#6039 (closed)
By bmortier on 2020-06-25T08:34:10 (imported from GitLab)
mentioned in commit fb4fab80
By Côme Chilliet on 2020-08-18T14:54:03 (imported from GitLab)
hello @cchilliet,
here is a first draft of the rules to migrate to old interfaces to the new interface in systems
rules :
-
if 1 ip and 1 mac we migrate the info in a single interface
-
if more than 1 ip but only 1 mac we migrate the info in a single interface
-
if more than 1 ip and several mac we ask them what to do
fusiondirectory-setup --migrate-interface interface name
interface name = eth0 by default
searching for system to migrate we first get a first list of easy conversion
-
the list for easy conversion only contains case that need to be migrated in 1 interface
-
if 1 ip and 1 mac we migrate the info in a single interface
-
if more than 1 ip but only 1 mac we migrate the info in a single interface
-
after the successful conversion of the easy list we get a second list with complex cases
-
the list for complex conversion only contains case that we don't know how to migrated automatically
- If more than 1 ip and more than 1 mac we ask the user how to group them together
- The idea may be to put number in brackets near ip and mac and let the user type the one to create te first interface and then let him chose the second interface and so on
- Another way should be to let the user get an ldif and let him migrate the data by hand
- If more than 1 ip and more than 1 mac we ask the user how to group them together
By bmortier on 2020-08-18T15:01:51 (imported from GitLab)
-
$ sudo perl ./contrib/bin/fusiondirectory-setup --migrate-interfaces Migrating your systems from FD < 1.4 The following systems are missing an interface node and can be migrated automatically: cn=S4mini,ou=mobile,ou=systems,dc=example,dc=com with no MAC and IP 192.168.42.99 Migrate these systems by adding an interface node [Yes/No]? yes Please enter the name for interfaces created by this migration [eth0]: test0 1 entries migrated The following systems are missing interfaces nodes but cannot be migrated because they have several MAC addresses: cn=adminer,ou=servers,ou=systems,l=WDC,dc=example,dc=com with MAC 00:11:22:33:44:88, 00:22:33:22:33:33 and IP 168.192.11.22, 192.168.42.1 Please edit them by hand in FusionDirectory to add interfacesBy Côme Chilliet on 2020-08-19T13:26:41 (imported from GitLab)
hello @cchilliet,
after discussing in irc i agree with this mode of operations
Cheers
By bmortier on 2020-08-19T13:37:33 (imported from GitLab)
mentioned in commit 76736a35
By Côme Chilliet on 2020-08-19T14:10:04 (imported from GitLab)
added To Be Tested label
assigned to @jswaelens and unassigned @cchilliet
By Côme Chilliet on 2020-08-19T14:46:55 (imported from GitLab)
removed To Be Tested label
added Added label
hello @cchilliet this as been tested by inalco and work so closing this bug
By bmortier on 2021-01-28T16:33:46 (imported from GitLab)
marked this issue as related to fd-plugins#6039 (closed)
By bmortier on 2021-02-02T08:52:57 (imported from GitLab)
