nodectl on plain CentOS hypervisors

Does it make sense to install nodectl utility on plain CentOS 7.x nodes? Or any other alternative for plain OS nodes vs ovirt-node-ng ones? On my updated CentOS 7.6 oVirt node I have not the command; I think it is provided by the package ovirt-node-ng-nodectl, that is one of the available ones if I run "yum search" on the system. Thanks Gianluca

Il giorno ven 23 ago 2019 alle ore 11:27 Gianluca Cecchi < gianluca.cecchi@gmail.com> ha scritto:
Does it make sense to install nodectl utility on plain CentOS 7.x nodes?
No, doesn't make sense. nodectl checks for oVirt Node specific configuration. # nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK # nodectl info layers: ovirt-node-ng-4.3.2-0.20190313.0: ovirt-node-ng-4.3.2-0.20190313.0+1 bootloader: default: ovirt-node-ng-4.3.2-0.20190313.0+1 entries: ovirt-node-ng-4.3.2-0.20190313.0+1: index: 0 title: ovirt-node-ng-4.3.2-0.20190313.0 kernel: /boot/ovirt-node-ng-4.3.2-0.20190313.0+1/vmlinuz-3.10.0-957.5.1.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn_host/swap rd.lvm.lv=onn_host/ovirt-node-ng-4.3.2-0.20190313.0+1 rhgb quiet LANG=en_US.UTF-8 img.bootid=ovirt-node-ng-4.3.2-0.20190313.0+1" initrd: /boot/ovirt-node-ng-4.3.2-0.20190313.0+1/initramfs-3.10.0-957.5.1.el7.x86_64.img root: /dev/onn_host/ovirt-node-ng-4.3.2-0.20190313.0+1 current_layer: ovirt-node-ng-4.3.2-0.20190313.0+1
Or any other alternative for plain OS nodes vs ovirt-node-ng ones?
what's the use case here? check host sanity? because nodectl is not checking that, it just check node config matches to requirements to be able to perform rollback if needed.
On my updated CentOS 7.6 oVirt node I have not the command; I think it is provided by the package ovirt-node-ng-nodectl, that is one of the available ones if I run "yum search" on the system.
Thanks Gianluca _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5I76UHJVK6ADY2...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

On Fri, Aug 23, 2019 at 2:32 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Or any other alternative for plain OS nodes vs ovirt-node-ng ones?
what's the use case here? check host sanity? because nodectl is not checking that, it just check node config matches to requirements to be able to perform rollback if needed.
ok, understood. Thanks for clarifying Gianluca
participants (2)
-
Gianluca Cecchi
-
Sandro Bonazzola