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

[Ryan Barry]

Next-gen node (since 4.0) doesn't have any strong notion of "persistence",
unlike previous versions of oVirt Node.

My guess would be that /exports was not moved across to the new system.

The update process for Node is essentially:

* create a new lv
* unpack the squashfs in the new RPM and put it on the LV
* Go through /var, /etc, and /root to see if any files were modified/added,
and copy those to the new layer
* Add a new bootloader entry
* Re-install any persistent RPMs

I would guess that /exports as not on its own partition, so it didn't carry
across. Mounting the LV for the old image somewhere (/tmp/...) will make
them visible again,


On Tue, Dec 19, 2017 at 9:26 AM, Kasturi Narra  wrote:

> Hello Matt,
>
>All the partitions will be persisted when gluster is installed on
> the ovirt node since gluster recommends user not to create bricks in root
> directory. If the gluster bricks are created in root partition then once
> the update of the node is done, you will not be able to see any of the
> bricks.
>
> Hope this helps !!!
>
> Thanks
> kasturi.
>
> On Tue, Dec 19, 2017 at 4:28 AM, Matt Simonsen  wrote:
>
>> On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
>>
>> On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis 
>> wrote:
>>
>>> have you gotten an image update yet?
>>>
>>> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  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/no
>> de/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
>>
>> ___
>> 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
>
>


-- 

RYAN BARRY

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR

Red Hat NA 

rba...@redhat.comM: +1-651-815-9306 IM: rbarry

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

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

[Kasturi Narra]

Hello Matt,

   All the partitions will be persisted when gluster is installed on
the ovirt node since gluster recommends user not to create bricks in root
directory. If the gluster bricks are created in root partition then once
the update of the node is done, you will not be able to see any of the
bricks.

Hope this helps !!!

Thanks
kasturi.

On Tue, Dec 19, 2017 at 4:28 AM, Matt Simonsen  wrote:

> On 12/15/2017 03:06 AM, Simone Tiraboschi wrote:
>
> On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis  wrote:
>
>> have you gotten an image update yet?
>>
>> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  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/
>
>
>
>
> 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
>
> ___
> 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

Re: [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 > wrote:


have you gotten an image update yet?

On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen > 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/





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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Simone Tiraboschi]

On Fri, Dec 15, 2017 at 4:45 AM, Donny Davis  wrote:

> have you gotten an image update yet?
>
> On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

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

[Donny Davis]

have you gotten an image update yet?

On Thu, Dec 14, 2017 at 8:08 PM, Matt Simonsen  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.
>
> 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