12:23 a.m.
I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How do I
upgrade to 4.4? Is there a guide?
5:31 a.m.
Vincent,
This document will be useful
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_...
On Wed, Sep 23, 2020, 3:55 AM Vincent Royer <vincent(a)epicenergy.ca> wrote:
I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How
do I
upgrade to 4.4? Is there a guide?
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TCX2RUE5RN7...
7:43 p.m.
My confusion is that those documents do not describe any gluster related
tasks for Ovirt Nodes. When I take a node down and install Ovirt Node 4.4
on it, won't all the gluster bricks on that node be lost? The part
describing "preserving local storage", that isn't anything about Gluster,
correct?
*Vincent Royer*
*778-825-1057*
<http://www.epicenergy.ca/>
*SUSTAINABLE MOBILE ENERGY SOLUTIONS*
On Tue, Sep 22, 2020 at 8:31 PM Ritesh Chikatwar <rchikatw(a)redhat.com>
wrote:
Vincent,
This document will be useful
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_...
On Wed, Sep 23, 2020, 3:55 AM Vincent Royer <vincent(a)epicenergy.ca> wrote:
> I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How do
> I upgrade to 4.4? Is there a guide?
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TCX2RUE5RN7...
>
8:31 p.m.
Before you reinstall the node , you should use 'gluster volume remove-brick
<VOL> replica <old number - 1> ovirt_node:/path-to-brick' to reduce the
volume to replica 2 (for example). Then you need to 'gluster peer detach
ovirt_node' in order to fully cleanup the gluster TSP.
You will have to remove the bricks that are on that < ovirt_node > before detaching
it.
Once you reinstall with EL 8, you can 'gluster peer probe
<reinstalled_ovirt_node>' and then 'gluster volume add-brick <VOL>
replica <current count + 1> reinstalled_ovirt_node:/path-to-brick.
Note that reusing bricks is not very easy, so just wipe the data via 'mkfs.xfs -i
size=512 /dev/block/device'.
Once all volumes are again a replica 3 , just wait for the healing to go over and you can
proceed with the oVirt part.
Best Regards,
Strahil Nikolov
В сряда, 23 септември 2020 г., 20:45:30 Гринуич+3, Vincent Royer
<vincent(a)epicenergy.ca> написа:
My confusion is that those documents do not describe any gluster related tasks for Ovirt
Nodes. When I take a node down and install Ovirt Node 4.4 on it, won't all the
gluster bricks on that node be lost? The part describing "preserving local
storage", that isn't anything about Gluster, correct?
Vincent Royer
778-825-1057
SUSTAINABLE MOBILE ENERGY SOLUTIONS
On Tue, Sep 22, 2020 at 8:31 PM Ritesh Chikatwar <rchikatw(a)redhat.com> wrote:
Vincent,
This document will be useful
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_...
On Wed, Sep 23, 2020, 3:55 AM Vincent Royer <vincent(a)epicenergy.ca> wrote:
> I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How do I upgrade to
4.4? Is there a guide?
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TCX2RUE5RN7...
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J6IERH7OAO6...
8:40 p.m.
well that sounds like a risky nightmare. I appreciate your help.
*Vincent Royer*
*778-825-1057*
<http://www.epicenergy.ca/>
*SUSTAINABLE MOBILE ENERGY SOLUTIONS*
On Wed, Sep 23, 2020 at 11:31 AM Strahil Nikolov <hunter86_bg(a)yahoo.com>
wrote:
Before you reinstall the node , you should use 'gluster volume
remove-brick <VOL> replica <old number - 1> ovirt_node:/path-to-brick'
to
reduce the volume to replica 2 (for example). Then you need to 'gluster
peer detach ovirt_node' in order to fully cleanup the gluster TSP.
You will have to remove the bricks that are on that < ovirt_node > before
detaching it.
Once you reinstall with EL 8, you can 'gluster peer probe
<reinstalled_ovirt_node>' and then 'gluster volume add-brick <VOL>
replica
<current count + 1> reinstalled_ovirt_node:/path-to-brick.
Note that reusing bricks is not very easy, so just wipe the data via
'mkfs.xfs -i size=512 /dev/block/device'.
Once all volumes are again a replica 3 , just wait for the healing to go
over and you can proceed with the oVirt part.
Best Regards,
Strahil Nikolov
В сряда, 23 септември 2020 г., 20:45:30 Гринуич+3, Vincent Royer <
vincent(a)epicenergy.ca> написа:
My confusion is that those documents do not describe any gluster related
tasks for Ovirt Nodes. When I take a node down and install Ovirt Node 4.4
on it, won't all the gluster bricks on that node be lost? The part
describing "preserving local storage", that isn't anything about Gluster,
correct?
Vincent Royer
778-825-1057
SUSTAINABLE MOBILE ENERGY SOLUTIONS
On Tue, Sep 22, 2020 at 8:31 PM Ritesh Chikatwar <rchikatw(a)redhat.com>
wrote:
> Vincent,
>
>
> This document will be useful
>
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_...
>
> On Wed, Sep 23, 2020, 3:55 AM Vincent Royer <vincent(a)epicenergy.ca>
wrote:
>> I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How
do I upgrade to 4.4? Is there a guide?
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TCX2RUE5RN7...
>>
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J6IERH7OAO6...
9:46 p.m.
As far as I know there is an automation to do it for you.
Best Regards,
Strahil Nikolov
В сряда, 23 септември 2020 г., 21:41:13 Гринуич+3, Vincent Royer
<vincent(a)epicenergy.ca> написа:
well that sounds like a risky nightmare. I appreciate your help.
Vincent Royer
778-825-1057
SUSTAINABLE MOBILE ENERGY SOLUTIONS
On Wed, Sep 23, 2020 at 11:31 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote:
> Before you reinstall the node , you should use 'gluster volume remove-brick
<VOL> replica <old number - 1> ovirt_node:/path-to-brick' to reduce the
volume to replica 2 (for example). Then you need to 'gluster peer detach
ovirt_node' in order to fully cleanup the gluster TSP.
>
> You will have to remove the bricks that are on that < ovirt_node > before
detaching it.
>
> Once you reinstall with EL 8, you can 'gluster peer probe
<reinstalled_ovirt_node>' and then 'gluster volume add-brick <VOL>
replica <current count + 1> reinstalled_ovirt_node:/path-to-brick.
>
> Note that reusing bricks is not very easy, so just wipe the data via 'mkfs.xfs -i
size=512 /dev/block/device'.
>
> Once all volumes are again a replica 3 , just wait for the healing to go over and you
can proceed with the oVirt part.
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
> В сряда, 23 септември 2020 г., 20:45:30 Гринуич+3, Vincent Royer
<vincent(a)epicenergy.ca> написа:
>
>
>
>
>
> My confusion is that those documents do not describe any gluster related tasks for
Ovirt Nodes. When I take a node down and install Ovirt Node 4.4 on it, won't all the
gluster bricks on that node be lost? The part describing "preserving local
storage", that isn't anything about Gluster, correct?
>
>
> Vincent Royer
> 778-825-1057
>
>
> SUSTAINABLE MOBILE ENERGY SOLUTIONS
>
>
>
>
>
> On Tue, Sep 22, 2020 at 8:31 PM Ritesh Chikatwar <rchikatw(a)redhat.com> wrote:
>> Vincent,
>>
>>
>> This document will be useful
>>
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_...
>>
>> On Wed, Sep 23, 2020, 3:55 AM Vincent Royer <vincent(a)epicenergy.ca> wrote:
>>> I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How do I
upgrade to 4.4? Is there a guide?
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TCX2RUE5RN7...
>>>
>>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J6IERH7OAO6...
>
10:02 p.m.
Not to give you any false hope, but when I recently reinstalled my oVirt
4.4.2 cluster, I left the gluster disks alone and only reformatted the
OS disks. Much to my surprise, after running the oVirt HCI wizard on
this new installation (using the exact same gluster settings as before),
the original contents of my gluster-based data domain were still intact.
I certainly wouldn't count on this behavior with any important data, though.
--Mike
On 9/23/20 1:40 PM, Vincent Royer wrote:
well that sounds like a risky nightmare. I appreciate your help.
*Vincent Royer*
*778-825-1057*
<http://www.epicenergy.ca/>
*SUSTAINABLE MOBILE ENERGY SOLUTIONS*
On Wed, Sep 23, 2020 at 11:31 AM Strahil Nikolov <hunter86_bg(a)yahoo.com>
wrote:
> Before you reinstall the node , you should use 'gluster volume
> remove-brick <VOL> replica <old number - 1>
ovirt_node:/path-to-brick' to
> reduce the volume to replica 2 (for example). Then you need to 'gluster
> peer detach ovirt_node' in order to fully cleanup the gluster TSP.
>
> You will have to remove the bricks that are on that < ovirt_node > before
> detaching it.
>
> Once you reinstall with EL 8, you can 'gluster peer probe
> <reinstalled_ovirt_node>' and then 'gluster volume add-brick
<VOL> replica
> <current count + 1> reinstalled_ovirt_node:/path-to-brick.
>
> Note that reusing bricks is not very easy, so just wipe the data via
> 'mkfs.xfs -i size=512 /dev/block/device'.
>
> Once all volumes are again a replica 3 , just wait for the healing to go
> over and you can proceed with the oVirt part.
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
> В сряда, 23 септември 2020 г., 20:45:30 Гринуич+3, Vincent Royer <
> vincent(a)epicenergy.ca> написа:
>
>
>
>
>
> My confusion is that those documents do not describe any gluster related
> tasks for Ovirt Nodes. When I take a node down and install Ovirt Node 4.4
> on it, won't all the gluster bricks on that node be lost? The part
> describing "preserving local storage", that isn't anything about
Gluster,
> correct?
>
>
> Vincent Royer
> 778-825-1057
>
>
> SUSTAINABLE MOBILE ENERGY SOLUTIONS
>
>
>
>
>
> On Tue, Sep 22, 2020 at 8:31 PM Ritesh Chikatwar <rchikatw(a)redhat.com>
> wrote:
>> Vincent,
>>
>>
>> This document will be useful
>>
>
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_...
>>
>> On Wed, Sep 23, 2020, 3:55 AM Vincent Royer <vincent(a)epicenergy.ca>
> wrote:
>>> I have 3 nodes running node ng 4.3.9 with a gluster/hci cluster. How
> do I upgrade to 4.4? Is there a guide?
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-leave(a)ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TCX2RUE5RN7...
>>>
>>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/J6IERH7OAO6...
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NXLHNX2ABBG...
6:43 p.m.
I am hoping for a miracle like that, too.
In the mean-time I am trying to make sure that all variants of exports and imports from
*.ova to re-attachable NFS domains work properly, in case I have to start from scratch.
HCI upgrades don't get the special love you'd expect after RHV's proud
announcement that they are now ready to take on Nutanix and vSAN.
8:01 p.m.
Interested to hear how upgrading 4.3 HCI to 4.4 goes. I've been considering
it in my environment but was thinking about moving all VMs off to NFS
storage then rebuilding oVirt on 4.4 and importing.
On Thu, Sep 24, 2020 at 1:45 PM <thomas(a)hoberg.net> wrote:
I am hoping for a miracle like that, too.
In the mean-time I am trying to make sure that all variants of exports and
imports from *.ova to re-attachable NFS domains work properly, in case I
have to start from scratch.
HCI upgrades don't get the special love you'd expect after RHV's proud
announcement that they are now ready to take on Nutanix and vSAN.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2HVZDUABWK...
12:22 a.m.
It's a bit disheartening that HCI users don't have an easier upgrade path.
So far there's a lot of 'this might work' or' that might work', and
good
luck. Certainly doesn't inspire much confidence.
Every time there is a survey asking what the pain points are, I say
"updates!!", but they seem to be getting more and more complicated.
On Thu., Sep. 24, 2020, 11:06 a.m. Jayme, <jaymef(a)gmail.com> wrote:
Interested to hear how upgrading 4.3 HCI to 4.4 goes. I've been
considering it in my environment but was thinking about moving all VMs off
to NFS storage then rebuilding oVirt on 4.4 and importing.
On Thu, Sep 24, 2020 at 1:45 PM <thomas(a)hoberg.net> wrote:
> I am hoping for a miracle like that, too.
>
> In the mean-time I am trying to make sure that all variants of exports
> and imports from *.ova to re-attachable NFS domains work properly, in case
> I have to start from scratch.
>
> HCI upgrades don't get the special love you'd expect after RHV's proud
> announcement that they are now ready to take on Nutanix and vSAN.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2HVZDUABWK...
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZKWFAVDI5L2...
5:43 a.m.
Have you checked the oVirt 2020 conference videos ?
There was a slot exactly on this topic- I think ansible was used for automatic upgrade.
I prefer the manual approach , as I have full control over the environment.
Best Regards,
Strahil Nikolov
В петък, 25 септември 2020 г., 02:23:49 Гринуич+3, Vincent Royer via Users
<users(a)ovirt.org> написа:
It's a bit disheartening that HCI users don't have an easier upgrade path.
So far there's a lot of 'this might work' or' that might work', and
good luck. Certainly doesn't inspire much confidence.
Every time there is a survey asking what the pain points are, I say "updates!!",
but they seem to be getting more and more complicated.
On Thu., Sep. 24, 2020, 11:06 a.m. Jayme, <jaymef(a)gmail.com> wrote:
Interested to hear how upgrading 4.3 HCI to 4.4 goes. I've been
considering it in my environment but was thinking about moving all VMs off to NFS storage
then rebuilding oVirt on 4.4 and importing.
On Thu, Sep 24, 2020 at 1:45 PM <thomas(a)hoberg.net> wrote:
> I am hoping for a miracle like that, too.
>
> In the mean-time I am trying to make sure that all variants of exports and imports
from *.ova to re-attachable NFS domains work properly, in case I have to start from
scratch.
>
> HCI upgrades don't get the special love you'd expect after RHV's proud
announcement that they are now ready to take on Nutanix and vSAN.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2HVZDUABWK...
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZKWFAVDI5L2...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/V6GFJJJI4RI...
3:33 p.m.
I was looking forward to that presentation for exactly that reason: But it completely
bypassed the HCI scenario, was very light on details and of course assumed that everything
would just work, because there is no easy fail-back and you're probably better off
taking down the complete farm during the upgrade. If you are actually depending on that
farm to operate,...
In the mean-time I try to make sure I have a plan-B and C solution in case the official
procedure fails, but have *.ova (plan-C) imports fail (again) in extract_ova.py on the
single-node 4.4.2 HCI cluster that I have set up as target to do migration testing... a
bug far to familiar for a newest release.
I'll be testing re-attachable NFS domains next (plan-B), but for me *.ova exports and
imports are still the most fundmental operations any hypervisor needs to support: If OVA
is the wrong file format, fine, just do another one. But IMHO turning a machine into a
file and a file into a machine is the very definition of what hypervisors do. And a
release that doesn't seem to test this operation, does not rhyme with "solution
for your entire enterprise" on the oVirt home page.
1312
days inactive
1316
days old
11 comments
6 participants
participants (6)
-
Jayme -
Michael Thomas -
Ritesh Chikatwar -
Strahil Nikolov -
thomas＠hoberg.net -
Vincent Royer