Refresh from bug#875088. MISSION Implement registration process within ovirt-node that is manager agnostic. No manager specific code to be written within node to enable registration. SCOPE 1. ovirt-node to define a protocol for registration into manager serving as http server. a. establish pki trust for ssl b. establish ssh trust c. register within manager an example can be found at engine host deploy protocol[1] 2. implement python library to implement that protocol at node side. an example of simple design that is targeted to vdsm can be found at bug#994451, it outlines the process. 3. integrate (2) into tui. 4. integrate (2) into boot process to get args from kernel command-lines. OUT OF SCOPE 1. implement engine side, manager implementation, of the protocol. [1] http://www.ovirt.org/Features/HostDeployProtocol
*** Bug 875088 has been marked as a duplicate of this bug. ***
Closing this bug as duplicate of bz#1231379 which has all flags for 3.6 release and it's related to the new tool which will deprecate vdsm-reg. For the record, the tool uses the new registration service as requested in bz#994451 and bz#1135921 and it's integrated to ovirt-node and can be used in a ordinary distro. *** This bug has been marked as a duplicate of bug 1231379 ***
Reopening this bug to get propper test coverage.
The source code of the new generic-registration tool is available here: https://github.com/oVirt/ovirt-register/
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Test version: rhev-hypervisor7-7.2-20160113.0 ovirt-node-3.6.1-3.0.el7ev.noarch > SCOPE > > 1. ovirt-node to define a protocol for registration into manager serving as > http server. PASS # cat /var/log/vdsm/register.log | grep https 01/19/2016 08:15:15 AM Engine URL: https://10.66.73.120:443 01/19/2016 08:15:15 AM Engine https port: 443 01/19/2016 08:15:15 AM Get version via: https://10.66.73.120/ovirt-engine/services/host-register?version=1&command=get-version 01/19/2016 08:15:15 AM Download CA via: https://10.66.73.120:443/ovirt-engine/services/host-register?version=1&command=get-pki-trust 01/19/2016 08:15:15 AM Download SSH via: https://10.66.73.120:443/ovirt-engine/services/host-register?version=1&command=get-ssh-trust 01/19/2016 08:15:15 AM Registration via: https://10.66.73.120:443/ovirt-engine/services/host-register?version=1&command=register&sshUser=root&sshPort=22&port=54321&name=dhcp-66-106-14.nay.redhat.com&uniqueId=4C4C4544-0058-3810-8033-B2C04F363358 > a. establish pki trust for ssl PASS /var/log/vdsm/register.log Download CA via: https://10.66.73.120:443/ovirt-engine/services/host-register?version=1&command=get-pki-trust > b. establish ssh trust PASS /var/log/vdsm/register.log Download SSH via: https://10.66.73.120:443/ovirt-engine/services/host-register?version=1&command=get-ssh-trust > c. register within manager PASS /var/log/vdsm/register.log Registration via: https://10.66.73.120:443/ovirt-engine/services/host-register?version=1&command=register&sshUser=root&sshPort=22&port=54321&name=dhcp-66-106-14.nay.redhat.com&uniqueId=4C4C4544-0058-3810-8033-B2C04F363358 > > an example can be found at engine host deploy protocol[1] > > 2. implement python library to implement that protocol at node side. PASS /usr/lib/python2.7/site-packages/vdsm/tool/register.py > > an example of simple design that is targeted to vdsm can be found at > bug#994451, it outlines the process. > > 3. integrate (2) into tui. PASS > > 4. integrate (2) into boot process to get args from kernel command-lines. PASS as auto install with management_server parameters can succeed. > > OUT OF SCOPE > > 1. implement engine side, manager implementation, of the protocol. PASS So the bug is fixed, change bug status to VERIFIED.