On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis <donny@fortnebula.com> wrote:
have you gotten an image update yet?

On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen <matt@khoza.com> wrote:
Hello all,

I read at https://www.ovirt.org/develop/projects/node/troubleshooting/ that "Changes made from the command line are done at your own risk. Making changes has the potential to leave your system in an unusable state." It seems clear that RPMs should not be installed.

That document mainly refers to vintage node.
In Next Generation Node now we have rpm persistence; please check
https://www.ovirt.org/develop/release-management/features/node/node-next-persistence/

 

Is this accurate for https://www.ovirt.org/node/ ?

We have added smartctl and hpacucli in order to do disk and RAID monitoring. So far our node servers have retained changes across reboots, which is the primary reason I'm wondering if perhaps this applies to an older version of oVirt Node.

If what we have been doing is not supported, what is the suggested method to do do hardware monitoring (in particular disks)?

Thanks
Matt
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users