Maybe better is to figure out who requested it to be part of vdsm-tool and why, while there were open bugs to have standalone tool. ----- Original Message -----
From: "Fabian Deutsch" <fdeutsch@redhat.com> To: "Douglas Landgraf" <dlandgra@redhat.com>, "Dan Kenigsberg" <danken@redhat.com>, "Alon Bar-Lev" <abarlev@redhat.com> Cc: devel@ovirt.org Sent: Wednesday, July 22, 2015 4:42:37 PM Subject: [ovirt-devel] Registration duplication?
Hey,
I've seen that some new code landed to support Engine registration using the generic registration approach.
But it seem that we now have two implementations:
1. vdsm-tool register [0] 2. ovirt-register [1]
To reduce code duplication I'd suggest to drop one of these approaches before we enter 3.6. Or are there reasons for keeping both of them?
My take is to keep ovirt-register which is independent and would allow us to add plain hosts to Engine (host-deploy is then taking care of the rest IIUIC). The vdsm-tool approach reuqires vdsm to be installed.
Thoughts?
Greetings fabian
--- [0] https://gerrit.ovirt.org/#/c/40966/ [1] https://gerrit.ovirt.org/gitweb?p=ovirt-register.git _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel