[ovirt-users] oVirt Node 4.1 question, writing files to /root and RPMs

[Matt Simonsen]

On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
> On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis <donny at fortnebula.com 
> <mailto:donny at fortnebula.com>> wrote:
>
>     have you gotten an image update yet?
>
>     On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen <matt at khoza.com
>     <mailto:matt at khoza.com>> wrote:
>
>         Hello all,
>
>         I read at
>         https://www.ovirt.org/develop/projects/node/troubleshooting/
>         <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/
>



I'm sure glad we tested!

On one Node image we had images locally stored in /exports and shared 
out via NFS. After an upgrade & reboot, images are gone.

If we "Convert to local storage" will the data persist?  I am planning 
to test, but want to be sure how this is designed.

I assume during a Gluster installation something is also updated in 
oVirt Node to allow for the Gluster partition to persist?

At this point I'm thinking I should manually install via CentOS7 to 
ensure folders and partitions are persistent. Is there any downside to 
installing over CentOS7?

Thanks
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20171218/efbbbc8c/attachment.html>